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 467290 - crash in Open Folder:
crash in Open Folder:
Status: RESOLVED DUPLICATE of bug 442829
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-16 11:47 UTC by ap
Modified: 2007-08-22 19:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description ap 2007-08-16 11:47:39 UTC
Version: 2.18.3

What were you doing when the application crashed?



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.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Glider
Icon Theme: gnome

Memory status: size: 28442624 vsize: 28442624 resident: 9293824 share: 7254016 rss: 9293824 rss_rlim: 4294967295
CPU usage: start_time: 1187264681 rtime: 15 utime: 8 stime: 7 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 -1208473888 (LWP 3244)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208473888 (LWP 3244))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 PyModule_GetDict
    from /usr/lib/libpython2.5.so.1.0
  • #5 nautilus_python_init_python
    from /usr/lib/nautilus/extensions-1.0/libnautilus-python.so
  • #6 nautilus_module_initialize
    from /usr/lib/nautilus/extensions-1.0/libnautilus-python.so
  • #7 ??
  • #8 g_type_module_use
    from /lib/libgobject-2.0.so.0
  • #9 nautilus_module_init
  • #10 nautilus_application_startup
  • #11 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (109 sec old) ---------------------
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3e0031a (tilda)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
14:42:47 : Yum Config Setup
14:42:48 : Yum Version : 3.2.2
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3e00003 (Yum Extend)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
14:42:48 : GUI Setup Completed
14:42:48 : Setup Yum : Transaction Set
14:42:48 : Setup Yum : RPM Db.
14:42:48 : Setup Yum : Repositories.
14:42:48 : Setup Yum : Package Sacks
14:42:49 : Setup Yum : Updates
14:43:22 : Setup Yum : Groups
14:43:22 : Setup Yum : Base setup completed
14:43:22 : Building Package Lists
--------------------------------------------------
Comment 1 Susana 2007-08-22 19:08:51 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 442829 ***