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 124869 - fatal error, segmentation fault
fatal error, segmentation fault
Status: RESOLVED DUPLICATE of bug 100272
Product: nautilus
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-10-17 20:09 UTC by ken.mcallister
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description ken.mcallister 2003-10-17 21:00:59 UTC
Package: nautilus
Severity: normal
Version: 2.0.5
Synopsis: fatal error, segmentation fault
Bugzilla-Product: nautilus
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:

I am  using KDE desktop

I transfer some files to floppy.  I press Ctl-W.  Three out of five
windows closed.  Error message:  Fatal error, segmentation fault
Steps to reproduce the problem:
1.   I  put BugBuddy in background and bring the  remaining Nautilus
windows forward.  They are blank of detail.  They can be resized and
shrunk but not closed

2. I tried running  a second instance of Nautilus.  An error message
screen appears.  It is blank of detail.  It can be resized and shrunk
but not closed

3  Process table can't be copied and pasted


Debugging Information:

Backtrace was generated from '/usr/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)...
0x40cda739 in wait4 () from /lib/i686/libc.so.6
  • #0 wait4
    from /lib/i686/libc.so.6
  • #1 sys_sigabbrev
    from /lib/i686/libc.so.6
  • #2 waitpid
    from /lib/i686/libpthread.so.0
  • #3 gnome_scores_display_with_pixmap
    from /usr/lib/libgnomeui-2.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-10-17 17:00 -------

The original reporter (ken.mcallister@clear.net.nz) 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-10-18 14:25:54 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 100272 ***