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

Re: Crash in GNOME System Monitor



Yep, you are right, after unmounting /chroot/home the GSM works great!

Thanks!

On Wed, 2005-02-16 at 18:35 -0500, Javier Kohen wrote:
> Sorry for the last empty message, I accidentally hit the Ctrl key as I 
> was pressing enter...
> 
> Yes!
> 
> I found it... from strace:
> [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) ---
> 
> So I guess a little unmounting will help...
> 
> Unmounting all binds under the chroot... and GSM is working again!
> 
> After a little more investigation proc, sysfs and /tmp (a bind mount) 
> don't break GSM, but /home does (another bind mount).
> 
> I just followed the Debian AMD64 instructions for the chroot mounts, so 
> I don't think I have to reproduce them here. As a temporary workaround 
> unmount your chroot's /home bind mount (or check if something similar is 
> causing the problem for you).
> 
> Could somebody with a working reportbug please send a report?
> 
> Andrei Mikhailovsky wrote:
> > same happens to me on pure64 ((
> > 
> > any ideas?
> > 
> > On Wed, 2005-02-16 at 14:07 -0500, Javier Kohen wrote:
> > 
> >>Since a very recent upgrade I found out that GSM won't start anymore. 
> >>I'm using the gcc-3.4 archive and I think the culprit could be either 
> >>libglade2-0-1:2.4.2-1 (I was using 2.4.1) or hicolor-icon-theme.
> >>
> >>The backtrace is:
> >>Program received signal SIGSEGV, Segmentation fault.
> >>0x0000002a97613200 in gnome_vfs_volume_get_icon ()
> >>    from /usr/lib/libgnomevfs-2.so.0
> >>(gdb) bt
> >>#0  0x0000002a97613200 in gnome_vfs_volume_get_icon ()
> >>    from /usr/lib/libgnomevfs-2.so.0
> >>#1  0x000000000040d542 in cb_switch_page ()
> >>#2  0x000000000040d64d in cb_switch_page ()
> >>#3  0x0000002a97f7e97d in g_hash_table_foreach ()
> >>    from /usr/lib/libglib-2.0.so.0
> >>#4  0x000000000040d956 in cb_update_disks ()
> >>#5  0x000000000040c32c in get_sys_pane_pos ()
> >>#6  0x000000000040c60c in create_main_window ()
> >>#7  0x000000000040ad89 in main ()
> >>
> >>Any ideas? I just tried changing GNOME's theme to the default (I was 
> >>using Glider), but it didn't help. Simple gives the same problem, so I 
> >>guess is not theme related (unless they all use the same icons and that 
> >>is somehow breaking GSM).
> >>
> >>Greetings,
> >>-- 
> >>Javier Kohen <jkohen@users.sourceforge.net>
> >>ICQ: blashyrkh #2361802
> >>Jabber: jkohen@jabber.org
> >>
> >>
> 
> 
> -- 
> Javier Kohen <jkohen@users.sourceforge.net>
> ICQ: blashyrkh #2361802
> Jabber: jkohen@jabber.org
> 
> 
-- 
Andrei Mikhailovsky
Arhont Ltd - Information Security

Web: http://www.arhont.com
     http://www.wi-foo.com
Tel: +44 (0)870 4431337
Fax: +44 (0)117 9690141
PGP: Key ID - 0xFF67A4F4
PGP: Server - keyserver.pgp.com

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: