So here I am again.
With this post I want to create some Arch troubleshooting guideline, I start the conversation with the problem I found and I was able to fix.
In one of last topics I said I found some updates in Arch that broke a sofware compatibility.
Two days ago I tried switch my workflow to an Arch Linux virtual machine and I found the same problem on the software, after activating the 3d graphic card acceleration.
So I was wondering if it’s a bug or what, since after almost 10 months ago it’s not fixed yet.
The problem I had was using Kreya (as api client) and IPTVnator (as multimedia broadcaster), both this software are using libwebgtk and on both of the softwares I had a blank window without any controls.
I did not saw this problem with Debian or Linux Lite because they are using an old library version.
I went deeply and looking at system logs there was some dumps in gtk libraries and javascript core frameworks. I understood that last updates (since gtk version 4.3) they add a feature for improve hardware acceleration. It seems this improvment have some issues with Nvidia cards, I own an RTX 3070ti, I fixed my problem by disabling this feature.
Here am I again, sorry for my absence but I was quite busy ~~
I’m having another problem on my Arch installation since yesterday: the file ~/.xsession-errors on my home folder is huge increasing, almost half megabyte for minute.
The issue is a cryptic log that is spamming the file ~~ each 200ms: here is a small portion of the file:
From the log I understood is some xfwm component that is trying to access to a database table which does not exists yet.
I want to resolve this problem, does someone come into this recently? Can someone help me identify which is the cause?
For now I created a startup script that will delete the log file at user login so I don’t have problems because the file does not exists, but this is not the correct way for solve this problem.
GLib-CRITICAL: This is a runtime error in a program using the GLib library. GLib is used in many Linux desktop environments, including Xfce and its components like xfwm.
g_hash_table_lookup: This is a GLib function. It looks up a key in a hash table and returns the corresponding value. If the hash table is invalid or uninitialized, it fails.
assertion 'hash_table != NULL' failed: The error means g_hash_table_lookup was called with a NULL (non-existent) hash table. This looks like a programming error, it’s likely the developer didn’t check whether the hash table was initialized before using it or other related issue.
Consider a less bleeding-edge rolling distro like Void Linux (features stable rolling release), Tumbleweed (also stable rolling) or Kali Linux (without pentesting tools, would be in the middle between Arch and those other two).
Thanks @hydn for the detailed explanation, the problem is I neither don’t know which piece of software is causing this log, I suspect it’s xfwm but I’m not sure.
The only thing I did was upgrading the system, for test if it’s a fresh software problem maybe some other Arch users in this forum recently updated their system they might encountered the same bug.
I’m afraid to open a bug report, I’m not sure it’s a bug or if it’s some bad configuration on my system… the odd thing is I notice only yesterday afternoon that log file was becoming huge.
@toadie yes I check the logs, there was nothing sospicious, that line was written in log many times every seconds, journalctl was silent, and grep did not filtering nothing.
Btw I found the problem and I was able to fix it:
The problem was the custom compositor Picom (this package) that is not updated for a while now and it’s becoming obsolete.
All I did was disabling the compositor, check the size of ~/.xsession-errors file that was stable and at that point I was sure and I launch the command yay -Rnf picom, followed by removing picom startup script.
After all of that all my system went ok and ~/.xsession-errors file size is now tiny, I will miss a bit the fancy window composition :] but in the end who cares.
Btw I was pretty sure it was not a bug in xfwm because I did not found any recent google result and my problem was too specific.
Sorry guys if I wasted a bit of your time but thanks for your help, I really appreciated.
)
