Bug 742749

Summary: kdebase4: Fix crash when toggling the menu-bar visibility - hangs SW Man & stomps YaST´s Online Update
Product: [openSUSE] openSUSE 12.1 Reporter: Guenter Huber <guenter_huber22>
Component: KDE4 ApplicationsAssignee: E-mail List <kde-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: ctrippe, guenter_huber22
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 12.1   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: patterns-openSUSE-kde4_basis-12.1-25.21.1.x86_64 requires dolphin, but this requirement cannot...

Description Guenter Huber 2012-01-21 13:46:00 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1

openSUSE-2011-86 - kdebase4: Fix crash when toggling the menu-bar visibility

Update package hangs Personal Settings / Software Management in a loop when you Yes "You are about to install unsigned packages... proceed..?

("Yes" catches you in the loop, but as there were 79 packs in the initial update after install... <argh>)

YaST / Online Update handles this (like other things!) more gracefully, telling a corruption problem with the Dolphin dependency.

Reproducible: Always

Steps to Reproduce:
"Interesting": In the last couple of days I installed 12.1 on
Win Server 2008 R2 Hyper-V
VMware Player on top of Win 7
to the hardware of a Tosh quad core...

...and it didn´t happen until today where I changed the Software to be installed.
Actual Results:  
SW Man loops until your mouse finger gets tired. ;-(

Expected Results:  
Dependent Dolphin update to work.
Comment 1 Guenter Huber 2012-01-21 13:49:51 UTC
BTW: The OS popup int he rep didn´t have a 12.1 item!!!
Comment 2 Guenter Huber 2012-01-21 13:53:08 UTC
Created attachment 472195 [details]
patterns-openSUSE-kde4_basis-12.1-25.21.1.x86_64 requires dolphin, but this requirement cannot...
Comment 3 Arvin Schnell 2012-01-31 09:33:20 UTC
Product is "openSUSE 12.1", OS is "openSUSE 11.4". Why do they differ? With
which version do you have the problem?
Comment 4 Guenter Huber 2012-01-31 09:53:44 UTC
(In reply to comment #3)
Because when I entered the bug through the form the Platform popup didn´t have a "12.1" item. (see Comment 1) Now it has. At least I can see it now. <g>
Thx
Comment 5 Arvin Schnell 2012-01-31 10:30:39 UTC
I'm unsure what program actually hangs. Where can I find this "Personal
Settings / Software Management"?
Comment 6 Arvin Schnell 2012-01-31 10:41:51 UTC
Ok, I have found the program. Looks like an KDE application not YaST.
Comment 7 Guenter Huber 2012-01-31 10:57:59 UTC
(In reply to comment #6)
> Ok, I have found the program. Looks like an KDE application not YaST.

<g>
Was puzzled either the first time I stumbled over it.

When I tried to change Network Settings from YaST it told me Network Manager owns that now and it could be problematic to change it from Network Settings.

If you search for Network Manager in the menu you don't find anything. NetworkManager (w/o space) wins you no pot either, but NetworkMa to NetworkManag filters the choices to 2 items, where "Network Connections" is easily identified as the correct one.

Puzzling for new users. Two GUI interfaces competing no good.
Thx
Comment 8 Guenter Huber 2012-01-31 14:34:57 UTC
Situation seems resolved partially!
1) Got back to the machine where the hickup occurred and saw several fixes were pending in YaST Online Update, including kdebase and Dolphin.

This time the update process went smoothly. I can only guess that someone fixed the Dolphin patch.

(Well, there was a problem with KDE and the nVidia developer driver (instead of nouveau), but I guess this is related to some other update and a driver install fixed it.)

2) Remains the problem that Personal Settings / Software Management catches you in an infinite loop when a patch is faulty.

If you Yes the "You are about to install unsigned packages... proceed..?" question it will NEVER proceed.

If you say No it will abort the update process altogether.

Only in YaST / Online Update it became clear what the problem was.
Thx
Comment 9 Christian Trippe 2012-01-31 19:32:01 UTC
As 1.) one fixed and 2.) is a duplicate of bug 731301 I will close this bug as such.

*** This bug has been marked as a duplicate of bug 731301 ***