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 497275 - crash in Open Folder:
crash in Open Folder:
Status: RESOLVED DUPLICATE of bug 459221
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-16 03:49 UTC by gentooisapeiceofshit
Modified: 2007-11-16 16:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description gentooisapeiceofshit 2007-11-16 03:49:27 UTC
Version: 2.18.3

What were you doing when the application crashed?



Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.3 2007-09-28 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-gentoo-r9 #1 PREEMPT Mon Nov 12 11:06:02 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Vista-Inspirate_1.0

Memory status: size: 80482304 vsize: 80482304 resident: 35418112 share: 20111360 rss: 35418112 rss_rlim: 4294967295
CPU usage: start_time: 1195186876 rtime: 306 utime: 280 stime: 26 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Really redefine built-in command "frame"? (y or n) [answered Y; input not from terminal]
Really redefine built-in command "thread"? (y or n) [answered Y; input not from terminal]
Really redefine built-in command "start"? (y or n) [answered Y; input not from terminal]
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
_______________________________________________________________________________
     eax:FFFFFE00 ebx:00001A36  ecx:BF805AC8  edx:00000000     eflags:00000293
     esi:BF805E7C edi:B6D89FF4  esp:BF8059E4  ebp:BF805AD8     eip:FFFFE410
     cs:0073  ds:007B  es:007B  fs:0000  gs:0033  ss:007B    o d I t S z A p C 
[007B:BF8059E4]---------------------------------------------------------[stack]
BF805A14 : 94 50 CC B6  90 1B 00 B7 - 00 00 00 00  28 5A 80 BF .P..........(Z..
BF805A04 : C8 5A 80 BF  00 00 00 00 - 01 00 00 00  D8 B9 6B 08 .Z............k.
BF8059F4 : 00 3F DA B7  00 00 00 00 - 6D DC D6 B7  36 1A 00 00 .?......m...6...
BF8059E4 : D8 5A 80 BF  00 00 00 00 - C8 5A 80 BF  AB 5F 00 B7 .Z.......Z..._..
[007B:BF805E7C]---------------------------------------------------------[ data]
BF805E7C : 20 00 00 00  00 00 00 00 - 00 00 00 00  00 00 00 00  ...............
BF805E8C : 00 00 00 00  00 00 00 00 - 00 00 00 00  00 00 00 00 ................
[0073:FFFFE410]---------------------------------------------------------[ code]
0xffffe410 <__kernel_vsyscall+16>:	pop    %ebp
0xffffe411 <__kernel_vsyscall+17>:	pop    %edx
0xffffe412 <__kernel_vsyscall+18>:	pop    %ecx
0xffffe413 <__kernel_vsyscall+19>:	ret    
0xffffe414 <_fini+1210164224>:	nop    
0xffffe415 <_fini+1210164225>:	nop    
------------------------------------------------------------------------------
0xffffe410 in __kernel_vsyscall ()
  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 ??
  • #5 ??


----------- .xsession-errors ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** ERROR **: file nautilus-navigation-window.c: line 834 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers))
aborting...
--------------------------------------------------
Comment 1 palfrey 2007-11-16 16:07:31 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 459221 ***