I’d been putting up with this stupid “unknown role” nonsense since I upgraded to 13.2 a week or two ago. And I submitted to the nonsense about being unable to review the details of the updates due to the stupid interaction with Packagekit.
Tonight is the last straw. Apper has to go.
I ran the updates for zypper, rpm, and Packagekit an hour or so ago, and all appeared to go well. I logged out and logged back in as requested (another nice Microsoft Windows touch I’ve never seen in Linux until now.)
Then I had 48 or so updates reported including Flash, Thunderbird, a number of openSUSE security updates and the usual plethora of audio library updates. I hit install…and nothing happened. It just sat there. I couldn’t cancel it, either.
I tried running zypper from the command line and it tells me Packagekit has the files locked and would I like to tell Packagekit to stop. So I say yes, and it comes back and says Packagekit is still running. Nothing can shut down Packagekit except kill -9.
I reboot the system. Same situation - 40-odd updates, nothing happens when I click install.
So this time I kill Packagekit and run zypper up from the command line. That works. So it’s clearly not the update process that is broken, merely this POS apper.
So now, like a lot of people, I’m going to disable apper and only run periodic updates using zypper from the command line or update via YAST.
This apper garbage needs to be fixed as a priority. It is no longer a “cosmetic issue” which that “unknown role” nonsense. It is BROKEN.
No need to rant. Every time you login, Apper starts anew looking for updates. When you at the same moment start YaST/zypper to do the same, they complain becaue there maybe only one busy at the time. Saying to YaST/zypper to carry on is useless unless you first stopped Apper. And loging out/in (with ot without reboot) is also useless, because Apper immediatly starts on login and you fail to wait for e.g. 30 mins (take a coffee, or do some usefull work on your computer) before starting YaST/zypper. That is the nice/nasty thing with computers: when you repaet things, they work out the same every time.
That said, I do even not install Apper and Packagekit on system installation. One of the most important reasons I use openSUSE is YaST. Including YaST > Software. Thus, why would I change to PackageKit?
“Every time you login, Apper starts anew looking for updates. When you at the same moment start YaST/zypper to do the same”
That is NOT what I did. I installed the first round of updates some time previously before the second round. Apper had PLENTY of time to finish its search and in fact it did because that’s when I finally saw the second round of updates.
“Saying to YaST/zypper to carry on is useless unless you first stopped Apper.”
If you’ll read what I wrote, zypper came back and said Packagekit had the files locked and would I like to tell Packagekit to quit. Note that this was AFTER apper simply sat there and did nothing when I told it to install. I did so. Packagekit did not quit. If Packagekit cannot be stopped, then why is apper asking me if it can be? That is just stupid design. Again, this was AFTER apper had already determined what updates were available.
“And loging out/in (with ot without reboot) is also useless, because Apper immediatly starts on login and you fail to wait for e.g. 30 mins”
It never takes 30 minutes on my system. Apper usually reports updates within a few minutes of logging in. The only time I’m logged out on my system is if I have to shut down because of some mess or if I’m asked to by the update process - which has only happened twice over the last couple days. And that’s a first, too - I’ve NEVER been asked to log out except for a kernel update in the past.
“That is the nice/nasty thing with computers: when you repaet things, they work out the same every time.”
I’ve been using computers for thirty years. I don’t need a lecture on their behavior.
Apper BROKE due to some update or its own poor implementation. It’s that simple. Making excuses for a utility that can’t even present a competent user interface (“unknown role”) and an inability to work with the rest of the system properly (Packagekit) is not appropriate. The developers need to get off the stick and fix this ****.
Sounds like it is broken for you. Not all are seeing what you are though. If you did an upgrade to 13.2 from an earlier ver which is??? Then there is a possibility of corrupted or outdated config files.
On Sun, 25 Jan 2015 02:36:01 +0000, richardstevenhack wrote:
> Actually, yes, there is.
This isn’t really the venue to rant about it, though - this is a user
community, so ranting about it here (a) isn’t going to get the
developers’ attention, (b) is only going to alienate people who will be
able to help you work around the issue (or resolve it for your situation).
Have you filed a bug on this in bugzilla, complete with steps you use to
reproduce the behaviour? As someone who has used computers for 30 years,
you must know that reproducibility is something that helps developers
find bugs and resolve them, and that a good bug report includes steps,
symptoms, output, and log information.
We understand that you’re frustrated; as fellow users, we feel your pain,
even if we don’t see your specific issue on our systems. That doesn’t
mean you need to come into a user support forum and start yelling at
people who are here to help you.
Of course, if your intention wasn’t to ask for help, then perhaps a forum
for user support isn’t the right place for you to be.
Further to that, if you are not actually seeking help (but just ranting), then the soapbox forum is appropriate. This sub-forum is for requesting help.
Actually I have a broken system, too, after running package kit updates. System locks after grub. Just made fresh reinstall, result system freezed. Now I made a install without running updates and system is back. So must be a bad kernel update.
On 2015-01-25 15:16, max spam wrote:
>
> Actually I have a broken system, too, after running package kit updates.
> System locks after grub. Just made fresh reinstall, result system
> freezed. Now I made a install without running updates and system is
> back. So must be a bad kernel update.
Totally different issue with many possibilities than the issue
“reported” by this thread.
I can remember a recent one with uefi secure booting, another conflict
between rpm, libzyp and spaces in file names… those two can hit a
system using apper, zypper or yast just the same. And both can break
badly a machine.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
hello,
following the above instructions offers the solution of the problem and is liable to calm down the dispute.
I’am working now with o.S. 13.2 on 3 laptops, all of the upgraded from 13.1 with zypper .
