On Wed, Mar 13, 2024 at 4:54 PM Patrick Shanahan wrote:

* Joe Salmeri [03-13-24 18:39]:

...

On 3/13/24 15:41, Fabian Vogt wrote:

...

Hi,

the next TW snapshot 20240311 contains KDE Plasma 6.0.1, Gear 24.02.0 and Frameworks 6.0.0: https://kde.org/announcements/megarelease/6/

Plasma 5 will be replaced, it is no longer part of the repository.

...

...

The Wayland session isn't default yet, that will have to be switched in a separate step later. This also makes it possible to differentiate whether bugs are more likely caused by Plasma 6 itself or the Wayland session.

Have a lot of fun, the openSUSE KDE packaging team

Excellent news, thanks for your hard work on this and for the links regarding the known issues.

When you later switch Wayland to the default, we'll still be able to login with X11 and X11 won't be removed right ?

Is there even talk about a timeframe where X11 would be removed or can we safely assume it will be available in TW for at least a few more years ?

echoing concern. very important to me to have X11 as wayland is not color managed. anyone working photographs or video currently requires X11.

Color management is in progress in Plasma Wayland. sRGB color management (similar to X11) is in place now. Expanded color management is planned for Plasma 6.1 in June. -- 真実はいつも一つ！/ Always, there's only one truth!

Patrick Shanahan wrote:

echoing concern. very important to me to have X11 as wayland is not color managed. anyone working photographs or video currently requires X11.

I tried out the color management in plasma6 wayland. You can specify an icc-profile per screen, very handy. The color management is very basic. It assumes that all apps output sRGB, then takes their output and converts it to the screen color space. So it's not usable for photo editing, if you work in bigger color spaces than sRGB. It does all calculations on the graphics hardware, so you shouldn't see a performance hit. Unfortunately, my integrated graphics is too weak, as I'm driving 2 4k screens, it only renders around 30 fps. Overall, it's very similar to what was possible with oyranos and compiz a decade ago. As far as I know, the plan for the future is: Every app, that doesn't opt out, is considered sRGB. Apps like Krita, Blender, Gimp have to explicitly opt out of general color management and are then responsible for drawing their own colors. But I don't know, if this is on the road map for 6.1 or for a later release. Because of the performance issues, and because QGIS doesn't work well in wayland, I switched back to X11. You might need to install "plasma6-session-x11". There is no difference in behavior to plasma5. Firefox works, gwenview works, krita works, gimp works, displayCAL works. Generally, this was the smoothest KDE upgrade I ever had! The visual tweaks to breeze are minimal, it kept my color scheme, my icons, my layout. Almost nothing has changed. And in X11, color management works as before. So you can upgrade savely.

On Thu, Mar 14, 2024 at 12:02 AM Andrei Borzenkov wrote:

On Wed, Mar 13, 2024 at 10:41 PM Fabian Vogt wrote:

...

The Wayland session isn't default yet, that will have to be switched in a separate step later.

The main reason I keep X11 in QEMU VM is clipboard sharing. Spice vdagent only supports X11 or GNOME (and works fine in another VM with GNOME/Wayland). Are there any improvements in KDE 6?

spice-vdagent needs support for wlr-data-control protocol: https://gitlab.freedesktop.org/spice/linux/vd_agent/-/issues/26 -- 真実はいつも一つ！/ Always, there's only one truth!

On Thu, Mar 14, 2024 at 7:28 AM Andrei Borzenkov wrote:

On Thu, Mar 14, 2024 at 1:53 PM Neal Gompa wrote:

...

On Thu, Mar 14, 2024 at 12:02 AM Andrei Borzenkov wrote:

...

On Wed, Mar 13, 2024 at 10:41 PM Fabian Vogt wrote:

...

The Wayland session isn't default yet, that will have to be switched in a separate step later.

The main reason I keep X11 in QEMU VM is clipboard sharing. Spice vdagent only supports X11 or GNOME (and works fine in another VM with GNOME/Wayland). Are there any improvements in KDE 6?

spice-vdagent needs support for wlr-data-control protocol: https://gitlab.freedesktop.org/spice/linux/vd_agent/-/issues/26

Sure, *that* I know :)

Any other possibilities not involving spice-vdagent?

Well, it now works on Plasma 6.0.3 for host-to-guest, but not the other way around through X11 clipboard stuff. https://invent.kde.org/plasma/kwin/-/commit/760e35065ed8b5f570f757cc464473b5... -- 真実はいつも一つ！/ Always, there's only one truth!

I just upgraded. It went smoothly. Minor cosmetic issues due to I was using latte-dock. Only remark that it defaulted to wayland for me, I think I'll keep it like that.

