Bug 751623

Summary: Online Update and Software Management and ALL Software Updates/Add and Remove Software in /Kcontrol FAIL
Product: [openSUSE] openSUSE 11.4 Reporter: Scott Couston <scott>
Component: YaST2Assignee: E-mail List <bnc-team-screening>
Status: VERIFIED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Critical    
Priority: P1 - Urgent CC: scott
Version: Final   
Target Milestone: Final   
Hardware: x86-64   
OS: openSUSE 11.4   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Installation logs of an X64 12.1 Install - more software/hardware errors than I can ever write down

Description Scott Couston 2012-03-09 23:39:23 UTC
User-Agent:       Mozilla/5.0 (Windows NT 6.1) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.56 Safari/535.11

Assessing Yast>Software>Software Management fails with the fatal error
pid 2922 (usr/lib/Yast2/bin/y2base

In Kcontrol>Software Management>Installed Software
AND
Kcontrol>Software Management>Installed Software
AND
Kcontrol>Software Managements>updates
AND
Kcontrol>software Management>Admin Tools
AND
Kcontrol>software Management>Security
AND
Every other tool in the Kcontrol>Software Management ALL Fail with the above error

I cannot even find where the default KDE Installation has its auto software update app and Icon in the System Tray - I can find NO application to check for software updates within a default KDE Installation

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Actual Results:  
If you need logs please be very specific but this is 100% reproducible in the community and at suse.DE - best thing to do to rectify this is contained lower on in this bug report - What a shamble of a RC


If you could please open a Opensuse wiki page that contains the information on how to terminate the pid in question and permit the use of Software Management tools in  Yast and Kcontrol and tel us where to locate the auto software updater this would go along way.
At the moment you could release the online bug fix update but the problem is NO one can utilise any Software Update to fix the problem - Thats why I suggest a wiki page on how to kill the pid and be able to perform a software update that has the fix for all this stuff in it.

At some stage we need to rationalise the manhours taken to fix all the bugs, against rushing ALL new releases based on a Calendar Date - Its not working for you overworked and over-bugged developers and the frustration and attrition from opensuse
Comment 1 Scott Couston 2012-03-10 00:22:34 UTC
Best Workaround for this issue I have tried is to boot from 12.1 DVD
Installation>Update>Select root/boot partition>
(Exercise caution here as install can NOT cope with detecting ANY RAID even if you tick 'show all partitions)
Installation>Update>Select root/boot partition>Enable ALL 12.1 Repositories>configure an Internet Address>Change-drop down box>Change to Search Tab>Select ONLY 'Name,Keyword,Summary,File List options>(the search tab can only search on ONE single work)use the word 'software' and search>Package>All in this list>Update Unconditionally

This will update the Packagekit which performs software management!


If your PC is freezing your version of your video river may be the issue.
Retain the same search options as above 
Search for either NVIDIA OR your video card brand>Package>ALL in this list>Update Unconditionally

May the force be with you and Hopefully we will get a fix for software management and an auto software updater soon...best I can do is above
Comment 2 Scott Couston 2012-03-10 02:52:30 UTC
Reverting to 11.3! 12.1 is neither video stable, nor Yast Management stable. Due to massive enormity of the bugs I search for in 12.1 that are significant problems; to label it as a RC is folly.

The man hours to correct the bugs far outweigh the absolute to release a new version based on calendar time/year. 12.1 as it is should have never got to RC given the enormousness nature of the serious bugs against it....I feel for the developers that has such a vast amount of bugs to fix. I have closed as WONTFIX as I believe the huge list of bugs cannot be corrected over a short period of time and is unfair for the developers to try to accomplish the impossible
Comment 3 Scott Couston 2012-03-13 21:18:48 UTC
There IS away to overcome the total ability to perform an Online update - This workaround is quite good but I dont think online updates via this method time initiate - Anyway the work around is easy BUT you should have all the repositories inplace before doing the following 

YAST>SOFTWARE MANAGEMENT>CONFIGURATION>ONLINE UPDATE> - enable Automatic Updates - Enable Agree with Licences - your choice to either enable/disable Interactive 
Patches - Enable your choice of frequency of update>OK >>>> ACCEPT 

A huge warning will be presented (don't worry about ANYTHING IN THE WARNING> The and the package manager will be UNINSTALED which gets rid of all the problems and install necessary files from local storage or DVD and then present you with a traditional Online Update list which you accept

I'm not sure of this will create auto time initiates but you will now be able to perform any Online Updates when ever you want without the package manager and KDE updates!

I have NO idea where the opensuse Online Updates was removed and I have no idea why the KDE updater does not work in 12.  In 11.4 the KDE update Module does work sort of..

Please be specific as to what log files you require to work out why the KDE Control> updates does not function in 12.1

QA/BNC - Please give us back an auto updates that sits in the system tray and auto executes time initiated AND provides a complete list of available update - see other bug regarding updates I have open

Don't even think about closing this as an upstream KDE4 Workspace - Its NOT
Comment 4 Scott Couston 2012-03-15 23:29:37 UTC
I cannot help by uploading any audit logs as my 12.1 X_64 is totally unstable where the Windowing Manager is failing totally exactly after 6 minutes once loaded from normal boot.

I can however provide more insight, fully reproducible event usage, and other notable events that causes the the complete KDE4 Window Manager fails!

The following may help with debugging 12.1 so at least you can make in 12.1 X64 stable enough to use it! As it stands with my X_64 + X11 Nvidia Graphics Card and driver I cannnot use it and I have no choice to revert to 11.4 just to give me a stable O/S!

My hardware is an AMD quad core X64 CPU with a Nvidia Graphics card and I have all auto updates from build services installed at system start! The last window that was opened like Yast>software Management>Online update remains on the screen with the KDE4 Debug crash application and its files installed!

I cannot give you a backtrace from the debug crash handler after following its instruction on the installation of debug software groups that enable a bactrace, and no backtrace is presented by the crash handler application.

I have noticed that the notification app in the system tray warns that the Neo indexing app was aborted just prior to a full crash but I disabled Neo Indexing and after checking the session, Its configured not to start! 

The other meaningful coincidence is the screen times out to be OFF yet the Monitor indicates its NOT in DPMS Mode!

I have only installed package groups from installation but had to manually deinstall KDE's Package Manager that initiates online update date/time.

As its stands 12.1 has NO active and successful auto update installer and in 11.4 the KDE auto update installer fails miserably to instal all updates from all repositories.

Dump all of KDE's software management apps in their Kcontrol System settings and just give us the opensuse updater. I still cannot believe that in 12.1 you have not been unable to combine all System Management to Yast rather that duplicate many and more apps in KDE System Settings. 

The other alternative would be to get rid of Yast and Enhance KDE own System Setting Control Application - We as a community need to decide as we cannot continue to support both - It screws up the head of any new users and, in my experience; is the sole reason for our new users to abandon SUSE and go to
 UBE KDE O/S!

I cannot offer anor supply any log info to help you...Sorry
Comment 5 Scott Couston 2012-03-15 23:32:16 UTC
Sorry I cannot proved any logs to help you see whats going so horribly wrong on my test network. My Online Network is stable at 11.2 - Reporter closed as invalid
Comment 6 Scott Couston 2012-04-19 00:02:46 UTC
Testing KDE software update problems have all but been solved in 11.4 - In this case the BUG that causes out of focus root authority and software issues all works well for me now - Its so much better.

As for 12.1 I'll attach the horror story of an X_64 Installation logs today or tomorrow...The installation failed in so many ways and had to be resolved so many times listing all the issues is an inordinate problem - They all relate to X_64 Hardware issues in the test case...I will leave the status as fixed on 11.3-4 for the fixing of KDE software update issue and attach y2logs on the 12.1 for post-mortem
Comment 7 Scott Couston 2012-04-19 00:24:11 UTC
Created attachment 486827 [details]
Installation logs of an X64 12.1 Install - more software/hardware errors than I can ever write  down

Installation logs of an X64 12.1 Install - more software/hardware errors than I can ever write down