Bug 171849 – gnome-vfs crashes in _gnome_vfs_drive_from_corba

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 171849 - gnome-vfs crashes in _gnome_vfs_drive_from_corba


Summary:	gnome-vfs crashes in _gnome_vfs_drive_from_corba


Status:	RESOLVED DUPLICATE of bug 148719

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other other

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2005-03-28 05:26 UTC by Andrew Turner
Modified:	2005-03-28 05:44 UTC

See Also:
GNOME target:	---
GNOME version:	2.9/2.10

Description Andrew Turner 2005-03-28 05:26:42 UTC

Distribution: Debian testing/unstable
Package: nautilus
Severity: normal
Version: GNOME2.10.0 2.10.1
Gnome-Distributor: JHBuild
Synopsis: gnome-vfs crashes in _gnome_vfs_drive_from_corba
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.10.1
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
gnome-vfs is crashing in _gnome_vfs_drive_from_corba

Steps to reproduce the crash:
1. Build Gnome 2.10 with jhbuild on Ubuntu
2. Run Gnome 2.10
3. 

Expected Results:
Gnome starts fine

How often does this happen?
Always

Additional Information:
I use jhbuild to build and run Gnome in Xnest.


Debugging Information:

Backtrace was generated from
'/home/andrew/building/gnome/build-cvs/bin/nautilus'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1090053504 (LWP 1240)]
[New Thread 1099463600 (LWP 1260)]
[Thread debugging using libthread_db enabled]
[New Thread 1090053504 (LWP 1240)]
[New Thread 1099463600 (LWP 1260)]
[Thread debugging using libthread_db enabled]
[New Thread 1090053504 (LWP 1240)]
[New Thread 1099463600 (LWP 1260)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 57407

Thread 1 (Thread 1090053504 (LWP 1240))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 741
#3 <signal handler called>
#4 _gnome_vfs_drive_from_corba
at gnome-vfs-drive.c line 598
#5 read_drives_from_daemon
at gnome-vfs-volume-monitor-client.c line 140
#6 gnome_vfs_volume_monitor_client_init
at gnome-vfs-volume-monitor-client.c line 198
#7 IA__g_type_create_instance
at gtype.c line 1596
#8 g_object_constructor
at gobject.c line 1045
#9 IA__g_object_newv
at gobject.c line 942
#10 IA__g_object_new_valist
at gobject.c line 985
#11 IA__g_object_new
at gobject.c line 823
#12 _gnome_vfs_get_volume_monitor_internal
at gnome-vfs-volume-monitor.c line 249
#13 gnome_vfs_get_volume_monitor
at gnome-vfs-volume-monitor.c line 276
#14 nautilus_application_instance_init
at nautilus-application.c line 166
#15 IA__g_type_create_instance
at gtype.c line 1596
#16 g_object_constructor
at gobject.c line 1045
#17 bonobo_object_constructor
at bonobo-object.c line 819
#18 IA__g_object_newv
at gobject.c line 942
#19 IA__g_object_new_valist
at gobject.c line 985
#20 IA__g_object_new
at gobject.c line 823
#21 nautilus_application_new
at nautilus-application.c line 194
#22 main
at nautilus-main.c line 422
#0 __kernel_vsyscall





------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-28 00:26 -------


Unknown version 2.10.1 in product nautilus.  Setting version to "unspecified".
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "nautilus".
   Setting to default milestone for this product, '---'
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Elijah Newren 2005-03-28 05:44:26 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 traces in bug 165127 and bug 170763, both of which have been
marked as a duplicate of 148719.

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