| Summary: | crash after closing system settings since upgrading to 11.10 | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | michael <jnt2880> |
| Component: | general | Assignee: | System Settings Bugs <sourtooth+ssbugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | cfeck, gapon007, mpgkde |
| Priority: | NOR | Keywords: | investigated, triaged |
| Version First Reported In: | 1.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
michael
2011-10-18 21:01:01 UTC
Did you visit the printer settings page? Are there any other System Settings modules installed that use the Python language? If you can provide the information requested in comment #1, please add it. If the crash is caused by visiting the printer settings page, it would be a duplicate of bug 283611. *** Bug 284991 has been marked as a duplicate of this bug. *** Created attachment 64976 [details]
New crash information added by DrKonqi
systemsettings (1.0) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4
- What I was doing when the application crashed:
I had just asked the printer to print a test page.
I previously had crashes when deleting a printer and when adding a printer.
-- Backtrace (Reduced):
#6 0x00007f9e4cdce0f5 in QHash<void*, PyQtProxy*>::duplicateNode(QHashData::Node*, void*) () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
#7 0x00007f9e6206c637 in QHashData::detach_helper2 (this=0x205f050, node_duplicate=0x7f9e4cdce0f0 <QHash<void*, PyQtProxy*>::duplicateNode(QHashData::Node*, void*)>, node_delete=0x7f9e4cdce0e0 <QHash<void*, PyQtProxy*>::deleteNode2(QHashData::Node*)>, nodeSize=<optimized out>, nodeAlign=8) at tools/qhash.cpp:235
#8 0x00007f9e4cdd2ca7 in sipQtFindSipslot () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
#9 0x00007f9e4ca4571e in sipWrapper_traverse (arg=0x0, visit=0x7f9e4dc8b620 <visit_decref>, self=0x2167170) at /build/buildd/sip4-4.12.4/siplib/siplib.c:9648
#10 sipWrapper_traverse (self=0x2167170, visit=0x7f9e4dc8b620 <visit_decref>, arg=0x0) at /build/buildd/sip4-4.12.4/siplib/siplib.c:9629
I am not really sure anymore, but it is possible that I may have tried to add a new network printer to the system. I had to get my system back up and running in working order so, I just went and did a complete new install of my dual boot system. Did not want to get stuck with only windows. The new install did not take very long since I do routine backups of certain folders. 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 set the bug status 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! Dear Bug Submitter, 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! |