On jeudi 14 mars 2024 13:21:41 CET Ianseeks via openSUSE Factory wrote:

On Wednesday, 13 March 2024 19:41:37 GMT Fabian Vogt wrote:

...

the next TW snapshot 20240311 contains KDE Plasma 6.0.1, Gear 24.02.0 and Frameworks 6.0.0: https://kde.org/announcements/megarelease/6/

Plasma 5 will be replaced, it is no longer part of the repository.

Just a few problems on one of my logins but otherwise great. I'll post these on opensuse-support too, just posted here for reference.

With this login i'm using to post to the list, it all seems fine.

With my login for personal stuff, a few issues so far. 1. akondai won't start postgresql (worked fine before update)

QSqlDatabase: QPSQL driver not loaded

The reply wasn't sent to the list. If you're using the postgres backend, you have to install the qt6-sql- postgresql package. Christophe

March 14, 2024 at 8:10 AM, "Christophe Marin via openSUSE Factory" wrote:

...

...

1. akondai won't start postgresql (worked fine before update)

QSqlDatabase: QPSQL driver not loaded

The reply wasn't sent to the list.

If you're using the postgres backend, you have to install the qt6-sql-

postgresql package.

Christophe

Thanks Christophe, I ran into this akonadi not starting issue and I was about to create a post to this list when I saw your response. Installing qt6-sql-postgresql as you suggested works. Mark

On 2024-03-14 13:23, phanisvara das wrote:

i have been running plasma5 via wayland and during the installation of the megarelease i got kicked out of the graphical session, unable to start an X session again. i didn't pay attention to what was being installed at the time  :-/

Same here. I upgraded 3-4 minutes ago. To continue, I just did a zypper dup again and the process went well. I always make a zypper dup --download-only && zypper dup so that I don't need a network when the upgrade is in the process. There seem to be some things in the panel that don't work anymore. I'll get back about them if I can't fix it myself. -- /bengan

I should add that on a Ryzen 9 Mini Computer Plasma 6 on Wayland runs flawlessly on initial install. Haven't exercised it much yet though. On Thu, Mar 14, 2024 at 7:22 AM Chuck Davis wrote:

In my case X11 runs Plasma 6 flawlessly. Wayland not so much. With Wayland the mouse on my Dell Precision jerks and is unresponsive to the point it is unusable.

...

The Wayland session isn't default yet, that will have to be switched in a separate step later. This also makes it possible to differentiate whether bugs are more likely caused by Plasma 6 itself or the Wayland session.

Have a lot of fun, the openSUSE KDE packaging team

On 15/03/24 04:01, Freek de Kruijf wrote:

During upgrade with zypper dup, before zypper finished, the system rebooted and I was unable to login with a login screen showing a few messages about missing libraries. So I started a console session and used zypper dup to finish the upgrade. After that I could login again.

Same here.

The only change I noticed was that I now have to double click in Dolphin to open a folder and when I need to choose a file to open, I also need to double click on the file.

Same, same.

Did not try Wayland.

Defaulted to Wayland (tho' installation was already in it anyway). Other than all that, some widgets don't work - message "incompatible with Plasma 6" or similar. And I can't coax application kwallet into life at all - it just doesn't run. Early days yet .... -- Robin K Wellington "Harbour City" New Zealand

Hello, On jeudi 14 mars 2024 19:03:46 CET Joe Salmeri wrote:

Updating on of my test TW machines I got the following error

Installing: libMagicWand-7-Q16HDRI10-7.1.1.29-2_x86_64 update-alternatives: error: no alternatives for ImageMagick-7 error: ImageMagick-7.1.1.29-2.1_x86_64: install failed error: ImageMagick-config-7-SUSE-7.1.1.26-1.6.x86_64: erase skipped error: ImageMagick-7.1.1.26-1.6.x86_64: erase skipped Installing: ImageMagick-7.1.1.29-2.1-x86_64 Installation of ImageMagick-7.1.1.29-2.1-x86_64 failed: Error: Subprocess failed: Error RPM failed: Command exited with status 1.

That's https://bugzilla.suse.com/show_bug.cgi?id=1220818

On Thursday 14 March 2024 08:51:03 PM (+01:00), mh@mike.franken.de wrote:

On Donnerstag, 14. März 2024 20:44:10 CET mh@mike.franken.de wrote:

...

On Mittwoch, 13. März 2024 20:41:37 CET Fabian Vogt wrote:

...

Hi,

the next TW snapshot 20240311 contains KDE Plasma 6.0.1, Gear 24.02.0 and Frameworks 6.0.0: https://kde.org/announcements/megarelease/6/

Plasma 5 will be replaced, it is no longer part of the repository.

There are a few minor issues in this snapshot found by openQA but not considered severe enough to actually block the snapshot from getting published. They'll all be fixed with Plasma 6.0.2 in one of the next snapshots, also for those installing or upgrading now.

1. I had to install plasma6-sql-postgresql (as others already reported) 2. plasma6-x11 was not installed, although I used plasma5-x11 3. module entries for kdewallet were missing in pam.d/session-* files 4. custom shortcuts were gone

Correction: They exist, but do not work.

my custom shortcuts were also saved but not active. after creating new shortcuts they do work.

...

5. custom theme is gone

Could have bee worse ;)

