Hello openSUSE KDE users and contributors,
This mail outlines our plans for moving towards Plasma 5 as a default desktop for the next openSUSE release, includinga tentative action plan and where help from you all is required. We do not believe on pushing changes on users without some sort of preparation, therefore this document describes the transition plan.
See the previous mails for a rationale of this decision.
==== The plan ====
Phase 1: Gather input from the community
In this phase, we would like people from the community, if they are able to, to test the currently-available code. It's quite easy, as all the required software is already available directly in Tumbleweed. You should install Plasma 5 from there (bear in mind that its install will not coexist with the 4.x workspace) and simply try using it.
We are most interested with feedback, in particular:
- Testing packaging - Testing upgrades of packages - Helping with building openQA tests - Checking for missing functionality
Feedback will tracked through the following connect.opensuse.org polls:
- Overall experience [1] : What does fowrk for you? What doesn't? - Missing functionality [2]: What are you missing from the 4.x workspace that you deem irrepleaceable? - Upgrade experience [3]: Was the upgrade from the 4.x packages smooth? Did anything break? - Visual and hardware-related issues [4]: Is Plasma 5 running well with your hardware?
Bugs in the software should be reported upstream, but any issue in the packaging should be reported to openSUSE's Bugzilla.
Phase 2: OpenQA testing
We will discuss with the rest of the openSUSE community on how to handle Plasma 5 on openQA. This is where we need your help the most, because openQA needles are an important part of the openSUSE testing and we need many to ensure a smooth experience (and transition from 4.x), and we need a lot of them to ensure there are no hiccups down the road. Refer to http://os-autoinst.github.io/openQA/ to see how you can contribute.
This phase will go as long as we can get comparable results as the 4.x workspace on openQA.
=== What about applications ? ===
As with regards to application releases from KDE (KDE Applications xx.yyy), our plan is to use directly what KDE releases, meaning that we will switch to KF5-based applications once upstream makes stable releases of them. If there are no KF5-based releases of a particular application, the currently available 4.x version will be used.
=== New repository layout ===
As part of the migration plan, when Plasma 5 becomes the default desktop in openSUSE the following changes will take place:
- KDE:Frameworks5 (already the devel project for Plasma 5 and the KF5 libraries) will take the place of KDE:Distro:Factory (slowly phased out) - Application releases will be hosted in a separate development project, KDE:Applications
KDE:Current, offering 4.x based releases, will be kept for users of past openSUSE versions.
=== Contingency plan ===
In case the issues reported during the testing period are too severe, we will revert back to the 4.x workspace and await further improvements from upstream.
=== How can I help ? ===
First and foremost: testing! We've been running the KF5 based desktop for a while but the team is small, we need more eyes looking for potential issues. Secondly: openQA tests are an essential foundation of an always-stable Tumbleweed, therefore this is another eare where help is warranted. A third area is documentation: wiki pages, guides, anything that can help in the transition. The team can help providing the required information.
Above all: always be constructive when reporting issues. Saying "It sucks, get back to 4.x" is not only not going to help, but it is severely demotivating and that can be a problem with a task of this size. We're all humans, don't forget that. ;)
=== Poll links ===
[1] https://connect.opensuse.org/pg/polls/read/luca_b/47114/what-is-your-experie... [2] https://connect.opensuse.org/pg/polls/read/luca_b/47132/what-functionality-d... [3] https://connect.opensuse.org/pg/polls/read/luca_b/47168/how-was-your-upgrade... [4] https://connect.opensuse.org/pg/polls/read/luca_b/47184/how-is-your-plasma-5...
Luca Beltrame on behalf of the openSUSE community KDE Team
Luca Beltrame composed on 2015-03-10 23:45 (UTC+0100):
- Checking for missing functionality
cannot set my short date to YYYY-MM-DD, nor my time to HH:MM https://bugs.kde.org/show_bug.cgi?id=340982 (filed November)
Current Fedora discussion: https://lists.fedoraproject.org/pipermail/kde/2015-March/014284.html
Other discussion: http://vizzzion.org/blog/2014/05/locale-changes-in-plasma-next/comment-page-...
* Luca Beltrame lbeltrame@kde.org [03-10-15 18:46]:
Hello openSUSE KDE users and contributors,
This mail outlines our plans for moving towards Plasma 5 as a default desktop for the next openSUSE release, includinga tentative action plan and where help from you all is required. We do not believe on pushing changes on users without some sort of preparation, therefore this document describes the transition plan.
See the previous mails for a rationale of this decision.
==== The plan ====
Phase 1: Gather input from the community
In this phase, we would like people from the community, if they are able to, to test the currently-available code. It's quite easy, as all the required software is already available directly in Tumbleweed. You should install Plasma 5 from there (bear in mind that its install will not coexist with the 4.x workspace) and simply try using it.
Is it possible to return to the 4.x workspace? How can kde4 apps work w/o the 4.x workspace?
The following 8 packages are going to be REMOVED: kdebase4-openSUSE 13.2-6.63 kdebase4-session 4.12-5.1 kdebase4-workspace 4.11.16-1.1 kdebase4-workspace-branding-openSUSE 13.2-6.63 patterns-openSUSE-kde 20150105-3.1 patterns-openSUSE-kde4_basis 20150105-3.1 patterns-openSUSE-kde4_imaging 20150105-3.1 plasmoid-cwp 1.12.0-16.2
Interested Tw user.
* Patrick Shanahan paka@opensuse.org [03-10-15 19:34]:
- Luca Beltrame lbeltrame@kde.org [03-10-15 18:46]:
Hello openSUSE KDE users and contributors,
This mail outlines our plans for moving towards Plasma 5 as a default desktop for the next openSUSE release, includinga tentative action plan and where help from you all is required. We do not believe on pushing changes on users without some sort of preparation, therefore this document describes the transition plan.
See the previous mails for a rationale of this decision.
==== The plan ====
Phase 1: Gather input from the community
In this phase, we would like people from the community, if they are able to, to test the currently-available code. It's quite easy, as all the required software is already available directly in Tumbleweed. You should install Plasma 5 from there (bear in mind that its install will not coexist with the 4.x workspace) and simply try using it.
Is it possible to return to the 4.x workspace? How can kde4 apps work w/o the 4.x workspace?
The following 8 packages are going to be REMOVED: kdebase4-openSUSE 13.2-6.63 kdebase4-session 4.12-5.1 kdebase4-workspace 4.11.16-1.1 kdebase4-workspace-branding-openSUSE 13.2-6.63 patterns-openSUSE-kde 20150105-3.1 patterns-openSUSE-kde4_basis 20150105-3.1 patterns-openSUSE-kde4_imaging 20150105-3.1 plasmoid-cwp 1.12.0-16.2
Interested Tw user.
zypper -v in --recommends plasma5-workspace
That screwed it up, no systemtray, no desktop. And <rt><clicking> on the wallpaper does nothing.
Removed plasma5 pkgs and returned, had to reconstruct desktop(s).
Patrick Shanahan composed on 2015-03-10 20:36 (UTC-0400):
zypper -v in --recommends plasma5-workspace
That screwed it up, no systemtray, no desktop. And <rt><clicking> on the wallpaper does nothing.
Removed plasma5 pkgs and returned, had to reconstruct desktop(s).
I have roughly 20 Fedora 22 and Rawhide installations, roughly half as many as I have 13.2 and TW. AFAIK, KF5 is the only available K* choice in them. I have yet to see a K* desktop in any F22/23. Most produce a popup announcing a plasma crash, and no more. The rest don't even get that far.
All my openSUSE installations I keep on KDE3, TDE and/or KDE4. Given the KDE3 features never migrated to KDE4, Fitt's Law "features" in KDE4[1], people openly chastising attempted/would-be contributors to K*[2], and K* feature plans that get stalled for months or years, it's hard to get motivated WRT spending time with K5 before it does a lot more maturing.
[1] e.g. https://bugs.kde.org/show_bug.cgi?id=325286 about option to reverse implementation in last release before feature freeze for switch from 4 to 5 [2] http://lists.kde.org/?l=kde-promo&m=142528113312500&w=2
On Wednesday 11 of March 2015 01:36:26 Patrick Shanahan wrote:
- Patrick Shanahan paka@opensuse.org [03-10-15 19:34]:
- Luca Beltrame lbeltrame@kde.org [03-10-15 18:46]:
Hello openSUSE KDE users and contributors,
This mail outlines our plans for moving towards Plasma 5 as a default desktop for the next openSUSE release, includinga tentative action plan and where help from you all is required. We do not believe on pushing changes on users without some sort of preparation, therefore this document describes the transition plan.
See the previous mails for a rationale of this decision.
==== The plan ====
Phase 1: Gather input from the community
In this phase, we would like people from the community, if they are able to, to test the currently-available code. It's quite easy, as all the required software is already available directly in Tumbleweed. You should install Plasma 5 from there (bear in mind that its install will not coexist with the 4.x workspace) and simply try using it.
Is it possible to return to the 4.x workspace? How can kde4 apps work w/o the 4.x workspace?
The following 8 packages are going to be REMOVED: kdebase4-openSUSE 13.2-6.63 kdebase4-session 4.12-5.1 kdebase4-workspace 4.11.16-1.1 kdebase4-workspace-branding-openSUSE 13.2-6.63 patterns-openSUSE-kde 20150105-3.1 patterns-openSUSE-kde4_basis 20150105-3.1 patterns-openSUSE-kde4_imaging 20150105-3.1 plasmoid-cwp 1.12.0-16.2
Interested Tw user.
zypper -v in --recommends plasma5-workspace
That screwed it up, no systemtray, no desktop. And <rt><clicking> on the wallpaper does nothing.
Yeah, you're missing plasma5-session package https://en.opensuse.org/SDB:KDE_Plasma_5#Installing_Plasma_5_on_openSUSE
Cheers, Hrvoje
Removed plasma5 pkgs and returned, had to reconstruct desktop(s).
* šumski hrvoje.senjan@gmail.com [03-10-15 22:05]:
On Wednesday 11 of March 2015 01:36:26 Patrick Shanahan wrote:
- Patrick Shanahan paka@opensuse.org [03-10-15 19:34]:
- Luca Beltrame lbeltrame@kde.org [03-10-15 18:46]:
Hello openSUSE KDE users and contributors,
This mail outlines our plans for moving towards Plasma 5 as a default desktop for the next openSUSE release, includinga tentative action plan and where help from you all is required. We do not believe on pushing changes on users without some sort of preparation, therefore this document describes the transition plan.
See the previous mails for a rationale of this decision.
==== The plan ====
Phase 1: Gather input from the community
In this phase, we would like people from the community, if they are able to, to test the currently-available code. It's quite easy, as all the required software is already available directly in Tumbleweed. You should install Plasma 5 from there (bear in mind that its install will not coexist with the 4.x workspace) and simply try using it.
Is it possible to return to the 4.x workspace? How can kde4 apps work w/o the 4.x workspace?
The following 8 packages are going to be REMOVED: kdebase4-openSUSE 13.2-6.63 kdebase4-session 4.12-5.1 kdebase4-workspace 4.11.16-1.1 kdebase4-workspace-branding-openSUSE 13.2-6.63 patterns-openSUSE-kde 20150105-3.1 patterns-openSUSE-kde4_basis 20150105-3.1 patterns-openSUSE-kde4_imaging 20150105-3.1 plasmoid-cwp 1.12.0-16.2
Interested Tw user.
zypper -v in --recommends plasma5-workspace
That screwed it up, no systemtray, no desktop. And <rt><clicking> on the wallpaper does nothing.
Yeah, you're missing plasma5-session package https://en.opensuse.org/SDB:KDE_Plasma_5#Installing_Plasma_5_on_openSUSE
tks, I'll try again tomorrow or next, have to go out of town for business.
* Patrick Shanahan paka@opensuse.org [03-10-15 23:10]: [...]
zypper -v in --recommends plasma5-workspace
That screwed it up, no systemtray, no desktop. And <rt><clicking> on the wallpaper does nothing.
Yeah, you're missing plasma5-session package https://en.opensuse.org/SDB:KDE_Plasma_5#Installing_Plasma_5_on_openSUSE
tks, I'll try again tomorrow or next, have to go out of town for business.
ok, zypper -v in --recommends plasma5-session plasma5-workspace
Still comes up w/o a system tray or taskmanager ;^(
Was able to add system-tray widget to desktop but no taskmanager... Did not reboot, only restarted X server
On Thursday 12 of March 2015 16:18:34 Patrick Shanahan wrote:
- Patrick Shanahan paka@opensuse.org [03-10-15 23:10]:
[...]
zypper -v in --recommends plasma5-workspace
That screwed it up, no systemtray, no desktop. And <rt><clicking> on the wallpaper does nothing.
Yeah, you're missing plasma5-session package https://en.opensuse.org/SDB:KDE_Plasma_5#Installing_Plasma_5_on_openSUS E
tks, I'll try again tomorrow or next, have to go out of town for business.
ok, zypper -v in --recommends plasma5-session plasma5-workspace
Still comes up w/o a system tray or taskmanager ;^(
Was able to add system-tray widget to desktop but no taskmanager... Did not reboot, only restarted X server
Can you try to logout, remove ~/.config/plasma*rc, and login back into plasma?
If that doesn't fix it, please report a bug @ novell bugzilla, together with the ~/.xsession-errors file so we can see what goes wrong. TIA!
Cheers, Hrvoje
* šumski hrvoje.senjan@gmail.com [03-12-15 11:31]:
On Thursday 12 of March 2015 16:18:34 Patrick Shanahan wrote:
- Patrick Shanahan paka@opensuse.org [03-10-15 23:10]:
[...]
zypper -v in --recommends plasma5-workspace
That screwed it up, no systemtray, no desktop. And <rt><clicking> on the wallpaper does nothing.
Yeah, you're missing plasma5-session package https://en.opensuse.org/SDB:KDE_Plasma_5#Installing_Plasma_5_on_openSUS E
tks, I'll try again tomorrow or next, have to go out of town for business.
ok, zypper -v in --recommends plasma5-session plasma5-workspace
Still comes up w/o a system tray or taskmanager ;^(
Was able to add system-tray widget to desktop but no taskmanager... Did not reboot, only restarted X server
Can you try to logout, remove ~/.config/plasma*rc, and login back into plasma?
If that doesn't fix it, please report a bug @ novell bugzilla, together with the ~/.xsession-errors file so we can see what goes wrong. TIA!
That appears to have worked, have taskmanager and it contains system-tray and other expected items. Will play some and advise noticed problems.
tks,
I'm having trouble playing .flac files with amarok on plasma5. I did a clean install and added the KDE5 base repo through YaST, then changed the default WM and display manager. The FLAC library is installed, but I suppose I'm missing some gstreamer library.
On Thu, Mar 12, 2015 at 8:36 AM, Patrick Shanahan paka@opensuse.org wrote:
- šumski hrvoje.senjan@gmail.com [03-12-15 11:31]:
On Thursday 12 of March 2015 16:18:34 Patrick Shanahan wrote:
- Patrick Shanahan paka@opensuse.org [03-10-15 23:10]:
[...]
zypper -v in --recommends plasma5-workspace
That screwed it up, no systemtray, no desktop. And <rt><clicking> on the wallpaper does nothing.
Yeah, you're missing plasma5-session package https://en.opensuse.org/SDB:KDE_Plasma_5#Installing_Plasma_5_on_openSUS E
tks, I'll try again tomorrow or next, have to go out of town for business.
ok, zypper -v in --recommends plasma5-session plasma5-workspace
Still comes up w/o a system tray or taskmanager ;^(
Was able to add system-tray widget to desktop but no taskmanager... Did not reboot, only restarted X server
Can you try to logout, remove ~/.config/plasma*rc, and login back into plasma?
If that doesn't fix it, please report a bug @ novell bugzilla, together with the ~/.xsession-errors file so we can see what goes wrong. TIA!
That appears to have worked, have taskmanager and it contains system-tray and other expected items. Will play some and advise noticed problems.
tks,
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
In data giovedì 12 marzo 2015 09:13:33, Sam M. ha scritto:
I'm having trouble playing .flac files with amarok on plasma5. I did a clean install and added the KDE5 base repo through YaST, then changed
Do you have phonon4qt5 and relative backend installed?
Focus does not appear to follow mouse as it did in kde4. I have same setting on both boxes and action is different, seemingly random on not at all following.
Please file bugs upstream (on bugs.kde.org) once you make sure you can reliably reproduce them (can you check with a different user account?).
Keyboard shortcuts appear to be lost.
I can't reproduce. Is kglobalacceld5 running?
* Luca Beltrame lbeltrame@kde.org [03-12-15 15:46]:
In data giovedì 12 marzo 2015 09:13:33, Sam M. ha scritto:
I'm having trouble playing .flac files with amarok on plasma5. I did a clean install and added the KDE5 base repo through YaST, then changed
Do you have phonon4qt5 and relative backend installed?
Focus does not appear to follow mouse as it did in kde4. I have same setting on both boxes and action is different, seemingly random on not at all following.
Please file bugs upstream (on bugs.kde.org) once you make sure you can reliably reproduce them (can you check with a different user account?).
working on...
Keyboard shortcuts appear to be lost.
I can't reproduce. Is kglobalacceld5 running?
yes
* Patrick Shanahan paka@opensuse.org [03-12-15 15:51]:
- Luca Beltrame lbeltrame@kde.org [03-12-15 15:46]:
In data giovedì 12 marzo 2015 09:13:33, Sam M. ha scritto:
I'm having trouble playing .flac files with amarok on plasma5. I did a clean install and added the KDE5 base repo through YaST, then changed
Do you have phonon4qt5 and relative backend installed?
Focus does not appear to follow mouse as it did in kde4. I have same setting on both boxes and action is different, seemingly random on not at all following.
Please file bugs upstream (on bugs.kde.org) once you make sure you can reliably reproduce them (can you check with a different user account?).
working on...
appears to work on a new user, must be in ~/.kde4 But, since most will be migrating/upgrading, this should not happen!
https://bugs.kde.org/show_bug.cgi?id=345097
Keyboard shortcuts appear to be lost.
I can't reproduce. Is kglobalacceld5 running?
yes
explanation, I use xset to blank screen and have a keyboard shortcut to immediately blank screen. The shortcut does not work in regular user and issuing from cl works, but after some period which I did not set, the screen locks. I do no want the screen lock.
I got my desktop set up in folder view and had my icons all arranged the way I wanted them, (after a clean install) then ran zypper up, and a bunch new KDE packages were downloaded. My desktop background on my main monitor switched to the resolution of my other monitor, and switched itself to Desktop view. I had to switch it back, and when I logged out and back in the desktop background went back to normal. I have no resize arrows to resize a window. I did before zypper up, but now I just have a basic looking arrow. I am guessing I am missing another package, and those settings aren't in the KDE Settings GUI at the moment.
On Thu, Mar 12, 2015 at 1:25 PM, Patrick Shanahan paka@opensuse.org wrote:
- Patrick Shanahan paka@opensuse.org [03-12-15 15:51]:
- Luca Beltrame lbeltrame@kde.org [03-12-15 15:46]:
In data giovedì 12 marzo 2015 09:13:33, Sam M. ha scritto:
I'm having trouble playing .flac files with amarok on plasma5. I did a clean install and added the KDE5 base repo through YaST, then changed
Do you have phonon4qt5 and relative backend installed?
Focus does not appear to follow mouse as it did in kde4. I have same setting on both boxes and action is different, seemingly random on not at all following.
Please file bugs upstream (on bugs.kde.org) once you make sure you can reliably reproduce them (can you check with a different user account?).
working on...
appears to work on a new user, must be in ~/.kde4 But, since most will be migrating/upgrading, this should not happen!
https://bugs.kde.org/show_bug.cgi?id=345097
Keyboard shortcuts appear to be lost.
I can't reproduce. Is kglobalacceld5 running?
yes
explanation, I use xset to blank screen and have a keyboard shortcut to immediately blank screen. The shortcut does not work in regular user and issuing from cl works, but after some period which I did not set, the screen locks. I do no want the screen lock.
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Freitag, 13. März 2015, 22:32:50 schrieb Sam M.:
I got my desktop set up in folder view and had my icons all arranged the way I wanted them, (after a clean install) then ran zypper up, and a bunch new KDE packages were downloaded. My desktop background on my main monitor switched to the resolution of my other monitor, and switched itself to Desktop view. I had to switch it back, and when I logged out and back in the desktop background went back to normal. I have no resize arrows to resize a window. I did before zypper up, but now I just have a basic looking arrow. I am guessing I am missing another package, and those settings aren't in the KDE Settings GUI at the moment.
Hi Sam,
do you have the package kscreen5 installed? In my case was not installed by default and so I had a duplicate screen in 2 my Dualscreen setup.
Stefan
* Stefan Kunze skunze@novell.com [03-16-15 03:52]:
Am Freitag, 13. März 2015, 22:32:50 schrieb Sam M.:
I got my desktop set up in folder view and had my icons all arranged the way I wanted them, (after a clean install) then ran zypper up, and a bunch new KDE packages were downloaded. My desktop background on my main monitor switched to the resolution of my other monitor, and switched itself to Desktop view. I had to switch it back, and when I logged out and back in the desktop background went back to normal. I have no resize arrows to resize a window. I did before zypper up, but now I just have a basic looking arrow. I am guessing I am missing another package, and those settings aren't in the KDE Settings GUI at the moment.
Hi Sam,
do you have the package kscreen5 installed? In my case was not installed by default and so I had a duplicate screen in 2 my Dualscreen setup.
Not Sam, but: Problem: kscreen5-5.2.1-1.1.x86_64 conflicts with kscreen provided by kscreen-1.0.71-3.3.x86_64 Solution 1: Following actions will be done: deinstallation of kscreen-1.0.71-3.3.x86_64 deinstallation of kdebase4-workspace-4.11.17-1.1.x86_64 deinstallation of patterns-openSUSE-kde4_basis-20150105-3.1.x86_64 deinstallation of kdebase4-workspace-branding-openSUSE-13.2-6.63.x86_64 deinstallation of patterns-openSUSE-kde4_imaging-20150105-3.1.x86_64 deinstallation of patterns-openSUSE-kde-20150105-3.1.x86_64 Solution 2: do not install kscreen5-5.2.1-1.1.x86_64
In data lunedì 16 marzo 2015 07:24:42, Patrick Shanahan ha scritto:
Not Sam, but: Problem: kscreen5-5.2.1-1.1.x86_64 conflicts with kscreen
As it's part of Plasma 5 the conflict is intentional: you will need to uninstall kscreen (which only works in Plasma 4.x) in order to use kscreen5 (which only works in Plasma 5).
On Mon, 16 Mar 2015 12:32, Luca Beltrame <lbeltrame@...> wrote:
In data lunedì 16 marzo 2015 07:24:42, Patrick Shanahan ha scritto:
Not Sam, but: Problem: kscreen5-5.2.1-1.1.x86_64 conflicts with kscreen
As it's part of Plasma 5 the conflict is intentional: you will need to uninstall kscreen (which only works in Plasma 4.x) in order to use kscreen5 (which only works in Plasma 5).
To speak clearly:
Frist deinstall kscreen-1* from kde4 while ignoring dependencies, else you will deinstall to much.
The "Require:" lines in kscreen-1* and other kde4 packages have not been corrected yet to honour this situation.
Then install the kscreen5-5.2.1-1.1.x86_64 package.
- Yamaban.
In data lunedì 16 marzo 2015 12:38:25, Yamaban ha scritto:
The "Require:" lines in kscreen-1* and other kde4 packages have not been corrected yet to honour this situation.
Please file a bug on bugzilla.opensuse.org so that this doesn't get forgotten.
* Yamaban foerster@lisas.de [03-16-15 07:39]:
On Mon, 16 Mar 2015 12:32, Luca Beltrame <lbeltrame@...> wrote:
In data lunedì 16 marzo 2015 07:24:42, Patrick Shanahan ha scritto:
Not Sam, but: Problem: kscreen5-5.2.1-1.1.x86_64 conflicts with kscreen
As it's part of Plasma 5 the conflict is intentional: you will need to uninstall kscreen (which only works in Plasma 4.x) in order to use kscreen5 (which only works in Plasma 5).
To speak clearly:
Frist deinstall kscreen-1* from kde4 while ignoring dependencies, else you will deinstall to much.
The "Require:" lines in kscreen-1* and other kde4 packages have not been corrected yet to honour this situation.
Then install the kscreen5-5.2.1-1.1.x86_64 package.
That appears to have worked. I had to use "rpm -e --nodeps <package>" as I could find no manner to perform a "nodeps" package removal with zypper. Have I missed something?
On Mon, 16 Mar 2015 12:54, Patrick Shanahan <paka@...> wrote:
- Yamaban foerster@lisas.de [03-16-15 07:39]:
On Mon, 16 Mar 2015 12:32, Luca Beltrame <lbeltrame@...> wrote:
In data lunedì 16 marzo 2015 07:24:42, Patrick Shanahan ha scritto:
Not Sam, but: Problem: kscreen5-5.2.1-1.1.x86_64 conflicts with kscreen
As it's part of Plasma 5 the conflict is intentional: you will need to uninstall kscreen (which only works in Plasma 4.x) in order to use kscreen5 (which only works in Plasma 5).
To speak clearly:
Frist deinstall kscreen-1* from kde4 while ignoring dependencies, else you will deinstall to much.
The "Require:" lines in kscreen-1* and other kde4 packages have not been corrected yet to honour this situation.
Then install the kscreen5-5.2.1-1.1.x86_64 package.
That appears to have worked. I had to use "rpm -e --nodeps <package>" as I could find no manner to perform a "nodeps" package removal with zypper. Have I missed something?
Yes, than is a 'missing' feature. Thankful we are for direct rpm usage.
- Yamaban.
PS: Is there any way to make 'activies' an option and not a requirement?
do you have the package kscreen5 installed? In my case was not installed by default and so I had a duplicate screen in 2 my Dualscreen setup.
Stefan
kscreen5 is installed, as I am running Plasma 5 by itself on a workstation with no other KDE version on it. There were some missing packages that I installed, as I only installed the KDE Plasma 5 base packages as well as multiple KDE updates over the last couple weeks, so the problem disappeared for me.
* Patrick Shanahan paka@opensuse.org [03-12-15 11:36]:
- šumski hrvoje.senjan@gmail.com [03-12-15 11:31]:
[...]
Can you try to logout, remove ~/.config/plasma*rc, and login back into plasma?
If that doesn't fix it, please report a bug @ novell bugzilla, together with the ~/.xsession-errors file so we can see what goes wrong. TIA!
That appears to have worked, have taskmanager and it contains system-tray and other expected items. Will play some and advise noticed problems.
Focus does not appear to follow mouse as it did in kde4. I have same setting on both boxes and action is different, seemingly random on not at all following.
* Patrick Shanahan paka@opensuse.org [03-12-15 12:23]:
- Patrick Shanahan paka@opensuse.org [03-12-15 11:36]:
- šumski hrvoje.senjan@gmail.com [03-12-15 11:31]:
[...]
Can you try to logout, remove ~/.config/plasma*rc, and login back into plasma?
If that doesn't fix it, please report a bug @ novell bugzilla, together with the ~/.xsession-errors file so we can see what goes wrong. TIA!
That appears to have worked, have taskmanager and it contains system-tray and other expected items. Will play some and advise noticed problems.
Focus does not appear to follow mouse as it did in kde4. I have same setting on both boxes and action is different, seemingly random on not at all following.
Cannot disable requirement for password when screen blanker becomes active.
On Thursday 12 of March 2015 19:19:33 Patrick Shanahan wrote:
- Patrick Shanahan paka@opensuse.org [03-12-15 12:23]:
- Patrick Shanahan paka@opensuse.org [03-12-15 11:36]:
- šumski hrvoje.senjan@gmail.com [03-12-15 11:31]:
[...]
Can you try to logout, remove ~/.config/plasma*rc, and login back into plasma?
If that doesn't fix it, please report a bug @ novell bugzilla, together with the ~/.xsession-errors file so we can see what goes wrong. TIA!
That appears to have worked, have taskmanager and it contains system-tray and other expected items. Will play some and advise noticed problems.
Focus does not appear to follow mouse as it did in kde4. I have same setting on both boxes and action is different, seemingly random on not at all following.
Cannot disable requirement for password when screen blanker becomes active.
System settings -> Desktop Behavior -> Screen Locking -> Lock screen after -> enter 0 (zero). This has improved usability for 5.3, where there is an explicit checkbox whether lock screen shall be enabled or not.
Cheers, Hrvoje
* šumski hrvoje.senjan@gmail.com [03-12-15 16:35]:
On Thursday 12 of March 2015 19:19:33 Patrick Shanahan wrote:
- Patrick Shanahan paka@opensuse.org [03-12-15 12:23]:
- Patrick Shanahan paka@opensuse.org [03-12-15 11:36]:
- šumski hrvoje.senjan@gmail.com [03-12-15 11:31]:
[...]
Can you try to logout, remove ~/.config/plasma*rc, and login back into plasma?
If that doesn't fix it, please report a bug @ novell bugzilla, together with the ~/.xsession-errors file so we can see what goes wrong. TIA!
That appears to have worked, have taskmanager and it contains system-tray and other expected items. Will play some and advise noticed problems.
Focus does not appear to follow mouse as it did in kde4. I have same setting on both boxes and action is different, seemingly random on not at all following.
Cannot disable requirement for password when screen blanker becomes active.
System settings -> Desktop Behavior -> Screen Locking -> Lock screen after -> enter 0 (zero). This has improved usability for 5.3, where there is an explicit checkbox whether lock screen shall be enabled or not.
Will try.
Box keeps loosing network, wicked, where it didn't before plasma5??
tks,
should this conversation be moved to factory?
* Patrick Shanahan paka@opensuse.org [03-12-15 16:37]:
- šumski hrvoje.senjan@gmail.com [03-12-15 16:35]:
On Thursday 12 of March 2015 19:19:33 Patrick Shanahan wrote:
- Patrick Shanahan paka@opensuse.org [03-12-15 12:23]:
- Patrick Shanahan paka@opensuse.org [03-12-15 11:36]:
- šumski hrvoje.senjan@gmail.com [03-12-15 11:31]:
[...]
Can you try to logout, remove ~/.config/plasma*rc, and login back into plasma?
If that doesn't fix it, please report a bug @ novell bugzilla, together with the ~/.xsession-errors file so we can see what goes wrong. TIA!
That appears to have worked, have taskmanager and it contains system-tray and other expected items. Will play some and advise noticed problems.
Focus does not appear to follow mouse as it did in kde4. I have same setting on both boxes and action is different, seemingly random on not at all following.
Cannot disable requirement for password when screen blanker becomes active.
System settings -> Desktop Behavior -> Screen Locking -> Lock screen after -> enter 0 (zero). This has improved usability for 5.3, where there is an explicit checkbox whether lock screen shall be enabled or not.
Will try.
There is no Desktop Behavior, it is in Monitor Settings
systemsettings will not take a "0", nothing smaller than 1 second.
Yes, I have systemsettings5 installed.
On Thursday 12 of March 2015 21:53:30 Patrick Shanahan wrote:
- Patrick Shanahan paka@opensuse.org [03-12-15 16:37]:
- šumski hrvoje.senjan@gmail.com [03-12-15 16:35]:
On Thursday 12 of March 2015 19:19:33 Patrick Shanahan wrote:
- Patrick Shanahan paka@opensuse.org [03-12-15 12:23]:
- Patrick Shanahan paka@opensuse.org [03-12-15 11:36]:
- šumski hrvoje.senjan@gmail.com [03-12-15 11:31]:
[...]
> Can you try to logout, remove ~/.config/plasma*rc, and login > back into plasma? > > If that doesn't fix it, please report a bug @ novell bugzilla, > together with the ~/.xsession-errors file so we can see what > goes wrong. TIA!
That appears to have worked, have taskmanager and it contains system-tray and other expected items. Will play some and advise noticed problems.
Focus does not appear to follow mouse as it did in kde4. I have same setting on both boxes and action is different, seemingly random on not at all following.
Cannot disable requirement for password when screen blanker becomes active.
System settings -> Desktop Behavior -> Screen Locking -> Lock screen after -> enter 0 (zero). This has improved usability for 5.3, where there is an explicit checkbox whether lock screen shall be enabled or not.
Will try.
There is no Desktop Behavior, it is in Monitor Settings
It's within Desktop Behavior section since 5.2.0... Are you using something older?
In any case, having [Daemon] Autolock=false Timeout=0
in ~/.config/kscreenlockerrc shall do the trick...
Cheers, Hrvoje
* šumski hrvoje.senjan@gmail.com [03-12-15 21:42]:
On Thursday 12 of March 2015 21:53:30 Patrick Shanahan wrote:
[...]
There is no Desktop Behavior, it is in Monitor Settings
It's within Desktop Behavior section since 5.2.0... Are you using something older?
In any case, having [Daemon] Autolock=false Timeout=0
in ~/.config/kscreenlockerrc shall do the trick...
There was no ~/.config/kscreenlockerrc, but I created on with the quoted entries.
This is three hours later: started systemsettings again and now have "Desktop Behavior" as you described. Started from kmenu. Waiting for screen to blank to test lock.
Also noticed that starting systemsetting from cl gives old display and systemsetting5 from cl gives what you described.
Success, no lock on return from screen blanker.
But where do you configure the screen saver?
In data giovedì 12 marzo 2015 22:23:43, Patrick Shanahan ha scritto:
But where do you configure the screen saver?
Support for other lock screens (save for no locking / blanking), that is screensavers, has been removed due to security concerns with regards to X11. This of course doesn't affect screen saving with powermanagement-related features like turning off the screen, etc.
Rationale explained (with plenty details) by the developer:
http://blog.martin-graesslin.com/blog/2014/05/screenlocker-architecture-in-p...
* Luca Beltrame lbeltrame@kde.org [03-13-15 02:34]:
In data giovedì 12 marzo 2015 22:23:43, Patrick Shanahan ha scritto:
But where do you configure the screen saver?
Support for other lock screens (save for no locking / blanking), that is screensavers, has been removed due to security concerns with regards to X11. This of course doesn't affect screen saving with powermanagement-related features like turning off the screen, etc.
Rationale explained (with plenty details) by the developer:
http://blog.martin-graesslin.com/blog/2014/05/screenlocker-architecture-in-p...
Tks, primarily a desktop user and powermanagement didn't ring the right bells. That works-for-me.
Notice the keyboard shortcuts aren't carried over. Example, I have a keyboard shortcut to immediately blank the screen: sleep 1;xset dpms force off which does nothing, but shows as assigned in "systemsettings"
Opened "systemsetting5" and assigned as a new global key and got complaint that was already assigned. After over-ridding/reassigning it now works. Plasma5 has a problem here, need bug report?
tks,
* Patrick Shanahan paka@opensuse.org [03-12-15 12:23]:
- Patrick Shanahan paka@opensuse.org [03-12-15 11:36]:
- šumski hrvoje.senjan@gmail.com [03-12-15 11:31]:
[...]
Can you try to logout, remove ~/.config/plasma*rc, and login back into plasma?
If that doesn't fix it, please report a bug @ novell bugzilla, together with the ~/.xsession-errors file so we can see what goes wrong. TIA!
That appears to have worked, have taskmanager and it contains system-tray and other expected items. Will play some and advise noticed problems.
Focus does not appear to follow mouse as it did in kde4. I have same setting on both boxes and action is different, seemingly random on not at all following.
Keyboard shortcuts appear to be lost.
On Tuesday 10 March 2015 23:45:48 Luca Beltrame wrote:
=== Contingency plan ===
In case the issues reported during the testing period are too severe, we will revert back to the 4.x workspace and await further improvements from upstream.
Just do https://old-en.opensuse.org/File:OS11.0-inst-6.jpg :-)
Plan sounds good, will completely trust the openSUSE team on this, because all the previous changes and migrations in the last 11 years were implemented very well.
But here is a question: when Plasma5 comes closer to be default, will you do the "migrational" KDE 4 repository for incompatible apps? We've been enjoying Wolfgang's Plasma5 "compatibility" packages under KDE4 for quite some time now, and doing the same for KDE 4 would be really helpful.
I don't know how many of apps like are out there, my main usecase is Kate, as I would like to use Kate5 (and I'm using it from Wolfgang's repos) but krusader is a showstopper app for me, and it specifically requires Kate 4. If that issue can be easily resolved somehow with OBS - I would appreciate any comments on this.
On Tuesday 10 March 2015 23:45:48 Luca Beltrame wrote:
Hello openSUSE KDE users and contributors,
This mail outlines our plans for moving towards Plasma 5 as a default desktop for the next openSUSE release, includinga tentative action plan and where help from you all is required. We do not believe on pushing changes on users without some sort of preparation, therefore this document describes the transition plan.
See the previous mails for a rationale of this decision.
==== The plan ====
Phase 1: Gather input from the community
In this phase, we would like people from the community, if they are able to, to test the currently-available code. It's quite easy, as all the required software is already available directly in Tumbleweed. You should install Plasma 5 from there (bear in mind that its install will not coexist with the 4.x workspace) and simply try using it.
We are most interested with feedback, in particular:
- Testing packaging
- Testing upgrades of packages
- Helping with building openQA tests
- Checking for missing functionality
Feedback will tracked through the following connect.opensuse.org polls:
- Overall experience [1] : What does fowrk for you? What doesn't?
- Missing functionality [2]: What are you missing from the 4.x workspace
that you deem irrepleaceable?
- Upgrade experience [3]: Was the upgrade from the 4.x packages smooth? Did
anything break?
- Visual and hardware-related issues [4]: Is Plasma 5 running well with your
hardware?
Bugs in the software should be reported upstream, but any issue in the packaging should be reported to openSUSE's Bugzilla.
Phase 2: OpenQA testing
We will discuss with the rest of the openSUSE community on how to handle Plasma 5 on openQA. This is where we need your help the most, because openQA needles are an important part of the openSUSE testing and we need many to ensure a smooth experience (and transition from 4.x), and we need a lot of them to ensure there are no hiccups down the road. Refer to http://os-autoinst.github.io/openQA/ to see how you can contribute.
This phase will go as long as we can get comparable results as the 4.x workspace on openQA.
=== What about applications ? ===
As with regards to application releases from KDE (KDE Applications xx.yyy), our plan is to use directly what KDE releases, meaning that we will switch to KF5-based applications once upstream makes stable releases of them. If there are no KF5-based releases of a particular application, the currently available 4.x version will be used.
=== New repository layout ===
As part of the migration plan, when Plasma 5 becomes the default desktop in openSUSE the following changes will take place:
- KDE:Frameworks5 (already the devel project for Plasma 5 and the KF5
libraries) will take the place of KDE:Distro:Factory (slowly phased out)
- Application releases will be hosted in a separate development project,
KDE:Applications
KDE:Current, offering 4.x based releases, will be kept for users of past openSUSE versions.
=== Contingency plan ===
In case the issues reported during the testing period are too severe, we will revert back to the 4.x workspace and await further improvements from upstream.
=== How can I help ? ===
First and foremost: testing! We've been running the KF5 based desktop for a while but the team is small, we need more eyes looking for potential issues. Secondly: openQA tests are an essential foundation of an always-stable Tumbleweed, therefore this is another eare where help is warranted. A third area is documentation: wiki pages, guides, anything that can help in the transition. The team can help providing the required information.
Above all: always be constructive when reporting issues. Saying "It sucks, get back to 4.x" is not only not going to help, but it is severely demotivating and that can be a problem with a task of this size. We're all humans, don't forget that. ;)
=== Poll links ===
[1] https://connect.opensuse.org/pg/polls/read/luca_b/47114/what-is-your-experi ence-with-plasma-5-in-opensuse [2] https://connect.opensuse.org/pg/polls/read/luca_b/47132/what-functionality-%...
do-you-miss-most-from-plasma-5 [3]
https://connect.opensuse.org/pg/polls/read/luca_b/47168/how-was-your-upgrad e-experience-from-plasma-workspace-4x-to-plasma-5 [4] https://connect.opensuse.org/pg/polls/read/luca_b/47184/how-is-your-plasma-%...
5-visual-experience
Luca Beltrame on behalf of the openSUSE community KDE Team
On Wednesday, March 25, 2015 02:20:18 PM Stanislav Baiduzhyi wrote:
Hi Stanislav
But here is a question: when Plasma5 comes closer to be default, will you do the "migrational" KDE 4 repository for incompatible apps? We've been enjoying Wolfgang's Plasma5 "compatibility" packages under KDE4 for quite some time now, and doing the same for KDE 4 would be really helpful.
Well, for a certain amount of time we would have KDE4 parts living together with Plasma5. As an example we will have for at least another year a KDEPIM suite that is based on KDE4, so we definitely will need to keep a number of KDE4 packages alive to support this. Also around half from the KDE Applications release is currently still KDE4 based.
I don't know how many of apps like are out there, my main usecase is Kate, as I would like to use Kate5 (and I'm using it from Wolfgang's repos) but krusader is a showstopper app for me, and it specifically requires Kate 4.
Well, here we get into the difficulty. The libraries were designed and ported to Frameworks with the idea/setup to be co-installable. The applications however where never designed for this. So Kate5 actually still installs the binary /usr/bin/kate, which also Kate4 does.
One could of course easily say, that you could have Kate4 install into a different prefix. Maybe, question would be if this also means that the libraries should be installed in this specific prefix. In order to set this up and validate if it works together with a standard desktop takes time. Time that we might have or not have. The team itself is very small and we rely on volunteers to do this specific setups for us. Wolfgang was so helpful to set up a specific repository which could be used for a complete co-installable Plasma5 experience. I am not sure if he would be willing to set up something similar for KDE4 applications. On the other hand, I have seen that porting work has started on Krusader, so maybe we have a Plasma5 based Krusader when we make the switch.
Regards
Raymond
On Wednesday 25 March 2015 14:51:21 Raymond Wooninck wrote:
Well, here we get into the difficulty. The libraries were designed and ported to Frameworks with the idea/setup to be co-installable. The applications however where never designed for this. So Kate5 actually still installs the binary /usr/bin/kate, which also Kate4 does.
One could of course easily say, that you could have Kate4 install into a different prefix. Maybe, question would be if this also means that the libraries should be installed in this specific prefix. In order to set this up and validate if it works together with a standard desktop takes time. Time that we might have or not have. The team itself is very small and we rely on volunteers to do this specific setups for us. Wolfgang was so helpful to set up a specific repository which could be used for a complete co-installable Plasma5 experience. I am not sure if he would be willing to set up something similar for KDE4 applications. On the other hand, I have seen that porting work has started on Krusader, so maybe we have a Plasma5 based Krusader when we make the switch.
Raymond,
Thanx for your response. Unfortunately, krusader has a rather big codebase and very few developers, and especially unfortunately for me that I have very different background and cannot help them with porting. But I'll experiment on OBS and if I'll have some luck having krusader under plasma5 - I'll report back, maybe it will help others as well.
On Wednesday 25 March 2015 15:53:43 Stanislav Baiduzhyi wrote:
Thanx for your response. Unfortunately, krusader has a rather big codebase and very few developers, and especially unfortunately for me that I have very different background and cannot help them with porting. But I'll experiment on OBS and if I'll have some luck having krusader under plasma5
- I'll report back, maybe it will help others as well.
Ok, that was really fast and simple. Krusader does not need kate, it needs libktexteditor. Looks like there will be one more plasma5 user after the weekend.
Is there a way in Plasma 5 to type the file or folder name of the file or folder you want to open when using folder view? I use this a lot in KDE 4 when I have lots of windows open and want to open something I have on the desktop that I know by memory. It's not working under Plasma 5.
On Wed, Mar 25, 2015 at 12:58 PM, Stanislav Baiduzhyi baiduzhyi.devel@gmail.com wrote:
On Wednesday 25 March 2015 15:53:43 Stanislav Baiduzhyi wrote:
Thanx for your response. Unfortunately, krusader has a rather big codebase and very few developers, and especially unfortunately for me that I have very different background and cannot help them with porting. But I'll experiment on OBS and if I'll have some luck having krusader under plasma5
- I'll report back, maybe it will help others as well.
Ok, that was really fast and simple. Krusader does not need kate, it needs libktexteditor. Looks like there will be one more plasma5 user after the weekend.
-- Regards, Stas
-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Thursday 26 of March 2015 00:15:04 Sam M. wrote:
Is there a way in Plasma 5 to type the file or folder name of the file or folder you want to open when using folder view? I use this a lot in KDE 4 when I have lots of windows open and want to open something I have on the desktop that I know by memory. It's not working under Plasma 5.
Do you mean 'Specify a folder' setting (in the attachment) ? This is working here.
Cheers, Hrvoje
On Wed, Mar 25, 2015 at 12:58 PM, Stanislav Baiduzhyi
baiduzhyi.devel@gmail.com wrote:
On Wednesday 25 March 2015 15:53:43 Stanislav Baiduzhyi wrote:
Thanx for your response. Unfortunately, krusader has a rather big codebase and very few developers, and especially unfortunately for me that I have very different background and cannot help them with porting. But I'll experiment on OBS and if I'll have some luck having krusader under plasma5 - I'll report back, maybe it will help others as well.
Ok, that was really fast and simple. Krusader does not need kate, it needs libktexteditor. Looks like there will be one more plasma5 user after the weekend.
-- Regards,
Stas-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
No, what I mean is you can click the mouse pointer on the desktop, while in folder view. If you want to open Thunderbird, for example, you could type "thund" and hit enter, and the program will open. I use this feature constantly and it's not working on Plasma 5.
Thanks Sam
On Wed, Mar 25, 2015 at 7:01 PM, šumski hrvoje.senjan@gmail.com wrote:
On Thursday 26 of March 2015 00:15:04 Sam M. wrote:
Is there a way in Plasma 5 to type the file or folder name of the file or folder you want to open when using folder view? I use this a lot in KDE 4 when I have lots of windows open and want to open something I have on the desktop that I know by memory. It's not working under Plasma 5.
Do you mean 'Specify a folder' setting (in the attachment) ? This is working here.
Cheers, Hrvoje
On Wed, Mar 25, 2015 at 12:58 PM, Stanislav Baiduzhyi
baiduzhyi.devel@gmail.com wrote:
On Wednesday 25 March 2015 15:53:43 Stanislav Baiduzhyi wrote:
Thanx for your response. Unfortunately, krusader has a rather big codebase and very few developers, and especially unfortunately for me that I have very different background and cannot help them with porting. But I'll experiment on OBS and if I'll have some luck having krusader under plasma5 - I'll report back, maybe it will help others as well.
Ok, that was really fast and simple. Krusader does not need kate, it needs libktexteditor. Looks like there will be one more plasma5 user after the weekend.
-- Regards,
Stas-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
In data mercoledì 25 marzo 2015 23:10:22, Sam M. ha scritto:
you could type "thund" and hit enter, and the program will open. I use this feature constantly and it's not working on Plasma 5.
I'll poke the maintainer of the folder view widget to see if this is intentional (unlikely) or an oversight, or just no time to implement it yet.
In data giovedì 26 marzo 2015 07:23:33, Luca Beltrame ha scritto:
I'll poke the maintainer of the folder view widget to see if this is intentional (unlikely) or an oversight, or just no time to implement it yet.
And here's the answer (for the record, the folder view uses QML):
<Sho_> einar77_work: Qt Quick has no support for it, so like all the things (any keyboard selection stuff including modifiers, rubber band selection, spatial arrow key movement ...) I gotta do it myself, and it's non-trivial because you have this whole timer thing where you can quickly type several letters matching an item name start, etc. ... doable, sure, but I didn't have time to do it properly so far. I don't like hacks so I won't do a quick one with a single letter or so
In short, it needs to be handled and it's non trivial, so it'll take some time.
Am Mittwoch, 25. März 2015, 15:53:43 schrieb Stanislav Baiduzhyi:
Thanx for your response. Unfortunately, krusader has a rather big codebase and very few developers, and especially unfortunately for me that I have very different background and cannot help them with porting. But I'll experiment on OBS and if I'll have some luck having krusader under plasma5
- I'll report back, maybe it will help others as well.
Well, it was ported quicker than you anticipated... ;)
I have a KF5 based krusader in my repo now: http://software.opensuse.org/package/krusader5
I only briefly tested it, but it seems to work fine so far.
Kind Regards, Wolfgang
Luca Beltrame writes:
We are most interested with feedback, in particular:
I've just updated my old box with TW by installing plasma5-session.
- Testing packaging
Lock screen can't be unlocked because kdecheckpass can't read the password database. That's a packaging bug according to upstream and has been known for almost a year.
- Checking for missing functionality
Where to start? There is apparently absolutely no migration of settings from KDE4. I'm not sure if it uses its own settings since I didn't try to go back to 4.12 yet.
- Overall experience [1] : What does fowrk for you? What doesn't?
Background can only be set to bitmap or solid color. Color gradients are not available anymore. Desktop Clock misses font settings and date formats. Tons of application icons are simply black squares in the application launcher (they render Ok in other applications, so it's probably down to some compositing bug).
- Missing functionality [2]: What are you missing from the 4.x workspace that
you deem irrepleaceable?
No CPU/Temp/Network monitor, really? No visual feedback on when/where I can resize windows (might be a theme issue, but I'd consider it a bug).
- Upgrade experience [3]: Was the upgrade from the 4.x packages smooth? Did
anything break?
- Visual and hardware-related issues [4]: Is Plasma 5 running well with your
hardware?
It's running, I can't really say how well (Athlon64 3200+ / RV350 AGP). It always seems to fall back to XRender backend no matter what else I set (it seems to accept the new setting but when you reopen the window it's back to XRender).
After switching the mouse pointer to something more easily seen, I still have the old pointer on the desktop, the new pointer in KDE applications and yet another pointer in Gtk applications.
Regards, Achim.
In data venerdì 3 aprile 2015 15:09:01, Achim Gratz ha scritto:
Hello,
Lock screen can't be unlocked because kdecheckpass can't read the password database. That's a packaging bug according to upstream and has been known for almost a year.
This is caused by PAM, not by KDE packaging, FTR: pam_unix2 is used instead of pam_unix, and the former doesn't allow kcheckpass to access passwd.
Check if you have rpmnew files in /etc/pam.d/.
Where to start? There is apparently absolutely no migration of settings
Applications need to opt-in for this (there is a specific functionality that can be used). Plasma won't be able to migrate settings as it changed too much on that regard.
Please file bugs upstream where apps do not migrate their settings from 4.x.
from KDE4. I'm not sure if it uses its own settings since I didn't try to go back to 4.12 yet.
No, they don't. KF5 based apps finally use the XDG specification (~/.config, ~/.local, ~/.cache) rather than .kde[4].
No CPU/Temp/Network monitor, really? No visual feedback on when/where I can resize windows (might be a theme issue, but I'd consider it a bug).
CPU/Temp/Network monitors are back in Plasma 5.3, *really*.
It always seems to fall back to XRender backend no matter what else I set (it seems to accept the new setting but when you reopen the window it's back to XRender).
Compositing needs OpenGL 2 at least. If your driver does not provide that, it will automatically fall back to XRender.
07.04.2015 Luca Beltrame:
Lock screen can't be unlocked because kdecheckpass can't read the password database. That's a packaging bug according to upstream and has been known for almost a year.
This is caused by PAM, not by KDE packaging, FTR: pam_unix2 is used instead of pam_unix, and the former doesn't allow kcheckpass to access passwd.
I don't really care who's packaging fault it is. At the very least I should be getting a message when installing plasma5-session that it's incompatible with pam-unix2.
Check if you have rpmnew files in /etc/pam.d/.
I have never changed anything for PAM, so I shouldn't have any. Will check later to be sure.
Where to start? There is apparently absolutely no migration of settings
Applications need to opt-in for this (there is a specific functionality that can be used). Plasma won't be able to migrate settings as it changed too much on that regard.
I'm not talking about applications. I'm talking about the desptop itself.
Please file bugs upstream where apps do not migrate their settings from 4.x.
from KDE4. I'm not sure if it uses its own settings since I didn't try to go back to 4.12 yet.
I've moved the machine back to KDE4 and it hosed all my desktop settings. I had to log in to a failsafe session to even get to a desktop at all and have to start from scratch. If you want people to experiment more with Plasma5 you should first make sure such catastrophes don't happen.
No, they don't. KF5 based apps finally use the XDG specification (~/.config, ~/.local, ~/.cache) rather than .kde[4].
No CPU/Temp/Network monitor, really? No visual feedback on when/where I can resize windows (might be a theme issue, but I'd consider it a bug).
CPU/Temp/Network monitors are back in Plasma 5.3, *really*.
I believe it when I see it.
It always seems to fall back to XRender backend no matter what else I set (it seems to accept the new setting but when you reopen the window it's back to XRender).
Compositing needs OpenGL 2 at least. If your driver does not provide that, it will automatically fall back to XRender.
That's available and working, even though most of it is software. I think the memory on the graphics card might be too small, but in any case things look to succeed when clearly they don't. In KDE4 the dialog would either not let me chose OpenGL to start with or fall back to XRender immediately after activating the setting.
In data martedì 7 aprile 2015 17:41:58, Achim Gratz ha scritto:
Hello,
I won't be bothering with much of your mail because even if the criticism is valid, it has a rather confrontational tone, in particular the part below.
I believe it when I see it.
Did you read all the mails we made before, or did you just skim them? The team is currently *using* the git master version that will become Plasma 5.3.
Given that you do not trust the people that are actually doing the work (and are also upstreams like myself), not a single bit, here's a (localized) screenshot proving it:
would either not let me chose OpenGL to start with or fall back to XRender immediately after activating the setting.
If you think it's an error, please file a bug upstream (against "kwin").
-
Achim Gratz -
Achim Gratz
-
Felix Miata -
Luca Beltrame -
Markus Slopianka -
Patrick Shanahan -
Raymond Wooninck -
Sam M. -
Stanislav Baiduzhyi -
Stefan Kunze -
Wolfgang Bauer -
Yamaban -
šumski