Hey, turtles are good programming practice. I’m getting this bug too, as of today. All the symptoms described are there for me as well, although I never tried restarting X. Instead, I restarted the process with “killall gnome-panel.” After doing that once or twice, the panel stopped automatically coming back (odd!), so I ran it from a terminal to reproduce the crash. Sadly, the panel output didn’t give me anything useful.
I made a backtrace. Keep in mind that the panel froze up and I had to kill the process, so that is what’s represented in the log. (Everything up to the “Program received signal SIGTERM” line is the output I got upon starting the process. Clicking the clock applet crashed the panel, but didn’t produce any output. Everything else is output I received upon or after killing the process.) (...Oh, and the panel was present, but unresponsive, even after I killed its process. It remained until I closed GDB, over its protests that a program was still running. Is that normal?) I’m using Ubuntu 8.10, “Intrepid Ibex,” with everything up-to-date. (I’d give you the time in UTC, but my panel clock is broken... waaaah...) It might be relevant that I use Mousetweaks for its “delay click” function, and that it stopped working right around when I found this bug. (I don’t know _why_ that would be relevant... I’ll restart X and see if Mousetweaks works again.) Thanks! ** Attachment added: "Hmm, I guess this isn’t what they meant by “feature freeze” ;)" http://launchpadlibrarian.net/17290621/gdb-gnome-panel.txt -- clicking the panel clock will freeze the panel https://bugs.launchpad.net/bugs/262372 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
