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 459814 - crash in File Browser: personalizzare i temi di...
crash in File Browser: personalizzare i temi di...
Status: RESOLVED DUPLICATE of bug 356181
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-24 04:45 UTC by salvo00365
Modified: 2007-07-25 14:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description salvo00365 2007-07-24 04:45:05 UTC
Version: 2.18.1

What were you doing when the application crashed?
personalizzare i temi di desktop


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Raleigh
Icon Theme: gnome

Memory status: size: 69894144 vsize: 69894144 resident: 21790720 share: 13635584 rss: 21790720 rss_rlim: 4294967295
CPU usage: start_time: 1185258455 rtime: 249 utime: 230 stime: 19 cutime:3 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 -1226729280 (LWP 4324)]
(no debugging symbols found)
0xb7f487f2 in ?? () from /lib/ld-linux.so.2

Thread 1 (Thread -1226729280 (LWP 4324))

  • #0 ??
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 gdk_x11_drawable_get_xdisplay
    from /usr/lib/libgdk-x11-2.0.so.0
  • #6 gdk_events_pending
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 gdk_events_pending
    from /usr/lib/libgdk-x11-2.0.so.0
  • #8 gdk_add_client_message_filter
    from /usr/lib/libgdk-x11-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #12 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 main
  • #0 ??
    from /lib/ld-linux.so.2


----------- .xsession-errors ---------------------
/usr/share/themes/Lush/gtk-2.0/gtkrc:7: Impossibile trovare il file da includere: "iconrc"
/usr/share/themes/Lush/gtk-2.0/gtkrc:7: Impossibile trovare il file da includere: "iconrc"
/usr/share/themes/Lush/gtk-2.0/gtkrc:7: Impossibile trovare il file da includere: "iconrc"
/usr/share/themes/Lush/gtk-2.0/gtkrc:7: Impossibile trovare il file da includere: "iconrc"
/usr/share/themes/Lush/gtk-2.0/gtkrc:7: Impossibile trovare il file da includere: "iconrc"
/usr/share/themes/Lush/gtk-2.0/gtkrc:7: Impossibile trovare il file da includere: "iconrc"
/usr/share/themes/Lush/gtk-2.0/gtkrc:7: Impossibile trovare il file da includere: "iconrc"
/usr/share/themes/Lush/gtk-2.0/gtkrc:7: Impossibile trovare il file da includere: "iconrc"
(gnome-theme-manager:4801): capplet-common-WARNING **: Could not open file "/usr/share/themes/Lush/gtk-2.0/iconrc"
/usr/share/themes/Lush/gtk-2.0/gtkrc:7: Impossibile trovare il file da includere: "iconrc"
(gnome-theme-manager:4802): Gtk-CRITICAL **: gtk_widget_map: assertion `GTK_WIDGET_VISIBLE (widget)' failed
(gnome-theme-manager:4802): Gtk-CRITICAL **: gtk_widget_map: assertion `GTK_WIDGET_VISIBLE (widget)' failed
--------------------------------------------------
Comment 1 André Klapper 2007-07-25 14:25:21 UTC
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 356181 ***