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 169208 - Crashes with bind mounts
Crashes with bind mounts
Status: RESOLVED DUPLICATE of bug 160560
Product: system-monitor
Classification: Core
Component: general
2.8.x
Other Linux
: Normal normal
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2005-03-04 16:59 UTC by Javier Kohen
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description Javier Kohen 2005-03-04 16:59:51 UTC
Version details: 2.8.1
Distribution/Version: Debian/AMD64 gcc-3.4/4.0

I'm running Debian/AMD64 compiled with gcc-3.4/4.0 I have a chroot with three
bind mounts. One of them causes GSM to crash on startup. I don't know why, but
unmounting this particular one fixes the problem.

Here's the strace output that put me on track:
[pid  1611] stat("/var/chroot/sid-ia32/home", {st_mode=S_IFDIR|S_ISGID|0775,
st_size=4096, ...}) = 0
[pid  1611] --- SIGSEGV (Segmentation fault) @ 0 (0) ---

Here's my fstab:
proc            /proc           proc    defaults        0       0
/dev/hda2       /               ext2    defaults,errors=remount-ro 0       1
/dev/hda5       /home           ext3    defaults        0       2
/dev/hda6       none            swap    sw              0       0
/dev/hdc        /media/cdrom0   iso9660 ro,user,noauto  0       0
/dev/hda1       /c              ntfs    ro,noauto       0       0

# IA32 chroot
/home           /var/chroot/sid-ia32/home       none    bind    0       0
/tmp            /var/chroot/sid-ia32/tmp        none    bind    0       0
proc            /var/chroot/sid-ia32/proc       proc    defaults        0      0
sysfs           /var/chroot/sid-ia32/sys        sysfs   defaults        0      0

And the backtrace:
Program received signal SIGSEGV, Segmentation fault.
0x0000002a97613200 in gnome_vfs_volume_get_icon ()
   from /usr/lib/libgnomevfs-2.so.0
(gdb) bt
  • #0 gnome_vfs_volume_get_icon
    from /usr/lib/libgnomevfs-2.so.0
  • #1 cb_switch_page
  • #2 cb_switch_page
  • #3 g_hash_table_foreach
    from /usr/lib/libglib-2.0.so.0
  • #4 cb_update_disks
  • #5 get_sys_pane_pos
  • #6 create_main_window
  • #7 main


I tried three different themes (Simple, Glider and "default") and this is
reproducible with all of them. Someone else corroborated my results on the
Debian-AMD64 mailing list.
Comment 1 Elijah Newren 2005-03-04 17:03:29 UTC
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you find.

Matches the stack trace in bug 162711, which has been marked as a duplicate of
160560.

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