#1821 received signal 11 -- Lenovo LifeTab E10320

[Anonymous]

libmtp reported (via qlix):
Device 0 (VID=17ef and PID=775a) is a Lenovo LifeTab E733X.
Android device detected, assigning default bug flags
Ouch! - Qlix received signal 11
Segmentation fault (core dumped)

---

KUbuntu 16.04 reported:
LIFETAB_E10320
"file access is okay"

---

Tablet reported:
LIFETAB E10320
Android 4.2.2
Kernel 3.0.36+

---

What does signal 11 mean?

[Marcus Meissner]

it is a bug in the software that led to a crash.

can you run it in gdb?

gdb qlix

on the prompt type "run"

and once it gets signal 11, can you run "bt" and paste the content here?

[Anonymous]

(gdb) run
Starting program: /usr/bin/qlix
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xb24b6b40 (LWP 18444)]
[New Thread 0xb1affb40 (LWP 18445)]
Device 0 (VID=17ef and PID=775a) is a Lenovo LifeTab E733X.
Android device detected, assigning default bug flags

Thread 2 "MtpWatchDog" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb24b6b40 (LWP 18444)]
__strlen_sse2_bsf () at ../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S:50
50 ../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S: No such file or directory.
(gdb) bt

0 __strlen_sse2_bsf () at ../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S:50

1 0x08055cc7 in ?? ()

2 0x08059840 in ?? ()

3 0x08057272 in ?? ()

4 0x0806ba7d in ?? ()

5 0x08079d79 in ?? ()

6 0xb7044d3e in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4

7 0xb6fc6295 in start_thread (arg=0xb24b6b40) at pthread_create.c:333

8 0xb6d5d0ae in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

(gdb)

[Anonymous]

With KUbuntu + Dolphin it says:
1. camera:
Lenovo LifeTab E733X
2. mtp:
LIFETAB_E10320