Summary: | Freezes Plasma when lauched from the menu | ||
---|---|---|---|
Product: | [Applications] kcharselect | Reporter: | Antonio Rojas <arojas> |
Component: | general | Assignee: | Daniel Laidig <laidig> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | cfeck, mklapetek, simonandric5 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kcharselect/8a9633827621390cde49b2493a8dc08194d5c2d7 | Version Fixed In: | 15.04.0 |
Sentry Crash Report: |
Description
Antonio Rojas
2015-03-06 07:46:56 UTC
Works with Plasma 4, cannot test Plasma 5 right now. But I wonder why it should be different. Because kcharselect is ported to KF5 in 15.04 Yes, I tested the KF5 port with Plasma 4. This not only affects kcharselect, but almost all new KF5 apps in 15.04. The following apps can't be launched from the menu: cantor kbruch kiten klettres kturtle kwordquiz step kruler kompare and many of kdegames It looks like the porting missed porting the .desktop files Git commit 8a9633827621390cde49b2493a8dc08194d5c2d7 by Hrvoje Senjan. Committed on 27/03/2015 at 02:24. Pushed by hrvojes into branch 'Applications/15.04'. Unbreak KRun powered startup ..by dropping KDE-specific X-DBUS keywords from kruler's desktop file Klauncher expected the app registered to DBus, but the code was never adjusted for that, and there doesn't seem to be a need to do that. REVIEW: 123074 FIXED-IN: 15.04.0 M +0 -2 org.kde.KCharSelect.desktop http://commits.kde.org/kcharselect/8a9633827621390cde49b2493a8dc08194d5c2d7 Antonio, what is the status of comment #4? (In reply to Christoph Feck from comment #6) > Antonio, what is the status of comment #4? These are still broken: - Don't launch at all because of -caption in the command line: kbruch, kturtle - Freeze plasma because of X-DBUS-StartupType: kruler - Both issues: kompare (In reply to Antonio Rojas from comment #7) > These are still broken: By "still" I mean in RC, don't know if any has been fixed since. Should this be reopened for the still broken applications or should I open new bugs (see comment #7)? Ideally open new bugs. Tracking multiple issues in one report is always hard. Thanks |