You are not logged in.
@ridge For testing purposes we downloaded a free JPEG pic of 6.4M. It was delayed, that's it. Image resists to shutdown, restart, lock and logout. Alt+d+s
@strangiato alt+tab opens default browser with thumbnail grid. Nothing broken here, not even Ark context menu.
Among new stuff on the taskbar, power profile is not available unless power-profiles-daemon is installed. It works fine after a restart. See message under battery icon.
There is no bug. and nothing is missing in the guess account. This first beta release is rock solid here.
Edit: Correction thumbnail grid -vs- compact mode in task switcher
Thumbnail grid opens active windows thumbnail popup. Default (compact) opens active windows popup (text only). The above result may have been caused by the update, but we learned long ago that shutdown fixes many things the next morning.
Last edited by Archcan_98 (2023-12-03 17:43:15)
Offline
> This first beta release is rock solid here.
not for all. yes if create a new user, not for upgrade from old
i'm still keep old plasma5, but upgrade to qt6/kf6 the rest of the apps
if not , desktop explode as f*** (wayland)
this package need to keep for working desktop
50 kde-unstable/bluedevil 1:5.27.9-1 -> 1:5.90.0-1
49 kde-unstable/drkonqi 5.27.9-2 -> 5.90.0-1
48 kde-unstable/kactivitymanagerd 5.27.9-1 -> 5.90.0-2
47 kde-unstable/kde-cli-tools 5.27.9-1 -> 5.90.0-1
46 kde-unstable/kde-gtk-config 5.27.9-1 -> 5.90.0-1
45 kde-unstable/kdecoration 5.27.9-1 -> 5.90.0-1
44 kde-unstable/kdeplasma-addons 5.27.9-1 -> 5.90.0-3
43 kde-unstable/kinfocenter 5.27.9-1 -> 5.90.0-1
42 kde-unstable/kmenuedit 5.27.9-1 -> 5.90.0-1
41 kde-unstable/kpipewire 5.27.9-1 -> 5.90.0-1
40 kde-unstable/kscreen 5.27.9-1 -> 5.90.0-1
39 kde-unstable/kscreenlocker 5.27.9-1 -> 5.90.0-1
38 kde-unstable/ksshaskpass 5.27.9-1 -> 5.90.0-1
37 kde-unstable/ksystemstats 5.27.9-1 -> 5.90.0-1
36 kde-unstable/kwallet-pam 5.27.9-1 -> 5.90.0-1
35 kde-unstable/kwayland-integration 5.27.9-1 -> 5.90.0-1
34 kde-unstable/kwin 5.27.9-1 -> 5.90.0-2
33 kde-unstable/kwrited 5.27.9-1 -> 5.90.0-1
32 kde-unstable/layer-shell-qt 5.27.9-1 -> 5.90.0-1
31 kde-unstable/libkscreen 5.27.9-1 -> 5.90.0-1
30 kde-unstable/libksysguard 5.27.9-1 -> 5.90.0-2
29 kde-unstable/milou 5.27.9-1 -> 5.90.0-1
28 kde-unstable/plasma-browser-integration 5.27.9-1 -> 5.90.0-1
27 kde-unstable/plasma-desktop 5.27.9-1 -> 5.90.0-2
26 kde-unstable/plasma-disks 5.27.9-1 -> 5.90.0-1
25 kde-unstable/plasma-firewall 5.27.9-1 -> 5.90.0-1
24 kde-unstable/plasma-integration 5.27.9-1 -> 5.90.0-1
23 kde-unstable/plasma-pa 5.27.9-1 -> 5.90.0-1
22 kde-unstable/plasma-systemmonitor 5.27.9-1 -> 5.90.0-1
21 kde-unstable/plasma-workspace 5.27.9.1-3 -> 5.90.0-2
20 kde-unstable/polkit-kde-agent 5.27.9-1 -> 5.90.0-1
19 kde-unstable/powerdevil 5.27.9-2 -> 5.90.0-2
18 kde-unstable/print-manager 23.08.3-1 -> 1:5.90.0-1
17 kde-unstable/systemsettings 5.27.9-1 -> 5.90.0-1
16 kde-unstable/xdg-desktop-portal-kde 5.27.9-1 -> 5.90.0-2
kded5 still make coredump sometimes, but i can live with it
greetings
Offline
I have not tested intensively but the X11 session seems to be in good shape, at least with a clean profile.
Excuse my poor English.
Offline
> This first beta release is rock solid here.
not for all. yes if create a new user, not for upgrade from old
i'm still keep old plasma5, but upgrade to qt6/kf6 the rest of the apps
if not , desktop explode as f*** (wayland)
Well I guess your mileage may vary.
I migrated from my old/current Plasma 5 session and it works really great here. And that's on Wayland too.
Except the missing Ark menu entries and KDE connect tray stuff I have no issue so far.
I experienced and alpha/beta tested KDE 3->4 and 4->5 transitions and so far this is the smoothest one.
Really kudos to the KDE team and the packagers !
Last edited by Akuma (2023-12-03 22:42:25)
AMD Ryzen 3700X - ASUS ROG STRIX B550 - Sapphire RX 580 - KDE Plasma
Offline
nvidia or intel/ati user?. only for discard things
greetings
Last edited by sl1pkn07 (2023-12-03 22:54:22)
Offline
nvidia or intel/ati user?. only for discard things
greetings
amdgpu.
AMD Ryzen 3700X - ASUS ROG STRIX B550 - Sapphire RX 580 - KDE Plasma
Offline
I have not tested intensively but the X11 session seems to be in good shape, at least with a clean profile.
I can say the same for the Wayland session. The first impressions of this beta are excellent, unlike the last alpha. For a moment I was even thinking about jumping to Plasma 6 right now on my main machine, but I think I'll wait until all the KDE applications I use are available in Qt6 version.
(AMD gpu + clean profile)
Excuse my poor English.
Offline
With a bit of manual juggling I got 5.90 installed. Things seem okay so far.
Any idea why my keyboard input doesn't work in SDDM with Wayland? I copied the suggested config from the wiki but keyboard inputs are not registered, also the Virtual keyboard option is crossed out. Not a big deal, it works with X11.
Offline
Any idea why my keyboard input doesn't work in SDDM with Wayland? I copied the suggested config from the wiki but keyboard inputs are not registered, also the Virtual keyboard option is crossed out. Not a big deal, it works with X11.
This is fixed in a recent commit to layer-shell-qt. See [1] and [2].
To fix this, you can compile it from source.
[1] https://bugs.kde.org/show_bug.cgi?id=477251
[2] https://invent.kde.org/plasma/layer-she … equests/48
Last edited by fanzhuyifan (2023-12-04 19:08:11)
Offline
Nice... however, if I build layer-shell-qt from source myself, SDDM and Plasma break. I wonder if it's because I have mix of Qt5 and Qt6 on the system.
Offline
Nice... however, if I build layer-shell-qt from source myself, SDDM and Plasma break. I wonder if it's because I have mix of Qt5 and Qt6 on the system.
That's not good.. If you want you could open a separate thread about this, so that we don't clutter up this thread too much.
Offline
MadCat_X wrote:Nice... however, if I build layer-shell-qt from source myself, SDDM and Plasma break. I wonder if it's because I have mix of Qt5 and Qt6 on the system.
That's not good.. If you want you could open a separate thread about this, so that we don't clutter up this thread too much.
Let me investigate this a little bit. I got sidetracked by not being able to mount my encrypted external drive, apparently because SolidUiServer cannot be called over D-Bus. AFAICT the whole "kf.solid.backends.udisks2" service is not running.
Let's take it one step at a time. I'll try to build layer-shell-qt from a clean chroot and see if that helps.
Offline
Okay, building layer-shell-qt from a chrooted environment fixes the breakage. With the patch you suggested I get a working keyboard in waylandized SDDM! Nice!
Offline
There is cyclic dependencies between xdg-desktop-portal-kde, plasma-integration, and plasma-workspace in KDE-unstable.
xdg-desktop-portal-kde depends on plasma-workspace, which depends on plasma-integration, which depends on xdg-desktop-portal-kde. Not sure what to do about those.
Offline
A cool new feature in plasma 6. Since kde-servicemenus-rootactions doesn't work with plasma 6 so I tried sudo dolphin. Below is the results.
Running Dolphin with sudo is not supported as it can cause bugs and expose you to security vulnerabilities. Instead, install the `kio-admin` package from your distro and use it to manage root-owned locations by right-clicking on them and selecting "Open as Administrator"
Offline
There is cyclic dependencies between xdg-desktop-portal-kde, plasma-integration, and plasma-workspace in KDE-unstable.
xdg-desktop-portal-kde depends on plasma-workspace, which depends on plasma-integration, which depends on xdg-desktop-portal-kde. Not sure what to do about those.
You don't need to do anything.
Offline
@sergekorol su works and su works on guess account. This is an old plasma 6 bug. No need for kio-admin, a buggy place to be. Adding open as root service in the Dolphin context menu is also buggy. Fedora 40 has a good one, but not available in Arch.
@fanzhuyifan Other than that, you don't have to do anything.
:: Starting full system upgrade...
:: Replace breeze with kde-unstable/breeze5? [Y/n] n
:: Replace kgamma5 with kde-unstable/kgamma? [Y/n] y
:: Replace oxygen with kde-unstable/oxygen5? [Y/n] n
:: Replace plasma-integration with kde-unstable/plasma5-integration? [Y/n] y
:: Replace plasma-wayland-session with kde-unstable/plasma-workspace? [Y/n] y
Offline
MTP seems not to be working for me in Plasma 6. Not sure if this is an upstream issue.
When I plug my phone in and select "File transfer / Android Auto", the device notifier doesn't see it. It's also not visible in Dolphin's Places panel.
I do have kio-extras installed, and it is detected by the kernel:
$ lsusb
Bus 001 Device 025: ID 18d1:4ee2 Google Inc. Nexus/Pixel Device (MTP + debug)
mtp-detect seems to think KDE has done something:
$ mtp-detect
libmtp version: 1.1.21
Listing raw device(s)
Device 0 (VID=18d1 and PID=4ee2) is a Google Inc Nexus/Pixel (MTP+ADB).
Found 1 device(s):
Google Inc: Nexus/Pixel (MTP+ADB) (18d1:4ee2) @ bus 1, dev 27
Attempting to connect device(s)
libusb_claim_interface() reports device is busy, likely in use by GVFS or KDE MTP device handling alreadyLIBMTP PANIC: Unable to initialize device
Unable to open raw device 0
OK.
Offline
MTP seems not to be working for me in Plasma 6. Not sure if this is an upstream issue.
Don't know if it's related, but KDE Connect cannot mount over sshfs either. But it's definitely upstream, because they're both broken when I tried MTP and sshfs in a Neon live USB
Offline
grassmonk wrote:MTP seems not to be working for me in Plasma 6. Not sure if this is an upstream issue.
Don't know if it's related, but KDE Connect cannot mount over sshfs either. But it's definitely upstream, because they're both broken when I tried MTP and sshfs in a Neon live USB
I reported https://bugs.kde.org/show_bug.cgi?id=478285 and it seems it's fixed, so hopefully beta 2 will work.
Offline
I reported https://bugs.kde.org/show_bug.cgi?id=478285 and it seems it's fixed, so hopefully beta 2 will work.
Cheers
Offline
After updating this morning, SDDM won't start:
Dec 16 11:12:32 samsungstick systemd[1]: Started Simple Desktop Display Manager.
Dec 16 11:12:32 samsungstick sddm[522]: /usr/bin/sddm: error while loading shared libraries: libicui18n.so.74: cannot open shared object file: No such file or directory
Dec 16 11:12:32 samsungstick systemd[1]: sddm.service: Main process exited, code=exited, status=127/n/a
Dec 16 11:12:32 samsungstick systemd[1]: sddm.service: Failed with result 'exit-code'.
Dec 16 11:12:32 samsungstick systemd[1]: sddm.service: Scheduled restart job, restart counter is at 1.
Dec 16 11:12:32 samsungstick systemd[1]: Started Simple Desktop Display Manager.
Dec 16 11:12:32 samsungstick sddm[524]: /usr/bin/sddm: error while loading shared libraries: libicui18n.so.74: cannot open shared object file: No such file or directory
Dec 16 11:12:32 samsungstick systemd[1]: sddm.service: Main process exited, code=exited, status=127/n/a
Dec 16 11:12:32 samsungstick systemd[1]: sddm.service: Failed with result 'exit-code'.
Dec 16 11:12:33 samsungstick systemd[1]: sddm.service: Scheduled restart job, restart counter is at 2.
Dec 16 11:12:33 samsungstick systemd[1]: sddm.service: Start request repeated too quickly.
Dec 16 11:12:33 samsungstick systemd[1]: sddm.service: Failed with result 'exit-code'.
Dec 16 11:12:33 samsungstick systemd[1]: Failed to start Simple Desktop Display Manager.
I tried reinstalling the icu package:
[2023-12-16T10:28:09-0500] [PACMAN] Running 'pacman -S icu'
[2023-12-16T10:28:13-0500] [ALPM] reinstalled icu (73.2-2)
I'm guessing I need 74.
Thanks to everyone working on this transition, especially as always arojas.
Offline
[2023-12-16T10:28:09-0500] [PACMAN] Running 'pacman -S icu' [2023-12-16T10:28:13-0500] [ALPM] reinstalled icu (73.2-2)
I'm guessing I need 74.
74 is in the core-testing repo, have you enabled it?
BTW: Anyone else not able to make Akonadi calendars to show up in the calendar plasmoid, when you click the clock in a panel?
(I'm using CalDAV, they're added via Merkuro Calendar)
Last edited by ridge (2023-12-16 17:00:21)
Offline
Thanks ridge. I had core-testing commented out, for reasons known to no one. SDDM starting now.
Offline
heads up, kde-unstable will be in a broken state for most of the day. I'd suggest not to update in the next 24 hours
Offline