On Sat, Dec 7, 2013 at 1:17 PM, Cristian Rodríguez
<crrodriguez@opensuse.org> wrote:
El 07/12/13 15:01, Greg Freemyer escribió:
On Sat, Dec 7, 2013 at 11:56 AM, Cristian Rodríguez
<crrodriguez@opensuse.org> wrote:
El 07/12/13 12:09, Greg Freemyer escribió:
# shutdown Failed to tald to shutdownd, proceeding with immediate shutdown: Connection refused Failed to open /dev/initctl: No such device or address Failed to talk to init daemon #
Is this a 32 bit version right ?
Correct
it is a known bug that affects 32 bit systems only, no.. it is not a bug in systemd, so resist the urge of shooting the messenger :-P.. it is a kernel regression. fixed in 3.11.8.
hmm... How many users are getting hit by this? I'm running vanilla 13.1 OSS and upgrades as far as this bug is concerned. Is it in bugzilla?
This may be the same bug, so I added a comment to it: <https://bugzilla.novell.com/show_bug.cgi?id=839170>
If you're right, there is no point troubleshooting.
Will cycling power fix it? Or at least let me connect to wireless?
If not, the only option I can think of off-hand to fix it is to use susestudio to build a custom live CD with a newer kernel (which is already in OBS). Then use that boot CD/DVD to upgrade my laptop in place.
That's not as hard as it sounds, but is there a better way?
Thanks Greg I get something similar on 64bit opensuse 13.1 (and previous versions) where
On Saturday 07 Dec 2013 21:54:44 Greg Freemyer wrote: the shutdown proceeds, the screen switches from graphical (ctrl-alt f7) to a CLI session on ctrl-alt-F1 which is at the login prompt and it stops there. I just login and type in shutdown or init 0 and it eventually shuts down and switches off. Sometimes i've done a "zypper up" during the sessions and sometimes i've not updated anything so i've never noticed a pattern of when it does it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org