I’m using KDE 3.5.9 with opensuse 11.0.
As a normal user I can’t start opensuseupdater-kde. It comes up with the error message
user@machine:~> opensuseupdater-kde
opensuseupdater-kde: symbol lookup error: /usr/lib/libkdeui.so.5: undefined symbol: _ZN13QWidgetAction11eventFilterEP7QObjectP6QEvent
I CAN run it as root but the next login it won’t start again although I marked “Automatically start updater on login”.
Does anyone have the slightest idea?
I don’t think I can open a bug report because I’m pretty sure that not everybody is experiencing this behavior. 
After I istalled some safe packages, just some media codecs and some safe updates (all varified as having no dependency issues) using package manager in yast all was good until I noticed the update icon on the menu bar was telling me there were more updates that affecting my update manager itself. Curious, I clicked install updates, was prompted to put in my password and told it was not the root password. It gets worse I then tried to go back to yast, and couldn’t open in it because again I was told my password was wrong. Yep you guessed it I am now locked out of all root privelleges and can’t get them back. This was actually the 2nd time it happened. The first time I had installed just updates, and then the icon said there were more, but I hadn’t noticed I’d lost my password until the next day, and so didn’t know why my password was invalid and reinstalled my whole system only for it to happen again. At least I know what caused it now though. Now this is either some serious bug with the update manager in the tool bar, or someone has managed to slip some pretty malicious code into the updates I’ve been downloaded. Either way, very worrying and making me think of switching back to linux mint. Any ideas which of the 2 scenarios it is?
Also should let people know I have 64 bit version with KDE 4, which when I downloaded recently claimed to be quite stable
Sorry about not really answering answering you question there either and going on about my problem which now I read again was quite different. I’ve got no idea how to answer you question as am total beginner with Suse and linux in general. However, on Linux mint xfce I often had trouble logging in as sudo root unless I was actual in the admin account that was used to operate as root. It would depend on the situation of course. So, without knowing much about linux yet, I would guess that sometimes there are occasionally some minor bugs in the directories in distro’s where an account is to act as root. This would presumably mean you could wait for the experts to slowly fix these bugs, or would have to alot about debuging and program language. Otherwise you’ll just have to log in as you main admin account when you want to do these things. That was what I did with mint xcfe. Anyway, I have no idea how experienced you are and am probably telling you stuff you already know and you wanted someone more experienced to give you more in depth answers and I’m only guessing so I think I’ll leave you to it now. As to my problem, if anyone is interested, it turned out that it was only yast I could not get into temporarily with my root account. ONLY yast. lol. It had sort of frozen because I had used it, combined with my update aplet to try and install upgrades on itself (like trying to do surgery on yourself I suppose). After I managed to get into yast through different menu options, it seemed to quickly finish the update and then I could once again get access to yast. However, my update aplet remained out of service for some times until I mucked around with the settings which had somehow changed during the update. I apologise if my threats of going back to mint over such a little issue offended anyone. I have noticed this type of comment can cause some controversy in the forums. I am going to keep going with Suse and have mint on another partition, which was my plan in the beginning since leaving macs and windows behind. Anyway, have a good day all who bother to read my ramblings. Steve.
Kommx, that’s a bizarre error. If it runs under root but not under your local, then there’s likely a permissions problem. Without knowing more (ie. when did it stop working, did anything change with updates etc.), I would simply suggest re-installing it via Yast. The install scripts that are part of the rpm may repair anything that has gotten borked. This is a shot in the dark, though…
Steve_2, welcome to the forums… Input is always appreciated, but if I can make one request, please use your enter key when entering comments, paragraphs are good… 
Cheers,
KV
I agree with KV about using paragraphs. That is hard going reading that!
Might I suggest you switch the updater OFF. (I never use it) But you can, just turn off and try this:
If Yast - Software - Software Management is working, open it.
Filter by repo
Select ‘System’ - it’s at the top of the list (this is in kde, I understand it is different in gnome)
then from packages tab (top left of screen)
select: update all in this list unconditionally.
This will re-install all your system packages
If you have high speed internet it doesn’t take long.
This may help to resolve your issue. Get back to us if you need more advice/suggestions.
@else_where:
Just reinstalling the updater package didn’t help.
Now I’m updating all packages as caf4926 proposed. That will be > 4 GB so it will take some time.
I’m going to post again after the updating is done.
It’s done, I updated all installed packages but it changed nothing. 
I don’t know when the problem occurred but I’m sure that it DID work a few weeks ago. I don’t know what caused it to happen.
Just don’t use it for now
Manage updates with software management, I always do that.
You can work on the issue in the mean time
You could try the command line in a console.
Type su then root pass then zypper dup -l (that’s a lower case L)
Geoff
I’m pretty up-to date
machine:~ # zypper dup -l
Reading installed packages...
Nothing to do.
uh…OK…this is something I HAVE been wondering about. SHOULD a normal user be ABLE to run an update? I think not! I disabled the updater for my normal users. Lordy!
How about just don’t go there.
uh…OK…this is something I HAVE been wondering about. SHOULD a normal
user be ABLE to run an update? I think not! I disabled the updater for
my normal users. Lordy!
How about just don’t go there.
kayschenk’s Profile: http://forums.opensuse.org/member.php?userid=16040
View this thread: http://forums.opensuse.org/showthread.php?t=399411