Up-to-date Fedora 14 Beta (Oct 1st):
"init 1" (or also "init 3") run from within a GNOME session here doesn't terminate X.
Is it just my installation or reproducible?
$ rpm -qf /sbin/init upstart-sysvinit-0.6.5-9.fc14.i686
Am Fri, 1 Oct 2010 21:40:13 +0200 schrieb Michael Schwendt mschwendt@gmail.com:
Up-to-date Fedora 14 Beta (Oct 1st):
"init 1" (or also "init 3") run from within a GNOME session here doesn't terminate X.
Is it just my installation or reproducible?
$ rpm -qf /sbin/init upstart-sysvinit-0.6.5-9.fc14.i686
It's reproducible for me, maybe a bug? o,O
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 10/01/2010 02:40 PM, Michael Schwendt wrote:
Up-to-date Fedora 14 Beta (Oct 1st):
"init 1" (or also "init 3") run from within a GNOME session here doesn't terminate X.
Is it just my installation or reproducible?
$ rpm -qf /sbin/init upstart-sysvinit-0.6.5-9.fc14.i686
I have the same issue. I suspected the graphics driver (radeon). For me booting with the kernel parameter nohz=off seems to resolve the issue (and improves the performance of Xorg).
- -Jeff
On Fri, 01 Oct 2010 22:38:28 -0500, Jeff wrote:
Up-to-date Fedora 14 Beta (Oct 1st):
"init 1" (or also "init 3") run from within a GNOME session here doesn't terminate X.
Is it just my installation or reproducible?
$ rpm -qf /sbin/init upstart-sysvinit-0.6.5-9.fc14.i686
I have the same issue. I suspected the graphics driver (radeon). For me booting with the kernel parameter nohz=off seems to resolve the issue (and improves the performance of Xorg).
nohz=off didn't change anything for me.
I've filed a bug about "upstart" even if that may be the wrong component: https://bugzilla.redhat.com/640925