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 543659 - crash in Open Folder: watching a video through...
crash in Open Folder: watching a video through...
Status: RESOLVED INCOMPLETE
Product: nautilus
Classification: Core
Component: general
2.22.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-07-18 21:17 UTC by fcoronel
Modified: 2008-12-06 12:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description fcoronel 2008-07-18 21:17:42 UTC 
Version: 2.22.2

What were you doing when the application crashed?
watching a video through smb with MPlayer.


Distribution: openSUSE 11.0 (i586)
Gnome Release: 2.22.1 2008-06-07 (SUSE)
BugBuddy Version: 2.22.0

System: Linux 2.6.25.9-0.2-pae #1 SMP 2008-06-28 00:00:07 +0200 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gilouche
Icon Theme: Gilouche

Memory status: size: 166809600 vsize: 166809600 resident: 13983744 share: 23547904 rss: 37531648 rss_rlim: 1805296640
CPU usage: start_time: 1216387838 rtime: 2209 utime: 1969 stime: 240 cutime:0 cstime: 20 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0xb6ad36d0 (LWP 4673)]
[New Thread 0xb0c68b90 (LWP 5970)]
0xffffe430 in __kernel_vsyscall ()

+ Trace 203217

Thread 1 (Thread 0xb6ad36d0 (LWP 4673))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 google_breakpad::ExceptionHandler::HandleException
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 <signal handler called>
  • #9 g_list_foreach
    from /usr/lib/libglib-2.0.so.0
  • #10 nautilus_file_list_unref
  • #11 nautilus_file_list_free
  • #12 remove_pending
  • #13 is_directory_ready_callback
  • #14 ready_callback_call
  • #15 call_ready_callbacks_at_idle
  • #16 g_idle_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #20 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (23525 sec old) ---------------------
[beagle]  NOT RUN_ENABLED status .  NO INDEX
[beagle] Page Loaded 
[beagle]  NOT RUN_ENABLED status .  NO INDEX
/usr/bin/compiz (animation) - Error: Animation settings mismatch in "Animation Selection" list for Focus event.
/usr/bin/compiz (animation) - Error: Animation settings mismatch in "Animation Selection" list for Focus event.
/usr/bin/compiz (animation) - Error: Animation settings mismatch in "Animation Selection" list for Focus event.
/bin/sh: /usr/bin/esd: No such file or directory
/bin/sh: /usr/bin/esd: No such file or directory
/bin/sh: /usr/bin/esd: No such file or directory
/bin/sh: /usr/bin/esd: No such file or directory
/bin/sh: /usr/bin/esd: No such file or directory
/bin/sh: /usr/bin/esd: No such file or directory
/bin/sh: /usr/bin/esd: No such file or directory
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-07-20 17:20:36 UTC 
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!
Comment 2 Bruno Boaventura 2008-12-06 12:18: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!