Bug 5234 - Have to login twice, first Gnome session always crashes
Summary: Have to login twice, first Gnome session always crashes
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Olav Vitters
QA Contact:
URL:
Whiteboard: MGA2TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-05 00:03 CEST by Reinout van Schouwen
Modified: 2013-02-27 01:08 CET (History)
2 users (show)

See Also:
Source RPM: gnome-session-3.4.0-1.mga2
CVE:
Status comment:

Attachments
xsession-errors (logged in session) (9.12 KB, text/plain)
2012-04-05 00:03 CEST, Reinout van Schouwen 		Details
xsession-errors (previous session, crashed) (8.47 KB, text/plain)
2012-04-05 00:03 CEST, Reinout van Schouwen 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Reinout van Schouwen 2012-04-05 00:03:12 CEST 
Created attachment 1925 [details]
xsession-errors (logged in session)

After booting my system, I always have to login twice. At the first try, my session appears to load but then the 'sad computer' Gnome Shell crash screen appears.

The second attempt then always works fine.

Attaching .xsession-errors and .xsession-errors.old (presumably corresponding to the failed session).
Comment 1 Reinout van Schouwen 2012-04-05 00:03:54 CEST 
Created attachment 1926 [details]
xsession-errors (previous session, crashed)
Reinout van Schouwen 2012-04-05 00:04:02 CEST

Hardware: i586 => x86_64

Comment 2 Manuel Hiebel 2012-04-05 00:29:50 CEST 
duplicate of bbug 4553 ?
Comment 3 Olav Vitters 2012-04-05 08:48:25 CEST 
Error seems to be:
GLib-GIO:ERROR:gdbusactiongroup.c:252:g_dbus_action_group_describe_all_done: assertion failed: (group->connection == (gpointer) source)

very generic error (somewhere in gdbus, part of gio)

I experienced bug 4553, but that one is a bit different.

Still, could you wait 2 minutes before logging in, then log in and see if it works.

Are there any core files in ~/ ? Stack trace would be pretty helpful to understand where the crasher is coming from.
Comment 4 Reinout van Schouwen 2012-04-10 00:03:51 CEST 
There are no core files but I think my ulimit doesn't allow them to be created. 
Where in Mageia is the proper place to change that?
Comment 5 Reinout van Schouwen 2012-04-19 23:10:07 CEST 
I don't see this as often as I did before, but I'm not quite sure it's completely solved yet.
Comment 6 Reinout van Schouwen 2012-05-02 19:43:52 CEST 
This is still happening for me. This is a showstopper for the release, as far as I am concerned. My question in comment #4 is still unanswered.

Severity: normal => critical

Comment 7 Colin Guthrie 2012-05-06 12:57:09 CEST 
Can't say I've ever seen this problem. Do you know how widespread it is?

CC: (none) => mageia

Comment 8 Reinout van Schouwen 2012-05-06 13:08:31 CEST 
(In reply to comment #7)
> Can't say I've ever seen this problem. Do you know how widespread it is?

No, I have only myself as reference. My impression is that there is some kind of timeout during session restore. In other words, it happens mostly after a cold boot if you had a lot of windows open when you last logged out.
Comment 9 Marja Van Waes 2012-05-26 13:01:47 CEST 
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 10 Reinout van Schouwen 2012-05-28 23:45:00 CEST 
I still suffer from this problem.

Version: Cauldron => 2

Sander Lepik 2012-05-29 09:04:21 CEST

Keywords: NEEDINFO => (none)
CC: (none) => sander.lepik
Version: 2 => Cauldron
Whiteboard: (none) => MGA2TOO

Comment 11 Reinout van Schouwen 2013-02-27 01:08:12 CET 
WFM now.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME
Note You need to log in before you can comment on or make changes to this bug.