Bug 315117 - KDE 4.10.0, Plasma requires an additional service for this operation: qstardict data engine
Summary: KDE 4.10.0, Plasma requires an additional service for this operation: qstardi...
Status: RESOLVED FIXED
Alias: None
Product: apper
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Daniel Nicoletti
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-14 09:34 UTC by G. Landini
Modified: 2014-02-08 09:32 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description G. Landini 2013-02-14 09:34:56 UTC
Installed KDE 4.10 from opensuse 12.2 repositories in 3 machines (all 64 bit version) and in all 3  this error pops up at the start of KDE:

Plasma requires an additional service for this operation
qstardict data engine

The dictionary widget is functional, and the error does not appear if I un-install it. 


Reproducible: Always

Steps to Reproduce:
1. Install the plasma dictionary widget
2. next time you log in KDE you get the error
3. the error popup offers to "continue" and searches for some data engine, but nothing is found. Despite this the dictionary works fine.
Actual Results:  
Error pops up at the start of KDE 10.0 on opensuse 64 bit:

Plasma requires an additional service for this operation
qstardict data engine

Expected Results:  
No errors
Comment 1 Jekyll Wu 2013-02-14 09:52:09 UTC
That message comes from apper. Reassign it to apper developers.
Comment 2 Jesper Goll 2013-03-22 18:15:08 UTC
After upgrading from OpenSuse 12.2 to 12.3, I got the exact same symptoms as described above by G. Landini.

I do not think this an Apper bug. It appears to be related to some kind of mix-up between the regular dictionary widget in KDE (from the Plasma Team) and an alternative, unofficial widget that is not part of the distro, but may be downloaded from software.opensuse.org (search for "qstardict").

The qstardict package is marked as unstable, yet it seems to be the "qstardict data engine" mentioned in the plasma error message (as described above by G. Landini). When I installed it, the error message stopped appearing - and the Plasma dictionary widget suddenly had a new (but empty) settings tab for "dictionaries". Simultaneously it stopped working, in the sense that I could no longer use it to look up English words.

The  regular plasma dictionary is web based - it only works when online. The alternative "qstardict" dictionary, however, seems to rely on a locally installed dictionary database.

Hypothesis:

The present bug seems to be caused by the regular Plasma dictionary widget trying to act as the "qstardict" widget - and then issuing an error when this fails because the qstardict engine is unavailable. After issuing the error, it then proceeds to act in its normal fashion, i.e. using a web-based dictionary.

When I had qstardict installed, I got a sort of "converse" bug: In that situation the widget did find the qstardict engine and so issued no error, but the presence of the qstardict engine then caused it to abandon any attempt at contacting the web-based dictionary. Since I had no local dictionary installed, this rendered my widget unusable.

In other words, I seem to have a choice between a functional widget that issues "qstardict" error messages, and a dysfunctional widget that issues no such error messages. Presumably I could get a completely functional widget by installing a local StarDict dictionary, but I have no wish to do so. The online dictionary works well for me.

Suggested solution:

EITHER remove the interdependency between the regular Plasma dictionary widget and qstardict, so that each is able to function without interfering with the other - OR make the regular Plasma dictionary widget more intelligent to that it reverts QUIETLY to web-based operation when the qstardict engine cannot be found or has no local dictionaries installed.
Comment 3 cushman 2013-04-05 19:21:32 UTC
I just wish to confirm the description given by G. Landini, except on 12.3.  Mine is also a 64-bit system.  The ABC dictionary seems to work fine after the qstardict window gives up looking for the "data engine."  Mine was a clean new install, even though an update from 11.4.

Aside from this very minor annoyance, KDE 4.10 seems to be working very nicely!

B. Cushman
Comment 4 Thomas Arend 2013-05-07 20:09:13 UTC
Can confirm this for  openSuSE 12.2 and 12.3 with KDE 4.10.2 and 4.10.3.

zypper cannot find qstardict in any repository. After "zypper in stardict" I found only a file 
/usr/share/locale/de/LC_MESSAGES/plasma_applet_qstardict.mo
Comment 5 Holger 2013-08-08 08:52:26 UTC
https://bugzilla.novell.com/show_bug.cgi?id=803538

As this other bug-report shows I wonder, if the dialog in question is capable of resolving any package dependencies? At least I would strongly suggest updating it's message to include more details on the exact requirement as to which package wants to install what other package and cannot find it.

For this problem here, I installed qstardict manually, but this didn't silence the message. In addition, qstardict is just an empty dictionary application and I didn't get any compatible offline-dictionary-data along with it.

On the other hand the plasma dictionary with an icon of a red book labeled ABC is still working (only online though).

Currently I help myself with "ding" ... a german english offline dictionary. It's not as explanatory, but better than nothing.

For reference: This is a Kubuntu 13.04 Raring Ringtail with KDE 4.10.5 successively updated two times a year from maybe Kubuntu 07.10 (cannot say when exactly the update last time failed so badly, that I had to reinstall from scratch, but the home directory along with the .kde always got restored from backups)
Comment 6 Rex Dieter 2014-02-07 17:27:07 UTC
The message actually comes from kdelibs
Comment 7 Daniel Nicoletti 2014-02-07 17:29:03 UTC
I'm sure it's an Apper dialog. The request however can come from there.
Comment 8 Rex Dieter 2014-02-07 17:49:51 UTC
Sure, sorry, I was unclear.  The request originates in kdelibs/plasma code, apper is just responding to the request to install missing plasma resources.
Comment 9 G. Landini 2014-02-07 18:46:42 UTC
Actually this bug seems to have been resolved since installing opensuse 13.1
Comment 10 Holger 2014-02-08 09:32:23 UTC
Haven't seen this bug in Kubuntu 13.10 Saucy Salamander anymore (KDE 4.11.3)