Yes, thank you; and I did indeed read your comment. However, I couldn't figure out how to obtain a backtrace using the link you gave me, because the link doesn't seem to cover these aforementioned situations:
* ... since this happens immediately on reboot and I don't manually run gnome-panel, how should I run it [gdb] to get the backtrace? * I managed to reproduce it [the bug] by being connected at reboot via ethernet, then removing the ethernet cable so that the password prompt window appeared. At this point I tried to attach gdb, but I could not send keyboard input to an open console when I selected it - all keyboard input went to the gnome-keyring window, no matter where the mouse pointer was or what I clicked on. I'm still not convinced a backtrace would be of any help, since gnome- panel does not actually crash, and the purpose of a backtrace seems to be when an application has crashed. Please correct me if I've misunderstood! I figure an strace would be probably be more useful, but I'm not sure how to attach it to the relevant process since I don't have keyboard control at the point where the window appears. -- gnome-panel freezes during keyring password entry https://bugs.launchpad.net/bugs/189777 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
