Summary: | plasma-desktop crashes when adding the presence-applet to the desktop | ||
---|---|---|---|
Product: | [Frameworks and Libraries] telepathy | Reporter: | Leonardo <leonardo.guilherme> |
Component: | presence-applet | Assignee: | Telepathy Bugs <kde-telepathy-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | detlev.casanova, kde, mklapetek |
Priority: | NOR | ||
Version: | 0.4.1 | ||
Target Milestone: | 0.5.0 | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Leonardo
2012-08-20 13:10:39 UTC
I can reproduce by uninstalling mission-control. The bug is as follows. PresenceApplet::onAccountManagerReady() account manager isn't ready because MC doesnt' exist. This prints out a tiny debug message. it then calls GlobalPresence::setAccountManager() which then decides to kFatal() Not sure where it's best to fix this. GlobalPresence will always show offline if AM isn't availbale, so maybe I should tone down the kFatal to kWarning. It should stop the crash. Then in the applet code if there was an error, use the Applet::setConfigurationRequired() and/or hide the options. *** Bug 305293 has been marked as a duplicate of this bug. *** Weird thing is that I do have mission control installed. Also I just downgraded to telepathy 4.0 and it still occurs... leonardo, can you run plasma-desktop from a terminal and paste any useful output here? plasma-desktop from a terminal had a lot of non-useful information. I did runned the ktp_presence plasmoid under plasma-windowed, and turns out that mission-control is segfaulting: plasma-windowed(7983) TelepathyPresenceApplet::onAccountManagerReady: "org.freedesktop.DBus.Error.Spawn.ChildSignaled" plasma-windowed(7983) TelepathyPresenceApplet::onAccountManagerReady: "Process /usr/libexec/mission-control-5 received signal 5" plasma-windowed(7983): KCrash: Attempting to start /usr/bin/plasma-windowed from kdeinit sock_file=/home/leo/.kde4/socket-cathy/kdeinit4__0 KCrash: Application 'plasma-windowed' crashing... KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit sock_file=/home/leo/.kde4/socket-cathy/kdeinit4__0 Tryin to execute it i get this message: --- process:17269): GLib-GIO-ERROR **: Settings schema 'im.telepathy.MissionControl.FromEmpathy' is not installed Trace/breakpoint trap -- which I guess is not useful, it probably means that a empathy-like must be running. How can I test mission-control and get a backtrace of it? You can run it in gdb - gdb "mission-control-5", then type "run" and hit enter, then make it crash and once it crashes, type "bt" and you'll get a backtrace. But you need debug packages to get a useful output. If you're on (K)ubuntu, install telepathy-mission-control-5-dbg package, it should be similar on other distros. I am not sure if I can reproduce the crash of mission control like this. Anyway, I installed mission-control version 5.12.1 and the bug is not reproducible anymore... weird. I guess this bug can be closed. I've seen that error before (in Arch on TelepathyLogger) it was a packaging bug that meant some gobject based post-install hook wasn't run. In either case, our code should not crash (or in this case deliberately close) if the backend goes down for whatever reason, and as such this remains valid. > Git commit 4256cbe5c0de0c142352b4ef33457d8bea868e9c by David Edmundson. > Committed on 21/08/2012 at 01:18. > Pushed by davidedmundson into branch 'master'. > > Don't treat MC errors as fatal > Reviewed-by: Martin Klapetek > > M +1 -1 KTp/global-presence.cpp |