After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 151353 - calling gnome_vfs_get_volume_monitor() crashes
calling gnome_vfs_get_volume_monitor() crashes
Status: RESOLVED DUPLICATE of bug 148719
Product: gnome-vfs
Classification: Deprecated
Component: File operations
cvs (head)
Other Linux
: Urgent critical
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
Depends on:
Blocks:
 
 
Reported: 2004-08-29 17:13 UTC by alito
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8


Description alito 2004-08-29 17:13:43 UTC 
running test-volumes from the tests directory triggers it. all important
dependencies (glib, bonobo, ORBit) are cvs head from the 27/08/04. gcc 3.3.3,
glibc 2.3.2
i've marked it as urgent since every gnome app now crashes when opening the file
selector
bt of test-volumes

+ Trace 49731

  • #0 _gnome_vfs_drive_from_corba
    at gnome-vfs-drive.c line 595
  • #1 read_drives_from_daemon
    at gnome-vfs-volume-monitor-client.c line 128
  • #2 gnome_vfs_volume_monitor_client_init
    at gnome-vfs-volume-monitor-client.c line 181
  • #3 g_type_create_instance
    at gtype.c line 1595
  • #4 g_object_constructor
    at gobject.c line 1044
  • #5 g_object_newv
    at gobject.c line 941
  • #6 g_object_new_valist
    at gobject.c line 984
  • #7 g_object_new
    at gobject.c line 822
  • #8 _gnome_vfs_get_volume_monitor_internal
    at gnome-vfs-volume-monitor.c line 241
  • #9 gnome_vfs_get_volume_monitor
    at gnome-vfs-volume-monitor.c line 264
  • #10 main
    at test-volumes.c line 103 






Comment 1


Christophe Fergeau





          2004-08-29 17:26:19 UTC
        




*** This bug has been marked as a duplicate of 148719 ***






Comment 2


alito





          2004-08-29 17:36:51 UTC
        



correct assessment.  restarting gnome-vfs-daemon solved it
Thanks