Bug 355327 - plasma-nm Causes Panel Freeze on Login; Complete Desktop Freeze
Summary: plasma-nm Causes Panel Freeze on Login; Complete Desktop Freeze
Status: RESOLVED DUPLICATE of bug 354230
Alias: None
Product: plasma-nm
Classification: Plasma
Component: applet (show other bugs)
Version: 5.4.2
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-14 06:19 UTC by boblovgren55
Modified: 2015-11-14 07:38 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description boblovgren55 2015-11-14 06:19:53 UTC
Qt Version: 5.5.1
Operating System: Linux 4.3.0-1-default x86_64
Distribution: "openSUSE Tumbleweed (20151111) (x86_64)"

After updating to the latest openSUSE Tumbleweed snapshot, plasma-nm is making the desktop hang upon logging into KDE. A couple things load on the panel like the clock plasmoid, but you can tell based on the spacing of where stuff should be on the panel and some artifacts present that it's hanging. It hangs the entire desktop for about 60 seconds before I can click anything on the desktop (even in folder view), although ctrl+esc will bring up KSysGuard during the hang and If a Dolphin window loads due to a previous session restore, I can perform actions in Dolphin during the hang. I can easily reproduce the problem by removing the panel, then right mouse clicking on the desktop bringing up the context menu, clicking on "Add Panel", then "Default Panel".

When switching to openSUSE's Wicked framework for network management which shuts off plasma-nm, the panel doesn't hang any longer upon boot or upon adding a panel to the desktop as I wrote above. This didn't happen until the last Tumbleweed snapshot.

Reproducible: Always

Steps to Reproduce:
1. Boot into Plasma 5
2. Desktop hangs for 1 minute
3. plasma-nm causes panel to not fully load
Comment 1 Jan Grulich 2015-11-14 07:38:16 UTC

*** This bug has been marked as a duplicate of bug 354230 ***