Why does my xfce4-panel keep crashing and immediately respawning itsel

forcedtopicksomething · 2023-07-26 10:44:29

f many times a day?

A month ago, I installed Linux (Debian 12) on my PC. XFCE for the DE. Chicago95 theme.

Right from the start, and for this entire time, there has been a weird bug of some kind which makes the taskbar (xfce4-panel) visually "glitch out" visually, seemingly crashing, only to then immediately respawn itself again.

This happens many times a day, but I can never predict it by doing some action. It seems to happen entirely randomly.

When it happens, it annoys me for a couple of seconds and often causes major confusion by reordering the opened window groups in the taskbar slightly.

Initially, I kept running `sudo journalctl -n 100` right after it happened and scrolled down to the bottom to see if there was anything logged. There never was.

Then, the other day, somebody told me about the file `~/.xsession-errors`. This file *does* contain some potentially relevant stuff:

(xfce4-panel:1492): libtasklist-CRITICAL **: 00:23:19.508: tasklist-widget.c:3055 (xfce_tasklist_button_enter_notify_event): expression 'XFCE_IS_TASKLIST (child->tasklist)' failed.

(xfce4-panel:1492): libtasklist-CRITICAL **: 00:23:19.516: tasklist-widget.c:3055 (xfce_tasklist_button_enter_notify_event): expression 'XFCE_IS_TASKLIST (child->tasklist)' failed.

(xfce4-panel:1492): libtasklist-CRITICAL **: 00:23:19.524: tasklist-widget.c:3055 (xfce_tasklist_button_enter_notify_event): expression 'XFCE_IS_TASKLIST (child->tasklist)' failed.

(wrapper-2.0:1545): GLib-GObject-CRITICAL **: 00:23:20.124: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

The "**CRITICAL**" parts make me think that this must be xfce4-panel crashing. But *why*?!

I don't use a bunch of weird plugins in the taskbar/panels. I don't do anything weird or exotic. All I want is to use my GUI without constantly waiting for that "crashing and respawning" process which is slowly driving me insane.

I have asked many times on IRC but nobody knows. I have also searched a lot online but find nothing relevant.

Some possibly useful information about my system:

libxfce4panel-2.0-4/stable,now 4.18.2-1 amd64 [installed,automatic]
xfce4-panel/stable,now 4.18.2-1 amd64 [installed,automatic]
xfce4/stable,now 4.18 all [installed,automatic]

There are no further updates. I am fully up to date.

Why does it keep doing this, and what can I do about it to make it stop?

PS: Please don't tell me to use a different DE since Gnome and KDE are both worse, and Chicago95 only works with Xfce. I have already invested so much in getting everything set up for Xfce. I just want it to stop doing this.

Tamaranch · 2023-07-26 14:09:43

Would you be able to extract a backtrace from one of the coredumps generated by these crashes?
See https://wiki.archlinux.org/title/Core_d … _core_dump

forcedtopicksomething · 2023-07-26 14:28:25

Tamaranch wrote:

Would you be able to extract a backtrace from one of the coredumps generated by these crashes?
See https://wiki.archlinux.org/title/Core_d … _core_dump

No. As I run Debian, I have no "coredumpctl" binary. (Nor did I know about this being a thing.)

I don't understand how this can be a thing for me and me only. Usually, at least I find discussions online with somebody *asking* about my problem (even if there is no answer)...

Tamaranch · 2023-07-26 14:36:42

Debian is not Devuan, it's systemd based, and if you have journalctl, you should have coredumpctl.

forcedtopicksomething · 2023-07-27 09:18:19

Tamaranch wrote:

Debian is not Devuan, it's systemd based, and if you have journalctl, you should have coredumpctl.

Well, I don't. It's a special package which I don't have. Is it strictly necessary to send a core dump? I'm worried about privacy as well.

Tamaranch · 2023-07-27 09:46:37

Well, that's up to you. If you don't want to install the basic tools to debug your problem, or share data, I don't see anything else to add.

forcedtopicksomething · 2023-07-27 17:46:31

Tamaranch wrote:

