Bug 145586 - Panel locks up when switching to wireless network
Summary: Panel locks up when switching to wireless network
Status: RESOLVED REMIND
Alias: None
Product: kicker
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Aaron J. Seigo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-18 02:37 UTC by Tristan Miller
Modified: 2008-09-24 11:58 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tristan Miller 2007-05-18 02:37:18 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    SuSE RPMs

I have a laptop which is normally connected to a wired ethernet network.  If I unplug the network cable, knetworkmanager will automatically switch over to the wireless network.  However, whenever it does so, everything in the panel (start menu, pager, taskbar) except for the system tray locks up for several minutes.  These applets become unresponsive to mouse clicks; they won't even repaint.

I suspect this may have something to do with NFS, since the amount of time the panel is unresponsive is about the same amount of time it takes to re-establish my mounted NFS filesystems.  However, none of the applets need to access anything on network filesystems, so they shouldn't be blocking.
Comment 1 Philip Rodrigues 2007-05-19 22:36:59 UTC
Can you find out for certain? Try getting a backtrace with 'kill -SEGV <pid-of-kicker>' when it crashes, or use strace on kicker.
Comment 2 Bram Schoenmakers 2007-07-24 20:13:25 UTC
Does this problem still exist, and if yes, can you please investigate it more following Philip's suggestions?
Comment 3 Bram Schoenmakers 2007-08-25 14:56:41 UTC
Please reopen whenever you can provide more info as requested by Philip.
Comment 4 Tristan Miller 2008-09-24 11:58:10 UTC
Have since upgraded to KDE 4, where kicker is no longer used, so it's unlikely I'll be providing any further information on this bug.