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 119572 - Error on nautilus startuo
Error on nautilus startuo
Status: RESOLVED DUPLICATE of bug 100709
Product: nautilus
Classification: Core
Component: general
unspecified
Other other
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-08-10 17:11 UTC by Rafael Caesar Lenzi
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Rafael Caesar Lenzi 2003-08-10 17:06:47 UTC
Package: nautilus
Severity: critical
Version: GNOME2.2.1 2.2.3.1
os_details: FreeBSD GNOME Project
Synopsis: Error on nautilus startuo
Bugzilla-Product: nautilus
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)
Description:
Description of Problem:
When I start the nautilus, I receive a error menssage: "Bus error" and
nautilus quit

Steps to reproduce the problem:
1. Start the nautilus

I use FreeBSD-5.1 and gnome-2.2.2.


Debugging Information:

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)...(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)...(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)...
[Switching to Process 670, Thread 1]
0x28d6c463 in poll () from /usr/lib/libc.so.5

Thread 1 (Process 670, Thread 1)

  • #0 poll
    from /usr/lib/libc.so.5
  • #1 _thread_kern_sched_state_unlock
    from /usr/lib/libc_r.so.5
  • #2 _thread_kern_scheduler
    from /usr/lib/libc_r.so.5
  • #3 ??




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-08-10 13:06 -------

The original reporter (rclenzi@t1000.com.br) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.

Comment 1 mwehner 2003-09-27 09:10:33 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 100709 ***