GNOME Bugzilla – Bug 563514
crash in Open Folder: I had just done Control-...
Last modified: 2008-12-08 23:10:51 UTC
Version: 2.20.0 What were you doing when the application crashed? I had just done Control-Alt-Backspace to restartthe GUI Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.23.12-dream #1 SMP PREEMPT Fri Jan 18 02:13:57 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Go-Chrome Icon Theme: gnome Memory status: size: 43675648 vsize: 43675648 resident: 15724544 share: 12197888 rss: 15724544 rss_rlim: 4294967295 CPU usage: start_time: 1228602287 rtime: 71 utime: 52 stime: 19 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xb6a5a9a0 (LWP 9441)] 0xb72973d1 in waitpid () from /lib/libpthread.so.0
+ Trace 210553
Thread 1 (Thread 0xb6a5a9a0 (LWP 9441))
----------- .xsession-errors (16 sec old) --------------------- [35;01mwarning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting.[0m [01mHP Linux Imaging and Printing System (ver. 2.8.6b)[0m [01mSystem Tray Status Service ver. 0.1[0m Copyright (c) 2001-8 Hewlett-Packard Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Initializing nautilus-open-terminal extension Esmart_Trans Error: Could not read root window pixmap property! Esmart_Trans Error: Cannot create transparency pixmap: no valid wallpaper and no background color set. Initializing gnome-mount extension App got engage,app,opened from Bug Buddy --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Bruno: There's a simple-dup-finder available, eh? ;-)
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 480179 ***
Sorry, Andre! Sometimes I do things in a hurry. :-)