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 130124 - Nautilus crashes on desktop-launch (bus error)
Nautilus crashes on desktop-launch (bus error)
Status: RESOLVED DUPLICATE of bug 100709
Product: nautilus
Classification: Core
Component: Desktop
2.4.x
Other FreeBSD
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-12-28 13:10 UTC by akeuchel
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4



Description akeuchel 2003-12-28 13:10:17 UTC
Every time I start Gnome 2.4.1 Nautilus starts to draw the Desktop but ends
with a "bus error" after drawing the first Desktop-Icon (home) on the screen.

The error-message: The application nautilus (process 65667) crashed on a
severe bug (Bus error) - I translated this from german into english, so I
might have not used the exact words.

Sorry, don't know how to provide any further information.
Comment 1 akeuchel 2003-12-28 13:17:19 UTC
Two further hints:

- yesterday I made a portupgrade (but there where no gnome or nautilus
packages?! I rmember tiff and libaudio but there where two oher
updated packages)

- I tried to "make deinstall" and "make reinstall" the
nautilus2-package, but with no effort 
Comment 2 Martin Wehner 2003-12-28 13:58:11 UTC
Thanks for the bug report. Without a stack trace from the crash it's
very hard to determine what caused the crash. Please see
http://bugzilla.gnome.org/getting-traces.cgi for more information
about getting a useful stack trace.
Comment 3 akeuchel 2003-12-28 14:22:13 UTC
Sorry, here comes the backtrace:

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

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...0x28d55b64 in __sys_poll ()
   from /usr/lib/libc_r.so.4

Thread 1 (process 66044, thread 1)

  • #0 __sys_poll
    from /usr/lib/libc_r.so.4
  • #1 _thread_kern_scheduler
    from /usr/lib/libc_r.so.4
  • #2 _thread_kern_scheduler
    from /usr/lib/libc_r.so.4
#3  0x0 in ?? ()
No symbol table info available.
Comment 4 John Fleck 2003-12-28 16:54:30 UTC
Thanks for the trace. Similar BSD-related bugs have been reported. See
bug 107089, where the following comment was recorded:

*********************
The following comment from 100709 may be relevant: "It turns out this
was an
accidental FreeBSD ABI change during the import of gcc-3.2.1. div(), a
structure
returning function, was the culprit."
*********************

I'm closing this as a dupe of 100709
Comment 5 John Fleck 2003-12-28 16:54:49 UTC

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