Ubuntu
linux package

Linux kernel 2.6.32-61 hangs gnome desktop on ubuntu 10.04 lucid lynx

Bug #1327014 reported by tmstaedt
96
This bug affects 18 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Just did a regular update and the latest kernel would boot, but when logging into my gnome desktop the mouse
cursor shows a sandbox and is inaccessible. Had to go back to 2.6.32-60.

Ubuntu 2.6.32-60.122-generic 2.6.32.61+drm33.26

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1327014

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: lucid
Revision history for this message
tmstaedt (tmstaedt) wrote : Re: Latest kernel security update to 2.32-61 hangs gnome desktop on ubuntu 10.04 lucid lynx

apport-collect 1327014
Error connecting to Launchpad: <html>
<head><title>api.edge.launchpad.net no longer supported</title></head>
<body>
<h1>edge.launchpad.net is no longer supported</h1>
<p><a href="http://blog.launchpad.net/general/edge-is-deprecated">edge.launchpad.net was deprecated back in 2010</a>, and is no longer available. Please update your API clients to use api.launchpad.net instead, as described in the blog post.</p>
</body>
</html>

You can reset the credentials by removing the file "/home/tom/.cache/apport/launchpad.credentials"

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Benno Schulenberg (bennoschulenberg)
summary: - Latest kernel security update to 2.32-61 hangs gnome desktop on ubuntu
- 10.04 lucid lynx
+ Linux kernel 2.6.32-61 hangs gnome desktop on ubuntu 10.04 lucid lynx
Revision history for this message
Benno Schulenberg (bennoschulenberg) wrote :

This is related to bug #1327220 and bug #1327349 -- it is all about kernel 2.6.32-61 making things hang or inoperational. For me it is Thunderbird hanging, and after clicking on it, the whole desktop (netbook-launcher) hangs, blocks, freezes. When choosing the previous kernel, 2.6.32-60, in the boot menu, everything works fine.

Revision history for this message
Benno Schulenberg (bennoschulenberg) wrote :