Bye. Michael.

-- phani.

On Thursday 14 March 2024 09:13:32 PM (+01:00), Patrick Shanahan wrote:

* phanisvara das [03-14-24 15:56]:

...

On Thursday 14 March 2024 08:51:03 PM (+01:00), mh@mike.franken.de wrote:

...

On Donnerstag, 14. März 2024 20:44:10 CET mh@mike.franken.de wrote:

...

On Mittwoch, 13. März 2024 20:41:37 CET Fabian Vogt wrote:

...

Hi,

the next TW snapshot 20240311 contains KDE Plasma 6.0.1, Gear 24.02.0 and Frameworks 6.0.0: https://kde.org/announcements/megarelease/6/

Plasma 5 will be replaced, it is no longer part of the repository.

There are a few minor issues in this snapshot found by openQA but not considered severe enough to actually block the snapshot from getting published. They'll all be fixed with Plasma 6.0.2 in one of the next snapshots, also for those installing or upgrading now.

1. I had to install plasma6-sql-postgresql (as others already reported) 2. plasma6-x11 was not installed, although I used plasma5-x11 3. module entries for kdewallet were missing in pam.d/session-* files 4. custom shortcuts were gone

Correction: They exist, but do not work.

my custom shortcuts were also saved but not active. after creating new shortcuts they do work.

