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 536612 - crash in File Browser: i was closing a folder b...
crash in File Browser: i was closing a folder b...
Status: RESOLVED DUPLICATE of bug 452894
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-04 14:48 UTC by pavo1900
Modified: 2008-06-04 23:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description pavo1900 2008-06-04 14:48:46 UTC
Version: 2.20.0

What were you doing when the application crashed?
i was closing a folder but meanwhile i was also downloading 4 heavy files with iceweasel, using secondlife (very heavy program/game) and listening to music with rythmbox and my creative player


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 87732224 vsize: 87732224 resident: 24821760 share: 15200256 rss: 24821760 rss_rlim: 4294967295
CPU usage: start_time: 1212585565 rtime: 5944 utime: 5179 stime: 765 cutime:22 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6c0f720 (LWP 3151)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6c0f720 (LWP 3151))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 IA__g_type_check_instance
    at /build/buildd/glib2.0-2.16.3/gobject/gtype.c line 3242
  • #7 IA__g_signal_connect_data
    at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 1637
  • #8 set_pending_icon_to_reveal
    at nautilus-icon-container.c line 568
  • #9 end_renaming_mode
    at nautilus-icon-container.c line 7149
  • #10 icon_toggle_selected
    at nautilus-icon-container.c line 440
  • #11 icon_set_selected
    at nautilus-icon-container.c line 484
  • #12 select_one_unselect_others
    at nautilus-icon-container.c line 1833
  • #13 button_press_event
    at nautilus-icon-container.c line 3245
  • #14 _gtk_marshal_BOOLEAN__BOXED
    at /tmp/buildd/gtk+2.0-2.12.9/gtk/gtkmarshalers.c line 84
  • #15 g_type_class_meta_marshal
    at /build/buildd/glib2.0-2.16.3/gobject/gclosure.c line 567
  • #16 IA__g_closure_invoke
    at /build/buildd/glib2.0-2.16.3/gobject/gclosure.c line 490
  • #17 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 2478
  • #18 IA__g_signal_emit_valist
    at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 2209
  • #19 IA__g_signal_emit
    at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 2243
  • #20 gtk_widget_event_internal
    at /tmp/buildd/gtk+2.0-2.12.9/gtk/gtkwidget.c line 4678
  • #21 IA__gtk_propagate_event
    at /tmp/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c line 2336
  • #22 IA__gtk_main_do_event
    at /tmp/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c line 1541
  • #23 gdk_event_dispatch
    at /tmp/buildd/gtk+2.0-2.12.9/gdk/x11/gdkevents-x11.c line 2351
  • #24 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2009
  • #25 g_main_context_iterate
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2642
  • #26 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2850
  • #27 IA__gtk_main
    at /tmp/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c line 1163
  • #28 main
    at nautilus-main.c line 556
  • #29 __libc_start_main
    from /lib/i686/cmov/libc.so.6
  • #30 _start
  • #0 __kernel_vsyscall


----------- .xsession-errors (2008 sec old) ---------------------
2008-06-04T14:13:50Z INFO: LLVoiceClient::sessionStateChangeEvent: left session sip:confctl-316@bhr.vivox.com, name  handle 
2008-06-04T14:13:50Z INFO: LLVoiceClient::removeAllParticipants: called
2008-06-04T14:13:50Z INFO: LLVoiceClient::removeParticipant: participant "xJXTPtMzTRYSt4OLKZL9kgA==" (2574cfb4-ccd3-4584-ade0-e2ca64bf6480) removed.
2008-06-04T14:13:50Z INFO: LLVoiceClient::sessionStateChangeEvent: left session c1_m1000xJXTPtMzTRYSt4OLKZL9kgA==40in state stateRunning
2008-06-04T14:13:50Z INFO: LLVoiceClient::setState: entering state stateSessionTerminated
2008-06-04T14:13:50Z INFO: LLVoiceClient::notifyStatusObservers:  STATUS_LEFT_CHANNEL, session URI sip:confctl-316@bhr.vivox.com
2008-06-04T14:13:50Z INFO: LLVoiceClient::setState: entering state stateNoChannel
2008-06-04T14:13:51Z INFO: LLVoiceClient::setState: entering state stateSessionCreate
2008-06-04T14:13:51Z INFO: LLVoiceClient::sessionCreateSendMessage: requesting join: sip:confctl-316@bhr.vivox.com
2008-06-04T14:13:51Z INFO: LLVoiceClient::notifyStatusObservers:  STATUS_JOINING, session URI sip:confctl-316@bhr.vivox.com
2008-06-04T14:13:51Z INFO: LLVoiceClient::setState: entering state stateJoiningSession
Wed Jun  4 16:13:52 2008 freepopsd: ERROR(log_lua.c,  70): (@/usr/share/freepops/lua/yahoo.lua, 1506) : Yahoo - unable to parse out crumb value.  Deletion will fail.
2008-06-04T14:13:52Z INFO: LLVoiceClient::sessionCreateResponse: Session.Create response received (success), session handle is c1_m1000xJXTPtMzTRYSt4OLKZL9kgA==41
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) 
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-06-04 23:59:10 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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