You are not logged in.

#1 2021-03-22 21:02:25

Dennis
Member
Registered: 2014-11-04
Posts: 46
Website

[fixed at upstream] lxdm-gtk3 greeter coredumps with glib2 2.68.0-2

<edit> temporary workaround, see: https://bbs.archlinux.org/viewtopic.php … 8#p1963548 </edit>
<edit2> further info: https://bugs.archlinux.org/task/70131 </edit2>
<edit3> upstream is informed </edit3>
<edit4> a potential fix was backported to 2.68, see https://gitlab.gnome.org/GNOME/glib/-/m … uests/2010 </edit4>

Can't log in to X with lxdm-greeter-gtk after upgrading glib2 (screen stays black and the process segfaults).

Downgrading to previous version via...
$ pacman -U /var/cache/pacman/pkg/glib2-2.66.7-1-x86_64.pkg.tar.zst /var/cache/pacman/pkg/lib32-glib2-2.66.7-1-x86_64.pkg.tar.zst /var/cache/pacman/pkg/glib2-docs-2.66.7-1-x86_64.pkg.tar.zst
...fixes it.

How do I know which package is the problem though?
Does lxdm-gtk3 just need to be rebuild or is it a bug in glib2?

message from journalctl:

Mar 22 21:44:15 DB2arch systemd-coredump[894]: Process 885 (lxdm-greeter-gt) of user 121 dumped core.
                                               
                                               Stack trace of thread 885:
                                               #0  0x00007fd57f40e102 n/a (libglib-2.0.so.0 + 0x4c102)
                                               #1  0x00007fd57f40e673 n/a (libglib-2.0.so.0 + 0x4c673)
                                               #2  0x00007fd57f40e8e1 n/a (libglib-2.0.so.0 + 0x4c8e1)
                                               #3  0x00007fd57f40e9c6 g_key_file_load_from_file (libglib-2.0.so.0 + 0x4c9c6)
                                               #4  0x000055726dddcabe n/a (lxdm-greeter-gtk + 0x6abe)
                                               #5  0x00007fd57f1fbb25 __libc_start_main (libc.so.6 + 0x27b25)
                                               #6  0x000055726ddddc7e n/a (lxdm-greeter-gtk + 0x7c7e)
                                               
                                               Stack trace of thread 892:
                                               #0  0x00007fd57f2cda9d syscall (libc.so.6 + 0xf9a9d)
                                               #1  0x00007fd57f4648ab g_cond_wait_until (libglib-2.0.so.0 + 0xa28ab)
                                               #2  0x00007fd57f3e5893 n/a (libglib-2.0.so.0 + 0x23893)
                                               #3  0x00007fd57f44728b n/a (libglib-2.0.so.0 + 0x8528b)
                                               #4  0x00007fd57f444241 n/a (libglib-2.0.so.0 + 0x82241)
                                               #5  0x00007fd57f3aa299 start_thread (libpthread.so.0 + 0x9299)
                                               #6  0x00007fd57f2d3053 __clone (libc.so.6 + 0xff053)
                                               
                                               Stack trace of thread 890:
                                               #0  0x00007fd57f2c837f __poll (libc.so.6 + 0xf437f)
                                               #1  0x00007fd57f46bdef n/a (libglib-2.0.so.0 + 0xa9def)
                                               #2  0x00007fd57f4136d1 g_main_context_iteration (libglib-2.0.so.0 + 0x516d1)
                                               #3  0x00007fd57f413722 n/a (libglib-2.0.so.0 + 0x51722)
                                               #4  0x00007fd57f444241 n/a (libglib-2.0.so.0 + 0x82241)
                                               #5  0x00007fd57f3aa299 start_thread (libpthread.so.0 + 0x9299)
                                               #6  0x00007fd57f2d3053 __clone (libc.so.6 + 0xff053)
                                               
                                               Stack trace of thread 891:
                                               #0  0x00007fd57f2cda9d syscall (libc.so.6 + 0xf9a9d)
                                               #1  0x00007fd57f4648ab g_cond_wait_until (libglib-2.0.so.0 + 0xa28ab)
                                               #2  0x00007fd57f3e5893 n/a (libglib-2.0.so.0 + 0x23893)
                                               #3  0x00007fd57f44728b n/a (libglib-2.0.so.0 + 0x8528b)
                                               #4  0x00007fd57f444241 n/a (libglib-2.0.so.0 + 0x82241)
                                               #5  0x00007fd57f3aa299 start_thread (libpthread.so.0 + 0x9299)
                                               #6  0x00007fd57f2d3053 __clone (libc.so.6 + 0xff053)

