http://bugzilla.novell.com/show_bug.cgi?id=527213 Summary: Updates don't Update Classification: openSUSE Product: openSUSE 11.0 Version: Final Platform: i686 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: rfengineer@juno.com QAContact: jsrain@novell.com Found By: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.0; Linux) KHTML/4.0.4 (like Gecko) SUSE Both a specific, and a general issue: Occasionally, an update/patch doesn't work. This is not computer specific, as I have 3 boxes all with the same problem right now with the exact same patch/update. The particular box I am on at this instant is configured as follows: ++++++++++++++ CPU: Genuine Intel(R) CPU T2300 @ 1.66GHz Speed: 1,000.00 MHz Cores: 2 Linux 2.6.25.20-0.4-default i686 openSUSE 11.0 (i586) KDE: 4.0.4 (KDE 4.0.4 >= 20080505) "release 15.2" Mozilla Thunderbird version 2.0.0.19 (20081227) Mozilla Firefox 3.0.12 ++++++++++++ The specific issue is an update Mozilla Thunderbird Update 2.0.0.22, which will not complete. It also causes other updates to not complete, unless I uncheck the update for Thunderbird. When checked to complete, the patch will not apply, and will not allow any other patches/updates to apply either. Reproducible: Always Steps to Reproduce: 1.Check for Updates 2."New Software Available" 3.Click "Install" 4.Give Password 5.Returns back to step 2 without installing or applying the new software. Actual Results: Does not install new software, or allow other patches/updates to install. No "don't ever apply this one" option for the operator. Expected Results: Specifically, this patch should be looked into to find the cause of the problem. Perhaps it is a problem with the repository? More generally, though, there should be an OPTION ADDED to allow a specific patch to be deleted from an/or ignored by the patch list (on a permanent basis) by the user at his option if it does not appear to work normally. Of course such an option should come with a warning statement so the user knows that not applying the patch may leave his computer vulnerable to attack, etc. But when there is a problem/issue with a specific patch not working on a specific system there needs to be an "out" for the user, which at present - there really isn't, except for allowing the user to uncheck a specific "bad patch", assuming the user knows which patch is bad. If the user is unaware of which patch is causing his computer to not proceed with other updates, he may wind up with several patches undone, because he is unaware of which patch (or patches ) to uncheck. Additionally, it might be a good idea to allow the operator ( at this time ) to notify the vendor of the problem, by sending a "hey, your patch didn't work on my machine" notice in real time. If this notice grabbed data from the sysinfo:/ file, it would then tell the vendor not only that there may be a problem with the patch, but on what particular system types, os's, microchips, etc. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.