[SOLVED] GDM restarts at next VT (8) instead of the same VT (7)

jomen · 2010-09-27 13:49:27

Hi,

searched and found only one thread, which looked similar:
https://bbs.archlinux.org/viewtopic.php?id=105120
but I think its not the same issue.

I have tried both methods of starting GDM, the inittab method as well as the daemon method.
This behaviour stays the same with eighter one - and it is annoying.
And it has been this way since I installed arch half a year ago.
Now I'd really like to fix it.
I may have missed some important thing but can't figure it out myself.
Please help!

My issue:

I followed the wiki about Gnome and GDM
http://wiki.archlinux.org/index.php/GNOME
http://wiki.archlinux.org/index.php/Display_Manager

Nothing very special there - it all works.

But:
_every_ time I log out of my Gnome-session GDM will restart (respawn?) on the next available VT.
It initially gets started at VT7 - when I log out it is then at VT8.

Then, nothing really works and I could as well have done a shutdown followed by a restart - would be quicker...

...
When I try to log back in then after a logout, I first see the Background and, after a while, the mouse pointer.
Then nothing appears to happen for quite some time.
After a few minutes, two empty message boxes appear - which, after again some time show the actual messages:
applets failed to load - would I want to delete these to prevent them being started...
and
another Error-message:
(I'll try to translate because the original is in German)

»x-nautilus-desktop:///« could not be displayed.
Error: DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Please choose a different viewer and try again.

original message:

»x-nautilus-desktop:///« konnte nicht angezeigt werden.
Fehler: DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Bitte wählen Sie einen anderen Betrachter und versuchen Sie es erneut.

There are also errors in the GDM-greeter.log.
This is how it looks right now - with everything working and me still logged in,
this is normal, so to speak...though it sure does not look normal to me:

[root@toy gdm]# cat \:0-greeter.log
** (<unknown>:3675): DEBUG: Client registered with session manager: /org/gnome/SessionManager/Client1

(gnome-settings-daemon:3676): GConf-CRITICAL **: gconf_value_get_float: assertion `value->type == GCONF_VALUE_FLOAT' failed
** (process:3707): DEBUG: Greeter session pid=3707 display=:0.0 xauthority=/var/run/gdm/auth-for-gdm-tUv3Q0/database

(polkit-gnome-authentication-agent-1:3705): GLib-GObject-WARNING **: cannot register existing type `_PolkitError'

(polkit-gnome-authentication-agent-1:3705): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
gdm-simple-greeter[3707]: Gtk-WARNING: gtkwidget.c:5628: widget not within a GtkWindow
gdm-simple-greeter[3707]: WARNING: Unable to read from file /etc/arch-release
gdm-simple-greeter[3707]: Pango-WARNING: Invalid UTF-8 string passed to pango_layout_set_text()
Warnung der Fensterverwaltung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1c00037 (Anmeldefen)
Warnung der Fensterverwaltung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Warnung der Fensterverwaltung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1c00037 (Anmeldefen)
Warnung der Fensterverwaltung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Warnung der Fensterverwaltung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1c00037 (Anmeldefen)
Warnung der Fensterverwaltung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Warnung der Fensterverwaltung:CurrentTime used to choose focus window; focus window may not be correct.
Warnung der Fensterverwaltung:Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!

(gnome-power-manager:3706): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(gnome-power-manager:3706): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Warnung der Fensterverwaltung:Log level 16: Failed to send buffer
Warnung der Fensterverwaltung:Log level 16: Failed to send buffer
gdm-simple-greeter[3707]: WARNING: Failed to send buffer

(gnome-power-manager:3706): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-power-manager:3706): atk-bridge-WARNING **: IOR not set.

(gnome-power-manager:3706): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-power-manager:3706): atk-bridge-WARNING **: IOR not set.

(polkit-gnome-authentication-agent-1:3705): polkit-gnome-1-WARNING **: Error enumerating temporary authorizations: Remote Exception invoking org.freedesktop.PolicyKit1.Authority.EnumerateTemporaryAuthorizations() on /org/freedesktop/PolicyKit1/Authority at name org.freedesktop.PolicyKit1: org.freedesktop.PolicyKit1.Error.Failed: Cannot determine session the caller is in

