Hello, trying to test https://bugzilla.redhat.com/show_bug.cgi?id=731245 as from the message [Test-Announce] Remaining F16 blockers and F16 planning
I installed from f16tc2 vmlinuz+initrd.img inside a kvm guest with direct kernel boot. host is f15+virt-preview and selected spice as video adapter At sw selection during install I chose to: - customize - select kde - deselect gnome
Installation completed but at first boot I completed the normal user definition and sent profile, but then instead of login window I get a window with message:
failed to load session "gdm-shell"
and a logout button I would expect kdm instead of gdm.... and kdm has been installed [root@f16tc2 ~]# type kdm kdm is /usr/bin/kdm
The same flow but leaving default (gnome selected during install and no selection for kde) leads to a system where I can correctly use gdm, instead....
Are my install choices supported? In that case any files I can provide ? My /var/log/messages: Oct 26 15:41:09 f16tc2 dbus-daemon[829]: dbus[829]: [system] Successfully activated service 'org.freedesktop.ConsoleKit' Oct 26 15:41:09 f16tc2 dbus-daemon[829]: dbus[829]: [system] Successfully activated service 'org.freedesktop.Accounts' Oct 26 15:41:09 f16tc2 dbus[829]: [system] Successfully activated service 'org.freedesktop.Accounts' Oct 26 15:41:09 f16tc2 accounts-daemon[986]: started daemon version 0.6.14 Oct 26 15:41:09 f16tc2 systemd-logind[795]: New user gdm logged in. Oct 26 15:41:09 f16tc2 systemd-logind[795]: New session 1 of user gdm. Oct 26 15:41:09 f16tc2 systemd-logind[795]: Linked /tmp/.X11-unix/X0 to /run/user/gdm/X11/display. Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): Enabling debugging Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GsmXsmpServer: SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1054,unix/unix:/tmp/.ICE-u nix/1054#012 Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GsmShell: Not connected to the shell Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GsmManager: setting client store 0x1a46920 Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GdmSignalHandler: Adding handler 1: signum=4 (nil) Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GdmSignalHandler: Registering for 4 signals Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GdmSignalHandler: Adding handler 2: signum=7 (nil) Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GdmSignalHandler: Registering for 7 signals Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GdmSignalHandler: Adding handler 3: signum=11 (nil) Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GdmSignalHandler: Registering for 11 signals Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GdmSignalHandler: Adding handler 4: signum=6 (nil) Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GdmSignalHandler: Registering for 6 signals Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GdmSignalHandler: Adding handler 5: signum=5 (nil) Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GdmSignalHandler: Registering for 5 signals Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GdmSignalHandler: Adding handler 6: signum=8 0x41bf30 Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GdmSignalHandler: Registering for 8 signals Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GdmSignalHandler: Adding handler 7: signum=1 0x41bf30 Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GdmSignalHandler: Registering for 1 signals Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GdmSignalHandler: Adding handler 8: signum=10 0x41bf30 Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GdmSignalHandler: Registering for 10 signals Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GdmSignalHandler: Adding handler 9: signum=15 0x41bf30 Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GdmSignalHandler: Registering for 15 signals Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GdmSignalHandler: Adding handler 10: signum=2 0x41bf30 Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): GdmSignalHandler: Registering for 2 signals Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): fill: *** Getting session 'gdm-shell' Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): fill: *** Looking if /var/lib/gdm/.config/gnome-session/sessions/gdm-shell.session is a valid session file Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): Cannot use session '/var/lib/gdm/.config/gnome-session/sessions/gdm-shell.session': non-existing or invalid file. Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): fill: *** Looking if /etc/xdg/gnome-session/sessions/gdm-shell.session is a valid session file Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): Cannot use session '/etc/xdg/gnome-session/sessions/gdm-shell.session': non-existing or invalid file. Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): fill: *** Looking if /usr/share/gdm/greeter/gnome-session/sessions/gdm-shell.session is a valid session file Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): Cannot use session '/usr/share/gdm/greeter/gnome-session/sessions/gdm-shell.session': non-existing or invalid file. Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): fill: *** Looking if /usr/local/share/gnome-session/sessions/gdm-shell.session is a valid session file Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): Cannot use session '/usr/local/share/gnome-session/sessions/gdm-shell.session': non-existing or invalid file. Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): fill: *** Looking if /usr/share/gnome-session/sessions/gdm-shell.session is a valid session file Oct 26 15:41:09 f16tc2 gnome-session[1054]: DEBUG(+): fill: *** Launching helper 'bash -c 'gnome-shell --help | grep -q gdm-mode && /usr/libexec/gnome-session-check-accelerated'' to know if session is runnable Oct 26 15:41:09 f16tc2 gnome-session[1054]: WARNING: Session 'gdm-shell' runnable check failed: Exited with code 1
Gianluca
On Wed, Oct 26, 2011 at 3:46 PM, Gianluca Cecchi wrote:
Installation completed but at first boot I completed the normal user definition and sent profile, but then instead of login window I get a window with message:
failed to load session "gdm-shell"
and a logout button I would expect kdm instead of gdm.... and kdm has been installed [root@f16tc2 ~]# type kdm kdm is /usr/bin/kdm
While writing /etc/sysconfig/desktop with DISPLAYMANAGER=KDE didn't work on first boot run session (even pressing Ctrl-Alt-Backspace). Setting it and rebooting the system lets kdm start. But the session is by default set to gnome (that I didn't select during install), and it seems I cannot select the "session type" option. At second attemp to click on it I get an X Windows System restart... the same trying to click on "Menu" option
At second click when X restrts: Oct 26 18:17:28 f16tc2 kdm[886]: X server for display :0 terminated unexpectedly Oct 26 18:17:28 f16tc2 kdm: :0[1609]: Fatal X server IO error: Interrupted system call Oct 26 18:17:28 f16tc2 abrt[1620]: saved core dump of pid 1604 (/usr/bin/Xorg) to /var/spool/abrt/ccpp-2011-10-26-18:17:28-1604 (3424256 bytes) Oct 26 18:17:28 f16tc2 abrtd: Directory 'ccpp-2011-10-26-18:17:28-1604' creation detected Oct 26 18:17:28 f16tc2 abrtd: DUP_OF_DIR: /var/spool/abrt/ccpp-2011-10-26-18:09:50-1212 Oct 26 18:17:28 f16tc2 abrtd: Dump directory is a duplicate of /var/spool/abrt/ccpp-2011-10-26-18:09:50-1212 Oct 26 18:17:28 f16tc2 abrtd: Deleting dump directory ccpp-2011-10-26-18:17:28-1604 (dup of ccpp-2011-10-26-18:09:50-1212), sending dbus signal
BTW: switching to a console window gives only garbage characters on all over the screen....
On 10/26/2011 12:18 PM, Gianluca Cecchi wrote:
On Wed, Oct 26, 2011 at 3:46 PM, Gianluca Cecchi wrote:
Installation completed but at first boot I completed the normal user definition and sent profile, but then instead of login window I get a window with message:
failed to load session "gdm-shell"
and a logout button I would expect kdm instead of gdm.... and kdm has been installed [root@f16tc2 ~]# type kdm kdm is /usr/bin/kdm
While writing /etc/sysconfig/desktop with DISPLAYMANAGER=KDE didn't work on first boot run session (even pressing Ctrl-Alt-Backspace). Setting it and rebooting the system lets kdm start. But the session is by default set to gnome (that I didn't select during install), and it seems I cannot select the "session type" option. At second attemp to click on it I get an X Windows System restart... the same trying to click on "Menu" option
At second click when X restrts: Oct 26 18:17:28 f16tc2 kdm[886]: X server for display :0 terminated unexpectedly Oct 26 18:17:28 f16tc2 kdm: :0[1609]: Fatal X server IO error: Interrupted system call Oct 26 18:17:28 f16tc2 abrt[1620]: saved core dump of pid 1604 (/usr/bin/Xorg) to /var/spool/abrt/ccpp-2011-10-26-18:17:28-1604 (3424256 bytes) Oct 26 18:17:28 f16tc2 abrtd: Directory 'ccpp-2011-10-26-18:17:28-1604' creation detected Oct 26 18:17:28 f16tc2 abrtd: DUP_OF_DIR: /var/spool/abrt/ccpp-2011-10-26-18:09:50-1212 Oct 26 18:17:28 f16tc2 abrtd: Dump directory is a duplicate of /var/spool/abrt/ccpp-2011-10-26-18:09:50-1212 Oct 26 18:17:28 f16tc2 abrtd: Deleting dump directory ccpp-2011-10-26-18:17:28-1604 (dup of ccpp-2011-10-26-18:09:50-1212), sending dbus signal
BTW: switching to a console window gives only garbage characters on all over the screen....
I ran into this on an earlier incarnation of F16 and had to install xdm as the display manager.
I would expect kdm if gnome desktop not selected and kdm selected. Looks like a bug.
On Wed, 2011-10-26 at 18:18 +0200, Gianluca Cecchi wrote:
On Wed, Oct 26, 2011 at 3:46 PM, Gianluca Cecchi wrote:
Installation completed but at first boot I completed the normal user definition and sent profile, but then instead of login window I get a window with message:
failed to load session "gdm-shell"
and a logout button I would expect kdm instead of gdm.... and kdm has been installed [root@f16tc2 ~]# type kdm kdm is /usr/bin/kdm
While writing /etc/sysconfig/desktop with DISPLAYMANAGER=KDE didn't work on first boot run session (even pressing Ctrl-Alt-Backspace). Setting it and rebooting the system lets kdm start. But the session is by default set to gnome (that I didn't select during install), and it seems I cannot select the "session type" option. At second attemp to click on it I get an X Windows System restart... the same trying to click on "Menu" option
At second click when X restrts: Oct 26 18:17:28 f16tc2 kdm[886]: X server for display :0 terminated unexpectedly Oct 26 18:17:28 f16tc2 kdm: :0[1609]: Fatal X server IO error: Interrupted system call Oct 26 18:17:28 f16tc2 abrt[1620]: saved core dump of pid 1604 (/usr/bin/Xorg) to /var/spool/abrt/ccpp-2011-10-26-18:17:28-1604 (3424256 bytes) Oct 26 18:17:28 f16tc2 abrtd: Directory 'ccpp-2011-10-26-18:17:28-1604' creation detected Oct 26 18:17:28 f16tc2 abrtd: DUP_OF_DIR: /var/spool/abrt/ccpp-2011-10-26-18:09:50-1212 Oct 26 18:17:28 f16tc2 abrtd: Dump directory is a duplicate of /var/spool/abrt/ccpp-2011-10-26-18:09:50-1212 Oct 26 18:17:28 f16tc2 abrtd: Deleting dump directory ccpp-2011-10-26-18:17:28-1604 (dup of ccpp-2011-10-26-18:09:50-1212), sending dbus signal
BTW: switching to a console window gives only garbage characters on all over the screen....
Yike. There's clearly a bug here, yes. Probably more than one.
One of the bugs you're hitting is the one that's currently tracked here:
https://bugzilla.redhat.com/show_bug.cgi?id=746693
gdm has got a bit complicated lately. If you have GNOME Shell installed and it works, login isn't actually handled by gdm itself at all: GNOME Shell runs in a special mode and handles login. This is /usr/share/gnome-session/sessions/gdm-shell.session .
If you don't have GNOME Shell installed, or your hardware doesn't support Shell, you get /usr/share/gnome-session/sessions/gdm-fallback.session , which is actually gdm. However, it seems to have grown a dependency on metacity (whether it really needs one or not). So *that* bug is: gdm's 'fallback mode' doesn't work if metacity isn't present, but gdm doesn't depend on metacity.
Then there's the issue of why you're getting gdm at all when you de-selected GNOME and selected KDE, and why when you get it working it thinks there's a GNOME session available. I suspect that's dependency/comps problems we'd need to figure out. It would help to have the logs of what packages actually got installed, but I should be able to reproduce that fairly easily. I'll look into it.
On Wed, 2011-10-26 at 10:37 -0700, Adam Williamson wrote:
On Wed, 2011-10-26 at 18:18 +0200, Gianluca Cecchi wrote:
On Wed, Oct 26, 2011 at 3:46 PM, Gianluca Cecchi wrote:
Installation completed but at first boot I completed the normal user definition and sent profile, but then instead of login window I get a window with message:
failed to load session "gdm-shell"
and a logout button I would expect kdm instead of gdm.... and kdm has been installed [root@f16tc2 ~]# type kdm kdm is /usr/bin/kdm
While writing /etc/sysconfig/desktop with DISPLAYMANAGER=KDE didn't work on first boot run session (even pressing Ctrl-Alt-Backspace). Setting it and rebooting the system lets kdm start. But the session is by default set to gnome (that I didn't select during install), and it seems I cannot select the "session type" option. At second attemp to click on it I get an X Windows System restart... the same trying to click on "Menu" option
At second click when X restrts: Oct 26 18:17:28 f16tc2 kdm[886]: X server for display :0 terminated unexpectedly Oct 26 18:17:28 f16tc2 kdm: :0[1609]: Fatal X server IO error: Interrupted system call Oct 26 18:17:28 f16tc2 abrt[1620]: saved core dump of pid 1604 (/usr/bin/Xorg) to /var/spool/abrt/ccpp-2011-10-26-18:17:28-1604 (3424256 bytes) Oct 26 18:17:28 f16tc2 abrtd: Directory 'ccpp-2011-10-26-18:17:28-1604' creation detected Oct 26 18:17:28 f16tc2 abrtd: DUP_OF_DIR: /var/spool/abrt/ccpp-2011-10-26-18:09:50-1212 Oct 26 18:17:28 f16tc2 abrtd: Dump directory is a duplicate of /var/spool/abrt/ccpp-2011-10-26-18:09:50-1212 Oct 26 18:17:28 f16tc2 abrtd: Deleting dump directory ccpp-2011-10-26-18:17:28-1604 (dup of ccpp-2011-10-26-18:09:50-1212), sending dbus signal
BTW: switching to a console window gives only garbage characters on all over the screen....
Yike. There's clearly a bug here, yes. Probably more than one.
One of the bugs you're hitting is the one that's currently tracked here:
https://bugzilla.redhat.com/show_bug.cgi?id=746693
gdm has got a bit complicated lately. If you have GNOME Shell installed and it works, login isn't actually handled by gdm itself at all: GNOME Shell runs in a special mode and handles login. This is /usr/share/gnome-session/sessions/gdm-shell.session .
If you don't have GNOME Shell installed, or your hardware doesn't support Shell, you get /usr/share/gnome-session/sessions/gdm-fallback.session , which is actually gdm. However, it seems to have grown a dependency on metacity (whether it really needs one or not). So *that* bug is: gdm's 'fallback mode' doesn't work if metacity isn't present, but gdm doesn't depend on metacity.
Then there's the issue of why you're getting gdm at all when you de-selected GNOME and selected KDE, and why when you get it working it thinks there's a GNOME session available. I suspect that's dependency/comps problems we'd need to figure out. It would help to have the logs of what packages actually got installed, but I should be able to reproduce that fairly easily. I'll look into it.
Well, I can't reproduce the most worrying issue here, with TC2: I just took the TC2 DVD, selected KDE, de-selected GNOME, and got a system with kdm installed but not gdm. It boots to a kdm login window and I can log in.
Did you make any other customizations to the package set?
There may be a difference between DVD and net install here somehow, I guess, but I can't immediately see how.
On Wed, 2011-10-26 at 11:09 -0700, Adam Williamson wrote:
Well, I can't reproduce the most worrying issue here, with TC2: I just took the TC2 DVD, selected KDE, de-selected GNOME, and got a system with kdm installed but not gdm. It boots to a kdm login window and I can log in.
Selecting Xfce and de-selecting GNOME also works, going for LXDE next...
On 10/26/2011 08:26 PM, Adam Williamson wrote:
On Wed, 2011-10-26 at 11:09 -0700, Adam Williamson wrote:
Well, I can't reproduce the most worrying issue here, with TC2: I just took the TC2 DVD, selected KDE, de-selected GNOME, and got a system with kdm installed but not gdm. It boots to a kdm login window and I can log in.
Selecting Xfce and de-selecting GNOME also works, going for LXDE next...
Just tested and it works fine with RC4. (It was broken in RC1 or 2)
-- Richard Marko
On Wed Oct 26 18:09:48 UTC 2011 Adam Williamson wrote:
Well, I can't reproduce the most worrying issue here, with TC2: I just took the TC2 DVD, selected KDE, de-selected GNOME, and got a system with kdm installed but not gdm. It boots to a kdm login window and I can log in. Did you make any other customizations to the package set?
No. No other changes. I can send install.log and yum.log. Let me know Update: today I ran - yum distro-sync full (had to remove autocorr-en and its dependencies because they came from updates-testing and otherwise the command didn't complete) - disable updates-testing repo - yum update And I think I'm now at RC4. - reboot Now kdm starts correctly and I'm able to drop down the "session type" and choose the "KDE plasma workspace" and able to login. Switching to console is correct too; no further garbage in ttys screens as before. Thanks I can start form scratch the install from vmlinuz+initrd from rc4 an retest the cycle... At this moment I manually created the classic /etc/sysconfig/desktop file. Is this supposed to be obsoleted now? And installation correctly care of defaulting to kdm when selected KDE, de-selected GNOME?
Gianluca
On Wed Nov 2 15:17:09 UTC 2011 Richard Marko wrote:
Just tested and it works fine with RC4. (It was broken in RC1 or 2)
And I confirm that installing in a Qemu/KVM (host is f15+virt-preview), with direct kernel+initrd boot from rc4 and choosing: - fresh install - customize now - deselect gnome - select kde
works without any problem ootb. At reboot kdm starts without problems and all is ok for menus, kde session and consoles.
BTW: It would be nice to have spice-vdagent package automatically installed if qxl is... or by default... I had to install it manually inside the guest and verified that it works correctly, at least with copy/paste operations from/to the guest
Gianluca
On Wed, 2011-11-02 at 16:42 +0100, Gianluca Cecchi wrote:
On Wed Nov 2 15:17:09 UTC 2011 Richard Marko wrote:
Just tested and it works fine with RC4. (It was broken in RC1 or 2)
And I confirm that installing in a Qemu/KVM (host is f15+virt-preview), with direct kernel+initrd boot from rc4 and choosing:
- fresh install
- customize now
- deselect gnome
- select kde
works without any problem ootb. At reboot kdm starts without problems and all is ok for menus, kde session and consoles.
BTW: It would be nice to have spice-vdagent package automatically installed if qxl is... or by default... I had to install it manually inside the guest and verified that it works correctly, at least with copy/paste operations from/to the guest
yeah, I'm not sure exactly which level that should be implemented at, but it'd be a nice convenience feature. hell, we could build it into the installer environment even.