Login Errors After Upgrade/Update to openSUSE 12.1

English Install/Boot/Login
#1

I just attempted to do an upgrade to openSUSE 12.1 from 11.4 through major package updates(KDE, X, SuSE-Branding) and adding of repositories. However, after updating some KDE packages, I attempted to update some YaST and X packages. The downloading of these packages worked well, but the installation failed due to obtaining locks on certain directories. I thought this odd, since downloading packages in YaST can only be used by root. I decided to restart my computer and encountered two problems:

  1. No Key or Mouse Input for KDM Login Manager
  2. Cannot Change Packages in YaST due to an error that states “config ‘root’ not found”. However, I can change printer settings fine.

Is there a way that I can fix these issues especially those of managing software? Thanks for your help.

By the way, I am running openSUSE 12.1 on a 64-bit machine.

#2

This is a pretty vague description of what you did.

When you want to do a distro update (like from 11.4 to 12.1) you can do this by removing all the 11.4 repos and then adding the apropriate 12.1 repos (where I would start with only OSS and non-OSS and Update, Packman and maybe others added later). And then do

zypper dup

You mention only that you added repos (not even which ones), not that you removed others. If this is not just a sloppy way of reporting to us what you did, but is the truth, it is no wonder you created a mess.

#3

Hcvv is right. Your initial post is almost worthless. I’m not trying to belabor the point or beat you down, but the point remains that you didn’t ask a good question.

A good question would involve providing info, like in this case a list of your repos and logs and error messages. It would involve the steps you took to get there, such as added the following repos to YaST (listing the repos), and performed the upgrade (describing how you upgraded). Then any errors you see, logs and so forth.

Did you look up the error yourself and try to resolve it?
What did you find?
What did you try on your own to fix this and what were the results?

There is just so much you left out, that one would almost need to be clairvoient to help you.

#4

On 2012-06-30 16:46, Paranelsus wrote:
>
> I just attempted to do an upgrade to openSUSE 12.1 from 11.4 through
> major package updates(KDE, X, SuSE-Branding) and adding of repositories.

The supported distribution upgrade methods are these two:

Online upgrade method
Offline upgrade method

It looks to me you are doing a partial upgrade - go figure what can happen!

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#5

Thanks for the reply.

Here is what I did:

Repositories

I added all of the official 12.1 repositories(in addition to Packman, KDE, and GNOME) listed in the openSUSE repository website: Package repositories - openSUSE.
I did not disable any 11.4 repositories, because I was concerned that some software would require packages in older repositories. Then, I started my upgrade.

Upgrading

First, I updated all packages with a newer version. However, when doing that there were too many unresolved dependencies. So I canceled this update(did not download or install packages) and then just updated the packages that I desired(KDE, X.Org, Firefox) in small batches. Note, that my “upgrade” was more like several updates. When I did this for KDE packages, everything was fine. However, when I did for YaST and X.Org(directly after that of KDE), YaST could download the packages, but could not install them. I retried this several times, but the installations kept failing. I do not remember the error word for word for failing to install packages, but I do remember it saying something about not being able to lock a particular file. Is there a way for me to retrieve the exact error?
**
Issues with Graphical Logon**

When I restarted my computer, I chose the system that I desired to use. Surprisingly, it still said 11.4, but displayed the new kernel version. As the login screen loaded, I found that it would not accept any keyboard or mouse input.

Problem with YaST Software Management Tool

Suspecting an X issue, I tried to use the failsafe login, but after trying to continue installing the packages via YaST, I received a “config ‘root’ not found” error when trying to use the Software Management tool in YaST and the SWManagement tool would not open. Interestingly, this same error printed out when trying to access the Printer tool in YaST, but still allowed me to go through the screens for Printers.

I searched online for “config ‘root’ not found”, but I did not find anything helpful. Thanks for your help.

#6

Ok. Thanks. Now we know whats wrong and why.
Disable your 11.4 repos and run zypper dup

#7

