| Summary: | KDE Daemon crashes on login | ||
|---|---|---|---|
| Product: | [Unmaintained] solid | Reporter: | captainknots |
| Component: | powermanagement-daemon | Assignee: | Dario Freddi <drf> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | afiestas, aleixpol, alex.merry, cfeck, fischer, kollix, oliver.henshaw, rserral, simonandric5, vivo75+kde |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 4.9 | |
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi Produced by "KDE Daemon - The KDE Crash Handler" |
||
|
Description
captainknots
2011-11-25 16:59:56 UTC
Might be a duplicate of bug 287039. Please check if the correct Activity Manager is running, as indicated in bug 287039 comment #1. Created attachment 66985 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.7.4 (4.7.4) using Qt 4.7.4
as bug opener, starting a new session of kde
-- Backtrace (Reduced):
#6 0x00007f8d49898ac5 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7 0x00007f8d49899f3b in __GI_abort () at abort.c:93
[...]
#11 0x00007f8d4bd47b56 in KConfigGroup::groupImpl (this=0x7fff735716d0, aGroup=...) at /usr/src/debug/kde-base/kdelibs-9999/kdelibs-9999/kdecore/config/kconfiggroup.cpp:516
#12 0x00007f8d4bd44a27 in KConfigBase::group (this=0x7fff735716d0, str=<optimized out>) at /usr/src/debug/kde-base/kdelibs-9999/kdelibs-9999/kdecore/config/kconfigbase.cpp:51
#13 0x00007f8d334a9044 in PowerDevil::Core::loadProfile(bool) () from /usr/lib64/libpowerdevilcore.so.0
*** Bug 290735 has been marked as a duplicate of this bug. *** I get this crash, and kactivitymanagerd is running just fine for me. *** Bug 291857 has been marked as a duplicate of this bug. *** Created attachment 68638 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.8.00 (4.8.0) using Qt 4.8.0
- What I was doing when the application crashed:
Just logging in, boom. I don't really know much else.
-- Backtrace (Reduced):
#11 0x00007f55d929b1f9 in KConfigGroup::groupImpl (this=0x7fffa3ef5fb0, aGroup=...) at /home/kde-devel/src/kdelibs/kdecore/config/kconfiggroup.cpp:516
#12 0x00007f55d929826c in KConfigBase::group (this=0x7fffa3ef5fb0, str=...) at /home/kde-devel/src/kdelibs/kdecore/config/kconfigbase.cpp:51
#13 0x00007f55c144651f in PowerDevil::Core::loadProfile (this=0x126f110, force=true) at /home/kde-devel/src/kde-workspace/powerdevil/daemon/powerdevilcore.cpp:267
#14 0x00007f55c1446143 in PowerDevil::Core::refreshStatus (this=0x126f110) at /home/kde-devel/src/kde-workspace/powerdevil/daemon/powerdevilcore.cpp:236
#15 0x00007f55c14456bd in PowerDevil::Core::onBackendReady (this=0x126f110) at /home/kde-devel/src/kde-workspace/powerdevil/daemon/powerdevilcore.cpp:153
Created attachment 69119 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.8.00 (4.8.0) using Qt 4.8.0
- What I was doing when the application crashed:
Booting KDE from today's master/trunk => This crash.
-- Backtrace (Reduced):
#6 0xb5a5e8c5 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7 0xb5a601d5 in __GI_abort () at abort.c:93
[...]
#11 0xb6a6a878 in qt_assert_x (where=0xb7018a57 "KConfigGroup::groupImpl", what=0xb7018a70 "can not have an unnamed child group", file=0xb7018710 "/local/git/KDE/libs/kdelibs/kdecore/config/kconfiggroup.cpp", line=516) at /local/git/Qt/frameworks/qt/src/corelib/global/qglobal.cpp:2007
#12 0xb6e6e2d8 in KConfigGroup::groupImpl (this=0xbfbbb8e0, aGroup=...) at /local/git/KDE/libs/kdelibs/kdecore/config/kconfiggroup.cpp:516
#13 0xb6e6b446 in KConfigBase::group (this=0xbfbbb8e0, str=...) at /local/git/KDE/libs/kdelibs/kdecore/config/kconfigbase.cpp:51
I can reproduce this bug on a Gentoo Linux system, using KDE 4.8.3 and Qt 4.8.1: - Created a new empty user, removed all (hidden) files from home except for some Bash files - Using a combination of su, export DISPLAY, and Xephyr to setup an X-in-X environment - Run "startkde" from prompt - Just wait for crash The kactivitymanagerd process is running. However, checking the output on stdout/stderror, I found the following two lines: kded(20117) PowerDevil::Core::loadProfile: We are now into activity "" kded(20205) PowerDevil::Core::loadProfile: We are now into activity "" which seem to match the debug output in powerdevil/daemon/powerdevilcore.cpp (line 262): kDebug() << "We are now into activity " << activity; The previous call on m_activityConsumer->currentActivity() seem to return an empty string. Restarting the KDE environment in the same way a second time does not crash (at least not here). I am wildly guessing here, but given that this crash happened in a completely fresh environment without any KDE_HOME, there may be no activity (yet) configured. So, either the documentation of currentActivity should state that an empty string may be returned for "no activity configured" (and all callers have to cope with this situation with crashing), or in case that there is no activity, a default/empty activity has to be configured first. My guess is that such activities will be created, but only too late. As a side note, the PowerDevil's code here contains a lot of multiple magical strings like "actLike". Those should be refactored into class constants. *** Bug 305230 has been marked as a duplicate of this bug. *** Created attachment 77561 [details]
Produced by "KDE Daemon - The KDE Crash Handler"
This crash occurs after login and when my ASUS R501V Laptop has its VGA output connected to a Cramer VGA Auto Switcher. This system is used at a Church that I attend. It occurs every time I connect and boot.
At home this problem does not occur where I use a normal VGA connection to an additional monitor.
(In reply to comment #10) > Created attachment 77561 [details] > Produced by "KDE Daemon - The KDE Crash Handler" > > This crash occurs after login and when my ASUS R501V Laptop has its VGA > output connected to a Cramer VGA Auto Switcher. This system is used at a > Church that I attend. It occurs every time I connect and boot. > > At home this problem does not occur where I use a normal VGA connection to > an additional monitor. This one looks like a (lib)kscreen problem. Can you file a separate bug for this? Dario/Oliver can we add some code to prevent null activity crashing us? (In reply to comment #12) > Dario/Oliver can we add some code to prevent null activity crashing us? I think you already have! See commit e1c13947e2bd83b3352b951fe2b45073170a4f97 which went into 4.9. but not 4.8.x. I only see reports of this problem on 4.8.x so I suspect that this is indeed fixed. Please re-open or comment if I've assumed wrongly and anyone does see the on recent KDE releases. |