Bugzilla – Bug 156555
Switch to NetworkManager freezes KDE
Last modified: 2008-06-25 09:53:49 UTC
Updated from SL 10.0 to 10.1 When switching the network setup method in Yast2 network from traditional to NetworkManager KDE (or X?) freezes. The systems starts to hang when SuSE.config is executed. Change to a text console is possible, but X has to be started new to get back into graphical mode. Furthermore, the HAL daemon must be started manually. Only then NetworkManager is able to set up the network.
Created attachment 72028 [details] /var/log/NetworkManager
Any logs? /var/log/NetworkManager, 200 lines of /var/log/messages and ~/.xsession-erros would be useful.
Created attachment 72034 [details] Last 200 lines of /var/log/messages
Created attachment 72038 [details] ~.X.err
Please try if this also happens using Windowmaker for example. I'm not sure whether this problem is KDE-related, X-related or a problem with NetworkManager, the log looks good.
I've tried the switch from traditional to NetworkManager under WindowMaker. No problems, everything worked smoothly. I will try it again with KDE.
I've tried now to switch from NetworkManager to traditional and the other way around (in KDE). Both actions lead to the same scenario: YaST2 gets stuck in the dialog "Saving Network Configuration" at the point "Run SuSEconfig" (72%). Yet KDE does not hang at this moment. Now I click on any other application and KDE hangs suddenly. Although the mouse is still functional. Also the reconfiguration of the network is successful as can be seen by looking at the ifconfig output. See the attached logs from these tries below.
Created attachment 73062 [details] ~X.err (Comment #7)
Created attachment 73063 [details] /var/log/NetworkManager (Comment #7)
Created attachment 73064 [details] Last 200 lines of /var/log/messages (Comment #7)
Can you finally try this with Gnome? Looks like it is KDE-related.
I've updated to beta 8. The problem is still there and shows in KDE and Gnome. Therefore, I think it is a problem with YaST2 (GUI). The logfile /var/log/Yast2/y2log is attached.
Created attachment 73948 [details] Log file y2log (Comment #12)
Martin, Stano, I haven't seen an update for a month. What's the status of this?
The hostname has changed, so X applications have problems. What is the value of /etc/sysconfig/network/dhcp/DHCLIENT_SET_HOSTNAME? (NM should respect it already, bug 144324)
DHCLIENT_SET_HOSTNAME="yes"
Too bad, don't do that. I could try to detect such cases and issue a warning.
Reassigning to the new maintainer of yast2-network.
move to later
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED. In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(