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 418379 - crash in Computer: openen van een audio-sch...
crash in Computer: openen van een audio-sch...
Status: RESOLVED DUPLICATE of bug 320020
Product: nautilus
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-14 22:08 UTC by stef.vanhoutte
Modified: 2007-03-15 20:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description stef.vanhoutte 2007-03-14 22:08:36 UTC 
Version: 2.16.2

What were you doing when the application crashed?
openen van een audio-schijf


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.19-1.2911.6.5.fc6 #1 SMP Sun Mar 4 16:41:13 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 152924160 vsize: 0 resident: 152924160 share: 0 rss: 35397632 rss_rlim: 0
CPU usage: start_time: 1173909934 rtime: 0 utime: 558 stime: 0 cutime:513 cstime: 0 timeout: 45 it_real_value: 0 frequency: 0

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 -1208243456 (LWP 15143)]
(no debugging symbols found)
0x00705402 in __kernel_vsyscall ()

+ Trace 118673

Thread 1 (Thread -1208243456 (LWP 15143))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 nautilus_directory_async_state_changed
  • #5 nautilus_directory_async_state_changed
  • #6 nautilus_undo_transaction_unregister_object
  • #7 nautilus_directory_async_state_changed
  • #8 fm_directory_view_bump_zoom_level
  • #9 fm_directory_view_bump_zoom_level
  • #10 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #12 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #14 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 POA_Nautilus_MetafileMonitor__init
  • #16 __libc_start_main
    from /lib/libc.so.6
  • #17 g_cclosure_marshal_VOID__ENUM
  • #0 __kernel_vsyscall 


----------- .xsession-errors (10756 sec old) ---------------------
==========================================================================
[equalizer] Limiting the number of filters to 9 due to low sample rate.
[equalizer] Limiting the number of filters to 9 due to low sample rate.
[equalizer] Limiting the number of filters to 9 due to low sample rate.
alsa-init: using device default
alsa: 48000 Hz/2 channels/4 bpf/65536 bytes buffer/Signed 16 bit Little Endian
AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample)
[equalizer] Limiting the number of filters to 9 due to low sample rate.
Starting playback...
VDec: vo config request - 308 x 240 (preferred colorspace: Planar YV12)
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is 1,14:1 - prescaling to correct movie aspect.
VO: [xv] 308x240 => 308x270 Planar YV12 
A:   0,5 V:   0,0 A-V:  0,470 ct: -0,727   1/  1 ??% ??% ??,?% 0 0              
A:   0,5 V:   0,7 A-V: -0,177 ct: -0,730   2/  2 ??% ??% ??,?% 0 0              
A:   0,5 V:   0,7 A-V: -0,185 ct: -0,7
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Christian Kirbach 2007-03-15 20:05:38 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 320020 ***