Bug 474067 – crash in CD/DVD Creator: trying to access remote ...

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 474067 - crash in CD/DVD Creator: trying to access remote ...


Summary:	crash in CD/DVD Creator: trying to access remote ...


Status:	RESOLVED DUPLICATE of bug 358172

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

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-09-05 23:47 UTC by david.bourget
Modified:	2007-09-06 12:22 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description david.bourget 2007-09-05 23:47:07 UTC

What were you doing when the application crashed?
trying to access remote directory through sftp, but while offline. clicked on link under "places" in file browser. 


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 96382976 vsize: 0 resident: 96382976 share: 0 rss: 22630400 rss_rlim: 0
CPU usage: start_time: 1186197991 rtime: 0 utime: 4835 stime: 0 cutime:4583 cstime: 0 timeout: 252 it_real_value: 0 frequency: 194

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226770752 (LWP 4717)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 160754

Thread 1 (Thread -1226770752 (LWP 4717))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 nautilus_file_is_directory
#11 nautilus_file_is_directory
#12 nautilus_file_get_uri
#13 nautilus_directory_async_state_changed
#14 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#15 ??
#16 ??
#17 ??
#18 ??
from /usr/lib/libgthread-2.0.so.0
#19 ??
#20 ??
from /usr/lib/libglib-2.0.so.0
#21 ??
#22 g_slice_alloc
from /usr/lib/libglib-2.0.so.0
#23 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#24 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#25 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#26 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#27 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#28 POA_Nautilus_MetafileMonitor__init
#29 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#30 ??
#0 __kernel_vsyscall

Comment 1 palfrey 2007-09-06 12:22:48 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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