Hello, we are having problems with Plasma5 logins seeming to dive-bomb themselves.
Problem #1 (Repetitive)
My wifes grandma only gets on Facebook and checks her email, all software and settings are setup by myself. It only lasts about a few days before she is no longer able to login. Plasma5 begins to load and then freezes while all other accounts work. Where is the account folder, like KDE4 had, so I can purge the settings it applied to itself instead of having to make new accounts/reinstall the system? Better yet, is KDE4 officially supported and available for 42.1?
Problem #2 (Happened once, but that’s enough)
KDE could no longer communicate with QDbus after reboot. I had been installing multimedia codecs and restarted my system when it locked up. No matter what, I could not recover. I force reinstalled all KDE packages, created a new account and still, would not communicate with QDBus, though I was able to call it with no issues, and no lag in response. It was almost as if KDE lost access to the stream.
Problem #3 (Repetitive)
NSF Server mounts that are not online halts booting. It seems as though when I set a mount point (through Yast) for a network shared location on our local server, if that server is not online the client computer will not boot. I feel that this should be handled post login as each user can have a different set of mount points than the next as well as it should never stop the computer from booting, unless I have it setup for network accounts.
Problems 1 & 2 have never been seen until the switch to 42.1 and it’s driving me up the wall. The reason I forced everyone in the house to Linux in the first place was stability. Once I got it set-up, it was quite a task for them to take it down. The previous install of OpenSuse ran from the release of 13.1 up until the computer died last week. Since then, I have spent far more time fixing issues and recovering from them than I have developing. I honestly can’t say I’ve even had to put this much effort into getting Windows stable.
Configuration settings are in “.config” and “.local”.
To a first approximation, what used to be in “.kde4/share/config” is now in “.config” and what used to be in “.kde4/share/apps” is now in “.local/share”.
However, non-kde software also uses these locations. So be careful about what you delete.
NSF Server mounts that are not online halts booting.
That’s what the automounter is for. You can bootup even if NFS servers are down. You won’t run into problems until you try to access data on the servers that are down.
Thank you for the location. I will be as safe as one can be ;)…though I’m not sure why it’s happening. She literally does nothing on her account aside launch firefox.
Thank you for that as well, though I may try the next suggestion on this one. Had I added this to fstab manually, I would expect this as I have left some flags out. However, I’m not sure this should be default behavior when configuring through a Yast utility. I just see a less experienced user having serious issues with that. I’ve been using linux for several years, albeit with debian for most of the time, and even I over-looked this as I was setting up a simple file server. It’s only for local access so that we can watch our DVDs that I’m copying – Yes, don’t worry, all legal. I have spent more money on movies that I would like to admit. I was able to recover, I just noted this as something that maybe shouldn’t be default behavior.
I had that problem quite some time ago - probably opensuse 13.1 may be earlier. So I entered the line in the /etc/sudoers file:
uli linux-dfsr=NOPASSWD:/bin/mount,/bin/umount
uli - that is me the user, linux-dfsr is the computer where the script is saved.
Then I put the following script into ~/.kde4/Autostart
#!/bin/bash
ping -c2 192.168.2.2
#sleep 2
if $? -eq 0 ]
then
sudo mount -t nfs 192.168.2.2:/mnt/md1/ulimnt /home/uli/ulimnt
fi
That script tests first whether the server is online with a ping - if so it mounts it at login. I agree though that the boot interruption when a mount is unsuccessful is not ideal.
Cheers
Uli
Thanks for that one…very simple I’ve honestly never run into this issue as previously if a server was down, all of them were down…so it just never popped up. Not sure why, but this is the first time I’ve got around to setting up a server like this for home use. It’s very nice…I just need like 4 DVD drives now to get through the collection xD
A little update on this thread. Last night, her and my son’s account crashed again without explanation and without reports. I go to do what I promised myself as the last install with a fresh download of OpenSuSe 42.1, checking the media before bringing it in the house to do. Then, I get called in for another issue…this one I at least can see and read logs for. Turns out it was my trusty friend Segates fault. The brand new SSD (bought last week) was silently dieing and it finally got to the critical sectors and we got errors during boot. Just got back from replacing it with a Samsung 850 Evo which is even faster and a better brand. All in all, I got dazzled by sticker price and got what I paid for. My apologies on that part
I’ve honestly never run into this issue as previously if a server was down, all of them were down…so it just never popped up. Not sure why, but this is the first time I’ve got around to setting up a server like this for home use. It’s very nice…I just need like 4 DVD drives now to get through the collection xD
