I have released porteus-v1.2rc1 so should start getting some reports from users in everyday life now. One thing i noticed with the pretty stuff was that the ksplash-engine-moodin was that it shows up in the kcontrol, but an error message 'This theme requires the plugin Moodin' is received and the splash will not preview. Others give the message that the plugin: default is required. This is also true for the 'fingerprint' splash by Tim.
twin-crystal-theme just doesn't show up in the themes at all.
Can someone please confirm this from a running Trinity desktop. If it is just me then i will start digging.
Jay
Seems this problem exists for me without the ksplash-moodin engine installed. I will recompile tdelibs and base and see whatsup.
Jay
On Tue, Feb 21, 2012 at 4:46 PM, Jay jayflood@gmail.com wrote:
I have released porteus-v1.2rc1 so should start getting some reports from users in everyday life now. One thing i noticed with the pretty stuff was that the ksplash-engine-moodin was that it shows up in the kcontrol, but an error message 'This theme requires the plugin Moodin' is received and the splash will not preview. Others give the message that the plugin: default is required. This is also true for the 'fingerprint' splash by Tim.
twin-crystal-theme just doesn't show up in the themes at all.
Can someone please confirm this from a running Trinity desktop. If it is just me then i will start digging.
Jay
Moodin is a separate thing altogether so it has to be installed separately in order to use some of the splashes. I don't know about the default plugin thing though.
*Moodin is a separate thing altogether so it has to be installed separately in order to use some of the splashes.* Yes, it is in the applications folder and builds no problem. I have since found (after rebuilding everything again) that the themes are broken for me. All themes.
If i run: kcmshell ksplashthememgr
I get the error message that the plugin:Default is not installed. The error in the konsole says that the library could not be loaded. All libraries are in place. The same error appears for any theme, stating that the plugin for the theme could not be loaded. It was working fine a few weeks ago.
Not sure why, or how yet.
Jay
On Tue, Feb 21, 2012 at 6:14 PM, Kristopher John Gamrat < chaotickjg@gmail.com> wrote:
Moodin is a separate thing altogether so it has to be installed separately in order to use some of the splashes. I don't know about the default plugin thing though. -- Kris Gamrat Ark Linux webmaster http://www.arklinux.org/
*Moodin is a separate thing altogether so it has to be installed separately in order to use some of the splashes.* Yes, it is in the applications folder and builds no problem. I have since found (after rebuilding everything again) that the themes are broken for me. All themes.
If i run: kcmshell ksplashthememgr
I get the error message that the plugin:Default is not installed. The error in the konsole says that the library could not be loaded. All libraries are in place. The same error appears for any theme, stating that the plugin for the theme could not be loaded. It was working fine a few weeks ago.
Not sure why, or how yet.
Jay
Are you building under qt3 instead of tqt3? If so I think I know what the problem is, but don't yet have a way to fix it.
Many TDE .desktop files contain a type string, e.g. TQString, that allows the plugin loader to know how to interpret library paths, etc. via the TQVariant class. These were recently renamed to fix loading under tqt3, but I am fairly certain this broke loading under qt3.
The easiest fix is to modify qt3, but I am very hesitant to do that...
Tim
Yep, that sounds like the problem. No problem, i would imagine you would prefer to leave qt3 to the side and develop tqt3 instead and i am happy to wait.
Tomorrow i will rebuild under tqt3 and see how she goes.
Thanks.
On Wed, Feb 22, 2012 at 12:43 AM, Timothy Pearson < kb9vqf@pearsoncomputing.net> wrote:
*Moodin is a separate thing altogether so it has to be installed separately in order to use some of the splashes.* Yes, it is in the applications folder and builds no problem. I have since found (after rebuilding everything again) that the themes are broken for me. All themes.
If i run: kcmshell ksplashthememgr
I get the error message that the plugin:Default is not installed. The error in the konsole says that the library could not be loaded. All libraries are in place. The same error appears for any theme, stating that the plugin for the theme could not be loaded. It was working fine a few weeks ago.
Not sure why, or how yet.
Jay
Are you building under qt3 instead of tqt3? If so I think I know what the problem is, but don't yet have a way to fix it.
Many TDE .desktop files contain a type string, e.g. TQString, that allows the plugin loader to know how to interpret library paths, etc. via the TQVariant class. These were recently renamed to fix loading under tqt3, but I am fairly certain this broke loading under qt3.
The easiest fix is to modify qt3, but I am very hesitant to do that...
Tim
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-
Jay -
Kristopher John Gamrat -
Timothy Pearson