Summary: | Plasma Desktop Crashes After Login | ||
---|---|---|---|
Product: | [Unmaintained] plasma4 | Reporter: | Patrick Thomas <admin> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | Keywords: | drkonqi |
Priority: | NOR | ||
Version: | 4.12.2 | ||
Target Milestone: | --- | ||
Platform: | Mint (Ubuntu based) | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Patrick Thomas
2014-02-28 22:42:22 UTC
*** This bug has been marked as a duplicate of bug 323679 *** Try wicd 0.3.1 *** This bug has been marked as a duplicate of bug 304089 *** It has nothing to do with Wicd, I changed over to network-manager and it still happened. Nor does it have to do with KWallet/KMail as I don't have KMail installed and KWallet doesn't start on boot. I'm a bit skeptical on the panel resize one as I didn't resize any panel nor did I get a chance to, but maybe it tried to "resize" to the right size... IDK. I rebooted and it was working fine, except internet was broke again. I restarted "networking" and it crashed again so I tried running plasma-desktop and it crashed before I even saw anything difference. Restarted kdm again, but this time the missing file thing didn't happen so that's good... but plasma-desktop was still broke... For now I am going to have to use DHCP, as using dhclient seems to work without problems. I hate DHCP. So whatever the problem is, it is related to the "networing" service. *After I restarted "networking" *saw anything different > It has nothing to do with Wicd, > 8 0x00007fae2d6255da in ?? () from /usr/lib/kde4/plasma_engine_wicd.so It does. Look at the backtrace. It wouldn't lie. Either upgrade wicd-kde to 0.3.1, or ensure the wicd daemon is already started before logining into the desktop. *** This bug has been marked as a duplicate of bug 304089 *** Then why is it that it did the *exact* same thing when I had *uninstalled* Wicd and installed network manager (although that one didn't produce a backtrace)? (In reply to comment #6) > Then why is it that it did the *exact* same thing when I had *uninstalled* > Wicd and installed network manager (although that one didn't produce a > backtrace)? Because the widget is called *wicd-kde* not *networkmanager-kde*, so it needs (a running) wicd daemon but not networkmanager daemon. Is that clear enough ? And please stop reopening the bug just because you have questions. Just ask, I will answer it, but don't reopen it again and again (It is not a funny game) . *** This bug has been marked as a duplicate of bug 323679 *** Oops, wrong bug number, again. *** This bug has been marked as a duplicate of bug 304089 *** |