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 423042 - crash in Computer: gebrannte CD in Nautilus...
crash in Computer: gebrannte CD in Nautilus...
Status: RESOLVED DUPLICATE of bug 351366
Product: nautilus
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-26 19:26 UTC by marek.online
Modified: 2007-03-31 13:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description marek.online 2007-03-26 19:26:30 UTC 
Version: 2.16.2

What were you doing when the application crashed?
gebrannte CD in Nautilus geöffnet


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2933.fc6xen #1 SMP Mon Mar 19 12:00:20 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 135532544 vsize: 0 resident: 135532544 share: 0 rss: 27406336 rss_rlim: 0
CPU usage: start_time: 1174936264 rtime: 0 utime: 174 stime: 0 cutime:151 cstime: 0 timeout: 23 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208543536 (LWP 4071)]
(no debugging symbols found)
0x002c5402 in __kernel_vsyscall ()

+ Trace 122393

Thread 1 (Thread -1208543536 (LWP 4071))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 nautilus_directory_async_state_changed
  • #5 nautilus_directory_async_state_changed
  • #6 nautilus_undo_transaction_unregister_object
  • #7 nautilus_directory_async_state_changed
  • #8 fm_directory_view_bump_zoom_level
  • #9 fm_directory_view_bump_zoom_level
  • #10 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #12 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #14 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 POA_Nautilus_MetafileMonitor__init
  • #16 __libc_start_main
    from /lib/i686/nosegneg/libc.so.6
  • #17 g_cclosure_marshal_VOID__ENUM
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
20061206T191007Z-5793-500-1-105@fedora.starbase has recurrences
20061206T191005Z-5793-500-1-30@fedora.starbase has recurrences
20061206T191007Z-5793-500-1-110@fedora.starbase has recurrences
20061206T191008Z-5793-500-1-145@fedora.starbase has recurrences
20061206T191005Z-5793-500-1-13@fedora.starbase has recurrences
20061206T191008Z-5793-500-1-150@fedora.starbase has recurrences
20061206T191006Z-5793-500-1-56@fedora.starbase has recurrences
20061206T191008Z-5793-500-1-133@fedora.starbase has recurrences
pas-id-4579BEEA000000EF-birthday has recurrences
pas-id-45B28B8600000001-birthday has recurrences
Error: Indexing secure https:// URIs is not secure!
Error: Indexing secure https:// URIs is not secure!
/usr/share/firefox-2.0/firefox/run-mozilla.sh: line 131:  4203 Speicherzugriffsfehler  "$prog" ${1+"$@"}
Flushing 42software.eu adverserve.net affaire.com agentursupport.de allianz.de ask.com bahn.de bayerninvest.de biglabels.de brauerei-rapp.de cinema-muenchen.com city-hotel.com comdirect.de computerfut
** (bug-buddy:4400): WARNING **: Symbol für Ordner öffnen konnte nicht geladen werden
--------------------------------------------------
Comment 1 André Klapper 2007-03-31 13:27:30 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 351366 ***