ubuntu freezes after login when login in not initiated within 5 minutes.

Bug #257062 reported by 129260
0
Affects Status Importance Assigned to Milestone
fglrx-installer (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

I am a new ubuntu user, long time windows user. So please bear with me. I can get information when needed, as long as i am told how to get it. OK, so here is what happens: On both my laptop and desktop, if i load ubuntu on my dual boot setup with windows xp, it loads correctly, but if i do not log in within 5 minutes, and then i go to log in, it looks like it is logging in fine, but then it freezes completely. I have to turn off the computer and then back on. Like i said, as long as i log in before roughly 5 minutes, there is no problem. But if i wait more then that and try to log in, it freezes completely. I am using the latest ubuntu, and my log in screen (under the local tab in setup login screen) is human list. ubuntu default welcome theme with face. You click your name and then type your password and that's how you log in. I do not know if i named the welcome screen i am using on both machines correctly but yeah.....i tried...I feel dumb but i know this has to be a bug, because it freezes the system completely. As long as someone can tell me how to get the information that you need, i can get it for you. It loads completely fine as long as i do not wait. No problems at all if its before 5 minutes. Firestarter the firewall is the only program set to auto start up. Nothing else. Thanks, and I appreciate your patience with me.

Revision history for this message
Andreas Moog (ampelbein) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in gdm.
For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https://wiki.ubuntu.com/ReportingBugs.

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

thank you for your bug report, do you get the issue if you uninstall this firewall software?

Changed in gdm:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
129260 (yprtb-deactivatedaccount) wrote :

yes, i still get the issue. I remember when i didn't not even have firestarter installed and it still did it.....at fist i thought this was a security feature or something to keep hackers from having the time to hack into ubuntu at the log in screen. Then i realized to myself that does not make sense. But it freezes the computer and makes it 100% unusable after logging in. And holding down the power button and having to log in again is annoying, but i would not say this is a critical issue, as everything works fine after logging on before 5 minutes. Is there a way you guys can test this on your ubuntu machine, and wait the time i said and see if you get the frozen desktop? Thanks for the reply, also could i get a log or something that will help you guys figure out what is causing the problem? As long as i know how to help, i will. Thanks for your patience with me!! Also i read the first comment link and tried to figure things out, but i am lost ha. Sorry...anyway i do know that most applications have a report a problem link, and i am very grateful for it. thanks!

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

could you attach your /var/log/messages, /var/log/syslog, /var/log/Xorg.0.log to the bug after getting the issue?
can you use ctrl-alt-f1 to switch to a vt when getting the bug?

Revision history for this message
129260 (yprtb-deactivatedaccount) wrote :

ya i can do that. i tried to switch when the bug occurred. it did not work. completely frozen.....

Revision history for this message
129260 (yprtb-deactivatedaccount) wrote :

var log system log

Revision history for this message
129260 (yprtb-deactivatedaccount) wrote :

/var/log/Xorg.0.log

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

when did you get the bug? the logs have quite some activity so knowing when was the issue would be a good indication
could you also try if you get that when not using the fglrx video driver? and do you have an another computer you could use to ssh to this one when it freeze to see if it's really crashed or just xorg hangs

Revision history for this message
129260 (yprtb-deactivatedaccount) wrote :

like i said i only get when waiting more then 5 minutes at the log in screen......i know it happened yesterday around 4pm, and the day before that at 6pm i think. Does that help? How do i not use the fglrx video driver? haha i am new to this so instructions will be helpful. :) I have a desktop as well that this happens on, so i guess i could ssh......if i knew how. :)

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

the closed source binary drivers are not used by default in ubuntu, just undo what you did to enable those?

Revision history for this message
129260 (yprtb-deactivatedaccount) wrote :

Oh ok, now i understand what you mean. Sorry for me misunderstanding. Ill try that and let you know of my results.

Revision history for this message
129260 (yprtb-deactivatedaccount) wrote :

After disabling my video driver, everything is fine now! Thank you so much! I no longer experience the issue. Ubuntu went back to its default driver and I am no longer experiencing the hang at login. Thanks for helping me with this issue.

Revision history for this message
129260 (yprtb-deactivatedaccount) wrote :

it was an ATI video driver that was used in my laptop by the way....

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

how did you enable the ati driver? if that's the version distributed in ubuntu the bug should be reassigned there

Revision history for this message
129260 (yprtb-deactivatedaccount) wrote :

no i disabled it from using it. system-administration-hardware drivers. I unchecked ati video driver. Restarted. Then it did not do it. Now this is what is weird.....I rechecked it again, and rebooted, and now it does not do it anymore? I don't know what happened, but it appears fixed...

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

reassigning to fglrx since that's the driver creating the issue

Changed in gdm:
assignee: desktop-bugs → nobody
status: Incomplete → New
Revision history for this message
Bryce Harrington (bryce) wrote :

Good day 129260,

I've just uploaded a new 8.543 version of -fglrx to Intrepid which now should work with xserver 1.5. Would you mind testing this new version and reporting back whether this issue is still present? If it is, it would be helpful if you could (re-)post your Xorg.0.log from running with this version. Thanks ahead of time.

If you don't have Intrepid installed on your system, you can test this by booting an Intrepid LiveCD (available from cdimage.ubuntu.com), using either the -vesa or -ati driver, then update to the latest version of Ubuntu, install fglrx, and then logout and back in. Your /var/log/Xorg.0.log will confirm whether you've loaded FGLRX successfully.

If you find any new issues, please report them as separate bugs. You can use the tool `ubuntu-bug fglrx-installer` which will gather the necessary files and create the launchpad report for you to fill in more easily.

Changed in fglrx-installer:
status: New → Incomplete
Revision history for this message
129260 (yprtb-deactivatedaccount) wrote :

i would test it, but the issue has stopped now. =] As i stated above...."no i disabled it from using it. system-administration-hardware drivers. I unchecked ati video driver. Restarted. Then it did not do it. Now this is what is weird.....I rechecked it again, and rebooted, and now it does not do it anymore? I don't know what happened, but it appears fixed..."

It has been fixed since i have done that, i have no idea how, or why it worked, but it did....I didn't mean to waste your time, and i am sorry if that does not make sense, it makes no sense to me ether. But it has not happened since 2008-08-15 until now. I don't know if that helps or not, but its fixed on my end...

Revision history for this message
Bryce Harrington (bryce) wrote :

Okay great, thanks for letting us know. We're always glad to hear of issues fixing themselves.
Feel free to reopen this bug if it occurs again, or file a new bug on any other issues you run into.

Changed in fglrx-installer:
status: Incomplete → Fix Released
Revision history for this message
129260 (yprtb-deactivatedaccount) wrote :

thanks :) I will let you guys know if it occurs again.

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.