Well, that's up to you. If you don't want to install the basic tools to debug your problem, or share data, I don't see anything else to add.

I already gave the error log. But you seem to be asking for a wealthy of private information for no reason, making it impossible for me to get this bug fixed as I can't send private information out from my machine.

ToZ · 2023-07-27 21:58:56

forcedtopicksomething wrote:

wealthy of private information for no reason,

Actually, he is asking for system debug information to help troubleshoot the problem. Unfortunately, you're in a position where you need to decide between providing this information for assistance, or not getting the assistance you are looking for.

mint4all · 2023-07-28 01:22:06

ToZ wrote:

forcedtopicksomething wrote:
wealthy of private information for no reason,
Actually, he is asking for system debug information to help troubleshoot the problem. Unfortunately, you're in a position where you need to decide between providing this information for assistance, or not getting the assistance you are looking for.

Greetings!

Perhaps its time to step back for a moment ... A long time ago, I was told that "No Ticky - No Washy" should be respected when asking for help. I have the UTMOST respect for ToZ and his collaborators that go to great length to help others (such as myself) in fixing things. So to put it plainly, if you the OP won't provide the info requested, you won't get the help you ask for.

However, there are other sides to the OPs "problem" that should be asnwered: is this system even stable? Has it been tested with a bona-fide, properly maintained theme, ie "GreyBird"? Are ALL of the "Chicago95"-theme requirements installed, ie the NotoSans fonts? The theme's Github repo @ https://github.com/grassmunk/Chicago95 itself does not even mention Xfce 4.18 as being supported. With v4.18 being a major upgrade to support the latest GTK3-internals, what assurances are there that it all works ok? The theme's documentation goes as far as v4.16. The theme's .css file goes as far as v4.14 --- I rest my case. When exploring new/old themes, one often "ends up in the weeds" (i learned that!) That's what I observe is happening here. It attests to XFCE's stability that the system runs as well as it does, and even recovers from the crash(es) ... My suggestion: start with a stable, supprted theme, then go from there.

Cheers, m4a

gogogadget · 2023-07-28 13:14:04

forcedtopicksomething wrote:

I already gave the error log. But you seem to be asking for a wealthy of private information for no reason, making it impossible for me to get this bug fixed as I can't send private information out from my machine.

You could use it and remove what you consider sensitive information before posting on the forum.
You could also use it for yourself and not share anything.

forcedtopicksomething · 2023-08-02 20:48:25

Well, I've now installed coredumpctl, waited for xfce4-panel to crash, noticed that it crashed, and verified that it was listed by coredumpctl. But even if I use --json, I still get a *massive* binary blob as output. Not plain text like the snippet I could see in the terminal. This file is gigantic and contains seemingly all information on my entire system. It would be both impractical and horrible for security to share it with anyone. Do you want me to run some kind of command that picks out the important/last part (as plain text)?

Tamaranch · 2023-08-02 20:55:50

Tamaranch wrote:

Would you be able to extract a backtrace from one of the coredumps generated by these crashes?
See https://wiki.archlinux.org/title/Core_d … _core_dump

