Summary: | kdm(-4.3.1) does not provide a fallback for "custom" session when .xsession not set | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | kavol |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ossi |
Priority: | High | Flags: | tampakrap:
Bugday+
|
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://svn.reviewboard.kde.org/r/6236/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | xsession error file for the x86 |
Description
kavol
2009-09-25 08:37:27 UTC
Is this still an issue with kde-4.4 or kde-4.5? (In reply to comment #1) > Is this still an issue with kde-4.4 or kde-4.5? yes, with kde-base/kdm-4.4.5 the problem is the same - choosing "custom" leads to the login screen reappearing without any error message slightly modified patchreported upstream in http://svn.reviewboard.kde.org/r/6236/ i'll wait for their feedback and act accordingly. thank you! the Xsession should display a message box if the session cannot be executed. kdm's default Xsession uses the xmessage tool for that - if that one is missing, the problem will go unreported. so one can make kdm depend on xmessage or modifiy the script to support both kdialog and xmessage and depend on xmessage|kdebase-apps. (In reply to comment #4) > the Xsession should display a message box if the session cannot be executed. > kdm's default Xsession uses the xmessage tool for that - if that one is > missing, the problem will go unreported. so one can make kdm depend on xmessage > or modifiy the script to support both kdialog and xmessage and depend on > xmessage|kdebase-apps. > This is strange because we have the dependency already in all in-tree versions... (In reply to comment #5) > This is strange because we have the dependency already in all in-tree > versions... Oswald is the upstream kdm developer, he is talking about kdm itself not about our depedencies :) Anyway, I'll try to update the patch no, i actually meant packages. kdm itself doesn't check the xmessage dependency anyway (which is admittedly a bit sloppy). upstream it would make sense to just switch to kdialog, as somebody installing from source will most likely install all of kdebase anyway. (In reply to comment #5) > This is strange because we have the dependency already in all in-tree > versions... I've just checked the machine, and it has xmessage installed ... however, checking emerge.log, it got installed on 1291754002 i.e. December 2010 - so, *after* comment #2 unfortunately, I don't have physical access to that machine now so I can't re-test (unless I figure out how to do that remotely ... any hints? :-) Created attachment 267365 [details]
xsession error file for the x86
(In reply to comment #8) > I've just checked the machine, and it has xmessage installed ... however, > checking emerge.log, it got installed on 1291754002 i.e. December 2010 - so, > *after* comment #2 OK, let's assume this is fixed then by installing xmessage... > unfortunately, I don't have physical access to that machine now so I can't > re-test (unless I figure out how to do that remotely ... any hints? :-) No idea :| |