|
Bugzilla – Full Text Bug Listing |
| Summary: | updater-applet (KDE) does not install recommended updates, repeatedly suggests new software available | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Stephan Diestelhorst <stephan.diestelhorst> |
| Component: | Update Problems | Assignee: | Thomas Göttlicher <tgoettlicher> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | axel.braun, dimesio, farcusnz, henk.vanvelden, stephan.diestelhorst, tgoettlicher, zaloha |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Relevant tail of zypper.log for update transaction.
German log of zypper update operation. sudo zypper up - Output, german Relevant part of zypper.log, again failing to use updater-applet sudo zypper up - Output, german (correct version) |
||
|
Description
Stephan Diestelhorst
2008-05-09 09:56:24 UTC
Created attachment 213852 [details]
Relevant tail of zypper.log for update transaction.
Apologies, seems to be similar to bug 360518, running "zypper update" helps, although no manual intervention was necessary. (German, apologies) Log of zypper update attached. *** This bug has been marked as a duplicate of bug 360518 *** Created attachment 214641 [details]
German log of zypper update operation.
Reopening, because: Today new updates were available, using the updater-applet did not work again, as originally reported. Running "sudo zypper up" however did the trick again. Will attach logs and output (again in german, sorry!). Created attachment 216827 [details]
sudo zypper up - Output, german
Created attachment 216830 [details]
Relevant part of zypper.log, again failing to use updater-applet
Created attachment 216832 [details]
sudo zypper up - Output, german (correct version)
Sorry, mix up. This is the output of the recent zypper up operation.
Had this before, today again. When only 'recommended' updates are signaled no installing takes place and the signalling is repeated (orange star). Using YaST > Software > Online Update works fine (I suppose like the CLI zypper users above). Also when later a 'security' leel update joines the list openSUSE Updater is OK. I've had this problem for the past couple of weeks. Manually updating with zypper clears the problem temporarily, until the updater finds the next set of updates. I did find a suggestion in a forum to try unchecking the "keep password" box when entering my password to update, and that did solve the problem, at least for today. This only started happening for me recently, and I've been using 10.3 since last December. I said above tha it will happen only with 'recommmended'. This is not true, it happens always. I just got a new update. First try gave the old problem. Then I tried Rosanne DiMesio's solution and unchecked "keep password". This worked! (In reply to comment #9 from Rosanne DiMesio) > This only started happening for me recently, and > I've been using 10.3 since last December. Yes, I can confirm: The problem appeared in the last weeks, not since release of 10.3. The workaround with the 'keep password' box is a workaround, but not a solution (think about newbies using openSUSE!) Thomas, is this known to you? On early openSUSE 11.0 beta versions was a similar bug in kdesu from kde4. A workaround was to remove tab characters from the command that is passed to kdesu. (See: bug 389765) It is the first time that I've heard about a similar bug on openSUSE 10.3. Due to the fact that opensuseupdater works on zillions of workstations I guess the cause for this bug is different. This is a bit too easy. As everybody states this bug is introduced in 10.3 about one month go. I do not hope that the fact that it is so young means that it is not serious. I do not know about the zillions, but are you aware of the facts that: a) a lot of people do not use the applet, but prefer to use YaST > Online Update evry other day or so; b) there are several threads in forums.suselinuxsupport.de about this problem (with workarounds provided by those who found it first) and that the number of people who found these threads, and thus did not complain at all, might be a multitude of this? I have the same problem (maybe last several weeks).... OpenSUSE updater applet indicates update(s) => I try to update this way => nothing happens, after some time updater indicates update(s) again.....and so on (neverending). The update repository setting is correct, update via zypper or YAST is OK. After such update(s) applet indicates "No updates available" - that means it is able to recognize the right update status, but it isn't able to initiate the update process... What is interesting: I have 10.3 on two machines (desktop and notebook), the problem appears only on desktop... Correction after today test: the same problem is also on my notebook... Two days ago there was a recommended update about timezones (Pakistan and a few others) anounced by the applet. I tried to install via the applet and it worked! This morning the appplet anounced an apache-php security update. I tried again and it installed! So the problem is gone but no clue about the why and how?? The problem is not gone for me. I just tested it on a recommended update--I can still only install through the updater if I uncheck the keep password box. It would be less annoying if I could permanently uncheck that box, but it keeps defaulting to being checked. I also see this in 10.3 - have had it for the life I have had 10.3 - seems intermittent. Very annoying. I can confirm the situation described above: if I uncheck the "keep password" box, the update(s) run correctly. But such "feature" is new (maybe several weeks?)... Looks like the same problem is also in openSUSE 11.0 / KDE 3.5.9, as I just learned with today's kernel-update..... Due to comment #20 I'm sure the bug is not in the updater applet but in kdesu. *** This bug has been marked as a duplicate of bug 389765 *** |