2010/3/5 Josselin Mouette: > * which process is going in a loop? > * what is it doing then (a gdb backtrace would be nice)? > * what is happening on the system bus at that time?
I don't know how exactly reply to your question. I try. Note: I don't have loop anytime I execute a command, I report here only bad case $ gnome-screenshot (gnome-screenshot:25861): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorGdu: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) $ gdb gnome-screenshot (gdb) run [error list] Ctrl-c ... dbus stop ... (gdb) bt Cannot access memory at address 0xbfffea80 (gdb) run The program being debugged has been started already. Start it from the beginning? (y or n) y Starting program: /usr/bin/gnome-screenshot [Thread debugging using libthread_db enabled] [New Thread 0xb6e89b70 (LWP 28503)] (gnome-screenshot:28502): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorGdu: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) [New Thread 0xb5551b70 (LWP 28512)] (gnome-screenshot:28502): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.6489 for volume monitor org.gtk.Private.GduVolumeMonitor connected to the bus; seeding drives/volumes/mounts (gnome-screenshot:28502): 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-screenshot:28502): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.6491 for volume monitor org.gtk.Private.GduVolumeMonitor connected to the bus; seeding drives/volumes/mounts [...] Ctrl-c Please let me know how to give you information you need. I don't know dbus. Ciao Davide -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
