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 538374 - crash in CD/DVD Creator: I'm making survey of som...
crash in CD/DVD Creator: I'm making survey of som...
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-14 20:52 UTC by v.merlin
Modified: 2008-06-15 10:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description v.merlin 2008-06-14 20:52:24 UTC 
What were you doing when the application crashed?
I'm making survey of some file (mp3,film...)  by icon NETWORK in menu PC  (it's the place where are all my disk) of Gnome. I'm examine the files (no opening) on far pc with Windows XP and the crash become when I enter to the some  directory. Just I'm not able,for automatic bug buddy, say if this is regular or iregular issue. Also I would say I'm using firewal Firestarter  
with regards M. Kovarik


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Enabled
GTK+ Theme: TransMetal
Icon Theme: Snow-Apple

Memory status: size: 481427456 vsize: 481427456 resident: 38191104 share: 19955712 rss: 38191104 rss_rlim: 18446744073709551615
CPU usage: start_time: 1213467604 rtime: 601 utime: 541 stime: 60 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2ad1f94bc240 (LWP 3929)]
0x00002ad1f29b2edf in waitpid () from /lib/libpthread.so.0

+ Trace 200455

Thread 1 (Thread 0x2ad1f94bc240 (LWP 3929))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 ??
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 ??
  • #9 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
  • #15 __libc_start_main
    from /lib/libc.so.6
  • #16 ??
  • #17 ??
  • #18 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (7 sec old) ---------------------
/home/martin/.themes/TransMetal/gtk-2.0/gtkrc:76: Background image options specified without filename
(eog:5644): Gtk-WARNING **: Theme directory 48x48/mimetypes of theme Snow-Apple has no size field
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
/home/martin/.themes/TransMetal/gtk-2.0/gtkrc:29: Nelze nalézt soubor obrázku v pixmap_path: "bubble-grey.png"
/home/martin/.themes/TransMetal/gtk-2.0/gtkrc:33: Background image options specified without filename
/home/martin/.themes/TransMetal/gtk-2.0/gtkrc:72: Nelze nalézt soubor obrázku v pixmap_path: "bubble-grey.png"
/home/martin/.themes/TransMetal/gtk-2.0/gtkrc:76: Background image options specified without filename
(bug-buddy:5661): Gtk-WARNING **: Theme directory 48x48/mimetypes of theme Snow-Apple has no size field
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-06-15 10:09:57 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 522534 ***