I installed F18 last week, and now when I log in, I get a pop up message box with the subject as the title. The top line then says "Plasma requires an additional service for this operation". Then there is an icon with "script engine" out to the side. Finally, at the bottom, it says "The following service is required. Do you want to search for this now?", and a Continue button and a Cancel button. When I click on the Continue, it comes back with "Failed to search for Plasma service" as the top line, and a big yellow triangle with "Could not find service in any configured software source" There is a Close button that deletes the message box. What is it looking for? What do I do to make it quit coming up? The only other strange thing that I observe that might possibly be connected is that when I try to start yumex, it fails with a message YUM: The value for the SHELL variable was not found the /etc/shells file
/etc/shells has all the entries that are in it on another machine where yumex works.
On 02/25/2013 07:10 PM, Lester M Petrie wrote:
I installed F18 last week, and now when I log in, I get a pop up message box with the subject as the title. The top line then says "Plasma requires an additional service for this operation". Then there is an icon with "script engine" out to the side
We (Kevin Kofler in particular)implemented this feature to install plasma data and script engines on-demand via PackageKit,
https://fedoraproject.org/wiki/Features/Plasma_PackageKit_Integration
So, apparently you had some plasma resource (applet, or whatever) that needed something not currently installed, but apparently it couldn't be found.
-- rex
On 02/25/2013 09:53 PM, Rex Dieter wrote:
On 02/25/2013 07:10 PM, Lester M Petrie wrote:
I installed F18 last week, and now when I log in, I get a pop up message box with the subject as the title. The top line then says "Plasma requires an additional service for this operation". Then there is an icon with "script engine" out to the side
We (Kevin Kofler in particular)implemented this feature to install plasma data and script engines on-demand via PackageKit,
https://fedoraproject.org/wiki/Features/Plasma_PackageKit_Integration
So, apparently you had some plasma resource (applet, or whatever) that needed something not currently installed, but apparently it couldn't be found.
-- rex _______________________________________________ kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
Any thoughts on how to determine what it is looking for, or what applet is missing something? I am not aware of anything missing.
Lester M Petrie wrote:
I installed F18 last week, and now when I log in, I get a pop up message box with the subject as the title. The top line then says "Plasma requires an additional service for this operation". Then there is an icon with "script engine" out to the side.
So this is very strange, normally it should be asking for some specific script engine, like "python script engine" or "ruby script engine". Just asking for "script engine" looks broken to me, and it's no big surprise that it isn't finding it. (The empty string is not a valid scripting language. ;-) )
The only other strange thing that I observe that might possibly be connected is that when I try to start yumex, it fails with a message YUM: The value for the SHELL variable was not found the /etc/shells file
This may or may not be related.
It's possible (but not necessarily the case) that both problems are symptoms of a more profound issue.
Kevin Kofler
On 02/27/2013 08:53 PM, Kevin Kofler wrote:
Lester M Petrie wrote:
I installed F18 last week, and now when I log in, I get a pop up message box with the subject as the title. The top line then says "Plasma requires an additional service for this operation". Then there is an icon with "script engine" out to the side.
So this is very strange, normally it should be asking for some specific script engine, like "python script engine" or "ruby script engine". Just asking for "script engine" looks broken to me, and it's no big surprise that it isn't finding it. (The empty string is not a valid scripting language. ;-) )
The only other strange thing that I observe that might possibly be connected is that when I try to start yumex, it fails with a message YUM: The value for the SHELL variable was not found the /etc/shells file
This may or may not be related.
It's possible (but not necessarily the case) that both problems are symptoms of a more profound issue.
Kevin Kofler
I haven't found a solution to the Plasma Resources problem yet, but the yumex problem was because sudo activates /usr/bin/bash as the shell, while /etc/shells had /bin/bash. I added /usr/bin/bash and yumex works fine. As far as I can tell, I am not missing any plasma resource (unless there is a resource for saving special window settings).
On 03/07/2013 08:32 PM, Lester M Petrie wrote:
On 02/27/2013 08:53 PM, Kevin Kofler wrote:
Lester M Petrie wrote:
I installed F18 last week, and now when I log in, I get a pop up message box with the subject as the title. The top line then says "Plasma requires an additional service for this operation". Then there is an icon with "script engine" out to the side.
So this is very strange, normally it should be asking for some specific script engine, like "python script engine" or "ruby script engine". Just asking for "script engine" looks broken to me, and it's no big surprise that it isn't finding it. (The empty string is not a valid scripting language. ;-) )
The only other strange thing that I observe that might possibly be connected is that when I try to start yumex, it fails with a message YUM: The value for the SHELL variable was not found the /etc/shells file
This may or may not be related.
It's possible (but not necessarily the case) that both problems are symptoms of a more profound issue.
Kevin KoflerI haven't found a solution to the Plasma Resources problem yet, but the yumex problem was because sudo activates /usr/bin/bash as the shell, while /etc/shells had /bin/bash. I added /usr/bin/bash and yumex works fine. As far as I can tell, I am not missing any plasma resource (unless there is a resource for saving special window settings).
I finally got tired enough of the Plasma Resources popping up every time I logged in that I went hunting for a ways to get rid of it. I removed apper and the message went away. I tried re installing apper, and it came back. Since I use yumex, I have removed apper permanently now. This also seems to have fixed a problem with yumex throwing an error pop up when it exits.
Lester M Petrie wrote:
I finally got tired enough of the Plasma Resources popping up every time I logged in that I went hunting for a ways to get rid of it. I removed apper and the message went away. I tried re installing apper, and it came back. Since I use yumex, I have removed apper permanently now. This also seems to have fixed a problem with yumex throwing an error pop up when it exits.
Well yes, PackageKit integration will do nothing if there is no PackageKit UI installed. It's not a fix though! But if it's good enough for you and if nobody else is having the bug, I guess it's fine…
Kevin Kofler
-
Kevin Kofler -
Lester Petrie -
Rex Dieter