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 113875 - i got a lot of destop bugs
i got a lot of destop bugs
Status: RESOLVED DUPLICATE of bug 100709
Product: nautilus
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-05-27 21:03 UTC by cutey69boy
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description cutey69boy 2003-05-28 04:04:52 UTC
Package: nautilus
Severity: normal
Version: GNOME2.2.0 2.2.1
os_details: Gnome.Org
Synopsis: i got a lot of destop bugs 
Bugzilla-Product: nautilus
Bugzilla-Component: Accessibility
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)
Description:
Description of Problem:


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

Actual Results:


Expected Results:


How often does this happen?


Additional Information:



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)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x28c6f56c in __sys_poll () from /usr/lib/libc_r.so.4

Thread 1 (process 404, thread 1)

  • #0 __sys_poll
    from /usr/lib/libc_r.so.4
  • #1 _thread_kern_sched_state_unlock
    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.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-05-28 00:04 -------

The original reporter (cutey69boy@hotmail.com) 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, padraig.obriain@sun.com.

Comment 1 padraig.obriain 2003-05-28 07:31:25 UTC
Accessibility is not the correct component for this.
Comment 2 Elijah Newren 2003-07-04 19:41:38 UTC
It looks like the reporter is using FreeBSD and that this is a
duplicate of bug 100709.

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