Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#47694 - [lightdm-gtk-greeter] cairo segfault at first login

Attached to Project: Arch Linux
Opened by Luca (lukypie) - Sunday, 10 January 2016, 13:11 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 12 January 2016, 15:38 GMT
Task Type Bug Report
Category Packages: Extra
Status Assigned
Assigned To Maxime Gauduin (Alucryd)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


Description: Unable to access to lightdm-gtk-greeter after starting up the PC, just the first time. Lightdm segfaults for
the first login attempt.

lightdm-gtk-greeeter 1:2.0.1-2
cairo 1.14.6-1

DMESG: lightdm-gtk-gre[435]: segfault at 10 ip 00007f8139a49840 sp 00007ffd995106a8 error 4 in[7f81399d6000+129000]

Steps to reproduce:

Start up the PC with lightdm & lightdm-gtk-greeter enabled
try to login
the screen flickers and lightdm-gtk-greeter segfaults just for the first time
try to login again, successfully
This task depends upon

Comment by Drew Noel (drewmnoel) - Thursday, 15 June 2017, 16:34 GMT
Still an issue:

lightdm-gtk-greeter 1:2.0.2-1
cairo 1.14.8-1

I attached my coredump. It looks like the call to cairo_surface_get_type caused the segfault.
Comment by Maxime Gauduin (Alucryd) - Friday, 17 May 2019, 14:44 GMT
Is this still a thing?
Comment by muradm (muradm) - Tuesday, 21 May 2019, 07:17 GMT
Yes, happens frequently to me on boot, and when unlocking.
Comment by muradm (muradm) - Tuesday, 21 May 2019, 07:31 GMT
Coredump journalctl entry attached
Comment by Maxime Gauduin (Alucryd) - Tuesday, 21 May 2019, 13:49 GMT
Looks like this is known upstream:

They don't seem to care much about it though.
Comment by Patrik Plihal (birdspider) - Sunday, 14 June 2020, 18:05 GMT
Hi, I too had this issue.

I didn't have a static hostname set (as hinted in,
after checking that `hostnamectl` gave "Static hostname: n/a" and setting it via `hostnamectl set-hostname blackbox` first login works ! (does not segfault)