Last edited by Dennis (2021-03-23 17:06:57)

Offline

#2 2021-03-23 02:45:19

WFV
Member
From: ☭USSA⛧⭒⭒⭒⭒
Registered: 2013-04-23
Posts: 281

Re: [fixed at upstream] lxdm-gtk3 greeter coredumps with glib2 2.68.0-2

Same as this? https://bbs.archlinux.org/viewtopic.php?id=264722, and this? https://bugs.archlinux.org/task/70124
lxdm-gtk3 (last update 5-25-2020) requires gtk3 which requires gobject-introspection which requires glib2. Downgrading glib2 results in partial upgrade, expect problems elsewhere.
Being many others work fine with latest glib2, suspect lx* needs update.

EDIT: rebuilt lxdm, lxappearance, lxpanel, lxrandr, lxsession, lxtask, lxterminal - all the ones that needed gtkX, in clean chroot with current glib2 and still dumps core at lxdm-greeter-gt - this is not the gtk3 version but both build.
EDIT: confirmed glib2-2.68.0-4 fixed issue here.

Last edited by WFV (2021-03-23 23:10:56)


∞ hard times make the strong, the strong make good times, good times make the weak, the weak make hard times ∞

Offline

#3 2021-03-23 06:13:03

vs220
Member
Registered: 2021-03-23
Posts: 2

Re: [fixed at upstream] lxdm-gtk3 greeter coredumps with glib2 2.68.0-2

WFV wrote:

Downgrading glib2 results in partial upgrade

As a temporary solution, you can remove non-English characters from the files on which the application crashes.

strace lxappearance 
strace lxsession-edit

most likely it is
/usr/share/icons/*/index.theme
/etc/xdg/autostart/*
2021-03-22-00-20-27.png

Offline

#4 2021-03-23 07:51:24

Dennis
Member
Registered: 2014-11-04
Posts: 46
Website

Re: [fixed at upstream] lxdm-gtk3 greeter coredumps with glib2 2.68.0-2

Ok, I did what vs220 wrote and removed all lines like..

Name[*]=*
Comment[*]=*

..from the affected files.

One of those files did not have any non-English characters in them though but still had two extra..

Name[*]=*
Comment[*]=*

..lines in addition to just..

Name=*
Comment=*

.

So is this a known issue upstream already?

EDIT:
caveat: After rebooting lxdm-greeter-gtk still segfaulted, so I had to edit my xinitrc to run just a terminal and did strace /usr/lib/lxdm-greeter-gtk in there to find another affected file that was not touched by lxappearance or lxsession-edit.

EDIT2:
Could not find a report about this on their bug-tracker, so I added one there: https://gitlab.gnome.org/GNOME/glib/-/issues/2361 (EDIT3: You might not be able to see the bug on their tracker anymore because it was marked confidential. )

Last edited by Dennis (2021-03-23 15:55:05)

Offline

#5 2021-03-23 17:07:46

Dennis
Member
Registered: 2014-11-04
Posts: 46
Website

Re: [fixed at upstream] lxdm-gtk3 greeter coredumps with glib2 2.68.0-2

Latest status update, a potential fix has been backported to glib2 2.68 upstream: https://gitlab.gnome.org/GNOME/glib/-/m … uests/2010

Offline

#6 2021-03-23 21:58:20

vs220
Member
Registered: 2021-03-23
Posts: 2

Re: [fixed at upstream] lxdm-gtk3 greeter coredumps with glib2 2.68.0-2

version glib2 2.68.0-4 should fix

Offline

Board footer

Powered by FluxBB