GNOME Bugzilla – Bug 146134
Panel crashed when using XEmacs
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-panel Severity: critical Version: 2.2.0.1 Synopsis: Panel crashed when using XEmacs Bugzilla-Product: gnome-panel Bugzilla-Component: Panel BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: Panel crashed when I was working in XEmacs 21.4 (patch 12), and killed a line. It's quite likely that has nothing to do with it, since the panel has crashed randomly before. Steps to reproduce the problem: 1. 2. 3. Actual Results: Expected Results: How often does this happen? First time when working in XEmacs, but it has occured when working with Kylix 3 and other programs. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (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)...[New Thread 1086439840 (LWP 2180)] 0xffffe002 in ?? ()
+ Trace 47722
Thread 1 (Thread 1086439840 (LWP 2180))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-08 20:15 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-panel". Setting to default milestone for this product, '---' 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.
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 is a duplicate of bug 116065, which has been marked as a duplicate of bug 105745. *** This bug has been marked as a duplicate of 105745 ***