pc locks up when trying to shut down

Bug #38096 reported by Mikkel Erup
16
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

If I try to shut down or reboot when I'm using kdm my laptop (IBM X40) freezez at a black screen. Using gdm it doesn't happen. Odly increasing debug output makes it not freeze but spams the log instead.
This is what the log says without debug output:
kdm_greet[2786]: Internal error: memory corruption detected

Revision history for this message
Rocco Stanzione (trappist) wrote :

Same happens to me on a Dell Inspiron 600m. It also happens if I ctrl-alt-backspace or /etc/init.d/kdm stop|restart. I'm not certain, but I think it began when I upgraded to kde 3.5.2.

Changed in kdebase:
status: Unconfirmed → Confirmed
Revision history for this message
mon (javiermon-deactivatedaccount) wrote :

What version of kubuntu are you using?

Changed in kdebase:
assignee: nobody → kubuntu-team
Revision history for this message
Mikkel Erup (mikkel-erup) wrote :

This is Dapper, kdm-3.5.2-0ubuntu5. It happened in 3.5.2-0ubuntu2, 3 and 4.

Mikkel

Revision history for this message
Mikkel Erup (mikkel-erup) wrote :

I meant to say it also happened in those versions ...

Revision history for this message
Rocco Stanzione (trappist) wrote :

Same here on the versions. It didn't happen on breezy + 3.5.2.

Revision history for this message
Rocco Stanzione (trappist) wrote :

It might be relevant that I'm running dual-head with the fglrx drivers from linux-restricted-modules. Nothing interesting in the syslog.

Revision history for this message
Mikkel Erup (mikkel-erup) wrote :

Rocco Stanzione wrote:
> It might be relevant that I'm running dual-head with the fglrx drivers from linux-restricted-modules. Nothing interesting in the syslog.
>
Interesting, but I doubt it's caused by that. My graphics is Intel
Extreme 855GM onboard.

Revision history for this message
Mikkel Erup (mikkel-erup) wrote :

It still happens in 3.5.2-0ubuntu6.
syslog says "Apr 13 22:18:06 freja kdm_greet[9669]: Internal error: memory corruption detected"

Revision history for this message
Mikkel Erup (mikkel-erup) wrote :

And in kdm-3.5.2-0ubuntu7

Revision history for this message
Mikkel Erup (mikkel-erup) wrote :

The problem continues to persist in kdm-3.5.2-0ubuntu8.

Revision history for this message
Rocco Stanzione (trappist) wrote :

This may be a duplicate of #30447, or vice versa.

Revision history for this message
Mikkel Erup (mikkel-erup) wrote :

Well on my computer sudo /etc/init.d/kdm restart works fine. Rebooting or shutting down also works fine from the login menu. It only freezes if I try rebooting or shutting down from within the kde session.

Revision history for this message
Paulo Tanimoto (tanimoto) wrote :

[quote]
Well on my computer sudo /etc/init.d/kdm restart works fine. Rebooting or shutting down also works fine from the login menu. It only freezes if I try rebooting or shutting down from within the kde session.
[/quote]

That's exactly the behavior for me as well. I've been having this issue since a few Flights ago. I've been installing Kubuntu from scratch to see if it gets fixed. What I have noticed is that in the first couple of times I use the system (even with fglrx), it behaves properly. After that, this starts to happen. Either the system becomes unusable or everything happens in a blank screen.

I'd be happy to post more information if you tell me what is necessary.

Revision history for this message
Paulo Tanimoto (tanimoto) wrote :

By the way, there's another thing that is probably related is this. When I click Restart or Shutdown nothing happens. Then I have to go to the Menu again and repeat the process. Only then I get the blank screen.

Revision history for this message
Laurent Bonnaud (laurent-bonnaud) wrote :

I am still seeing this bug every day in edgy on an Acer 8204 WLMI:

/var/log/syslog.4.gz:Nov 4 20:35:14 localhost kdm_greet[4852]: Internal error: memory corruption detected
/var/log/syslog.5.gz:Nov 3 11:03:33 localhost kdm_greet[4847]: Internal error: memory corruption detected
/var/log/syslog.6.gz:Nov 1 22:04:44 localhost kdm_greet[5227]: Internal error: memory corruption detected
/var/log/syslog.6.gz:Nov 2 12:53:06 localhost kdm_greet[4862]: Internal error: memory corruption detected

Revision history for this message
Brian Ealdwine (eode) wrote :

..I have the same entries in my logs.. Memory corruption detected.

Is it possible to up the importance of this bug? This causes my filesystem (reiserfs) to become out of whack, which prevents me from booting. I then have to boot into recovery mode, which somehow works, and mounts the filesystem, replaying the journal, etc. Then I can boot up normally.

Revision history for this message
Reuben Firmin (reubenf) wrote :

I am seeing this (or something very close to it) on Feisty, except the problem seems to be intermittent. I click shutdown from within KDE, all x applications exit, but the PC locks up somewhere between that and the kubuntu splash coming up.

Revision history for this message
Daugirdas (daugirdas) wrote :

The bug also affects the up-to date 7.04 installation on ~AMD 1Ghz machine with latest kde/kdm. The shut down, however is smooth from the KDM screen. Please fix.

Revision history for this message
Reuben Firmin (reubenf) wrote :

I've started seeing a "red screen of death" on my laptop when shutting down, sometimes. The screen is completely red, and the machine is locked.

Other times, I get a screen dump with the last output being NetworkManager shutdown errors, and nothing following.

I have the corruption messages (as above), but I'm not convinced that they're associated with the lockup.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Does this still happen with Intrepid (or KDE4?)

Changed in kdebase:
status: Confirmed → Incomplete
Revision history for this message
Harald Sitter (apachelogger) wrote :

Bug will be closed on 2008-10-09 if it didn't receive a reply by then.

Changed in kdebase:
assignee: kubuntu-bugs → nobody
Revision history for this message
Harald Sitter (apachelogger) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kdebase:
status: Incomplete → Invalid
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.