[Bug 1252121] Re: with installing TLP: missing PrepareForSleep signal after resuming, causing networking to stay disabled
I'm not using TLP or Jupiter or powertop, still I have the problem even with the PPA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: with installing TLP: missing PrepareForSleep signal after resuming, causing networking to stay disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184262] Re: times out too early, stuck in PrepareForSleep, causing network and other services to not resume
This doesn't make it worse for me, it makes it better, but it still doesn't completely solve the network failing to resume problem. As with the first patch I get a failure rate of around 1 in 30. I've tried suspending 30 times in 3 different ways: using the lid, using sudo pm- suspend and the menu or the power button menu. The X below shows the failure :) lid: | X pm-suspend: | | menu/power button: | | The failure case was solved by running nmcli nm sleep false. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184262 Title: times out too early, stuck in PrepareForSleep, causing network and other services to not resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1184262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184262] Re: times out too early, stuck in PrepareForSleep, causing network and other services to not resume
I'll try this experiment and report in the next 24 hours then. It takes quite a bit, and I'll try to get a larger number of repeats. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184262 Title: times out too early, stuck in PrepareForSleep, causing network and other services to not resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1184262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1252121] Re: networkmanager networking is disabled on suspend-resume
Hey Martin, I tried the command you gave in comment #6, and I could reproduce the network problem in 13 tries. Unfortunately this seems to invalidate your hypothesis on only the lid closing causing the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: networkmanager networking is disabled on suspend-resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1252121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234469] Re: Network does not come up after resuming from suspend.
*** This bug is a duplicate of bug 1184262 *** https://bugs.launchpad.net/bugs/1184262 @Vladimir: you're commenting on a duplicate. There is already a potential fix in the comments of #1184262. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234469 Title: Network does not come up after resuming from suspend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume
For me Martin's package solves the problem ~96.6% of the time, which is already great progress since before I was having the problem almost every time. I've tried suspending my machine about 30 times (10 times by closing the lid, 10 times by clicking the suspend button in the menu, and 10 times with pm-suspend), and I got only one case when the network didn't come back. In the failing case the error reported by systemd-logind was slightly different than before (see #34 for the previous error message): Lid closed. Suspending... Failed to send delayed message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Lid opened. I no longer encountered the case when resumption didn't work at all (machine going back to sleep as in #34). And it happened twice that pm- suspend wouldn't do anything (with output from systemd-logind). Anyway, this is a step in the right direction, I would say :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184262 Title: [logind] stuck in PrepareForSleep, causing network and other services to not resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1184262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume
@Daniel Lombraña González (teleyinex) #66 however, if I suspend the machine again and resume it, after few seconds it starts again to suspend without me doing anything, leaving the machine in an unusable state. Just try resuming again and again. For me this eventually works, but it sometimes takes 4-5 retries. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184262 Title: [logind] stuck in PrepareForSleep, causing network and other services to not resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume
I'm getting this with GNOME classic. On Mon, Oct 28, 2013 at 4:19 PM, Evan Huus 1184...@bugs.launchpad.net wrote: Martin, I am seeing this regularly under Unity. Smells like a race condition to me. -- You received this bug notification because you are subscribed to a duplicate bug report (1234469). https://bugs.launchpad.net/bugs/1184262 Title: [logind] stuck in PrepareForSleep, causing network and other services to not resume Status in “network-manager” package in Ubuntu: Confirmed Status in “systemd” package in Ubuntu: Incomplete Bug description: After a suspend/resume, network-manager claimed that wireless was not available and would not let me reconnect to the wireless here. 'iwlist wlan1 scan' would also not work; so thinking that it was a driver problem, I rebooted the system. When it came back up, nm- applet in lightdm claimed that networking was disabled, and the option to enable it was greyed out. It could also not be enabled by nmcli. I ended up stopping network-manager, bringing up the interface via /etc/network/interfaces, and logging in... at which point, restarting network-manager *did* let me enable networking from my logged-in session. So there are several problems here: - after a reboot, network-manager claimed networking was disabled. - nm-applet is not letting me enable networking from the lightdm session. - the networking was failing after a suspend/resume cycle, and could not be enabled even from inside the user session. The last issue probably *was* a kernel driver problem; but the first two issues are network-manager problems of some kind. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu8 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 21:38:31 2013 InstallationDate: Installed on 2010-09-24 (974 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) IpRoute: default via 192.168.1.1 dev wlan1 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.106 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago) WifiSyslog: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: ** (process:11977): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN not running unknownunknown unknown unknown unknownunknown unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184262 Title: [logind] stuck in PrepareForSleep, causing network and other services to not resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume
@Pablo180 (paultait22) #30: I'm already running 3.11.0-12-generic, so changing to that can't be the fix. @Julien Olivier (julo) #33: I also have this probably related problem, and so far I found no workaround for that, other than trying to resume again and again until it eventually works. I've already mentioned this in one of the duplicates (1234469), but I'll repeat the log I get from systemd-logind for a case in which the first 3 resumes failed, but the fourth one succeeded. Lid closed. Suspending... Failed to execute operation: Message did not receive a reply (timeout by message bus) Suspending... Failed to execute operation: Message did not receive a reply (timeout by message bus) Suspending... Failed to execute operation: Message did not receive a reply (timeout by message bus) Suspending... Lid opened. Operation finished. Other problems I encountered that seem also related: sometimes the computer fails to suspend and sometimes even fails to shutdown. Everything worked fine before this crappy Ubuntu upgrade. I'm on a Dell Latitude 6400. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184262 Title: [logind] stuck in PrepareForSleep, causing network and other services to not resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107374] Re: adding new entries to alacarte has no effect
I'm having this problem on Ubuntu 13.10 and alacarte 3.10.0-1, both as normal user and as root. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/107374 Title: adding new entries to alacarte has no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/107374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume
General question: since Ubuntu seems to not support reverting dist- upgrades, is there any collection of packages I can restore to their pre 13.10 working state to avoid this horrible problem? (If not I'll seriously consider switching distribution; this is just too much) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184262 Title: [logind] stuck in PrepareForSleep, causing network and other services to not resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234469] Re: Network does not come up after resuming from suspend.
*** This bug is a duplicate of bug 1184262 *** https://bugs.launchpad.net/bugs/1184262 Here is one more log for a case in which the first 3 resumes failed, but the fourth one succeeded. Lid closed. Suspending... Failed to execute operation: Message did not receive a reply (timeout by message bus) Suspending... Failed to execute operation: Message did not receive a reply (timeout by message bus) Suspending... Failed to execute operation: Message did not receive a reply (timeout by message bus) Suspending... Lid opened. Operation finished. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234469 Title: Network does not come up after resuming from suspend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1234469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234469] Re: Network does not come up after resuming from suspend.
*** This bug is a duplicate of bug 1184262 *** https://bugs.launchpad.net/bugs/1184262 I've tried suggested by pitti. After the first suspend and resume I get this: Lid closed. Suspending... Failed to send delayed message: Message did not receive a reply (timeout by message bus) Lid opened. Networking was disabled so I brought it back up with nmcli nm sleep false. Then I suspended again. After the second suspend trying to resume just led to another suspend I didn't ask for. Had to force another resume (power button) before the thing actually resumed: Lid closed. Suspending... Failed to execute operation: Message did not receive a reply (timeout by message bus) Suspending... Operation finished. Lid opened. Earlier today it happened to me that I couldn't resume at all because of this problem happening many times in a row. I would get to the login prompt but the machine would go back to sleep so fast that I wouldn't even have time to enter my password. I had to power off and restart the machine to take it out of that state. I'm on a Dell Latitude E6400. BTW. Should I stop commenting here and switch to #1184262 instead? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234469 Title: Network does not come up after resuming from suspend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1234469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 596095] Re: /usr/lib/cups/filter/pstopdf failed for any PDF
I know this is an old one, but I'm getting the same error message (/usr/lib/cups/filter/pstopdf failed) with Ubuntu 13.10, CUPS 1.7rc1, and various TOSHIBA e-Studio printers with the recommended Foomatic/pxlmono and Foomatic/Postscript drivers. Was this bug ever fixed and this is a regression? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/596095 Title: /usr/lib/cups/filter/pstopdf failed for any PDF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/596095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1116513] Re: /usr/lib/cups/filter/pdftops failed
What happened with this bug? I'm getting the same error message (/usr/lib/cups/filter/pstopdf failed) with Ubuntu 13.10, CUPS 1.7rc1, poppler 24.1 and various TOSHIBA e-Studio printers with the recommended Foomatic/pxlmono and Foomatic/Postscript drivers. I'm on a Dell Latitude E6400. Was this bug ever fixed and is my problem a regression? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1116513 Title: /usr/lib/cups/filter/pdftops failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1116513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1116513] Re: /usr/lib/cups/filter/pdftops failed
Correction: my problem is with /usr/lib/cups/filter/pdftops (typo in #6) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1116513 Title: /usr/lib/cups/filter/pdftops failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1116513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1116513] Re: /usr/lib/cups/filter/pdftops failed
Eventually I manged to make both my Toshiba printers work with a combination of the workarounds described here https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120 and changing to the autodetected drivers although they don't really match the precise model of the printer and other drivers are recommended for one of the priters. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1116513 Title: /usr/lib/cups/filter/pdftops failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1116513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234469] Re: Network does not come up after resuming from suspend.
Updated to 13.10 just to run into this bug. It happens to me every time I close the lid (Suspend). Every single Ubuntu update has been a similar fiasco for me. I'm beyond disapointed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234469 Title: Network does not come up after resuming from suspend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1234469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1075923] Re: nautilus hangs copying large directories from a samba share
Everything works well for me after updating to version 1.16.1-0ubuntu1.1 I could download 1.7GB of photos from my camera without any trouble. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075923 Title: nautilus hangs copying large directories from a samba share To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1075923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 830267] Re: Hibernation fails with not enough free memory error
I get a similar error on a Dell Latitude E6400 after updating to Ubuntu 12.04 with 4G of RAM and a 6GB swap partition (didn't have the problem before the update). My kernel version is 3.2.0-24-generic-pae. I've attached the relevant part of the syslog. ** Attachment added: syslog-hibernate-problem.log https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/830267/+attachment/3138607/+files/syslog-hibernate-problem.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/830267 Title: Hibernation fails with not enough free memory error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/830267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 712521] Re: [Needs packaging] TeXLive 2011
Just for the record, Norbert is talking about this debian-tex-maint thread: http://lists.debian.org/debian-tex-maint/2011/11/msg6.html So there is new hope :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/712521 Title: [Needs packaging] TeXLive 2011 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/712521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 712521] Re: [Needs packaging] TeXLive 2011
I think that from the options Norbert presented I prefer #2: pay someone to do it for you. I willing to pledge 30$ to see this fixed ASAP. Does anyone else want to put their money where their mouth is? We could start a Pledgie campaign for this!? Just to see if this is realistic or not, maybe Norbert can tell us what would be a good target we should be aiming at :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/712521 Title: [Needs packaging] TeXLive 2011 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/712521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 712521] Re: [Needs packaging] TeXLive 2011
@preining Could you post the links to the preliminary 2011 packages here too? I would like to try. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/712521 Title: [Needs packaging] TeXLive 2011 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/712521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 712521] Re: [Needs packaging] TeXLive 2011
How about removing the ancient texlive 2009 from Ubuntu, and advising people to install Tex Live 2011 directly from here: http://www.tug.org/texlive/ The completely obsolete version you ship with Ubuntu is much worse than nothing! It forces novices into using buggy versions of TeX packages, although these bugs were fixed years ago. All this wait 2 years and we'll make a monolithic Tex Live package for you is just bullshit! Either get your shit together and package things in a reasonable time, or admit that you're not able to keep up with the rate at which Tex Live, and stop confusing everyone with obsolete packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/712521 Title: [Needs packaging] TeXLive 2011 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/712521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 661711] Re: Hibernate fails on Thinkpad X60
I'm having the same problem (I think) with a Dell Latitude E6400 on Ubuntu 10.10. Booting with the previous kernel 2.6.32-25 (the one before the 10.10 upgrade) seems to have solved the problem for me. Could it be that this problem was introduced by kernel version 2.6.35-22? -- Hibernate fails on Thinkpad X60 https://bugs.launchpad.net/bugs/661711 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
