Ubuntu
gdm package

Bug #136529
Comment #35

Comment 35 for bug 136529

Revision history for this message

Bernhard Sessler (burnhead) wrote on 2008-01-08:

#35

dmesg.log Edit (32.9 KiB, text/plain)

Okay, as I was so stupid to post in a report that was marked as a duplicate of this one, I'll post my problem here (thanks for the hint Pär ;-)).
I've got the same problem as all people do here - when I try to login to a GNOME session the screen just freezes at the brown Ubuntu background. I can still move my mouse pointer though and switch to the console via Ctrl-Alt-F1 (or any other function key).
The only really weird thing is that this only happens with the new 2.6.24 kernel. As with kernel 2.6.24-2 I couldn't even boot my system without providing the "acpi=off" or "acpi="ht" boot-option. However, this problem is now gone (or it has been solved) when I dist-upgraded to kernel 2.6.24-3 this morning - but I still can't login to any gnome session. This also goes for the GNOME failsafe session and the problem isn't solved by disabling the dual core functionality in the BIOS or by providing the "acpi=off" boot-option.
As I said before, everything works fine with the old gutsy kernel 2.6.22 and other versions before, so it might have something to do with the kernel itself (but don't take my word for it, I don't know what exactly causes the problem).
I'm using the latest Hardy version, with all the upgrades and dist-upgrades so far - and apart from a self-compiled ndiswrapper (latest SVN) every package on my system is in its original state. I should also mention that I didn't compile ndiswrapper for the 2.6.24 kernel so far, so it shouldn't be the cause of this problem. I don't know if it's related to this specific bug, but the avahi daemon won't start with the 2.6.24 kernel (it just tells me that the start failed at boot time) and when I'm trying to use the command "sudo" on the console the system also hangs (I can still type things via keyboard and switch to another console, but I can't kill nor abort the process).
Well, that seems to be it for now. I'll attach a few logfiles (tell me if you need more).
Here are my system specs:
- Samsung R60Plus Notebook with a
- Core2Duo T5450 (@1.66GHz) CPU
- 2048 MB RAM
- ATI Mobility Radeon X2300
- and nothing attached but a small mouse

Cheers, Bernhard

Okay, as I was so stupid to post in a report that was marked as a duplicate of this one, I'll post my problem here (thanks for the hint Pär ;-)).
I've got the same problem as all people do here - when I try to login to a GNOME session the screen just freezes at the brown Ubuntu background. I can still move my mouse pointer though and switch to the console via Ctrl-Alt-F1 (or any other function key).
The only really weird thing is that this only happens with the new 2.6.24 kernel. As with kernel 2.6.24-2 I couldn't even boot my system without providing the "acpi=off" or "acpi="ht" boot-option. However, this problem is now gone (or it has been solved) when I dist-upgraded to kernel 2.6.24-3 this morning - but I still can't login to any gnome session. This also goes for the GNOME failsafe session and the problem isn't solved by disabling the dual core functionality in the BIOS or by providing the "acpi=off" boot-option.
As I said before, everything works fine with the old gutsy kernel 2.6.22 and other versions before, so it might have something to do with the kernel itself (but don't take my word for it, I don't know what exactly causes the problem).
I'm using the latest Hardy version, with all the upgrades and dist-upgrades so far - and apart from a self-compiled ndiswrapper (latest SVN) every package on my system is in its original state. I should also mention that I didn't compile ndiswrapper for the 2.6.24 kernel so far, so it shouldn't be the cause of this problem. I don't know if it's related to this specific bug, but the avahi daemon won't start with the 2.6.24 kernel (it just tells me that the start failed at boot time) and when I'm trying to use the command "sudo" on the console the system also hangs (I can still type things via keyboard and switch to another console, but I can't kill nor abort the process).
Well, that seems to be it for now. I'll attach a few logfiles (tell me if you need more). 
Here are my system specs:
- Samsung R60Plus Notebook with a
-  Core2Duo T5450 (@1.66GHz) CPU
- 2048 MB RAM
- ATI Mobility Radeon X2300
- and nothing attached but a small mouse

Cheers, Bernhard

Ubuntugdm package

Comment 35 for bug 136529

Ubuntu
gdm package