Bug#935914: kinit: Signal: Segmentation fault (11) after rebooting

2019-10-12 Thread Ralf Jung
After a big dist-upgrade I just did (and a reboot), I am not also experiencing kdeinit5 crashes. There's a notification popping up every now and then telling me it crashed. However it doesn't let me report a bug (looks like no bug reporting URL is set, or so); so I am not sure how to even capture

Bug#935914: kinit: Signal: Segmentation fault (11) after rebooting

2019-08-27 Thread Nicholas D Steeves
I'm still not sure how to reliably reproduce this bug, but the kdeinit5 crashes have continued to occur every ~30min today (within a single session). The memory usage spike I mentioned in a previous message seems to be caused by baloosearch.so ... which didn't have this issue in stretch. The backt

Bug#935914: kinit: Signal: Segmentation fault (11) after rebooting

2019-08-27 Thread Nicholas D Steeves
Wow, it was harder than expected to get the dbsym packages without a security-debug suite. Thanks to adsb and ansgar on #debian-qt-kde for the help (adds additional steps to my easy useful backtraces for end users plan). Here it is: Application: kdeinit5 (kdeinit5), signal: Segmentation fault Us

Bug#935914: kinit: Signal: Segmentation fault (11) after rebooting

2019-08-27 Thread Nicholas D Steeves
Package: kinit Version: 5.54.0-1 Severity: important Hi, I haven't been able to reproduce this 100% of the time, but it happens some of the time after logging in after rebooting. I have a system load monitor and have noticed that memory balloons and system responsiveness drops right before the c