libglib2.0-0 is breaking some parts

Bug #901407 reported by Sworddragon
This bug affects 3 people
Affects Status Importance Assigned to Milestone
lxdm (Ubuntu)
Julien Lavergne

Bug Description

I'm using Ubuntu 12.04 dev and have upgraded libglib2.0-0 to version 2.31.2-0ubuntu1. After a reboot of the system lxdm-binary was using constantly 100% cpu time of one core. If gksu is started from PCmanFM it isn't even showing every time. Downgrading libglib2.0-0 to version 2.30.0-0ubuntu4 fixes both problems.

Related branches

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

thank you for your bug report, the gksu issue was a libgksu issue which got fixed today:

without extra details it's likely that the lxdm issue is due to that software, reassigning there but feel free to reassign back to glib if it's really a bug in glib and not something weird lxdm is doing

affects: glib2.0 (Ubuntu) → lxdm (Ubuntu)
Revision history for this message
Sworddragon (sworddragon-deactivatedaccount) wrote :

The gksu issue was not fixed for me with this version. It seems this is a problem which is related to libglib2.0-0 too.

Julien Lavergne (gilir)
Changed in lxdm (Ubuntu):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Julien Lavergne (gilir)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lxdm - 0.4.1-0ubuntu5

lxdm (0.4.1-0ubuntu5) precise; urgency=low

  * debian/patches/90_fix_event_check.patch:
   - From upstream, fix event check which causes 100% CPU activity.
     LP: #901407
 -- Julien Lavergne <email address hidden> Sun, 01 Jan 2012 17:17:02 +0100

Changed in lxdm (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Kuya Marc (kuya-marc) wrote :

I found a Quick Fix!!!

First and foremost, add this alias to your list of aliases:

alias reset-lxdm='sudo killall lxdm-binary && sleep 5 && sudo lxdm-binary &'

Second, on a cold-boot, login as normal, but this time, press Ctrl-Alt-F1 and login. Type the reset-lxdm command.

And third, re-login as normal.

On repeated reboots, repeat steps 2 and 3.

I am not sure how to do a automated-timed killall of lxdm-binary at bootup.

Revision history for this message
Sworddragon (sworddragon-deactivatedaccount) wrote :

Maybe you are landed in the wrong ticket. This problem is already solved but there is another similar problem:

Revision history for this message
Jebril WeedWall (jebril) wrote :

I don't understand how they could release something like this as a finished product. Seriously...

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

Other bug subscribers