GNOME Bugzilla – Bug 550958
crash in Open Folder: I moved several thoused ...
Last modified: 2008-09-06 18:27:56 UTC
Version: 2.20.0 What were you doing when the application crashed? I moved several thoused emails from Thunderbird Junk folter to Trash folder. At the same time Opera, Skype, Liferea, OpenOffice.org3 beta, rDesktop and lots of terminals was opened and working. Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Wed Aug 20 12:56:41 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Murrina-LiNsta Icon Theme: LiNsta-0.3 Memory status: size: 74338304 vsize: 74338304 resident: 22839296 share: 15384576 rss: 22839296 rss_rlim: 4294967295 CPU usage: start_time: 1220599555 rtime: 1048 utime: 990 stime: 58 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6a80710 (LWP 18587)] (no debugging symbols found) 0xb7eed424 in __kernel_vsyscall ()
+ Trace 206353
Thread 1 (Thread 0xb6a80710 (LWP 18587))
----------- .xsession-errors (672061 sec old) --------------------- ** (liferea:3112): WARNING **: Update in "metadata" table failed (error code=5, database is locked) ** (liferea:3112): WARNING **: Could not save update state for subscription kjurtld (error code 5)! ** (liferea:3112): WARNING **: Insert in "itemsets" table failed (error code=5, database is locked) ** (liferea:3112): WARNING **: item update failed (error code=5, database is locked) ** (liferea:3112): WARNING **: Update in "metadata" table failed (error code=5, database is locked) ** (liferea:3112): WARNING **: Update in "metadata" table failed (error code=5, database is locked) ** (liferea:3112): WARNING **: Insert in "itemsets" table failed (error code=5, database is locked) ...Too much output, ignoring rest... --------------------------------------------------
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!
Sergio: Please DO USE the simple dup finder.
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 ***