forcedtopicksomething · 2023-08-02 23:24:06

                Module libsystemd.so.0 from deb systemd-252.12-1~deb12u1.amd64
                Stack trace of thread 1487:
                #0  0x00007f62e9df559a n/a (libtasklist.so + 0x959a)
                #1  0x00007f62ed363bb8 g_closure_unref (libgobject-2.0.so.0 + 0x15bb8)
                #2  0x00007f62ed37c1be g_signal_handlers_destroy (libgobject-2.0.so.0 + 0x2e1be)
                #3  0x00007f62ed36888d n/a (libgobject-2.0.so.0 + 0x1a88d)
                #4  0x00007f62ed36abb8 g_object_run_dispose (libgobject-2.0.so.0 + 0x1cbb8)
                #5  0x00007f62eda1e68d n/a (libgtk-3.so.0 + 0x21e68d)
                #6  0x00007f62ed921227 n/a (libgtk-3.so.0 + 0x121227)
                #7  0x00007f62ed3643b0 g_closure_invoke (libgobject-2.0.so.0 + 0x163b0)
                #8  0x00007f62ed377124 n/a (libgobject-2.0.so.0 + 0x29124)
                #9  0x00007f62ed37dbf5 g_signal_emit_valist (libgobject-2.0.so.0 + 0x2fbf5)
                #10 0x00007f62ed37ddbf g_signal_emit (libgobject-2.0.so.0 + 0x2fdbf)
                #11 0x00007f62edb740dd n/a (libgtk-3.so.0 + 0x3740dd)
                #12 0x00007f62ed36abb8 g_object_run_dispose (libgobject-2.0.so.0 + 0x1cbb8)
                #13 0x00007f62e9dfc1f8 n/a (libtasklist.so + 0x101f8)
                #14 0x00007f62ed3645a9 n/a (libgobject-2.0.so.0 + 0x165a9)
                #15 0x00007f62ed37dbbf g_signal_emit_valist (libgobject-2.0.so.0 + 0x2fbbf)
                #16 0x00007f62ed37ddbf g_signal_emit (libgobject-2.0.so.0 + 0x2fdbf)
                #17 0x00007f62eda1f95d gtk_menu_shell_activate_item (libgtk-3.so.0 + 0x21f95d)
                #18 0x00007f62eda1fc71 n/a (libgtk-3.so.0 + 0x21fc71)
                #19 0x00007f62ed890cb4 n/a (libgtk-3.so.0 + 0x90cb4)
                #20 0x00007f62ed3645a9 n/a (libgobject-2.0.so.0 + 0x165a9)
                #21 0x00007f62ed37d05e g_signal_emit_valist (libgobject-2.0.so.0 + 0x2f05e)
                #22 0x00007f62ed37ddbf g_signal_emit (libgobject-2.0.so.0 + 0x2fdbf)
                #23 0x00007f62edb697d4 n/a (libgtk-3.so.0 + 0x3697d4)
                #24 0x00007f62eda077de n/a (libgtk-3.so.0 + 0x2077de)
                #25 0x00007f62eda09296 gtk_main_do_event (libgtk-3.so.0 + 0x209296)
                #26 0x00007f62ed732815 n/a (libgdk-3.so.0 + 0x3c815)
                #27 0x00007f62ed78c702 n/a (libgdk-3.so.0 + 0x96702)
                #28 0x00007f62ed26a7a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9)
                #29 0x00007f62ed26aa38 n/a (libglib-2.0.so.0 + 0x54a38)
                #30 0x00007f62ed26acef g_main_loop_run (libglib-2.0.so.0 + 0x54cef)
                #31 0x00007f62eda08435 gtk_main (libgtk-3.so.0 + 0x208435)
                #32 0x00005608935e7003 main (xfce4-panel + 0x15003)
                #33 0x00007f62ece3b1ca __libc_start_call_main (libc.so.6 + 0x271ca)
                #34 0x00007f62ece3b285 __libc_start_main_impl (libc.so.6 + 0x27285)
                #35 0x00005608935e7561 _start (xfce4-panel + 0x15561)
                
                Stack trace of thread 1490:
                #0  0x00007f62ecf1003f __GI___poll (libc.so.6 + 0xfc03f)
                #1  0x00007f62ed26a9ae n/a (libglib-2.0.so.0 + 0x549ae)
                #2  0x00007f62ed26acef g_main_loop_run (libglib-2.0.so.0 + 0x54cef)
                #3  0x00007f62ed4c58f6 n/a (libgio-2.0.so.0 + 0x1188f6)
                #4  0x00007f62ed294cfd n/a (libglib-2.0.so.0 + 0x7ecfd)
                #5  0x00007f62ece9d044 start_thread (libc.so.6 + 0x89044)
                #6  0x00007f62ecf1d5fc __clone3 (libc.so.6 + 0x1095fc)
                
                Stack trace of thread 112603:
                #0  0x00007f62ece99da6 __futex_abstimed_wait_common64 (libc.so.6 + 0x85da6)
                #1  0x00007f62ece9c468 __pthread_cond_wait_common (libc.so.6 + 0x88468)
                #2  0x00007f62d34fc99f n/a (librsvg-2.so.2 + 0xfc99f)
                #3  0x00007f62d34fc3be n/a (librsvg-2.so.2 + 0xfc3be)
                #4  0x00007f62d36c2c92 n/a (librsvg-2.so.2 + 0x2c2c92)
                #5  0x00007f62d36c83f1 n/a (librsvg-2.so.2 + 0x2c83f1)
                #6  0x00007f62d36bebed n/a (librsvg-2.so.2 + 0x2bebed)
                #7  0x00007f62d3a31153 n/a (librsvg-2.so.2 + 0x631153)
                #8  0x00007f62ece9d044 start_thread (libc.so.6 + 0x89044)
                #9  0x00007f62ecf1d5fc __clone3 (libc.so.6 + 0x1095fc)
                
                Stack trace of thread 112601:
                #0  0x00007f62ece99da6 __futex_abstimed_wait_common64 (libc.so.6 + 0x85da6)
                #1  0x00007f62ece9c468 __pthread_cond_wait_common (libc.so.6 + 0x88468)
                #2  0x00007f62d34fc99f n/a (librsvg-2.so.2 + 0xfc99f)
                #3  0x00007f62d34fc3be n/a (librsvg-2.so.2 + 0xfc3be)
                #4  0x00007f62d36c2c92 n/a (librsvg-2.so.2 + 0x2c2c92)
                #5  0x00007f62d36c83f1 n/a (librsvg-2.so.2 + 0x2c83f1)
                #6  0x00007f62d36bebed n/a (librsvg-2.so.2 + 0x2bebed)
                #7  0x00007f62d3a31153 n/a (librsvg-2.so.2 + 0x631153)
                #8  0x00007f62ece9d044 start_thread (libc.so.6 + 0x89044)
                #9  0x00007f62ecf1d5fc __clone3 (libc.so.6 + 0x1095fc)
                
                Stack trace of thread 112605:
                #0  0x00007f62ece99da6 __futex_abstimed_wait_common64 (libc.so.6 + 0x85da6)
                #1  0x00007f62ece9c468 __pthread_cond_wait_common (libc.so.6 + 0x88468)
                #2  0x00007f62d34fc99f n/a (librsvg-2.so.2 + 0xfc99f)
                #3  0x00007f62d34fc3be n/a (librsvg-2.so.2 + 0xfc3be)
                #4  0x00007f62d36c2c92 n/a (librsvg-2.so.2 + 0x2c2c92)
                #5  0x00007f62d36c83f1 n/a (librsvg-2.so.2 + 0x2c83f1)
                #6  0x00007f62d36bebed n/a (librsvg-2.so.2 + 0x2bebed)
                #7  0x00007f62d3a31153 n/a (librsvg-2.so.2 + 0x631153)
                #8  0x00007f62ece9d044 start_thread (libc.so.6 + 0x89044)
                #9  0x00007f62ecf1d5fc __clone3 (libc.so.6 + 0x1095fc)
                
                Stack trace of thread 112607:
                #0  0x00007f62ece99da6 __futex_abstimed_wait_common64 (libc.so.6 + 0x85da6)
                #1  0x00007f62ece9c468 __pthread_cond_wait_common (libc.so.6 + 0x88468)
                #2  0x00007f62d34fc99f n/a (librsvg-2.so.2 + 0xfc99f)
                #3  0x00007f62d34fc3be n/a (librsvg-2.so.2 + 0xfc3be)
                #4  0x00007f62d36c2c92 n/a (librsvg-2.so.2 + 0x2c2c92)
                #5  0x00007f62d36c83f1 n/a (librsvg-2.so.2 + 0x2c83f1)
                #6  0x00007f62d36bebed n/a (librsvg-2.so.2 + 0x2bebed)
                #7  0x00007f62d3a31153 n/a (librsvg-2.so.2 + 0x631153)
                #8  0x00007f62ece9d044 start_thread (libc.so.6 + 0x89044)
                #9  0x00007f62ecf1d5fc __clone3 (libc.so.6 + 0x1095fc)
                
                Stack trace of thread 112604:
                #0  0x00007f62ece99da6 __futex_abstimed_wait_common64 (libc.so.6 + 0x85da6)
                #1  0x00007f62ece9c468 __pthread_cond_wait_common (libc.so.6 + 0x88468)
                #2  0x00007f62d34fc99f n/a (librsvg-2.so.2 + 0xfc99f)
                #3  0x00007f62d34fc3be n/a (librsvg-2.so.2 + 0xfc3be)
                #4  0x00007f62d36c2c92 n/a (librsvg-2.so.2 + 0x2c2c92)
                #5  0x00007f62d36c83f1 n/a (librsvg-2.so.2 + 0x2c83f1)
                #6  0x00007f62d36bebed n/a (librsvg-2.so.2 + 0x2bebed)
                #7  0x00007f62d3a31153 n/a (librsvg-2.so.2 + 0x631153)
                #8  0x00007f62ece9d044 start_thread (libc.so.6 + 0x89044)
                #9  0x00007f62ecf1d5fc __clone3 (libc.so.6 + 0x1095fc)
                
                Stack trace of thread 112602:
                #0  0x00007f62ece99da6 __futex_abstimed_wait_common64 (libc.so.6 + 0x85da6)
                #1  0x00007f62ece9c468 __pthread_cond_wait_common (libc.so.6 + 0x88468)
                #2  0x00007f62d34fc99f n/a (librsvg-2.so.2 + 0xfc99f)
                #3  0x00007f62d34fc3be n/a (librsvg-2.so.2 + 0xfc3be)
                #4  0x00007f62d36c2c92 n/a (librsvg-2.so.2 + 0x2c2c92)
                #5  0x00007f62d36c83f1 n/a (librsvg-2.so.2 + 0x2c83f1)
                #6  0x00007f62d36bebed n/a (librsvg-2.so.2 + 0x2bebed)
                #7  0x00007f62d3a31153 n/a (librsvg-2.so.2 + 0x631153)
                #8  0x00007f62ece9d044 start_thread (libc.so.6 + 0x89044)
                #9  0x00007f62ecf1d5fc __clone3 (libc.so.6 + 0x1095fc)
                
                Stack trace of thread 1488:
                #0  0x00007f62ecf1003f __GI___poll (libc.so.6 + 0xfc03f)
                #1  0x00007f62ed26a9ae n/a (libglib-2.0.so.0 + 0x549ae)
                #2  0x00007f62ed26aacc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc)
                #3  0x00007f62ed26ab11 n/a (libglib-2.0.so.0 + 0x54b11)
                #4  0x00007f62ed294cfd n/a (libglib-2.0.so.0 + 0x7ecfd)
                #5  0x00007f62ece9d044 start_thread (libc.so.6 + 0x89044)
                #6  0x00007f62ecf1d5fc __clone3 (libc.so.6 + 0x1095fc)
                
                Stack trace of thread 112608:
                #0  0x00007f62ece99da6 __futex_abstimed_wait_common64 (libc.so.6 + 0x85da6)
                #1  0x00007f62ece9c468 __pthread_cond_wait_common (libc.so.6 + 0x88468)
                #2  0x00007f62d34fc99f n/a (librsvg-2.so.2 + 0xfc99f)
                #3  0x00007f62d34fc3be n/a (librsvg-2.so.2 + 0xfc3be)
                #4  0x00007f62d36c2c92 n/a (librsvg-2.so.2 + 0x2c2c92)
                #5  0x00007f62d36c83f1 n/a (librsvg-2.so.2 + 0x2c83f1)
                #6  0x00007f62d36bebed n/a (librsvg-2.so.2 + 0x2bebed)
                #7  0x00007f62d3a31153 n/a (librsvg-2.so.2 + 0x631153)
                #8  0x00007f62ece9d044 start_thread (libc.so.6 + 0x89044)
                #9  0x00007f62ecf1d5fc __clone3 (libc.so.6 + 0x1095fc)
                
                Stack trace of thread 112606:
                #0  0x00007f62ece99da6 __futex_abstimed_wait_common64 (libc.so.6 + 0x85da6)
                #1  0x00007f62ece9c468 __pthread_cond_wait_common (libc.so.6 + 0x88468)
                #2  0x00007f62d34fc99f n/a (librsvg-2.so.2 + 0xfc99f)
                #3  0x00007f62d34fc3be n/a (librsvg-2.so.2 + 0xfc3be)
                #4  0x00007f62d36c2c92 n/a (librsvg-2.so.2 + 0x2c2c92)
                #5  0x00007f62d36c83f1 n/a (librsvg-2.so.2 + 0x2c83f1)
                #6  0x00007f62d36bebed n/a (librsvg-2.so.2 + 0x2bebed)
                #7  0x00007f62d3a31153 n/a (librsvg-2.so.2 + 0x631153)
                #8  0x00007f62ece9d044 start_thread (libc.so.6 + 0x89044)
                #9  0x00007f62ecf1d5fc __clone3 (libc.so.6 + 0x1095fc)
                ELF object binary architecture: AMD x86-64

