Bug#794110: More info needed

2016-04-08 Thread 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

Bug#794110: More info needed

2016-04-04 Thread 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

Bug#794110: More info needed

2016-03-31 Thread 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 signatu

Bug#794110: More info needed

2016-03-22 Thread 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'

Bug#794110: More info needed

2016-03-19 Thread 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 0x7f5376

Bug#794110: More info needed

2016-03-19 Thread 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

Bug#794110: More info needed

2016-03-18 Thread 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/libQt5Qm