GNOME Bugzilla – Bug 457292
crash in Open Folder: I was searching files.
Last modified: 2007-07-25 13:45:46 UTC
Version: 2.18.3 What were you doing when the application crashed? I was searching files. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 108613632 vsize: 108613632 resident: 38313984 share: 22745088 rss: 38313984 rss_rlim: 4294967295 CPU usage: start_time: 1184570387 rtime: 1263 utime: 896 stime: 367 cutime:0 cstime: 0 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208482080 (LWP 3110)] [New Thread -1333204080 (LWP 3799)] (no debugging symbols found) 0x00875402 in __kernel_vsyscall ()
+ Trace 148307
Thread 2 (Thread -1333204080 (LWP 3799))
----------- .xsession-errors (6 sec old) --------------------- KK <notify/notify.cpp:199> void Notify::statusChanged(UserListElement, QString, const UserStatus&, bool, bool) ** gg_event_free(0x90f63e8); KK <chat_manager.cpp:491> void ChatManager::refreshTitles() KK <userbox.cpp:566> void UserBox::refresh() KK <userbox.cpp:642> void UserBox::resetVerticalPosition() KK <dnshandler.cpp:36> void DNSHandler::resultsReady() KK <gadu.cpp:587> void GaduProtocol::protocolUserDataChanged(QString, UserListElement, QString, QVariant, QVariant, bool, bool) KK <history.cpp:1281> void HistoryManager::checkImagesTimeouts() KK <gadu.cpp:1016> void GaduProtocol::everyMinuteActions() ** gg_ping(0x90b0a78); ** gg_send_packet(0x90b0a78, 0x08, ...); // gg_send_packet(0x08) 08 00 00 00 00 00 00 00 (nautilus:3110): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x1ece0)! --------------------------------------------------
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 456445 ***