Gnome 3 - new users have no panel [Solved]

Compiz, KDE, Gnome, Fluxbox, etc...

Moderator: Moderators

Gnome 3 - new users have no panel [Solved]

Postby anakonda » Sat Oct 29, 2011 3:24

Hello, I returned recently Sabayon and after a fresh-install I encountered this issue:
after adding new users to my machine, only the 1st user have got full Desktop Environment while other users, after loggin in, haves no Gnome Panel on the top but only Desktop with icons and right menu working.

This is the .xsession-errors file from the 2nd user been created:
Code: Select all
/etc/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.5.2:/usr/games/bin)
/etc/gdm/Xsession: Setup done, will execute: /usr/bin/dbus-launch --exit-with-session /usr/bin/ssh-agent -- gnome-session
gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
GNOME_KEYRING_CONTROL=/tmp/keyring-1zOWfx
GNOME_KEYRING_CONTROL=/tmp/keyring-1zOWfx
GNOME_KEYRING_CONTROL=/tmp/keyring-1zOWfx
SSH_AUTH_SOCK=/tmp/keyring-1zOWfx/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-1zOWfx
SSH_AUTH_SOCK=/tmp/keyring-1zOWfx/ssh
GPG_AGENT_INFO=/tmp/keyring-1zOWfx/gpg:0:1

(gnome-settings-daemon:7899): power-plugin-WARNING **: Failed set DPMS mode: Could not set DPMS timeouts

(gnome-settings-daemon:7899): color-plugin-WARNING **: failed to get edid: unable to get EDID for output
NVIDIA: could not open the device file /dev/nvidiactl (Permesso negato).
NVIDIA: could not open the device file /dev/nvidiactl (Permesso negato).
Initializing nautilus-open-terminal extension

(gnome-shell:7927): Bluetooth-WARNING **: Could not open RFKILL control device, please verify your installation
      JS LOG: GNOME Shell started at Fri Oct 28 2011 22:28:45 GMT+0200 (CEST)
gnome-shell-calendar-server[7949]: Got HUP on stdin - exiting

(nautilus:7941): Liboobs-WARNING **: There was an unknown error communicating asynchronously with the backends: Rejected send message, 3 matched rules; type="method_call", sender=":1.109" (uid=1001 pid=7941 comm="nautilus -n ") interface="org.freedesktop.SystemToolsBackends" member="get" error name="(unset)" requested_reply="0" destination="org.freedesktop.SystemToolsBackends" (uid=0 pid=7164 comm="/usr/sbin/system-tools-backends -D ")
gnome-session[7870]: WARNING: Application 'gnome-shell.desktop' killed by signal

(nautilus:7941): Liboobs-WARNING **: There was an unknown error communicating asynchronously with the backends: Rejected send message, 3 matched rules; type="method_call", sender=":1.109" (uid=1001 pid=7941 comm="nautilus -n ") interface="org.freedesktop.SystemToolsBackends" member="get" error name="(unset)" requested_reply="0" destination="org.freedesktop.SystemToolsBackends" (uid=0 pid=7164 comm="/usr/sbin/system-tools-backends -D ")

** (nautilus:7941): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS

** (nautilus:7941): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS

** (nautilus:7941): WARNING **: Can not get _NET_WORKAREA

** (nautilus:7941): WARNING **: Can not determine workarea, guessing at layout
NVIDIA: could not open the device file /dev/nvidiactl (Permesso negato).
NVIDIA: could not open the device file /dev/nvidiactl (Permesso negato).

(gnome-shell:7966): Bluetooth-WARNING **: Could not open RFKILL control device, please verify your installation
      JS LOG: GNOME Shell started at Fri Oct 28 2011 22:28:51 GMT+0200 (CEST)

(gnome-settings-daemon:7899): power-plugin-WARNING **: failed to turn the panel on: Could not set DPMS timeouts
gnome-shell-calendar-server[7975]: Got HUP on stdin - exiting
gnome-session[7870]: WARNING: Application 'gnome-shell.desktop' killed by signal
Failed to connect to the VirtualBox kernel service
Failed to connect to the VirtualBox kernel service
Failed to connect to the VirtualBox kernel service
Failed to connect to the VirtualBox kernel service
Failed to play sound: File or data not found
** Message: applet now removed from the notification area

