Thanks, I’m on a waiting list now to go get them done at the hospital so they can gas me/knock me out
ISP wants me to use their “new” shiny modem/router as it is “much better!”.
But that modem does not offer the functions I need (I need to set my own DNS, port forwarding, etc) for my nextcloud, vpn, adguard.
ISP and me have crossed swords all day and ended in a stalemate: new modem has been activated, and “un-activated” (which was technically not possible, they said 
), the old one is online again and nothings is changed.
Took us all day to get this far 
.
I have not made new friends today.
1 Like
Good luck!
1 Like
Horrible companies to deal with at times. I’m hoping the one I signed up to and waiting to get connected sometime this week is as good as the electricity part of their company in terms of customer service and price (I’m just over $300 in credit with them now my last electricity company I was always having to pay the bill off, I swear they were reading the wrong meter).
Are you sure they actually bothered to read any meter rather than just taking the reading from the last time they did bother and add some average * period to it? 
I honestly don’t know, there’s no reason for them not to be able to read it. But thats in the past now, as long as this new company stays the same as they are now I’ll be happy.
Hey, I just started testing plasma 6 following along this thread. I have reported a few bugs that have been confirmed, but before I do anymore. I just wanted to see if any of you are experiencing the same issues.
Here is my system info: just in case: I do have nvidia, so that may cause some of these issues. Plus I am specifically interested in testing out the wayland session. I’m also using the beta 550 driver since it fixed a lot of the xwayland games flickering for me. At least it seems to when I tested with supertuxkart which flickered non stop on the 545 driver. Lastly this is a dual monitor setup, so yeah, I’ll probably run into all the problems.
Operating System: EndeavourOS
KDE Plasma Version: 5.92.0
KDE Frameworks Version: 5.248.0
Qt Version: 6.7.0
Kernel Version: 6.7.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7C95
System Version: 1.0
List of potential bugs:
-
Dragging an image from say firefox and dropping it onto the desktop, besides having to wait for 1 or more seconds (see this bug here https://bugs.kde.org/show_bug.cgi?id=448867), if you select
set image. It does nothing.
Edit 5: Bug report filed here (https://bugs.kde.org/show_bug.cgi?id=480557)
Confirmed -
Dragging an image from dolphin onto the desktop and again choosing
set imageworks initially, but after logging out and back in or rebooting. The setting seems to be reverted back to whatever the previous wallpaper was. In other words it doesn’t persist. (I jumped the gun and opened a bug report for this one already https://bugs.kde.org/show_bug.cgi?id=480509 , It would be nice if any of you can confirm whether or not you have the same issue though)
Confirmed -
Whenever I login there is a solid blue line underneath my top panel. It is only this panel for some reason. I’ll upload a picture of this later and further experiment with removing the panel and adding it back to see if that works.
Edit 2: Here is the picture of what I am talking about. I tried removing the panel, but it just appeared on the panel on my second monitor instead. It seems to appear only on one panel at a time, but if the only panel I have is the default one. Then it never appears.
Edit 6: Here is the bug report for this one (https://bugs.kde.org/show_bug.cgi?id=480558)
Resolved -
Sometimes kickoff, the default application launcher tied to the Super or Meta key does not launch when the button is pressed. Since my panels autohide, pressing the super / meta key will show the panel and even highlight the kickoff widget as if it had been activated, but it refuses to show up. I’ll try and capture this one on video.
Edit 3: I recorded a video showing what I mean but not sure how to share it.
Edit 7: Bug report which also has a video attachment of the issue that I could not show here (https://bugs.kde.org/show_bug.cgi?id=480559)
Edit 11: Resolved Upstream -
Spectacle’s pipewire recording works exactly one time. Every subsequent run causes spectacle to hang. Eventually I ended up having to kill the process.
Edit 1: this is the output for spectacle when it doesn’t outright crash.
kpipewire_record_logging: VAAPI: Display initialized
kpipewire_record_logging: VAAPI: API version 1 . 20
kpipewire_record_logging: VAAPI: VA-API NVDEC driver [egl backend] in use for device "/dev/dri/renderD128"
kpipewire_record_logging: DRM device not found
kpipewire_record_logging: VAAPI: Display initialized
kpipewire_record_logging: VAAPI: API version 1 . 20
kpipewire_record_logging: VAAPI: VA-API NVDEC driver [egl backend] in use for device "/dev/dri/renderD128"
kpipewire_record_logging: DRM device not found
KQuickPadding is both anonymous and named
qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/GlobalSonnetSettings.qml" and "qrc:/qt/qml/org/kde/desktop/private/MobileTextActionsToolBar.qml"
qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/GlobalSonnetSettings.qml" and "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml"
qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/MobileTextActionsToolBar.qml" and "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml"
qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/GlobalSonnetSettings.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml"
qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/MobileTextActionsToolBar.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml"
qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml"
qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/GlobalSonnetSettings.qml" and "qrc:/qt/qml/org/kde/desktop/private/CheckIndicator.qml"
qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/MobileTextActionsToolBar.qml" and "qrc:/qt/qml/org/kde/desktop/private/CheckIndicator.qml"
qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/private/CheckIndicator.qml"
kpipewire_logging: Stream error: no more input formats
kpipewire_logging: PipeWire remote error: -32 no more input formats
kpipewire_record_logging: VAAPI: Display initialized
kpipewire_record_logging: VAAPI: API version 1 . 20
kpipewire_record_logging: VAAPI: VA-API NVDEC driver [egl backend] in use for device "/dev/dri/renderD128"
kpipewire_record_logging: DRM device not found
kpipewire_record_logging: VAAPI: Display initialized
kpipewire_record_logging: VAAPI: API version 1 . 20
kpipewire_record_logging: VAAPI: VA-API NVDEC driver [egl backend] in use for device "/dev/dri/renderD128"
kpipewire_record_logging: DRM device not found
Killed
Edit 12: So far this was solved by me installing the “libva-nvidia-driver” package.
Edit 13: Once again an issue after RC2 update, but still mostly works better than before.
-
I activated the experimental hdr settings and it sets the default brightness for non hdr content to 200 nits. I tried recording the screen with spectacle. The one time I got it to work, but the resulting video was unwatchable because the recording was super bright and washed out. Despite the screen looking fine.
Edit 4: The same thing happens when using the gpu screen record app, so this is not just linked to pipewire.
Edit 8: Bug report regarding this one (https://bugs.kde.org/show_bug.cgi?id=480561)
Resolved after update to RC2 -
So far I have only noticed this in firefox and on these forums specifically, but some times the black line marker that lets you know where you are at when you are typing disappears. Clicking outside of the typing space and then back into it seems to fix that though. Perhaps this is one of those text input bugs I heard about.
-
Switching to a tty and back sometimes results in one or both of my monitors giving a black screen. Sometimes restarting the compositor solves the issue, but of course all applications are gone if you do this on wayland. However sometimes, if both screens are black. Only the mouse works.
Edit 9: filed this one here (https://bugs.kde.org/show_bug.cgi?id=480562)
Edit 11: Resolved after an update.
Newly Added
-
There seems to be some wonkiness when using the overview with a dual monitor setup. For example if I move a window from desktop 2 to desktop 1. It will show up on the first monitor on desktop 2. If I then click on the window. It will promptly disappear. At this point if I switch to desktop 1. It will be on the second monitor of desktop 1 like it is supposed to be.
Edit 10: This one was hard to describe and the resulting screen recording was about 78 MiB which is too big to upload to the bug tracker, but I filed a report about it anyway here (https://bugs.kde.org/show_bug.cgi?id=480564)
Confirmed -
Various issues when recording with spectacle now that I have gotten it work reliably.
-
The first issue is that when using a dual monitor setup. If I try to record using the full screen option, no matter which monitor I choose. It will only ever record my second monitor.
Resolved -
The second issue is that choosing the “window” option when recording results in the video being upside down.
I’ve file bugs for each of these:
Confirmed: https://bugs.kde.org/show_bug.cgi?id=480599
Solved: https://bugs.kde.org/show_bug.cgi?id=480600
This is what I have run into so far. If anyone can confirm any of these, then I will go ahead and file bug reports for them.
1 Like
Great to read what you’ve been doing, @d-air1.
Now that I’m online again I expect to be able to chime in again the next couple of days.
1 Like
You might get lucky: A few years back the water company installed new meters in our street.
These new meters would occasionally start running backwards.
Happy times 
.
1 Like
Spectacle has seen some problems under Plasma 6. On my setup is was unusable until I added swap.
@Schlaefer reported this bug:
https://bugs.kde.org/show_bug.cgi?id=478045
All bugs related to Spectacle under Plasma 6:
https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=NEEDSINFO&bug_status=VERIFIED&bug_status=CLOSED&classification=Applications&component=general&keywords=qt6%2C%20&keywords_type=allwords&list_id=2596140&product=Spectacle&query_format=advanced
1 Like
I tried dragging from firefox and all I got was the “wait-for-it!”-turning wheel - it stopped after 60 seconds or so, but nothing happened.
So, I can’t confirm your bug, but I can say it doesn’t work for me. I’ll investigate some more.
Edit: lots of typo’s.
1 Like
I’ll have to look into this; not sure what the set image equivalent is in my language.
1 Like
I see that blue line as well:
It only shows up if i click on that panel. If another screen object has focus, the blue line disappears.
Edit: removing the panel works but I have but one screen.
1 Like
Have not noticed this yet, will try and pay attention, though. I have no autohiding panels. I’ll see what happens if I turn that on.
1 Like
Yes, I have noticed that too. In fact it happened when I added the previous comment. Clicking elsewhere did not make the cursor reappear though.
1 Like
Can’t confirm - I’m on a laptop with only one screen.
1 Like
If you do, and link to the bug reports here, I’ll add my info to the reports as well.
Great work. 
1 Like
Alright, I think my issue seems to be related to that first bug you linked.
Alright, I’ll file a bug report for this one then if one doesn’t already exist. I’ll also edit my original post to include the bug reports as I file them.
Could have been a fluke on my part that it came back. I’ll try and investigate it more.