After switching to Plasma 5 from KDE SC 4, I have a couple of small issue, and I wonder if anyone else already has a solution? 1) I'm using SDDM now, but even with KDE4, I was unable to get SDDM to actually launch a Plasma session. After entering my details, I get a black screen and no further activity. I have to switch to another console, log in, and invoke startx myself. 2) I used to have some global shortcuts for launching certain apps. I don't seem able to set these up any more. After setting a shortcut on a lancher in the panel (e.g. Firefox), nothing happens when I actually hit the shortcut combination. 3) Despite installing sni-qt, I'm getting no tray icon for my Telepathy IM contacts. 4) I'm not sure how to get my beloved comic widget back on my desktop :( Paul
Paul Gideon Dann wrote:
2) I used to have some global shortcuts for launching certain apps. I don't seem able to set these up any more. After setting a shortcut on a lancher in the panel (e.g. Firefox), nothing happens when I actually hit the shortcut combination.
Confirmed, please report upstream
3) Despite installing sni-qt, I'm getting no tray icon for my Telepathy IM contacts.
The telepathy tray icon is not a standalone application, it's a plasmoid. So the KDE4 version won't work in Plasma 5. The KF5 version is available in git and will be released in April.
4) I'm not sure how to get my beloved comic widget back on my desktop :(
Not ported yet, will be back in Plasma 5.3
On 16 February 2015 at 13:23, Antonio Rojas
2) I used to have some global shortcuts for launching certain apps. I don't seem able to set these up any more. After setting a shortcut on a lancher in the panel (e.g. Firefox), nothing happens when I actually hit the shortcut combination.
Confirmed, please report upstream
I managed to fix the global shortcut issue through "Custom Shortcuts" in the System Settings. I had to create a new global shortcut command, and that seemed to work fine. I had thought that once a shortcut to an application was added to a panel, setting "Shortcut" on that widget would invoke the application, but that's not the case. The shortcut in the widget configuration panel seems to be a generic setting, which I assume is intended to e.g. open widget panels and other UI-type interactions, such as a folder view. However, global shortcuts are ignoring my keyboard layout. That's a frustrating issue. I'll report that upstream if it's not already reported. Paul
Paul Gideon Dann wrote:
I managed to fix the global shortcut issue through "Custom Shortcuts" in the System Settings. I had to create a new global shortcut command, and that seemed to work fine. I had thought that once a shortcut to an application was added to a panel, setting "Shortcut" on that widget would invoke the application, but that's not the case. The shortcut in the widget configuration panel seems to be a generic setting, which I assume is intended to e.g. open widget panels and other UI-type interactions, such as a folder view.
Ah, I thought you mean adding icons directly to the panel. For taskbar launchers it is to be expected that it won't work, right, as you can't assign shortcuts to individual launchers. For icons, OTOH, assigned shortcuts should launch the application.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Am 16.02.2015 um 14:03 schrieb Paul Gideon Dann:
1) I'm using SDDM now, but even with KDE4, I was unable to get SDDM to actually launch a Plasma session. After entering my details, I get a black screen and no further activity. I have to switch to another console, log in, and invoke startx myself.
i am sure you read the wiki article… maybe something helpful there. you can try autologin and see, if that works. also, check your sessions available. maybe it works in failsafe mode? g -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJU4fFRAAoJELKHx5nAxn3sRcwIAKV/moViOj8Tio4gwBNDrhcL roiiREPSTgadb5hHkVecJ5knhmKHGmw93jkMvC2OquLo16i5vWA9WU9DdZGjupJx /MrSPtPdo6kCbuxw0PbxuW4FXb0AwofAOMZiNYjz23Pkkr4+uzIZilrtqIL7sNQy bfwEw0+9/vfpvoIt5tergh6I4aIcleAZ5vgoqbtbOFEHNfH1v+oaIkogYychpb6i Dw6gRXKztUISkgjcQZ+rxxJgPInUKsFaGgwd+5sf8vAg+VCZmQXmx86ddeHBcSwM jXAgJqYGqgNHX8pWjM9E/IHLGL0uN4yG2RHVIxmBNvD4jQ7+/UtMiBwnq/TRBOk= =/Gf1 -----END PGP SIGNATURE-----
On Monday, February 16, 2015 01:03:36 PM Paul Gideon Dann wrote:
After switching to Plasma 5 from KDE SC 4, I have a couple of small issue, and I wonder if anyone else already has a solution?
1) I'm using SDDM now, but even with KDE4, I was unable to get SDDM to actually launch a Plasma session. After entering my details, I get a black screen and no further activity. I have to switch to another console, log in, and invoke startx myself.
I had this problem too for a while. It turned out that I had zsh misconfigured in some way. I cleared out all my zsh configuration files to start fresh and sddm worked. I still don't know exactly what caused it and it certainly may be an upstream bug, but that solved it for me.
On 16 February 2015 at 18:14, Kevin Ott
1) I'm using SDDM now, but even with KDE4, I was unable to get SDDM to actually launch a Plasma session. After entering my details, I get a black screen and no further activity. I have to switch to another console, log in, and invoke startx myself.
I had this problem too for a while. It turned out that I had zsh misconfigured in some way. I cleared out all my zsh configuration files to start fresh and sddm worked. I still don't know exactly what caused it and it certainly may be an upstream bug, but that solved it for me.
Thanks; you got me on the right track looking into ZSH. I found the fix here: https://github.com/sddm/sddm/pull/358/files This applies to /usr/share/sddm/scripts/Xsession, and I guess it'll be rolled into the next sddm release. Paul
participants (4)
-
Antonio Rojas
-
G. Schlisio
-
Kevin Ott
-
Paul Gideon Dann