Summary: | Unable to start ksplashx when testing user installed splash themes | ||
---|---|---|---|
Product: | [Plasma] ksplash | Reporter: | Antenore <antenore> |
Component: | general | Assignee: | Lubos Lunak <l.lunak> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | antenore, dtombaugh, gluk47, kairo, kde, kde, mail, phlogi1, tomasdeltell, vivymarcy |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Antenore
2008-08-05 10:42:23 UTC
I can confirm this happens on debian too. I am using kde 4.1.0 from debian experimental. I was reporting the wrong package version. Name: kdebase4-workspace Version: 4.1.0-37.5@i586 *** Bug 169725 has been marked as a duplicate of this bug. *** This bug still exists in KDE 4.1.2@Mandriva 2009.0 snd this bugfix still solves it :) But this should be simple to change one path in one module, isn't it so? I can confirm this on Mandriva 2009.0 and KDE 4.1.2 I can confirm this on opensuse 11 and kde4 (4.1.3). Although I can not remove them from the $home/.kde4/share/apps/ksplash/theme directory and still have them work. I need a copy in both places. any news? I still have the same problem as well... no news from kde team Here I can't even see any new splash in the list of available splashes after installing a new one with GetHotNewStuff. However in GetHotNewStuff itself it says its installed.... SVN commit 899901 by gkiagia: Use KDE_DEFAULT_HOME instead of hardcoded ".kde" This is required to be able to preview and use themes installed in the home directory (probably downloaded via get-hot-new-stuff) in all distros that do not use ~/.kde as their default KDEHOME. BUG: 168394 M +1 -1 splash.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=899901 Confirmed, exists still in 4.2.0 tobias?? I have fixed this before 4.2.0 and it works fine here with 4.2.0 installed. What exactly are you experiencing? Do you see the "unable to start ksplashx" message? (In reply to comment #12) > tobias?? I have fixed this before 4.2.0 and it works fine here with 4.2.0 > installed. What exactly are you experiencing? Do you see the "unable to start > ksplashx" message? > Tobias is not wrong. I confirm the issue has never been fixed. What I wrote in my first post is still the same except for the package versions. I even cannot see the new themes I installed. Let me (us) know which information you need and we will provide it to you. Thanks in advance (In reply to comment #13) > I even cannot see the new themes I installed. That happens with some themes. The problem is that the themes are broken! An example of a working theme is "Glassified Splash" (appears 1st in highest rating sorting order). I just downloaded that theme from the get-hot-new-stuff dialog and tested it just fine. So, please do the following: 1) Make *sure* you are using ksplashx from kde 4.2.0 (or later) packages. 2) Download and test the theme I mentioned above. PS: Why did you set the status to "WONTFIX"? Did anybody say that kde developers don't want to fix this bug? I'm reopening now... (In reply to comment #14) > (In reply to comment #13) > > I even cannot see the new themes I installed. > > That happens with some themes. The problem is that the themes are broken! An > example of a working theme is "Glassified Splash" (appears 1st in highest > rating sorting order). I just downloaded that theme from the get-hot-new-stuff > dialog and tested it just fine. > > So, please do the following: > 1) Make *sure* you are using ksplashx from kde 4.2.0 (or later) packages. > 2) Download and test the theme I mentioned above. Yes, you are right!!! I'm wondering why there are so many broken splash themes, and why are visible if broken. Would be possible to have a kind of check? > PS: Why did you set the status to "WONTFIX"? Did anybody say that kde > developers don't want to fix this bug? I'm reopening now... > Sorry I surely changed the resolution by mistake, was not my intention, apologizes. Could you please retest with Plasma 5 and reopen if this is still a problem. Thanks. |