Tamaranch · 2023-08-03 07:42:06

It doesn't look like any of the crashes already reported to my knowledge, so it's not going to be enough to investigate the problem. You'd have to provide a complete backtrace, with the panel's debug symbols. See
* https://wiki.debian.org/Debuginfod
* https://wiki.debian.org/DebugPackage

Also once you've opened the coredump in gdb, type `bt` as shown in the Arch wiki link above. This will give you a shorter, more detailed trace than the above.

Alternatively, you can share the coredump by uploading it somewhere and providing the link via PM...

forcedtopicksomething · 2023-08-03 09:05:34

Tamaranch wrote:

It doesn't look like any of the crashes already reported to my knowledge, so it's not going to be enough to investigate the problem. You'd have to provide a complete backtrace, with the panel's debug symbols. See
* https://wiki.debian.org/Debuginfod
* https://wiki.debian.org/DebugPackage
Also once you've opened the coredump in gdb, type `bt` as shown in the Arch wiki link above. This will give you a shorter, more detailed trace than the above.
Alternatively, you can share the coredump by uploading it somewhere and providing the link via PM...

Sorry. I was already *very* uncomfortable posting the above quote, so anything further is unthinkable.

Looks like yet another thing that will remain a major annoyance and won't be fixed because somehow it "only happens to me" and I'm asked for too much information about my system. I don't get how it isn't a known issue, or why the tons of information I provided above doesn't help.

