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 480807 - crash in Open Folder:
crash in Open Folder:
Status: RESOLVED INCOMPLETE
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 480887 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-09-27 01:58 UTC by Víctor Daniel
Modified: 2008-06-08 11:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Víctor Daniel 2007-09-27 01:58:57 UTC
Version: 2.20.0

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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Raleigh
Icon Theme: gnome

Memory status: size: 81833984 vsize: 81833984 resident: 18128896 share: 12406784 rss: 18128896 rss_rlim: 4294967295
CPU usage: start_time: 1190857561 rtime: 978 utime: 863 stime: 115 cutime:501 cstime: 53 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208821520 (LWP 25643)]
0x0012d402 in __kernel_vsyscall ()

Thread 1 (Thread -1208821520 (LWP 25643))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 nautilus_module_extension_list_free
    at nautilus-module.c line 250
  • #5 eel_debug_shut_down
    from /usr/lib/libeel-2.so.2
  • #6 main
    at nautilus-main.c line 563
  • #0 __kernel_vsyscall


----------- .xsession-errors (122616 sec old) ---------------------
==========================================================================
==========================================================================
Opening audio decoder: [mp3lib] MPEG layer-2, layer-3
AUDIO: 48000 Hz, 2 ch, s16le, 160.0 kbit/10.42% (ratio: 20000->192000)
Selected audio codec: [mp3] afm: mp3lib (mp3lib MPEG layer-2, layer-3)
==========================================================================
AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample)
Starting playback...
VDec: vo config request - 640 x 480 (preferred colorspace: Planar YV12)
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is 1.33:1 - prescaling to correct movie aspect.
VO: [x11] 640x480 => 640x480 Planar YV12 
[swscaler @ 0x874f778]SwScaler: using unscaled yuv420p -> bgr565 special converter
A:   0.3 V:   0.0 A-V:  0.341 ct:  0.000   1/  1 ??% ??% ??,?% 0 0              
A:   0.7 V:   0.0 A-V:  0.641 ct: -0.000   2/  2 ??% ??% ??,?% 1 0              
A:   0.7 V:   0.1 A-V:  0.613 ct:  0.0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Christian Kirbach 2007-10-07 20:32:40 UTC
*** Bug 480887 has been marked as a duplicate of this bug. ***
Comment 2 Christian Kirbach 2007-10-07 21:11:10 UTC
could be Bug 346401
Comment 3 André Klapper 2007-10-23 11:41:42 UTC
Thanks for taking the time to report this bug.
Unfortunately, the 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.

Could you please help fixing this by installing eel2-debuginfo, start the application as normal, and try to reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance!

More details can be found here: http://live.gnome.org/GettingTraces
Comment 4 André Klapper 2008-06-08 11:59:59 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!