Bugzilla – Bug 416316
kdesu - update kde4 can't updates
Last modified: 2010-10-20 18:13:34 UTC
Created attachment 232764 [details] Warn log Then I check updates with tray icon in KDE 4.1 and found new version programs, I choice all and click update, but zypp crash with: kdesu(4356)/kdesu (kdelibs) KDESu::KDEsuClient::command: [/usr/src/packages/BUILD/kde-libs-4.1.0/kdesu/client.cpp: 196] no reply from daemon I click OK and computer again writels: aviable updates and LOOP this! I open Yast2 - managment programs, choice reposity KDE 4 and select all with update if aviable (green icon), click Apply and computer correctly updates KDE 4.1 Why I can't update with Manager Zypp and tray icon in KDE 4.1?
Created attachment 232765 [details] Zypp log
> Why I can't update with Manager Zypp and tray icon in KDE 4.1? Frankly, I really don't know.
Created attachment 233749 [details] Screenshot
This bug might be similar to bug 414284.
Can you reproduce the problem reliably? What is the exact version of kdelibs4 package?
I get the same. :) kdelibs4-core-4.1.1-31.2 kdelibs4-4.1.1-31.2 In my current session it happens everytime I try to update 3rd party repos. I click on "upgrades", "select all apackages" in opensuseupdater and then on "install".
I see the same issue running the latest version of KDE 4.1.1 on 10.3. If I only select patches and uncheck "Keep Password" it seems to work OK. Any other combination (e.g. check "keep password" or select any upgrades) generates the error message as described above.
Some more info was provided, and more duplicates.
I just generated the same error today updating kde4-kpackage to 4.1.3-22.1 on 10.3. The error occurred after the package was updated but before opensuseupdater-kde rechecked for updates after the install.
*** Bug 445311 has been marked as a duplicate of this bug. ***
I may have stumbled across a clue this morning - whether it is relevant or not I'm not sure. I had 190 available upgrades including boost and boost-devel 1.34 -> 1.36. I know that the boost packages have dependency conflicts with yast2-squid-2.16.3-37.1.i586 and atom-project-0.4.-0.pm.1.i586 (from checking manually with Yast2) but I left them selected anyway. The process failed with the "no reply from daemon" message. I reselected all updates and deselected just boost and boost-devel and the update process ran fine. Is it possible that this message is being triggered by dependency conflicts (at least as part of the cause)?"
Is there somebody who can reproduce this for a case when manual online update using yast2 does not report any problem (such as a conflict)?
No responses, 11.0 is no longer supported, closing.