Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

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

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#32773 - [accountsservice] 0.6.28-1 segfault, unable to login with GDM

Attached to Project: Arch Linux
Opened by György Balló (City-busz) - Tuesday, 20 November 2012, 18:50 GMT
Last edited by Jan Steffens (heftig) - Thursday, 22 November 2012, 07:11 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ionut Biru (wonder)
Jan Steffens (heftig)
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
After I updated to accountsservice 0.6.28-1, GDM fails to load on two of my systems. I tried to run /usr/lib/accountsservice/accounts-daemon and I received a segmentation fault. Downgrading to accountsservice 0.6.25 solves the problem.


Additional info:
* package version(s)
- accountsservice 0.6.28-1
- gdm 3.6.2-1

* config and/or log files etc.
The output of /usr/lib/accountsservice/accounts-daemon:
(accounts-daemon:366): GLib-GObject-WARNING **: g_object_set_valist: object class `User' has no property named `ballogy'

(accounts-daemon:366): GLib-GObject-WARNING **: g_object_set_valist: object class `User' has no property named `login-previous_login'
Segmentation fault

I attached the backtrace (trace.log).


Steps to reproduce:
Run /usr/lib/accountsservice/accounts-daemon and see the output
This task depends upon

Closed by  Jan Steffens (heftig)
Thursday, 22 November 2012, 07:11 GMT
Reason for closing:  Fixed
Additional comments about closing:  0.6.29
Comment by Ionut Biru (wonder) - Tuesday, 20 November 2012, 18:56 GMT Comment by György Balló (City-busz) - Tuesday, 20 November 2012, 20:17 GMT
No, it does not solve the problem.
Comment by Ionut Biru (wonder) - Tuesday, 20 November 2012, 20:36 GMT
i think this issue should be reported upstream
Comment by György Balló (City-busz) - Tuesday, 20 November 2012, 21:27 GMT
Yes, I reported this bug to upstream now:
https://bugs.freedesktop.org/show_bug.cgi?id=57343
Comment by Kristian (klausenbusk) - Wednesday, 21 November 2012, 10:02 GMT
It weired, i only have this probelm on my desktop. Not on my laptop..
Comment by whoop (whoop) - Wednesday, 21 November 2012, 21:02 GMT
@Kristian: I have been wondering this myself... I only have this on one system.
Grasping at straws here but maybe it depends on the ammount of users on the system?
Comment by Kristian (klausenbusk) - Wednesday, 21 November 2012, 21:16 GMT
@whoop Have just tested, and amount of users seems to have no effect.
Comment by Tom (SIGTERM) - Wednesday, 21 November 2012, 21:54 GMT
I can confirm this issue. However, when I restart GDM using systemctl restart gdm from TTY2, it does allow me to log in.
Comment by György Balló (City-busz) - Thursday, 22 November 2012, 01:55 GMT
It was fixed in version 0.6.29, please update the package.

Loading...