Yesterday I upgraded from 12.3 to 13.1 on my desktop; now I write from my laptop.
It seems OK as root, but as user (‘myuser’) my screen empty and where nothig can be done; in the middle :
“HPLIP Status Service
No system tray detected on this system.
Unable to start. Exiting” button OK
As root I have access to ‘myuser’ directory and there is no problem with the data.
As root this is the information from the user ‘myuser’ :
# id myuser
uid=1000(myuser) gid=100(users) groups=482(vboxusers),33(video),100(users)
# groups myuser
myuser : users vboxusers video
# finger myuser
Login: myuser Name: My Name
Directory: /home/ myuser Shell: /bin/bash
Last login Tue Jul 15 22:04 (CEST) on :0 from console
Mail last read Tue Jul 15 14:59 2014 (CEST)
No Plan.
What does this mean?
Did you boot from the DVD and chose “Upgrade an existing installation”? (aka offline upgrade)
Or did you do an online upgrade via “zypper dup”?
Is it the source of the problem?
Of course this can lead to problems, but in your case I don’t think it’s the reason.
If it works as root it doesn’t seem to be an installation problem.
How to recuperate the use of the other (me) user: ‘myuser’ ?
Does it work in “Recover Mode” (“Advanced Options” in the boot menu)?
Try to create a new user account. Does it work with that?
What DE are you actually using?
I suppose it is KDE, right?
Check the UID (user ID) the OS actually uses UID rather then your name to identify you. At install the first UID is 1000. If your old user does not have a UID 1000 and/or the home is not set to the same as the user record you will have problems.
Go to Yast and user and group management and check the UID
If in a gui check the properties of the users directory and be sure the UIDs match
If you booted from the DVD and chose “Upgrade an existing installation”, you did not use “zypper dup”.
If you used “zypper dup”, you cannot have selected “Upgrade an existing installation”, as “zypper dup” doesn’t offer that option.
So I take it you used “zypper dup”.
In that case, you should maybe also post your repo list.
On 2014-07-18 19:06, wolfi323 wrote:
>
> palp56;2654716 Wrote:
>> No via via “zypper dup”. Yes “Upgrade an existing installation”.
> So what now?
>
> If you booted from the DVD and chose “Upgrade an existing installation”,
> you did not use “zypper dup”.
> If you used “zypper dup”, you cannot have selected “Upgrade an existing
> installation”, as “zypper dup” doesn’t offer that option.
>
> So I take it you used “zypper dup”.
No, no. He used the “Upgrade an existing installation” menu entry you
see when booting the big dvd. That is, the offline upgrade method
The typical problem is that the DVD can not upgrade what is not included
in the DVD itself. The cure is to run, after the offline upgrade, a
modified online upgrade:
zypper patch
zypper up
zypper dup
Yes, the three of them, and in that order, I think.
It has to be done before any additional repos are added, which would
complicate matters greatly.
An exception could be nvidia/ati repo, if it was used previously. If the
dvd upgraded system booted, then don’t add it yet.
After you do the above, and reboot, you can add packman and do the
multimedia things.
# zypper patch
Loading repository data...
Reading installed packages...
Resolving package dependencies...
Nothing to do.
# zypper up
PackageKit is blocking zypper. This happens if you have an updater applet or other software management application using PackageKit running.
Tell PackageKit to quit? [yes/no] (no): no
System management is locked by the application with pid 3836 (/usr/lib/packagekitd).
Close this application before trying again.
# zypper up
Loading repository data...
Reading installed packages...
Nothing to do.
# zypper dup
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Loading repository data...
Reading installed packages...
Computing distribution upgrade...
Nothing to do.
An exception could be nvidia/ati repo, if it was used previously. If the dvd upgraded system booted, then don't add it yet.
YaST Control Center is ok on nvidia, apparently.
‘newuser’ is a new created user, ‘myuser’ is the old one.
‘myuser’ was UID 1000 before, in 12.3, and it is now; as root I don’t have problems to arrive the to the data into /myuser.
User and Group Administration
Login Name UID Groups
myuser My Name 1000 vbouxusers, users, video
newuser His name 1001 users
‘/home’ holds ‘/myuser’ and its data but there is no a ‘/newuser’ directory.
Opening myuser/password it is ok, but it gives a usless screen; so computer off.
With newuser/password the answer is :
Cannot enter home diredctory. Using /
I don’t know how to check UID on /theusername directory …
Well, if you still have the nvidia driver packages for 12.3 installed, this could of course cause problems. So, did you try “Recovery Mode” yet?
‘/home’ holds ‘/myuser’ and its data but there is no a ‘/newuser’ directory.
…
With newuser/password the answer is :
Cannot enter home diredctory. Using /
And how did you create the new user?
Do you have a separate /home partition?
Is it mounted? Was it mounted when you created the new user?
Login as root, open YaST->Security and Users->User and Group Management, delete the new user, and create a new one.
There should be a home directory for that user then (in /home/).
> --------------------
> # zypper patch
> Loading repository data...
> Reading installed packages...
> Resolving package dependencies...
>
> Nothing to do.
>
> # zypper up
> PackageKit is blocking zypper. This happens if you have an updater applet or other software management application using PackageKit running.
> Tell PackageKit to quit? [yes/no] (no): no
> System management is locked by the application with pid 3836 (/usr/lib/packagekitd).
> Close this application before trying again.
>
> # zypper up
No, abort!
You have to KILL packagekit, in the previous step. Going forward is futile.
Although “zypper dup” said there was nothing to do, so probably
everything is alright.
