Bug 402676 – crash in Home Folder: ???????????????? nexuiz

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 402676 - crash in Home Folder: ???????????????? nexuiz


Summary:	crash in Home Folder: ???????????????? nexuiz


Status:	RESOLVED NOTGNOME

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:

Duplicates:	429980 (view as bug list)
Depends on:
Blocks:

Reported:	2007-01-31 01:01 UTC by koldunovn
Modified:	2007-06-22 23:59 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description koldunovn 2007-01-31 01:01:39 UTC

What were you doing when the application crashed?
запустил nexuiz 


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 236261376 vsize: 236261376 resident: 35725312 share: 13357056 rss: 35725312 rss_rlim: -1
CPU usage: start_time: 1170205177 rtime: 140 utime: 131 stime: 9 cutime:0 cstime: 0 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 47532046731856 (LWP 1964)]
(no debugging symbols found)
0x00002b3ae6c57eef in waitpid () from /lib/libpthread.so.0

+ Trace 106709

Thread 1 (Thread 47532046731856 (LWP 1964))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 jpeg_idct_islow
from /usr/lib/libjpeg.so.62
#4 jinit_d_main_controller
from /usr/lib/libjpeg.so.62
#5 jinit_phuff_decoder
from /usr/lib/libjpeg.so.62
#6 jpeg_read_scanlines
from /usr/lib/libjpeg.so.62
#7 to_callback_terminate
from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-jpeg.so
#8 to_callback_terminate
from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-jpeg.so
#9 gdk_pixbuf_loader_write
from /usr/lib/libgdk_pixbuf-2.0.so.0
#10 eel_gdk_pixbuf_load
from /usr/lib/libeel-2.so.2
#11 eel_background_is_set
from /usr/lib/libeel-2.so.2
#12 eel_background_is_set
from /usr/lib/libeel-2.so.2
#13 nautilus_directory_async_state_changed
#14 nautilus_directory_async_state_changed
#15 fm_directory_view_bump_zoom_level
#16 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#20 fm_directory_view_bump_zoom_level
#21 nautilus_clipboard_monitor_emit_changed
#22 nautilus_clipboard_monitor_emit_changed
#23 nautilus_directory_async_state_changed
#24 nautilus_icon_container_request_update_all
#25 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#26 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#27 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#28 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#29 POA_Nautilus_MetafileMonitor__init
#30 __libc_start_main
from /lib/libc.so.6
#31 ??
#32 ??
#33 ??
#0 waitpid
from /lib/libpthread.so.0

Comment 1 palfrey 2007-02-20 18:56:44 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!

Comment 2 palfrey 2007-04-16 18:27:17 UTC

*** Bug 429980 has been marked as a duplicate of this bug. ***

Comment 3 Karsten Bräckelmann 2007-06-22 23:59:24 UTC

Thanks for taking the time to report this bug.

However, this is a crash in libjpeg, which does not track its bugs in the GNOME Bugzilla. We kindly ask you to report the bug to the application authors. For a selective list of other bug tracking systems please consult
  http://live.gnome.org/Bugsquad/TriageGuide/NonGnome.

If the affected third party application has a bug tracking system you should investigate whether a bug for the reported issue is already filed in this system. If it has not been filed yet please do so. Also ensure that both bug reports contain a link to each other.  Thanks!