You are not logged in.
Hi all,
Did a full system update recently... Now I cannot login into a KDE session from KDM. I can run other sessions (e.g. installed RazorQt and can log into that without any issues - from KDM). I've tried deleting my KDE user profile (~/.kde4). Clearing out all my tmp files in /tmp and /var/tmp. But I still get an X popup window Call to lnusertemp failed (temporary directories full?) when I try to log into KDE and the login fails returning to the KDM screen. I've hunted through my FS checking user permissions - can't see any issues there either...
Only see the following in the *systemd* logs...
journalctl --no-pager -p 0..3 --since=today --unit=kdm
-- Logs begin at Thu 2013-03-14 22:51:21 GMT, end at Sat 2013-08-03 17:33:34 BST. --
Aug 03 17:33:32 robs-core-i7-pc kdm[1051]: :0[1051]: Abnormal termination of greeter for display :0, code 127, signal 0Been bumping my head off this problem for about a week now... I've tried most of the suggested fixes in the Google results for this error. Just running KDE from the standard Arch repository... The system is fully updated.
Any thoughts?
Thanks
Bob
Last edited by bobwya (2013-08-05 13:30:57)
Offline
I guess you found https://bbs.archlinux.org/viewtopic.php?pid=796868.
Also did you do any of the checks mentioned at http://forum.kde.org/viewtopic.php?f=66&t=86360? e.g. executing the command manually etc. Or https://forum.kde.org/viewtopic.php?f=66&t=109644. (I'm not suggesting you reinstall but there are other suggestions in that thread even if the OP didn't use them.)
EDIT: Also telling us that you tried most of the stuff thrown up by a google search isn't much help if we don't know what it threw up or what results you got. Please explain what you have tried. I am guessing, for example, that you probably tried the stuff above. But of course I don't know because you haven't said.
Last edited by cfr (2013-08-05 01:38:03)
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
Perhaps not your issue, but I ran into a similar situation with Bodhi E17 recently. The problem was related to a kernel issue and related sna acceleration. I was able to resolve it by reverting the sna acceleration back to uxa (Intel Sandy Bridge hardware). In your case, if you still have an older kernel installed, try booting that one.
Offline
Perhaps not your issue, but I ran into a similar situation with Bodhi E17 recently. The problem was related to a kernel issue and related sna acceleration. I was able to resolve it by reverting the sna acceleration back to uxa (Intel Sandy Bridge hardware). In your case, if you still have an older kernel installed, try booting that one.
Hi David,
Thanks for the response. I know I'm guilty (as charged) of not writing enough background info for the problem!! I should really keep a log book to go over the steps I've taken to solve a problem...
My system specs are as follows:
Core i7 920
24Gb DDR3 RAM
Nvidia 8800GTX
Marvell Technology Group Ltd. 88SE9480 SAS/SATA 6Gb/s RAID controller (rev 03)
w/ 6 SATA drives: Samsung 830 256Gb SSD (4x)/Seagate Momentus XT 750Gb hybrid (2x) - no hardware RAID or LLVM, etc. - simple GPT volumes.
In the (minor) update I performed the kernel version went from linux-3.9.4-1-ARCH to 3.10.3-1-ARCH... Nvidia (proprietary) drivers went from nvidia-319.17-2-x86_64 to nvidia-319.32-4-x86_64. My first thought was that the Nvidia drivers aren't playing nice with the 3.10.x kernel (which is what happened to me on OpenSUSE and Gentoo). This was not the case however as reverting the nvidia packages and kernel version resulted in the same error. I'm using the stock ARCH kernel (the system is so grossly overspec'd it's not worth monkeying about with this :-) ).
Also I've been able to sucessfully launch both an XMBC session and a RazorQt session from KDM. So it's definitely only my KDE install/ settings that are "borked"!! Just tearing my hair out with this dumb error message now (which has been going on for about 2 weeks now)... ![]()
Thanks
Bob
Offline
I guess you found https://bbs.archlinux.org/viewtopic.php?pid=796868.
Also did you do any of the checks mentioned at http://forum.kde.org/viewtopic.php?f=66&t=86360? e.g. executing the command manually etc. Or https://forum.kde.org/viewtopic.php?f=66&t=109644. (I'm not suggesting you reinstall but there are other suggestions in that thread even if the OP didn't use them.)
EDIT: Also telling us that you tried most of the stuff thrown up by a google search isn't much help if we don't know what it threw up or what results you got. Please explain what you have tried. I am guessing, for example, that you probably tried the stuff above. But of course I don't know because you haven't said.
Thanks I though I'd tried all that!!
So (run as my standard user in an Arch chroot from my Gentoo install):
/usr/lib/kde4/libexec/lnusertempCheck
mkdir -v /tmp/testCheck
mkdir -v /var/tmp/testCheck
ls -Al ~/.kde*Fail!! Permission denied
So it turned out it was my ~/.kde4 directory. I had recursively chown'd this to my user. However it had permissions 600 - which didn't let me view the contents (for some reason - why the execute flag -weird??) It was definitely owned as my user and group. I hadn't done a "full check" as I'd my chroot'd in as root.
So anyway I recursively changed the permissions to 700 on both ~/.kde and ~/.kde4. Also went through ~/.kde and ~/.kde4 - cleared out all the symbolic links to old tmp and /var/tmp cache folders I had previously deleted...
I knew it had to be the ~/.kde4 folder (since the other sessions worked) - just hadn't done my checks thoroughly enough!!
So thanks for kicking my butt, cfr , got my Arch back up and running!!
Bob
Last edited by bobwya (2013-08-05 12:13:27)
Offline
I'm glad you figured out the problem but I'm not so sure that was the optimal way to solve it.
The execute bit is required to read the contents of a directory. However, you probably didn't really want to make all of the files under ~/.kde4 executable as well.
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
I'm glad you figured out the problem but I'm not so sure that was the optimal way to solve it.
The execute bit is required to read the contents of a directory. However, you probably didn't really want to make all of the files under ~/.kde4 executable as well.
Yeh, well it's the "optimal way" to fix it in terms of speed - I know it's also a massive security hole, etc.
I'll go back to sort things out later :-) You know it had never registered on my brain organ that I needed to have excute permission enabled to get read access to a directory - that's really pretty dumb IMHO...
Thanks for the help again.
Bob
Offline
chmod -R u+X ~/.kde ~/.kde4is pretty quick... Note the capital X makes all the difference...
I think technically the execute bit is a search bit when applied to a directory. But it shows the same way and gets manipulated the same way.
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline