Summary: | Plasma Desktop crashes on login (Python fatal error) | ||
---|---|---|---|
Product: | [Developer tools] bindings | Reporter: | Patrick "Finn" Robins <13.finn> |
Component: | pykde | Assignee: | kde-bindings |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | andresbajotierra, aseigo, asraniel, cpigat242 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | patch for wallpaper-clock 0.6 as workaround |
Description
Patrick "Finn" Robins
2010-12-09 02:22:57 UTC
After noticing a very similar bug report where the reporter mentioned running wallpaper clocks I turned mine off. For the first time in awhile I can log in and the plasma desktop didn't crash. I will try to verify if this actually fixes the and if I can replicate the isssue. [Comment from a bug triager] The crash is related to the Python Qt bindings used by the Python powered plasmoids. - Which third-party plasmoids are you using ? do you know if any of them use the Python engine ? Probably related to bug 243119. Regards Created attachment 79836 [details]
patch for wallpaper-clock 0.6 as workaround
For me, wallpaper-clocks (which is written in python) sometimes crashes at login if I two wallpaper-clocks are loaded in dual monitor setup.
For those who want a quick workaround:
I added a patch that removes concurrency from wallpaper-clock; this seems to be responsible for messing up and crashing python. (I've looked at the code superficially and could not find the exact reason.)
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. 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 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! Hello, unfortunately this bug is being closed as unmaintained, per request of einar77. |