[systemsettings] [Bug 455431] "Spare Layouts" feature on Wayland
https://bugs.kde.org/show_bug.cgi?id=455431 geisserml changed: What|Removed |Added CC||geisse...@gmail.com --- Comment #17 from geisserml --- Also experiencing this issue. It's quite useful to have a group of main layouts to switch through, and other layouts on demand with specific shortcuts. e.g. native layout with and without dead keys as primary group (toggle shortcut for frequent switching), and a cyrillic layout with separate shortcut as it is needed only occasionally. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 475850] Flatpak build produces permission error on attempt to play video
https://bugs.kde.org/show_bug.cgi?id=475850 --- Comment #5 from geisserml --- > As for the releases I'm not sure, I was under the impression that apps get > "refreshes" without a version bump. I'll ask the Flatpak guy I know and see > if I can pry more details from him. Indeed, `flatpak update` revealed that a new build was available, even though https://flathub.org/apps/org.kde.plasmatube still says "23.08.2 - 11 days ago". Kind of confusing, but I can confirm the new build does fix the issue. Thanks! > If you want the latest yt-dlp, that would be a distribution packaged > plasmatube + mpv + yt-dlp. I tried the Fedora 37 distro package first, but it is unable to display channel content, which fails with `qrc:/VideoGridItem.qml:58:9: QML Image: Error decoding: https://yt.artemislena.eu/: Unsupported image format` I can file a separate issue about that if desired. The problem with distro packages is, they're often a bit outdated, while flatpak is a convenient way to get latest releases. However, that's kind of outweighed if bundled deps fall outdated in return, but I understand this might just be an intentional flatpak limitation. If there were actual build instructions, I could perhaps build from source, but I'm not used to kdesrc-build yet. -- You are receiving this mail because: You are watching all bug changes.
[audiotube] [Bug 464708] Option to list all results in Audiotube
https://bugs.kde.org/show_bug.cgi?id=464708 geisserml changed: What|Removed |Added CC||geisse...@gmail.com --- Comment #1 from geisserml --- +1. Unfortunately audiotube isn't really navigable/usable for me if one can only see the first few items of an artist. -- You are receiving this mail because: You are watching all bug changes.
[audiotube] [Bug 474806] KeyError: 'acodec' every time I try to open a song
https://bugs.kde.org/show_bug.cgi?id=474806 geisserml changed: What|Removed |Added CC||geisse...@gmail.com --- Comment #1 from geisserml --- Same for me with the Fedora 37 package, see also https://invent.kde.org/multimedia/audiotube/-/issues/30#note_786752 Latest flatpak works, though. I guess audiotube & deps just have to be updated frequently to stay in sync with the server. Maybe classical distro packages don't make too much sense here, unless continuous updates can be managed. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 475850] Flatpak build produces permission error on attempt to play video
https://bugs.kde.org/show_bug.cgi?id=475850 --- Comment #3 from geisserml --- Thanks! However, since the issue seems to have been outdated yt-dlp, how can we prevent this from reoccurring? Is there any chance of auto-updating the bundled yt-dlp and releasing a new flatpak whenever a new version is available? My understanding is that one should always use the latest available version of yt-dlp. Also, while the PR has produced a new test build, it looks like the actual release flatpak might only be updated whenever there's a new KDE apps batch release? But yt-dlp might have to be updated independently if we want to avoid gaps of breakage. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 475850] New: Flatpak build produces permission error on attempt to play video
https://bugs.kde.org/show_bug.cgi?id=475850 Bug ID: 475850 Summary: Flatpak build produces permission error on attempt to play video Classification: Applications Product: PlasmaTube Version: 23.08.2 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: geisse...@gmail.com CC: espi...@gmail.com Target Milestone: --- SUMMARY Video playback doesn't seem to work with the flatpak package. STEPS TO REPRODUCE 1. flatpak run org.kde.plasmatube OBSERVED RESULT ``` qrc:/videoplayer/VideoControls.qml:237:5: QML Dialog: Binding loop detected for property "implicitHeight" qrc:/videoplayer/VideoControls.qml:237:5: QML Dialog: Binding loop detected for property "implicitHeight" qrc:/components/Sidebar.qml:9:1: QML Sidebar: Binding loop detected for property "contentHeight" file:///usr/lib/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight" file:///usr/lib/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight" file:///usr/lib/qml/org/kde/kirigami.2/ContextDrawer.qml:135:9: QML ListView: Binding loop detected for property "topMargin" Cannot load libcuda.so.1 file:///usr/lib/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight" file:///usr/lib/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight" [ffmpeg] https: HTTP error 403 Forbidden Failed to open https://rr1---sn-h0jeened.googlevideo.com/videoplayback?expire=1697768291=A48xZYawCarA6dsPxpSLiA4=2003%3Ad3%3A8707%3A8d00%3Ada09%3A449b%3Af0f5%3Af44a=o-AMsBeWhw8GNf7Vf9AfKZa8-fiszcpaFgbX6iqjSE5SbE=22=youtube=yes=Xp=31%2C26=sn-h0jeened%2Csn-4g5edndz=au%2Conr=m=1=43=de=1452500=UWF9fwP2hOGM6KMqeeDZP2f71cMrF4Asn_dUsPCosg=1=1=video%2Fmp4=14=yes=501.643=1592541062827497=1697746390=3=24007246=24350018=ANDROID=2316222=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cgcr%2Cspc%2Cvprv%2Csvpuc%2Cmime%2Ccnr%2Cratebypass%2Cdur%2Clmt=AGM4YrMwRQIgPaPMBHnS5cx-qtYTRzPP--3imwGpwfzyvHRdZyZUn9sCIQDH3BaBMySTiCYPVgjjd5pjqUsJ2u9Vv6yqOssRgo1DlQ%3D%3D=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps=AK1ks_kwRgIhAKJka4U50q4PR4bury-4nwBc6OZM4VN4Oml5HAwMNUabAiEAoccVz8MPnNVJ3H8GLcfS9k-U_sdgO4Wc5Gxpu95Yw9k%3D. [ytdl_hook] ERROR: [generic] None: Unable to download webpage: HTTP Error 403: Forbidden (caused by ); please report this issue on https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using yt-dlp -U [ytdl_hook] youtube-dl failed: unexpected error occurred [ffmpeg] https: HTTP error 403 Forbidden Failed to open https://rr1---sn-h0jeened.googlevideo.com/videoplayback?expire=1697768291=A48xZYawCarA6dsPxpSLiA4=2003%3Ad3%3A8707%3A8d00%3Ada09%3A449b%3Af0f5%3Af44a=o-AMsBeWhw8GNf7Vf9AfKZa8-fiszcpaFgbX6iqjSE5SbE=22=youtube=yes=Xp=31%2C26=sn-h0jeened%2Csn-4g5edndz=au%2Conr=m=1=43=de=1452500=UWF9fwP2hOGM6KMqeeDZP2f71cMrF4Asn_dUsPCosg=1=1=video%2Fmp4=14=yes=501.643=1592541062827497=1697746390=3=24007246=24350018=ANDROID=2316222=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cgcr%2Cspc%2Cvprv%2Csvpuc%2Cmime%2Ccnr%2Cratebypass%2Cdur%2Clmt=AGM4YrMwRQIgPaPMBHnS5cx-qtYTRzPP--3imwGpwfzyvHRdZyZUn9sCIQDH3BaBMySTiCYPVgjjd5pjqUsJ2u9Vv6yqOssRgo1DlQ%3D%3D=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps=AK1ks_kwRgIhAKJka4U50q4PR4bury-4nwBc6OZM4VN4Oml5HAwMNUabAiEAoccVz8MPnNVJ3H8GLcfS9k-U_sdgO4Wc5Gxpu95Yw9k%3D. ``` EXPECTED RESULT Working playback SOFTWARE/OS VERSIONS Flatpak ADDITIONAL INFORMATION Used instance: https://yt.artemislena.eu/ -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 463695] Unable to make screenshot on Wayland
https://bugs.kde.org/show_bug.cgi?id=463695 --- Comment #31 from geisserml --- Thanks for clarifying! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 463695] Unable to make screenshot on Wayland
https://bugs.kde.org/show_bug.cgi?id=463695 --- Comment #29 from geisserml --- @drmacro Does it crash, or does it say "Could not take a screenshot", or both? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 463695] Unable to make screenshot on Wayland
https://bugs.kde.org/show_bug.cgi?id=463695 --- Comment #25 from geisserml --- For me, the problem is gone. Should we close this bug, or keep it open for others to provide further feedback? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 463695] Unable to make screenshot on Wayland
https://bugs.kde.org/show_bug.cgi?id=463695 --- Comment #22 from geisserml --- Funnily enough, my spectacle now randomly works again. Let's see if it stays that way. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 463695] Unable to make screenshot on Wayland
https://bugs.kde.org/show_bug.cgi?id=463695 --- Comment #21 from geisserml --- Thanks for linking the ksnip thread, that's interesting... I see there is an entry `X-KDE-DBUS-Restricted-Interfaces=org.kde.kwin.Screenshot,org.kde.KWin.ScreenShot2` in the .desktop file, but I can't believe that's taken for a permission check. That would be inherently unsafe, especially if local desktop files were taken into account, wouldn't it? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 463695] Unable to make screenshot on Wayland
https://bugs.kde.org/show_bug.cgi?id=463695 --- Comment #19 from geisserml --- Crazy. It looks like your bug might be something fundamentally different compared to mine? Are you sure you're drawing the right logical connections and that this is not just coincidence? I see your screencast, but I still can't logically understand how the desktop file should change anything, if you run spectacle from the command line - aren't desktop files only relevant for launching apps from a graphical interface ... ? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 463695] Unable to make screenshot on Wayland
https://bugs.kde.org/show_bug.cgi?id=463695 --- Comment #17 from geisserml --- Trying to take a screenshot via qdbus fails as well: ``` $ qdbus-qt5 org.kde.KWin.ScreenShot2 /Screenshot org.kde.kwin.Screenshot.screenshotFullscreen Error: org.kde.kwin.Screenshot.Error.NoAuthorized The process is not authorized to take a screenshot ``` (I assembled the command by completion proposals, so not fully sure if it's actually valid, but it seems to run into the same permission error...) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 463695] Unable to make screenshot on Wayland
https://bugs.kde.org/show_bug.cgi?id=463695 --- Comment #15 from geisserml --- Again, none of what Prajna Sariputra wrote applies to my case. I don't have a spectacle entry in `~/.local/share/applications`, and `/usr/share/applications/org.kde.spectacle.desktop` shows `Exec=/usr/bin/spectacle`. Logically, running `update-desktop-database` does not change the situation for me. Apart from that, I never had a custom build of spectacle installed, but I guess Prajna Sariputra might have. From what you wrote, I suppose your `spectacle` does not resolve to `/usr/bin/spectacle`, but something different, like `/usr/local/bin/spectacle` - can you check the return of `which spectacle` to confirm? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 463695] Unable to make screenshot on Wayland
https://bugs.kde.org/show_bug.cgi?id=463695 --- Comment #13 from geisserml --- Is there any way how I could help you reproduce/analyse this? FWIW, I also installed the kdeapps flatpak beta of spectacle, but its GUI doesn't even show up. Is this expected? The command line output basically is ``` $ flatpak run org.kde.spectacle --version libEGL warning: wayland-egl: could not open /dev/dri/renderD128 (No such file or directory) spectacle 23.03.70 $ flatpak run org.kde.spectacle libEGL warning: wayland-egl: could not open /dev/dri/renderD128 (No such file or directory) Error querying plasma version "org.freedesktop.DBus.Error.ServiceUnknown" "org.freedesktop.DBus.Error.ServiceUnknown" [geisserml: further occurrences hidden] Error calling KWin DBus interface: "org.kde.kwin.Screenshot.Error.NoAuthorized" "The process is not authorized to take a screenshot" ``` -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 463695] Unable to make screenshot on Wayland
https://bugs.kde.org/show_bug.cgi?id=463695 --- Comment #11 from geisserml --- Since this is a permission error, I wonder if it is possible to somehow inspect/modify which applications/binaries have screenshot permission? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 463695] Unable to make screenshot on Wayland
https://bugs.kde.org/show_bug.cgi?id=463695 --- Comment #10 from geisserml --- (In reply to Noah Davis from comment #7) > Is Spectacle being run from the same prefix as kwin_wayland? If you're using > /usr/bin/kwin_wayland, you have to use /usr/bin/spectacle. They're both from /usr/bin (verified using command paths shown in process explorer). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427913] Resizing the sidebar causes disk write to go up
https://bugs.kde.org/show_bug.cgi?id=427913 geisserml changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||23.03 Status|CONFIRMED |RESOLVED --- Comment #10 from geisserml --- @popov895 Ah, I just realized by name that you are probably the author of the MR yourself? If that's right, then thanks a lot for your work! I just installed the okular beta via kdeapps flatpak and can confirm that the bug is indeed fixed. Resizing is now super smooth again, as it used to be back in 2020. And of course it's nice the panel can now be moved. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427913] Resizing the sidebar causes disk write to go up
https://bugs.kde.org/show_bug.cgi?id=427913 --- Comment #8 from geisserml --- (In reply to popov895 from comment #7) > Isn't this fixed along with BUG 455013? Certainly looks like a nice change, but I can't tell if it will actually fix this issue (AFAICS, the topic resizing wasn't explicitly mentioned anywhere on that MR). If I'm not mistaken, the change is supposed to land in Okular 23.04? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427913] Resizing the sidebar causes disk write to go up
https://bugs.kde.org/show_bug.cgi?id=427913 --- Comment #6 from geisserml --- > Please don't change the Version field, which represents the _initial_ version > which showed the issue. Ah, that makes sense. Sorry! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427913] Resizing the sidebar causes disk write to go up
https://bugs.kde.org/show_bug.cgi?id=427913 --- Comment #4 from geisserml --- *** Bug 441676 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 441676] Resizing the left panel is jerky
https://bugs.kde.org/show_bug.cgi?id=441676 geisserml changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from geisserml --- Bug 427913 mentions config file writes on any movement as possible cause, so maybe users with faster disks don't experience this as much... *** This bug has been marked as a duplicate of bug 427913 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427913] Resizing the sidebar causes disk write to go up
https://bugs.kde.org/show_bug.cgi?id=427913 geisserml changed: What|Removed |Added Version|1.11.2 |22.12.1 --- Comment #3 from geisserml --- I reported Bug 441676 linked in the See Also section, and unfortunately the problem still persists with Okular 22.12.1. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 463695] Unable to make screenshot on Wayland
https://bugs.kde.org/show_bug.cgi?id=463695 --- Comment #6 from geisserml --- The problem persists in spite of some KDE updates. I wonder if I'm the only one experiencing this on Fedora 37? Anyway, I'd be glad if something could be done; I use screenshots a lot and ksnip is really inconvenient compared to spectacle. (Or if anyone can recommend a better XDG-based screenshot tool than ksnip, that would be welcome too.) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 452669] Slideshow controls do not work on Wayland
https://bugs.kde.org/show_bug.cgi?id=452669 geisserml changed: What|Removed |Added CC||geisse...@gmail.com --- Comment #7 from geisserml --- I can confirm the problem. Slideshow control works on X11 but doesn't work on Wayland. Lucky I found this thread, as I would not have thought this to be related to Wayland. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 463695] Unable to make screenshot on Wayland
https://bugs.kde.org/show_bug.cgi?id=463695 --- Comment #4 from geisserml --- I cannot confirm Prajna Sariputra's findings. Downgrading Spectacle does not fix the problem for me, nor does upgrading back. IMO, the points I mentioned are evidence that some KDE component might be broken, esp. since ksnip's Plasma Wayland backend fails but the generic XDG one still works. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 463695] Unable to make screenshot on Wayland
https://bugs.kde.org/show_bug.cgi?id=463695 --- Comment #2 from geisserml --- FWIW, ksnip works, but only if "Force Generic Wayland (xdg-desktop-portal) Screenshots" is set. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 463695] Unable to make screenshot on Wayland
https://bugs.kde.org/show_bug.cgi?id=463695 --- Comment #1 from geisserml --- Created attachment 154940 --> https://bugs.kde.org/attachment.cgi?id=154940=edit Screencast via OBS -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 442900] [Feature request] Optional reStructuredText syntax highlighting for inline Python documentation
https://bugs.kde.org/show_bug.cgi?id=442900 geisserml changed: What|Removed |Added Resolution|--- |REMIND Status|REPORTED|RESOLVED --- Comment #1 from geisserml --- Closing as I'm not using KDevelop anymore. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 446683] Syntax highlighting for property functions is confusing
https://bugs.kde.org/show_bug.cgi?id=446683 geisserml changed: What|Removed |Added Resolution|--- |REMIND Status|REPORTED|RESOLVED --- Comment #2 from geisserml --- Closing as I'm not using KDevelop anymore. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 436412] Package dependency option cannot be changed
https://bugs.kde.org/show_bug.cgi?id=436412 geisserml changed: What|Removed |Added Resolution|--- |REMIND Status|REPORTED|RESOLVED --- Comment #2 from geisserml --- Closing as I'm not using muon anymore. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 436409] Locked packages cannot be unlocked
https://bugs.kde.org/show_bug.cgi?id=436409 geisserml changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |REMIND --- Comment #3 from geisserml --- Closing as I'm not using muon anymore. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 441675] Right part of File Assosications page is cropped off on smaller monitors
https://bugs.kde.org/show_bug.cgi?id=441675 geisserml changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |REMIND --- Comment #4 from geisserml --- Closing as there's a workaround and I'm not using a 5:4 monitor anymore. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439480] Google accounts can't be added
https://bugs.kde.org/show_bug.cgi?id=439480 geisserml changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from geisserml --- Closing, I'm now content with Thunderbird anyway. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 446076] Wine is not installable
https://bugs.kde.org/show_bug.cgi?id=446076 geisserml changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from geisserml --- Closing as I'm not using KDE Neon anymore. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450252] Overview effect shows blank rectangles instead of virtual desktop previews
https://bugs.kde.org/show_bug.cgi?id=450252 geisserml changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #4 from geisserml --- Closing as the bug is gone since I switched distribution. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 463695] New: Unable to make screenshot on Wayland
https://bugs.kde.org/show_bug.cgi?id=463695 Bug ID: 463695 Summary: Unable to make screenshot on Wayland Classification: Applications Product: Spectacle Version: 22.12.0 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: geisse...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY Since recent updates on Fedora 37, Spectacle is broken, reporting 'Could not take a screenshot. Please report this bug here: [...]'. Console output says 'Screenshot request failed: "The process is not authorized to take a screenshot"'. STEPS TO REPRODUCE 1. Open Spectacle on Wayland 2. View error message OBSERVED RESULT Spectacle is defunct EXPECTED RESULT Spectacle should work SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.0.15-300.fc37.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442226] [search/replace + Wayland] Strange pop-ups instead of a dropdown menu for completition propositions
https://bugs.kde.org/show_bug.cgi?id=442226 geisserml changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #6 from geisserml --- (In reply to Christoph Cullmann from comment #5) > Please try a more recent version, I use Wayland now since months and have > not seen this. > I think the is no general switch to turn all this stuff of, if comboboxes > fail to work, something is very broken. You're right, that bug is gone, and I had almost forgotten about this report. I don't remember if it had already disappeared while I was still using kde neon, or if it was only since I switched to opensuse. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 441668] Please make middle-click pasting optional
https://bugs.kde.org/show_bug.cgi?id=441668 --- Comment #21 from geisserml --- I think it was stated in comment [1] that it is not nicely possible to implement this setting with X11. [1] https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/970#note_462083 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 441668] Please make middle-click pasting optional
https://bugs.kde.org/show_bug.cgi?id=441668 geisserml changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #19 from geisserml --- Thanks! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 441668] Please make middle-click pasting optional
https://bugs.kde.org/show_bug.cgi?id=441668 --- Comment #12 from geisserml --- > But this needs to be reviewed, please be patient. Sure, take your time :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 441668] Please make middle-click pasting optional
https://bugs.kde.org/show_bug.cgi?id=441668 --- Comment #10 from geisserml --- (In reply to Bug Janitor Service from comment #9) > A possibly relevant merge request was started @ > https://invent.kde.org/plasma/kwin/-/merge_requests/2487 If I understood this right, once the PR is merged, we can add the lines below to `~/.config/kwinrc` to disable middle-click paste on Wayland? ``` [Wayland] EnablePrimarySelection=false ``` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450252] Overview effect shows blank rectangles instead of virtual desktop previews
https://bugs.kde.org/show_bug.cgi?id=450252 geisserml changed: What|Removed |Added Summary|Overview effect shows blank |Overview effect shows blank |rectangles instead of |rectangles instead of |virtual desktop previews|virtual desktop previews |with software rendering | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450252] Overview effect shows blank rectangles instead of virtual desktop previews with software rendering
https://bugs.kde.org/show_bug.cgi?id=450252 --- Comment #3 from geisserml --- I just checked that this bug is also present without software rendering. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450252] Overview effect shows blank rectangles instead of virtual desktop previews with software rendering
https://bugs.kde.org/show_bug.cgi?id=450252 --- Comment #2 from geisserml --- > This looks like a QtQuick bug. Yeah, probably. QtQuick is very buggy on my system anyway, sadly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450252] New: Overview effect shows blank rectangles instead of virtual desktop previews
https://bugs.kde.org/show_bug.cgi?id=450252 Bug ID: 450252 Summary: Overview effect shows blank rectangles instead of virtual desktop previews Product: kwin Version: 5.24.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: geisse...@gmail.com Target Milestone: --- Created attachment 146735 --> https://bugs.kde.org/attachment.cgi?id=146735=edit Screenshot of the bug SUMMARY The Overview effect does not show previews of the virtual desktops at the top as expected. Instead, there's only a white rectangle. STEPS TO REPRODUCE 1. Open the overview effect 2. Take a look at the virtual desktop bar OBSERVED RESULT Blank rectangles (screenshot attached). EXPECTED RESULT Preview of the desktop as I've seen in screencasts from other users. Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-28-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz Memory: 7.2 GiB of RAM Graphics Processor: llvmpipe ADDITIONAL INFORMATION Note that I have to use software rendering (`LIBGL_ALWAYAS_SOFTWARE=1`) due to this QtQuick bug: https://bugreports.qt.io/browse/QTBUG-99686 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 geisserml changed: What|Removed |Added CC||geisse...@gmail.com --- Comment #476 from geisserml --- As far as I am concerned, there is way too much unproductive off-topic talk in this thread. Can you please carry that out elsewhere in some chat room? This is a bug tracker after all. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 geisserml changed: What|Removed |Added CC|geisse...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439938] System Monitor causes the system to overload and freeze
https://bugs.kde.org/show_bug.cgi?id=439938 geisserml changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #12 from geisserml --- I think this incident probably was the same cause as Bug 433071. Since I am using LIBGL_ALWAYS_SOFTWARE=1, I haven't had any performance problems with plasma-systemmonitor, and the graphs now also show up again. I recently filed a Qt Bug about my graphics issues in QtQuick apps with OpenGL. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 424024] Main window doesn't repaint correctly on Wayland
https://bugs.kde.org/show_bug.cgi?id=424024 --- Comment #23 from geisserml --- So today kxmlgui got updated to 5.89 in Neon User. Your commit unfortunately does not fix the issue. Please investigate the true cause. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 439478] Menu/tooltip background is transparent
https://bugs.kde.org/show_bug.cgi?id=439478 --- Comment #27 from geisserml --- > The main question is, why are you running Core profile? So apparently there is an OpenGL Core profile and a Compatibility profile. Support for Compatibility profile is optional, and especially some Intel drivers don't support it well. If this is the case, why are you/Qt relying on Compatibility profile if support is not generally available? Could that piece of code be changed to support Core profile and OpenGL <= 4.2? Should I file a bug with Qt? BTW, my GPU is `Mesa DRI Intel® HD Graphics 4000` -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 424024] Main window doesn't repaint correctly on Wayland
https://bugs.kde.org/show_bug.cgi?id=424024 --- Comment #22 from geisserml --- @davidedmundson Repeating the question: Is your supposed fix part of the kxmlgui release that is currently in KDE Neon User? If yes, then it clearly didn't fix the issue. If not, we need to update kxmlgui and then check again. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 446683] Syntax highlighting for property functions is confusing
https://bugs.kde.org/show_bug.cgi?id=446683 --- Comment #1 from geisserml --- Created attachment 144351 --> https://bugs.kde.org/attachment.cgi?id=144351=edit Another example The size attribute of :class:`PIL.Image.Image` is a property, too. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 446683] New: Syntax highlighting for property functions is confusing
https://bugs.kde.org/show_bug.cgi?id=446683
Bug ID: 446683
Summary: Syntax highlighting for property functions is
confusing
Product: kdev-python
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Language support
Assignee: m...@svenbrauch.de
Reporter: geisse...@gmail.com
Target Milestone: ---
Created attachment 144349
--> https://bugs.kde.org/attachment.cgi?id=144349=edit
Code using property functions in KDevelop
SUMMARY
In Python, there is a concept called property functions. Where you would
typically use getter and setter methods in other programming languages, this
can be done with proteries in Python. It basically means that custom code can
be written to handle attribute access and assignment.
Here's a small, theoretical demo:
```python3
import pikepdf
class PdfHandler:
def __init__(self):
self._pdf = None
@property
def pdf(self):
if self._pdf is not None:
return self._pdf
else:
raise ValueError("No input given")
@pdf.setter
def pdf(self, file_or_data):
self._pdf = pikepdf.Pdf.open(file_or_data)
def close(self):
self._pdf.close()
if __name__ == '__main__':
handler = PdfHandler()
handler.pdf = "~/Downloads/Anderes/pdfs/gimp_manual_en.pdf"
del handler.pdf.pages[4:]
handler.pdf.save("./out.pdf")
handler.close()
```
(You can read more about properties here:
https://www.learnbyexample.org/python-properties/)
KDevelop highlights property access like normal functions, which is confusing
because it implies reassigning the function. I think it would make more sense
to highlight properties like normal attributes.
STEPS TO REPRODUCE
1. Paste the above code (or any other code using property functions) into
KDevelop
2. See how the property is highlighted
OBSERVED RESULT
It has the same colour as a function call.
EXPECTED RESULT
It should have the colour of an attribute.
SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.23
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-41-generic (64-bit)
Graphics Platform: Wayland
--
You are receiving this mail because:
You are watching all bug changes.
[lokalize] [Bug 424024] Main window doesn't repaint correctly on Wayland
https://bugs.kde.org/show_bug.cgi?id=424024 geisserml changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 439478] Menu/tooltip background is transparent
https://bugs.kde.org/show_bug.cgi?id=439478 --- Comment #26 from geisserml --- (In reply to Arjen Hiemstra from comment #25) > The main question is, why are you running Core profile? Sorry, what does this mean? > With regards to software rendering, if you're using Mesa the environment > variable is `LIBGL_ALWAYS_SOFTWARE=1`. That works, thanks! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 439478] Menu/tooltip background is transparent
https://bugs.kde.org/show_bug.cgi?id=439478 --- Comment #24 from geisserml --- > I think I can now prove your guess that it's an upstream bug in the graphics > driver: > Running QtQuick apps (e. g. Elisa) with the environment variables > `QT_XCB_FORCE_SOFTWARE_OPENGL=1 QT_QPA_PLATFORM=xcb` fixes the problems. >From looking at the console output, when not using the Software OpenGL flag, there are a lot of warnings about "Problematic vertex shader source code" and messages like "This file is intended for desktop OpenGL version 4.5 or greater". So probably the cause is code written for a newer version of OpenGL than what I have: ``` QOpenGLShader::compile(Vertex): 0:14(10): error: GLSL 4.50 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.40, 1.50, 3.30, 4.00, 4.10, 4.20, 1.00 ES, and 3.00 ES *** Problematic Vertex shader source code *** [...] // This file contains common directives needed for the shaders to work. // It is included as the very first bit in the shader. // Important: If a specific GLSL version is needed, it should be set in this // file. // This file is intended for desktop OpenGL version 4.5 or greater. [...] ``` -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 439478] Menu/tooltip background is transparent
https://bugs.kde.org/show_bug.cgi?id=439478 --- Comment #23 from geisserml --- ... however, this didn't work for kcm_style. There it's still the same problem, despite enforcing software OpenGL, so this will probably have a different cause... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 439478] Menu/tooltip background is transparent
https://bugs.kde.org/show_bug.cgi?id=439478 --- Comment #22 from geisserml --- I think I can now prove your guess that it's an upstream bug in the graphics driver: Running QtQuick apps (e. g. Elisa) with the environment variables `QT_XCB_FORCE_SOFTWARE_OPENGL=1 QT_QPA_PLATFORM=xcb` fixes the problems. (Question: Is there a also Wayland-specific flag to force software OpenGL?) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #21 from geisserml --- @ Vlad Zahorodnii: Any ideas about the purple text background on X that I mentioned in Comment 3? Is this a known bug? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #20 from geisserml --- > Latest snapshot of user edition should contain the fix. Confirmed, thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #18 from geisserml --- I've moved the issue to KDE Neon, as it's caused by Qt packaging rather than by the Overview effect itself. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 geisserml changed: What|Removed |Added CC||j...@jriddell.org, ||neon-b...@kde.org, ||sit...@kde.org Component|effects-overview|Packages User Edition Product|kwin|neon Assignee|kwin-bugs-n...@kde.org |neon-b...@kde.org Version|5.23.3 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #17 from geisserml --- * installed packages I mean installed files, of course. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #16 from geisserml --- Created attachment 143935 --> https://bugs.kde.org/attachment.cgi?id=143935=edit qt5-declarative-dev (list of installed files) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #15 from geisserml --- The thing is that there is no `qt5-declarative` package, only `qt5-declarative-dev` and `qt5-declarative-private-dev`. >From looking at the list of installed packages for `qt5-declarative-dev`, it seems like this package also contains binaries, not only headers. I'll attach the list for you to check. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 446076] New: Wine is not installable
https://bugs.kde.org/show_bug.cgi?id=446076
Bug ID: 446076
Summary: Wine is not installable
Product: neon
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Packages User Edition
Assignee: neon-b...@kde.org
Reporter: geisse...@gmail.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
Target Milestone: ---
SUMMARY
It seems that none of the wine packages are installable - any attempt to
install `wine`, `wine-stable`, `wine64` or `q4wine` cause unresolvable package
conflicts that would lead to the deinstallation of fundamental system
components.
STEPS TO REPRODUCE
1. $ `sudo apt install ` + {wine, wine-stable, wine64, q4wine}
OBSERVED RESULT
None of the mentioned packages can be installed (conflicts).
EXPECTED RESULT
It should be possible to install Wine on KDE Neon.
SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.23
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-40-generic (64-bit)
Graphics Platform: Wayland
ADDITIONAL INFORMATION
While I currently have no direct need for wine, it would be nice if it were
possible to use it in theory.
--
You are receiving this mail because:
You are watching all bug changes.
[markdownpart] [Bug 441541] Comments break preview
https://bugs.kde.org/show_bug.cgi?id=441541 --- Comment #12 from geisserml --- Created attachment 143806 --> https://bugs.kde.org/attachment.cgi?id=143806=edit QOwnNotes Markdown Preview -- You are receiving this mail because: You are watching all bug changes.
[markdownpart] [Bug 441541] Comments break preview
https://bugs.kde.org/show_bug.cgi?id=441541 --- Comment #11 from geisserml --- > You might want to get in contact with other potential developers and heavy > Markdown users > to form some critical mass to get active development here going. I just found out there is a program called QOwnNotes [1], which offers an excellent markdown preview. Maybe it would be possible to work together with the QOwnNotes developers and make that preview generator available to KDE Apps? [1] https://github.com/pbek/QOwnNotes -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 439477] Clicking on links in Qt/KDE apps causes the website to be cached, rather than the link being forwarded to the browser
https://bugs.kde.org/show_bug.cgi?id=439477 geisserml changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #13 from geisserml --- Unfortunately, this bug got back with kf5 updates. It was fixed for some time, but now I have the same problem again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #13 from geisserml --- Is there any way how we can help accelerate getting this fixed in distributions quickly, in particularly KDE Neon? I'm kind of tired to wait until the next regular release cycle for this bug to get resolved, as the next release might introduce similar new bugs in other areas. I know developing reliable software is really hard, but from a user perspective it would sometimes apear nice if KDE had better means of quality control for releases. The bugginess of the system sometimes annoys me a bit. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 424024] Main window doesn't repaint correctly on Wayland
https://bugs.kde.org/show_bug.cgi?id=424024 geisserml changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #20 from geisserml --- (In reply to geisserml from comment #19) > (Software versions: KDE Frameworks 5.88 and kxmlgui 5.87.0+build37 in Neon > User ... however, now I come to think about this, it's really strange that system settings report Frameworks 5.88 and most kf5 package versions have something with 5.88, but libkf5xmlgui5 is still at 5.87 - is this an issue with Neon Packages? Is the fix part of KF5 5.87 already, or not? -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 424024] Main window doesn't repaint correctly on Wayland
https://bugs.kde.org/show_bug.cgi?id=424024 geisserml changed: What|Removed |Added Ever confirmed|1 |0 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #19 from geisserml --- I don't know if there's a misunderstanding, but the commit you referenced is one year old and therefore should already have been released to end users, right? As the obvious visual problems still persist, I believe your commit did not fix the issue. (Software versions: KDE Frameworks 5.88 and kxmlgui 5.87.0+build37 in Neon User) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #12 from geisserml --- (In reply to tgnff242 from comment #11) > It might have been an even older working version on Neon, more split > packages or that you hadn't restarted kwin. > > In any case, it seems to be fixed by an update to qt5-declarative on my end. I did restart kwin (via system reboot), but probably it will be more split packages, as you say. If this is already fixed in newer Qt packages I'm fine with it, hoping they will get released to Neon User at some point. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445641] New: PDF preview does not take CropBox into account
https://bugs.kde.org/show_bug.cgi?id=445641 Bug ID: 445641 Summary: PDF preview does not take CropBox into account Product: dolphin Version: 21.08.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: information Assignee: dolphin-bugs-n...@kde.org Reporter: geisse...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 143659 --> https://bugs.kde.org/attachment.cgi?id=143659=edit PDF with CropBox SUMMARY The preview for PDF documents on the information panel of Dolphin misses to take the /CropBox parameter of PDF documents into account. A CropBox can be used to cut off borders from a PDF page. It is widely used and part of the core PDF standard since the very beginning (cf. PDF RM 1.7, p. 77). While Okular and Gewnview correctly apply CropBox as view area, the Dolphin preview renderer does not. STEPS TO REPRODUCE 1. Go to a folder that contains a PDF where the first page has a CropBox. (You might want to use the attached document.) 2. Focus the file so the first page appears in the preview 3. Open the file with Okular or Gwenview 4. Compare the images OBSERVED RESULT In Dolphin, the PDF is displayed with a border that is not shown in Okular/Gwenview. EXPECTED RESULT The PDF should look the same in Dolphin preview as it does in PDF viewers, i. e. the Dolphin preview should take CropBox into account. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-40-generic (64-bit) Graphics Platform: Wayland Graphics Processor: Mesa DRI Intel® HD Graphics 4000 ADDITIONAL INFORMATION Assuming you are using something Poppler-like to render the PDF, you might have to set a "use cropbox" parameter to true. For pdftoppm, this would be the `-cropbox` flag, for example. I'm not sure how the PDF preview is currently implemented, but maybe you could just use a classical QImage like Gwenview does, instead of an external renderer. The Qt PDF Plugin seems to correctly take CropBox into account. This will require the `qt5-image-formats-plugin-pdf` package to be installed, though. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #10 from geisserml --- So now I managed to roll back both the qtdeclaratives5-dev and the qtdeclaratives5-dev-tools package to the older versions using the following commands: ```bash cd /var/cache/apt/archives sudo dpkg --force-all -i qtdeclarative5-dev-tools_5.15.2+p20.04+tunstable+git2020.0228-0_amd64.deb qtdeclarative5-dev_5.15.2+p20.04+tunstable+git2020.0228-0_amd64.deb ``` However, it's still the same issue anyway... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #9 from geisserml --- > That one and the `qtdeclarative5-dev-tools`. Oh, pardon - I overlooked the "that one and". I'll have to re-test this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #8 from geisserml --- @tgnff242 I rolled back the `qtdeclarative5-dev-tools` package as suggested, but it didn't fix the issue, unfortunately. From looking at the package contents, this would also seem unlikely, since it appears to only contain development utilities that are not used at runtime, as far as I can guess. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #6 from geisserml --- @tgnff242 Thanks for the information. Unfortunately I'm not able to check as I can't easily revert the update. Is the Archlinux `qt5-declarative` package equivalent to `qtdeclarative5-dev` in KDE Neon? -- You are receiving this mail because: You are watching all bug changes.
