I have finished installing 13.2 on 4 different systems, with only some minor issues.
The installs went smoothly with NO drama.
Kudos to all who worked on this release! Thank you!
Minor issues to solve:
Three of these systems were Lenovo Thinkpads, a T400, T420s and a W530.
All three Thinkpads will dim the display drastically on logoff or shutdown.
The T400 & T420s have Intel display chips. The W530 has Optumus.
Is there some setting available to fix this?
I automatically run zypper after logon to refresh the repositories. On 13.2, packagekitd seems to be
blocking this from running. If I wait and then answer ‘yes’ to 'quit packagekit?’, zypper, may
or may not insert itself between packagekitd running. It looks like packagekitd stops and starts
continually. Is this a bug, or a feature?
Neither of these problems were present on the prior release (13.1). All systems were installed clean (new install).
However, home directories were kept.
zypper cannot be used when packagekitd is running and vice versa.
Only one application can access the package management at the same time. You also cannot use zypper when YaST->Software Management is running and vice-versa.
At login the desktop’s updater applet (which is just a frontend to PackageKit) looks for updates, that’s why packagekitd is running.
It should shut itself down after being idle for 15 seconds with the default settings.
If the updater applet checks for updates again, or you interact with it, it will restart packagekitd again of course.
zypper’s option to “quit packagekit” does not always work (at least immediately) when packagekitd is busy. That’s a known problem, yes, but existed in earlier versions as well. Actually it has improved since 11.x e.g.
IIUIC, the plan is to make it possible that the different packagemanagement systems are not locking themselves out completely, but only if necessary, e.g. when packages are actually being installed at the moment.
But don’t expect improvements in this area before 13.3.
What desktop environment are you using?
In KDE apper always checks for updates on login, regardless of the settings or when it checked the last time.
The only way to prevent this is to disable the “Apper monitor” service in “Configure Desktop”->Startup and Shutdown->Services Manager. But then you won’t get automatic update notifications any more, you’ll have to check manually.
Neither of these problems were present on the prior release (13.1).
Oh yes.
The zypper/PackageKit conflict exists since ever.
That’s why openSUSE has a default PackageKit timeout of 15 seconds, instead of the upstream default of 15 minutes (or none at all in the latest version).
Thanx for the info.
I think that the timing for packagekit starting has changed. In 13.1 the zypper command got there first. In 13.2 packagekit wins. What I think is ALSO happening is
when I answer ‘yes’ to the zypper question, it is causing packagekit to RESTART, and once again blocking. The only way to get this to run is to CLOSE
the terminal opened at login and manually run the zypper refresh…
I added this function because I was seeing a lot of update failures due to stale repository listings. Any suggestions on a better way?
This is a KDE desktop.
No, this hasn’t changed really AFAICT.
But Apper has been updated, and I haven’t looked at the code.
It could just be coincidence as well.
What I think is ALSO happening is
when I answer ‘yes’ to the zypper question, it is causing packagekit to RESTART, and once again blocking. The only way to get this to run is to CLOSE
the terminal opened at login and manually run the zypper refresh…
Yes, that also was a problem in many earlier versions. I remember a bug report from years ago about exactly this.
You can kill packagekitd instead if you wanted to:
sudo killall -KILL packagekitd
This should work in any case.
I added this function because I was seeing a lot of update failures due to stale repository listings. Any suggestions on a better way?
This is a KDE desktop.
Sorry, I do not quite understand this.
What’s a “stale repository listing”? And what function did you add where?
If you mean that your repository caches are often outdated and therefore packages are not found, I’d say just enable auto-refresh for them with zypper or YaST->Software Management…
On 2014-11-07 15:26, wolfi323 wrote:
>
> richardrosa;2673793 Wrote:
>> I added this function because I was seeing a lot of update failures due
>> to stale repository listings. Any suggestions on a better way?
>> This is a KDE desktop.
> Sorry, I do not quite understand this.
> What’s a “stale repository listing”? And what function did you add
> where?
He probably disabled automatic refresh.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Yes, I meant outdated caches. The zypper refresh command was the “function” I was referring to.
This command has been part of my login for quite some time. I added this years ago when I was experiencing update failures due to inconsistancies in the repository states.
It sounds like it is no longer needed.
It was never needed. At least I never had to run “zypper ref”.
If you run it as root, zypper refreshes automatically when necessary and always did (unless you turn off auto-refresh for a repo).
There is a limit though: if the last refresh was less than 10 minutes ago, it does not refresh. You would have to force a refresh with “zypper ref” then.
That timeout is configurable in /etc/zypp/zypp.conf.
PS: If PackageKit cannot reach the repos when refreshing, it might be busy for a long time and seems stuck, i.e. cannot be quit by zypper. So maybe this is the problem you encounter? (again nothing new, some people complained about that when 13.1 was released too).
Do you get errors when running “zypper ref”?
