Bug 464939 – crash in Computer: When click right > Prope...

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 464939 - crash in Computer: When click right > Prope...


Summary:	crash in Computer: When click right > Prope...


Status:	RESOLVED DUPLICATE of bug 463468

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.18.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-08-09 06:32 UTC by debian
Modified:	2007-08-10 14:22 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description debian 2007-08-09 06:32:55 UTC

Version: 2.18.3

What were you doing when the application crashed?
When click right > Properties on some files


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-1-amd64 #1 SMP Sun Jul 29 13:54:41 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: humility-icons-MERGE

Memory status: size: 374988800 vsize: 374988800 resident: 32546816 share: 18518016 rss: 32546816 rss_rlim: 18446744073709551615
CPU usage: start_time: 1186587312 rtime: 816 utime: 695 stime: 121 cutime:681 cstime: 59 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46977284508496 (LWP 2801)]
[New Thread 1107310928 (LWP 5489)]
(no debugging symbols found)
0x00002ab9ba351c7f in waitpid () from /lib/libpthread.so.0

+ Trace 153897

Thread 1 (Thread 46977284508496 (LWP 2801))

#0 waitpid
from /lib/libpthread.so.0
#1 ??
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_logv
from /usr/lib/libglib-2.0.so.0
#4 g_log
from /usr/lib/libglib-2.0.so.0
#5 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#6 ??
from /usr/lib/libgtk-x11-2.0.so.0
#7 ??
#8 ??
#9 g_sequence_sort_changed_iter
#10 ??
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_list_store_set_valist
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_list_store_set
from /usr/lib/libgtk-x11-2.0.so.0
#13 ??
from /usr/lib/libeel-2-2.18.so
#14 eel_mime_application_chooser_new
from /usr/lib/libeel-2-2.18.so
#15 ??
#16 ??
#17 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#18 ??
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 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (142688 sec old) ---------------------
[AO SDL] Samplerate: 44100Hz Channels: Stereo Format s16le
AO: [sdl] 44100Hz 2ch s16le (2 bytes per sample)
Starting playback...
VDec: vo config request - 294 x 240 (preferred colorspace: Planar YV12)
Could not find matching colorspace - retrying with -vf scale...
Opening video filter: [scale]
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is undefined - no prescaling applied.
[swscaler @ 0xe78180]SwScaler: using unscaled yuv420p -> bgr24 special converter
VO: [gl2] 294x240 => 294x240 BGR 24-bit 
[gl2] You have OpenGL >= 1.2 capable drivers, GOOD (16bpp and BGR is ok!)
[gl2] antialiasing off
[gl2] bilinear linear
A:   0.0 V:   0.0 A-V:  0.048 ct:  0.000   1/  1 ??% ??% ??,?% 0 0              
A:   0.0 V:   0.0 A-V:  0.009 ct:  0.000   2/  2 ??% ??% ??,?% 0 0              
A:   0.1 V:   0.1 A-V:  0.011 ct:  0.0
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Susana 2007-08-10 14:22:16 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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