Bug#794110: More info needed

[Thomas Preud'homme]

Le mercredi 16 mars 2016, 10:16:18 Lisandro Damián Nicanor Pérez Meyer a écrit 
:
> tag 794110 moreinfo
> thanks
> 
> Hi everyone! With my Qt maintainer hat on, I would like you to give me some
> info.
> 
> First: We have only one backtrace coming from the original submitter. Can
> the rest of you check if when a crash happens the current thread's (the
> crashing one) backtrace says something like:

Hi Lisandro,

I hope you are doing well.

Sorry for the late answer, I was in the middle of a relocation and didn't 
touch my computer much. I haven't had any crash since I have so the bug seems 
to be solved on my side. I'll update the bug report if I ever get a new crash 
in the following (14) days but I don't expect to.

Best regards,

Thomas

signature.asc
Description: This is a digitally signed message part.

Re: Bug#794110: More info needed

[Francois Gouget]

On Fri, 1 Apr 2016, Diederik de Haas wrote:

> On Friday 18 March 2016 19:57:52 Francois Gouget wrote:
> > I installed plasma-workspace-dbg and got a new crash so here is the 
> > backtrace for the crashing thread. Unfortunately I did not find a dbg 
> > package for libqt5qml5.
> 
> qtbase5-dbg and qtdeclarative5-dbg may provide (even) more info

I installed these two packages. This does help. Now most backtrace 
entries have function names and source file line numbers:

Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7efe1f6fc940 (LWP 5703))]

