Bug 427867 – crash in Computer: terminal ge?ffnet und # ...

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 427867 - crash in Computer: terminal ge?ffnet und # ...


Summary:	crash in Computer: terminal ge?ffnet und # ...


Status:	RESOLVED DUPLICATE of bug 371225

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:	2007-04-09 13:29 UTC by petrieheil189076
Modified:	2007-04-09 14:29 UTC

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

Description petrieheil189076 2007-04-09 13:29:53 UTC

What were you doing when the application crashed?
terminal geöffnet und # sh ati-driver-installer-8.35.5-x86.x86_64.run --listpkg
eingefügt und dann auf ausführen gedrückt.
Habe Probleme mit ati 1650 pro expert und suse linux 10.2
Keine Aktivierung des Grafikkartenbeschleunigers.
Bitte um Hilfe
Danke


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 367382528 vsize: 367382528 resident: 11169792 share: 22048768 rss: 33218560 rss_rlim: 1793459200
CPU usage: start_time: 1176125083 rtime: 119 utime: 113 stime: 6 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47749917696640 (LWP 26731)]
(no debugging symbols found)
0x00002b6da25fbc5f in waitpid () from /lib64/libpthread.so.0

+ Trace 126278

Thread 1 (Thread 47749917696640 (LWP 26731))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /opt/gnome/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 nautilus_file_get_uri
#4 nautilus_file_get_parent_uri
#5 g_list_foreach
from /opt/gnome/lib64/libglib-2.0.so.0
#6 g_list_foreach
from /opt/gnome/lib64/libglib-2.0.so.0
#7 g_list_foreach
from /opt/gnome/lib64/libglib-2.0.so.0
#8 g_list_foreach
from /opt/gnome/lib64/libglib-2.0.so.0
#9 g_list_foreach
from /opt/gnome/lib64/libglib-2.0.so.0
#10 POA_Nautilus_MetafileMonitor__init
#11 fm_directory_view_bump_zoom_level
#12 fm_directory_view_bump_zoom_level
#13 g_closure_invoke
from /opt/gnome/lib64/libgobject-2.0.so.0
#14 g_signal_override_class_closure
from /opt/gnome/lib64/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /opt/gnome/lib64/libgobject-2.0.so.0
#16 g_signal_emit
from /opt/gnome/lib64/libgobject-2.0.so.0
#17 nautilus_directory_async_state_changed
#18 nautilus_directory_async_state_changed
#19 gnome_vfs_job_get_count
from /opt/gnome/lib64/libgnomevfs-2.so.0
#20 g_main_context_dispatch
from /opt/gnome/lib64/libglib-2.0.so.0
#21 g_main_context_prepare
from /opt/gnome/lib64/libglib-2.0.so.0
#22 g_main_loop_run
from /opt/gnome/lib64/libglib-2.0.so.0
#23 gtk_main
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#24 POA_Nautilus_MetafileMonitor__init
#25 __libc_start_main
from /lib64/libc.so.6
#26 g_cclosure_marshal_VOID__ENUM
#27 ??
#28 ??
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 palfrey 2007-04-09 14:29:01 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find

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