Can the update of libudev from 11.1 to 11.2 caused problem with lid switch?
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
After an update of libudev/systemd (details on update below), Ubuntu was not able to read the lid state anymore. Now, the lid state always reports "open". Before the update on the 18th of September, the lid switch worked perfectly and put the system in suspend. Now, it is not working anymore.
Therefore my question: Is it possible that the update of libudev/systemd from 11.1 to 11.2 caused the problem? How could I downgrade from libudev/systemd 11.2 to 11.1 to try out whether it works (synaptic offers only v11 and gives lots of dependency issues)?
Details on my problem are here: http://
2013-09-18 21:03:35 upgrade libudev-dev:amd64 198-0ubuntu11.1 198-0ubuntu11.2
2013-09-18 21:03:36 upgrade libudev1:i386 198-0ubuntu11.1 198-0ubuntu11.2
2013-09-18 21:03:38 upgrade libudev1:amd64 198-0ubuntu11.1 198-0ubuntu11.2
2013-09-18 21:04:04 upgrade libsystemd-
2013-09-18 21:04:05 upgrade libsystemd-
2013-09-18 21:04:06 upgrade systemd-
> Ubuntu was not able to read the lid state anymore.
What do you mean with that, i. e. where did you see the lid switch status? From "upower --dump"?
For downgrading you can select your architecture (i386 or amd64) from https:/ /launchpad. net/ubuntu/ +source/ systemd/ 198-0ubuntu11. 1, then download the older .debs, and install them with "sudo dpkg -i <package>.deb". It's a bit unlikely that systemd-services would affect upower's ability to read the lid switch status, especially as the diff (http:// launchpadlibrar ian.net/ 150608501/ systemd_ 198-0ubuntu11. 1_198-0ubuntu11 .2.diff. gz) does not affect anything is related to lid switch (only timedated, localed, and hostnamed).
But it can certainly not hurt to try and downgrade and see which particular package caused this. I suggest starting with systemd-services and udev first and keep the libraries. Sometimes a mere package upgrade causes the weirdest things which are completely unrelated to the actual code changes.