On 02/03/2010 05:50 PM, ubiquitous1980 wrote:
> Alan McKinnon wrote:
>> On Wednesday 03 February 2010 09:15:05 ubiquitous1980 wrote:
>>
>>> Daniel Troeder wrote:
>>>
>>>> On 02/02/2010 06:10 PM, ubiquitous1980 wrote:
>>>>
>>>>> Selecting shut down in the menu sometimes lands me back a gdm login
>>>>> screen. At other times, the computer shuts down normally.
>>>>>
>>>> When I had similar problems it was sometimes because of
>>>> permission-problems when talking to some service over the dbus. Check
>>>> your ~/.xsession-errors for "dbus-send...." errors.
>>>>
>>>> Just a wild guess

>>>> Daniel
>>>>
>>> It hasn't done it in the last few reboots, but I have nopasted it:
>>> http://dpaste.com/154084/ to see if you might find any problems
>>>
>>>
>>
>> Please don't use short-lived URL shorteners here. This list is archived and
>> after a time your posted info goes away and cannot help any future user.
>>
>> The post was very small anyway and it's perfectly acceptable to insert it in-
>> line.
>>
>>
> No worries Alan. Here are the full details of that config file.
>
> /etc/X11/gdm/Xsession: Beginning session setup...
> which: no keychain in
> (/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.3.4:/usr/lib64/subversion/bin:/usr/games/bin)
> /etc/X11/gdm/Xsession: Setup done, will execute: gnome-session
> GNOME_KEYRING_SOCKET=/tmp/keyring-OaCPoA/socket
> SSH_AUTH_SOCK=/tmp/keyring-OaCPoA/socket.ssh
> shm_open() failed: Permission denied
> Window manager warning: Failed to read saved session file
> /home/ubiquitous1980/.config/metacity/sessions/10f50da8e07be8ee31126518933845497800000046660017.m s:
> Failed to open file
> '/home/ubiquitous1980/.config/metacity/sessions/10f50da8e07be8ee31126518933845497800000046660017.m s':
> No such file or directory
>
> (gnome-settings-daemon:4705): GLib-GObject-CRITICAL **:
> g_param_spec_flags: assertion `G_TYPE_IS_FLAGS (flags_type)' failed
>
> (gnome-settings-daemon:4705): GLib-GObject-CRITICAL **:
> g_object_class_install_property: assertion `G_IS_PARAM_SPEC (pspec)' failed
> ** Message: NumLock remembering disabled because hostname is set to
> "localhost"
> shm_open() failed: Permission denied
> shm_open() failed: Permission denied
> shm_open() failed: Permission denied
> shm_open() failed: Permission denied
> ** (gnome-volume-control-applet:4822): DEBUG: Disabling debugging
> shm_open() failed: Permission denied
> shm_open() failed: Permission denied
> shm_open() failed: Permission denied
> Failure: Module initalization failed
>
> ** (nm-applet:4811): WARNING **: <WARN> request_name(): Could not
> acquire the session service as it is already taken. Return: 3
>
>
> ** (nm-applet:4811): WARNING **: <WARN> constructor(): Couldn't
> initialize the D-Bus manager.
>
> ** Message: Initializing gksu extension...
>
> (gnome-panel:4771): Gtk-WARNING **: gtk_widget_size_allocate(): attempt
> to allocate widget with width -9 and height 24
> Unable to open desktop file epiphany.desktop for panel launcher
> Unable to open desktop file evolution.desktop for panel launcher
>
> ** (nautilus:4792): WARNING **: Unable to add monitor: Not supported
>
> ** (nautilus:4792): WARNING **: Unable to add monitor: Not supported
> error: option --qt not a unique prefix
>
> HP Linux Imaging and Printing System (ver. 2.8.6b)
> System Tray Status Service ver. 0.1
>
> Copyright (c) 2001-8 Hewlett-Packard Development Company, LP
> This software comes with ABSOLUTELY NO WARRANTY.
> This is free software, and you are welcome to distribute it
> under certain conditions. See COPYING file for more details.
>
>
>
> Usage: hp-systray [OPTIONS]
>
> [OPTIONS]
> Force Qt3: --qt3 (default)
> Force Qt4: --qt4
> Startup even if no -x or --force-startup
> hplip CUPS queues
> are present:
> Set the logging -l<level> or --logging=<level>
> level:
> <level>: none, info*, error, warn, debug (*default)
> Run in debug mode: -g (same as option: -ldebug)
> This help -h or --help
> information:
>
>
>
> ** (gnome-settings-daemon:4705): WARNING **: No screensaver available
> No running windows found
> Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message
> with a timestamp of 0 for 0x2200045 (Mozilla Fi)
> Window manager warning: meta_window_activate called by a pager with a 0
> timestamp; the pager needs to be fixed.
> Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message
> with a timestamp of 0 for 0x2200045 (Mozilla Fi)
> Window manager warning: meta_window_activate called by a pager with a 0
> timestamp; the pager needs to be fixed.
>>> It hasn't done it in the last few reboots, but I have nopasted it:
Well - this look OK. But if there hasn't been any error, I didn't expect
to find anything

Post this again directly after the problem occurs.
Bye,
Daniel
--
PGP key @ http://pgpkeys.pca.dfn.de/pks/lookup?search=0xBB9D4887&op=get
# gpg --recv-keys --keyserver hkp://subkeys.pgp.net 0xBB9D4887