Bug 507408 – crash in Home Folder: cliquei com o botão dire...

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 507408 - crash in Home Folder: cliquei com o botão dire...


Summary:	crash in Home Folder: cliquei com o botão dire...


Status:	RESOLVED DUPLICATE of bug 440988

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-05 02:54 UTC by arkanum
Modified:	2008-01-05 18:57 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description arkanum 2008-01-05 02:54:27 UTC

What were you doing when the application crashed?
cliquei com o botão direito sobre um arquivo AVI e escolhi a opção Propriedades.


Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-k7 #1 SMP Mon Nov 12 09:12:50 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Lush
Icon Theme: Lush

Memory status: size: 72146944 vsize: 72146944 resident: 23347200 share: 15671296 rss: 23347200 rss_rlim: 4294967295
CPU usage: start_time: 1199413392 rtime: 1542 utime: 1354 stime: 188 cutime:1601 cstime: 122 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6e1f6b0 (LWP 3235)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 184120

Thread 1 (Thread 0xb6e1f6b0 (LWP 3235))

#0 __kernel_vsyscall
#1 waitpid
from /lib/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 __kernel_vsyscall
#7 raise
from /lib/i686/cmov/libc.so.6
#8 abort
from /lib/i686/cmov/libc.so.6
#9 g_logv
from /usr/lib/libglib-2.0.so.0
#10 g_log
from /usr/lib/libglib-2.0.so.0
#11 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 ??
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
#16 ??
from /usr/lib/libgtk-x11-2.0.so.0
#17 ??
from /usr/lib/libgtk-x11-2.0.so.0
#18 ??
from /usr/lib/libgtk-x11-2.0.so.0
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??
#32 ??
#33 ??
#34 ??
#35 ??
#36 ??
#37 ??
#38 ??
#39 ??
#40 ??
#41 ??
from /usr/lib/libgtk-x11-2.0.so.0
#42 ??
#43 ??
#44 ??
#45 ??
#46 ??
#47 ??
#48 ??
#49 ??
from /usr/lib/libgtk-x11-2.0.so.0
#50 ??
#51 ??
#52 ??
#53 ??
#54 ??
#55 ??
#56 g_sequence_sort_changed_iter
#0 __kernel_vsyscall



----------- .xsession-errors (35560 sec old) ---------------------
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
OggS-SEEK: at 0 want 50168 got 45120 (diff-requested 50168)
OggS-SEEK: at 50240 want 520 got 0 (diff-requested -49720)
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 André Klapper 2008-01-05 18:57:20 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 440988 ***