Frankly, I find it disturbing when people are asked to upload all kinds of private information. If they don't know any better, they will just go along with it and not question it. When I was younger, I would've just uploaded the whole thing and violated my own privacy and security, as well as potentially others', if their information was made public through this.

forcedtopicksomething · 2023-08-03 09:08:48

(gdb) bt
#0  0x00007f62e9df559a in ?? () from /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libtasklist.so
#1  0x00007f62ed363bb8 in g_closure_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#2  0x00007f62ed37c1be in g_signal_handlers_destroy () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#3  0x00007f62ed36888d in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#4  0x00007f62ed36abb8 in g_object_run_dispose () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5  0x00007f62eda1e68d in ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
#6  0x00007f62ed921227 in ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
#7  0x00007f62ed3643b0 in g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x00007f62ed377124 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9  0x00007f62ed37dbf5 in g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x00007f62ed37ddbf in g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x00007f62edb740dd in ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
#12 0x00007f62ed36abb8 in g_object_run_dispose () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x00007f62e9dfc1f8 in ?? () from /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libtasklist.so
#14 0x00007f62ed3645a9 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x00007f62ed37dbbf in g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x00007f62ed37ddbf in g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#17 0x00007f62eda1f95d in gtk_menu_shell_activate_item () from /lib/x86_64-linux-gnu/libgtk-3.so.0
#18 0x00007f62eda1fc71 in ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
#19 0x00007f62ed890cb4 in ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
#20 0x00007f62ed3645a9 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#21 0x00007f62ed37d05e in g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#22 0x00007f62ed37ddbf in g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#23 0x00007f62edb697d4 in ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
#24 0x00007f62eda077de in ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
#25 0x00007f62eda09296 in gtk_main_do_event () from /lib/x86_64-linux-gnu/libgtk-3.so.0
#26 0x00007f62ed732815 in ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
#27 0x00007f62ed78c702 in ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
#28 0x00007f62ed26a7a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007f62ed26aa38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x00007f62ed26acef in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
--Type <RET> for more, q to quit, c to continue without paging--
#31 0x00007f62eda08435 in gtk_main () from /lib/x86_64-linux-gnu/libgtk-3.so.0
#32 0x00005608935e7003 in main ()
(gdb)

