GNOME Bugzilla – Bug 172384
Panel crashed when adding third new custom launcher component to a new drawer.
Last modified: 2005-04-01 18:18:10 UTC
Distribution: Debian 3.1 Package: gnome-panel Severity: critical Version: GNOME2.10.0 2.10.x Gnome-Distributor: Ubuntu Synopsis: Panel crashed when adding third new custom launcher component to a new drawer. Bugzilla-Product: gnome-panel Bugzilla-Component: Panel Bugzilla-Version: 2.10.x BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: Panel crashed when adding the third new custom launcher component to a new drawer. Steps to reproduce the crash: 1. Create a new drawer. 2. Add a custom launcher, then another; still OK. 3. Add a third custom launcher, then it should crash. Expected Results: Crash (maybe). How often does this happen? Only tried it once; will try again. Additional Information: I'll update this report if there is a way to do that. Thank you, Joe Carchidi (508)655-8667 Carchidi@MSN.com Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (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) [Thread debugging using libthread_db enabled] [New Thread -1221975328 (LWP 9571)] [New Thread -1232888912 (LWP 10846)] [New Thread -1224315984 (LWP 9644)] (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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 57608
Thread 3 (Thread -1224315984 (LWP 9644))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-01 13:14 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-panel". 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 Carchidi@MSN.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.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but the maintainers are looking for more information. Could you please answer the questions in the other report? *** This bug has been marked as a duplicate of 171014 ***