Summary: | kdeinit4 crashing after logon | ||
---|---|---|---|
Product: | [Plasma] KScreen | Reporter: | gpe <coolmojo> |
Component: | kded | Assignee: | Alex Fiestas <afiestas> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | christian_bay, dantti12, dvratil, info, jlupox, jr, kde.stratic, rohan |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kscreen/ffe2de800c74b4a927f194568511c813f9c5ffc7 | Version Fixed In: | 1.0 |
Attachments: |
Crash report
Output of kscreen-console bug KCrash report |
Description
gpe
2013-04-26 08:23:19 UTC
Created attachment 79455 [details]
Crash report
Reassigning to kscreen developers, because of the crash KScreen::Output::id. There is, however, some wiredness going on with "kded_colord.so", most certainly using synchronous D-Bus calls. I thought we were pretty clear that synchronous D-Bus call are a no-go in a kded module. Adding colord maintainer. Are you running a laptop, or a workstation? Could you please provide output from "kscreen-console bug" ? Created attachment 79465 [details]
Output of kscreen-console bug
I am running laptop with nvidia driver (304.88). Please find the kscreen-console bug output attached.
Git commit ffe2de800c74b4a927f194568511c813f9c5ffc7 by Dan Vrátil. Committed on 26/04/2013 at 18:54. Pushed by dvratil into branch 'master'. Fix crash when embeddedOutput() fails to detect embedded output Some laptops (probably older models) use 'VGA-*' to identify embedded outputs, so embeddedOutput() will fail, because it only looks for modern 'LVDS', 'EDP', etc. In such case, just try to use the output with lowest ID. It's highly probably that it will be the right one. We should also try to come up with some really reliable method, instead of name-based guessing. FIXED-IN: 1.0 M +11 -2 kded/generator.cpp http://commits.kde.org/kscreen/ffe2de800c74b4a927f194568511c813f9c5ffc7 Same here. Exact same stacktrace. This is really a bummer because without KDED, *NOTHING* works. Also a laptop setup with proprietary nvidia-driver, KDED runs fine until I dock the laptop (and thus add an external monitor). Created attachment 79471 [details]
KCrash report
Oh, and this also happened after update to Ubuntu 13.04.
*** Bug 319005 has been marked as a duplicate of this bug. *** You can disable the "KScreen 2" kded from systemsettings-->startup and shutdown -->Services Will try to fix asap. @Alex Fiestas: Thank you, I'll try that, but I think this will work for me. Thanks! Got the solution figured out, will implement and try to release tomorrow. Thanks and sorry for the mess :( *** Bug 319051 has been marked as a duplicate of this bug. *** *** Bug 319108 has been marked as a duplicate of this bug. *** Forgot to close the bug, this has been fix in 0.0.92 (RC2) Thanks for reporting ! (In reply to comment #14) > Forgot to close the bug, this has been fix in 0.0.92 (RC2) > > Thanks for reporting ! Thanks for fixing it :) Hi As part of the SRU process in Ubuntu we require testing of our packages before the package is released into Ubuntu. The kscreen packages to be tested can be found here https://launchpad.net/~kubuntu-ppa/+archive/experimental The SRU bug can be found here : https://bugs.launchpad.net/ubuntu/+source/kscreen/+bug/1177333 Steps to add the PPA on raring: sudo add-apt-repository ppa:kubuntu-ppa/experimental sudo apt-get update sudo apt-get install kscreen Once done, please logout and login, and check if plasma still crashes. @Rohan: There is no more crash at startup with the experimental package. But kscreen did not works anymore with it... In the system settings, the display configuration panel reports the following error: "No supported X Window system extension found" kscreen-console reports the following: START kscreen-console(9742) BackendLoader::init: No KScreen backend set! Config::current() took 0 milliseconds Config is invalid, probably backend couldn't load @stratic Could you paste the output of the command : apt-cache policy libkscreen0 kscreen I believe this is caused by having a older libkscreen0 , so please update libkscreen0 as well and then check if it still causes the issue. @Rohan libkscreen0 was not updated automatically after a simple : "sudo apt-get install kscreen". Now, after an explicit libkscreen0 update request, kscreen works properly. Thank's you Ack. Minor packaging issue, will be uploading a fixed package to Ubuntu shortly :) stratic: can you also sudo apt-get install libkscreen0 and test again? Ignore my last comment, I see you've done it already thanks :) |