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 387770 - crash in Computer: Performed a yum update w...
crash in Computer: Performed a yum update w...
Status: RESOLVED DUPLICATE of bug 374002
Product: nautilus
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-20 03:44 UTC by pentothal_natrium
Modified: 2006-12-20 12:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description pentothal_natrium 2006-12-20 03:44:26 UTC 
Version: 2.16.2

What were you doing when the application crashed?
Performed a yum update with Yumex.
dbus related?


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2868.fc6 #1 SMP Fri Dec 15 17:32:54 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled
----------- .xsession-errors (81593 sec old) ---------------------
Retrying in 5 seconds...
No bootable disk was found.
Please insert a bootable disk in any drive.
Retrying in 5 seconds...
No bootable disk was found.
Please insert a bootable disk in any drive.
Retrying in 5 seconds...
No bootable disk was found.
Please insert a bootable disk in any drive.
Retrying in 5 seconds...
No bootable disk was found.
Please insert a bootable disk in any drive.
Retrying in 5 seconds...
...Too much output, ignoring rest...
--------------------------------------------------

Memory status: size: 156106752 vsize: 0 resident: 156106752 share: 0 rss: 30093312 rss_rlim: 0
CPU usage: start_time: 1166497767 rtime: 0 utime: 8091 stime: 0 cutime:6917 cstime: 0 timeout: 1174 it_real_value: 0 frequency: 3

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 -1208469808 (LWP 3691)]
(no debugging symbols found)
0x00584402 in __kernel_vsyscall ()

+ Trace 95578

Thread 1 (Thread -1208469808 (LWP 3691))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gtk_ui_manager_remove_ui
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 nautilus_marshal_BOOLEAN__POINTER
  • #6 fm_directory_view_bump_zoom_level
  • #7 fm_directory_view_bump_zoom_level
  • #8 fm_directory_view_update_menus
  • #9 fm_directory_view_bump_zoom_level
  • #10 g_source_get_current_time
    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/libc.so.6
  • #17 g_cclosure_marshal_VOID__ENUM
  • #0 __kernel_vsyscall 






Comment 1


Susana





          2006-12-20 12:58:27 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 374002 ***