Upgrade KDE Wayland Spin 38->39 KDE Background Screen Issue
by richard emberson
Upgrade KDE Wayland Spin 38->39 KDE Background Screen Issue
KDE Screen Issue (or Plasma issue, or...)
1) Login screen comes up and can login.
2) KDE screen mix of colors and black... moving mouse and screen continues
to redraw random colors (but, mostly black).
3) Bottom panel (in hide mode) comes up and looks normal. Top ToolBar
is drawing like the screen (not normal) but I can tell its being drawn
ontop of the screen background (different colors/black).
5) Firefox comes up rendering like normal.
6) Thunderbird asks for password and it comes up drawing like normal.
7) Using Mouse Right Button, menu come up (look normal) and can
8 "Open Terminal". Kconsole comes up like normal.
9) From Kconsole can launch alacritty multiple times all normal.
10) Background and ToolBar still not rendering correctly.
11) Can move mouse over ToolBar and popups appear. Can also click and
launch/hide terminals, firefox, thunderbird when mouse if over their
position in ToolBar.
12) I can render a jpeg photo in eog and it comes up just fine.
With Fedora 38 KDE Spin I did not have this issue with the background
or ToolBar.
So, has anyone seen this behavior?
Where do I start?
Thanks.
Richard
Notes:
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
dmesg
First mention of nouveau (same as in /var/log/messages):
[ 4.179073] nouveau 0000:01:00.0: vgaarb: deactivate vga console
[ 4.180078] Console: switching to colour dummy device 80x25
[ 4.180114] nouveau 0000:01:00.0: NVIDIA GT218 (0a8280b1)
[ 4.299581] nouveau 0000:01:00.0: bios: version 70.18.6f.00.05
[ 4.300463] nouveau 0000:01:00.0: fb: 1024 MiB DDR3
[ 4.976871] nouveau 0000:01:00.0: DRM: VRAM: 1024 MiB
[ 4.976880] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[ 4.976883] nouveau 0000:01:00.0: DRM: TMDS table version 2.0
[ 4.976885] nouveau 0000:01:00.0: DRM: DCB version 4.0
[ 4.976887] nouveau 0000:01:00.0: DRM: DCB outp 00: 01000302 00020030
XXXXXXXXXX
Near bottom of dmesg:
[ 31.161539] ixgbe 0000:02:00.0 enp2s0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[ 45.207388] nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 4 [sddm-greeter[1097]] get 000021f5e8 put 0000220df4 ib_get 00000015 ib_put 00000016 state 80000000 (err: INVALID_CMD) push 00400040
[ 256.400353] systemd-journald[538]: File /var/log/journal/582cf700f5764fe09e7f2b1840341c3b/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[ 300.729194] nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 9 [plasmashell[1612]] get 0000621000 put 0000621088 ib_get 00000015 ib_put 00000016 state 80000024 (err: INVALID_CMD) push 00400040
[ 301.168768] nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 9 [plasmashell[1612]] get 0000621088 put 0000622944 ib_get 00000017 ib_put 00000018 state 80000024 (err: INVALID_CMD) push 00400040
....
[ 301.678444] nouveau 0000:01:00.0: gr: DATA_ERROR 0000000c [INVALID_BITFIELD]
[ 301.678448] nouveau 0000:01:00.0: gr: 00100000 [] ch 9 [003f208000 plasmashell[1612]] subc 3 class 8597 mthd 1dc0 data 03816308
[ 301.678460] nouveau 0000:01:00.0: gr: DATA_ERROR 0000000c [INVALID_BITFIELD]
[ 301.678463] nouveau 0000:01:00.0: gr: 00100000 [] ch 9 [003f208000 plasmashell[1612]] subc 3 class 8597 mthd 1dc4 data 187c7dc0
[ 301.678479] nouveau 0000:01:00.0: gr: DATA_ERROR 0000000c [INVALID_BITFIELD]
.....
[ 301.678537] nouveau 0000:01:00.0: gr: DATA_ERROR 00000005 [INVALID_ENUM]
[ 301.678541] nouveau 0000:01:00.0: gr: 00100000 [] ch 9 [003f208000 plasmashell[1612]] subc 3 class 8597 mthd 1e00 data 00040060
[ 301.678554] nouveau 0000:01:00.0: gr: DATA_ERROR 00000005 [INVALID_ENUM]
[ 301.678557] nouveau 0000:01:00.0: gr: 00100000 [] ch 9 [003f208000 plasmashell[1612]] subc 3 class 8597 mthd 1e04 data beef0201
[ 301.678568] nouveau 0000:01:00.0: gr: DATA_ERROR 00000005 [INVALID_ENUM]
[ 301.678571] nouveau 0000:01:00.0: gr: 00100000 [] ch 9 [003f208000 plasmashell[1612]] subc 3 class 8597 mthd 1e08 data 00140010
....
[ 362.200940] nouveau 0000:01:00.0: fifo: CACHE_ERROR - ch 9 [plasmashell[1612]] subc 3 mthd 0000 data 00000030
[ 362.211967] nouveau 0000:01:00.0: gr: TRAP_MP_EXEC - TP 0 MP 0: 00000010 [INVALID_OPCODE] at 000000 warp 0, opcode ff9b8456 ff9b8456
[ 362.211976] nouveau 0000:01:00.0: gr: TRAP_MP_EXEC - TP 0 MP 1: 00000010 [INVALID_OPCODE] at 000000 warp 0, opcode ff9b8456 ff9b8456
....
[ 362.319066] nouveau 0000:01:00.0: gr: 00200000 [] ch 9 [003f208000 plasmashell[1612]] subc 3 class 8597 mthd 15e0 data 00000000
[ 362.323151] nouveau 0000:01:00.0: gr: TRAP_CCACHE 00000001 [FAULT]
[ 362.323158] nouveau 0000:01:00.0: gr: TRAP_CCACHE 000e0080 00000000 00000000 00000000 00000000 00000004 00000000
[ 362.323161] nouveau 0000:01:00.0: gr: 00200000 [] ch 9 [003f208000 plasmashell[1612]] subc 3 class 8597 mthd 15e0 data 00000000
[ 362.323171] nouveau 0000:01:00.0: fb: trapped read at 0000000000 on channel 9 [3f208000 plasmashell[1612]] engine 00 [PGRAPH] client 05 [CCACHE] subclient 00 [CB] reason 00000002 [PAGE_NOT_PRESENT]
[ 362.334146] nouveau 0000:01:00.0: gr: TRAP_CCACHE 00000001 [FAULT]
...
[ 364.471270] nouveau 0000:01:00.0: fb: trapped read at 0000000000 on channel 9 [3f208000 plasmashell[1612]] engine 00 [PGRAPH] client 05 [CCACHE] subclient 00 [CB] reason 00000002 [PAGE_NOT_PRESENT]
[ 521.901383] perf: interrupt took too long (2508 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
[ 566.002661] EXT4-fs (sdb1): mounted filesystem cc75fc98-10fb-41ab-9fb7-6f58b3c07b76 r/w with ordered data mode. Quota mode: none.
[ 566.645348] EXT4-fs (sdc1): mounted filesystem 055939b6-6a83-43ec-9d9a-e5394567ff3f r/w with ordered data mode. Quota mode: none.
[ 566.768251] EXT4-fs (sdd1): mounted filesystem 8d6d8835-64ce-416e-9acf-918c4810894a r/w with ordered data mode. Quota mode: none.
[ 566.864909] EXT4-fs (sde1): mounted filesystem c388fa01-5314-4e4c-8bc5-cbd9b4d85b4f r/w with ordered data mode. Quota mode: none.
[ 567.013171] EXT4-fs (sdf): mounted filesystem f4860393-482a-41aa-a7e2-601ee6afbc03 r/w with ordered data mode. Quota mode: none.
[ 1032.769502] perf: interrupt took too long (3140 > 3135), lowering kernel.perf_event_max_sample_rate to 63000
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
/var/log/boot.log
All "OK" no ERRORS
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
/var/log/messages
The following appears 2018 times (and counting):
Nov 30 14:26:59 olympia kactivitymanagerd[1631]: kf.service.services: The desktop entry file "/usr/share/applications/org.freedesktop.Xwayland.desktop" has Type= "Application" but has no Exec field.
# grep freedesktop.Xwayland.desktop messages | wc -l
2018
XXXXXXXXXX
Some nouveau messages:
Nov 30 12:42:57 olympia kernel: nouveau 0000:01:00.0: vgaarb: deactivate vga console
Nov 30 12:42:57 olympia kernel: Console: switching to colour dummy device 80x25
Nov 30 12:42:57 olympia kernel: nouveau 0000:01:00.0: NVIDIA GT218 (0a8280b1)
Nov 30 12:42:57 olympia kernel: ixgbe 0000:02:00.0 enp2s0: renamed from eth0
Nov 30 12:42:57 olympia kernel: nouveau 0000:01:00.0: bios: version 70.18.6f.00.05
Nov 30 12:42:57 olympia kernel: nouveau 0000:01:00.0: fb: 1024 MiB DDR3
Nov 30 12:42:58 olympia kernel: nouveau 0000:01:00.0: DRM: VRAM: 1024 MiB
Nov 30 12:42:58 olympia kernel: nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
Nov 30 12:42:58 olympia kernel: nouveau 0000:01:00.0: DRM: TMDS table version 2.0
XXXXXXXXXX
At bottom of messages file:
Nov 30 14:43:54 olympia baloo_file_extractor[5398]: kf.baloo: Failed to add include folder config entry for "/home/emberson"
Nov 30 14:43:54 olympia baloo_file_extractor[5398]: kf.baloo: Failed to add include folder config entry for "/home/emberson"
Nov 30 14:43:54 olympia baloo_file_extractor[5398]: kf.baloo: Failed to add include folder config entry for "/home/emberson"
Nov 30 14:43:54 olympia baloo_file_extractor[5398]: kf.baloo: Failed to add exclude folder config entry for "/home/emberson"
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
1 day, 23 hours
Python code error in F39, but not in F38
by Ranjan Maitra
Hi,
I was running the code here: https://github.com/maitra/Visual-Information-Fidelity---Python3
However, the code runs in F38 (python 3.11) without error, but not in F39 (python 3.12) where it
ends with a segmentation fault (after doing the calculations).
Both, however, give an answer that are not the same after the 14th
decimal place. Not sure if I should be bothered about that.
Looking at valgrind, I can not tell if there is an error in the python call itself. Here is what I get (note that the code calls shared objects created by the gcc compiler).
==278781== Invalid read of size 8
==278781== at 0x4A50B5B: UnknownInlinedFun (pycore_pystate.h:118)
==278781== by 0x4A50B5B: UnknownInlinedFun (obmalloc.c:866)
==278781== by 0x4A50B5B: _PyObject_Free (obmalloc.c:1850)
==278781== by 0x6526E92E: UnknownInlinedFun (siplib.c:2241)
==278781== by 0x6526E92E: UnknownInlinedFun (objmap.c:69)
==278781== by 0x6526E92E: finalise (siplib.c:2143)
==278781== by 0x49AC4D3: UnknownInlinedFun (pylifecycle.c:3018)
==278781== by 0x49AC4D3: Py_FinalizeEx.cold (pylifecycle.c:1977)
==278781== by 0x4B22336: Py_RunMain (main.c:691)
==278781== by 0x4ADD85B: Py_BytesMain (main.c:743)
==278781== by 0x4EE1149: (below main) (libc_start_call_main.h:58)
==278781== Address 0x10 is not stack'd, malloc'd or (recently) free'd
==278781==
==278781==
==278781== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==278781== Access not within mapped region at address 0x10
==278781== at 0x4A50B5B: UnknownInlinedFun (pycore_pystate.h:118)
==278781== by 0x4A50B5B: UnknownInlinedFun (obmalloc.c:866)
==278781== by 0x4A50B5B: _PyObject_Free (obmalloc.c:1850)
==278781== by 0x6526E92E: finalise (siplib.c:2143)
==278781== by 0x49AC4D3: UnknownInlinedFun (pylifecycle.c:3018)
==278781== by 0x49AC4D3: Py_FinalizeEx.cold (pylifecycle.c:1977)
==278781== by 0x4B22336: Py_RunMain (main.c:691)
==278781== by 0x4ADD85B: Py_BytesMain (main.c:743)
==278781== by 0x4EE1149: (below main) (libc_start_call_main.h:58)
==278781== If you believe this happened as a result of a stack
==278781== overflow in your program's main thread (unlikely but
==278781== possible), you can try to increase the size of the
==278781== main thread stack using the --main-stacksize= flag.
==278781== The main thread stack size used in this run was 8388608.
==278781==
==278781== HEAP SUMMARY:
==278781== in use at exit: 18,046,811 bytes in 92,137 blocks
==278781== total heap usage: 2,212,074 allocs, 2,119,937 frees, 1,983,813,202 bytes allocated
==278781==
==278781== LEAK SUMMARY:
==278781== definitely lost: 2,160,027 bytes in 41,915 blocks
==278781== indirectly lost: 112 bytes in 2 blocks
==278781== possibly lost: 5,021,632 bytes in 34,430 blocks
==278781== still reachable: 10,863,024 bytes in 15,769 blocks
==278781== suppressed: 0 bytes in 0 blocks
It is possible that there is a bug in the code itself, but nothing above
points to my created code.
Any suggestions? Or is this a bug?
Many thanks and best wishes,
Ranjan
6 days, 22 hours
Black screen after login to F39
by Michael Eager
I upgraded from Fedora 38 to Fedora 39 on an AMD Ryzen 5 5600
with Nvidia Geforce RTX 3050 graphics card. I'm running KDE
Plasma-X11, not Wayland.
I tried to install the GPU drivers several ways using repos/RPMs,
but was not successful. I am using the Nvidia proprietary
drivers. They support dual monitors with no problems; I've had
problems with the nouveau driver and dual monitors in the past.
I start the system in multi-user (CLI) mode and then run "startx"
to start X11 and Plasma. (I started doing this in F38 because of
sddm hanging, which I was not able to resolve.)
When I log in with my user account and run startx, I get a black
screen (extending across both monitors) with an X cursor. The
cursor moves in response to the mouse, but neither left or right
mouse button do anything. I can get to an alternate console
using alt-F3 and kill the login.
I have discovered a bit of a rain dance to get a working system. I
can log in as root, run startx, and get a working KDE Plasma-X11
screen. Then I log out to the sddm screen and log in again with
my user account. After this, everything (or almost everything)
works correctly.
I've checked the system logs and the Xorg log for any error
or warning messages, but nothing looks incorrect or at all
informative.
Does anyone have any suggestions or insights into this problem?
--
Michael Eager
1 week
Virtualbox vs VMware for Fedora?
by Sbob
All;
I am running Fedora39, I have run VMware workstation for years, and I
have on and off had issues since VMware does not officially support
Fedora, normally I run a patch after each kernel update and it mostly
just works.
I am also running the osx unlocker so I can run mac VM's
I recently tried virtualbox on a spare laptop, havent looked at
virtualbox in years, and I was impressed, a few questions for the community:
- can I run the osx unlocker with virtualbox?
- does virtualbox have the same issues where it needs a patch after
each kernel and sometimes
just breaks with a new kernel , even with the patch?
Thanks in advance
1 week
conflict with ffmpeg
by Michael Hennebry
More joy of a recent upgrade.
Last metadata expiration check: 0:01:05 ago on Fri 24 Nov 2023 07:29:43 PM CST.
Error:
Problem: problem with installed package libswscale-free-6.0-5.fc38.x86_64
- package ffmpeg-libs-6.0-6.fc38.x86_64 from rpmfusion-free conflicts with
libswscale-free provided by libswscale-free-6.0-5.fc38.x86_64 from @System
- package ffmpeg-libs-6.0-6.fc38.x86_64 from rpmfusion-free conflicts with
libswscale-free provided by libswscale-free-6.0-2.fc38.x86_64 from fedora
- package ffmpeg-libs-6.0-6.fc38.x86_64 from rpmfusion-free conflicts with
libswscale-free provided by libswscale-free-6.0.1-1.fc38.x86_64 from updates
- package ffmpeg-6.0-6.fc38.x86_64 from rpmfusion-free requires
ffmpeg-libs(x86-64) = 6.0-6.fc38, but none of the providers can be installed
- conflicting requests
- package ffmpeg-6.0.1-2.fc38.x86_64 from rpmfusion-free-updates requires
ffmpeg-libs(x86-64) = 6.0.1-2.fc38, but none of the providers can be installed
- package ffmpeg-libs-6.0.1-2.fc38.x86_64 from rpmfusion-free-updates
conflicts with libswscale-free provided by libswscale-free-6.0-5.fc38.x86_64
from @System
- package ffmpeg-libs-6.0.1-2.fc38.x86_64 from rpmfusion-free-updates
conflicts with libswscale-free provided by libswscale-free-6.0-2.fc38.x86_64
from fedora
- package ffmpeg-libs-6.0.1-2.fc38.x86_64 from rpmfusion-free-updates
conflicts with libswscale-free provided by libswscale-free-6.0.1-1.fc38.x86_64
from updates
(try to add '--allowerasing' to command line to replace conflicting packages or
'--skip-broken' to skip uninstallable packages)
[hennebry@fedora ~]$
--allowerasing would seem to be the only suggestion likely to result in a
functional ffmpeg,
but I do not kow what damage that would cause.
Suggestions?
I was hoping for a --dry-run or some such option,
but no such luck.
--
Michael hennebry(a)mail.cs.ndsu.NoDak.edu
"I was just thinking about the life of a pumpkin. Grow up in the sun,
happily entwined with others, and then someone comes along,
cuts you open, and rips your guts out." -- Buffy
1 week, 1 day
NFS Mount Point Write Failure
by Stephen Morris
I have a network drive being mounted from the following entry in /etc/fstab:
192.168.1.12:/mnt/HD/HD_a2 /mnt/nfs nfs
users,nconnect=2,owner,rw,_netdev 0 0
This results in the following definition in /etc/mtab:
192.168.1.12:/mnt/HD/HD_a2 /mnt/nfs nfs
rw,nosuid,nodev,noexec,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,nconnect=2,timeo=600,retran
s=2,sec=sys,mountaddr=192.168.1.12,mountvers=3,mountport=57759,mountproto=udp,local_lock=none,addr=192.168.1.12
0 0
I can read from the mount point but I can't write to it.
A touch /mnt/nfs/filetest.txt fails with a read only volume error:
touch: cannot touch '/mnt/nfs/filetest.txt': Read-only file system
Can anyone guide me on what I am doing wrong, I am using F39, and I
believe the fstab specification worked fine in F38 before I upgraded to F39.
regards,
Steve
1 week, 2 days
vlc alternative?
by Alex
Hi,
I'm using vlc with my hdhomerun TV tuner, but vlc has a problem that hasn't
been fixed for a really long time. Does anyone have a recommendation for a
similar app I can use for streaming?
I'm really only otherwise familiar with mplayer, but I don't think it
supports streaming in this way where I can connect it to a socket like I
can with vlc.
btw, the vlc error involves messages like these:
[00007fb3a4001130] ts demux error: libdvbpsi error (PSI decoder): TS
discontinuity (received 10, expected 9) for PID 112
Thanks,
Alex
1 week, 3 days
DNF Upgrade from F38 to F39 Issues
by Stephen Morris
Hi,
I used dnf system-upgrade to upgrade from F38 to F39. After the
upgrade when I booted into gdm to login and start KDE, the machine hung
on KDE startup into X11.
Thinking it might be an nvidia UEFI enrolment issue with the F39
nvidia drivers, I reset the machine and booted back into gdm.
I then used ctrl+alt+F2 to start a terminal interface. In that
terminal I went through the UEFI enrolment process but that said the
drivers were already enrolled.
I issued dmesg to see if there were any nvidia failure messages, of
which there none, but I did notice there were initialisation and what
looked like failure messages from Nouveau, but I don't understand why
there would be an Nouveau messages at all when Nouveau is blacklisted in
the kernel parameters in grub.
I then uninstalled all the nvidia drivers that were present. I then
used ctrl+alt+delete to reboot from the terminal. That process hung for
1.5 minutes waiting for a job stop (I don't remember what it was waiting
on), and, when the 1.5 minute timer finished it then hung waiting for
XWayland to shut down. Why was it waiting for XWayland to shut down when
I don't use Wayland, I only use X11?
On reboot, I started up KDE under Nouveau, which doesn't work
properly with my BENQ 4K monitor, it can't determine what the monitor
is, so doesn't run in the right resolutions, although it does honour the
display scaling specified when using the nvidia drivers (which do
recognise the monitor and set things up properly).
I reinstalled the nvidia drivers and a subsequent reboot then
booted into KDE with any issues (which is where I'm sending this email
from). Why did this freezing of the nvidia drivers happen, is it because
the F39 nvidia drivers don't work properly with an update and have to be
installed from scratch to work properly?
Also, after reinstalling the nvidia drivers, at the gdm login
screen the display manager selection options only showed "Gnome", "Gnome
Classic" and "Plasma/X11", where are the options for all of those to
swap them between Wayland and X11 if I want to, that were present in F38
before the upgrade to F39?
regards,
Steve
1 week, 3 days
Openh264, ffmpeg,etc.
by Ger van Dijck
Hi Fedora/Linux Lovers,
I have the impression that the problems with Fedora-Cisco-Openh264 and
FFmpeg gives me the idea of "The ever continued story of
Coronationstreet".
When I do an dnf update I get the following message:
Fedora 39 openh264 (From Cisco)-x86_64 Errors during downloading for
fedora-cisco-openh264.
Statuscode 404 for
https://codecs/fedoraproject.org/openh264/39/x86_64/repodata/repomd.xml
(IP 18.133.140.134).
Cannot download repodata/repomd.xml : All mirrors were tried.
Failed to download metadata for "fedora-cisco-openh264".
I found a solution in downloading Repo Terra 39 Fedora and could
install openh264 : And all , you dont believe it functioned.
I had a very helpsome discussion with Tom Horsley, Samual Sieb,Jef
Walton and Go Cames.
When giving dnf info openh264 I got from Terra 39 Fedora installed
packages : Repos Terra 39 Fedora openh264 Fedora URL
https://www.openh264.org
License:BSD.
UPDATED:
DNfdagora did sent a messsage on November 24.11.2023 to update some
objects and in this list :
gstreamer1-plugin-openh264-1.22.7-2.fc39.x86_64
openh264-2.4.0-1.fc39.x86_64
INStALLED:
openh264-2.4.0-2.fc39.x86_64
After this execised nothing did functioned anymore.
Dnfdagora did sent a message on November 25.11.2023 to update objects
and in this list:
UPDATED:
libde265-1.0.13-1.fc39.86_64
After that
INSTLALLED:
gstreamer1-plugin-openh264-1.22.7-2.fc39.86_64
ffmpeg-libs-3.3.6-3.4.x86_64
ffmpeg-3.3.6-3.4.x86_64
libavdevice-3.3.6-3.4.x86_64
UPDATED:
ffmpeg-libs-6.0.1-3.fc39.x86_64
ffmpeg-6.0.1-3.fc39.x86_64
libavdevice-6.0.1-3.fc39.X86_64
And all runs : Thanks God.
Is there in this (Unix) world someone (Abe Ye Kanobi ?) who can and is
willing to solve this problem ?
Ger van Dijck
1 week, 4 days
kernel-6.6.2-201.fc39.x86_64 does not boot, process hangs
by olivares33561
Dear fellow fedora users,
upon updating and rebooting the new kernel refuses to boot or just hangs. How do I troubleshoot this issue?
I have to boot 6.5.12-300 so I can use the computer.
Thanks in Advance,
Antonio
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
1 week, 4 days