(nm-applet:7987): libnotify-WARNING **: Failed to connect to proxy
ERROR:dbus.proxies:Introspect error on :1.123:/notifier: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.122" (uid=1001 pid=7991 comm="/usr/bin/python2.7 /usr/lib/entropy/magneto/magnet") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply="0" destination=":1.123" (uid=0 pid=8111 comm="/usr/bin/python2 -O /usr/libexec/entropy-updates-s")
Traceback (most recent call last):
  File "/usr/lib/entropy/magneto/magneto.py", line 90, in <module>
    _startup()
  File "/usr/lib/entropy/magneto/magneto.py", line 64, in _startup
    magneto.startup()
  File "/usr/lib/entropy/magneto/magneto/gtk/interfaces.py", line 103, in startup
    self.__send_keepalive()
  File "/usr/lib/entropy/magneto/magneto/gtk/interfaces.py", line 119, in __send_keepalive
    self.send_keepalive()
  File "/usr/lib/entropy/magneto/magneto/core/interfaces.py", line 307, in send_keepalive
    iface.client_ping()
  File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 143, in __call__
    **keywords)
  File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 630, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.122" (uid=1001 pid=7991 comm="/usr/bin/python2.7 /usr/lib/entropy/magneto/magnet") interface="org.entropy.Client" member="client_ping" error name="(unset)" requested_reply="0" destination=":1.123" (uid=0 pid=8111 comm="/usr/bin/python2 -O /usr/libexec/entropy-updates-s")

(gnome-settings-daemon:7899): power-plugin-WARNING **: failed to turn the panel on: Could not set DPMS timeouts
** (deja-dup-monitor:7994): DEBUG: monitor.vala:263: Invalid next run date.  Not scheduling a backup.

(gnome-settings-daemon:7899): power-plugin-WARNING **: failed to turn the panel on: Could not set DPMS timeouts

(gnome-settings-daemon:7899): power-plugin-WARNING **: failed to turn the panel on: Could not set DPMS timeouts

(gnome-settings-daemon:7899): power-plugin-WARNING **: failed to turn the panel on: Could not set DPMS timeouts

(gnome-settings-daemon:7899): power-plugin-WARNING **: failed to turn the panel on: Could not set DPMS timeouts

(gnome-settings-daemon:7899): power-plugin-WARNING **: failed to turn the panel on: Could not set DPMS timeouts

(gnome-settings-daemon:7899): power-plugin-WARNING **: failed to turn the panel on: Could not set DPMS timeouts

(gnome-settings-daemon:7899): power-plugin-WARNING **: failed to turn the panel on: Could not set DPMS timeouts

(gnome-settings-daemon:7899): power-plugin-WARNING **: failed to turn the panel off: Could not change DPMS mode

(evolution-alarm-notify:7986): evolution-alarm-notify-WARNING **: alarm.c:260: Requested removal of nonexistent alarm!

(gnome-settings-daemon:7899): power-plugin-WARNING **: failed to turn the panel on: Could not set DPMS timeouts

(gnome-terminal:7985): GLib-WARNING **: Failed to read from child watch wake up pipe: Chiamata di sistema interrotta

(gnome-settings-daemon:7899): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
gnome-session[7870]: GLib-WARNING: Failed to read from child watch wake up pipe: Chiamata di sistema interrotta

(gdu-notification-daemon:7992): Gdk-WARNING **: gdu-notification-daemon: Fatal IO error 11 (Risorsa temporaneamente non disponibile) on X server :0.


(nm-applet:7987): Gdk-WARNING **: nm-applet: Fatal IO error 11 (Risorsa temporaneamente non disponibile) on X server :0.


(evolution-alarm-notify:7986): Gdk-WARNING **: evolution-alarm-notify: Fatal IO error 11 (Risorsa temporaneamente non disponibile) on X server :0.


(gnome-screensaver:7996): Gdk-WARNING **: gnome-screensaver: Fatal IO error 11 (Risorsa temporaneamente non disponibile) on X server :0.


(nautilus:7941): Gdk-WARNING **: nautilus: Fatal IO error 0 (Successo) on X server :0.
Last edited by anakonda on Sun Oct 30, 2011 20:44, edited 1 time in total.
anakonda
Baby Hen
 
Posts: 6
Joined: Mon Jun 21, 2010 0:42

Re: Gnome 3 - new users have no panel

Postby anakonda » Sun Oct 30, 2011 20:43

Hello I have understand what is happened to my system.
I created new users through /usr/bin/perl /usr/share/system-tools-backends-2.0/scripts/SystemToolsBackends.pl -m UsersConfig but users created with this one tool have no privileges so gnome-shell don't load at startup.
Editing the users through this will let you set them correct privileges: /usr/bin/perl /usr/share/system-tools-backends-2.0/scripts/SystemToolsBackends.pl -m GroupsConfig

I hope this can help someone in future
anakonda
Baby Hen
 
Posts: 6
Joined: Mon Jun 21, 2010 0:42

Re: Gnome 3 - new users have no panel

Postby huwie » Sat Nov 12, 2011 23:37

anakonda wrote:I hope this can help someone in future


It did help. Although your solution didn't work for me (bash did nothing after entering your command) it did point me in the right direction. I was having precisely the same problem, so I used the add users dialogue and edited my second user's groups. I just added her to a few groups like audio devices, USB devices etc and somehow that did the trick.

Thank you!
huwie
Young Hen
 
Posts: 31
Joined: Sun Jan 16, 2011 21:47


Return to 3D Desktops and Window Managers

Who is online

Users browsing this forum: No registered users and 1 guest