Tamaranch · 2023-08-03 09:13:23

Adding debug symbols to report a truly usable trace won't impact your privacy in any way, it'll just require a little effort on your part. Again, it's up to you.

forcedtopicksomething · 2023-08-04 14:19:04

Tamaranch wrote:

Adding debug symbols to report a truly usable trace won't impact your privacy in any way, it'll just require a little effort on your part. Again, it's up to you.

What you are asking for is massive amounts of highly sensitive private data. It's irresponsible and insulting. Please stop pretending as if "it's up to me" and I'm somehow "being difficult and not really wanting help" when you are asking for something which is impossible to provide. If you can't or won't help, don't act as if it's "my fault" and I'm "just not putting in the effort". It's got nothing whatsoever to do with the amount of effort.

CwF · 2023-08-04 16:31:48

The obvious culprit seems to be the Chicago95 theme.

Simply change themes and run to test stability. It's a Y/N issue.
It is not Debian 12 or XFCE 4.18 that's the problem. I had pre release instances with 6 month uptimes and haven't seen this.

Usually .xsession-errors will show theme issues.

forcedtopicksomething · 2023-08-07 12:04:39

From ~/.xsession-errors, right after it crashed the last time:

	(xfwm4:1487): xfwm4-WARNING **: 13:50:15.204: unmanaged net_wm_state (window 0x4e0000d, atom "_NET_WM_STATE_STAYS_ON_TOP")

	(wrapper-2.0:1579): LIBDBUSMENU-GLIB-WARNING **: 13:50:15.293: Unable to replace properties on 0: Error getting properties for ID

	*** THIS POINT IS WHERE THE LAST CRASH HAPPENED ***

	(wrapper-2.0:1593): GLib-GObject-WARNING **: 13:57:23.399: ../../../gobject/gsignal.c:2772: instance '0x55dd258efe70' has no handler with id '60'

	(wrapper-2.0:1595): GLib-GObject-CRITICAL **: 13:57:23.400: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

	** (wrapper-2.0:22716): WARNING **: 13:57:25.991: No outputs have backlight property

