Hi,
(openSuse 13.1)
Yesterday I done full update (after a week). It downloaded 1.1GB of updates, installed sucessfully. These problems occured:
When lid is closed, it ignores settings for suspend (yes, i have checked confuguration and its OK)
Nearly nothing works from yast2 control center, online update, install and remove sowftware, nothing works. It starts some process according to cursor icon, but nothing happens.
When starting install and remove from main menu, its ask for password as always, but it dindt start up.
So now i am stucked with updating or configuring anything from gui. I haven’t enough time to try other options.
Any suggestions what to do?
I love this os, i installed it 2 weeks ago. Now i got job, and i don’t want to reinstall and set up everything again.
What desktop are you using (KDE, Gnome, or other - tell us which);
Did you reboot after that large update?
1.1G of updates is large. But if you are using KDE, there was a recent KDE update. So might have been 1.1G or more. The thing about a large update such as that, is that it can leave you running software in an inconsistent state. So rebooting is advisable.
It’s hard to know what the problem is, given the small amount of information you have provided. So tell us which desktop you are using. Maybe give us the output from:
erikkubica, further to nrickert’s advice, it may be useful for you to advise us as to what repositories you have enabled. That is because what you have experienced is not nominal, and knowing what may have caused it could possibly help as well in finding a solution.
Please, could you send the following command in a terminal/konsole, and copy and paste the output here (please paste it in between code ] … /code ] tags ) :
2014-02-14T07:53:08.693871+01:00 linux-rwt0 gnomesu-pam-backend: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring-uD5T9F/control
2014-02-14T07:53:08.694536+01:00 linux-rwt0 gnomesu-pam-backend: gkr-pam: couldn't unlock the login keyring.
2014-02-14T07:53:08.705393+01:00 linux-rwt0 gnomesu-pam-backend: pam_systemd(gnomesu-pam:session): pam_putenv: delete non-existent entry; XDG_RUNTIME_DIR
But i think this have nothing whit lid closed problem is suspend manually works. And if it helps, i have Lenovo B590 i5 2.5GHz turbo 3.10GHz, 8GB of memory, with indel hd 4000
The reason is clear: you added the Factory repo, thus when you updated,
you updated to the Factory release (or rather, a mix). Factory is, by
definition, not stable. It is where things are tested, and often they
break (more at the start of the dev cycle). And using a mix, things are
bound to break.
So do what caf4926 says.
I also see you have two packman repos. Ie, you have repeated repos.
Choose one, remove the other.
You also have “videolan”. It is not advisable to simultaneously have
packman and videolan, you get problems. Choose one.
I would do that before doing the “zypper dup”.
Probably I should also mention that if you see repos labeled
“tumbleweed”, they are similar to factory, in the sense that they mean
“different release”. If you are interested in tumbleweed, there is a
wiki page that explains it. Quite bleeding edge, and problems of its own.
The package management tools will not even warn you when you add
repositories for a different release, even if you shoot your own foot by
doing that.
On 2014-02-14 15:46, erikkubica wrote:
>
> robin_listas, its right. I think both are good. There are huge
> discusions about rpm vs deb, but its something like Java vs C#.
Well, repo release checking is something that people have been
requesting from devs, for some time. It would be a good feature. You are
not the first person to been bitten by the lack of it.
It is simply that old hands are aware of it, and we double check what
repos we add. If I were to use Debian instead I would be surely in
trouble, not been used to it.
> commands posted by “caf4926” worked perfectly, now everything is working
> perfectly. Thank you very much for everybody who tried to help me.
I used debian based distros for 5 years. I started with openSuse because to learn somethin new.