[NeoChat] [Bug 492744] New: Room opens on application launch, which on mobile is unwanted behaviour
https://bugs.kde.org/show_bug.cgi?id=492744 Bug ID: 492744 Summary: Room opens on application launch, which on mobile is unwanted behaviour Classification: Applications Product: NeoChat Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: bribb...@disroot.org CC: c...@carlschwan.eu Target Milestone: --- On desktop, opening the last opened room on application launch makes sense, but on mobile this behaviour is unexpected. The opened room shows instead of the room list so the first thing I most of the time do is switch out of the room to choose the room I actually want to open from the room list. So on mobile, the room list should be shown on application launch rather than a room. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 486707] Playing videos on a Pixel 3A fails, failure to open VDPAU backend
https://bugs.kde.org/show_bug.cgi?id=486707
--- Comment #3 from Bart Ribbers ---
It seems this is not actually the cause of the video not playing. If you
disable hardware acceleration by commenting out line 18 in
src/utils/mpvobject.cpp the error disappears, but still no video plays.
A log with that line commented out and failing to play video:
org.kde.plasmatube: Loading source "{24ee1339-b49b-4f42-81f6-c8dd0be1d68b}"
org.kde.plasmatube: Loading source "{bb131e8c-ead5-42ab-9222-3ba6691e6f2a}"
kf.purpose.externalprocess: Cannot initialize model for plugin type "ShareUrl"
with data QJsonObject(): missing key "urls"
qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:401:33: QML Binding: Binding
loop detected for property "value"
qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:344:18: QML ScrollView: Binding
loop detected for property "implicitHeight"
kf.purpose.externalprocess: Cannot initialize model for plugin type "ShareUrl"
with data QJsonObject(): missing key "urls"
kf.purpose.externalprocess: Cannot initialize model for plugin type "ShareUrl"
with data QJsonObject(): missing key "urls"
qrc:/qt/qml/org/kde/plasmatube/ui/TrendingPage.qml:10:1: QML TrendingPage:
Created graphical object was not placed in the graphics scene.
Not trying to load comments for an empty video id.
[file] Cannot open file '': No such file or directory
Failed to open .
qrc:/qt/qml/org/kde/plasmatube/ui/components/VideoListItem.qml:57:9: QML
QQuickImage: Cannot open:
qrc:/qt/qml/org/kde/plasmatube/ui/components/api.youtube.fam-ribbers.com
--
You are receiving this mail because:
You are watching all bug changes.
[Powerdevil] [Bug 477152] Other monitor (via other input) dims while not actively connected in a multi system multi monitor set-up.
https://bugs.kde.org/show_bug.cgi?id=477152 --- Comment #2 from Bart C --- (In reply to Jakob Petsovits from comment #1) > This should be fixed with Plasma 6.2 on Wayland, because on Wayland we > provide hardware brightness controls to KWin and then ask KWin to change > brightness only for enabled screens. Thereby ignoring other hardware > brightness controls that don't belong to an enabled KWin screen. > > I don't currently have the hardware at hand to confirm that this is indeed > fixed now, so let's leave this open until I or someone else can retest. > > It may be possible to fix this also for X11, but would require additional > work and is not high up on my priority list. Thank you for reminding me of this one - as I turned off the dimming after x time so not seeing this behavior and upgrading to KDE 6 I kind of forgot this one. I'm currently on the software mentioned below (hardware hasn't changed except for the dock due to changing employer) and unfortunately I still see this behavior. Operating System: Arch Linux KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.6-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-4590 CPU @ 3.30GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B85M-HD3 ADDITIONAL INFORMATION * Docking station Dell UD22 -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 492031] New: Opening the notification panel hangs the application
https://bugs.kde.org/show_bug.cgi?id=492031 Bug ID: 492031 Summary: Opening the notification panel hangs the application Classification: Applications Product: Tokodon Version: 24.07.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bribb...@disroot.org CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- This happens on git master for me but not on 24.05.2. An error appears in the console: qrc:/qt/qml/org/kde/tokodon/content/ui/NotificationPage.qml:127:9: QML Connections: Detected function "onPostSourceReady" in Connections element. This is probably intended to be a signal handler but no signal of the target matches the name. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 492030] New: Sidebar opens on application start
https://bugs.kde.org/show_bug.cgi?id=492030 Bug ID: 492030 Summary: Sidebar opens on application start Classification: Applications Product: Tokodon Version: 24.07.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bribb...@disroot.org CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- The first thing that happens when the application opens is the sidebar opening. First thing I do is closing it because I just want to see the feed, not click any buttons in the sidebar. This happens on mobile of course. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 491930] New: When adding a second account the "Welcome to Tokodon" page is shown over other pages rather than replacing them
https://bugs.kde.org/show_bug.cgi?id=491930 Bug ID: 491930 Summary: When adding a second account the "Welcome to Tokodon" page is shown over other pages rather than replacing them Classification: Applications Product: Tokodon Version: 24.07.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bribb...@disroot.org CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- This means that when you select any sidebar option the view doesn't change until you press the back button on the welcome page. This makes it feel like nothing happens at all besides closing the sidebar when you click a menu option. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 491929] New: Sidebar doesn't close when clicking "Add account"
https://bugs.kde.org/show_bug.cgi?id=491929 Bug ID: 491929 Summary: Sidebar doesn't close when clicking "Add account" Classification: Applications Product: Tokodon Version: 24.07.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bribb...@disroot.org CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- On mobile this is annoying because you first have to manually close the sidebar before you can interact with the just opened page. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 491928] New: Can not add second account, login and register pages don't open
https://bugs.kde.org/show_bug.cgi?id=491928 Bug ID: 491928 Summary: Can not add second account, login and register pages don't open Classification: Applications Product: Tokodon Version: 24.07.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bribb...@disroot.org CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- I'm currently running Tokodon on Plasma Mobile and I'm trying to add a second account. However although the "Welcome to Tokodon" page opens just fine, the "Register" and "Login" buttons don't appear to do anything. When Tokodon is opened through the console some errors pop up. Login page: qrc:/qt/qml/org/kde/tokodon/content/ui/LoginFlow/LoginPage.qml:15:1: QML LoginPage: Created graphical object was not placed in the graphics scene. Register page: qrc:/qt/qml/org/kde/tokodon/content/ui/LoginFlow/ServersPage.qml:15:1: QML ServersPage: Created graphical object was not placed in the graphics scene. This is using git master compiled on the 18th of August. -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 491920] New: Kamoso crashes when the camera is inaccessible
https://bugs.kde.org/show_bug.cgi?id=491920 Bug ID: 491920 Summary: Kamoso crashes when the camera is inaccessible Classification: Applications Product: kamoso Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: bribb...@disroot.org Target Milestone: --- Currently on the Google Pixel 3A work is in progress to make the camera work. Currently it works but only once per boot. Kamoso will show a picture briefly after which it crashes while for example GNOME's Snapshot shows an image for the entire time the application is open (until the user closes and restarts it). When it crashes the following error is thrown: $ kamoso kf.kirigami: Failed to find a Kirigami platform plugin error debugMessage: stream error: error set output format: -22 (Invalid argument) error: "../src/gst/gstpipewiresrc.c(704): on_state_changed (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:/GstPipeWireSrc:Built-in Front Camera" Stop (kamoso:4067): GLib-GObject-CRITICAL **: 22:19:49.651: g_object_notify: assertion 'G_IS_OBJECT (object)' failed error debugMessage: stream error: error set output format: -22 (Invalid argument) error: "../src/gst/gstpipewiresrc.c(704): on_state_changed (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:/GstPipeWireSrc:Built-in Front Camera" Stop (kamoso:4067): GLib-GObject-CRITICAL **: 22:19:50.108: g_object_notify: assertion 'G_IS_OBJECT (object)' failed (kamoso:4067): GLib-GObject-CRITICAL **: 22:19:50.108: g_object_notify: assertion 'G_IS_OBJECT (object)' failed error debugMessage: stream error: error set output format: -22 (Invalid argument) error: "../src/gst/gstpipewiresrc.c(704): on_state_changed (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:/GstPipeWireSrc:Built-in Front Camera" Stop Segmentation fault I understand not being able to show a camera image when this happens but the application should at least not crash and show an error instead. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417227] No keyboard shortcuts work on Wayland when using musl instead of glibc
https://bugs.kde.org/show_bug.cgi?id=417227 Bart Ribbers changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #22 from Bart Ribbers --- Seems it has been resolved with the upgrade to Plasma 6.0 actually. I got rid of the workaround that removes the capabilities altogether a while ago. Closing! -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 491156] New: Adding a new account makes NeoChat prompt to join a room but only shows the internal room room ID
https://bugs.kde.org/show_bug.cgi?id=491156 Bug ID: 491156 Summary: Adding a new account makes NeoChat prompt to join a room but only shows the internal room room ID Classification: Applications Product: NeoChat Version: 24.05.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: bribb...@disroot.org CC: c...@carlschwan.eu Target Milestone: --- Created attachment 172201 --> https://bugs.kde.org/attachment.cgi?id=172201&action=edit NeoChat with a newly added account prompting to join rooms but only showing the internal room ID I recently tombstoned some rooms and made replacements for them. It seems NeoChat doesn't like logging into accounts having joined such rooms very much as on adding the account it prompts to join those rooms but only shows the internal room ID's. I figured out which rooms they are from a different client and account and they all appear to be tombstoned/replaced rooms, but it doesn't seem to prompt for all of those rooms either so I'm not sure what makes it prompt for these ones. It's good to note that for these particular rooms I'm not actually in them, I'm only in their replacements. Due to a fuck up while managing my infrastructure I'm unable to join those rooms either (not a NeoChat bug). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482362] Mouse cursor is invisible in Qemu unless KWIN_FORCE_SW_CURSOR=1 is specified
https://bugs.kde.org/show_bug.cgi?id=482362 Bart Ribbers changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #14 from Bart Ribbers --- Uh I did give info, changing the status back to REPORTED. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 490468] New: No video load using the Piped backend: "[file] Cannot open file '': No such file or directory"
https://bugs.kde.org/show_bug.cgi?id=490468 Bug ID: 490468 Summary: No video load using the Piped backend: "[file] Cannot open file '': No such file or directory" Classification: Applications Product: PlasmaTube Version: 24.04.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- With Plasmatube built from git master today no videos load using the Piped backend. In the console I see "[file] Cannot open file '': No such file or directory" whenever I click on any video. Interestingly enough 24.05.0 on my desktop using the same Piped backend and instance loads the video just fine (but then I get https://bugs.kde.org/show_bug.cgi?id=486707 preventing me from playing the video but that's a separate problem). -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 490407] New: The notifications window constantly switches label between "No notifications" and "Loading..."
https://bugs.kde.org/show_bug.cgi?id=490407 Bug ID: 490407 Summary: The notifications window constantly switches label between "No notifications" and "Loading..." Classification: Applications Product: NeoChat Version: 24.05.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: bribb...@disroot.org CC: c...@carlschwan.eu Target Milestone: --- Basically multiple times a second, but not so quick I can't read what it says. I guess it tries to load notifications, loads none and because of that instantly tries to load notifications again. This is then causing an infinite loop and the label changes along. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdoctools] [Bug 490390] Since Qt6.7 doc generation on 32-bit architectures fail
https://bugs.kde.org/show_bug.cgi?id=490390 --- Comment #4 from Bart Ribbers --- On 17-07-2024 10:55, Luigi Toscano wrote: > https://bugs.kde.org/show_bug.cgi?id=490390 > > --- Comment #3 from Luigi Toscano --- > Try to reproduce the failed build, for example any command like: > > cd > /home/buildozer/aports/community/kde-cli-tools/src/kde-cli-tools-6.1.3/build/doc/kdesu > && /usr/bin/meinproc6 --stylesheet > /usr/share/kf6/kdoctools/customization/kde-include-man.xsl --check > /home/buildozer/aports/community/kde-cli-tools/src/kde-cli-tools-6.1.3/doc/kdesu/man-kdesu.1.docbook Running the command manually (outside of CMake) as you specified, with adjusted paths and `doc/kdesu/man-kdesu.1.docbook` as target, succeeded. So the input doesn't seem to matter specifically. > Bonus point for running meinproc6 command under gdb and getting a stacktrace: > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports gdb is sadly going to be impossible. I don't have access to an armv7 or x86 machine and am running this through non-interactive packaging tools which use qemu to get the right architecture. The distribution builders that eventually build these packages run on native arches though and are failing in the same way. I've ran it with Make instead and got the following: [ 1%] Generating po/de/docs/kcontrol6/filetypes/index.cache.bz2 [ 1%] Generating po/de/docs/kdesu/kdesu.1 qemu: uncaught target signal 4 (Illegal instruction) - core dumped [ 2%] Generating po/ca/docs/kcontrol6/filetypes/index.cache.bz2 gmake[2]: *** [CMakeFiles/po-de-docs-kcontrol6-filetypes-index-cache-bz2.dir/build.make:74: po/de/docs/kcontrol6/filetypes/index.cache.bz2] Illegal instruction [ 4%] Generating po/ca/docs/kdesu/index.cache.bz2 [ 4%] Generating po/es/docs/kdesu/index.cache.bz2 [ 5%] Generating po/de/docs/kdesu/index.cache.bz2 gmake[1]: *** [CMakeFiles/Makefile2:1202: CMakeFiles/po-de-docs-kcontrol6-filetypes-index-cache-bz2.dir/all] Error 2nv gmake[1]: *** Waiting for unfinished jobs [ 6%] Generating po/es/docs/kcontrol6/filetypes/index.cache.bz2 qemu: uncaught target signal 4 (Illegal instruction) - core dumped gmake[2]: *** [CMakeFiles/po-de-docs-kdesu-kdesu-1.dir/build.make:74: po/de/docs/kdesu/kdesu.1] Illegal instruction gmake[1]: *** [CMakeFiles/Makefile2:1254: CMakeFiles/po-de-docs-kdesu-kdesu-1.dir/all] Error 2 [ 6%] Generating po/ca/docs/kdesu/kdesu.1 qemu: uncaught target signal 4 (Illegal instruction) - core dumped gmake[2]: *** [CMakeFiles/po-ca-docs-kdesu-index-cache-bz2.dir/build.make:74: po/ca/docs/kdesu/index.cache.bz2] Illegal instruction gmake[1]: *** [CMakeFiles/Makefile2:1150: CMakeFiles/po-ca-docs-kdesu-index-cache-bz2.dir/all] Error 2 qemu: uncaught target signal 4 (Illegal instruction) - core dumped gmake[2]: *** [CMakeFiles/po-ca-docs-kcontrol6-filetypes-index-cache-bz2.dir/build.make:74: po/ca/docs/kcontrol6/filetypes/index.cache.bz2] Illegal instruction gmake[1]: *** [CMakeFiles/Makefile2:1124: CMakeFiles/po-ca-docs-kcontrol6-filetypes-index-cache-bz2.dir/all] Error 2 qemu: uncaught target signal 4 (Illegal instruction) - core dumped qemu: uncaught target signal 4 (Illegal instruction) - core dumped gmake[2]: *** [CMakeFiles/po-es-docs-kcontrol6-filetypes-index-cache-bz2.dir/build.make:74: po/es/docs/kcontrol6/filetypes/index.cache.bz2] Illegal instruction gmake[1]: *** [CMakeFiles/Makefile2:1280: CMakeFiles/po-es-docs-kcontrol6-filetypes-index-cache-bz2.dir/all] Error 2 gmake[2]: *** [CMakeFiles/po-de-docs-kdesu-index-cache-bz2.dir/build.make:74: po/de/docs/kdesu/index.cache.bz2] Illegal instruction gmake[1]: *** [CMakeFiles/Makefile2:1228: CMakeFiles/po-de-docs-kdesu-index-cache-bz2.dir/all] Error 2 qemu: uncaught target signal 4 (Illegal instruction) - core dumped gmake[2]: *** [CMakeFiles/po-es-docs-kdesu-index-cache-bz2.dir/build.make:74: po/es/docs/kdesu/index.cache.bz2] Illegal instruction gmake[1]: *** [CMakeFiles/Makefile2:1306: CMakeFiles/po-es-docs-kdesu-index-cache-bz2.dir/all] Error 2 qemu: uncaught target signal 4 (Illegal instruction) - core dumped gmake[2]: *** [CMakeFiles/po-ca-docs-kdesu-kdesu-1.dir/build.make:74: po/ca/docs/kdesu/kdesu.1] Illegal instruction gmake[1]: *** [CMakeFiles/Makefile2:1176: CMakeFiles/po-ca-docs-kdesu-kdesu-1.dir/all] Error 2 gmake: *** [Makefile:146: all] Error 2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdoctools] [Bug 490390] Since Qt6.7 doc generation on 32-bit architectures fail
https://bugs.kde.org/show_bug.cgi?id=490390 --- Comment #2 from Bart Ribbers --- I can do that. What would be the exact arguments to run meinproc6 with? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdoctools] [Bug 490390] New: Since Qt6.7 doc generation on 32-bit architectures fail
https://bugs.kde.org/show_bug.cgi?id=490390 Bug ID: 490390 Summary: Since Qt6.7 doc generation on 32-bit architectures fail Classification: Frameworks and Libraries Product: frameworks-kdoctools Version: 6.4.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: bribb...@disroot.org CC: kdelibs-b...@kde.org Target Milestone: --- Since the Qt6.7 upgrade (from 6.6) generation of docs using kdoctools has been failing for several packages on 32-bit architectures, I see it occur on armv7 and x86. 64-bit architectures seem to be fine. Strangely enough it seems to generate part of the docs just fine. [20/137] Generating po/uk/docs/kdesu/kdesu.1 [21/137] Generating po/uk/docs/kdesu/index.cache.bz2 [22/137] Generating po/uk/docs/kcontrol6/filetypes/index.cache.bz2 [23/137] Generating po/tr/docs/kdesu/kdesu.1 [24/137] Generating po/tr/docs/kdesu/index.cache.bz2 [25/137] Generating po/tr/docs/kcontrol6/filetypes/index.cache.bz2 [26/137] Generating po/sv/docs/kdesu/kdesu.1 [27/137] Generating po/sv/docs/kdesu/index.cache.bz2 [28/137] Generating po/sv/docs/kcontrol6/filetypes/index.cache.bz2 [29/137] Generating po/sr@latin/docs/kdesu/kdesu.1 [30/137] Generating po/sr@latin/docs/kdesu/index.cache.bz2 [31/137] Generating po/sr@latin/docs/kcontrol6/filetypes/index.cache.bz2 [32/137] Generating po/sr/docs/kdesu/kdesu.1 [33/137] Generating po/sr/docs/kdesu/index.cache.bz2 [34/137] Generating po/sr/docs/kcontrol6/filetypes/index.cache.bz2 [35/137] Generating po/ru/docs/kdesu/kdesu.1 [36/137] Generating po/ru/docs/kdesu/index.cache.bz2 [37/137] Generating po/ru/docs/kcontrol6/filetypes/index.cache.bz2 [38/137] Generating po/pt_BR/docs/kdesu/kdesu.1 [39/137] Generating po/pt_BR/docs/kdesu/index.cache.bz2 [40/137] Generating po/pt_BR/docs/kcontrol6/filetypes/index.cache.bz2 [41/137] Generating po/pt/docs/kdesu/kdesu.1 [42/137] Generating po/pt/docs/kdesu/index.cache.bz2 [43/137] Generating po/pt/docs/kcontrol6/filetypes/index.cache.bz2 [44/137] Generating po/nl/docs/kdesu/kdesu.1 [45/137] Generating po/nl/docs/kdesu/index.cache.bz2 [46/137] Generating po/nl/docs/kcontrol6/filetypes/index.cache.bz2 [47/137] Generating po/nb/docs/kdesu/kdesu.1 [48/137] Generating po/it/docs/kdesu/kdesu.1 [49/137] Generating po/it/docs/kdesu/index.cache.bz2 [50/137] Generating po/it/docs/kcontrol6/filetypes/index.cache.bz2 [51/137] Generating po/id/docs/kdesu/kdesu.1 [52/137] Generating po/id/docs/kdesu/index.cache.bz2 [53/137] Generating po/id/docs/kcontrol6/filetypes/index.cache.bz2 [54/137] Generating po/fr/docs/kdesu/kdesu.1 [55/137] Generating po/fr/docs/kdesu/index.cache.bz2 [56/137] Generating po/fr/docs/kcontrol6/filetypes/index.cache.bz2 [57/137] Generating po/et/docs/kdesu/kdesu.1 [58/137] Generating po/et/docs/kdesu/index.cache.bz2 [59/137] Generating po/es/docs/kdesu/kdesu.1 [60/137] Generating po/es/docs/kdesu/index.cache.bz2 [61/137] Generating po/es/docs/kcontrol6/filetypes/index.cache.bz2 [62/137] Generating po/de/docs/kdesu/kdesu.1 [63/137] Generating po/de/docs/kdesu/index.cache.bz2 [64/137] Generating po/de/docs/kcontrol6/filetypes/index.cache.bz2 [65/137] Generating po/ca/docs/kdesu/kdesu.1 [66/137] Generating po/ca/docs/kdesu/index.cache.bz2 [67/137] Generating po/ca/docs/kcontrol6/filetypes/index.cache.bz2 ninja: job terminated due to signal 4: cd /home/buildozer/aports/community/kde-cli-tools/src/kde-cli-tools-6.1.3/build/doc/kdesu && /usr/bin/meinproc6 --stylesheet /usr/share/kf6/kdoctools/customization/kde-include-man.xsl --check /home/buildozer/aports/community/kde-cli-tools/src/kde-cli-tools-6.1.3/doc/kdesu/man-kdesu.1.docbook ninja: job terminated due to signal 4: cd /home/buildozer/aports/community/kde-cli-tools/src/kde-cli-tools-6.1.3/doc/kdesu && /usr/bin/meinproc6 --check --cache /home/buildozer/aports/community/kde-cli-tools/src/kde-cli-tools-6.1.3/build/doc/kdesu//index.cache.bz2 index.docbook ninja: job terminated due to signal 4: cd /home/buildozer/aports/community/kde-cli-tools/src/kde-cli-tools-6.1.3/doc/kcontrol6/filetypes && /usr/bin/meinproc6 --check --cache /home/buildozer/aports/community/kde-cli-tools/src/kde-cli-tools-6.1.3/build/doc/kcontrol6/filetypes//index.cache.bz2 index.docbook ninja: job terminated due to signal 4: cd /home/buildozer/aports/community/kde-cli-tools/src/kde-cli-tools-6.1.3/build/po/uk/docs/kdesu && /usr/bin/meinproc6 --stylesheet /usr/share/kf6/kdoctools/customization/kde-include-man.xsl --check /home/buildozer/aports/community/kde-cli-tools/src/kde-cli-tools-6.1.3/po/uk/docs/kdesu/man-kdesu.1.docbook ninja: job terminated due to signal 4: cd /home/buildozer/aports/community/kde-cli-tools/src/kde-cli-tools-6.1.3 && /usr/bin/meinproc6 --check --cache /home/buildozer/aports/community/kde-cli-tools/src/kde-cli-tools-6.1.3/build/
[kwin] [Bug 482362] Mouse cursor is invisible in Qemu unless KWIN_FORCE_SW_CURSOR=1 is specified
https://bugs.kde.org/show_bug.cgi?id=482362 --- Comment #12 from Bart Ribbers --- Sadly it does not no -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482362] Mouse cursor is invisible in Qemu unless KWIN_FORCE_SW_CURSOR=1 is specified
https://bugs.kde.org/show_bug.cgi?id=482362 Bart Ribbers changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #10 from Bart Ribbers --- Oh sorry. Kernel 6.6.39 at the moment, KWIN_DRM_NO_AMS=0 doesn't change anything. Since reporting I upgraded to Plasma 6.1.2 but it still happens. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482362] Mouse cursor is invisible in Qemu unless KWIN_FORCE_SW_CURSOR=1 is specified
https://bugs.kde.org/show_bug.cgi?id=482362 Bart Ribbers changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #7 from Bart Ribbers --- Nope, still an issue on 6.0.5 sadly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487979] Enabling HDR causes entire display to have a green tint
https://bugs.kde.org/show_bug.cgi?id=487979 --- Comment #3 from Bart Ribbers --- 6.6.32, latest LTS. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487979] Enabling HDR causes entire display to have a green tint
https://bugs.kde.org/show_bug.cgi?id=487979 --- Comment #1 from Bart Ribbers --- Ah forgot to enable but obviously relevant, the GPU is an AMD GPU, RX580, using Mesa 24.1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487979] Enabling HDR causes entire display to have a green tint
https://bugs.kde.org/show_bug.cgi?id=487979 Bart Ribbers changed: What|Removed |Added Version|5.24.90 |6.0.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487979] New: Enabling HDR causes entire display to have a green tint
https://bugs.kde.org/show_bug.cgi?id=487979 Bug ID: 487979 Summary: Enabling HDR causes entire display to have a green tint Classification: Plasma Product: kwin Version: 5.24.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: colour-management Assignee: kwin-bugs-n...@kde.org Reporter: bribb...@disroot.org Target Milestone: --- Created attachment 170103 --> https://bugs.kde.org/attachment.cgi?id=170103&action=edit Picture of a HDR-enabled TV showing a green tint SUMMARY My TV has HDR support so I enabled it in plasma settings, however doing that causes the complete display to show a green tint over everything. STEPS TO REPRODUCE 1. Enable HDR OBSERVED RESULT The display is tinted entirely green EXPECTED RESULT The display to show as normal until HDR content is being shown SOFTWARE/OS VERSIONS Linux/KDE Plasma: Alpine Linux edge KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.6.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481113] When not using Systemd or Plasma's Systemd session launch integration, changes to pinned apps are not saved when Plasmashell quits
https://bugs.kde.org/show_bug.cgi?id=481113 Bart Ribbers changed: What|Removed |Added CC||bribb...@disroot.org --- Comment #49 from Bart Ribbers --- I can currently reproduce this on Alpine Linux using Plasma 6.0.5 with KDE Frameworks 6.2.0, but only on one of 3 machines (a new laptop). My desktop and previous laptop have been upgraded from Plasma 5 before and do not experience this issue, but my new laptop that has only ever had Plasma 6 resets on every login. No systemd, just OpenRC. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 485207] Error while trying to create calendar item. Error was: Invalid parent collection
https://bugs.kde.org/show_bug.cgi?id=485207 Bart Ribbers changed: What|Removed |Added CC||bribb...@disroot.org --- Comment #6 from Bart Ribbers --- This seems to be the same as https://bugs.kde.org/show_bug.cgi?id=485070 and https://bugs.kde.org/show_bug.cgi?id=470517 I can reproduce when adding calendar entries for a NextCloud (Caldav) source. -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 485070] Unable to create new event with a Google account: invalid parent collection
https://bugs.kde.org/show_bug.cgi?id=485070 Bart Ribbers changed: What|Removed |Added CC||bribb...@disroot.org --- Comment #3 from Bart Ribbers --- This seems to be the same as https://bugs.kde.org/show_bug.cgi?id=470517 and https://bugs.kde.org/show_bug.cgi?id=485207 I can reproduce when adding calendar entries for a NextCloud (Caldav) source. -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 470517] Unable to create new contact: invalid parent collection
https://bugs.kde.org/show_bug.cgi?id=470517 Bart Ribbers changed: What|Removed |Added CC||bribb...@disroot.org --- Comment #3 from Bart Ribbers --- This seems to be the same as https://bugs.kde.org/show_bug.cgi?id=485070 and https://bugs.kde.org/show_bug.cgi?id=485207 I can reproduce when adding calendar entries for a NextCloud (Caldav) source. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 487472] New: Context menu for messages send by the user themselves empties itself when hovered over
https://bugs.kde.org/show_bug.cgi?id=487472 Bug ID: 487472 Summary: Context menu for messages send by the user themselves empties itself when hovered over Classification: Applications Product: NeoChat Version: 24.05.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: bribb...@disroot.org CC: c...@carlschwan.eu Target Milestone: --- Created attachment 169768 --> https://bugs.kde.org/attachment.cgi?id=169768&action=edit NeoChat with the broken context menu open When this happens the menu entries are moved to the message itself, shown as is done on messages send by others. The context menu is left empty but still shown, thus shows as a few pixels high empty box. See the attached screenshot for more details. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 486710] New: Subscriptions, Playlists and History pages don't open
https://bugs.kde.org/show_bug.cgi?id=486710 Bug ID: 486710 Summary: Subscriptions, Playlists and History pages don't open Classification: Applications Product: PlasmaTube Version: 24.04.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- The left sidebar contains options to open the Subscriptions, Playlists and History pages. However clicking these don't actually do anything. This happens using PlasmaTube compiled from git master yesterday. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 486708] New: Video thumbnails fail to load from a Piped backend
https://bugs.kde.org/show_bug.cgi?id=486708 Bug ID: 486708 Summary: Video thumbnails fail to load from a Piped backend Classification: Applications Product: PlasmaTube Version: 24.01.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- We actually had this problem earlier and resolved it at the time, not sure why it came back. Any video thumbnails fail to load completely, showing just a placeholder instead. The console reports the same error for each thumbnail, an example: qrc:/qt/qml/org/kde/plasmatube/ui/components/VideoListItem.qml:53:9: QML QQuickImage: Error decoding: https://proxy.youtube.fam-ribbers.com/vi/NPqDIwWMtxg/hqdefault.jpg?host=i.ytimg.com&rs=AOn4CLDE4s7_-YKbJqQ2HxLu0lg8ap1hIg&sqp=-oaymwEcCNACELwBSFXyq4qpAw4IARUAAIhCGAFwAcABBg%3D%3D: Unsupported image format That image loads just fine in a browser however. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 486707] New: Playing videos on a Pixel 3A fails, failure to open VDPAU backend
https://bugs.kde.org/show_bug.cgi?id=486707 Bug ID: 486707 Summary: Playing videos on a Pixel 3A fails, failure to open VDPAU backend Classification: Applications Product: PlasmaTube Version: 24.01.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- I'm using Plasmatube on a Pixel 3A running postmarketOS with Plasma Mobile on a 6.8 kernel. It is however currently unable to play any video. A separate window opens up showing the first frame of a video but it's frozen (no playback controls). In the console the following is logged: Failed to open VDPAU backend Error loading shared library libvdpau_nvidia.so: No such file or directory [ffmpeg] AVHWDeviceContext: VDPAU device creation on X11 display :0 failed. Failed to open VDPAU backend Error loading shared library libvdpau_nvidia.so: No such file or directory [ffmpeg] AVHWDeviceContext: VDPAU device creation on X11 display :0 failed. This device uses an Adreno GPU with Mesa's Freedreno, so I'm unsure why it's trying to get a NVIDIA library in the first place. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 486706] New: Button to open the left sidebar appears over UI elements on the settings tab blocking the pressing of various UI elements
https://bugs.kde.org/show_bug.cgi?id=486706 Bug ID: 486706 Summary: Button to open the left sidebar appears over UI elements on the settings tab blocking the pressing of various UI elements Classification: Applications Product: PlasmaTube Version: 24.01.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- Created attachment 169260 --> https://bugs.kde.org/attachment.cgi?id=169260&action=edit Screenshot of the settings page See the screenshot. The button appears over the search bar making me unable to click on the left corner of the input field to focus it. It's not much of a problem there, it's wide enough to just click to the right of it, but it's blocking the "go back" button on any deeper page. -- You are receiving this mail because: You are watching all bug changes.
[angelfish] [Bug 486463] Opening a link in a new tab automatically and unexpectedly switches you to that tab and show a popup largely blocking the tab switcher button to switch back
https://bugs.kde.org/show_bug.cgi?id=486463 Bart Ribbers changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #2 from Bart Ribbers --- Oh you're right, there is. Well then I'd say that settings needs to by off by default, because it's the opposite of every other browser really. And the issue remains that it shows a popup telling you that the tab was opened, even though you just switched to it and already know. And it's blocking the bottom bar, it should really be placed above it if it's going to be shown at all. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 486546] New: Confirmation should be asked before leaving a room
https://bugs.kde.org/show_bug.cgi?id=486546 Bug ID: 486546 Summary: Confirmation should be asked before leaving a room Classification: Applications Product: NeoChat Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: bribb...@disroot.org CC: c...@carlschwan.eu Target Milestone: --- Because of https://bugs.kde.org/show_bug.cgi?id=486545 I accidentally left a room. Besides that the menu shouldn't have been open in the first place, NeoChat should really have asked for confirmation because the action is quite destructive. This was a private room which I could not just rejoin without an invite so now I had to bother others to ask them to invite me again. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 486545] New: Opening a room on Plasma Mobile will also activate the room actions menu
https://bugs.kde.org/show_bug.cgi?id=486545 Bug ID: 486545 Summary: Opening a room on Plasma Mobile will also activate the room actions menu Classification: Applications Product: NeoChat Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: bribb...@disroot.org CC: c...@carlschwan.eu Target Milestone: --- The actions menu containing actions like "mark room as read" or "leave the room". So to do anything in the room that was just opened you first have to click that room away which is annoying. In fact I accidentally left a room because of it because I immediately tried to click on the message bar to start typing a message but because of the action menu being there I left the room instead. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 486521] New: Clicking on an entry on the account switcher on Plasma Mobile will switch pages on the background but not remove the account switcher popup
https://bugs.kde.org/show_bug.cgi?id=486521 Bug ID: 486521 Summary: Clicking on an entry on the account switcher on Plasma Mobile will switch pages on the background but not remove the account switcher popup Classification: Applications Product: NeoChat Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: bribb...@disroot.org CC: c...@carlschwan.eu Target Milestone: --- You still have to click away the account switcher to actually fully see and use the page it switched too in the background. -- You are receiving this mail because: You are watching all bug changes.
[angelfish] [Bug 486463] New: Opening a link in a new tab automatically and unexpectedly switches you to that tab and show a popup largely blocking the tab switcher button to switch back
https://bugs.kde.org/show_bug.cgi?id=486463 Bug ID: 486463 Summary: Opening a link in a new tab automatically and unexpectedly switches you to that tab and show a popup largely blocking the tab switcher button to switch back Classification: Applications Product: angelfish Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: j...@kaidan.im Reporter: bribb...@disroot.org Target Milestone: --- When you hold any link a context menu will popup with an option to open the link in a new tab. Clicking that option then immediately moves you to that just opened tab. This was very unexpected for me, no other browser I ever used does this, and I'd like it to stay in the current active tab until I tell Angelfish to switch. So when I want to switch back immediately this is made harder by the fact that a little snackbar message pops up saying the tab was opened (this whole message seems unnecessary to me, especially when you're already switched to the tab) blocking the clicking on the address bar or even the tab switcher. I'd like to have it first of all not switch me automatically to the new tab and secondly not show the snackbar message as it's unnecessary and relaying information you already have as a user. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 485081] New: Clicking on the timeline next to a post on empty space opens the post next to the click
https://bugs.kde.org/show_bug.cgi?id=485081 Bug ID: 485081 Summary: Clicking on the timeline next to a post on empty space opens the post next to the click Classification: Applications Product: Tokodon Version: 24.02.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bribb...@disroot.org CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- SUMMARY When clicking the empty space between a post and the border of the window (or side panel on the left side) when on the timeline view opens the post next to where is clicked. This is unexpected and really threw me off a few times when I just tried to focus the window by clicking on the empty space. STEPS TO REPRODUCE 1. Open the timeline view 2. Click next to a post, on the empty space of the page OBSERVED RESULT The post next to the click is opened EXPECTED RESULT Nothing to happen, the user didn't click on a post to open. SOFTWARE/OS VERSIONS Linux: Alpine Linux edge KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 485080] New: Pasting a fediverse link into the search box on the left side panel doesn't load the post
https://bugs.kde.org/show_bug.cgi?id=485080 Bug ID: 485080 Summary: Pasting a fediverse link into the search box on the left side panel doesn't load the post Classification: Applications Product: Tokodon Version: 24.02.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bribb...@disroot.org CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- SUMMARY I'd like to be able to copy any fediverse URL to a post and paste it in the search field in Tokodon to make it load that post through my instance. This is something the default Mastodon web interface supports and from what I hear also something Tokodon is supposed to support but it seems to be broken at the moment. STEPS TO REPRODUCE 1. Copy the URL to any fediverse post, for example https://ma.fellr.net/@fell/112217662940193667 2. Paste it in the search field in Tokodon 3. Press enter to make it "search" OBSERVED RESULT It reports "No search results" EXPECTED RESULT The post to be loaded into the main view after my server has retrieved it SOFTWARE/OS VERSIONS Linux: Alpine Linux edge KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482362] Mouse cursor is invisible in Qemu unless KWIN_FORCE_SW_CURSOR=1 is specified
https://bugs.kde.org/show_bug.cgi?id=482362 Bart Ribbers changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED --- Comment #5 from Bart Ribbers --- Uh, I did provide info... -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 483250] New: Indicate if there are any unread messages in rooms that belong to one or more spaces
https://bugs.kde.org/show_bug.cgi?id=483250 Bug ID: 483250 Summary: Indicate if there are any unread messages in rooms that belong to one or more spaces Classification: Applications Product: NeoChat Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: bribb...@disroot.org CC: c...@carlschwan.eu Target Milestone: --- I use my spaces to organize the rooms but when I have 1 space active I do not know if there are any new messages in rooms in other spaces. It would be great if a space could be marked as read or unread so I know a non-active space has rooms with messages to read. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482362] Mouse cursor is invisible in Qemu unless KWIN_FORCE_SW_CURSOR=1 is specified
https://bugs.kde.org/show_bug.cgi?id=482362 --- Comment #2 from Bart Ribbers --- Created attachment 166381 --> https://bugs.kde.org/attachment.cgi?id=166381&action=edit wayland-session log from SDDM I'm not sure where to get KWin logs from, so I'll just upload the entire Wayland session log from SDDM, I hope that's enough. This is with the env variable applied, do you need it without it as well? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482362] New: Mouse cursor is invisible in Qemu unless KWIN_FORCE_SW_CURSOR=1 is specified
https://bugs.kde.org/show_bug.cgi?id=482362 Bug ID: 482362 Summary: Mouse cursor is invisible in Qemu unless KWIN_FORCE_SW_CURSOR=1 is specified Classification: Plasma Product: kwin Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: bribb...@disroot.org Target Milestone: --- SUMMARY I've just upgraded my VM on a Macbook M3 to run Plasma 6 and now the mouse cursor is invisible. Unless I set KWIN_FORCE_SW_CURSOR=1 (which makes it show up) it's impossible to use the mouse for anything. This wasn't a problem with Plasma 5.x.y, zo this is a regression. STEPS TO REPRODUCE 1. Install Plasma 6 in a Qemu VM OBSERVED RESULT No mouse cursor is shown EXPECTED RESULT Mouse cursor to be shown SOFTWARE/OS VERSIONS Linux/KDE Plasma: Alpine Linux Edge KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION This system runs in a Qemu VM (using the UTM application) on macOS. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480421] Icons-only task manager often messes up rendering resulting in either 1-2 pixels wide icons or icons about 4 times as small as they should be
https://bugs.kde.org/show_bug.cgi?id=480421 --- Comment #5 from Bart Ribbers --- Sorry, not really so far. As you can see on the screenshot my panel is horizontally. It's on a left screen as well, the second screen to the right in my setup has no panel. It always happens on boot, but I can't figure out what other situations make it happen. This has started since the Plasma 6 first beta release, it's not an issue on Plasma 5. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480421] Icons-only task manager often messes up rendering resulting in either 1-2 pixels wide icons or icons about 4 times as small as they should be
https://bugs.kde.org/show_bug.cgi?id=480421 --- Comment #2 from Bart Ribbers --- Created attachment 165300 --> https://bugs.kde.org/attachment.cgi?id=165300&action=edit The icons as they should be -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480421] Icons-only task manager often messes up rendering resulting in either 1-2 pixels wide icons or icons about 4 times as small as they should be
https://bugs.kde.org/show_bug.cgi?id=480421 --- Comment #1 from Bart Ribbers --- Created attachment 165299 --> https://bugs.kde.org/attachment.cgi?id=165299&action=edit Still too small icons, but rather than 1-2 pixels wide now about 4 times as small as intended -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480421] New: Icons-only task manager often messes up rendering resulting in either 1-2 pixels wide icons or icons about 4 times as small as they should be
https://bugs.kde.org/show_bug.cgi?id=480421 Bug ID: 480421 Summary: Icons-only task manager often messes up rendering resulting in either 1-2 pixels wide icons or icons about 4 times as small as they should be Classification: Plasma Product: plasmashell Version: 5.92.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: bribb...@disroot.org CC: qydwhotm...@gmail.com Target Milestone: 1.0 Created attachment 165298 --> https://bugs.kde.org/attachment.cgi?id=165298&action=edit 1-2 pixels wide icons SUMMARY As the title says, the icons-only task manager often messes up the rendering resulting in weird glitches. This is often "fixed" by launching or closing an application but that's not always the case, and after being correct for a while it also likes to mess up again. I'm not sure what invokes it but it definitely always appears just after booting. I'd add more screenshots in this initial post demonstrating the problem but Bugzilla only seems to allow just 1 attachment per post, so I'll post the others in subsequent comments on this bug report. STEPS TO REPRODUCE 1. Put the icons-only task manager on a panel 2. Reboot OBSERVED RESULT Rendering is messed up, resulting in either 1-2 pixels wide icons or icons about 3 times as small as they should be. Launching an application changes it back to regular sized icons. EXPECTED RESULT Icons to always be rendered at the correct size. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Alpine Linux edge KDE Plasma Version: 5.92.0 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 478405] New: Subscriber count on an open video is hard to read due to not using separation dots/commas
https://bugs.kde.org/show_bug.cgi?id=478405 Bug ID: 478405 Summary: Subscriber count on an open video is hard to read due to not using separation dots/commas Classification: Applications Product: PlasmaTube Version: 24.01.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- Created attachment 164095 --> https://bugs.kde.org/attachment.cgi?id=164095&action=edit Screenshot showing subscriber count on a random video See attached image. It would be better if it was formatted "12.200.000" (Dutch locale) or "12,200,000" (non-Dutch locale, I suppose). Or even better, shorten the number like the views and likes counter just beneath it. "12M". -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 476006] Thumbnails fail to load with the Piped backend
https://bugs.kde.org/show_bug.cgi?id=476006 Bart Ribbers changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #6 from Bart Ribbers --- I talked with Joshua over Matrix and we found the problem. The system didn't have Qt6ImageFormats installed (only the Qt5 variant) and that's required for WebP images, which piped uses. After installing it the problem was resolved. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 476006] Thumbnails fail to load with the Piped backend
https://bugs.kde.org/show_bug.cgi?id=476006 Bart Ribbers changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Bart Ribbers --- The problem occurs on other instances too. For example https://pipedproxy.kavin.rocks/vi/NcJF-R1DGQ8/hqdefault.jpg?host=i.ytimg.com&qhash=5af0f5be&rs=AOn4CLCTBgkOkpx5A2Kwz9jSyYhVyIj6vw&sqp=-oaymwEcCNACELwBSFXyq4qpAw4IARUAAIhCGAFwAcABBg%3D%3D: fails to load as well. How do I check what image format it thinks it is? It isn't printed to stdout. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 478153] Images don't load using the piped backend
https://bugs.kde.org/show_bug.cgi?id=478153 Bart Ribbers changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Bart Ribbers --- Sorry this is a duplicate of https://bugs.kde.org/show_bug.cgi?id=476006, my own bug report lol. I knew I made the bug report at some point but couldn't find it any more so I wasn't sure if it still existed. Seems it does! *** This bug has been marked as a duplicate of bug 476006 *** -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 476006] Thumbnails fail to load with the Piped backend
https://bugs.kde.org/show_bug.cgi?id=476006 --- Comment #4 from Bart Ribbers --- *** Bug 478153 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 478153] New: Images don't load using the piped backend
https://bugs.kde.org/show_bug.cgi?id=478153 Bug ID: 478153 Summary: Images don't load using the piped backend Classification: Applications Product: PlasmaTube Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- It doesn't change when switching between instances either. stdout is full of warnings: qrc:/qt/qml/org/kde/plasmatube/ui/components/VideoGridItem.qml:86:9: QML QQuickImage: Error decoding: https://pipedproxy.kavin.rocks/vi/NcJF-R1DGQ8/hqdefault.jpg?host=i.ytimg.com&qhash=5af0f5be&rs=AOn4CLCTBgkOkpx5A2Kwz9jSyYhVyIj6vw&sqp=-oaymwEcCNACELwBSFXyq4qpAw4IARUAAIhCGAFwAcABBg%3D%3D: Unsupported image format -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477635] Panel doesn't respect transparency setting, doesn't go transparent/translucent
https://bugs.kde.org/show_bug.cgi?id=477635 --- Comment #11 from Bart Ribbers --- Oh no 🙈 I came from Latte Dock where it _was_ a feature and was glad it was a thing on the regular Plasma panel of well. I suppose this can then be turned into a feature request lol. Or is there a different way to get just a task manager on the bottom there without having it on a panel? I'm sad to see my desktop change 😢 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477635] Panel doesn't respect transparency setting, doesn't go transparent/translucent
https://bugs.kde.org/show_bug.cgi?id=477635 --- Comment #9 from Bart Ribbers --- Created attachment 163661 --> https://bugs.kde.org/attachment.cgi?id=163661&action=edit Screenshot of Plasma 5 desktop with desired panel configuration No I'm just using Breeze Dark. As shown on the screenshot the bottom panel is completely transparent, only the task manager widget and a network monitor is visible. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477635] Panel doesn't respect transparency setting, doesn't go transparent/translucent
https://bugs.kde.org/show_bug.cgi?id=477635 --- Comment #7 from Bart Ribbers --- This is not a VM no, it's my desktop on an installation that upgraded from Plasma 5. Maybe there is an old config setting messing things up? And maybe I'm misunderstanding something, is translucent not the same as transparent? I don't want to see anything of the panel, just the widget that's on there. I want it to be transparent, and it's very, very obvious that it's not transparent. I don't understand why you are talking about "hard to notice". I just noticed on my laptop, which still runs Plasma 5, the setting is set to "opague". It translates to the same word in my language and I guess I don't have a full understanding of it but doesn't that mean the opposite of transparent? Anyhow I've also tried "opague" on Plasma 6 and it didn't change anything, and neither does switching to translucent on Plasma 5 really. So to be clear, what I want is the panel to not be visible at all, just the widget that's on it. So far I fail to see how I can achieve that while it worked fine in Plasma 5. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477635] Panel doesn't respect transparency setting, doesn't go transparent/translucent
https://bugs.kde.org/show_bug.cgi?id=477635 --- Comment #4 from Bart Ribbers --- I do not notice a difference. But, hard to notice? On Plasma 5 the panel is completely transparent while it's not at all on the KDE6 alpha. It's not just hard to notice, it's completely different. I do not want to see the panel, I only want to see the task manager. How is this not a bug? 😅 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477635] Panel doesn't respect transparency setting, doesn't go transparent/translucent
https://bugs.kde.org/show_bug.cgi?id=477635 --- Comment #2 from Bart Ribbers --- Created attachment 163611 --> https://bugs.kde.org/attachment.cgi?id=163611&action=edit Screenshot of desktop with edit mode open for opague panel set to translucent As you can see the setting is set to translucent but the panel remains opague, and there is no difference outside of edit mode. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477635] New: Panel doesn't respect transparency setting, doesn't go transparent/translucent
https://bugs.kde.org/show_bug.cgi?id=477635 Bug ID: 477635 Summary: Panel doesn't respect transparency setting, doesn't go transparent/translucent Classification: Plasma Product: plasmashell Version: 5.27.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: bribb...@disroot.org CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY I have a bottom panel with an icons-only task manager. The entire panel should be transparent but plasmashell seems to ignore the setting. Setting it to translucent keeps it opague, and setting it to opague and back doesn't fix it. STEPS TO REPRODUCE 1. Add a panel 2. Setting opague setting to translucent OBSERVED RESULT Panel remains opague EXPECTED RESULT Panel goes translucent SOFTWARE/OS VERSIONS Linux/KDE Plasma: Alpine Linux edge (available in About System) KDE Plasma Version: KDE6 alpha, 5.27.80 KDE Frameworks Version: KDE6 alpha, 5.245.0 Qt Version: 6.6.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 477321] New: Add Nymphcast support
https://bugs.kde.org/show_bug.cgi?id=477321 Bug ID: 477321 Summary: Add Nymphcast support Classification: Applications Product: PlasmaTube Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- Nymphcast (https://github.com/MayaPosch/nymphcast) is a FOSS alternative to Google's Chromecast, both on the server and client-side. It would be great for Plasmatube to support it so you can cast videos and audio to any Nymphcast receiver, for example Plasma Bigscreen. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 477241] New: Non-fullscreen videos don't inhibit the screen, making powerdevil turn off the screen after a few seconds on mobile
https://bugs.kde.org/show_bug.cgi?id=477241 Bug ID: 477241 Summary: Non-fullscreen videos don't inhibit the screen, making powerdevil turn off the screen after a few seconds on mobile Classification: Applications Product: PlasmaTube Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- I don't always watch videos fullscreen but when I don't Plasmatube doesn't tell powerdevil to keep the device awake which causes it to turn off the screen after half a minute or so. This doesn't happen when the video is in fullscreen mode. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 477239] New: Can't scroll through list of videos on mobile, it opens the video being clicked on instead
https://bugs.kde.org/show_bug.cgi?id=477239 Bug ID: 477239 Summary: Can't scroll through list of videos on mobile, it opens the video being clicked on instead Classification: Applications Product: PlasmaTube Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- Not sure what more info to give 😅 -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 477231] New: In fullscreen the video controls never hide
https://bugs.kde.org/show_bug.cgi?id=477231 Bug ID: 477231 Summary: In fullscreen the video controls never hide Classification: Applications Product: PlasmaTube Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- Not sure how I can be more specific 😅 -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 477230] New: Double-clicking the video to fullscreen it toggles pause/resume video
https://bugs.kde.org/show_bug.cgi?id=477230 Bug ID: 477230 Summary: Double-clicking the video to fullscreen it toggles pause/resume video Classification: Applications Product: PlasmaTube Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- Most of the time the video is already playing when I want to fullscreen it and I most definitely don't want to pause it when that happens. However currently double-clicking the video to fullscreen it also pauses the video (or resumes it when it was paused). -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 477152] New: Other monitor (via other input) dims while not actively connected in a multi system multi monitor set-up.
https://bugs.kde.org/show_bug.cgi?id=477152 Bug ID: 477152 Summary: Other monitor (via other input) dims while not actively connected in a multi system multi monitor set-up. Classification: Plasma Product: Powerdevil Version: 5.27.9 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bclep...@gmail.com CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY Other monitor (active via other input) dims while not actively connected in a multi system multi monitor set-up. System is not being used for a while and dims monitor 1. As a result monitor 2 dims as well (even though it is not showing/connected to said system - but displaying another input). STEPS TO REPRODUCE Monitor 1 connected via DVI-D to 'desktop'. Monitor 1 has no other inputs connected. Monitor 2 connected via VGA to 'desktop'. Monitor 2 connected via DisplayPort to docking station. Monitor 1 is displaying DVI-D (so 'desktop'). Monitor 2 is displaying DisplayPort (so docking station). Docking station is connected to a laptop. Now wait until screen dims. OBSERVED RESULT 'desktop' dims monitor 1 after not being used for a while (correct). Monitor 2 dims as well (even though it is not showing/connected to desktop) (unexpected). Waking up monitor 1 (by e.g. mouse activity on 'desktop') also wakes up (i.e. undims) monitor 2. EXPECTED RESULT Monitor 1 and monitor 2 are dimmed by their respective connected inputs (they listen to the device they are connected to). SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.1-arch1-1 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-4590 CPU @ 3.30GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B85M-HD3 ADDITIONAL INFORMATION * 2 monitors (2x Dell P2314H) Energy Smart is off, DDC/CI disabled, LCD conditioning enabled (on both) * Dell docking station D6000 USB-C * System (name 'desktop') -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420280] Google authentication process gets stuck due to excessively old version of signon-ui library
https://bugs.kde.org/show_bug.cgi?id=420280 --- Comment #100 from Bart Ribbers --- It's not weird at all that it works fine on Alpine Linux. The issue is known, an old version of signon-ui. Alpine Linux ships a newer version that _does_ work. Problem solved. (and Musl really shouldn't be an issue for 99% of the users, there is Flatpak for things like Steam anyway. Offtopic though) I'm not sure why people are still going on about this issue, the cause is known (it's literally in the title) and the solution is also known. Distros just have to update their signon-ui package. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 476007] New: Fullscreen shows the sidebar as well
https://bugs.kde.org/show_bug.cgi?id=476007 Bug ID: 476007 Summary: Fullscreen shows the sidebar as well Classification: Applications Product: PlasmaTube Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- The video does go fullscreen, except that the sidebar is also shown and can't be hidden. This doesn't always happen but when it does on a video there is no way to get rid of it. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 476006] Thumbnails fail to load with the Piped backend
https://bugs.kde.org/show_bug.cgi?id=476006 --- Comment #1 from Bart Ribbers --- Sorry forgot to post the full error message: qrc:/qt/qml/org/kde/plasmatube/ui/components/VideoGridItem.qml:61:9: QML QQuickImage: Error decoding: https://proxy.youtube.fam-ribbers.com/vi/XFJRcVg2QmE/hq720.jpg?sqp=-oaymwEcCOgCEMoBSFXyq4qpAw4IARUAAIhCGAFwAcABBg==&rs=AOn4CLAczJ_9TlLHrJBM_rAYjIyihAAAtQ&host=i.ytimg.com: Unsupported image format -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 476006] New: Thumbnails fail to load with the Piped backend
https://bugs.kde.org/show_bug.cgi?id=476006 Bug ID: 476006 Summary: Thumbnails fail to load with the Piped backend Classification: Applications Product: PlasmaTube Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- Using my own instance, https://youtube.fam-ribbers.com (API on https://api.youtube.fam-ribbers.com and proxy on https://proxy.youtube.fam-ribbers.com), any video thumbnail fails to load. However putting it's URL in the browser appears to work just fine. Example of a thumbnail failing to load: https://proxy.youtube.fam-ribbers.com/vi/XFJRcVg2QmE/hq720.jpg?sqp=-oaymwEcCOgCEMoBSFXyq4qpAw4IARUAAIhCGAFwAcABBg==&rs=AOn4CLAczJ_9TlLHrJBM_rAYjIyihAAAtQ&host=i.ytimg.com -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 476005] New: Sync local subscriptions, video playback progress and playlists to other instances over something like Matrix
https://bugs.kde.org/show_bug.cgi?id=476005 Bug ID: 476005 Summary: Sync local subscriptions, video playback progress and playlists to other instances over something like Matrix Classification: Applications Product: PlasmaTube Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- That way no account is needed per used service/backend and it makes it easier to switch services. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 472749] MPRIS support
https://bugs.kde.org/show_bug.cgi?id=472749 Bart Ribbers changed: What|Removed |Added CC||bribb...@disroot.org --- Comment #1 from Bart Ribbers --- *** Bug 475972 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 475972] Add MPRIS support
https://bugs.kde.org/show_bug.cgi?id=475972 Bart Ribbers changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Bart Ribbers --- Woops sorry, duplicated of https://bugs.kde.org/show_bug.cgi?id=472749 *** This bug has been marked as a duplicate of bug 472749 *** -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 475972] New: Add MPRIS support
https://bugs.kde.org/show_bug.cgi?id=475972 Bug ID: 475972 Summary: Add MPRIS support Classification: Applications Product: PlasmaTube Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- To be able to control playback of the video via Plasma widgets, keyboard media keys and KDE Connect. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 475971] New: Double-clicking the video should fullscreen it
https://bugs.kde.org/show_bug.cgi?id=475971 Bug ID: 475971 Summary: Double-clicking the video should fullscreen it Classification: Applications Product: PlasmaTube Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- Rather than just having a tiny button to do it. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 475970] New: Add video seeking using arrow keys
https://bugs.kde.org/show_bug.cgi?id=475970 Bug ID: 475970 Summary: Add video seeking using arrow keys Classification: Applications Product: PlasmaTube Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- On YouTube I quite often seek through the video using the arrow keys, it would be great if PlasmaTube supported that s well. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 475969] New: Add Twitch support using Twineo
https://bugs.kde.org/show_bug.cgi?id=475969 Bug ID: 475969 Summary: Add Twitch support using Twineo Classification: Applications Product: PlasmaTube Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- https://codeberg.org/CloudyyUw/twineo Twineo is a privacy-friendly based frontend for Twitch inspired by Invidious and Nitter. It would be great if Plasmatube had support for that. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 475968] New: Application appears with mpv icon in plasma-pa
https://bugs.kde.org/show_bug.cgi?id=475968 Bug ID: 475968 Summary: Application appears with mpv icon in plasma-pa Classification: Applications Product: PlasmaTube Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- Rather than the Plasmatube icon as it should. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 475967] New: No volume control in the video player
https://bugs.kde.org/show_bug.cgi?id=475967 Bug ID: 475967 Summary: No volume control in the video player Classification: Applications Product: PlasmaTube Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- I realize that you can set the application volume via the OS settings, but it would be nice to be able to do it directly in the video player as well. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 475966] New: Pressing escape doesn't close fullscreen videos
https://bugs.kde.org/show_bug.cgi?id=475966 Bug ID: 475966 Summary: Pressing escape doesn't close fullscreen videos Classification: Applications Product: PlasmaTube Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- As the title says. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 475965] New: Clicking on the video player should pause/resume the video
https://bugs.kde.org/show_bug.cgi?id=475965 Bug ID: 475965 Summary: Clicking on the video player should pause/resume the video Classification: Applications Product: PlasmaTube Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- YouTube does this (well any video player in browsers) and it's a lovely feature. It wouldn't be too great on mobile though so if possible it would be nice to have this a setting depending on the used platform. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 475964] New: Changing video resolution doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=475964 Bug ID: 475964 Summary: Changing video resolution doesn't do anything Classification: Applications Product: PlasmaTube Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- Created attachment 162502 --> https://bugs.kde.org/attachment.cgi?id=162502&action=edit Screenshot of the resolution list Also right now it seems to be random ordering, it would be nice to sort that by quality. Also I didn't realize "Settings" would just have resolution options available. Is the plan to add more settings there or is it just going to be resolution options? If the latter maybe the icon to open the menu should be changed. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 475650] DRD does not work with C11 threads
https://bugs.kde.org/show_bug.cgi?id=475650
Bart Van Assche changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Bart Van Assche ---
The following two additional commits have been pushed:
* 45590cee742b ("drd/tests/thrd_create: Convert from C++ to C")
* a9d065c48d35 ("configure.ac: Convert the thrd_create() test from C++ to C")
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 475650] DRD does not work with C11 threads
https://bugs.kde.org/show_bug.cgi?id=475650 Bart Van Assche changed: What|Removed |Added CC||bart.vanassche+...@gmail.co ||m --- Comment #2 from Bart Van Assche --- Does commit 6cea271f436d help? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 473476] Okular crashing (SIGSEGV) when saving a PDF
https://bugs.kde.org/show_bug.cgi?id=473476 --- Comment #3 from Bart Ribbers --- Created attachment 161324 --> https://bugs.kde.org/attachment.cgi?id=161324&action=edit Okular through Valgrind output I did have debug symbols installed, of both Okular and Kio. It didn't change the backtrace unfortunately. Not sure how useful the Valgrind output is but it's attached. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 473476] New: Okular crashing (SIGSEGV) when saving a PDF
https://bugs.kde.org/show_bug.cgi?id=473476 Bug ID: 473476 Summary: Okular crashing (SIGSEGV) when saving a PDF Classification: Applications Product: okular Version: 23.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: bribb...@disroot.org Target Milestone: --- SUMMARY This happens seemingly in KIO, but I only experience it through Okular. Happens every time I make any kind of modification to a PDF and try to save it. Thread 25 "KIO::WorkerThre" received signal SIGSEGV, Segmentation fault. [Switching to LWP 9837] 0x7fffdf1f0789 in ?? () from /usr/lib/qt5/plugins/kf5/kio/kio_file.so (gdb) bt #0 0x7fffdf1f0789 in ?? () from /usr/lib/qt5/plugins/kf5/kio/kio_file.so #1 0x77c07713 in KIO::SlaveBase::dispatch(int, QByteArray const&) () from /usr/lib/libKF5KIOCore.so.5 #2 0x77c08326 in KIO::SlaveBase::dispatchLoop() () from /usr/lib/libKF5KIOCore.so.5 #3 0x77ca2935 in ?? () from /usr/lib/libKF5KIOCore.so.5 #4 0x764ac9db in operator() (__closure=) at thread/qthread_unix.cpp:350 #5 (anonymous namespace)::terminate_on_exception > (t=...) at thread/qthread_unix.cpp:287 #6 QThreadPrivate::start (arg=0x7fffe37ab620) at thread/qthread_unix.cpp:310 #7 0x77fb8239 in start (p=0x7fffdd1f5860) at src/thread/pthread_create.c:207 #8 0x77fba83a in __clone () at src/thread/x86_64/clone.s:22 STEPS TO REPRODUCE 1. Open any PDF 2. Add some kind of annotations 3. Save the PDF OBSERVED RESULT Okular crashes instantly EXPECTED RESULT Okular saving the file properly SOFTWARE/OS VERSIONS Linux/KDE Plasma: Alpine Linux edge (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 with KDE patches -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420280] Can't add Google account: authentication process gets stuck
https://bugs.kde.org/show_bug.cgi?id=420280 --- Comment #48 from Bart Ribbers --- Ah I now see you were talking about signond in that case. Still, signon-ui is also important in this stack and yes, last commit was 5 years ago and the last tag was 8(!) years ago. That does seem dead to me, even if signond isn't. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420280] Can't add Google account: authentication process gets stuck
https://bugs.kde.org/show_bug.cgi?id=420280 --- Comment #47 from Bart Ribbers --- Not sure if you see something different Nate, bu https://gitlab.com/accounts-sso/signon-ui/-/commits/master?ref_type=heads only lists commits from 5 years ago. That doesn't seem "recent" to me. It is the commit I've been packaging in Alpine Linux but I really rather see something more maintained... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420280] Can't add Google account: authentication process gets stuck
https://bugs.kde.org/show_bug.cgi?id=420280 --- Comment #39 from Bart Ribbers --- Can't reproduce on Alpine Linux with 8.61-r1 either. Even better, it works with a hardware key for 2FA which I didn't expect at all. So this definitely seems like an Ubuntu-only problem. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 415843] musl system: can't be compiled due to missing fstab.h
https://bugs.kde.org/show_bug.cgi?id=415843 Bart Ribbers changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Bart Ribbers --- This isn't relevant anymore and hasn't been for a while. Alpine Linux (with Musl libc) has been shipping k3b for a while -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 455913] [Wayland + Nvidia] Krunner stops showing after opening / closing it a few times
https://bugs.kde.org/show_bug.cgi?id=455913 Bart Janssens changed: What|Removed |Added CC||b...@bartjanssens.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417227] No keyboard shortcuts work on Wayland when using musl instead of glibc
https://bugs.kde.org/show_bug.cgi?id=417227 Bart Ribbers changed: What|Removed |Added Status|NEEDSINFO |REPORTED Ever confirmed|1 |0 Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417227] No keyboard shortcuts work on Wayland when using musl instead of glibc
https://bugs.kde.org/show_bug.cgi?id=417227 --- Comment #16 from Bart Ribbers --- It is not, but only because at Alpine Linux we now ship a workaround, https://git.alpinelinux.org/aports/tree/community/kwin/APKBUILD#n108. The same workaround is applied at powerdevil to make that launch at all, https://git.alpinelinux.org/aports/tree/community/powerdevil/APKBUILD#n73. Pretty sure this workaround has other unforeseen consequences, so I rather have it fixed properly. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 470863] New: Screen rearrangments applied through kscreen-doctor are not persistent across screen turning off and on
https://bugs.kde.org/show_bug.cgi?id=470863 Bug ID: 470863 Summary: Screen rearrangments applied through kscreen-doctor are not persistent across screen turning off and on Classification: Plasma Product: KScreen Version: 5.27.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: bribb...@disroot.org Target Milestone: --- SUMMARY Split out from https://bugs.kde.org/show_bug.cgi?id=470674, see that bug for some more info. Basically I'm using kscreen-doctor to apply my screen layout, 3 screens: 2 desktop monitors which are exact same model next to each other, and a separate TV as a third screen. In my ideal setup I have the TV (third screen) mirrored to the left screen of the two desktop monitors. However Plasma keeps making it mirror the right desktop monitor instead every time I turn off and on the TV. Thus I have to keep on calling kscreen-doctor every time I turn on the TV. STEPS TO REPRODUCE Not sure, it's seems setup specific. But I suppose: 1. have 3 screens of which 1 should mirror one of the other two 2. turn off the third screen 3. turn it back on OBSERVED RESULT The third screen mirrors the wrong screen every time it's turned off and on. EXPECTED RESULT The screen mirroring to be remembered correctly across screen reboots. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Alpine Linux edge (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 with KDE patches -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470674] Screen that appears in kscreen-doctor doesn't appear in the KCM draggable view
https://bugs.kde.org/show_bug.cgi?id=470674 --- Comment #14 from Bart Ribbers --- I'm still not sure it's the exact same as that report. Like I said it's not hidden, it's just not there. I can drag the "overlapping" screen all I want, the other screen _will_ _not_ _appear_. And the screen gives me no way to "detach" the screen either. In that other bug report it seems you can just drag the screens off each other and everything will appear correctly. I will file a report separately for the changes not persisting though, that indeed is separate. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470674] Screen that appears in kscreen-doctor doesn't appear in the KCM draggable view
https://bugs.kde.org/show_bug.cgi?id=470674 --- Comment #12 from Bart Ribbers --- Yes that is accurate. The changes don't persist when I turn off and on that third screen. For some reason even though the screen is still detected when it's off, it's rearranges my screen setup and when I turn it back on it's back to mirroring the wrong one. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 470763] Crash copying files in Dolphin due to stack overflow.
https://bugs.kde.org/show_bug.cgi?id=470763 Bart Ribbers changed: What|Removed |Added CC||bribb...@disroot.org --- Comment #1 from Bart Ribbers --- Just to include a bit more detail in this bug report rather than having to go outside this bugtracker: This seems to be due to a small stack size. When the stack size of Dolphin is increased to 1M (using LDFLAGS="$LDFLAGS -Wl,-z,stack-size=0x10") it never happens. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470674] Screen that appears in kscreen-doctor doesn't appear in the KCM draggable view
https://bugs.kde.org/show_bug.cgi?id=470674 --- Comment #10 from Bart Ribbers --- No that part is correct, it's mirroring that screen. It's not what I want though, I actually want it to mirror my left screen and right now I have to run a kscreen-doctor command every time I turn that screen on. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470674] Screen that appears in kscreen-doctor doesn't appear in the KCM draggable view
https://bugs.kde.org/show_bug.cgi?id=470674 Bart Ribbers changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #8 from Bart Ribbers --- Actually I just realized the right screen is marked as duplicated, so I guess that's where that screen is? That isn't in anyway clear though if you just select the screen from the dropdown. Also I'm unsure how to get it detached from that other screen. Screen priorities seems to do nothing -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470674] Screen that appears in kscreen-doctor doesn't appear in the KCM draggable view
https://bugs.kde.org/show_bug.cgi?id=470674 --- Comment #7 from Bart Ribbers --- Created attachment 159508 --> https://bugs.kde.org/attachment.cgi?id=159508&action=edit Screenshot of the Display Configuration KCM Attached the screenshot. As you can see the device selected in the dropdown isn't present in the "Drag screens" view. -- You are receiving this mail because: You are watching all bug changes.
