You are not logged in.
Pages: 1
A problem began just yesterday. I'm running GNOME. I suspend (close the laptop lid), and when I resume, the first thing I notice is that the wifi is not connected. I click the network menu and it says "not managed" under both "Wired" and "Wireless". I click Power Off from the user menu and the dialogue comes up as usual. But clicking Restart or Power Off only dismisses the dialogue. The computer does nothing. I cannot turn off the computer (by normal means). Also, it won't suspend a second time. If I close the lid, it stays on. I hit Ctrl-Alt-F6 and the screen goes blank with a cursor blinking at the top left, but the login prompt never appears. The only way to turn off my computer (after suspend) is to hold down the power button. Everything works fine after booting. It's only after suspend (to RAM) that all these system issues happen. Again, before yesterday I could suspend and resume all day long and everything worked fine.
Last edited by MisterEwok (2013-09-22 20:01:44)
Offline
Looks like today's update fixed the problem...
Offline
Others had resume issues. See: https://bbs.archlinux.org/viewtopic.php?id=170008), I forgot to mention that I had wifi problems too. You're the second person to say today's update (I assume you went from systemd 207-[3..4] to 207-5) fixes the problem.
edit: forgot the end of my sentence
Last edited by agumonkey (2013-09-25 09:51:10)
Offline
So, this problem persists. It just isn't consistent like it was before the above-referenced update (yes, it was to systemd 207-5).
Offline
It seems the bug is a bad interaction between many parts, kernel, systemd and maybe some services. As I said, I don't have the issue, but I don't run many things on my machine.
Offline
I've switched to booting linux-lts (with which this problem does not occur), but the problem persists with the most recent linux.
Offline
I've been using the standard linux for a couple of days now, and I haven't had a problem. So, I'm assuming this bug has been worked out?
Offline
Pages: 1