Summary: | System settings crashes after exiting from multimedia with unsaved changes | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | nakki <titibanjekistan> |
Component: | general | Assignee: | System Settings Bugs <sourtooth+ssbugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | cfeck |
Priority: | NOR | Keywords: | investigated, triaged |
Version: | 1.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
nakki
2012-02-21 13:51:29 UTC
Did you visit the printer settings page? Are there any other System Settings modules installed that use the Python language? (In reply to comment #1) > Did you visit the printer settings page? I think yes, but I'm not sure...I was watching many settings in that moment... > Are there any other System Settings modules installed that use the Python language? I don't know...Can you explain the question, please? The problem with the backtrace from comment #0 is that it does not reveal which System Settings module (Printer settings, Language settings etc.) is responsible for the crash, since the backtrace only shows a crash in the Python interpreter. To find out which modules are using the Python interpreter, you would have to check your installation, as KDE itself only supplies the Printer module implemented in Python. Many other third-party (synaptiks, grub manager, etc.) or distribution specific (language installation, user management, etc.) modules are also written in Python. Since we are getting many duplicates of this crash, it would be nice to have a list of possible offenders. It could also be a bug in the Python interpreter or bindings, but that is impossible to tell from the backtrace. How do I know if I have other python modules in addition to that printer? 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! |