GNOME_VFS_Daemon_getVolumes hangs [was: nautilus hangs]



Hello,

No, I'm not using hal for gnome-vfs.

However, I saw the problem is not tied to nautilus, but happens on any
opening of a file-chooser dialog box.
In fact, everything which seems to use the GNOME_VFS_Daemon_getVolumes
component.
That's why I post it now on the gnome-vfs-list.

Maybe should I open a bugreport ?



Sylvain

Le mercredi 25 août 2004 à 19:34 +0200, Christophe Fergeau a écrit :
> Hi,
> 
> Are you using a gnome-vfs version with hal support enabled (--enable-hal
> passed to configure)?
> 
> Christophe
> 
> Le mercredi 25 août 2004 à 02:10 +0200, Sylvain Pasche a écrit :
> > Hello,
> > 
> > I get some hangs sometimes from nautilus (version HEAD as of 8.25):
> > 
> > #0  0xffffe410 in __kernel_vsyscall ()
> > #1  0x4047428e in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
> > #2  0x40b0b404 in link_wait () at linc.c:488
> > #3  0x40b0c2c8 in link_connection_try_reconnect (cnx=0x81be7d0) at linc-connection.c:585
> > #4  0x40ae23f5 in giop_connection_try_reconnect (cnx=0x81be7d0) at giop-connection.c:192
> > #5  0x40aed74d in ORBit_try_connection_T (obj=0x81be4b8) at corba-object.c:271
> > #6  0x40aed8df in ORBit_object_get_connection (obj=0x81be4b8) at corba-object.c:314
> > #7  0x40aeb039 in ORBit_small_invoke_stub (obj=0x81be4b8, m_data=0x40aad720, ret=0xbfffece0, args=0xbfffecdc, ctx=0x0, ev=0xbfffed10) at orbit-small.c:631
> > #8  0x40aeaf20 in ORBit_small_invoke_stub_n (object=0x81be4b8, methods=0x40aad824, index=4, ret=0xbfffece0, args=0xbfffecdc, ctx=0x0, ev=0xbfffed10) at orbit-small.c:575
> > #9  0x40b03895 in ORBit_c_stub_invoke (obj=0x81be4b8, methods=0x40aad824, method_index=4, ret=0xbfffece0, args=0xbfffecdc, ctx=0x0, ev=0xbfffed10, class_id=0, 
> >     method_offset=20, skel_impl=0x40a5bdd2 <_ORBIT_skel_small_GNOME_VFS_Daemon_getVolumes>) at poa.c:2640
> > #10 0x40a5cf95 in GNOME_VFS_Daemon_getVolumes (_obj=0x81be4b8, client=0x81bea18, ev=0xbfffed10) at GNOME_VFS_Daemon-stubs.c:449
> > #11 0x40a946cb in read_volumes_from_daemon (volume_monitor_client=0x81be940) at gnome-vfs-volume-monitor-client.c:157
> > #12 0x40a94795 in gnome_vfs_volume_monitor_client_init (volume_monitor_client=0x81be940) at gnome-vfs-volume-monitor-client.c:182
> > #13 0x4098bf8b in g_type_create_instance (type=135491784) at gtype.c:1595
> > #14 0x40972902 in g_object_constructor (type=135491784, n_construct_properties=0, construct_params=0x0) at gobject.c:1044
> > #15 0x4097226d in g_object_newv (object_type=135491784, n_parameters=0, parameters=0x0) at gobject.c:941
> > #16 0x409724d8 in g_object_new_valist (object_type=135491784, first_property_name=0x0, var_args=0xbfffef58 "\b�\033\b\b�\033\b\004\v� 4�@x���\fP� \001")
> >     at gobject.c:984
> > #17 0x40971d2f in g_object_new (object_type=135491784, first_property_name=0x0) at gobject.c:822
> > #18 0x40a94f87 in _gnome_vfs_get_volume_monitor_internal (create=1) at gnome-vfs-volume-monitor.c:243
> > #19 0x40a9500c in gnome_vfs_get_volume_monitor () at gnome-vfs-volume-monitor.c:264
> > #20 0x0806981a in nautilus_application_instance_init (application=0x81bec18) at nautilus-application.c:183
> > #21 0x4098bf8b in g_type_create_instance (type=136046488) at gtype.c:1595
> > #22 0x40972902 in g_object_constructor (type=136046488, n_construct_properties=1, construct_params=0x81c2b58) at gobject.c:1044
> > #23 0x409cb332 in bonobo_object_constructor (type=136046488, n_construct_properties=1, construct_properties=0x81c2b58) at bonobo-object.c:819
> > #24 0x4097226d in g_object_newv (object_type=136046488, n_parameters=0, parameters=0x0) at gobject.c:941
> > #25 0x409724d8 in g_object_new_valist (object_type=136046488, first_property_name=0x0, var_args=0xbffff1b8 "9") at gobject.c:984
> > #26 0x40971d2f in g_object_new (object_type=136046488, first_property_name=0x0) at gobject.c:822
> > #27 0x08069947 in nautilus_application_new () at nautilus-application.c:202
> > #28 0x0807897e in main (argc=1, argv=0xbffff414) at nautilus-main.c:323
> > 
> > I saw several nautilus hangs some times ago, but none of which seems to be related to this backtrace. Nor did
> > gnome bugzilla returned a bug containing such a trace.
> > 
> > What I find curious is that nautilus does not seem to exec the bonobo server "gnome-vfs-daemon" when it hangs in 
> > such a way. I tested the server was not running, and compared the access time to see it.
> > 
> > Any hints about this ?
> > 
> > Cheers,
> > 
> > Sylvain
> > 
> > 




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]