FS#62105 - [lightdm-gtk-greeter] Core dump on start with default theme and gtk3 1:3.24.7+25+g17665f06e3-1

Attached to Project: Arch Linux
Opened by Frederic Bezies (fredbezies) - Thursday, 21 March 2019, 20:20 GMT
Last edited by Antonio Rojas (arojas) - Tuesday, 14 May 2019, 18:37 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: When I updated gtk3 to its version 1:3.24.7+25+g17665f06e3-1, I noticed lightdm cores dump.

Using another theme like arc-gtk one and lightdm gets back to work.

Additional info:
gtk3 1:3.24.7+25+g17665f06e3-1
lightdm 1:2.0.6-1

Steps to reproduce:

Just use lightdm and its default theme. Upgrade gtk3. Logout. You cannot log in again. Rebuilding lightdm-gtk-greeter doesn't help.
This task depends upon

Closed by  Antonio Rojas (arojas)
Tuesday, 14 May 2019, 18:37 GMT
Reason for closing:  Fixed
Comment by Frederic Bezies (fredbezies) - Thursday, 21 March 2019, 20:32 GMT
Core dump from journalctl -xe:

march 21 21 21:19:19:46 fredo-archlinux kernel: audit: type=1701 audit
(1553199586.978:66): auid=4294967295 uid=620 gid=620 ses=4294967295
pid=4173 comm="lightdm-gtk-gre" exe="/usr/bin/lightdm-gtk-greeter"
sig=6 res=1
march 21 21 21:19:19:47 fredo-archlinux lightdm[4170]:
pam_unix(lightdm-greeter:session): session closed for user lightdm
March 21 21 21:19:19:47 fredo-archlinux systemd-coredump[4185]:
Process 4173 (lightdm-gtk-gre) of user 620 dumped core.
#51
0x000000564b546e1293 n/a (lightdm-gtk-greeter)
#52
0x000000564b546e3320 greeter_background_connect (lightdm-gtk-greeter)
#53
0x000000564b546db384 main (lightdm-gtk-greeter)
#55
0x000000564b546dc7of _start (lightdm-gtk-greeter)
-- Subject: Process 4173 (lightdm-gtk-gre) generated a core file
-- Process 4173 (lightdm-gtk-gre) has planted and generated a core file.

Note : I only tested in VirtualBox, not in my main computer.
Comment by Frederic Bezies (fredbezies) - Thursday, 21 March 2019, 21:55 GMT
Tested in Qemu/Kvm and no bug. Looks like it is a VirtualBox bug?!
Comment by Frederic Bezies (fredbezies) - Thursday, 28 March 2019, 08:23 GMT
Looks like an update fixed this bug. No need to let this bug opened.

Loading...