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 366143 - crash in CD/DVD Creator: Had just connected to a ...
crash in CD/DVD Creator: Had just connected to a ...
Status: RESOLVED DUPLICATE of bug 366025
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-28 07:54 UTC by mbt
Modified: 2006-10-31 17:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description mbt 2006-10-28 07:54:25 UTC 
What were you doing when the application crashed?
Had just connected to a Windows Share.

A shortcut (for want of the correct linux term!) was on the desktop from an earlier connection to the Windows box.
I had created it via Go -> Connect to Server (or whatever the correct menu item is). 
I selected smb and entered the details.

Anyway, I had just typed my password after clicking on this link. The files were displayed and the bug report tool popped up.


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

Memory status: size: 85180416 vsize: 0 resident: 85180416 share: 0 rss: 30629888 rss_rlim: 0
CPU usage: start_time: 1162019575 rtime: 0 utime: 536 stime: 0 cutime:492 cstime: 0 timeout: 44 it_real_value: 0 frequency: 2347

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 -1226950992 (LWP 4625)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 79153

Thread 1 (Thread -1226950992 (LWP 4625))

  • #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 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #5 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #7 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 POA_Nautilus_MetafileMonitor__init
  • #9 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #10 ??
  • #0 __kernel_vsyscall 






Comment 1


Behdad Esfahbod





          2006-10-31 17:55:40 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
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.


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