No networking after the gdm theme is changed several times

Bug #48353 reported by Guido Mureddu
10
Affects Status Importance Assigned to Milestone
gdm (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gdm

I dist-upgraded from Breezy to Dapper. A few days later, I used gdmsetup to change the GDM login theme. I tried several of them, then settled for one called CleanLinux, which I downloaded using gnome-art.

After a reboot, there was no networking anymore ("network is unreachable" was the error message). I couldn't access/ping the router, the router couldn't see this computer online, and I got the same results from another computer connected to the LAN at the same time. Using some tools (network-admin, ifconfig) I checked if something was wrong with my settings. Nothing was, so I didn't change anything. The last move I tried was to change the GDM theme back to the default Human theme. After a reboot, everything worked.

I was able to reproduce this bug. Changing the theme only once didn't cause any problems, networking was okay after the reboot.

But after changing the theme several times (4 or 5 times: change theme, close gdmsetup, open it again, change theme and so on), logging in and out to try it, and then rebooting, I was left with no networking once more. Again, changing back to the Human theme, and rebooting again, fixed it.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. That's weird than changing the gdm theme does change your network. Do you have anything to /var/log/messages or /var/log/syslog about it? Did you already get such issues with your network without changing gdm configuration?

Changed in gdm:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
Guido Mureddu (malcolm81) wrote :

Sorry for the delay in answering this. I had no issue with my network before changing the gdm configuration. Even after I "fixed" it, however, sometimes there won't be any connection and then I just have to reboot, which solves it. I don't think this is related to gdm, anyway, but it wasn't like this before the problem I had.
I haven't had this problem for a while, but I will try it again and check my system logs as soon as possible.

Thank you for the assistance.

Revision history for this message
Sebastien Bacher (seb128) wrote :

no update and previous comment states that was not a gdm bug, closing

Changed in gdm:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.