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 170910 - gnome-vfs-daemon segfault
gnome-vfs-daemon segfault
Status: RESOLVED OBSOLETE
Product: gnome-vfs
Classification: Deprecated
Component: File operations
cvs (head)
Other All
: Urgent critical
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
Depends on:
Blocks:
 
 
Reported: 2005-03-19 16:23 UTC by Simon Morgan
Modified: 2005-07-02 12:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10

Attachments
Patch to fix this bug (788 bytes, patch)
2005-03-22 08:34 UTC, Martin Pitt 		none Details | Review

Description Simon Morgan 2005-03-19 16:23:06 UTC 
Version details: 2.10.0-0ubuntu2
Distribution/Version: Ubuntu Hoary

Having just moved across an IDE NTFS formatted drive from another computer to
this machine and connected to the primary connector on the first IDE channel and
with the cable select jumper setting (Linux is installed on an SATA drive which
is the drive that I actually boot from) I booted up and noticed that my gnomevfs
samba folder had disappeared from my desktop. Checking dmesg I noticed the
following:

gnome-vfs-daemo[6074]: segfault at 0000000000000050 rip 0000002a957e1ba0 rsp
0000007fbffff218 error 4
gnome-vfs-daemo[6082]: segfault at 0000000000000050 rip 0000002a957e1ba0 rsp
0000007fbffff218 error 4
gnome-vfs-daemo[6086]: segfault at 0000000000000050 rip 0000002a957e1ba0 rsp
0000007fbffff218 error 4
gnome-vfs-daemo[6088]: segfault at 0000000000000050 rip 0000002a957e1ba0 rsp
0000007fbffff218 error 4
gnome-vfs-daemo[6095]: segfault at 0000000000000050 rip 0000002a957e1ba0 rsp
0000007fbffff218 error 4
gnome-vfs-daemo[6103]: segfault at 0000000000000050 rip 0000002a957e1ba0 rsp
0000007fbffff218 error 4
gnome-vfs-daemo[6114]: segfault at 0000000000000050 rip 0000002a957e1ba0 rsp
0000007fbffff218 error 4
gnome-vfs-daemo[6116]: segfault at 0000000000000050 rip 0000002a957e1ba0 rsp
0000007fbffff218 error 4
gnome-vfs-daemo[6118]: segfault at 0000000000000050 rip 0000002a957e1ba0 rsp
0000007fbffff218 error 4
gnome-vfs-daemo[6231]: segfault at 0000000000000050 rip 0000002a957e1ba0 rsp
0000007fbffff218 error 4
gnome-vfs-daemo[6269]: segfault at 0000000000000050 rip 0000002a957e1ba0 rsp
0000007fbffff218 error 4
gnome-vfs-daemo[6271]: segfault at 0000000000000050 rip 0000002a957e1ba0 rsp
0000007fbffff218 error 4
gnome-vfs-daemo[6273]: segfault at 0000000000000050 rip 0000002a957e1ba0 rsp
0000007fbffff218 error 4
gnome-vfs-daemo[6328]: segfault at 0000000000000050 rip 0000002a957e1ba0 rsp
0000007fbffff218 error 4
gnome-vfs-daemo[6336]: segfault at 0000000000000050 rip 0000002a957e1ba0 rsp
0000007fbffff218 error 4

Here's a backtrace:

(gdb) r
Starting program: /usr/lib/gnome-vfs2/gnome-vfs-daemon
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 182931822432 (LWP 6345)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
libhal.c 911 : Error sending msg: No property info.category on device with id
/org/freedesktop/Hal/devices/ide_0_0

Program received signal SIGSEGV, Segmentation fault.

+ Trace 57058

Thread 182931822432 (LWP 6345)

  • #0 hal_volume_get_fsusage
    from /usr/lib/libhal-storage.so.0
  • #1 hal_volume_policy_should_be_visible
    from /usr/lib/libhal-storage.so.0
  • #2 _gnome_vfs_hal_mounts_modify_drive
  • #3 gnome_vfs_volume_monitor_daemon_force_probe
  • #4 gnome_vfs_volume_monitor_daemon_get_type
  • #5 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #10 _gnome_vfs_get_volume_monitor_internal
    from /usr/lib/libgnomevfs-2.so.0
  • #11 gnome_vfs_get_volume_monitor
    from /usr/lib/libgnomevfs-2.so.0
  • #12 main 






Comment 1


Sebastien Bacher





          2005-03-19 17:03:55 UTC
        



could you get a backtrace with libgnomevfs2-0-dbg installed ?






Comment 2


Simon Morgan





          2005-03-19 17:10:09 UTC
        



(gdb) r
Starting program: /usr/lib/gnome-vfs2/gnome-vfs-daemon
[Thread debugging using libthread_db enabled]
[New Thread 182931822432 (LWP 6996)]
libhal.c 911 : Error sending msg: No property info.category on device with id
/org/freedesktop/Hal/devices/ide_0_0

Program received signal SIGSEGV, Segmentation fault.




+
Trace
    57060






Thread 182931822432
          (LWP 6996)


    

  • 
#0
hal_volume_get_fsusage

    
                from
                /usr/lib/libhal-storage.so.0

    

    • 

  • 
#1
hal_volume_policy_should_be_visible

    
                from
                /usr/lib/libhal-storage.so.0

    

    • 

  • 
#2
_gnome_vfs_hal_mounts_modify_drive

    • 

  • 
#3
gnome_vfs_volume_monitor_daemon_force_probe

    • 

  • 
#4
gnome_vfs_volume_monitor_daemon_get_type

    • 

  • 
#5
g_type_create_instance

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#6
g_object_new_valist

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#7
g_object_newv

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#8
g_object_new_valist

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#9
g_object_new

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#10
_gnome_vfs_get_volume_monitor_internal

    
                at gnome-vfs-volume-monitor.c
                  line
                  250

    

    • 

  • 
#11
gnome_vfs_get_volume_monitor

    
                at gnome-vfs-volume-monitor.c
                  line
                  277

    

    • 

  • 
#12
main

    • 













Comment 3


Martin Pitt





          2005-03-22 08:34:55 UTC
        



Created attachment 39057 [details] [review]
Patch to fix this bug

This patch was applied to the Ubuntu package, the submitter confirmed that it
fixes the segfault. It's also pretty obvious.






Comment 4


Christian Neumair





          2005-05-09 18:50:18 UTC
        



Thanks for your bug report!
This looks like a very sane addition, considering that hal_volume may actually
be NULL. I wonder whether libhal_drive_policy_compute_icon_name may receive NULL
as 2nd parameter. If not, we'd have to handle that case as well.






Comment 5


Christian Kellner





          2005-07-02 12:25:41 UTC
        



Hal code changed. Closing this one therefore.