Last edited by forcedtopicksomething (2023-08-07 12:04:59)

CwF · 2023-08-07 15:23:58

	(wrapper-2.0:1579): LIBDBUSMENU-GLIB-WARNING **: 13:50:15.293: Unable to replace properties on 0: Error getting properties for ID

You can look at 'Task Manager' or use ps to identify process 1579, and that number can change. It may or may not be the issue. Whatever element it is, I'd start the audit there. I scanned a few deb12.1/4.18 systems and don't have any occurrence of "LIBDBUS"
I'll admit the -errors log is a tad noisier than prior versions.

Last edited by CwF (2023-08-07 15:24:55)

forcedtopicksomething · 2023-08-07 16:28:57

CwF wrote:

You can look at 'Task Manager' or use ps to identify process 1579

Well, whatever process that was, it's long gone now...

CwF wrote:

I scanned a few deb12.1/4.18 systems and don't have any occurrence of "LIBDBUS"

apt list --installed | grep libdbus

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libdbus-1-3/stable,now 1.14.8-2~deb12u1 amd64 [installed,automatic]
libdbus-glib-1-2/stable,now 0.112-3 amd64 [installed,automatic]
libdbusmenu-glib4/stable,now 18.10.20180917~bzr492+repack1-3 amd64 [installed,automatic]
libdbusmenu-gtk3-4/stable,now 18.10.20180917~bzr492+repack1-3 amd64 [installed,automatic]
libdbusmenu-qt5-2/stable,now 0.9.3+16.04.20160218-2+b1 amd64 [installed,automatic]

