|
Bugzilla – Full Text Bug Listing |
| Summary: | Autoupdate applet issue with update | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Forgotten User CxVz4LpaB5 <forgotten_CxVz4LpaB5> |
| Component: | YaST2 | Assignee: | Thomas Göttlicher <tgoettlicher> |
| Status: | RESOLVED NORESPONSE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Forgotten User CxVz4LpaB5
2008-05-21 22:52:46 UTC
Could you provide more information please? Does the applet show any error messages? Without additional details it is hard to find this bug. I guess I know what the problem is. You are asked for the root password, after entering the password nothing happens?!? Please try to uncheck the "keep password"-checkbox and try again. If it works in this case, it was bug 389765. Can you confirm that? You are correct for 1 of the issue. The applet show an icon telling me that they are some updates available, then I open it and prompted for password and nothing happens. another issue is that some update seems to be hidden. Maybe it is resolve with the last update of the update library... It happens like this: - I have opened yast and then selected the online uptate - only some update related to kde appear (1 or 2) - when I start the update, I am prompted to installed additional updates/packages and a warning tells me that some of the update concern the yast update itself, which is strange because I was not seeing it. - The update goes and finish and all seems to be fine this time. Like I said maybe it is related to a bug with the update library/program which the latest update resolve. If this is the case then the bug can be closed. I will update the report as soon as I can install additional update or maybe try the release candidate. You are right, the 2nd part of you report sound like bug 390769. Looking forward to your next test with the release candidate. Thanks in advance. Does the problem still exist on RC1? Not yet tested, but I will update this report as soon as I can. Bug closed because of no response for more than one month. |