[arch-general] kdm3 crash on logout - no apparrent errors

[David C. Rankin, J.D.,P.E.]

On Tuesday 12 May 2009 04:42:33 Alessandro Doro wrote:
> On Tue, May 12, 2009 at 01:53:11AM -0500, David C. Rankin, J.D.,P.E. wrote:
> > Listmates,
> >
> > 	After the kernel update, my kdm3 is crashing with each user logout.
> > Basically, on logout you are dumped back to tty1 and must then login and
> > issue kdm3 restart to restore the display manager. I am using the
> > radeonhd driver. Before the latest update this didn't occur. What can I
> > check to get information to help solve this puzzle?
> >
> > 	I've checked /var/log/messages.log and Xorg.0.log, but nothing is out of
> > the ordinary. Any help would be greatly appreciated.
>
> Have a look at /var/log/kdm.log and/or ~/.xsession-errors (before
> relogin).
>
>
> You can try to add:
>
> TerminateServer=true
>
> to the [X-*-Core] section of /opt/kde/share/config/kdm/kdmrc
>
> I need(ed) that line because of similar problems.

Alessandro,

	I think the new kernel and vesafb is the problem. Here is the log after the 
crash on user logout:

X.Org X Server 1.6.1
Release Date: 2009-4-14
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.29-ARCH x86_64
Current Operating System: Linux alchemy 2.6.29-ARCH #1 SMP PREEMPT Sat May 9 
14:09:36 CEST 2009 x86_64
Build Date: 15 April 2009  11:01:49AM

        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue May 12 18:43:59 2009
(==) Using config file: "/etc/X11/xorg.conf"
(EE) Failed to load module "type1" (module does not exist, 0)
(EE) Failed to load module "freetype" (module does not exist, 0)
None
QSettings: error creating /tmp/0151698992/.qt
QSettings: failed to open file '/tmp/0151698992/.qt/qt_plugins_3.3rc'
QSettings::sync: filename is null/empty
QSettings: error creating /tmp/0151698992/.qt
QSettings: failed to open file '/tmp/0151698992/.qt/qt_plugins_3.3rc'
QSettings::sync: filename is null/empty
QSettings: error creating /tmp/0151698992/.qt
QSettings: failed to open file '/tmp/0151698992/.qt/qt_plugins_3.3rc'
QSettings::sync: filename is null/empty
QSettings: error creating /tmp/0151698992/.qt
QSettings: failed to open file '/tmp/0151698992/.qt/qt_plugins_3.3rc'
QSettings::sync: filename is null/empty
QSettings: error creating /tmp/0151698992/.qt
QSettings: failed to open file '/tmp/0151698992/.qt/qt_plugins_3.3rc'
QSettings::sync: filename is null/empty
QSettings: error creating /tmp/0151698992/.qt
QSettings: failed to open file '/tmp/0151698992/.qt/qt_plugins_3.3rc'
QSettings::sync: filename is null/empty
(EE) RADEONHD(0): Failed to map FB.

Fatal server error:
AddScreen/ScreenInit failed for driver 0

On startup, this is the log:

<snip>
QSettings::sync: filename is null/empty
QSettings: error creating /tmp/0872520527/.qt
QSettings: failed to open file '/tmp/0872520527/.qt/qt_plugins_3.3rc'
QSettings::sync: filename is null/empty
*********************************WARN_ONCE*********************************
File r300_mem.c function r300_mem_alloc line 225
Ran out of GART memory (for 1048576)!
Please consider adjusting GARTSize option.
***************************************************************************

	Dunno where the error is because it starts just fine and used to login and 
logout without crashing with the most recent kernel before the last kernel 
update. What should I try?



-- 
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com