Bug 444730
| Summary: | kdm crashes after upgrade to F-9 due to missing theme | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dean Mander <knolderpoor> |
| Component: | kdebase-workspace | Assignee: | Rex Dieter <rdieter> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | CC: | fedora, kevin, ltinkl, rdieter, than |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-05-10 12:09:51 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 235705 | ||
|
Description
Dean Mander
2008-04-30 11:23:51 UTC
Old themes simply aren't compatible. The new default theme is FedoraWaves.
> Secondly, KDM should use "no" or the "default" team rather than stopping and
halting X.
I agree, please report that upstream to bugs.kde.org.
> Old themes simply aren't compatible. The new default theme is FedoraWaves.
If so, why isn't the incompatible theme changed during my offline upgrade?
Without, it just breaks the system.
I mean, that kind of stuff is exactly the excuse why Fedora promotes offline
rather than live upgrades, so the installer can notify and fix stuff that breaks
because of the upgrade.
> I agree, please report that upstream to bugs.kde.org. for the second problem: http://bugs.kde.org/show_bug.cgi?id=161480 Reopening. Early on in the dev-cycle, I hit that "can't open Theme" error, but it at least didn't crash X. I'll try to confirm that. Ick, ok, confirmed, will continue to track upstream. ok, sorry for the bz spam, reopening, I've got some possible ideas here, mostly involving %post hacks to check for valid/existing themes. Something like "If Theme in
{Bluecurve,FedoraDNA,FedoraFlyingHigh,FedoraInfinity} change Theme to
FedoraWaves" should work.
In sed, that would be: sed -i -e 's!^Theme=/usr/share/apps/kdm/themes/(Bluecurve|FedoraDNA| FedoraFlyingHigh| FedoraInfinity)$!Theme=/usr/share/kde4/apps/kdm/themes/FedoraWaves!g' /etc/kde/kdm/kdmrc or a catch-all to replace all KDM 3 themes: sed -i -e 's!^Theme=/usr/share/apps/kdm/themes/.*$!Theme=/usr/share/kde4/apps/kdm/themes/FedoraWaves!g' /etc/kde/kdm/kdmrc (please test before committing ;-) ). A version of hack from comment #8 is going in kde-settings-4.0-22 fixed build available, please test: http://koji.fedoraproject.org/koji/buildinfo?buildID=47798 Tested but failed.
The %{_kde4_datadir} variable in the specfile must be incorrect,
because it replaces
/usr/share/apps/kdm/themes/FedoraInfinity
with
/usr/share/apps/kdm/themes/FedoraWaves
while the actual theme is located in:
/usr/share/kde4/apps/kdm/themes/FedoraWaves
Hmm... it worked here. I'll have to retest and doublecheck. You used %{_kde4_datadir}/apps instead of %{_kde4_appsdir} (which
is %{_kde4_datadir}/kde4/apps).
Should be fixed in kde-settings-4.0-22.fc9.1: http://koji.fedoraproject.org/koji/buildinfo?buildID=47829 Confirmed. This fixes the problem. Great work! |