I deleted and recreated several but they do not work :(

I restarted plasma but did not help

when i recreated them within the container they were saved in, they did not work. only after creating new shortcuts from the "+" sign on top of the page, assigning a command, then a shortcut, then clicking the "apply" button at the bottom, did they start working.

* Patrick Shanahan [03-14-24 16:14]:

* phanisvara das [03-14-24 15:56]:

...

On Thursday 14 March 2024 08:51:03 PM (+01:00), mh@mike.franken.de wrote:

...

On Donnerstag, 14. März 2024 20:44:10 CET mh@mike.franken.de wrote:

...

On Mittwoch, 13. März 2024 20:41:37 CET Fabian Vogt wrote:

...

Hi,

the next TW snapshot 20240311 contains KDE Plasma 6.0.1, Gear 24.02.0 and Frameworks 6.0.0: https://kde.org/announcements/megarelease/6/

Plasma 5 will be replaced, it is no longer part of the repository.

There are a few minor issues in this snapshot found by openQA but not considered severe enough to actually block the snapshot from getting published. They'll all be fixed with Plasma 6.0.2 in one of the next snapshots, also for those installing or upgrading now.

1. I had to install plasma6-sql-postgresql (as others already reported) 2. plasma6-x11 was not installed, although I used plasma5-x11 3. module entries for kdewallet were missing in pam.d/session-* files 4. custom shortcuts were gone

Correction: They exist, but do not work.

my custom shortcuts were also saved but not active. after creating new shortcuts they do work.

I deleted and recreated several but they do not work :(

I restarted plasma but did not help

fwiw: after the fourth reboot, my *recreated* snapshots work. and those subsequently created also. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

* mh@mike.franken.de [03-15-24 17:58]:

On Freitag, 15. März 2024 22:34:14 CET Patrick Shanahan wrote:

...

* Patrick Shanahan [03-14-24 16:14]:

...

* phanisvara das [03-14-24 15:56]:

...

On Thursday 14 March 2024 08:51:03 PM (+01:00), mh@mike.franken.de wrote: [...]

...

...

4. custom shortcuts were gone

Correction: They exist, but do not work.

my custom shortcuts were also saved but not active. after creating new shortcuts they do work.> I deleted and recreated several but they do not work :(

I restarted plasma but did not help

fwiw: after the fourth reboot, my *recreated* snapshots work. and those subsequently created also.

Did you try with plasma 6.0.1 or 6.0.2?

both

With 6.0.1 newly created snapshots worked for me. With 6.0.2 nothing at all works - neither existing nor newly created ones. Especially for bash or perl scripts really crazy named desktop files are created. If you use something like $HOME, the complete directory tree to the script is copied to ~/.local/share/applications.

I use xset for screen blanker #! /bin/bash sleep .3 ; xset dpms force off and it works fine. note: sleep necessary to delay action until keyboard is clear. but I have not tried using variables for command address, only full path. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

On Freitag, 15. März 2024 23:31:22 CET Patrick Shanahan wrote:

* Patrick Shanahan [03-15-24 18:19]:

...

* mh@mike.franken.de [03-15-24 17:58]:

...

On Freitag, 15. März 2024 22:34:14 CET Patrick Shanahan wrote:

...

* Patrick Shanahan [03-14-24 16:14]:

...

* phanisvara das [03-14-24 15:56]:

...

On Thursday 14 March 2024 08:51:03 PM (+01:00), mh@mike.franken.de

wrote: [...]

...

...

...

> > 4. custom shortcuts were gone > > Correction: They exist, but do not work.

my custom shortcuts were also saved but not active. after creating new shortcuts they do work.>

I deleted and recreated several but they do not work :(

I restarted plasma but did not help

fwiw: after the fourth reboot, my *recreated* snapshots work. and those subsequently created also.

Did you try with plasma 6.0.1 or 6.0.2?

both

...

With 6.0.1 newly created snapshots worked for me. With 6.0.2 nothing at all works - neither existing nor newly created ones. Especially for bash or perl scripts really crazy named desktop files are created. If you use something like $HOME, the complete directory tree to the script is copied to ~/.local/share/applications.

I use xset for screen blanker

#! /bin/bash sleep .3 ; xset dpms force off

and it works fine. note: sleep necessary to delay action until keyboard is clear.

but I have not tried using variables for command address, only full path.

guess I very poorly explained. I have a script in ~/bin which I have set as a "script" to use Ctrl+Shift+X

and it works with plasma 6.0.2

Ok, so I spent an afternoon to test each and everything regarding shortcuts. Thats what I found out (not sure, though, if it completely correct): - The interface for custom shortcuts is ugly for both handling and optics. - Not only *some* shortcuts didn't work, but also *some* desktop "links to application". - .desktop files (belonging to both desktop icons and shortcuts) with links to shell scripts or binaries worked as expected, if they didn't need parameters; that's not true for all, but most parameters. I didn't find out, which parameters worked and which one didn't. - .desktop files linking to script files for other interpreters like perl never worked. So I wrote a starter shell script for all of my shortcuts and desktop icons. You can create links for the appropriate script or program with all the necessary parameters. These script links can be used for shortcuts or desktop icons as "application". ---------------------< snip >------------------ #!/bin/bash my_base=$( dirname $0 ) my_name=$( basename $0 ) ACTION="$1" declare -A APPSTART # some examples APPSTART["appstart-kcminit.sh"]="/usr/bin/kcminit /usr/lib64/qt5/plugins/ plasma/kcminit/kcm_mouse_init.so" APPSTART["appstart-pbpswitchusb.sh"]="monitor_pbp_switch -m U4924DW -a switchusb" APPSTART["appstart-pbpswitchboth.sh"]="monitor_pbp_switch -m U4924DW -a switchboth" APPSTART["appstart-pbpreset.sh"]="monitor_pbp_switch -m U4924DW -a reset" APPSTART["appstart-firefox.sh"]="firefox" APPSTART["appstart-calc.sh"]="kcalc" APPSTART["appstart-gvim.sh"]="gvim" APPSTART["appstart-plasmashell_restart.sh"]="plasmashell_restart" if test "$my_name" = "appstart"; then case "$ACTION" in mklink) for _appstart in "${!APPSTART[@]}" do _t="${my_base}/${_appstart}" test -L "${_t}.sh" \ || ln -s "${my_base}/${my_name}" "$_t" done ;; rmlink) for _appstart in "${!APPSTART[@]}" do _t="${my_base}/${_appstart}" test -L "$_t" && rm -f "$_t" done ;; esac else _run="${APPSTART[$my_name]}" if test -n "$_run"; then echo "running ${_run}" $_run & fi fi ---------------------< snip >------------------ Bye. Michael.

On Donnerstag, 14. März 2024 21:00:53 CET Patrick Shanahan wrote:

* mh@mike.franken.de [03-14-24 15:53]:

...

On Donnerstag, 14. März 2024 20:44:10 CET mh@mike.franken.de wrote: ...

[...]

...

...

3. module entries for kdewallet were missing in pam.d/session-* files

what I use worked

Does your kwallet get opened automatically with your plasma login password?

...

...

4. custom shortcuts were gone

Correction: They exist, but do not work.

same here.

Seems to be a problem with kglobalacceld6. There are a few open bugs regarding this service.

unfortunately X11 WAS NOT installed as default as I was led to believe nor even available w/o adding apps.

I only had to install plasma6-session-x11. Or did I misunderstand you?

past that and slow boot, most is good and functional.

Slow system boot? Or slow plasma6 boot? I don't have any of them, I don't even observe the 25s, Fabian mentioned in his initial post. Bye. Michael.

On 3/14/24 15:51, mh@mike.franken.de wrote:

2. plasma6-x11 was not installed, although I used plasma5-x11

FWIW, plasma6-session-x11 was installed when I did my update to 20240311. With plasma 5 these pkgs were installed plasma5-session X11 plasma5-session-wayland wayland Whereas with plasma 6 since wayland is now the default we have plasma6-session wayland plasma6-session-x11 x11 So they switched the pkg names based on the new default but my plasma 5 PCs and my plasma6 PCs have both installed. -- Regards, Joe

On Thu, 14 Mar 2024 20:44:10 +0100, mh@mike.franken.de wrote:

On Mittwoch, 13. März 2024 20:41:37 CET Fabian Vogt wrote:

...

Hi,

the next TW snapshot 20240311 contains KDE Plasma 6.0.1, Gear 24.02.0 and Frameworks 6.0.0: https://kde.org/announcements/megarelease/6/

Plasma 5 will be replaced, it is no longer part of the repository.

There are a few minor issues in this snapshot found by openQA but not considered severe enough to actually block the snapshot from getting published. They'll all be fixed with Plasma 6.0.2 in one of the next snapshots, also for those installing or upgrading now.

1. I had to install plasma6-sql-postgresql (as others already reported) 2. plasma6-x11 was not installed, although I used plasma5-x11 3. module entries for kdewallet were missing in pam.d/session-* files 4. custom shortcuts were gone 5. custom theme is gone

Could have bee worse ;)

Agree! I was looking forward to this. Apart from the shortcuts (easy to fix, just takes a bit of time), I am just disappointed (currently) in these remaining issues (to me): • Special Windows settings Alt-F3 or right-click titlebar - the menu appears in different positions. With Alt-F3, the position is logical, with right-click on the titlebar, it seems to appear on the top-left on the screen, which is rather weird when working on a window on the bottom-right of a 40" screen - Alt-F3 - More actions - No titlebar and frame has no option to *also* remove it from the taskbar. If I choose either "Configure Special Window settings" or "Configure Special Application Settings", the UI is completely incomprehensible. I have no idea what to do there. - Changes like the above are not saved, so restarting the X11 session (with or without a proper logout/end-session) will show titlebar and decoration again This means that getting into a "working state" for my laptop after a reboot will need a truckload of removing titlebars and decorations for windows that do not need them. Size and location seem to be preserved, but for the window *with* decoration, so I have to resize and reposition all of them after removing the decorations.

Michael.

-- H.Merijn Brand https://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.37 porting perl5 on HP-UX, AIX, and Linux https://tux.nl/email.html http://qa.perl.org https://www.test-smoke.org

On Freitag, 15. März 2024 00:34:25 CET dale via openSUSE Factory wrote:

I have dates and times including today, yesterday, etc in kmail.

On Thursday, March 14, 2024 7:24:19 PM EDT mh@mike.franken.de wrote:

...

On Mittwoch, 13. März 2024 20:41:37 CET Fabian Vogt wrote:

...

Hi,

the next TW snapshot 20240311 contains KDE Plasma 6.0.1, Gear 24.02.0 and Frameworks 6.0.0: https://kde.org/announcements/megarelease/6/

Plasma 5 will be replaced, it is no longer part of the repository.

One more problem: Kontact/Kmail doesn't show the receive date for mails - the columns remains empty.

Bye. Michael.

With akonadi using postgresql.

On Fri, Mar 15, 2024 at 1:25 PM wrote:

Next in the list:

I seriously doubt that this announcement was intended as the place to collect every possible bug in KDE 6.

Woohoo! Smooth sailing for the upgrade. The qt6-multimedia package was missing, so Elisa player did not play any audio files.

On Friday, 15 March 2024 12:43:17 GMT mh@mike.franken.de wrote:

On Freitag, 15. März 2024 13:31:18 CET Ianseeks via openSUSE Factory wrote:

...

On Wednesday, 13 March 2024 19:41:37 GMT Fabian Vogt wrote:

...

Hi,

the next TW snapshot 20240311 contains KDE Plasma 6.0.1, Gear 24.02.0 and Frameworks 6.0.0: https://kde.org/announcements/megarelease/6/

Since this update, one of my logins now takes nearly 2 minutes to get to desktop. I get the usual splash screen and that closes after a short while then i get a black screen for ages until the desktop finally arrives. Looking at the journal there are a couple of spots of no activity for 21 seconds and 15 seconds.

Is there somewhere i can put the log file to be read to save attaching it?

Anyone else with this problem?

As mentioned in the original posting:

4. Plasmashell takes 25s during start if bluetooth not available: https://bugs.kde.org/show_bug.cgi?id=481870 If kdeconnect-kde is installed on a system without bluetooth HW, it delays Plasma start by 25s. Workaround is to disable the KDE Connect systray icon.

Could that be the reason? Thanks.

i did think about that but the login i'm using does not suffer the same issue oo i thought it might be something else. I'm doing another zypper now so i'll check if the issue has gone.

...

regards

Ian

Bye. Michael.

openSUSE Tumbleweed 20240313 kwin 6.0.1 kmail2 6.0.0 (24.02.0) - akonadiserver 6.0.0 (24.02.0) - Kernel: 6.7.9-1- default - kernel-firmware-radeon 20240229

* Robert Kaiser [03-15-24 18:33]:

On 3/13/24 20:41, Fabian Vogt wrote:

...

the next TW snapshot 20240311 contains KDE Plasma 6.0.1, Gear 24.02.0 and Frameworks 6.0.0: https://kde.org/announcements/megarelease/6/

Plasma 5 will be replaced, it is no longer part of the repository.

Thanks for notifying here. It's great that people can test the new release, that's what TW is for.

no, Tw is a production environment but is UpToDate rather than stagnant.

It's also good for me to know to not update TW for a while as I'm depending heavily on full session restore and that's not yet working in Plasma 6 (I'm following the issue and hope they'll get this done soon).

fwiw: I only updated a single workstation to plasma 6 but after two days and currently updating the rest. and I do utilize Tw as a production environment and have for much longer than 10 years. and I have as few problems with the exception of continually updating as the multitude running Leap.xxx -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

For what it’s worth I had basically the same experience as Oliver, I don’t remember if I had to just wait for the next snapshot or the next two. From my point of view (I’m trying to just use Wayland) I had to set again the scaling factor to 200% for my 4K monitor and I noticed I have two VLCs now, one installed via zypper, one installed via flatpak. Did it become an hard dependency or what? I didn’t remember to have the zypper one before. Maybe it’s just me tho. Apart from that, everything working pretty great on the laptop I’m using with Plasma 6. Keep it up! Alessio

Il giorno 16 mar 2024, alle ore 10:30, Oliver Schwabedissen ha scritto:

For me, the update resulted in an unusable system. I updated from snapshot 20240310 (probably not a "very old system") to snapshot 20240314. So not only from Plasma5 to Plasma6, but also from kernel 6.7.7 to kernel 6.7.9.

As with some others, the KDE session crashed after about 2/3 of the installation. The system did not reboot but did a complete shutdown. On reboot I received several kernel error messages, presumably because the postinstall scripts could not be executed. The system booted up to a gray screen with 3 green squares. Nothing happened after that.

I then switched to a previous snapshot (snapper rollback) and was able to start the system again.

Since I installed the "tumbleweed" package, I was then able to perform the update step by step:

Switch to a textmode console, init 3, tumbleweed switch 20240311, zypper dup.

I then rebooted and repeated the procedure, this time switching to snapshot 20240313.

Finally, do the same again with snapshot 20240314.

After the 3rd reboot, the system started with Plasma6 without any problems. But although I had previously worked exclusively with X11 and Plasma5, I was forced to use Wayland. X11 was not available on the login screen. I therefore installed plasma6-session-x11 and can now work with X11 and Plasma6.

Let's see what else no longer works as expected...

Oliver

...

Am 13.03.24 um 20:41 schrieb Fabian Vogt: Hi,

the next TW snapshot 20240311 contains KDE Plasma 6.0.1, Gear 24.02.0 and Frameworks 6.0.0: https://kde.org/announcements/megarelease/6/

Plasma 5 will be replaced, it is no longer part of the repository.

There are a few minor issues in this snapshot found by openQA but not considered severe enough to actually block the snapshot from getting published. They'll all be fixed with Plasma 6.0.2 in one of the next snapshots, also for those installing or upgrading now.

1. For fresh installs, the GTK theme is not set correctly: https://bugs.kde.org/show_bug.cgi?id=482763 Workaround is to either set it manually in systemsettings or run "kded5" once in a terminal or krunner.

2. For upgrades (any version), the launcher icon switches to the Plasma one: https://github.com/openSUSE/plasma-opensuse/pull/25 Workaround is to change the icon manually to "start-here-branding" for now.

3. Upgrades from very old systems fail due to "libksysguard5-helper": https://bugzilla.opensuse.org/show_bug.cgi?id=1221350 When upgrading from Leap <= 15.3, you might encounter

Problem: libksysguard5-plugins-5.27.10-2.2.x86_64 requires libprocesscore.so.9()(64bit), but this requirement cannot be provided

As workaround, select the "deinstallation of libksysguard5-helper" option.

4. Plasmashell takes 25s during start if bluetooth not available: https://bugs.kde.org/show_bug.cgi?id=481870 If kdeconnect-kde is installed on a system without bluetooth HW, it delays Plasma start by 25s. Workaround is to disable the KDE Connect systray icon.

5. The etesync resource is broken in kdepim-runtime 24.02.0. It will be back in one of the next snapshots.

The Wayland session isn't default yet, that will have to be switched in a separate step later. This also makes it possible to differentiate whether bugs are more likely caused by Plasma 6 itself or the Wayland session.

Have a lot of fun, the openSUSE KDE packaging team

-- PGP Public Key available at https://pgp.mit.edu/ Key fingerprint = 3264 280C 05B1 572F 3F0B 42B8 1E7B 2D9D 063B D507

Op maandag 18 maart 2024 09:27:37 CET schreef Roger Oberholtzer:

My update failed. At some point when doing the installs, the system rebooted automatically. And I had a new sddm login screen, where I was expecting to see the completed zypper dup. On one display was a virtual keyboard, and on another was the sddm login. But with complaints about missing things. And a login failed, returning me back to the sddm login. The rollback failed. So I had to delete snapshots by hand to get to where I was before the attempted update. And now most of my system is read-only, even though the mounts are all rw. So, generally speaking, not a successful update. I'm now trying to see how to make the system not be read-only. The snapshot I am in is the most recent.

I did have the same experience, but after that I went to a console Ctrl+Alt+F1 and entered "zypper dup" which completed the upgrade. After a reboot I got the proper login screen and was able to login. Later I found out that I entered a Wayland session. Now I am back to X11 because SimpleScreenRecorder does not work in Wayland. -- fr.gr. member openSUSE Freek de Kruijf

I should have checked for a reboot. Silly me. It explains why my rollback did not work. On Mon, Mar 18, 2024 at 11:32 AM Fabian Vogt wrote:

Hi,

Am Montag, 18. März 2024, 09:27:37 CET schrieb Roger Oberholtzer:

...

My update failed. At some point when doing the installs, the system rebooted automatically.

No reboot, systemd macros kill the session: https://bugzilla.opensuse.org/show_bug.cgi?id=1221405

To recover from this, perform a rollback and either wait until the bug is fixed or perform the update outside of a graphical session.

Cheers, Fabian

...

...

So not only from Plasma5 to Plasma6, but also from kernel 6.7.7 to kernel 6.7.9.

...

As with some others, the KDE session crashed after about 2/3 of the

installation. The system did not reboot but did a complete shutdown. On reboot I received several kernel error messages, presumably because the postinstall scripts could not be executed. The system booted up to a gray screen with 3 green squares. Nothing happened after that.

...

I then switched to a previous snapshot (snapper rollback) and was

able to start the system again.

...

Since I installed the "tumbleweed" package, I was then able to

perform the update step by step:

...

Switch to a textmode console, init 3, tumbleweed switch 20240311,

zypper dup.

...

I then rebooted and repeated the procedure, this time switching to

snapshot 20240313.

...

Finally, do the same again with snapshot 20240314.

After the 3rd reboot, the system started with Plasma6 without any

problems. But although I had previously worked exclusively with X11 and Plasma5, I was forced to use Wayland. X11 was not available on the login screen. I therefore installed plasma6-session-x11 and can now work with X11 and Plasma6.

...

Let's see what else no longer works as expected...

Oliver

...

Am 13.03.24 um 20:41 schrieb Fabian Vogt: Hi,

the next TW snapshot 20240311 contains KDE Plasma 6.0.1, Gear

...

...

Frameworks 6.0.0: https://kde.org/announcements/megarelease/6/

Plasma 5 will be replaced, it is no longer part of the repository.

There are a few minor issues in this snapshot found by openQA but not considered severe enough to actually block the snapshot from getting published. They'll all be fixed with Plasma 6.0.2 in one of the next snapshots, also for those installing or upgrading now.

1. For fresh installs, the GTK theme is not set correctly: https://bugs.kde.org/show_bug.cgi?id=482763 Workaround is to either set it manually in systemsettings or run "kded5" once in a terminal or krunner.

2. For upgrades (any version), the launcher icon switches to the Plasma one: https://github.com/openSUSE/plasma-opensuse/pull/25 Workaround is to change the icon manually to "start-here-branding" for now.

3. Upgrades from very old systems fail due to "libksysguard5-helper": https://bugzilla.opensuse.org/show_bug.cgi?id=1221350 When upgrading from Leap <= 15.3, you might encounter

Problem: libksysguard5-plugins-5.27.10-2.2.x86_64 requires libprocesscore.so.9()(64bit), but this requirement cannot be

...

...

As workaround, select the "deinstallation of libksysguard5-helper"

24.02.0 and provided option.

...

...

4. Plasmashell takes 25s during start if bluetooth not available: https://bugs.kde.org/show_bug.cgi?id=481870 If kdeconnect-kde is installed on a system without bluetooth HW, it

delays

...

Plasma start by 25s. Workaround is to disable the KDE Connect systray icon.

5. The etesync resource is broken in kdepim-runtime 24.02.0. It will be back in one of the next snapshots.

The Wayland session isn't default yet, that will have to be switched in a separate step later. This also makes it possible to differentiate whether bugs are more likely caused by Plasma 6 itself or the Wayland session.

Have a lot of fun, the openSUSE KDE packaging team

-- PGP Public Key available at https://pgp.mit.edu/ Key fingerprint = 3264 280C 05B1 572F 3F0B 42B8 1E7B 2D9D 063B D507

...

And I had a new sddm login screen, where I was expecting to see the completed zypper dup. On one display was a virtual keyboard, and on another was the sddm login. But with complaints about missing things. And a login failed, returning me back to the sddm login. The rollback failed. So I had to delete snapshots by hand to get to where I was before the attempted update. And now most of my system is read-only, even though the mounts are all rw. So, generally speaking, not a successful update. I'm now trying to see how to make the system not be read-only. The snapshot I am in is the most recent.

On Sat, Mar 16, 2024 at 10:44 PM Alessio Biancalana via openSUSE Factory < factory@lists.opensuse.org> wrote:

...

For what it’s worth I had basically the same experience as Oliver, I don’t remember if I had to just wait for the next snapshot or the next two.

From my point of view (I’m trying to just use Wayland) I had to set again the scaling factor to 200% for my 4K monitor and I noticed I have two VLCs now, one installed via zypper, one installed via flatpak. Did it become an hard dependency or what? I didn’t remember to have the zypper one before. Maybe it’s just me tho.

Apart from that, everything working pretty great on the laptop I’m using with Plasma 6. Keep it up!

Alessio

...

Il giorno 16 mar 2024, alle ore 10:30, Oliver Schwabedissen < oliver@schwabedissen.name> ha scritto:

For me, the update resulted in an unusable system. I updated from snapshot 20240310 (probably not a "very old system") to snapshot

-- Roger Oberholtzer

On Montag, 18. März 2024 17:59:07 CET Jogchum Reitsma via openSUSE Factory wrote: [...]

The program icons on copied to the desktop do not function - is that what some posters in this topic describe as (not functioning) short cuts?

At least I think so. Open one of the non functional desktop files under ~/Desktop with an editor. Probably you'll see something weird in the Exec= line, for example apostrophes where they shouldn't be.

But for the rest, well done for such a massive release, I would say. Thanks!

regards, Jogchum

Bye. Michael.

On Montag, 18. März 2024 21:51:22 CET H.Merijn Brand via openSUSE Factory wrote:

On Mon, 18 Mar 2024 19:35:01 +0100, mh@mike.franken.de wrote:

...

On Montag, 18. März 2024 17:59:07 CET Jogchum Reitsma via openSUSE Factory wrote: [...]

...

The program icons on copied to the desktop do not function - is that what some posters in this topic describe as (not functioning) short cuts?

At least I think so.

To me it is something completely different: Withe the move from Plasma5 to Plasma6, all custom key bindings (shortcuts) where "forgotten".

The reason is, that in kde5 the khotkey service handled them, but in kde6 this service is no longer provided.

Systemsettings - Input & Output - Keyboard - Shortcuts

When I got to there, I see that the designated key bindings to my fav apps (e.g. Meta-X for Xterm) where still "known", but did not work.

Because there was a "connection" between those entries in kglobalaccel and khotkeyrc, but no service could handle them.

Changing them to something else (Shift-Alt-Control-Z) and back to what it was re-enables them. Not to big an issue to deal with

After that kglobalacceld itself now can handle them. Not sure if this is completely correct, but it is what I got from my tests. Bye. Michael.