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 481541 - crash in Open Folder: Installing themes
crash in Open Folder: Installing themes
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-09-29 09:27 UTC by david
Modified: 2007-10-19 22:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description david 2007-09-29 09:27:40 UTC 
Version: 2.18.3

What were you doing when the application crashed?
Installing themes


Distribution: MEPIS 7.0 (etch)
Gnome Release: 2.14.3 2007-02-15 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-1-mepis-smp #1 SMP PREEMPT Wed Sep 5 22:23:08 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Raleigh
Icon Theme: kids

Memory status: size: 74907648 vsize: 74907648 resident: 20754432 share: 11624448 rss: 20754432 rss_rlim: 4294967295
CPU usage: start_time: 1191057698 rtime: 657 utime: 617 stime: 40 cutime:7 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/tls/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226597504 (LWP 4008)]
(no debugging symbols found)
0xb7613231 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 166370

Thread 1 (Thread -1226597504 (LWP 4008))

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


----------- .xsession-errors (17 sec old) ---------------------
(gnome-theme-manager:4046): Gtk-WARNING **: Unable to locate theme engine in module_path: "industrial",
Window manager warning: Log level 16: Unable to locate theme engine in module_path: "industrial",
(gnome-panel:4002): Gtk-WARNING **: Unable to locate theme engine in module_path: "industrial",
(gnome-theme-manager:4045): Gtk-WARNING **: Unable to locate theme engine in module_path: "industrial",
(nautilus:4008): Gtk-WARNING **: Unable to locate theme engine in module_path: "industrial",
(gnome-session:3922): Gtk-WARNING **: Unable to locate theme engine in module_path: "industrial",
(bluetooth-applet:4017): Gtk-WARNING **: Unable to locate theme engine in module_path: "industrial",
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2007-10-19 22:54:04 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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