Just how can I figure out what is creating my gnome-panel to freeze?

Around daily my gnome-panel ices up.

Just how can I generate some type of debug details to:

  • Identify what is creating the freeze or
  • Submit a bug or see if its an existing bug

When gdb is affixed to gnome-panel and also the bug happens I can not get a pile trace out of gdb.

Reading symbols from /lib/libbz2.so.1.0...(no debugging symbols found)...done.
Loaded symbols for /lib/libbz2.so.1.0
0x00007f7cefe10f48 in poll () from /lib/libc.so.6
(gdb) c


The "^ C" is to show that as soon as the bug takes place gdb quits replying to Ctrl+ c and also kill -INT.

2019-05-07 00:34:05
Source Share
Answers: 2

The talk about this bug report on the very same concern first factor the press reporter to a wiki web page qualified Debugging a Program Crash and afterwards to a web page defining how to get a backtrace. Probably those will certainly aid you get the debugging details you require.

I addressed a question about a similar problem with a workaround that might aid you. It goes like this :

  1. Create a manuscript called postponed - gnome - panel.sh in your house directory site and also mark it as executable.

  2. Modify the manuscript to resemble this :

    #! /bin/bash
    sleep 3 && gnome-panel &
  3. Then modify/ usr/share/applications/ gnome - panel.desktop to make sure that exec=bash /home/<user>/delayed-gnome-panel.sh.

2019-05-08 21:26:04

Attach to the panel after it's frozzen.

$ gdb --pid=`pidof gnome-panel`
(gdb) bt full

Also see to it you have the essential debugging icons mounted. At the very least libglib2.0 - 0 - dbg and also libgtk2.0 - 0 - dbg.

2019-05-08 16:42:58