GNOME Bugzilla – Bug 307371
gnome not not initializing properly
Last modified: 2005-12-30 01:36:54 UTC
Distribution: Debian 3.1 Package: gnome-panel Severity: blocker Version: GNOME2.10.0 2.10.x Gnome-Distributor: Ubuntu Synopsis: gnome not not initializing properly Bugzilla-Product: gnome-panel Bugzilla-Component: Panel Bugzilla-Version: 2.10.x BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: first bootup, mouse support failed, rebooted to fix the issue. Gnome-panel would not initalize correctly, even after numerous attempts to correct with killall command in terminal. would get error message about workspace applets not initalizing properly, delete or continue, both buttons unuseable. Steps to reproduce the crash: 1. failed initialization of Gnome-panel 2. constantly have to force quit question box about workspace applets on bottom panel. 3. reconfigured bottom panel, gnome panel terminates unexpectantly Expected Results: updtaed release of gnome-panel with some sort of error-correction How often does this happen? gnome-panel fails to initialize often, have ot restart wth killall command in terminal Additional Information: 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 -1222519328 (LWP 7783)] (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 60892
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-06-12 12:47 UTC ------- 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 efwis@netins.net.
*** This bug has been marked as a duplicate of 137308 ***
Hrm... This was supposed to be fixed, but it's not. Could you please install the gnome-panel-dbg package and paste a new stack trace if it occurs again? Thanks,
if I am reading the infor correctly, I need to make the crash happen again, unfortuntely it happened before I read the info. just a little bit over an hour ago. It only happens as startup when it does happen, how would I get this info for you?
Ed: sorry for the late answer. Once you have installed gnome-panel-dbg, wait for the crash to happen again and copy the stack trace from bug-buddy here. Thanks
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!