On 2012-06-30 20:16, Paranelsus wrote:
>
> Thanks for the reply.
>
> Here is what I did:
>
> REPOSITORIES
> I added all of the official 12.1 repositories(in addition to Packman,
> KDE, and GNOME) listed in the openSUSE repository website: ‘Package
> repositories - openSUSE’
> (http://en.opensuse.org/Package_repositories#Official_repositories).
> I did not disable any 11.4 repositories, because I was concerned that
> some software would require packages in older repositories. Then, I
> started my upgrade.
>
> UPGRADING
> First, I updated all packages with a newer version. However, when doing
> that there were too many unresolved dependencies. So I canceled this
> update(did not download or install packages) and then just updated the
> packages that I desired(KDE, X.Org, Firefox) in small batches. Note,
> that my “upgrade” was more like several updates. When I did this for KDE
> packages, everything was fine. However, when I did for YaST and
> X.Org(directly after that of KDE), YaST could download the packages, but
> could not install them. I retried this several times, but the
> installations kept failing. I do not remember the error word for word
> for failing to install packages, but I do remember it saying something
> about not being able to lock a particular file. Is there a way for me to
> retrieve the exact error?

You invented a procedure and broke your system. Disable all 11.4 repos, and
do a zypper dup, exactly as described in the documentation I posted.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#8

I just disabled all the 11.4 repositories and have done the zypper dup as described.
I can now move my mouse and enter keys using my keyboard on the login screen. Thanks for the assistance.

However, I now have a different problem. After attempting to login, I receive an error with the following statement: “Warning: Cannot open ConsoleKit session: Unable to open session. Did not receive a reply. Possible causes include: the remote… or the network connection was broken.” This error occurs when logging into either the KDE session or IceWM session. After a long time(2 min), an x-term pops up with the message: “Could not start ksmserver. Check your installation.”. Interestingly, I can logon to the system with the IceWM, but not with KDE as stated above. Thanks for your help.

#9

I have more information regarding the above error:
I checked the command the system was trying to run using systemctls and found the following:

Console-Kit Daemon

command=“console-kit-daemon --no-daemon”
Output when manually run:

missing action

Console-kit-daemon: symbol lookup error: /usr/lib64/libpolkit-gobject-1.so.0: undefined symbol: g_mutex_lock

Network Manager
/usr/lib64/gio/modules/libgiognutls.so: undefined symbol: g_bytes_hash
Failed to load module: /usr/lib64/gio/modules/libgiognutls.so
NetworkManager: symbol lookup error: /usr/lib64/gio/modules/libgiofam.so: undefined symbol: g_mutex_lock

Thanks for your help.

#10

On 07/01/2012 06:56 AM, Paranelsus wrote:
> “Warning: Cannot open
> ConsoleKit session: Unable to open session. Did not receive a reply.
> Possible causes include: the remote… or the network connection was
> broken.” This error occurs when logging into either the KDE session or
> IceWM session. After a long time(2 min), an x-term pops up with the
> message: “Could not start ksmserver. Check your installation.”.

maybe it is time you tell us more about what you are doing, like:

why is a network needed? that is, are you operating a remote machine, or
are you sitting at the keyboard and monitor directly hooked to the
system having problems?

are you running openSUSE directly on that machine you are sitting at
or possibly is openSUSE running in a VM? if so, which (precisely and
exactly) and what is the host OS?

and, are you “attempting to login” as yourself (a regular user) or as
root/super user/administrator?

and, in one of your posts you wrote: “I added all of the official 12.1
repositories(in addition to Packman, KDE, and GNOME)” which tell me you
enabled LOTS of repos! don’t do that unless you know which ones you
should enable and which not (enabling all “official repos” can easily
introduce sever complications…

suggest you disable ALL repos other than oss, non-oss, update and
packman [which is exactly as hcvv said he would do in his earlier post]
and do the dup again…

i guess if you do that you might have a chance to recover your system…

for next time, please don’t make up a way to upgrade…instead closely
study and apply these:

http://tinyurl.com/6kvoflv
http://tinyurl.com/35p966c
http://tinyurl.com/7l4m2td

see the complexity?

–
dd

#11

On 2012-07-01 08:36, Paranelsus wrote:
>
> I have more information regarding the above error:
> I checked the command the system was trying to run using systemctls and
> found the following:

Probably a library inconsistency because you have too many repos enabled.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#12

You might reread my post #2 above, which advises for the initial upgrade to have only OSS-nonOSS and Update.
Then check what you have, (and try to repair problems in this well known state where people here can help you). Then add Packman and use the normal “switch to this repo”. After that you might feel the need to go for other repos like a newer KDE, etc.

#13

On 2012-07-01 12:56, hcvv wrote:
>
> You might reread my post #2 above, which advises for the initial upgrade
> to have only OSS-nonOSS and Update.

And mine, linking to the documentation on how to do upgrades…

> Then check what you have, (and try to repair problems in this well
> known state where people here can help you). Then add Packman and use
> the normal “switch to this repo”. After that you might feel the need to
> go for other repos like a newer KDE, etc.

Indeed.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#14

Sorry for the long lull. I have done a “dup” with the OSS, non-OSS, and Update repositories. However, I cannot use USB devices, and the system constantly states that it needs gstreamer-0_10 version 0.10.36.*, which can be found in other repositories that are not enabled. When you say use the normal “switch to this repo”, do you mean the “switch system packages” option in the Repositories tab in YaST Software Management. Thank you.

#15

Now that you say you have the correct repos. pleae show the output of

zypper lr -d

And then specify your two problems better.

a) " I cannot use USB devices". Tell which USB devices those are. USB serves a lot of devices like wireless keyboard/mouse, sound, storage, … End explain what means “cannot use” in for the divices mentioned.

b) “the system constantly states that it needs gstreamer-0_10 version 0.10.36.*”. where does it do so (some loging?), and what is "constantly, I can not thake “constantly” litarely, because then you wouldn’t have any system resources left for doing other things.

And yes, the switch is the “switch system packages to those in this repo” (or words like that) above the list you see when you choose the Repositories View. But first we have to cure your system before we go for Packman and more.