Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 309649 - xfce-base/xfce4-session-4.6.1 complains of corrupted double-linked list, and crashes, causing XFCE to restart
Summary: xfce-base/xfce4-session-4.6.1 complains of corrupted double-linked list, and ...
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: XFCE Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-15 20:53 UTC by Paul McDermott
Modified: 2010-06-11 12:35 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
Bottom half of ~/.xsession-errors (xsession-errors.txt,12.01 KB, text/plain)
2010-03-15 20:55 UTC, Paul McDermott
Details
Results of emerge --info (emerge-info.txt,4.26 KB, text/plain)
2010-03-15 20:55 UTC, Paul McDermott
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Paul McDermott 2010-03-15 20:53:17 UTC
Starting XFCE from GDM, a message about the session lasting less than 10 seconds appears. Clicking OK returns me to the the GDM login screen. Inspection of .xsession-errors reveals that xfce4-session has terminated abnormally: glibc has detected a corrupted double-linked list. Re-logging in eventually gets round this problem, but I have to try a (variable) number of times. Problem only appeared after upgrading to xfce4. xfce4-4.6.1 and xfce4-4.6.1-r1 both exhibit this problem.

Reproducible: Sometimes

Steps to Reproduce:
1.Log in to XFCE4 via GDM
2.Message about session lasting < 10s appears
3.Clicking OK re-starts XWindows and returns to the GDM login screen

Actual Results:  
XFCE4 / XWindows does not start. Returned to GDM login screen

Expected Results:  
Successful login to XFCE4

See attachments for final contents of .xsession-errors and emerge --info
Comment 1 Paul McDermott 2010-03-15 20:55:19 UTC
Created attachment 223793 [details]
Bottom half of ~/.xsession-errors

Sometimes this error message will not appear, in which case xfce4-session does not crash, and XFCE4 starts normally.
Comment 2 Paul McDermott 2010-03-15 20:55:45 UTC
Created attachment 223795 [details]
Results of emerge --info
Comment 3 Paul McDermott 2010-04-30 21:54:45 UTC
Why has this been changed to "Normal"? It meets the criteria set out for "Critical": The software CRASHES, hangs, or causes you to lose data.

I am completely unable to use XFCE because of this bug, and have switched to Gnome as a result.
Comment 4 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2010-04-30 22:05:19 UTC
(In reply to comment #3)
> Why has this been changed to "Normal"? It meets the criteria set out for
> "Critical": The software CRASHES, hangs, or causes you to lose data.
> 
> I am completely unable to use XFCE because of this bug, and have switched to
> Gnome as a result.
> 

There are no steps to reproduce and we don't know how to reproduce the issue. Furthermore, no other users have encountered this. Please do not take offense to the fact that this bug has not been resolved.
Comment 5 Paul McDermott 2010-05-02 22:38:01 UTC
No offence taken. I am merely pointing out that you are inconsistently applying your own severity criteria. Not being able to resolve the bug does not make it any less severe.
Comment 6 Christoph Mende (RETIRED) gentoo-dev 2010-06-03 19:19:48 UTC
Please try again with xfce4-session-4.6.2, if the problem still exists, please attach a gdb backtrace (see http://www.gentoo.org/doc/en/bugzilla-howto.xml#doc_chap2).

Also, I'm lowering severity again, because even though this bug might be critical to you, it is most likely a problem on your system (see Jeremy's comment) and not directly a critical bug in xfce4-session. Setting the severity higher is just for us to notice the priority bugs in the bug queue first, thus it's usually the maintainer who sets the severity, not the user.
Comment 7 Christoph Mende (RETIRED) gentoo-dev 2010-06-11 12:35:45 UTC
closing for now, please reopen with the mentioned details if this bug still exists