Hi,
I did a fresh install of F9Beta on my second test HDD (only default things). After an upgrade to the latest rawhide I noticed a new /etc/inittab.rpmnew file. I made a backup of inittab and switched to a new version. After a reboot gdm doesn't start automatically - "telinit 3, telinit 5" fixes this problem.
/etc/event.d/prefdm start on stopped rc5 <- broken deps in upstart?
I suggest to restore line x:5:respawn:/etc/X11/prefdm -nodaemon in inittab.
Regards, Michal
I experience the same. After ctrl+alt+backspace kdm doesn't restore
On Fri, Apr 18, 2008 at 11:12 AM, Optimization Kit optimizationkit@gmail.com wrote:
Hi,
I did a fresh install of F9Beta on my second test HDD (only default things). After an upgrade to the latest rawhide I noticed a new /etc/inittab.rpmnew file. I made a backup of inittab and switched to a new version. After a reboot gdm doesn't start automatically - "telinit 3, telinit 5" fixes this problem.
/etc/event.d/prefdm start on stopped rc5 <- broken deps in upstart?
I suggest to restore line x:5:respawn:/etc/X11/prefdm -nodaemon in inittab.
Regards, Michal
-- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Optimization Kit (optimizationkit@gmail.com) said:
I did a fresh install of F9Beta on my second test HDD (only default things). After an upgrade to the latest rawhide I noticed a new /etc/inittab.rpmnew file. I made a backup of inittab and switched to a new version. After a reboot gdm doesn't start automatically - "telinit 3, telinit 5" fixes this problem.
/etc/event.d/prefdm start on stopped rc5 <- broken deps in upstart?
Shouldn't be. Are you booting to runlevel 5? Does gdm log anything to /var/log/messages.
I suggest to restore line x:5:respawn:/etc/X11/prefdm -nodaemon in inittab.
That won't solve anything, as that line would be ignored.
Bill
On 18/04/2008, Bill Nottingham notting@redhat.com wrote:
Optimization Kit (optimizationkit@gmail.com) said:
I did a fresh install of F9Beta on my second test HDD (only default things). After an upgrade to the latest rawhide I noticed a new /etc/inittab.rpmnew file. I made a backup of inittab and switched to a new version. After a reboot gdm doesn't start automatically - "telinit 3, telinit 5" fixes this problem.
/etc/event.d/prefdm start on stopped rc5 <- broken deps in upstart?
Shouldn't be. Are you booting to runlevel 5?
Gahhh, I guess no http://www.stardust.webpages.pl/files/gdm_problem/inittab.rpmnew id:3:initdefault:
Why init 3 is a default runlevel?
/var/log/messages http://www.stardust.webpages.pl/files/gdm_problem/messages
original inittab http://www.stardust.webpages.pl/files/gdm_problem/inittab
Regards, Michal
Optimization Kit (optimizationkit@gmail.com) said:
Shouldn't be. Are you booting to runlevel 5?
Gahhh, I guess no http://www.stardust.webpages.pl/files/gdm_problem/inittab.rpmnew id:3:initdefault:
Why init 3 is a default runlevel?
It always has been, requiring admin (or installer) action to change it.
Bill
On Fri, Apr 18, 2008 at 6:13 AM, Bill Nottingham notting@redhat.com wrote:
It always has been, requiring admin (or installer) action to change it.
Or to put a finer point on it.....a working run level 3 is a common denominator that all systems should have...so its a reasonable default for a config file. For typical install situations (single user home systems), the installer will choose to set the default runlevel to 5 as appropriate before you boot into the system for the first time.
-jef"Never blindly replace a working config with an rpmnew'd version of that config. You should be reviewing diffs of the files to make sure the config is what you expect"spaleta
On 18/04/2008, Jeff Spaleta jspaleta@gmail.com wrote:
"Never blindly replace a working config with an rpmnew'd version of that config. You should be reviewing diffs of the files to make sure the config is what you expect"
I'll remember this.