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 519984 - crash in Open Folder: It's clear now - moving ...
crash in Open Folder: It's clear now - moving ...
Status: RESOLVED DUPLICATE of bug 519050
Product: nautilus
Classification: Core
Component: general
2.21.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-02 21:45 UTC by nemes.sorin
Modified: 2008-03-03 01:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description nemes.sorin 2008-03-02 21:45:28 UTC 
Version: 2.21.92

What were you doing when the application crashed?
It's clear now - moving some files to trash or get Properties for PDF files kill my Nautilus - I can reproduce that easily now.

ON other circumstances or open Properties window for other kind of files ..no problem.

The only problem along PDF is deag-and-drop on Desktop and Trash folder 


Distribution: Ubuntu 8.04 (hardy)
Gnome Release: 2.21.92 2008-02-29 (Ubuntu)
BugBuddy Version: 2.21.90

System: Linux 2.6.24-10-generic #1 SMP Fri Feb 22 19:08:18 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Aurora Borealis
Icon Theme: nuoveXT.2.2

Memory status: size: 186994688 vsize: 186994688 resident: 93536256 share: 27860992 rss: 93536256 rss_rlim: 4294967295
CPU usage: start_time: 1204482058 rtime: 18060 utime: 12275 stime: 5785 cutime:1064 cstime: 162 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b5e720 (LWP 19156)]
[New Thread 0xb067eb90 (LWP 25081)]
[New Thread 0xb69d9b90 (LWP 19329)]
0xb7fc1410 in __kernel_vsyscall ()

+ Trace 191085

Thread 1 (Thread 0xb6b5e720 (LWP 19156))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/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 <signal handler called>
  • #6 trash_state_changed_cb
    at nautilus-pathbar.c line 211
  • #7 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 ??
    from /usr/lib/libgobject-2.0.so.0
  • #10 ??
  • #11 ??
  • #0 __kernel_vsyscall 

----------- .xsession-errors (58 sec old) ---------------------
[00000001] main private debug: removing playlist handler
[00000284] main private debug: thread 2838043536 joined (playlist/playlist.c:247)
[00000283] main playlist debug: thread 2763402128 joined (playlist/playlist.c:248)
[00000283] main playlist debug: deleting playlist item `http://frankenblog.com/theevilimpulse.mp3'
[00000001] main private debug: removing all video outputs
[00000001] main private debug: removing all audio outputs
[00000001] main private debug: removing module "memcpy"
[00000001] main private debug: saving plugins cache file /home/sorin/.vlc/cache/plugins-04041e.dat
VLC media player 0.8.6d Janus
[00000338] jack audio output error: failed to connect to JACK server
[00000338] oss audio output error: cannot open audio device (/dev/dsp)
[00000372] equalizer private error: rate not supported
[00000338] main audio output error: cannot add user filter equalizer (skipped)
overflow in spectral RLE, ignoring
[00000283] main playlist: stopping playback
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-03-03 01:26:11 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 519050 ***