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 163642 - Application "gnome-panel " (process 5467) has crashed due to a fatal error (Segment fault)
Application "gnome-panel " (process 5467) has crashed due to a fatal error (S...
Status: RESOLVED DUPLICATE of bug 134395
Product: general
Classification: Other
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Unknown User
Unknown User
Depends on:
Blocks:
 
 
Reported: 2005-01-11 11:13 UTC by libran_attitudes
Modified: 2005-01-11 16:33 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description libran_attitudes 2005-01-11 11:13:10 UTC
Distribution: Fedora Core release 1 (Yarrow)
Package: gnome-panel
Severity: normal
Version: GNOME2.4.0 unspecified
Gnome-Distributor: GNOME.Org
Synopsis: Application "gnome-panel " (process 5467) has crashed due to a fatal error (Segment fault)
Bugzilla-Product: gnome-panel
Bugzilla-Component: Window Menu Applet
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:
I get an error alert that says - 
Application "gnome-panel " (process 5467) has crashed due to a fatal
error (Segment fault).

Steps to reproduce the crash:
1.Login in as non-root .
2. Click on the red hat on the panel (menu).
3. See an ugly error poping up ur face.

Expected Results:
It should have shown the menu.

How often does this happen?
Each time i click on the start menu.

Additional Information:
This bug did not initially exist in my build. It has started 2 days ago.
I do not get this problem when i log in as root. It is only when i login
as a normal user i get this error.


Debugging Information:

Backtrace was generated from '/usr/bin/gnome-panel'

(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)...[Thread debugging using libthread_db
enabled]
[New Thread -1085230976 (LWP 5365)]
(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)...0x00233c32 in _dl_sysinfo_int80 ()
   from /lib/ld-linux.so.2

Thread 1 (Thread -1085230976 (LWP 5365))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strlen
    from /lib/tls/libc.so.6
  • #5 FAMDebugLevel
    from /usr/lib/libfam.so.0
  • #6 FAMMonitorFile
    from /usr/lib/libfam.so.0
  • #7 ??
    from /usr/lib/gnome-vfs-2.0/modules/libfile.so
  • #8 ??
  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-01-11 06:13 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "general".
   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 libran_attitudes@yahoo.com.
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 Elijah Newren 2005-01-11 16:33:11 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. 

Matches the stack trace in bug 149980, which has been marked as a duplicate of
134395.

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