|
Bugzilla – Full Text Bug Listing |
| Summary: | opensuseupdater is not started automatically | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Forgotten User --EoyBps8f <forgotten_--EoyBps8f> |
| Component: | YaST2 | Assignee: | Duncan Mac-Vicar <dmacvicar> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | joe_morris |
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Forgotten User --EoyBps8f
2006-12-01 20:22:34 UTC
Check your sysconfig variable (Yast>System>etc sysconfig Editor>System>Yast2>PREFERRED_SW_MANAGER_STACK) and make sure it is set to opensuse. Refer to Bug 2193900 for more info. You may also need to update opensuseupdater. HTH Please recheck with RC/GM/Final if it still does happen there. Yes it still happens with the GM. I had to change the sysconfig-value, which does not make sense to me. Here is why: zen-updater is default, the sys-config thingy is set to zlm, fair enough. I open zen-updater and explicitly disabled "start on login", this is no wish but a command, so the sys-config value should be changed to "". I then started opensuse-updater and made sure that "start at login" was enabled, again that is no wish but a command, hence, and especially if zen-updater is neither running nor set to "start at login", the sys-config value should be set to "opensuse". I think you misuderstood the function of the sysconfig variable. Though it affects the startup of both programs, it is not used by either. There is another program that starts (runupdater) which checks this variable and makes the decision to start the one you set with the variable. If you, in the zen-updater config disable that, it neither affects opensuse updater, the variable, nor runupdater, only zen-updater. If you with the variable are saying to start zen, they by zen's config disable it, you have effectively disabled all your updaters. The correct solution is to set the sysconfig variable used by runupdater to the updater of choice, and you are done. If you do want to disable your updaters, then that is still possible. It is the answer to having several parallel but different updaters, aimed at different scenarios, and make it pretty easy (once understood) to switch to the one you want. HTH. this is not a bug in the updater but the way we handle 2 pkg manager stacks. "Start updater automatically at login" is unambigious and does not work on its own. It does not state "Start updater automatically at login, if sysconfig is set to xyz". So either the text is changed, or it does not work and is thus a bug. It does not make sense to have a checkbox that only works, if something else is changed automatically, without stating it right next to the checkbox. If this checkbox is just meant to supply the possibility to turn the updater off, then the text has to be changed to "Disable starting updater automatically when logging in". Either way, it is a bug! I meant "changed manually" instead of "changed automatically" |