Thread 7 (Thread 0x7efe09c23700 (LWP 5712)):
#0  0x7efe19e46e4d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7efe1def9382 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7efe1defaff7 in xcb_wait_for_event () from 
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7efe0af1a789 in QXcbEventReader::run (this=0x17fa540) at 
qxcbconnection.cpp:1230
#4  0x7efe1a52b7fe in QThreadPrivate::start (arg=0x17fa540) at 
thread/qthread_unix.cpp:331
#5  0x7efe1964f454 in start_thread (arg=0x7efe09c23700) at 
pthread_create.c:334
#6  0x7efe19e4fedd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7efe031d2700 (LWP 5884)):
#0  0x7efe16c37a79 in g_mutex_lock () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7efe16bf28c9 in g_main_context_prepare () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7efe16bf325b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7efe16bf343c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7efe1a762a5b in QEventDispatcherGlib::processEvents 
(this=0x7efdfc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7efe1a709d6a in QEventLoop::exec (this=this@entry=0x7efe031d1c60, 
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7efe1a526854 in QThread::exec (this=this@entry=0x18ddc40) at 
thread/qthread.cpp:503
#7  0x7efe1cdb9105 in QQmlThreadPrivate::run (this=0x18ddc40) at 
qml/ftw/qqmlthread.cpp:141
#8  0x7efe1a52b7fe in QThreadPrivate::start (arg=0x18ddc40) at 
thread/qthread_unix.cpp:331
#9  0x7efe1964f454 in start_thread (arg=0x7efe031d2700) at 
pthread_create.c:334
#10 0x7efe19e4fedd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7efdf9b53700 (LWP 5892)):
#0  0x7efe16c37a94 in g_mutex_unlock () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7efe16bf28b0 in g_main_context_prepare () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7efe16bf325b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7efe16bf343c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7efe1a762a5b in QEventDispatcherGlib::processEvents 
(this=0x7efdf40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7efe1a709d6a in QEventLoop::exec (this=this@entry=0x7efdf9b52c60, 
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7efe1a526854 in QThread::exec (this=this@entry=0x1b6ce00) at 
thread/qthread.cpp:503
#7  0x7efe1cdb9105 in QQmlThreadPrivate::run (this=0x1b6ce00) at 
qml/ftw/qqmlthread.cpp:141
#8  0x7efe1a52b7fe in QThreadPrivate::start (arg=0x1b6ce00) at 
thread/qthread_unix.cpp:331
#9  0x7efe1964f454 in start_thread (arg=0x7efdf9b53700) at 
pthread_create.c:334
#10 0x7efe19e4fedd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7efdf39c7700 (LWP 5896)):
#0  0x7efe19e46e4d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7efe16bf332c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7efe16bf343c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7efe1a762a5b in QEventDispatcherGlib::processEvents 
(this=0x7efdec0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7efe1a709d6a in QEventLoop::exec (this=this@entry=0x7efdf39c6c60, 
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7efe1a526854 in QThread::exec (this=this@entry=0x1c55250) at 
thread/qthread.cpp:503
#6  0x7efe1cdb9105 in QQmlThreadPrivate::run (this=0x1c55250) at 
qml/ftw/qqmlthread.cpp:141
#7  0x7efe1a52b7fe in QThreadPrivate::start (arg=0x1c55250) at 
thread/qthread_unix.cpp:331
#8  0x7efe1964f454 in start_thread (arg=0x7efdf39c7700) at 
pthread_create.c:334
#9  0x7efe19e4fedd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7efdf20b6700 (LWP 5902)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7efe1f1661c4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7efe1f166209 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7efe1964f454 in start_thread (arg=0x7efdf20b6700) at 

Bug#794110: More info needed

[Diederik de Haas]

On Friday 18 March 2016 19:57:52 Francois Gouget wrote:
> I installed plasma-workspace-dbg and got a new crash so here is the 
> backtrace for the crashing thread. Unfortunately I did not find a dbg 
> package for libqt5qml5.

qtbase5-dbg and qtdeclarative5-dbg may provide (even) more info

signature.asc
Description: This is a digitally signed message part.

Bug#794110: More info needed

[Sven-Haegar Koch]

On Wed, 16 Mar 2016, Lisandro Damián Nicanor Pérez Meyer wrote:

> Hi everyone! With my Qt maintainer hat on, I would like you to give me some 
> info.
> 
> First: We have only one backtrace coming from the original submitter. Can the 
> rest of you check if when a crash happens the current thread's (the crashing 
> one) backtrace says something like:

There have been lots of updates to both Qt and KDE in the meantime, and 
I did not see this plasmashell crash for quite a while anymore.

But I also restart kwin_x11 --replace regulary since a while, because 
after running some days (without problems) it starts leaving some 
window-contents (xterm) black, rendering errors on text-scrolling in 
Firefox or just-closed windows stay visible on the desktop background. 
Since these errors are very difficult to describe and quickly reproduce 
I did not report this.

Once of the systems with had the crash problem and also the current one:

Module 'org.kde.kwin.decoration' does not contain a module identifier directive 
- it cannot be protected from external registrations.
QXcbConnection: XCB error: 8 (BadMatch), sequence: 3783, resource id: 62914576, 
major code: 42 (SetInputFocus), minor code: 0
OpenGL vendor string:   Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Mobile Intel® GM45 Express 
Chipset x86/MMX/SSE2
OpenGL version string:  2.1 Mesa 11.1.2
OpenGL shading language version string: 1.20
Driver: Intel
GPU class:  i965
OpenGL version: 2.1
GLSL version:   1.20
Mesa version:   11.1.2
X server version:   1.18
Linux kernel version:   4.3
Requires strict binding:yes
GLSL shaders:   yes
Texture NPOT support:   yes
Virtual Machine:no
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 4789, resource id: 0, 
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 4799, resource id: 0, 
major code: 14 (GetGeometry), minor code: 0

The other two where I saw it had different Intel onboard graphics (all 
laptops)

c'ya
sven-haegar

-- 
Three may keep a secret, if two of them are dead.
- Ben F.

Bug#794110: More info needed

[Lisandro Damián Nicanor Pérez Meyer]

tag 794110 moreinfo
thanks

Hi everyone! With my Qt maintainer hat on, I would like you to give me some 
info.

First: We have only one backtrace coming from the original submitter. Can the 
rest of you check if when a crash happens the current thread's (the crashing 
one) backtrace says something like:

Thread 1 (Thread 0x7f5376449940 (LWP 18333)):
[KCrash Handler]
#6  0x7f5373d1d1b9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f5373f860c8 in QQmlDelegateModel::_q_itemsChanged(int, int, 
QVector const&) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f5373fadd2c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7f5373fae46f in QQmlDelegateModel::qt_metacall(QMetaObject::Call, 
int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x7f53718d723a in QMetaObject::activate(QObject*, int, int, void**) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5

or is it different?

Second: as this seems to be QML-related I would like to know which video card 
and drivers (proprietary or not) are you using.

This might or not be a Qt bug, but as long as we can't reproduce it with a 
minimal example or get some more information it is difficult to say.

Qt 5.6.0 has been released today, but we are not going to push it to unstable 
until 5.6.1 comes out (between 4 to 8 weeks more) due to the need of a 
transition.


Kinds regards, Lisandro.

-- 
Super cow powers | bbq > /dev/stomach
  Traveler1, seen on #debian-ar, irc.oftc.net

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Bug#794110: More info needed

[Francois Gouget]

On Wed, 16 Mar 2016, Lisandro Damián Nicanor Pérez Meyer wrote:
[...]
> First: We have only one backtrace coming from the original submitter. Can the 
> rest of you check if when a crash happens the current thread's (the crashing 
> one) backtrace says something like:
> 
> Thread 1 (Thread 0x7f5376449940 (LWP 18333)):
> [KCrash Handler]
> #6  0x7f5373d1d1b9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
> #7  0x7f5373f860c8 in QQmlDelegateModel::_q_itemsChanged(int, int, 
> QVector const&) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
> #8  0x7f5373fadd2c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
> #9  0x7f5373fae46f in QQmlDelegateModel::qt_metacall(QMetaObject::Call, 
> int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
> #10 0x7f53718d723a in QMetaObject::activate(QObject*, int, int, void**) 
> () 
> from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
> 
> or is it different?

I have the same stack in the crashing thread. I have attached a fresh 
backtrace (which the crash reporting assistant says does not contain 
enough information).


> Second: as this seems to be QML-related I would like to know which video card 
> and drivers (proprietary or not) are you using.

I use the integrated GPU of my i7-4790K CPU. Intel says it's an Intel
HD Graphics 4600 GPU.
http://ark.intel.com/fr/products/80807/Intel-Core-i7-4790K-Processor-8M-Cache-up-to-4_40-GHz

The driver is open-source and provided by xserver-xorg-video-intel 
2:2.99.917+git20160218-1.


I have also run into a bunch of other issues which may or may not be 
related and may point to a driver or compositor issue or other:
 * When I close a window its image sometimes lingers on until I switch 
   focus between two windows, or erase it by moving a window around. 
   Note that this is not just the background not being repainted as it 
   also affects the windows that were behind it.
 * I use Google Chrome to displays photographs, one per tab. Sometimes 
   switching between tabs does not completely repaint the tab, forcing 
   me to switch back and forth a few times to get it to work.
 * I also sometimes, but quite rarely, get this when I switch between 
   Konsole tabs.

-- 
Francois Gouget   http://fgouget.free.fr/
May your Tongue stick to the Roof of your Mouth with the Force of a Thousand 
Caramels.Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1693995940 (LWP 10876))]

