Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[GNOME] Problème de lancement
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index French
View previous topic :: View next topic  
Author Message
floc_12
Apprentice
Apprentice


Joined: 28 Jun 2006
Posts: 191

PostPosted: Wed Jul 14, 2010 9:47 pm    Post subject: [GNOME] Problème de lancement Reply with quote

Bonjour,

Suite à l'installation de gnome, je rencontre des problèmes lors de son lancement. Gnome démarre ave difficulté, et lorsqu'il apparait, la barre de menu aparait 1 fois sur deux, et le menu application est vide.

Pendant son execution, si je regarde dans la console de lancement, le message ci-dessous apparait en boucle :

xauth: creating new authority file /root/.serverauth.4206


Quote:
X.Org X Server 1.7.6
Release Date: 2010-03-17
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.33-gentoo-r2 x86_64
Current Operating System: Linux thess 2.6.33-gentoo-r2 #4 SMP Sun Jul 11 21:47:16 CEST 2010 x86_64
Kernel command line: root=/dev/sda6
Build Date: 12 July 2010 08:34:37PM

Current version of pixman: 0.18.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul 14 22:01:45 2010
(==) Using config file: "/etc/X11/xorg.conf"
(II) [KMS] Kernel modesetting enabled.

** (gnome-keyring-daemon:4238): WARNING **: couldn't read 4 bytes from gnome-keyring socket: Connexion r�-initialis�e par le correspondant

** (gnome-keyring-daemon:4238): WARNING **: couldn't initialize running daemon
GNOME_KEYRING_SOCKET=/tmp/keyring-8wVxT6/socket
SSH_AUTH_SOCK=/tmp/keyring-8wVxT6/socket.ssh
GNOME_KEYRING_PID=4241

(gnome-settings-daemon:4242): GLib-GObject-CRITICAL **: g_param_spec_flags: assertion `G_TYPE_IS_FLAGS (flags_type)' failed

(gnome-settings-daemon:4242): GLib-GObject-CRITICAL **: g_object_class_install_property: assertion `G_IS_PARAM_SPEC (pspec)' failed
Avertissement du gestionnaire de fen�tres�: La lecture du fichier de session enregistr� /root/.config/metacity/sessions/106b8712676069938127913770680311100000042270013.ms a �chou��: L'ouverture du fichier ��/root/.config/metacity/sessions/106b8712676069938127913770680311100000042270013.ms�� a �chou��: Aucun fichier ou dossier de ce type

(gnome-panel:4271): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorGdu: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

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

(polkit-gnome-authentication-agent-1:4284): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

(gnome-panel:4271): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.35 for volume monitor org.gtk.Private.GduVolumeMonitor connected to the bus; seeding drives/volumes/mounts

(gnome-panel:4271): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorGdu: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

(nautilus:4272): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorGdu: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

(gnome-panel:4271): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.39 for volume monitor org.gtk.Private.GduVolumeMonitor connected to the bus; seeding drives/volumes/mounts

(gnome-panel:4271): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorGdu: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

(gnome-panel:4271): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.41 for volume monitor org.gtk.Private.GduVolumeMonitor connected to the bus; seeding drives/volumes/mounts

(gnome-panel:4271): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorGdu: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

(gnome-panel:4271): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.43 for volume monitor org.gtk.Private.GduVolumeMonitor connected to the bus; seeding drives/volumes/mounts
Initializing nautilus-gdu extension
** Message: Initializing gksu extension...

(nautilus:4272): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.41 for volume monitor org.gtk.Private.GduVolumeMonitor connected to the bus; seeding drives/volumes/mounts

(gnome-panel:4271): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorGdu: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

(gnome-panel:4271): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.45 for volume monitor org.gtk.Private.GduVolumeMonitor connected to the bus; seeding drives/volumes/mounts

(nautilus:4272): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorGdu: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

(nautilus:4272): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.43 for volume monitor org.gtk.Private.GduVolumeMonitor connected to the bus; seeding drives/volumes/mounts


D'après google, Dbus serait dans le coup. J'ai essayer de changer de version de gnom, de dbus, de supprimer gnome-panel, mais le problème est toujours présent.

Quelqu'un aurait il deja rencontré ce problème, car il n'y a pas de solution sur le net (bug connu apparemment).

Merci
Back to top
View user's profile Send private message
pulsar
n00b
n00b


Joined: 08 Nov 2009
Posts: 11

PostPosted: Fri Jul 16, 2010 9:30 am    Post subject: Reply with quote

Slut FLo,

j´ai exactement le meme Pb depuis 3 semaines ....j´aimerai savoir si tu as deja une solution ...

Merc!
Back to top
View user's profile Send private message
pulsar
n00b
n00b


Joined: 08 Nov 2009
Posts: 11

PostPosted: Fri Jul 16, 2010 9:43 am    Post subject: Reply with quote

je viens de trouver une solution prometteuse
Quote:

emerge -C devicekit-disks



devicekit-disks est une dependance du packet
Quote:
gnome-disk-utility
version 2.28
Back to top
View user's profile Send private message
floc_12
Apprentice
Apprentice


Joined: 28 Jun 2006
Posts: 191

PostPosted: Fri Jul 16, 2010 11:14 am    Post subject: Reply with quote

Salut pulsar,

Je n'ai malheureusement pas encore trouvé de solutions à ce problème. J'ai répondu à un post anglais si ca t'intéresse, ils proposent de downgrader dbus. J'ai testé, mais ca ne fait rien :

https://forums.gentoo.org/viewtopic-p-6351932.html#6351932

Sinon, je teste ta solution et te tiens au courant. Ca a fonctionné chez toi ?

A++
Back to top
View user's profile Send private message
netfab
Veteran
Veteran


Joined: 03 Mar 2005
Posts: 1685
Location: 127.0.0.1

