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 526956 - crash in CD/DVD Creator: Hello. I just burn on my...
crash in CD/DVD Creator: Hello. I just burn on my...
Status: RESOLVED DUPLICATE of bug 355018
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-04-08 14:32 UTC by rataa
Modified: 2008-04-13 09:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description rataa 2008-04-08 14:32:59 UTC
What were you doing when the application crashed?
Hello. I just burn on my cd-rw .iso file and place program at 2nd workplace. After succesfull burning, application just "waiting" for me. On 1st workplace i use at this time nautilus for navigate some files  - directories, archives(tar.gz), shell-scripts. It's no 1st time crash of app CD/DVD burning, before this times i just clicked "Cancel" everyime because app crashed when i'm just open it and navigate on menu. Sorry for bad english :/ 


Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Xfce-4.2
Icon Theme: Wasp

Memory status: size: 82464768 vsize: 82464768 resident: 31137792 share: 16711680 rss: 31137792 rss_rlim: 4294967295
CPU usage: start_time: 1207663376 rtime: 1320 utime: 1242 stime: 78 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

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

Thread 1 (Thread 0xb6b8e720 (LWP 3456))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 strcmp
    from /lib/i686/cmov/libc.so.6
  • #7 g_str_equal
    from /usr/lib/libglib-2.0.so.0
  • #8 ??
    from /usr/lib/libeel-2-2.20.so
  • #9 ??
  • #10 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
(gecko:3703): Gdk-CRITICAL **: gdk_window_invalidate_rect: assertion `window != NULL' failed
FG: isPreferred(application/x-gzip,[object Object])
FG: _shouldIntercept(application/x-gzip)
FG: isPreferred(application/x-gzip,[object Object])
FG: _shouldIntercept(application/x-gzip)
FG: isPreferred(application/x-gzip,[object Object])
FG: _shouldIntercept(application/x-gzip)
FG: isPreferred(application/x-sh,[object Object])
FG: _shouldIntercept(application/x-sh)
Предупреждение менеджера окон: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x380001d (Менед)
Предупреждение менеджера окон: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Предупреждение менеджера окон: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x380001d (Менед)
Предупреждение менеджера окон: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(nautilus:3456): Eel-WARNING **: No extension, not implemented yet
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-04-13 09:50:28 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 355018 ***