Bug 409770 - kdeinit5 crashed with SIGABRT in qt_message_fatal() / NewPrinterNotification
Summary: kdeinit5 crashed with SIGABRT in qt_message_fatal() / NewPrinterNotification
Status: RESOLVED WORKSFORME
Alias: None
Product: print-manager
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Daniel Nicoletti
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-13 13:03 UTC by Nathaniel Beaver
Modified: 2022-11-02 05:06 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Thread stack trace (26.13 KB, text/plain)
2019-07-13 13:03 UTC, Nathaniel Beaver
Details
Stack trace (all threads) (5.60 KB, text/plain)
2019-07-13 13:06 UTC, Nathaniel Beaver
Details
Process status (1.36 KB, text/plain)
2019-07-13 13:08 UTC, Nathaniel Beaver
Details
Process memory mappings (163.77 KB, text/plain)
2019-07-13 13:09 UTC, Nathaniel Beaver
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nathaniel Beaver 2019-07-13 13:03:49 UTC
Created attachment 121495 [details]
Thread stack trace

I'm still working on the method to reproduce, but I got a nice stack trace so I thought I ought to submit it. This was on the wifi for a university network, so that might be the connection to NewPrinterNotification.

These may be downstream bugs, but I don't see NewPrinterNotification in the stack trace anywhere, so the similarity might end at the SIGABRT and qt_message_fatal() part:

https://bugs.launchpad.net/ubuntu/+source/kinit/+bug/1371864

https://bugs.launchpad.net/ubuntu/+source/kinit/+bug/1723433

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.12.7
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5
$ apt-cache policy kinit
kinit:
  Installed: 5.44.0-0ubuntu1
  Candidate: 5.44.0-0ubuntu1
  Version table:
 *** 5.44.0-0ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
        100 /var/lib/dpkg/status
Comment 1 Nathaniel Beaver 2019-07-13 13:06:58 UTC
Created attachment 121496 [details]
Stack trace (all threads)
Comment 2 Nathaniel Beaver 2019-07-13 13:08:05 UTC
Created attachment 121497 [details]
Process status
Comment 3 Nathaniel Beaver 2019-07-13 13:09:04 UTC
Created attachment 121498 [details]
Process memory mappings
Comment 4 Justin Zobel 2022-10-03 23:55:06 UTC
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 5 Bug Janitor Service 2022-10-18 04:57:52 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2022-11-02 05:06:04 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!