Thread 7 (Thread 0x7f167dedf700 (LWP 10884)):
#0  0x7f168e0ddb6d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f1692192382 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f1692193ff7 in xcb_wait_for_event () from 
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f167f1d55b9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f168e7c288e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f168d8df284 in start_thread (arg=0x7f167dedf700) at 
pthread_create.c:333
#6  0x7f168e0e6a4d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f16775ef700 (LWP 10897)):
#0  0x7f168aec9899 in g_mutex_lock () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f168ae851b2 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f168ae852dc in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f168e9fa2db in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f168e9a12ea in 
QEventLoop::exec(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f168e7bd8d4 in QThread::exec() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f1691052105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f168e7c288e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f168d8df284 in start_thread (arg=0x7f16775ef700) at 
pthread_create.c:333
#9  0x7f168e0e6a4d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f166dd5d700 (LWP 10926)):
#0  0x7f168aec98b4 in g_mutex_unlock () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f168ae841ce in g_main_context_acquire () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f168ae85085 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f168ae852dc in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f168e9fa2db in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f168e9a12ea in 
QEventLoop::exec(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f168e7bd8d4 in QThread::exec() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f1691052105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f168e7c288e in ?? () from 

Bug#794110: More info needed

[Francois Gouget]

I installed plasma-workspace-dbg and got a new crash so here is the 
backtrace for the crashing thread. Unfortunately I did not find a dbg 
package for libqt5qml5.

Thread 1 (Thread 0x7f49f97b7940 (LWP 8428)):
[KCrash Handler]
#6  0x7f49f6c46358 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f49f6eb597a in QQmlDelegateModel::_q_itemsChanged(int, int, 
QVector const&) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f49f6edd04c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7f49f6edd838 in QQmlDelegateModel::qt_metacall(QMetaObject::Call, 
int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x7f49f47f4860 in QMetaObject::activate(QObject*, int, int, void**) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f49f4870bbc in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f49c8304884 in TaskManager::TasksModelPrivate::itemChanged 
(this=0x3c5b7b0, changes=...) at 
/build/plasma-workspace-KFkJSD/plasma-workspace-5.4.3/libtaskmanager/tasksmodel.cpp:521
#13 0x7f49c8305b07 in TaskManager::TasksModel::qt_static_metacall 
(_o=, _c=, _id=, 
_a=0x7ffdbae20ba0) at 
/build/plasma-workspace-KFkJSD/plasma-workspace-5.4.3/obj-x86_64-linux-gnu/libtaskmanager/moc_tasksmodel.cpp:214
#14 0x7f49f47f46aa in QObjectPrivate::~QObjectPrivate() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0xc55653c6e1c0fb00 in ?? ()
#16 0x7f49c852b6f0 in __bss_start () from 
/usr/lib/x86_64-linux-gnu/libtaskmanager.so.5
#17 0x7f49c8300aba in TaskManager::TaskManager::taskChanged 
(this=0x4387050, changes=...) at 
/build/plasma-workspace-KFkJSD/plasma-workspace-5.4.3/libtaskmanager/taskmanager.cpp:385
#18 0x7f49c830da28 in TaskManager::AbstractGroupableItem::changed 
(this=, _t1=...) at 
/build/plasma-workspace-KFkJSD/plasma-workspace-5.4.3/obj-x86_64-linux-gnu/libtaskmanager/moc_abstractgroupableitem.cpp:223
#19 0x7f49c82faf70 in TaskManager::TaskItemPrivate::filterChange 
(change=..., this=) at 
/build/plasma-workspace-KFkJSD/plasma-workspace-5.4.3/libtaskmanager/taskitem.cpp:73
#20 TaskManager::TaskItem::qt_static_metacall (_o=, 
_c=, _id=, _a=) at 
/build/plasma-workspace-KFkJSD/plasma-workspace-5.4.3/obj-x86_64-linux-gnu/libtaskmanager/moc_taskitem.cpp:147
#21 0x7f49f47f46aa in QObjectPrivate::~QObjectPrivate() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x0e10 in ?? ()
#23 0x01bdab60 in ?? ()
#24 0x in ?? ()


Also here is more information about my configuration:

Video card:
$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th 
Gen Core Processor Integrated Graphics Controller (rev 06)

Video driver:
$ lsmod | grep 915
snd_hda_codec_hdmi 49152  1
i915 1122304  16
drm_kms_helper131072  1 i915
drm   348160  17 i915,drm_kms_helper
i2c_algo_bit   16384  1 i915
video  36864  2 i915,asus_wmi
button 16384  1 i915
parport49152  3 lp,ppdev,parport_pc
usbhid 49152  0


Kernel:
$ cat /proc/version
Linux version 4.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc 
version 5.3.1 20160121 (Debian 5.3.1-7) ) #1 SMP Debian 4.3.5-1 
(2016-02-06)


-- 
Francois Gouget   http://fgouget.free.fr/
The nice thing about meditation is that it makes doing nothing quite respectable
  -- Paul Dean