[plasmashell] [Bug 481912] Feature request: Wayland remote login sessions with Plasma, like xrdp
https://bugs.kde.org/show_bug.cgi?id=481912 --- Comment #7 from Matthias Klumpp --- No, krdp does not work at all like xrdp yet. The whole session management part is missing (unless that has changed extremely recently) and you basically need to have physical access to the remote computer to make krdp viable. Check out https://wiki.archlinux.org/title/xrdp and https://github.com/neutrinolabs/xrdp?tab=readme-ov-file#features -- You are receiving this mail because: You are watching all bug changes.
[kuser] [Bug 376157] kf5 kuser
https://bugs.kde.org/show_bug.cgi?id=376157 --- Comment #14 from Matthias --- Yeah sorry, I skimmed too quickly over the last comment, my fault. -- You are receiving this mail because: You are watching all bug changes.
[kuser] [Bug 376157] kf5 kuser
https://bugs.kde.org/show_bug.cgi?id=376157 Matthias changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #11 from Matthias --- I dont know how its called, but I have a KCM for user management for a long time now. I upload a screenshot, and add that I assume this is standard in the systemsettings now, as I do not see a package with 'user' and 'kcm' being available. I think this is fixed. (I am using Garuda KDE, also available on NixOS and KaOS.) -- You are receiving this mail because: You are watching all bug changes.
[kuser] [Bug 376157] kf5 kuser
https://bugs.kde.org/show_bug.cgi?id=376157 --- Comment #10 from Matthias --- Created attachment 169687 --> https://bugs.kde.org/attachment.cgi?id=169687=edit KCM -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 433463] Discover should de-duplicate apps whose AppStream IDs differ only by the presence or absence of the ".desktop" suffix
https://bugs.kde.org/show_bug.cgi?id=433463 --- Comment #12 from Matthias Klumpp --- Oh, just to add: Component IDs should be matched *exactly*, doing heuristics was a really bad idea of the past. If an application wants to rename its ID, it can do so *explicitly* by using a `replaces` block: https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-replaces Of course, if such a hint is there, Discover should follow it and combine the two components under the new name (if libappstream hasn't done that already). Some components use "provides" instead of "replaces", which is a bit unfortunate (likely from a time before we had a proper replacement mechanism in AppStream...), but at least this is also explicit and no error-prone heuristics are happening. If any duplicate apps happen, those issues should be fixed by the distributors (Flathub, Debian/Fedora/OpenSUSE/Ubuntu/etc) or by the respective upstreams by either fixing the ID or by adding any missing `replaces` tags. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 433463] Discover should de-duplicate apps whose AppStream IDs differ only by the presence or absence of the ".desktop" suffix
https://bugs.kde.org/show_bug.cgi?id=433463 Matthias K. changed: What|Removed |Added CC||matth...@tenstral.net --- Comment #11 from Matthias K. --- To make one thing super clear: This *must not* be fixed in Discover, and it also *must not* be addressed in AppStream either. No entity except for the upstream project and, in rare cases, the packager, should ever mess with the component ID. A lot of stuff is tied to it, changing is basically means renaming the project, and stripping a bunch of associated metadata. We also have pretty bad history with messing with component IDs, causing a ton of issues (so, the only place we touch them in distributions is when there is no MetaInfo file and an ID is synthesized). For the issue at hand, this is a weird one! I was looking at this using the Debian package, since that's the distro I use. On Debian, the component has the ID `org.godotengine.Godot`, so I thought maybe we rename it in the package! Turns out, that is not the case: https://salsa.debian.org/debian/godot3/-/blob/master/debian/rules?ref_type=heads#L97 So, Debian just ships the metaInfo file that upstream provides, which has the `org.godotengine.Godot` ID. So, looking at the Flatpak recipe, for some reason Flatpak does *not* use the upstream-provided MetaInfo file, but provides its own one! And look at that: https://github.com/flathub/org.godotengine.Godot/blob/master/org.godotengine.Godot.appdata.xml#L3 => It has the "wrong" ID, diverging from upstream! Funnily enough, the Flatpak itself is named `org.godotengine.Godot`, so I see no reason at all for this weird diversion... Maybe it had something to do with appstream-glib in the past before Flatpak switched to libappstream, but that would be odd... In any case, this goes completely against what MetaInfo files are designed for, upstream is supposed to provide them, and packagers may only provide one if upstream doesn't have one. So, tl;dr, this is not a Discover bug or AppStream or Flatpak bug, but a bug in the Flatpak bundle. IMHO the downstream MetaInfo file should just be deleted and the one from upstream should be used instead, that's what it's for! (and if anything is missing, just contribute the metadata upstream!) At the very least, the component ID should be harmonized with what upstream ships though. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 392146] aarch64: unhandled instruction 0xD5380001 (MRS rT, midr_el1)
https://bugs.kde.org/show_bug.cgi?id=392146 --- Comment #32 from Matthias Brugger --- It's good to see that this got fixed. That said it seems that the community process in valgrind is somewhat broken. I sent a fix, it went silent for nearly 6 years. You took up the work, did a small change and pushed that right away, no review or possibility to fix it myself. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 486564] svg font-variant displayed in text-edit but not on canvas
https://bugs.kde.org/show_bug.cgi?id=486564 --- Comment #2 from Matthias --- (In reply to Nate Graham from comment #1) > What's the context? What app are you using? Is this in Krita? Yeah sorry, this is for Krita. I changed product but I must've forgotten to save it. Now it should be in the right place :D -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 486564] svg font-variant displayed in text-edit but not on canvas
https://bugs.kde.org/show_bug.cgi?id=486564 Matthias changed: What|Removed |Added Version|unspecified |5.2.2 Component|general |Tool/Text Product|kde |krita -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 486565] svg font-variant displayed in text-edit but not on canvas
https://bugs.kde.org/show_bug.cgi?id=486565 Matthias changed: What|Removed |Added Version|unspecified |5.2.2 Product|kde |krita Assignee|unassigned-b...@kde.org |krita-bugs-n...@kde.org Component|general |Tool/Text -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 486565] svg font-variant displayed in text-edit but not on canvas
https://bugs.kde.org/show_bug.cgi?id=486565 --- Comment #1 from Matthias --- Created attachment 169184 --> https://bugs.kde.org/attachment.cgi?id=169184=edit recording of the bug -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 486565] New: svg font-variant displayed in text-edit but not on canvas
https://bugs.kde.org/show_bug.cgi?id=486565 Bug ID: 486565 Summary: svg font-variant displayed in text-edit but not on canvas Classification: I don't know Product: kde Version: unspecified Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: marschner.matth...@icloud.com Target Milestone: --- If you edit the svg source of a text and add the font-variant string, it will display the change in the text-edit box but not on the canvas itself. I tried it with 10+ fonts but no luck. STEPS TO REPRODUCE 1. add text box and write anything 2. add the font-variant string to the style parameter 3. click save OBSERVED RESULT lower case letters are still lower case EXPECTED RESULT lower case letters should be in small caps SOFTWARE/OS VERSIONS Windows: / macOS: macOS 14.4.1 (23E224) Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 486564] New: svg font-variant displayed in text-edit but not on canvas
https://bugs.kde.org/show_bug.cgi?id=486564 Bug ID: 486564 Summary: svg font-variant displayed in text-edit but not on canvas Classification: I don't know Product: kde Version: unspecified Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: marschner.matth...@icloud.com Target Milestone: --- If you edit the svg source of a text and add the font-variant string, it will display the change in the text-edit box but not on the canvas itself. I tried it with 10+ fonts but no luck. STEPS TO REPRODUCE 1. add text box and write anything 2. add the font-variant string to the style parameter 3. click save OBSERVED RESULT lower case letters are still lower case EXPECTED RESULT lower case letters should be in small caps SOFTWARE/OS VERSIONS Windows: / macOS: macOS 14.4.1 (23E224) Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486431] Templates for C++ Plasmoids look for KF6PlasmaConfig
https://bugs.kde.org/show_bug.cgi?id=486431 --- Comment #8 from Matthias --- https://invent.kde.org/plasma/libplasma/-/tree/Plasma/6.0/templates/cpp-plasmoid6 https://invent.kde.org/plasma/libplasma/-/tree/Plasma/6.0/templates/qml-plasmoid6-with-qml-extension Those are the two in question. I found, that the CMakeLists.txt in /plugin and /src had been adjusted by Nicolas 5 months ago, the CMakeLists.txt in the upper directory, has not seen such an adjustment. Could it be, that this is the cause? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486431] Templates for C++ Plasmoids look for KF6PlasmaConfig
https://bugs.kde.org/show_bug.cgi?id=486431 --- Comment #5 from Matthias --- Created attachment 169090 --> https://bugs.kde.org/attachment.cgi?id=169090=edit Plasma QML/C++ Applet -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486431] Templates for C++ Plasmoids look for KF6PlasmaConfig
https://bugs.kde.org/show_bug.cgi?id=486431 --- Comment #4 from Matthias --- Created attachment 169089 --> https://bugs.kde.org/attachment.cgi?id=169089=edit Plasma QML Applet with QML Extension -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486431] Templates for C++ Plasmoids look for KF6PlasmaConfig
https://bugs.kde.org/show_bug.cgi?id=486431 --- Comment #3 from Matthias --- Those are the two templates, I mean. Upload Screenshots -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486431] Templates for C++ Plasmoids look for KF6PlasmaConfig
https://bugs.kde.org/show_bug.cgi?id=486431 --- Comment #2 from Matthias --- No, these are not even ported to 6 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486431] New: Templates for C++ Plasmoids look for KF6PlasmaConfig
https://bugs.kde.org/show_bug.cgi?id=486431 Bug ID: 486431 Summary: Templates for C++ Plasmoids look for KF6PlasmaConfig Classification: Applications Product: kdevelop Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- Created attachment 169086 --> https://bugs.kde.org/attachment.cgi?id=169086=edit KF6PlasmaConfig not found SUMMARY The two templates for C++ QML Plasmoids look for KF6PlasmaConfig, while they should look for PlasmaConfig. See screenshot STEPS TO REPRODUCE 1. Open up one of the C++ Plasmoid Templates 2. See error message Operating System: KaOS (2024) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.8-1-next (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800U with Radeon Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82L0 System Version: Yoga Slim 7 Carbon 14ACN6 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 392146] aarch64: unhandled instruction 0xD5380001 (MRS rT, mdir_el1)
https://bugs.kde.org/show_bug.cgi?id=392146 Matthias Brugger changed: What|Removed |Added CC||mbrug...@suse.com --- Comment #22 from Matthias Brugger --- (In reply to Paul Floyd from comment #13) > Do you have any tests for this? Unfortunately after such a long time I'm not able to find the reproducer. At that time I remeber that is was some code in glibc that invoked reads of MDIR_EL1. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 486252] New: Implementation of a context menu entry to mention users
https://bugs.kde.org/show_bug.cgi?id=486252 Bug ID: 486252 Summary: Implementation of a context menu entry to mention users Classification: Applications Product: NeoChat Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: shaloksha...@protonmail.ch CC: c...@carlschwan.eu Target Milestone: --- Created attachment 168972 --> https://bugs.kde.org/attachment.cgi?id=168972=edit Context menu On Discord, its very easy to tap on an username (on mobile clients) or right click on it, to open the context menu and choose an entry there, in order to paste his username into the text field. That is useful, when you like to mention someone, without replying to a specific post of them. I attach a screenshot, to illustrate, which context menu I mean. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 485892] Command line options from MPV do not work
https://bugs.kde.org/show_bug.cgi?id=485892 Matthias changed: What|Removed |Added Summary|Do not prevent playback |Command line options from |when unknown options are|MPV do not work |used| -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 485892] Do not prevent playback when unknown options are used
https://bugs.kde.org/show_bug.cgi?id=485892 Matthias changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REOPENED|RESOLVED --- Comment #7 from Matthias --- For future reference - since the maintainer seems to have another language than English as mother tongue - the MPV command line options translate into a different format: --sub-auto=all becomes set sub-auto fuzzy This could be documented, and best be provided as error message, when launched in the wrong format. Or obviously be translated. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 485892] Do not prevent playback when unknown options are used
https://bugs.kde.org/show_bug.cgi?id=485892 Matthias changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|NOT A BUG |--- --- Comment #6 from Matthias --- Do you even understand, what you are talking about? -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 485892] Do not prevent playback when unknown options are used
https://bugs.kde.org/show_bug.cgi?id=485892 Matthias changed: What|Removed |Added Ever confirmed|0 |1 Resolution|NOT A BUG |--- Status|RESOLVED|REOPENED --- Comment #4 from Matthias --- It does show the syntax that I use, and not the syntax that you suggest? Like... ?? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 485769] Autologin settings for SSD not read from kde_settings.conf correctly
https://bugs.kde.org/show_bug.cgi?id=485769 --- Comment #5 from Matthias --- Same with Oxygen and Breeze. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 485769] Autologin settings for SSD not read from kde_settings.conf correctly
https://bugs.kde.org/show_bug.cgi?id=485769 Matthias changed: What|Removed |Added CC||shaloksha...@protonmail.ch --- Comment #4 from Matthias --- Did we rule out, that this is the theme? -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 485892] Do not prevent playback when unknown options are used
https://bugs.kde.org/show_bug.cgi?id=485892 --- Comment #2 from Matthias --- https://mpv.io/manual/stable/#options-sub-auto -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 485892] New: Do not prevent playback when unknown options are used
https://bugs.kde.org/show_bug.cgi?id=485892 Bug ID: 485892 Summary: Do not prevent playback when unknown options are used Classification: Applications Product: Haruna Version: unspecified Platform: KaOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: shaloksha...@protonmail.ch Target Milestone: --- Created attachment 168741 --> https://bugs.kde.org/attachment.cgi?id=168741=edit My config SUMMARY Hi there. I use "--sub-auto=all" by default, and did set my desktop file to it. That does prevent me to open audio files now, since they dont know --sub-auto=all. This means, I can currently choose between a sane standard (imho) and not playing audio files. STEPS TO REPRODUCE 1. Set Haruna to use --sub-auto=all as the default command line option (MenuEdit) 2. Try to launch a music file 3. Wonder where your lovely music is OBSERVED RESULT No music/app does not open EXPECTED RESULT App does open Operating System: KaOS (2024) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-1-next (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800U with Radeon Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82L0 System Version: Yoga Slim 7 Carbon 14ACN6 -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 485042] Use subtitles in same directory as the movie
https://bugs.kde.org/show_bug.cgi?id=485042 --- Comment #3 from Matthias --- Its all srt files from opensubtitle. It does work with a baked in subtitle, so when it is part of the mkv file. mpv behaves weird: It either does not manage to open a file at all, or the OSD is not showing. Hnn, maybe related? -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 485042] Use subtitles in same directory as the movie
https://bugs.kde.org/show_bug.cgi?id=485042 --- Comment #2 from Matthias --- Created attachment 168596 --> https://bugs.kde.org/attachment.cgi?id=168596=edit Subtitle not loading -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 485644] Neochat: Screen shows no conversations or rooms, just spaces
https://bugs.kde.org/show_bug.cgi?id=485644 --- Comment #2 from Matthias --- No rooms appeared, when I would click on a space. I deleted the config, and got it working again. I am sorry, I just realized, I should have kept the old file, I guess. neochat 24.02.2 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 485644] New: Neochat: Screen shows no conversations or rooms, just spaces
https://bugs.kde.org/show_bug.cgi?id=485644 Bug ID: 485644 Summary: Neochat: Screen shows no conversations or rooms, just spaces Classification: Applications Product: NeoChat Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: shaloksha...@protonmail.ch CC: c...@carlschwan.eu Target Milestone: --- Created attachment 168590 --> https://bugs.kde.org/attachment.cgi?id=168590=edit Neochat OBSERVED RESULT Screen shows no conversations and channels anymore EXPECTED RESULT Conversations and rooms are shown. Operating System: KaOS (2024) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.6-1-next (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800U with Radeon Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82L0 System Version: Yoga Slim 7 Carbon 14ACN6 ADDITIONAL INFORMATION I think it had to do with the Plasma 6 update. I updated, and Neochat was still displaying all correctly. After I closed and opened the app, it seems to have resulted in this issue. To be sure, I rebooted and still, same result. Running the app from command line: ``` Reading access token from the keychain for "@shalokshalom:kde.org" quotient.main: The library is built with end-to-end encryption (E2EE) qrc:/org/kde/neochat/qml/main.qml:250:9: QML RoomListPage: Created graphical object was not placed in the graphics scene. quotient.jobs.thumbnail: 500 <- GET https://kde.modular.im/_matrix/media/v3/thumbnail/nixos.org/f4d22fb201b86281502301aea97c3c692c9ea2db quotient.jobs.thumbnail: "GetContentThumbnailJob" status NetworkError: Unexpected Error quotient.jobs.thumbnail: "GetContentThumbnailJob": retry #1 in 5 s ``` And sudo journalctl -b -p err ``` Apr 16 21:48:36 cosmos kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPC0.EC0.OKEC], AE_NOT_FOUND (20230628/psargs-330) Apr 16 21:48:36 cosmos kernel: ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20230628/psparse-529) Apr 16 21:48:42 cosmos bluetoothd[750]: Failed to load LTKs for hci0: Invalid Parameters (0x0d) Apr 16 21:48:42 cosmos bluetoothd[750]: Failed to load IRKs for hci0: Invalid Parameters (0x0d) Apr 16 21:48:45 cosmos systemd[826]: /run/user/1000/systemd/generator.late/app-xdg\x2duser\x2ddirs\x2dupdate@autostart.service:18: WorkingDirectory= path is not absolute, ignoring: Apr 16 21:48:45 cosmos bluetoothd[750]: src/gatt-database.c:database_add_chrc() Failed to create characteristic entry in database Apr 16 21:48:45 cosmos bluetoothd[750]: src/gatt-database.c:database_add_service() Failed to add characteristic Apr 16 21:48:45 cosmos bluetoothd[750]: src/gatt-database.c:database_add_app() Failed to add service Apr 16 21:48:45 cosmos bluetoothd[750]: src/gatt-database.c:client_ready_cb() Failed to create GATT service entry in local database Apr 16 21:48:46 cosmos kup-daemon[1224]: kup.daemon: "Kup is not enabled, enable it from the system settings module. You can do that by running kcmshell5 kup" ``` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474196] The blur effect does not work in Konsole when moving a window if the "Wobbly Window" effect is enabled
https://bugs.kde.org/show_bug.cgi?id=474196 Matthias Mueller changed: What|Removed |Added CC||mat.muel...@mailbox.org --- Comment #2 from Matthias Mueller --- Can confirm this (minus the flickering). Plasma 6.0.3 KF 6.0.0 QT 6.7.0 ArchLinux on AMDGPU -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 485298] Detect misconfigurations and automatically reset them
https://bugs.kde.org/show_bug.cgi?id=485298 --- Comment #2 from Matthias --- Do we not get the nessecary information by the TV? Forgive my ignorance, but this seems rather easy. The external display is not reporting back a healthy setup, and we act accordingly. How is the halting problem involved? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 485269] 'Unify output' using the OSD or widget leaves the system with no display output
https://bugs.kde.org/show_bug.cgi?id=485269 --- Comment #5 from Matthias --- So, I could reproduce this now on the Garuda and KaOS live ISOs. Both show again the same behavior: Wayland sessions get every time into a black screen on both the laptop and the TV. I tried it as well on X11, and both Garuda and KaOS show the same behavior as well. In this case, the OSD disappears, but no change is applied, and that counts for all options of the OSD. With Wayland, only the Unify button misbehaves, in X11 all of them show no effect at all. I should mention, that with both, Wayland and X11, I get an extended to the side view, when I start the live mode with the TV attached. That one works perfectly. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 485269] 'Unify output' using the OSD or widget leaves the system with no display output
https://bugs.kde.org/show_bug.cgi?id=485269 Matthias changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Matthias --- So, I just got this issue on Arch as well. Makes three independent distributions. This is definitely due to a recent update. I did this on a LG E9. Who knows, how many devices could possibly also effected. 3 Installations rendered unusable. I need another way of bugtracking this -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 485285] Countdown confirmation for the OSD and Plasma applet
https://bugs.kde.org/show_bug.cgi?id=485285 --- Comment #3 from Matthias --- *** Bug 484592 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 484592] External display rendered unusable due to misconfiguration
https://bugs.kde.org/show_bug.cgi?id=484592 Matthias changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Matthias --- *** This bug has been marked as a duplicate of bug 485285 *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 485298] New: Detect misconfigurations and automatically reset them
https://bugs.kde.org/show_bug.cgi?id=485298 Bug ID: 485298 Summary: Detect misconfigurations and automatically reset them Classification: Plasma Product: KScreen Version: 6.0.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- SUMMARY There are several cases of misconfigurations, who lead to parts of the monitor setup, or the entirety of it, as inaccessible. Those are major issues, since essentially the entire installation of the OS is not usable anymore, or certain hardware with that installation. I raised one proposal, that aims to prevent that by introducing a countdown/confirmation button to the OSD widget. Still, by accidentally confirming such an ill setup, this issue could occur as well. Also, the confirmation countdown could render the OSD/Plasma widget as cumbersome, since it is intended to provide a quick and easy way, to change the output device. This proposal intents to detect ill setups and automatically corrects them. Currently, KScreen and KWin are completely fine with establishing a connection, that results in a black screen so long as it had been confirmed by the KScreen KCM before. That results in several issues, where KScreen connects to a device, that is not showing any content, while simultaneously applying the ill configuration. So KScreen/Kwin definitely detects the hardware, and does act upon it, despite the hardware not showing any content. I am confident, that we can simply restore to a healthy default, when we detect that the output is not displayed at all? Or do (some) displays not even report this back? I mean, isnt there a way to read the resolution, etc, which would - assumingly - not be valid? Or maybe the refresh rate? Are there really displays out there, who report the values we might expect, despite not showing anything? Including my very own internal laptop display? Reference list: First issue: https://bugs.kde.org/show_bug.cgi?id=485269 Second issue: https://bugs.kde.org/show_bug.cgi?id=484592 Countdown feature proposal: https://bugs.kde.org/show_bug.cgi?id=485285 Thanks a lot -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 485269] 'Unify output' using the OSD or widget leaves the system with no display output
https://bugs.kde.org/show_bug.cgi?id=485269 --- Comment #3 from Matthias --- I have no idea, what caused this error. The error in 484592 is known and reproducible. This error also disables the main laptop screen, and renders the entire installation of the OS essentially inaccessible. The error in 484592 only renders the specific external device unusable. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484592] External display rendered unusable due to misconfiguration
https://bugs.kde.org/show_bug.cgi?id=484592 Matthias changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 485285] New: Countdown confirmation for the OSD and Plasma applet
https://bugs.kde.org/show_bug.cgi?id=485285 Bug ID: 485285 Summary: Countdown confirmation for the OSD and Plasma applet Classification: Plasma Product: KScreen Version: 6.0.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: OSD and Plasma applet Assignee: kscreen-bugs-n...@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- SUMMARY The OSD and Plasma widget has currently no confirmation timer, to avoid setting configurations, who happen to lead into issues. The KScreen KCM has such one, and this proposal is about adding that to the OSD/Plasma widget as well. Related: https://bugs.kde.org/show_bug.cgi?id=485269 https://bugs.kde.org/show_bug.cgi?id=484592 I would prefer, that configurations who are known to work, will not be asked for confirmation after the first time. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 485269] New: 'Unifying output' leaves the system with no display output
https://bugs.kde.org/show_bug.cgi?id=485269 Bug ID: 485269 Summary: 'Unifying output' leaves the system with no display output Classification: Plasma Product: KScreen Version: 6.0.3 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- SUMMARY I had a TV connected to my laptop, and chose only it as the shown output. Then I hit Fn + F7 to open the screen layout widget, and chose "Unify output". The result was a black screen on both the laptop and the TV. Removing the cable connection, was not restoring the display output on the laptop. Rebooting booted straight into a black screen as well. I booted into my second installation (first is KaOS, second NixOS) and tried the same thing there again, with the same outcome. This has to be due to a recent change, as I use both systems on a rolling release, and had used that feature in the past with the same hardware, and no such issue occurred. In this case, no user error was involved. Still, I managed to reach a similar bad state (with only the TV being inaccessible) with a bad configuration, that involved me confirming a display resolution for the TV as valid, that wasnt. In both cases, the simple usage of a multi monitor setup meant partly, or complete loss of display functionality. To make matters worse, kscreen is not a declarative file anymore. I think that is a very big mistake, and I strongly suggest to restore that functionality. Today, it seems that the entire display configuration is created by a binary, that then creates a yaml file. That one cannot be edited and reloaded. This goes against the UNIX philosophy and makes it very hard to restore from such a case. I would need to do dark magic, or have a rollback feature on filesystem level enabled, to recover from this. I thought about several mechanisms to prevent such issues. 1) Ask if the configuration is fine for the 'Screen Layout' widget as well. At least when the configuration involves new settings. Maybe when the API and/or hardware changes. 2.) Implement a shortcut, that resets the configuration to its default state. 3.) Implement such a button to reset the configuration in the KScreen KCM. This could have helped with the second case, where only the external display was inaccessible. I put this on major, and think it could be ranked more severe even. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 485043] Ctrl + ` doesnt work
https://bugs.kde.org/show_bug.cgi?id=485043 Matthias changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 485043] New: Ctrl + ` doesnt work
https://bugs.kde.org/show_bug.cgi?id=485043 Bug ID: 485043 Summary: Ctrl + ` doesnt work Classification: Applications Product: Haruna Version: unspecified Platform: KaOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: shaloksha...@protonmail.ch Target Milestone: --- Hi there :) Ctrl + ` does not open the Action Dialog for me. It works, when I set the right click to it, so I guess its only the keybinding. It is set in the settings, just doesnt trigger. STEPS TO REPRODUCE 1. Open Haruna 2. Press Ctrl + ` 3. Nothing happens OBSERVED RESULT Nothing happens EXPECTED RESULT Action dialog opens SOFTWARE/OS VERSIONS Operating System: KaOS (2024) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 Kernel Version: 6.7.9-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800U with Radeon Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82L0 System Version: Yoga Slim 7 Carbon 14ACN6 -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 485042] New: Use subtitles in same directory as the movie
https://bugs.kde.org/show_bug.cgi?id=485042 Bug ID: 485042 Summary: Use subtitles in same directory as the movie Classification: Applications Product: Haruna Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: shaloksha...@protonmail.ch Target Milestone: --- SUMMARY I am not quite sure, I understand, how subtitles are supposed to work in Haruna, so forgive me, if this is redundant. STEPS TO REPRODUCE 1. Open up a video 2. Have the subtitle in the same directory 3. Being unable to select it as a primary or secondary subtitle OBSERVED RESULT Subtitles have to be chosen as "external subtitle" EXPECTED RESULT Being able to load the subtitle easily. Operating System: KaOS (2024) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 Kernel Version: 6.7.9-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800U with Radeon Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82L0 System Version: Yoga Slim 7 Carbon 14ACN6 ADDITIONAL INFORMATION I am also confused by the default value in the settings. It says "Subs" in the field that is meant to contain a directory. What is this supposed to mean? There is no explanation to that, and it seems to serve no purpose. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 483495] Some commands are named differently in certain distros
https://bugs.kde.org/show_bug.cgi?id=483495 --- Comment #2 from Matthias --- To be honest, I think this is not on Kate to fix. Distros diverting from standards, and causing problems for others, should not be something that we support. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 484599] Name of UI element too long (Hide/Show Sidebar)
https://bugs.kde.org/show_bug.cgi?id=484599 --- Comment #6 from Matthias --- I am just confused -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 484599] Name of UI element too long (Hide/Show Sidebar)
https://bugs.kde.org/show_bug.cgi?id=484599 --- Comment #4 from Matthias --- So it will show 'Hide Sidebar' when open? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484592] External display rendered unusable due to misconfiguration
https://bugs.kde.org/show_bug.cgi?id=484592 --- Comment #3 from Matthias --- No. I missed to specify that, but the error occurs, when I confirm a configuration, that doesnt work. As you can read from my report, I am already in a situation, that prevents me from using that TV as an external display. There is no way, to restore its functionality so far as I can see. (Not even modifiying a text file can help, sincs that one is generated and cannot be modified seemingly.) The issue is, that the irrevertable action does not come with the KCM setting itself, but by using the Fn+F7 menu (dont know its name) with which you determine the output configuration. It allows you to choose between several options, among those: ) Switch to internal display ) Switch to external display ) Unify output ) Extend left ) Extend right If you choose to follow the steps outlined in the original report, and then choose 'Switch to external display' there is no way of changing the setup again. And plugging the device in, will always result in a black screen on both devices. Since it is only possible to edit it once plugged in, and plugging it in, it switches to 'external screen only' - even though that one is in an ill state. The TV rejects the format, and we seem to have no detection for that. Another possible solution would be, to never except such an illegal state in the first place. My TV does not accept a seemingly plausible resolution (2560 x 1440) and shows this on its screen. I dont know, if it reports this back on an API as well. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 484599] Name of UI element too long (Hide/Show Sidebar)
https://bugs.kde.org/show_bug.cgi?id=484599 --- Comment #2 from Matthias --- Do I understand this right, that the text now says 'Show Sidebar' both when its already open, and when its closed? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 484599] New: Name of UI element too long (Hide/Show Sidebar)
https://bugs.kde.org/show_bug.cgi?id=484599 Bug ID: 484599 Summary: Name of UI element too long (Hide/Show Sidebar) Classification: Applications Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- Created attachment 167845 --> https://bugs.kde.org/attachment.cgi?id=167845=edit UI Element SUMMARY The current name for the toolbar element to show and hide the sidebar is unnecessary long: Hide/Show the component sidebar This makes it uneasy, to use this as a dedicated button in the toolbar. (See screenshot) First, there is no other sidebar, so "component" is superfluous to begin with. Second, other buttons have the option to change, depending on the state. Like in Dolphin, where the "Split" element changes into "Close" and vice versa. We could implement, to do the same here. Otherwise, I suggest to rename the element simply into "Sidebar" and call it a day. Also consider, that this causes the translators to do work, so let us decide on this with foresight. :) Thanks a lot STEPS TO REPRODUCE 1. Open Kontact, switch to the KMail panel (I assume standalone Kmail is the same) 2. Add the 'Hide/Show the component sidebar' element to the toolbar. 3. Acknowledge, that it takes much space. Operating System: NixOS 24.05 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.6.22 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800U with Radeon Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484592] External display rendered unusable due to misconfiguration
https://bugs.kde.org/show_bug.cgi?id=484592 --- Comment #1 from Matthias --- Maybe we add kscreen-doctor to the KCM? (By the way, there is no component for KScreen here in the bugtracker) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484592] New: External display rendered unusable due to misconfiguration
https://bugs.kde.org/show_bug.cgi?id=484592 Bug ID: 484592 Summary: External display rendered unusable due to misconfiguration Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- SUMMARY I managed to setup the external TV in a way, that it is completely unusable from this installation. There is currently no GUI way, to restore its functionality as external display. I suggest to implement a functionality, that allows to configure previous output devices even when they are not connected. (Or at least restore their settings) STEPS TO REPRODUCE 1. Connect an external display 2. Choose an incompatible resolution (2560x1440) 3. Switch to it as the only output source (Fn+F7 in my case) I also set the TV as the primary display in the KCM, idk if thats important to replicate. OBSERVED RESULT Both devices stay black, once the TV is connected. EXPECTED RESULT Either the OS recognizing and accommodating for the issue, or providing an option to reset the ill setting manually before the connection happens. ab Operating System: NixOS 24.05 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.6.22 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800U with Radeon Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION I like to add, that the chosen resolution is not only made available by the KCM, it is also a theoretically compatible format (16:9 on this LG E9) So this can happen easily to common users. I actually replicated that based on an issue, that a friend of mine just experienced on Windows. Seems like we can do better here ;) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 392146] aarch64: unhandled instruction 0xD5380001 (MRS rT, mdir_el1)
https://bugs.kde.org/show_bug.cgi?id=392146 --- Comment #14 from Matthias Brugger --- I used to have a test for this, but I lost that over the last 6 years. But under "Implementation" https://bugs.kde.org/show_bug.cgi?id=482013 gives a code snipped that can be easily used to create a test. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482339] Tasks Show on incorrect screen after monitor reconnected
https://bugs.kde.org/show_bug.cgi?id=482339 Matthias Fehring changed: What|Removed |Added CC||buschman...@opensuse.org -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 478474] Kmail ask for sieve passworts on every start
https://bugs.kde.org/show_bug.cgi?id=478474 --- Comment #2 from Matthias Fehring --- I also tried to disable “Reuse host login configuration“. No matter if I use “IMAP user and password“ or give “User name and password“ in the Sieve config, it asks for the password when trying to connect to the Sieve server. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 478474] Kmail ask for sieve passworts on every start
https://bugs.kde.org/show_bug.cgi?id=478474 Matthias Fehring changed: What|Removed |Added CC||buschman...@opensuse.org --- Comment #1 from Matthias Fehring --- Same here with kmail2 6.0.0 (24.02.0) on Plasma 6.0.1 and KDE Frameworks 6.0.0. Log shows the following lines for every account: We have an error during reading password "Entry not found" org.kde.pim.kmail: An error occurred while reading password: "Entry not found" -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 483495] New: Some commands are named differently in certain distros
https://bugs.kde.org/show_bug.cgi?id=483495 Bug ID: 483495 Summary: Some commands are named differently in certain distros Classification: Applications Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- Created attachment 167136 --> https://bugs.kde.org/attachment.cgi?id=167136=edit Discussion in chat SUMMARY Some of the LSP commands are renamed at the packaging level of some distros. It seems they had contributed the original config for vscode language server of css and html, at least. See screenshot P.S: Kate has no LSP component here in the bug tracker. I think its worth it, doing one. Operating System: NixOS 24.05 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.0 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800U with Radeon Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479712] Plasma 6's SNI implementation doesn't respect the IconThemePath property
https://bugs.kde.org/show_bug.cgi?id=479712 Matthias changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #17 from Matthias --- Sorry, we failed. That issue here is indeed solved and we encountered an independent problem in Qbittorrent. Closing -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479712] Plasma 6's SNI implementation doesn't respect the IconThemePath property
https://bugs.kde.org/show_bug.cgi?id=479712 --- Comment #16 from Matthias --- Created attachment 166894 --> https://bugs.kde.org/attachment.cgi?id=166894=edit missing icon in 6.0.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479712] Plasma 6's SNI implementation doesn't respect the IconThemePath property
https://bugs.kde.org/show_bug.cgi?id=479712 Matthias changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED CC||shaloksha...@protonmail.ch --- Comment #15 from Matthias --- At least two people on 6.0.1 confirm that this bug is still active. Tested with QBittorrent. NixOS and Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481912] Feature request: Wayland remote login sessions with Plasma, like xrdp
https://bugs.kde.org/show_bug.cgi?id=481912 Matthias K. changed: What|Removed |Added CC||matth...@tenstral.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481912] New: Feature request: Wayland remote login sessions with Plasma, like xrdp
https://bugs.kde.org/show_bug.cgi?id=481912 Bug ID: 481912 Summary: Feature request: Wayland remote login sessions with Plasma, like xrdp Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Session Management Assignee: plasma-b...@kde.org Reporter: matth...@tenstral.net Target Milestone: 1.0 Hi everyone! (I was asked to report the feature request here to keep track of it, since it affects multiple desktop components under Wayland) I work at a research lab where we have very powerful servers connected to large data storage via a fast link. A lot of image processing as well as simulations are run on these machines, and it is incredibly convenient as people can take a working environment with them, and we also can share an expensive system extremely efficiently among many scientists. This is how it is set up currently: 1. The user ssh-tunnels into the server they want to connect to (RDP ports are not exposed) 2. A RDP connection to xrdp[1] is created 3. xrdp-sesman[2], the session manager module of xrdp, creates a session for the user after authenticating them 4. Plasma/X11 is started for that user session and renders to the remote display, instead of an actual display If a user disconnects, the session is kept running, and they get their session back as soon as they log in again. To terminate a session, the user has to log out explicitly. We are also utilizing Apache Guacamole[3] to make this process even more convenient so people can avoid installing any additional software and get almost the same experience as if they were using e.g. Remmina[4] to connect remotely. Of course, this complete workflow will not work at all when Plasma is running on Wayland, and XRDP, as the name suggests, is very X.org-specific (it is a fantastic tool though and serves us well). In the long run it would be great if we could switch to Wayland and keep using Plasma (surprisingly, if stripped down just slightly Plasma is not much heavier than light desktops, and users like to use the desktop's tools, e.g. the Dolphin filemanager). GNOME has a remote login in the works that looks similar to what XRDP provides and works on Wayland[5], but it would be fantastic if KDE could provide a similar feature. Having any XDG portals or interactivity will not work - as soon as the user is authenticated, they should get a session noninteractively and there should not be a need to stay logged in for the session to continue to exist (the servers are headless, and if needed, the admin can always set session resource limits for users via logind). A feature like this could for example be implemented by having a system service that takes incoming RDP connections and uses SDDM to authenticate and spawn a new Wayland session that can be interacted with using the transient seat protocol. Or if SDDM is too heavy, some lightweight service to handle the session authentication part. In any case, this will require non-trivial work on a lot of components, and there's likely multiple ways to implement this feature (and it wouldn't even necessarily have to be RDP-based, but we found the protocol to be a bit more efficient than VNC in testing). Thanks to everyone for the phantastic work on Plasma! Cheers, Matthias [1]: https://www.xrdp.org/ [2]: https://manpages.debian.org/testing/xrdp/xrdp-sesman.8.en.html [3]: https://guacamole.apache.org/ [4]: https://remmina.org/ [5]: https://wiki.gnome.org/Initiatives/Wayland/Remoting#Remote_Login -- 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 Matthias Mailänder changed: What|Removed |Added CC||matth...@mailaender.name --- Comment #104 from Matthias Mailänder --- Reported downstream https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/2055195 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478347] Pictures from old collection (network share) still in database after removing it
https://bugs.kde.org/show_bug.cgi?id=478347 Matthias Brändli changed: What|Removed |Added CC||matthias.braen...@mpb.li --- Comment #7 from Matthias Brändli --- Hello, I had a similar issue. I had added a read-only mounted external image collection, and then removed it again before it terminated scanning all entries. No "null album" visible, but picture placeholders (no thumbnails) in the timeline. The database still contained albums referring to the non-existing AlbumRoot. I have made a backup copy of digikam4.db and have executed `DELETE from Albums WHERE albumRoot <> 1;`, which fixed the problem for me. As Maik said it's ok to have Images with NULL album, I didn't clean up anything else. Cheers Matthias -- You are receiving this mail because: You are watching all bug changes.
[kfind] [Bug 430437] Copy from KFind to Dolphin with multiple files
https://bugs.kde.org/show_bug.cgi?id=430437 Matthias changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WORKSFORME |FIXED --- Comment #3 from Matthias --- Yep, resolved -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 471036] disInstr_AMD64: disInstr miscalculated next %rip on RORX imm8, m32/64, r32/64
https://bugs.kde.org/show_bug.cgi?id=471036 Matthias Schwarzott changed: What|Removed |Added Attachment #165688|0 |1 is obsolete|| --- Comment #5 from Matthias Schwarzott --- Created attachment 165691 --> https://bugs.kde.org/attachment.cgi?id=165691=edit Show more context (rip, instr bytes, vex-disasm trace) for this panic case Even more context for the error case (idea how to rerun disInstr_AMD64_WRK taken from the expect_CAS case below): current %rip = 0x109ABE assumed next %rip = 0x109AC7 actual next %rip = 0x109AC8 instruction bytes: 0xC4 0xE3 0xFB 0xF0 0xD 0x60 0x45 0x0 0x0 0x43 0x109ABE: rorx 67,17760(%rip),%rcx vex: the `impossible' happened: disInstr_AMD64: disInstr miscalculated next %rip -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 471036] disInstr_AMD64: disInstr miscalculated next %rip on RORX imm8, m32/64, r32/64
https://bugs.kde.org/show_bug.cgi?id=471036 --- Comment #4 from Matthias Schwarzott --- I tested the attachment "Example patch for guest_amd64_toIR" https://bugs.kde.org/attachment.cgi?id=159662 It perfectly fixes the problem. Without fix (but extended context-printing) the extended bmi testcase fails like this: shrx32 -> current %rip = 0x109ABE assumed next %rip = 0x109AC7 actual next %rip = 0x109AC8 instruction bytes: 0xC4 0xE3 0xFB 0xF0 0xD 0x60 0x45 0x0 0x0 0x43 vex: the `impossible' happened: disInstr_AMD64: disInstr miscalculated next %rip vex storage: T total 171126616 bytes allocated vex storage: P total 512 bytes allocated valgrind: the 'impossible' happened: LibVEX called failure_exit(). host stacktrace: ==20396==at 0x5804383A: show_sched_status_wrk (m_libcassert.c:407) ==20396==by 0x58043957: report_and_quit (m_libcassert.c:478) ==20396==by 0x58043BAB: panic (m_libcassert.c:554) ==20396==by 0x58043BAB: vgPlain_core_panic_at (m_libcassert.c:559) ==20396==by 0x58043BCA: vgPlain_core_panic (m_libcassert.c:564) ==20396==by 0x58058034: failure_exit (m_translate.c:761) ==20396==by 0x5813068A: vpanic (main_util.c:253) ==20396==by 0x581BBDDD: disInstr_AMD64 (guest_amd64_toIR.c:32714) ==20396==by 0x58148E76: disassemble_basic_block_till_stop.constprop.0 (guest_generic_bb_to_IR.c:956) ==20396==by 0x5814965C: bb_to_IR (guest_generic_bb_to_IR.c:1365) ==20396==by 0x5812D6AF: LibVEX_FrontEnd (main_main.c:583) ==20396==by 0x5812E00C: LibVEX_Translate (main_main.c:1235) ==20396==by 0x5805A791: vgPlain_translate (m_translate.c:1831) ==20396==by 0x58097F3B: handle_chain_me (scheduler.c:1164) ==20396==by 0x5809A42B: vgPlain_scheduler (scheduler.c:1531) ==20396==by 0x580E5569: thread_wrapper (syswrap-linux.c:102) ==20396==by 0x580E5569: run_a_thread_NORETURN (syswrap-linux.c:155) sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 20396) ==20396==at 0x1099FC: do_rorx64 (bmi.c:379) ==20396==by 0x10AEDC: main (bmi.c:1012) client stack range: [0x1FFEFFD000 0x1FFF000FFF] client SP: 0x1FFEFFF258 valgrind stack range: [0x1002DEB000 0x1002EEAFFF] top usage: 10960 of 1048576 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 471036] disInstr_AMD64: disInstr miscalculated next %rip on RORX imm8, m32/64, r32/64
https://bugs.kde.org/show_bug.cgi?id=471036 --- Comment #3 from Matthias Schwarzott --- Created attachment 165690 --> https://bugs.kde.org/attachment.cgi?id=165690=edit Add rorx rip-relative testcase to bmi.c Adding these instructions to the bmi testcase: 1abe: c4 e3 fb f0 0d 60 45rorx $0x43,0x4560(%rip),%rcx# 6028 1ac5: 00 00 43 1bf9: c4 e3 7b f0 0d 2d 44rorx $0x43,0x442d(%rip),%ecx# 6030 1c00: 00 00 43 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 471036] disInstr_AMD64: disInstr miscalculated next %rip on RORX imm8, m32/64, r32/64
https://bugs.kde.org/show_bug.cgi?id=471036 Matthias Schwarzott changed: What|Removed |Added CC||z...@gentoo.org --- Comment #2 from Matthias Schwarzott --- Created attachment 165688 --> https://bugs.kde.org/attachment.cgi?id=165688=edit Show more context (rip and instr bytes) for this panic case -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 480206] New: Add Julia LSP support
https://bugs.kde.org/show_bug.cgi?id=480206 Bug ID: 480206 Summary: Add Julia LSP support Classification: Applications Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: task Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- SUMMARY Hi there. This Wiki contains the code needed to enable support for the LSP of Julia. https://github.com/julia-vscode/LanguageServer.jl/wiki/Kate#custom-lsp-setting As you can see, is all what the user needs to do, is to run: 1. julia 2. ] 3. add LanguageServer Ideally, we could run those lines initially as well, but I think its the policy of Kate, to let that to the user entirely. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480159] Add option to make Caps lock key a 'bindable' key (F12)
https://bugs.kde.org/show_bug.cgi?id=480159 Matthias changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|NOT A BUG |--- Ever confirmed|0 |1 --- Comment #2 from Matthias --- So far as I understand, is this dependent on X11 and considering we phase that out, is it wise to find a solution that doesnt require a component of X11, right? I guess there will be a replacement for the whole Advanced tab. I am more looking for a solution, that can actually be accieved within Plasma and not some external component. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480161] Add entry "move windows to other screen" to shortcuts
https://bugs.kde.org/show_bug.cgi?id=480161 --- Comment #1 from Matthias --- Created attachment 165125 --> https://bugs.kde.org/attachment.cgi?id=165125=edit Move windows to other screen -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480161] New: Add entry "move windows to other screen" to shortcuts
https://bugs.kde.org/show_bug.cgi?id=480161 Bug ID: 480161 Summary: Add entry "move windows to other screen" to shortcuts Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- SUMMARY Hi there :) I like to move my windows with a shortcut. The functionality for it is there, seen in the screenshot. Currently only available with the mouse. Thanks a lot Sidenote: The systemsettings product category here in the Bugtracker misses the kcm_shortcuts component. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480159] New: Add option to make Caps lock key a 'bindable' key (F12)
https://bugs.kde.org/show_bug.cgi?id=480159 Bug ID: 480159 Summary: Add option to make Caps lock key a 'bindable' key (F12) Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_keyboard Assignee: plasma-b...@kde.org Reporter: shaloksha...@protonmail.ch CC: butir...@gmail.com, natalie_clar...@yahoo.de Target Milestone: --- Created attachment 165119 --> https://bugs.kde.org/attachment.cgi?id=165119=edit Example of the category SUMMARY I like to bind Yakuake to Caps lock. In order to do this, I need two things: Disable the normal caps lock behavior (why the heck isnt this default :P) and do bind it instead to a key, that can be used to create a shortcut. I add the following suggestion to the project: Please create an entry in Keyboard > Advanced > Caps lock behavior (why are there two entries of this category?) and let this entry say and do: Caps lock sends F12 F12 is used to bind any application to caps lock really, and it could also be another key. (But really, use F12, its the default and established key to launch Yakuake and generally a good generic key to bind things to. People who dont use Yakuake, have it free for other things.) It could also be a custom key, but considering there is no such example in the whole KCM yet for it, I imagine the API for it has not been implemented or written yet, or it is against a design decision. Thanks STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478838] Plasmashell sometimes crashes in QPlatformWindow::hasPendingUpdateRequest() after or during screen being turned off
https://bugs.kde.org/show_bug.cgi?id=478838 Matthias Dahl changed: What|Removed |Added CC||ua_bugz_kde@binary-island.e ||u -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467074] When returning from screen energy saving, Plasma forgets that an external screen is connected and doesn't assign it a containment
https://bugs.kde.org/show_bug.cgi?id=467074 Matthias Dahl changed: What|Removed |Added CC||ua_bugz_kde@binary-island.e ||u -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477941] Plasma crashes in ShellCorona::createWaitingPanels() after connecting the external display
https://bugs.kde.org/show_bug.cgi?id=477941 Matthias Dahl changed: What|Removed |Added CC||ua_bugz_kde@binary-island.e ||u -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478700] kwin_wayland + NVIDIA modesetting - Atomic commits failed (and crash)
https://bugs.kde.org/show_bug.cgi?id=478700 Matthias Dahl changed: What|Removed |Added CC||ua_bugz_kde@binary-island.e ||u -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share
https://bugs.kde.org/show_bug.cgi?id=451050 --- Comment #38 from Matthias Gruß --- Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f493e91f5c8 in KCoreDirListerCache::slotUpdateResult(KJob*) () at /lib64/libKF5KIOCore.so.5 #5 0x7f493cce8871 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #6 0x7f493e0e6706 in KJob::result(KJob*, KJob::QPrivateSignal) () at /lib64/libKF5CoreAddons.so.5 #7 0x7f493e0ec5bb in KJob::finishJob(bool) () at /lib64/libKF5CoreAddons.so.5 #8 0x7f493cce8871 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #9 0x7f493e8c5bc8 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () at /lib64/libKF5KIOCore.so.5 #10 0x7f493e8c07fb in KIO::SlaveInterface::dispatch() () at /lib64/libKF5KIOCore.so.5 #11 0x7f493e8c3251 in KIO::Slave::gotInput() () at /lib64/libKF5KIOCore.so.5 #12 0x7f493cce8871 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #13 0x7f493ccdf11b in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #14 0x7f493d9aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #15 0x7f493ccb4598 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #16 0x7f493ccb7a45 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #17 0x7f493cd06fef in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #18 0x7f493a912e5c in g_main_context_dispatch_unlocked.lto_priv () at /lib64/libglib-2.0.so.0 #19 0x7f493a96ddd8 in g_main_context_iterate_unlocked.isra () at /lib64/libglib-2.0.so.0 #20 0x7f493a910ad3 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #21 0x7f493cd06ad9 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #22 0x7f493ccb2f5b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #23 0x7f493ccbb1eb in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #24 0x559e85ff9055 in main () [Inferior 1 (process 5596) detached] -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share
https://bugs.kde.org/show_bug.cgi?id=451050
--- Comment #37 from Matthias Gruß ---
In my case, it is about the share on a Synology NAS.
After calling smb://192.168.2.150/ the login and password are requested.
Output in the terminal when calling without slash (192.168.2.150):
matthias@fedora-notebook:~$ dolphin
kf.kio.core: Internal error: itemsInUse did not contain
QUrl("smb://matsch@192.168.2.150/")
KCrash: Application 'dolphin' crashing...
KCrash: Attempting to start /usr/libexec/drkonqi
kf5idletime_wayland: This plugin does not support polling idle time
[1]+ Angehalten dolphin
Output of coredumpctl info dolphin:
PID: 3861 (dolphin)
UID: 1000 (matthias)
GID: 1000 (matthias)
Signal: 11 (SEGV)
Timestamp: Thu 2023-11-30 08:57:15 CET (5 days ago)
Command Line: /usr/bin/dolphin
Executable: /usr/bin/dolphin
Control Group:
/user.slice/user-1000.slice/user@1000.service/app.slice/app-\x2fusr\x2fbin\x2fdolphin-2a68a52399074d6baf01951b89126bdd.scope
Unit: user@1000.service
User Unit:
app-\x2fusr\x2fbin\x2fdolphin-2a68a52399074d6baf01951b89126bdd.scope
Slice: user-1000.slice
Owner UID: 1000 (matthias)
Boot ID: 04f8632289b54a5fa2947f45f8271790
Machine ID: 5db137b5cf784732be137c6dcb9329d1
Hostname: fedora-notebook
Storage:
/var/lib/systemd/coredump/core.dolphin.1000.04f8632289b54a5fa2947f45f8271790.3861.170133103500.zst
(missing)
Package: dolphin/23.08.3-1.fc39
build-id: 196e791b2c06aeee903690cac5e4b3b9a7aaeb66
Message: Process 3861 (dolphin) of user 1000 dumped core.
Module kio_file.so from rpm kf5-kio-5.111.0-1.fc39.x86_64
Module libxdg-shell.so from rpm
qt5-qtwayland-5.15.11-1.fc39.x86_64
Module libwebpdemux.so.2 from rpm libwebp-1.3.2-2.fc39.x86_64
Module libwebpmux.so.3 from rpm libwebp-1.3.2-2.fc39.x86_64
Module libqwebp.so from rpm
qt5-qtimageformats-5.15.11-1.fc39.x86_64
Module libqwbmp.so from rpm
qt5-qtimageformats-5.15.11-1.fc39.x86_64
Module libjbig.so.2.1 from rpm jbigkit-2.1-26.fc39.x86_64
Module libLerc.so.4 from rpm liblerc-4.0.0-4.fc39.x86_64
Module libwebp.so.7 from rpm libwebp-1.3.2-2.fc39.x86_64
Module libtiff.so.5 from rpm libtiff-4.4.0-8.fc39.x86_64
Module libqtiff.so from rpm
qt5-qtimageformats-5.15.11-1.fc39.x86_64
Module libqsvg.so from rpm qt5-qtsvg-5.15.11-1.fc39.x86_64
Module libmng.so.2 from rpm libmng-2.0.3-19.fc39.x86_64
Module libqmng.so from rpm
qt5-qtimageformats-5.15.11-1.fc39.x86_64
Module libqjpeg.so from rpm qt5-qtbase-5.15.11-7.fc39.x86_64
Module libqjp2.so from rpm
qt5-qtimageformats-5.15.11-1.fc39.x86_64
Module libqico.so from rpm qt5-qtbase-5.15.11-7.fc39.x86_64
Module libqicns.so from rpm
qt5-qtimageformats-5.15.11-1.fc39.x86_64
Module libqgif.so from rpm qt5-qtbase-5.15.11-7.fc39.x86_64
Module kimg_xcf.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module kimg_tga.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module kimg_rgb.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module liblcms2.so.2 from rpm lcms2-2.15-2.fc39.x86_64
Module libjasper.so.6 from rpm jasper-3.0.6-4.fc39.x86_64
Module libjpeg.so.62 from rpm libjpeg-turbo-2.1.4-3.fc39.x86_64
Module libraw.so.23 from rpm LibRaw-0.21.1-5.fc39.x86_64
Module kimg_raw.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module kimg_ras.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module kimg_qoi.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module kimg_psd.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module kimg_pic.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module kimg_pcx.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module kimg_ora.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module kimg_kra.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module libjxl_threads.so.0.8 from rpm
jpegxl-0.8.2-3.fc39.x86_64
Module kimg_jxl.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module libsharpyuv.so.0 from rpm libwebp-1.3.2-2.fc39.x86_64
Module libheif.so.1 from rpm libheif-1.16.2-2.fc39.x86_64
Module kimg_heif.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module kimg_hdr.so from rpm
kf5-kimageformats-5.111.0-1.fc39.x86_64
Module libIlmThread-3_1.so.30 from rpm
openexr-3.1.10-2.fc39.x86_64
Module libIex-3_1.so.30 from rpm openexr-3.1.10-2.f
[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share
https://bugs.kde.org/show_bug.cgi?id=451050 --- Comment #34 from Matthias Gruß --- Dolphin 23.08.3 on Fedora 39 KDE Plasma. smb://192.168.2.150 crashes Dolphin, smb://192.168.2.150/ works fine. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share
https://bugs.kde.org/show_bug.cgi?id=451050 --- Comment #32 from Matthias Gruß --- The bug occurs reproducibly for me if I do not end the IP address with a slash. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share
https://bugs.kde.org/show_bug.cgi?id=451050 Matthias Gruß changed: What|Removed |Added CC||matthiasgr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477417] Dolphin crashes upon connecting to SMB share
https://bugs.kde.org/show_bug.cgi?id=477417 Matthias Gruß changed: What|Removed |Added CC||matthiasgr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 477764] New: Dark mode for KHelpcenter
https://bugs.kde.org/show_bug.cgi?id=477764 Bug ID: 477764 Summary: Dark mode for KHelpcenter Classification: Applications Product: khelpcenter Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- SUMMARY Currently, I see no way to read KHelpcenter with a black background. STEPS TO REPRODUCE 1. Open KHelpcenter 2. Try to make the screen not flood your eyes with bright light Particularly in the night, when I have everything dark - Browser and Webpages, Plasma, and all other apps, is this convenient. Thanks a lot ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477052] New: Plasma 6: Desktop Effects > Appearance
https://bugs.kde.org/show_bug.cgi?id=477052 Bug ID: 477052 Summary: Plasma 6: Desktop Effects > Appearance Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- SUMMARY The massive amount of desktop effects are purely cosmetic changes, so I claim that they fit under the Appearance category. They do not change the behavior of the system in any meaningful way, and its counter-intuitive to place it there. I see the change to Plasma 6 as an opportunity, to change this. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476878] New: Missed string highlight in Nix file
https://bugs.kde.org/show_bug.cgi?id=476878
Bug ID: 476878
Summary: Missed string highlight in Nix file
Classification: Applications
Product: kate
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: scripting
Assignee: kwrite-bugs-n...@kde.org
Reporter: shaloksha...@protonmail.ch
Target Milestone: ---
Created attachment 163074
--> https://bugs.kde.org/attachment.cgi?id=163074=edit
String not highlighted
SUMMARY
The string in line 4 is not highlighted as such:
```nix
programs.firefox = {
enable = true;
preferences = {
"widget.use-xdg-desktop-portal.file-picker" = 1;
"widget.use-xdg-desktop-portal.mime-handler" = 1;
"browser.backspace_action" = 0;
};
};
```
STEPS TO REPRODUCE
1. Open file
2. Paste above content into it
3. Name it blabla.nix or set file type to Nix
4. Look at line 4
OBSERVED RESULT
String not highlighted
EXPECTED RESULT
String highlighted as all the other strings
Operating System: NixOS 23.05
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.10
Kernel Version: 6.6.0 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 5800U with Radeon Graphics
Memory: 13,5 GiB of RAM
Graphics Processor: AMD Radeon Graphics
ADDITIONAL INFORMATION
See screenshot
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 475933] Fish syntax reported falsely as error
https://bugs.kde.org/show_bug.cgi?id=475933 --- Comment #5 from Matthias --- Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 473539] Double binding of a shortcut with varying results
https://bugs.kde.org/show_bug.cgi?id=473539 --- Comment #6 from Matthias --- Created attachment 162919 --> https://bugs.kde.org/attachment.cgi?id=162919=edit Screenshot 2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 473539] Double binding of a shortcut with varying results
https://bugs.kde.org/show_bug.cgi?id=473539 --- Comment #5 from Matthias --- I think I can add to that issue, that Plasma indeed has some functionality, that circumvents the conflict of some double use of shortcuts. One way it is doing that, is by differentiating in which app window the shortcut is called. I ran into another issue, that shows that this functionality seems to be working, and another part of the logic is dysfunctional. I have, on a relatively standard NixOS, observed the following behavior: Screenshot 2 This shows the Ctrl+Shift+S behavior not working out of the box, showing the same error as we saw it with Shift+Del before. In this case, no Shortcut besides the intended one is even configured with this binding. Funnily enough, looking into "Custom Shortcuts" it reveals that no such shortcut is set there as well. But removing all the ticks from the preset "KMenuEdit" and "Konqueror Gestures" solved the conflict. Note, that I reapplied those ticks afterwards, and saved it. Now, the conflict does not happen anymore. -- You are receiving this mail because: You are watching all bug changes.
[kfind] [Bug 430437] Copy from KFind to Dolphin with multiple files
https://bugs.kde.org/show_bug.cgi?id=430437 Matthias changed: What|Removed |Added Summary|Copy from KFile to Dolphin |Copy from KFind to Dolphin |with multiple files |with multiple files -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476346] New: MainToolbar entries show up after MainToolbar
https://bugs.kde.org/show_bug.cgi?id=476346 Bug ID: 476346 Summary: MainToolbar entries show up after MainToolbar Classification: Applications Product: kate Version: unspecified Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- Created attachment 162749 --> https://bugs.kde.org/attachment.cgi?id=162749=edit Screenshot SUMMARY See for yourself via the provided screenshot STEPS TO REPRODUCE 1. Edit the default toolbar 2. Add an entry to MainToolbar 3. See that it pops up next to the entries OBSERVED RESULT Open Recent shows up next to "Redo" EXPECTED RESULT Open Recent shows up next to "Open" Operating System: NixOS 23.05 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.10 Kernel Version: 6.1.57 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5800U with Radeon Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476099] Nuspell and Enchant not recognized
https://bugs.kde.org/show_bug.cgi?id=476099 --- Comment #1 from Matthias --- The doc page I am referencing to: https://docs.kde.org/stable5/en/khelpcenter/fundamentals/spellcheck.html -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476099] New: Nuspell and Enchant not recognized
https://bugs.kde.org/show_bug.cgi?id=476099 Bug ID: 476099 Summary: Nuspell and Enchant not recognized Classification: Applications Product: kate Version: 23.08.1 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- SUMMARY Nuspell, an alternative Hunspell implementation is not recognized. Enchant, an officially supported spellcheck library is not recognized. STEPS TO REPRODUCE 1. Install nuspell, enchant and hunspell-en_us (do not install hunspell) 2. Launch Kate 3. See that no backend is available Operating System: Garuda Linux KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.8-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 7,4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: HP Product Name: HP EliteBook 820 G3 ADDITIONAL INFORMATION This doc specifically mentions Enchant and nuspell should work everywhere, where hunspell works https://nuspell.github.io/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349785] Intelligent auto-hide mode ("Dodge Windows") that hides the panel only when windows are maximized or move over it
https://bugs.kde.org/show_bug.cgi?id=349785 --- Comment #36 from Matthias --- I feel like this is bad communication by now. First, I invested quite some time into tracking and documenting half a dozen issues related to "windows can cover" and it does seem, it is essentially unmaintained for quite some time now. If it was clear that it was gonna be discontinued, a little note could have helped, at least when I issued the first "windows can cover issue" Then, you seem to discontinue one feature, to introduce another one that does almost the same thing: I don't see the point here at all. How is "hiding" different from "can be covered" Does it animate the hide? I am a bit puzzled, as to what I should expect. To me, that smells like the previous version was just a messy implementation, and now we are launching the same product under a different name to address that. Also in order to clarify the state for other contributors as well, I would welcome a public statement around that issue, thanks a lot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475563] Panel in "Windows Can Cover" mode disappears in Wayland
https://bugs.kde.org/show_bug.cgi?id=475563 --- Comment #10 from Matthias --- So in Plasma5, it will remain broken? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349785] Intelligent auto-hide mode ("Dodge Windows") that hides the panel only when windows are maximized or move over it
https://bugs.kde.org/show_bug.cgi?id=349785 Matthias changed: What|Removed |Added CC||shaloksha...@protonmail.ch --- Comment #31 from Matthias --- How is "intelligent autohide" different from the now-implemented "Windows can cover" Is there any difference in functionality? Or is this simply a new name, a new implementation, and the same functionality? -- You are receiving this mail because: You are watching all bug changes.