(polkit-gnome-authentication-agent-1:3705): polkit-gnome-1-WARNING **: Error enumerating temporary authorizations: Remote Exception invoking org.freedesktop.PolicyKit1.Authority.EnumerateTemporaryAuthorizations() on /org/freedesktop/PolicyKit1/Authority at name org.freedesktop.PolicyKit1: org.freedesktop.PolicyKit1.Error.Failed: Cannot determine session the caller is in

when logging out and then back in, a few lines are appended (from the last greeter-log)

[root@toy gdm]# cat \:0-greeter.log.1 

...

(polkit-gnome-authentication-agent-1:3986): polkit-gnome-1-WARNING **: Error enumerating temporary authorizations: Remote Exception invoking org.freedesktop.PolicyKit1.Authority.EnumerateTemporaryAuthorizations() on /org/freedesktop/PolicyKit1/Authority at name org.freedesktop.PolicyKit1: org.freedesktop.PolicyKit1.Error.Failed: Cannot determine session the caller is in
polkit-gnome-authentication-agent-1: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.0.
The application 'polkit-gnome-authentication-agent-1' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.

The Desktop then gets populated - but with the contents of my HOME folder rather than the contents of the Desktop folder, which is inside the HOME folder...
And everything appers to work again - distorted as everything looks...and what feels like about 10 minutes later.
As said above - shutdown + restart is much quicker than this - and at least I'm at a clean Desktop.

Last edited by jomen (2010-09-29 10:51:49)

jomen · 2010-09-27 15:31:02

instead of adding more to the already long post, I add via replying to myself:

writing about the issue made some things more clear, so I looked and found this:
http://lists.debian.org/debian-user/201 … 00474.html
which looks like my issue.

I went and tried - and a variation of it works.

1.) I log out
2.) GDM gets restarted - inittab method
it gets restarted at VT8 - it was at VT7
3.) I go to another VT - like VT1 - and log in as root
4.) I find the pid of consolekit with:

ps aux | grep console

and kill it

kill -9 <PID>

5.) I restart GDM - which will be at VT7 now, as it should
and then go back to VT1, because I'll be at the GDM-login screen at VT7 now...
6.) I find and kill consolekit _again_
7.) I can now switch to VT7 with GDM running and log in as it should be

console-kit-daemon will be started _again_ automatically
It seems it gets re-started at the wrong place - or with the wrong options

I always see it running like:

root      6439  0.0  0.3  17432  2768 ?        Sl   17:18   0:00 /usr/sbin/console-kit-daemon --no-daemon

Maybe it is the "--no-daemon" option? Or that it should not be started by GDM but only afterwards, by the Gnome-session?
...or something else...

It is not a solution really, since all this takes as much time as restarting the whole system, but without all the typing and killing and switching back and forth to consoles...but it works.

What is happening here? Is this normal? Where could my misconfiguration be?

Cheers

Last edited by jomen (2010-09-27 15:48:11)

jomen · 2010-09-29 10:50:31

I just finished a fresh installation and everything is working now.

Still, when I log out and then back in, GDM runs at VT8 instead at VT7 where it was.
But it works flawlessly.

Just tried to switch users - logging on as another without logging out, which I never tried before.
I only had one user.
It starts a new GDM-screen at VT8.
The same as when just logging out.

I may have missed something while installing arch the first time around and so ran into this.
Very probably - but not important anymore.
I still have the old install - if someone is interested in finding out what caused this, I could look and compare.
I have not found any obvious differences - and never messed with default configs of dbus or policykit.

Well...
Now everything works.

Cheers

Last edited by jomen (2010-09-29 11:06:47)

Arch Linux

#1 2010-09-27 13:49:27

[SOLVED] GDM restarts at next VT (8) instead of the same VT (7)

#2 2010-09-27 15:31:02

Re: [SOLVED] GDM restarts at next VT (8) instead of the same VT (7)

#3 2010-09-29 10:50:31

Re: [SOLVED] GDM restarts at next VT (8) instead of the same VT (7)

Board footer