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 511341 - crash in Open Folder: adding emblems to an ico...
crash in Open Folder: adding emblems to an ico...
Status: RESOLVED DUPLICATE of bug 355018
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-22 19:17 UTC by r.bradley.williams
Modified: 2008-01-23 10:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description r.bradley.williams 2008-01-22 19:17:46 UTC
Version: 2.18.3

What were you doing when the application crashed?
adding emblems to an icon for a  vfat disk mounted  over nfs at mountpoint /media/USBHD  this is where automounted disks go on my distro 


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Tactile
Icon Theme: G-Flat-SVG

Memory status: size: 70258688 vsize: 70258688 resident: 16576512 share: 10448896 rss: 16576512 rss_rlim: 4294967295
CPU usage: start_time: 1201000973 rtime: 731 utime: 651 stime: 80 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6dc46b0 (LWP 3281)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6dc46b0 (LWP 3281))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.14.3/glib/gspawn.c line 369
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.14.3/glib/gspawn.c line 677
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 strcmp
    from /lib/i686/cmov/libc.so.6
  • #7 changed_group_callback
    at fm-properties-window.c line 1646
  • #8 IA__g_cclosure_marshal_VOID__VOID
    at /tmp/buildd/glib2.0-2.14.3/gobject/gmarshal.c line 77
  • #9 IA__g_closure_invoke
    at /tmp/buildd/glib2.0-2.14.3/gobject/gclosure.c line 490
  • #10 signal_emit_unlocked_R
    at /tmp/buildd/glib2.0-2.14.3/gobject/gsignal.c line 2440
  • #11 IA__g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.14.3/gobject/gsignal.c line 2199
  • #12 IA__g_signal_emit
    at /tmp/buildd/glib2.0-2.14.3/gobject/gsignal.c line 2243
  • #13 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
  • #15 ??
  • #16 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (21 sec old) ---------------------
WARNING: DCOPReply<>: cast to 'QString' error
WARNING: DCOPReply<>: cast to 'QString' error
WARNING: DCOPReply<>: cast to 'QString' error
WARNING: DCOPReply<>: cast to 'QString' error
WARNING: DCOPReply<>: cast to 'QString' error
WARNING: DCOPReply<>: cast to 'QString' error
WARNING: DCOPReply<>: cast to 'QString' error
WARNING: DCOPReply<>: cast to 'QString' error
WARNING: DCOPReply<>: cast to 'QString' error
WARNING: DCOPReply<>: cast to 'QString' error
WARNING: DCOPReply<>: cast to 'QString' error
/home/russ1/.themes/Tactile/gtk-2.0/gtkrc:1046: Unable to locate image file in pixmap_path: "spin_button_up_arrow_prelight.png"
/home/russ1/.themes/Tactile/gtk-2.0/gtkrc:1050: Overlay image options specified without filename
/home/russ1/.themes/Tactile/gtk-2.0/gtkrc:1056: Unable to locate image file in pixmap_path: "spin_button_down_arrow_prelight.png"
/home/russ1/.themes/Tactile/gtk-2.0/gtkrc:1060: Overlay image options specified without filename
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-23 10:29:25 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 ***