Unsure how to check what caused those to be installed.

But are you sure the relevant thing isn't what's *below* the "*** THIS POINT IS WHERE THE LAST CRASH HAPPENED ***" text (which I added to make it clear)? The stuff that happened above was 7 minutes earlier... Can that really be relevant? I provided it only for context.

CwF · 2023-08-07 16:50:12

forcedtopicksomething wrote:

CwF wrote:
You can look at 'Task Manager' or use ps to identify process 1579
Unsure how to check what caused those to be installed.
.

I was unclear, I scanned the .xsession-errors and found no mention.
The pid will change, a respawn may be a new pid, you'll have to watch. Note the pids of all panels before the issue, and match the later error.

forcedtopicksomething · 2023-08-08 15:23:24

Well, I took a screenshot of Task manager with "panel" typed into the filter field, and then looked again in the error log after it happened just now, but there is no "1494" PID there. However, "1564" is libpulseaudio-plugin.so:

/usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libpulseaudio-plugin.so 8 14680076 pulseaudio PulseAudio Plugin Adjust the audio volume of the PulseAudio sound system

Does that help at all?

(xfce4-panel:1494): libtasklist-CRITICAL **: 17:14:17.917: tasklist-widget.c:3055 (xfce_tasklist_button_enter_notify_event): expression 'XFCE_IS_TASKLIST (child->tasklist)' failed.

(xfce4-panel:1494): libtasklist-CRITICAL **: 17:14:17.931: tasklist-widget.c:3055 (xfce_tasklist_button_enter_notify_event): expression 'XFCE_IS_TASKLIST (child->tasklist)' failed.

(xfce4-panel:1494): libtasklist-CRITICAL **: 17:14:17.960: tasklist-widget.c:3055 (xfce_tasklist_button_enter_notify_event): expression 'XFCE_IS_TASKLIST (child->tasklist)' failed.

(wrapper-2.0:1564): GLib-GObject-CRITICAL **: 17:14:22.303: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

It's frustrating that this logfile doesn't use any kind of timestamps, so you have to be really quick or it soon gets messy and you have no idea where it happened.

Last edited by forcedtopicksomething (2023-08-08 15:24:25)

CwF · 2023-08-09 16:59:07

Chasing bugs isn't always easy!

Don't forget to throw out the stubborn and test variations in themes and panels.
The finding may be indirect, as in "if I don't do this, it doesn't hurt"

It maybe means nothing, but I notice your pids are numbered higher than I see. My wrapper/panel pids are usually in the 6-700's.

Xfce Forum

Sub domains

#1 2023-07-26 10:44:29

Why does my xfce4-panel keep crashing and immediately respawning itsel

#2 2023-07-26 14:09:43

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#3 2023-07-26 14:28:25

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#4 2023-07-26 14:36:42

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#5 2023-07-27 09:18:19

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#6 2023-07-27 09:46:37

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#7 2023-07-27 17:46:31

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#8 2023-07-27 21:58:56

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#9 2023-07-28 01:22:06

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#10 2023-07-28 13:14:04

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#11 2023-08-02 20:48:25

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#12 2023-08-02 20:55:50

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#13 2023-08-02 23:24:06

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#14 2023-08-03 07:42:06

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#15 2023-08-03 09:05:34

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#16 2023-08-03 09:08:48

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#17 2023-08-03 09:13:23

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#18 2023-08-04 14:19:04

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#19 2023-08-04 16:31:48

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#20 2023-08-07 12:04:39

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#21 2023-08-07 15:23:58

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#22 2023-08-07 16:28:57

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#23 2023-08-07 16:50:12

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#24 2023-08-08 15:23:24

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

#25 2023-08-09 16:59:07

Re: Why does my xfce4-panel keep crashing and immediately respawning itsel

Board footer