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 150134 - When installing updates with YOU (YaST2) computer crashed
When installing updates with YOU (YaST2) computer crashed
Status: RESOLVED DUPLICATE of bug 120222
Product: nautilus
Classification: Core
Component: general
2.4.x
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-08-14 16:20 UTC by nickjb
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4



Description nickjb 2004-08-14 16:21:53 UTC
Distribution: SuSE Linux 9.1 (i586)
Package: nautilus
Severity: normal
Version: GNOME2.4.1 2.4.2
Gnome-Distributor: GNOME.Org
Synopsis: When installing updates with YOU (YaST2) computer crashed
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.4.2
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:
Nautilus would no longer start after YOU was interupted during an online
update

Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

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

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...[Thread debugging using
libthread_db enabled]
[New Thread 1089979328 (LWP 24911)]
[New Thread 1093745584 (LWP 24917)]
[Thread debugging using libthread_db enabled]
[New Thread 1089979328 (LWP 24911)]
[New Thread 1093745584 (LWP 24917)]
[Thread debugging using libthread_db enabled]
[New Thread 1089979328 (LWP 24911)]
[New Thread 1093745584 (LWP 24917)]
[New Thread 1093479344 (LWP 24916)]
[New Thread 1093213104 (LWP 24915)]
[New Thread 1092946864 (LWP 24914)]
[New Thread 1092680624 (LWP 24913)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...0xffffe410 in ?? ()

Thread 1 (Thread 1089979328 (LWP 24911))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #5 libgnomeui_segv_handle
    from /opt/gnome/lib/libgnomeui-2.so.0
  • #6 <signal handler called>
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 raise
    from /lib/tls/libc.so.6
  • #12 abort
    from /lib/tls/libc.so.6
  • #13 g_logv
    from /opt/gnome/lib/libglib-2.0.so.0
  • #14 g_log
    from /opt/gnome/lib/libglib-2.0.so.0
  • #15 add_to_hash_table
    from /opt/gnome/lib/libnautilus-private.so.2
  • #16 nautilus_directory_add_file
    from /opt/gnome/lib/libnautilus-private.so.2
  • #17 nautilus_desktop_icon_file_new
    from /opt/gnome/lib/libnautilus-private.so.2
  • #18 create_icon_file
    from /opt/gnome/lib/libnautilus-private.so.2
  • #19 nautilus_desktop_link_new_from_volume
    from /opt/gnome/lib/libnautilus-private.so.2
  • #20 create_volume_link
    from /opt/gnome/lib/libnautilus-private.so.2
  • #21 create_one_volume_link
    from /opt/gnome/lib/libnautilus-private.so.2
  • #22 nautilus_volume_monitor_each_mounted_volume
    from /opt/gnome/lib/libnautilus-private.so.2
  • #23 nautilus_desktop_link_monitor_init
    from /opt/gnome/lib/libnautilus-private.so.2
  • #24 g_type_create_instance
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #25 g_object_constructor
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #26 g_object_newv
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #27 g_object_new_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #28 g_object_new
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #29 nautilus_desktop_link_monitor_get
    from /opt/gnome/lib/libnautilus-private.so.2
  • #30 nautilus_application_startup
  • #31 main
  • #0 ??




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-08-14 12:21 -------


Unknown version 2.4.2 in product nautilus. Setting version to "1.0.x".
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "nautilus".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was nickjb@internode.on.net.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Martin Wehner 2004-08-21 15:30:30 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 120222 ***