(BTW, I get the same error from apport-collect as in comment #2. The package launchpad-lib should be updated to say "https://api.launchpad.net/" instead of "https://api.edge.launchpad.net/" in the file /usr/share/pyshared/launchpadlib/uris.py.)

Revision history for this message
Alex Robinson (alex-launchpad-tranzoa) wrote :

Same thing on two quite different systems (different in hardware, that is). Both are Lucid Desktop 64-bit.

Sometimes it takes a while for the freeze to happen.

One system auto-logins and it may not freeze until a GUI program is run from the Desktop. Sometimes not even then, but later, at random. Terminal programs are fine. I had thought this system had a simple problem with my renaming a .desktop file in ~/.config/autostart because the first freeze happened exactly when I did that.

The other system freezes showing the grayed login box just after hitting Enter on the password entry dialog box in the login screen.

Both systems consistently have the problem.

sudo restart gdm makes them work for a moment or more.

apport-collect seems to be broken, as mentioned by someone else above.

Revision history for this message
Nick T (n1ck) wrote :

I also have problems on two different machines with the 2.6.32-61 kernel upgrade.
On one (Lenovo M57 Core 2 Duo E8500 with Intel graphics) I can use the desktop but many apps (eg Firefox) just hang almost immediately - window greys out and force quit is only thing that works.
On other (Lenovo X61 laptop Core 2 Duo T7300 with Intel mobile graphics) the desktop appears after login but with no sound and does not respond to mouse-clicks. Ctrl-Alt-T brings up terminal window but does not display prompt or accept keystrokes. Ctrl-Alt-F1 gives access to console that seems to work ok.
On both machines, holding Shift on booting to get the GRUB menu and selecting the -60 kernel gets everything working again.

Revision history for this message
ted thomas (tthomas-x) wrote :

When I login to my normal primary user account, the Gnome desktop hangs. However, I can login to a different account, and the Gnome desktop comes up, and everything appears to run fine. However, the sound system is broken on the secondary account.

Revision history for this message
penalvch (penalvch) wrote :

tmstaedt, thank you for reporting this bug to Ubuntu. Lucid Desktop reached EOL on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

Please upgrade to the latest version and re-test. If the bug is still reproducible, please file a new report via a terminal:
ubuntu-bug linux

Please feel free to report any other bugs you may find.

Changed in linux (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
tmstaedt (tmstaedt) wrote :

> Lucid Desktop reached EOL on May 9, 2013.

I know that. Canonical still delivers critical security patches for 10.04, though.

> Please upgrade to the latest version and re-test.

I just started update-manager and there was no new kernel available (Di 10. Jun 00:32:23 CEST 2014), only some updates
for libxml2, which I installed.

Revision history for this message
hamish (hamish-b) wrote :

This is also broken in 10.04 Server. Reopening.

as mentioned in comment 3, see duplicate launchpad bug #1327220 and #1327349.

see also many complaining of the same trouble in the forums:
 http://ubuntuforums.org/showthread.php?t=2228206

thanks,
Hamish

hamish (hamish-b)
Changed in linux (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Steve Langasek (vorlon) wrote :

All of the cited bugs concern desktop applications. No evidence is provided to support the claim that Ubuntu 10.04 Server is affected. While the kernel is common to both desktop and server flavors, you can expect that regressions that only impact end-of-life configurations will not be a high priority for resolution.

Revision history for this message
hamish (hamish-b) wrote :

er, seriously? the kernel and firefox don't fall under things people might possibly need LTS for?

The linux-image-2.6.32-61-server package appears to contain a serious regression affecting many people. this should be fixed or the buggy package withdrawn.

"'supported' but stay away from certain kernel modules or kernel features because they aren't", does not make a hell of a lot of sense or inspire much confidence. and not all servers are strictly going to be headless. Staying with the old+working kernel package long term is no solution either.

It is completely understandable that a random end-user X11 app with a popcon ranking of 20000 would not be at the top of the list for getting updates in a server edition, but if the core of the server edition is not actually going to be supported our migration strategy is suddenly out the window and there's simply no reason for our institution, or any other for that matter, to trust ubuntu for real LTS in future. which kinda sucks, since our users like ubuntu.

at least the (non-lucid) thin clients still seem to be working with the broken app servers. without knowing the cause I don't know if an end user could accidentally/trivially trigger a system-wide DoS for all the other users though.

</rant>

regards,
Hamish

Revision history for this message
Steve Langasek (vorlon) wrote : Re: [Bug 1327014] Re: Linux kernel 2.6.32-61 hangs gnome desktop on ubuntu 10.04 lucid lynx

On Tue, Jun 10, 2014 at 02:50:04AM -0000, hamish wrote:
> er, seriously? the kernel and firefox don't fall under things people
> might possibly need LTS for?

You seem to have misunderstood what "LTS" means. "LTS" does not mean "feel
free to run this OS indefinitely, without upgrading, and expect to continue
to receive support from the Ubuntu community". The 10.04 LTS desktop
packages - which *definitely* include firefox - were only supported until
April 2013. Anyone running a desktop environment on top of 10.04 is using
software that has not been receiving critical security updates for over a
year.

So no, you should not expect Ubuntu developers to go out of their way to
enable you to continue running in a configuration which we do not endorse.
Any desktop-affecting regressions in the kernel security update are
certainly unintentional, but if they only affect no-longer-supported desktop
packages, it is not a critical regression.

> and not all servers are strictly going to be headless.

I can see that this is true, but that in no way changes our support policy
for such things.

> Staying with the old+working kernel package long term is no solution
> either.

Sure; the solution is to upgrade to a supported version of the Ubuntu
desktop packages, 12.04 LTS (or 14.04 LTS).

> but if the core of the server edition is not actually going to be
> supported

"firefox" is not part of the core of the server edition. If you can present
a case wherein a supported server package is affected by this bug, then this
would be a higher priority issue.

For instance, there is a new linux kernel package in lucid-proposed,
2.6.32-62.125, which purports to fix a regression identified in the previous
security update. You might check if this update fixes your issue as well -
perhaps it's the same issue.

But your configuration is still unsupported and you should upgrade to a
currently-supported desktop release.

Revision history for this message
penalvch (penalvch) wrote :

As per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327014/comments/8 .

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
Revision history for this message
davec (david-covell-plus) wrote :

I would suggest that there is a critical difference between deciding not to fix a bug in a version that is out of support , and introducing a bug in an update and then declining to fix it! So, no I do not "expect Ubuntu developers to go out of their way to enable you to continue running in a configuration which we do not endorse", but I do expect them to fix what they just broke.

Revision history for this message
tmstaedt (tmstaedt) wrote :

Am Dienstag, den 10.06.2014, 03:24 +0000 schrieb Steve Langasek:
> On Tue, Jun 10, 2014 at 02:50:04AM -0000, hamish wrote:
> > er, seriously? the kernel and firefox don't fall under things people
> > might possibly need LTS for?
>
> You seem to have misunderstood what "LTS" means. "LTS" does not mean "feel
> free to run this OS indefinitely, without upgrading, and expect to continue
> to receive support from the Ubuntu community". The 10.04 LTS desktop
> packages - which *definitely* include firefox - were only supported until
> April 2013. Anyone running a desktop environment on top of 10.04 is using
> software that has not been receiving critical security updates for over a
> year.
>
> So no, you should not expect Ubuntu developers to go out of their way to
> enable you to continue running in a configuration which we do not endorse.
> Any desktop-affecting regressions in the kernel security update are
> certainly unintentional, but if they only affect no-longer-supported desktop
> packages, it is not a critical regression.

Hmm. But you withdrew that kernel update for 10.04, i.e. the 10.04
update-manager does not show that new kernel version as an update
anymore.
And you continue to deliver critical security fixes to this unsupported
10.04 release for a while, right?
Well, then you should also try to fix these issues in due time or at
least give clear advice what sysadmins or experienced users can do get
things working again.
Or stop updating the kernel for 10.04 all together!

> Sure; the solution is to upgrade to a supported version of the Ubuntu
> desktop packages, 12.04 LTS (or 14.04 LTS).
>

...which will potentially break existing software which had been running
stably for a long time and had many happy users.
... and has a little blackmailing momentum in it, doesn't it?

--
thomas

Revision history for this message
jaybo (ubuntu-one-ostaffe) wrote :

First break kernel 60 with 61. Then say will not fix because 10.04 is no longer supported even though updates have been routinely provided. Then tease with a kernel fix, 62. But once a few get a taste and validate the fix, 62 is removed from the update manager. This style of management makes no sense. If you do not want to support 10.04, stop support. But at least you can do is leave it in working condition before abandoning.

Revision history for this message
tmstaedt (tmstaedt) wrote : kernel in lucid proposed comes up normal

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327300/comments/4:

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag
'verification-needed-lucid' to 'verification-done-lucid'.
>
> If verification is not done by 5 working days from today, this fix
 will be dropped from the source code, and this bug will be closed.
>
> See https://wiki.ubuntu.com/Testing/EnableProposed for documentation
 how to enable and use -proposed. Thank you!
>
>
> tags: added: verification-needed-lucid
>
>

All right, I just installed the kernel from lucid-proposed and it would
come up okay. Could log on into GNOME desktop and things appear to
be working normal, just like with previous kernel updates!

--
thomas

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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