Summary: | unable to create new activities with the user interface | ||
---|---|---|---|
Product: | [Frameworks and Libraries] plasma-activities | Reporter: | trekrek |
Component: | general | Assignee: | Ivan Čukić <ivan.cukic> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | plasma-bugs, rdieter |
Priority: | NOR | ||
Version: | 5.20.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
trekrek
2016-05-06 14:06:26 UTC
I can confirm this testing on f24/x86_64 with plasma-5.6.3 + kf5-kactivities-5.21.0 Does this button work in the activity switcher? (Meta + q by default) Can you test with Plasma 5.7.2 (or older 5.7) since this seems like a problem in the installation/packages related to the repository transition we had for 5.6. still present in plasma 5.7.1. I will test it again when packages for plasma 5.7.2 will appear in the repositories. The button works in the activity switcher and also under system settings->desktop behaviour->activities Wait - activity switcher *and* system settings work, but kcmshell does not? That is strange for a few reasons: - The code is shared between all three - The code is the same for system settings and kcmshell - that is, both load exactly the same dialogue. Is there a live ISO with all the packages updated where I could test this? yes only kcmshell doesn't work. There is only this one https://spins.fedoraproject.org/kde/download/index.html but it's quite old as you can see here http://archive.fedoraproject.org/pub/fedora/linux/releases/24/Spins/x86_64/iso/. I'm downloading it to see if the bug is present (it should be there in principle, since it's newer than my first post) Thanks for being an active bug reporter :) yes you can use that live image to reproduce it I forgot to reply - the activity creation dialogue opens, but it does not go above the main kcmshell window. There was a bug in kcmshell which was fixed some time ago (can't remember whether the fix is in 5.7 or it will be released with 5.8). it's fixed on 5.7.5, I didn't test in 5.7.4, but I'm quite sure that I've tested it on 5.7.3 and it was not fixed. So the fix is either in 5.7.4 or in 5.7.5. Thanks |