PostPosted: Fri Jul 16, 2010 3:05 pm    Post subject: Reply with quote

Quote:

Avertissement du gestionnaire de fen�tres�: La lecture du fichier de session enregistr� /root/.config/metacity/sessions/

Pourquoi lancer gnome en root ?
Sinon, sur ton système tu as peut-être de vieux fichiers de configuration dbus/gconf/autres qui entrent en conflit. Regarde ici par exemple. Je cite :
Quote:

I got tired of this problem so I uninstalled almost all packages,
manually removed all remaining dbus/gconf/... files that I found
on the machine, reinstalled everything back, and now I don't have
this problem anymore.

Et vu que les messages d'erreurs du départ ressemblent fortement aux tiens...
Back to top
View user's profile Send private message
floc_12
Apprentice
Apprentice


Joined: 28 Jun 2006
Posts: 191

PostPosted: Fri Jul 16, 2010 4:49 pm    Post subject: Reply with quote

Bonjour,

J'ai lancé la commande de Pulsar, et gnome démarre, mais mon menu application est vide.

Dans ma console de lancement, je n'ai plus le essage qui tourne en boucle, en revanche, j'ai cela :

Quote:
(gnome-settings-daemon:4658): GLib-GObject-CRITICAL **: g_param_spec_flags: assertion `G_TYPE_IS_FLAGS (flags_type)' failed

(gnome-settings-daemon:4658): GLib-GObject-CRITICAL **: g_object_class_install_property: assertion `G_IS_PARAM_SPEC (pspec)' failed
Avertissement du gestionnaire de fen�tres�: La lecture du fichier de session enregistr� /home/ced/.config/metacity/sessions/1046dfad104fbfcfb2127929642199252800000046440014.ms a �chou��: L'ouverture du fichier ��/home/ced/.config/metacity/sessions/1046dfad104fbfcfb2127929642199252800000046440014.ms�� a �chou��: Aucun fichier ou dossier de ce type

(gnome-panel:4689): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/libexec/gvfs-gdu-volume-monitor received signal 11

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

(polkit-gnome-authentication-agent-1:4704): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

(gdu-notification-daemon:4705): libgdu-WARNING **: Couldn't get daemon properties

(gdu-notification-daemon:4705): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(gdu-notification-daemon:4705): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(gdu-notification-daemon:4705): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(gdu-notification-daemon:4705): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(gdu-notification-daemon:4705): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(gdu-notification-daemon:4705): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(gdu-notification-daemon:4705): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(gdu-notification-daemon:4705): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(nautilus:4690): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/libexec/gvfs-gdu-volume-monitor received signal 11
Initializing nautilus-gdu extension
** Message: Initializing gksu extension...



netfab, pour le root, c'était pour avoir les messages d'erreurs via ssh et les copier sur le forum (je vais sur internet avec mon 2ieme pc).
Pour les vieux fichiers de conf, je ne pense pas. Mon install est toute fraiche, et j'avais deja essayer d'installer dbus. Je viens d'essayer gconf, mais pareil

Merci a tous les 2
Back to top
View user's profile Send private message
netfab
Veteran
Veteran


Joined: 03 Mar 2005
Posts: 1685
Location: 127.0.0.1

PostPosted: Fri Jul 16, 2010 5:06 pm    Post subject: Reply with quote

Pour le menu applications regarde ici à propos de la variable d'environnement XDG_MENU_PREFIX.
Back to top
View user's profile Send private message
floc_12
Apprentice
Apprentice


Joined: 28 Jun 2006
Posts: 191

PostPosted: Fri Jul 16, 2010 6:07 pm    Post subject: Reply with quote

Merci,

C'est ok pour le menu application en rajoutant une ligne dans le .xinitrc. Ce n'était pas grand chose.
Je suis en train de faire des recherches sur mes warnings et erreurs de la session (enfin, entre la cuisson de 2 crêpes, miam, lol ...).

Je vous tiens au courant de l'avancement
Back to top
View user's profile Send private message
pulsar
n00b
n00b


Joined: 08 Nov 2009
Posts: 11

PostPosted: Fri Jul 16, 2010 7:59 pm    Post subject: Reply with quote

En ce qui concerne le menu "Application" ..j´ai eu le meme problem apres avoir desinstalle devicekit-disks
mais actuellement tout marche pour le mieux ...(apres quelque revdep..., )

voici quelques informations importantes pour gnome 2.28


http://www.gentoo.org/proj/en/desktop/gnome/howtos/gnome-2.28-upgrade.xml

Tenez moi au courrant si vous avez pu supprimer un warning
Back to top
View user's profile Send private message
anigel
Bodhisattva
Bodhisattva


Joined: 14 Apr 2003
Posts: 1889
Location: Un petit bled pas loin de Limoges ;-)

PostPosted: Fri Jul 16, 2010 8:55 pm    Post subject: Reply with quote

Bonsoir,

Sur un système de test fraîchement compilé il y a 10 jours, j'ai rencontré ce souci également. Je n'ai trouvé qu'un seul moyen de le régler (ok, j'ai pas trop cherché non plus :lol:) : supprimer le paquet cité plus haut. On arrive au même résultat en désactivant le flag "gdu" du paquet gnome-vfs. Or ce flag est requis par gnome-base/gnome-light ou gnome-base/gnome pour permettre l'automontage des périphériques.

La solution propre : désactiver à la fois le flag gdu et le flag automount. Problème : dans ce cas quand on insère une clef USB il ne se passe plus rien.

A noter que le problème ne touche pas uniquement Gentoo visiblement : j'ai vu des messages concernant ce souci sur des forums d'autres distribs.
_________________
Il y a 10 sortes d'individus en ce bas-monde : ceux qui causent binaire, et les autres.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index French All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum