Bug#803451: kactivities: kactivitymanage segfaults on logout

2015-11-17 Thread Lisandro Damián Nicanor Pérez Meyer
After digging the web my suspicion is that the problem comes from plugins being unloaded when they should not. Upstream is currently looking at that issue. Maybe we can backport the fix or maybe we need to wait for 5.6 :-/ -- Lo que me sorprende de las mujeres es que se arrancan los pelos

Bug#803451: kactivities: kactivitymanage segfaults on logout

2015-11-03 Thread Andy G Wood
Hi Lisandro, After applying all the updates to testing in the past few days (up to date as of 3rd November), I can confirm that the problem is still there today: Nov 3 09:01:53 kernel: [85668.293452] kactivitymanage[32057]: segfault at 7f35e2794cd0 ip 7f35d004b291 sp 7fff55d905e8

Bug#803451: kactivities: kactivitymanage segfaults on logout

2015-11-01 Thread Diederik de Haas
On Sunday 01 November 2015 14:52:16 Lisandro Damián Nicanor Pérez Meyer wrote: > This is probably due to #802811, please update your system and try again. Not in my case, it's still segfaulting here: $ dmesg | grep kactivitymanage [ 183.490848] kactivitymanage[1656]: segfault at 7f904f07ecd0 ip

Bug#803451: kactivities: kactivitymanage segfaults on logout

2015-11-01 Thread Lisandro Damián Nicanor Pérez Meyer
tag 803451 moreinfo thanks Hi Andy! This is probably due to #802811, please update your system and try again. -- Nearly all men can stand adversity, but if you want to test a man's character, give him power. Abraham Lincoln Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/

Bug#803451: kactivities: kactivitymanage segfaults on logout

2015-10-30 Thread Andy Wood
Package: kactivities Version: 5.15.0-1 Severity: normal Dear Maintainer, Reliably on every logout, kactivitymanage segfaults: $ dmesg | grep kactivitymanage [23749.771197] kactivitymanage[2884]: segfault at 7f5854b06cd0 ip 7f58385421b1 sp 7ffca2a92e88 error 4 in

Bug#803451: kactivities: kactivitymanage segfaults on logout

2015-10-30 Thread Diederik de Haas
Package: kactivities Version: 5.15.0-1 Followup-For: Bug #803451 Saw this bug come by in the ML and checked for myself and noticed the same issue, only with a newer version of QT. Thus I'm filing this report so that it's known to also happen with QT 5.5. -- System Information: Debian Release: