Bug 406571

Summary:	opensuseupdater-kde reports "Backend plugin is not properly configured."
Product:	[openSUSE] openSUSE 11.0	Reporter:	Randy Cushman <suse>
Component:	libzypp	Assignee:	Thomas Göttlicher <tgoettlicher>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	schubi
Version:	Final
Target Milestone:	---
Hardware:	PC
OS:	openSUSE 11.0
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Randy Cushman 2008-07-04 23:23:03 UTC

After upgrading to openSUSE 11.0 from openSUSE 10.3, I began seeing various errors indicating a problem with "Backend plugin".  The only suggestions in the messages, was to go to Updater configuration and select a backend.  The configuration provided exactly zero backends to choose from.

Steps taken before error was encountered:
- Start with openSUSE 10.3, configured with KDE desktop.
- Upgrade to openSUSE 11.0 Final.
- At this point "this program is deprecated" messages will be generated by opensuseupdater-kde (opensuse-updater-kde-0.6-32).
- Install kde4-opensuse-updater-0.7.17-6.2.
- At this point "Backend plugin is not properly configured" messages will be generated by opensuseupdater-kde.

Workaround:
- Log out of KDE3 desktop.
- Log into KDE4 desktop.
- opensuseupdater-kde functions as expected
- Log out of KDE4 desktop.
- Log into KDE3 desktop.
- opensuseupdater-kde functions as expected

Comment 1 Stefan Schubert 2008-07-08 08:31:40 UTC

Thomas, can you help here ?

Comment 2 Thomas Göttlicher 2008-07-15 15:15:40 UTC

opensuseupdater-kde uses the kde pluing mechanism to know which backends are available.

kde-maintainers, do you know why the restart of the kde sessions is needed? Is there any possibility to avoid this annoying procedure?

Comment 3 Dirk Mueller 2008-07-15 15:58:27 UTC

I've seen it as well, it seems to be caused by kbuildsycoca4 not being invoked, so the cache is not up to date when running under kde3. 

I'd say its a bug in KDE.

Comment 4 Thomas Göttlicher 2008-07-29 10:21:48 UTC

(In reply to comment #3 from Dirk Mueller)
> I'd say its a bug in KDE.
Is there a bug number for kde already? Or should I report this bug?

Comment 5 Dirk Mueller 2008-07-30 15:18:35 UTC

there is no bugreport as far as I know (although I know about the issue..)

Comment 6 Thomas Göttlicher 2008-07-31 07:18:46 UTC

I filed a new bug 413492 for this problem and close this bug.

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