SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have the red icon with exclamation mark on my toolbar, which means that the software updater is running and when I click on it , it started to run the software update which ends with the following :Transaction failed: Package transaction failed: You do not have the required access level (superuser) for this method.
The first time you run it, it will ask you to add a privileged user. You probably overlooked that part.
In any case, you can look at "man rug" to add and adjust users. I think that updater is buggy though because, at least for me, sometimes it works and sometimes it doesn't.
No I did add a privileged user name when I started it the first time. Next update, it asked for a su name and password and since then it is as I have described. That is why I posted this thread. I also have a look at the thread which was posted at the same time as mine and read the following: https://bugzilla.novell.com/show_bug.cgi?id=171171.
So I will wait till they repair the bug.
I agree. I got virtually identical results. You could try "man rug" to all rug can do. I prefer to use GUI commands and only revert to CLI for investigation purposes or as a last resort. Having been a system software developer since 1964 I've learned that GUI tends to be more trouble free and successful.
True, you can always still use the 10.0 method as well. I've found over the past 2 weeks that it seems to work better than the buggy tray icon. Yast > Software > Online Update.
True, you can always still use the 10.0 method as well. I've found over the past 2 weeks that it seems to work better than the buggy tray icon. Yast > Software > Online Update.
Ummm, that option no longer exists after I upgraded to 10.1!!!
There's an automatic online update option that doesn't appear to do anything. I did the register/configure thing and the automatic online update just comes up with a pretty empty box that I can click "finish" on. It has some text about adding a cron job, but it doesn't seem to actually do that.
I'd prefer to do manual updates anyways since it's a server. Unfortunately the old online update option is no longer in the menu :-( (I tried to run it manually too and the program doesn't seem to exist anymore).
Distribution: Mac OS X Leopard 10.6.2, Windows 2003 Server/Vista/7/XP/2000/NT/98, Ubuntux64, CentOS4.8/5.4
Posts: 2,986
Rep:
I got the same error as you. The work around is to use the SuSE 10 online update. Unfortunately I forgot the command to do it. I found it randomly doing a google search.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.