You are not logged in.
Pages: 1
Hello everyone,
I have recently made a switch to arch distro, and am using Awesome WM. I used to be able to change graphical appearance (mouse cursor etc.) via the use of lxappearance. However now I cannot turn it on and when i try to run it via terminal the only message I get is
[1] 24574 segmentation fault (core dumped) lxappearance
The number itself varies from run to run. I tried to run it as sudo to see if it gives a different behavior and I get
** (lxappearance:24856): WARNING **: 09:58:39.420: lxappearance.c:67: Failed to connect to the session message bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead
[1] 24846 segmentation fault sudo lxappearance
I tried reinstalling lxappearance via pacman, I've also tried different versions via yay (gtk2 and gtk3) as well as tried to build it from the lxappearance website itself. I am guessing it's something stupid, thank you in advance for your time.
Last edited by Sv7n (2021-03-22 14:27:54)
Offline
Likely last link in my signature.
Offline
Thank you for you response! I have .xinitrc file in my home dir it looks like this:
I've understood little from http://wiki.archlinux.org/index.php/Xinit#xinitrc, I'm guessing my monkey brain is to blame. As mentioned in a note one has to include the last if block from /etc/X11/xinit/xinitrc, in my .xinitrc this is the case. Other than that I'm not sure what I am meant to put in there.
Last edited by Sv7n (2021-03-22 12:45:23)
Offline
That xinitrc has the session relevant bits, but won't start the awesome WM.
If that's not the entire file, please post the entire file.
echo $DBUS_SESSION_BUS_ADDRESS
loginctl session-status
Also please use code tags when posting shell IO or file contents.
Offline
That was the entire content of .xinitrc. For DBUS_SESSION_BUS_ADDRESS I get
unix:path=/run/user/1000/bus
while for loginctl session-status I get
Thank you for your help.
Offline
You're getting an active session that you start w/ lightdm (your xinitrc is irrelevant) and DBUS_SESSION_BUS_ADDRESS is fine.
So the warning from lxappearance is bogus. Let's check the actual coredump, "man coredumpctl" & https://wiki.archlinux.org/index.php/Co … _core_dump
Offline
Oh wow, that makes more sense now. I ran
coredumpctl
list to get PID (5131) and then got the core dump with
coredumpctl info 5131
to get
But from that I understand little to nothing, libglib-2.0 looks a bit dodgy with these "n/a"'s but at this point I am just guessing.
Offline
The symbol string is just not available in the library, that's "normal".
It crashes when trying to read some ini file, presumingly icon related.
strace
…
…
sudo lxappearance
Please just don't sudo it…?
Offline
I am having the exact same error... I'll follow along to see what happens. Thanks!
FWIW... here's my coredump (most recent)
coredumpctl info 2801
PID: 2801 (lxappearance)
UID: 1000 (mark)
GID: 1000 (mark)
Signal: 11 (SEGV)
Timestamp: Mon 2021-03-22 07:01:12 MDT (15min ago)
Command Line: lxappearance
Executable: /usr/bin/lxappearance
Control Group: /user.slice/user-1000.slice/session-2.scope
Unit: session-2.scope
Slice: user-1000.slice
Session: 2
Owner UID: 1000 (mark)
Boot ID: 9534c352a9894694a74bbe323515a613
Machine ID: 644ee4914af140559c07b0163ffb9a66
Hostname: ArchLinux
Storage: /var/lib/systemd/coredump/core.lxappearance.1000.9534c352a9894694a74bbe3235>
Message: Process 2801 (lxappearance) of user 1000 dumped core.
Stack trace of thread 2801:
#0 0x00007fddb24d0102 n/a (libglib-2.0.so.0 + 0x4c102)
#1 0x00007fddb24d0673 n/a (libglib-2.0.so.0 + 0x4c673)
#2 0x00007fddb24d08e1 n/a (libglib-2.0.so.0 + 0x4c8e1)
#3 0x00007fddb24d09c6 g_key_file_load_from_file (libglib-2.0.so.0 + 0x4c9c>
#4 0x00005597c33fc910 load_icon_themes_from_dir (lxappearance + 0x7910)
#5 0x00005597c33fcc5a icon_theme_init (lxappearance + 0x7c5a)
#6 0x00005597c33fa337 main (lxappearance + 0x5337)
#7 0x00007fddb2141b25 __libc_start_main (libc.so.6 + 0x27b25)
#8 0x00005597c33fa67e _start (lxappearance + 0x567e)
Stack trace of thread 2802:
#0 0x00007fddb220e37f __poll (libc.so.6 + 0xf437f)
#1 0x00007fddb252ddef n/a (libglib-2.0.so.0 + 0xa9def)
#2 0x00007fddb24d56d1 g_main_context_iteration (libglib-2.0.so.0 + 0x516d1)
#3 0x00007fddb24d5722 n/a (libglib-2.0.so.0 + 0x51722)
#4 0x00007fddb2506241 n/a (libglib-2.0.so.0 + 0x82241)
#5 0x00007fddb187d299 start_thread (libpthread.so.0 + 0x9299)
#6 0x00007fddb2219053 __clone (libc.so.6 + 0xff053)
Stack trace of thread 2806:
PID: 2801 (lxappearance)
UID: 1000 (mark)
GID: 1000 (mark)
Signal: 11 (SEGV)
Timestamp: Mon 2021-03-22 07:01:12 MDT (15min ago)
Command Line: lxappearance
Executable: /usr/bin/lxappearance
Control Group: /user.slice/user-1000.slice/session-2.scope
Unit: session-2.scope
Slice: user-1000.slice
Session: 2
Owner UID: 1000 (mark)
Boot ID: 9534c352a9894694a74bbe323515a613
Machine ID: 644ee4914af140559c07b0163ffb9a66
Hostname: ArchLinux
Storage: /var/lib/systemd/coredump/core.lxappearance.1000.9534c352a9894694a74bbe3235>
Message: Process 2801 (lxappearance) of user 1000 dumped core.
Stack trace of thread 2801:
#0 0x00007fddb24d0102 n/a (libglib-2.0.so.0 + 0x4c102)
#1 0x00007fddb24d0673 n/a (libglib-2.0.so.0 + 0x4c673)
#2 0x00007fddb24d08e1 n/a (libglib-2.0.so.0 + 0x4c8e1)
#3 0x00007fddb24d09c6 g_key_file_load_from_file (libglib-2.0.so.0 + 0x4c9c>
#4 0x00005597c33fc910 load_icon_themes_from_dir (lxappearance + 0x7910)
#5 0x00005597c33fcc5a icon_theme_init (lxappearance + 0x7c5a)
#6 0x00005597c33fa337 main (lxappearance + 0x5337)
#7 0x00007fddb2141b25 __libc_start_main (libc.so.6 + 0x27b25)
#8 0x00005597c33fa67e _start (lxappearance + 0x567e)
Stack trace of thread 2802:
#0 0x00007fddb220e37f __poll (libc.so.6 + 0xf437f)
#1 0x00007fddb252ddef n/a (libglib-2.0.so.0 + 0xa9def)
#2 0x00007fddb24d56d1 g_main_context_iteration (libglib-2.0.so.0 + 0x516d1)
#3 0x00007fddb24d5722 n/a (libglib-2.0.so.0 + 0x51722)
lines 1-34/73 43%
Feell free to ignore this, unless you need a reference re: commonality.
Pax vobiscum,
Mark Rabideau - http://many-roads.com
spectrwm, i3, bspwm, dwm ~ Reg. Linux User #449130
"For every complex problem there is an answer that is clear, simple, and wrong." H. L. Mencken
Offline
'key - let's assume it's not just sudo, it really crashes and the sudo+session error was already a mitigation effort:
strace lxappearance > /tmp/lxappearance.strace 2>&1
and post that file.
Offline
I thought using sudo on it was not the right way to go, I got desperate and though "hey maybe this is it", it was giving me seg faults before I tried sudo. After running
strace lxappearance > /tmp/lxappearance.strace 2>&1
i got
I can see
access("/usr/share/icons", W_OK) = -1 EACCES (Permission denied)
this looks bad.
Offline
No, it just checks wether it can write. The crash happens when reading /usr/share/icons/Bibata-Modern-Classic/index.theme, so please upload that file (do NOT copy and paste it from a text editor)
Offline
I'm guessing by upload u mean
curl -F 'f:1=<-' ix.io < index.theme
this is what i get
I have a gb keyboard which I set a while ago via
sudo setxkbmap -layout gb
Last edited by Sv7n (2021-03-22 13:47:52)
Offline
There's as tray blank in the [ar] line and a weird "sr@Lat"
To pre-check, what if you move away all "/usr/share/icons/Bibata-*" directories (you don't have to delete them, but get them out of /usr/share/icons)
Offline
I moved all Bibata-* directories to ~/dodgyicons for now. lxappearence still gives seg fault (with coredump), running coredumpctl on that PID gives me
from
strace lxappearance > /tmp/lxappearance.strace 2>&1
i get
Offline
Just crashes at the breeze icons, so the bug is probably somehwere before any of this and only causes and overflow here.
I'd start by moving all but hi/locolor icons away. If it starts, re-add your icons gradually.
You can bisect this by re-adding half the themes, if good, re-add haf of the rest, otherwise remove half of the themes you just added to figure which half holds the bad theme (if there's a bad theme)
Offline
It works, thank you a lot!
I've removed everything then it worked (but no icons obviously), then tried re-adding everything except Bibata-* and breeze* and it worked. I tried to see if its Bibata or breeeze but if I add either it stops working so its both. Thank you for investigating this with me, I've learned a lot !
Offline
To see whether this is a memory issue, remove something (maybe two or three themes) else and re-add one of the breeze themes.
If it still fails, it's something about the theme, otherwise you encounter a more general memory violation.
In any event, crashing is not a good way to deal with garbage input, so you most certainly want to file a bug against lxde/lxappearance.
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
It is none of the above, it is the glib2 update, downgraded and all is now working.
Offline
Possible.
Though the commit is 2 months old, https://gitlab.gnome.org/GNOME/glib/-/c … 63c93c7f61 looks like a good contender.
"gboolean" is "gint" is bulls… I mean regular-ass-C int, so the flow relies on an un-initialized integer and the 2.68 build added "-D glib_debug=disabled" which might result in the loss of "implicit" initialization.
Does anyone here have a gnome gitlab account to file a bug?
Offline
Nope, I haven't. Another thing I noticed is it affects the right click menu in my browser (vivaldi). The fonts where all small.
Offline
https://bugs.archlinux.org/task/70131 - let's hope somebody there is allowed to file gnome bugs.
Offline
FWIW: I fixed my issues by removing questionable themes, all lx related apps and performing reinstalls of essential components. Now everything is hunky-dorey.
Pax vobiscum,
Mark Rabideau - http://many-roads.com
spectrwm, i3, bspwm, dwm ~ Reg. Linux User #449130
"For every complex problem there is an answer that is clear, simple, and wrong." H. L. Mencken
Offline
glib2 2.68.0-4 has been rolled out and seems to fix the problem.
Offline
Pages: 1