[dolphin] [Bug 364957] Add a pause button in Dolphins sidepanel
https://bugs.kde.org/show_bug.cgi?id=364957 Matthias changed: What|Removed |Added Summary|add a pause button or |Add a pause button in |change the stop button to a |Dolphins sidepanel |pause button| -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 360170] Failed with error while ripping DVD (may be encrypted DVD)
https://bugs.kde.org/show_bug.cgi?id=360170 --- Comment #14 from Matthias --- 2 Months without any answer, correct? -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 360170] Failed with error while ripping DVD (may be encrypted DVD)
https://bugs.kde.org/show_bug.cgi?id=360170 --- Comment #16 from Matthias --- yeah, 4 years no updates, so is this a surprise..? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 372919] New: Recreate the old transition dialog
https://bugs.kde.org/show_bug.cgi?id=372919 Bug ID: 372919 Summary: Recreate the old transition dialog Product: dolphin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: shaloksha...@riseup.net Target Milestone: --- Created attachment 102438 --> https://bugs.kde.org/attachment.cgi?id=102438&action=edit Old file dialog Recreate the old transition dialog: http://funkyimg.com/i/2k7H8.jpg -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 372920] New: Recreate the old transition dialog
https://bugs.kde.org/show_bug.cgi?id=372920 Bug ID: 372920 Summary: Recreate the old transition dialog Product: dolphin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: shaloksha...@riseup.net Target Milestone: --- Recreate the old transition dialog: http://funkyimg.com/i/2k7H8.jpg -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 372920] Create an option to enable the old transition dialog
https://bugs.kde.org/show_bug.cgi?id=372920 Matthias changed: What|Removed |Added Summary|Recreate the old transition |Create an option to enable |dialog |the old transition dialog -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 372920] Recreate the old transition dialog
https://bugs.kde.org/show_bug.cgi?id=372920 --- Comment #1 from Matthias --- Ah, its actually already implemented. Its a bit hidden: Disable the notifications for file transfer did it. Can we think about another option, like in Dolphins settings menu? -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 355168] Launch Phonon KCM once a digital audio/video device is detected
https://bugs.kde.org/show_bug.cgi?id=355168 --- Comment #3 from Matthias --- Do what you think is suitable, so long as the current situation change. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 450638] New: Provide checkbox to allow overlapping by the sidebar
https://bugs.kde.org/show_bug.cgi?id=450638 Bug ID: 450638 Summary: Provide checkbox to allow overlapping by the sidebar Product: digikam Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Showfoto-Thumbs Assignee: digikam-bugs-n...@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- Created attachment 146992 --> https://bugs.kde.org/attachment.cgi?id=146992&action=edit Sidebar is under the thumbbar SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I like that the sidebar can overlap the Thumbnails. Optimally, the Thumbbar automatically rescales. STEPS TO REPRODUCE 1. Open Thumbnails 2. Open Stack or Foldersview 3. See Result OBSERVED RESULT See Attachment EXPECTED RESULT Sidebar not covered by the thumbbar SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.23 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 450638] Provide checkbox to allow overlapping by the sidebar
https://bugs.kde.org/show_bug.cgi?id=450638 Matthias changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Matthias --- Oh, I figured it out. When you double click the lock/unlock zone, it moves back into place. I probably unlocked that, some time ago and didnt notice. It might make sense, to put a distinct button on it. Since that was it, what I was looking for. Thanks -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 450642] New: Provide an option to open the light table after click on thumbnail
https://bugs.kde.org/show_bug.cgi?id=450642 Bug ID: 450642 Summary: Provide an option to open the light table after click on thumbnail Product: digikam Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Thumbs-Image Assignee: digikam-bugs-n...@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- Created attachment 146995 --> https://bugs.kde.org/attachment.cgi?id=146995&action=edit Settings menu Currently, we provide the option to open the editor, preview and another application, when the user clicks on a thumbnail. I suggest, to also add the option to open that in lighttable. Also consider putting that option in the setup wizard. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 450643] New: Expose menus optionally in the toolbar
https://bugs.kde.org/show_bug.cgi?id=450643 Bug ID: 450643 Summary: Expose menus optionally in the toolbar Product: digikam Version: 7.5.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability-Ergonomy Assignee: digikam-bugs-n...@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- Created attachment 146996 --> https://bugs.kde.org/attachment.cgi?id=146996&action=edit proposal Summary I know about the tools sidebar. Still, particularity new users and people who use Showfoto find that placement to hard to be seen. The menu bar itself is on many systems put into the window bar, in order to save space. I suggest to make some menu entries (color, enhance, transform) available in the toolbar. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 450643] Expose menus optionally in the toolbar : burger main menu feature
https://bugs.kde.org/show_bug.cgi?id=450643 --- Comment #2 from Matthias --- Oh yeah, thanks. Also thanks for adjusting my messy tags.. ;) Original-Nachricht Am 21. Feb. 2022, 13:02, schrieb: > https://bugs.kde.org/show_bug.cgi?id=450643 > > caulier.gil...@gmail.com changed: > > What |Removed |Added > > CC| |caulier.gil...@gmail.com > > --- Comment #1 from caulier.gil...@gmail.com --- > Comment on attachment 146996 > --> https://bugs.kde.org/attachment.cgi?id=146996 > proposal > > Ah you want a "burger menu" in fact... > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 450643] Expose menus optionally in the toolbar : burger main menu feature
https://bugs.kde.org/show_bug.cgi?id=450643 --- Comment #6 from Matthias --- Looks awesome, thanks -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 454470] New: Warning about preview keeps showing up
https://bugs.kde.org/show_bug.cgi?id=454470 Bug ID: 454470 Summary: Warning about preview keeps showing up Product: kdenlive Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- SUMMARY The clip monitor is used to preview online resources. The warning, that the clip may take some while, appears unnecessary and annoying to me personally. But the whole purpose of this issue is, to get rid of the warning, after it has been shown once. STEPS TO REPRODUCE 1. Preview Online Ressources 2. 3. OBSERVED RESULT Warning is shown again and again This is distracting EXPECTED RESULT Warning shows just the first time. SOFTWARE/OS VERSIONS Operating System: Garuda Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 6 × AMD Ryzen 5 3500X 6-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics ADDITIONAL INFORMATION https://youtu.be/BY0pDhMoe7w -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 454727] New: Klick von Protokollierung zu Bearbeiten verschieben sich das komplette Menü nach rechts
https://bugs.kde.org/show_bug.cgi?id=454727 Bug ID: 454727 Summary: Klick von Protokollierung zu Bearbeiten verschieben sich das komplette Menü nach rechts Product: kdenlive Version: 22.04.1 Platform: Microsoft Windows OS: Other Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: krem...@matthiasstanke.de Target Milestone: --- Created attachment 149390 --> https://bugs.kde.org/attachment.cgi?id=149390&action=edit UI Screenshot oben rechts SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Klick auf Protokollierung 2. Klick auf Bearbeiten 3. OBSERVED RESULT Das gesamte Eingabefeld verschiebt sich nach rechts. Alle anderen Klicks auf Audio, Effekte oder Farbe provozieren diesen Fehler nicht. Vorläufige Notlösung: Fenster vom Vollbildmodus zu Fenstermodus und wieder Vollbildmodus. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 11 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.
[rkward] [Bug 404431] RKWard crashes when changing the class of an opened object
https://bugs.kde.org/show_bug.cgi?id=404431 Matthias changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #2 from Matthias --- The bug persists with the following versions: R version (compile time): 4.0.2 (2020-06-22 r78730) R runtime session info: R version 4.1.2 (2021-11-01) Platform: x86_64-pc-linux-gnu (64-bit) Running under: Ubuntu 22.04.1 LTS Matrix products: default BLAS: /usr/lib/x86_64-linux-gnu/blas/libblas.so.3.10.0 LAPACK: /usr/lib/x86_64-linux-gnu/lapack/liblapack.so.3.10.0 locale: [1] LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=C [3] LC_TIME=de_DE.UTF-8 LC_COLLATE=de_DE.UTF-8 [5] LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=de_DE.UTF-8 [7] LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 [9] LC_ADDRESS=de_DE.UTF-8LC_TELEPHONE=de_DE.UTF-8 [11] LC_MEASUREMENT=de_DE.UTF-8LC_IDENTIFICATION=de_DE.UTF-8 attached base packages: [1] stats graphics grDevices utils datasets methods base other attached packages: [1] rkward_0.7.2 loaded via a namespace (and not attached): [1] compiler_4.1.2 tools_4.1.2 -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 404431] RKWard crashes when changing the class of an opened object
https://bugs.kde.org/show_bug.cgi?id=404431
--- Comment #4 from Matthias ---
Sorry, my bad. The bug can be triggered with this script:
#Preparation
library(likert)
set.seed(1)
n <- 100
# Create dataframe df
df <- data.frame(
id=sample(1:5,n, replace=T),
rating=factor(sample(1:5,n, replace=T),
labels=c("Good","Neither","Poor","Very Good","Very Poor"))
)
#Now open df in Rkward's viewer, then run:
df <- likert(items=df[,2, drop = FALSE], nlevels = 5)
--
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 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&action=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 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 488243] New: Brightness resets unwanted
https://bugs.kde.org/show_bug.cgi?id=488243 Bug ID: 488243 Summary: Brightness resets unwanted Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brightness and Color Assignee: plasma-b...@kde.org Reporter: shaloksha...@protonmail.ch CC: natalie_clar...@yahoo.de Target Milestone: 1.0 *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Hi there :) When I manually adjust the brightness level, the slider of the Brightness and Colors widget resets to 30% It does not reset the actual brightness, mind you. Still, whenever that value is read by Plasma, it obviously jump to that level: Let's say I set the brightness level to 5%, and set "Turn off screen" for "When laptop lid is closed" Closing and opening the laptop lid brings the brightness up to 30% now. I assume this was due to the upgrade to Plasma 6.0.5 or Qt 6.7.1 Operating System: Garuda Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-zen1-1-zen (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.
[plasmashell] [Bug 488243] Brightness resets unwanted
https://bugs.kde.org/show_bug.cgi?id=488243 --- Comment #1 from Matthias --- I now realize, the OSD has no effect on the widget. Changing my display brightness via keyboard combinations shows the change on the OSD and actually changes it. Here is my log, journalctl -b: https://dpaste.org/rvht4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488259] New: Documentation and implementation differ for installing KWin scripts
https://bugs.kde.org/show_bug.cgi?id=488259 Bug ID: 488259 Summary: Documentation and implementation differ for installing KWin scripts Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: scripting Assignee: kwin-bugs-n...@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- Created attachment 170294 --> https://bugs.kde.org/attachment.cgi?id=170294&action=edit Screenshot 1 SUMMARY The docs say I may import a KPackage via the systemsettings GUI The KDialog window of said KCM asks for a .kwinscript instead. STEPS TO REPRODUCE 1. https://develop.kde.org/docs/plasma/kwin/#packaging-kwin-scripts 2. See screenshot Operating System: Garuda Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-zen1-1-zen (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.
[kwin] [Bug 488259] Documentation and implementation differ for installing KWin scripts
https://bugs.kde.org/show_bug.cgi?id=488259 --- Comment #1 from Matthias --- Created attachment 170295 --> https://bugs.kde.org/attachment.cgi?id=170295&action=edit Screenshot 2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488259] Documentation and implementation differ for installing KWin scripts
https://bugs.kde.org/show_bug.cgi?id=488259 --- Comment #2 from Matthias --- I should add, that I installed successful (but didnt bring my script to work, yet) via the also promoted kpackagetool. That means there could be the option to import via the KPackage format, as this seems to be supported on the command line already. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488243] Brightness resets unwanted
https://bugs.kde.org/show_bug.cgi?id=488243 Matthias changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Matthias --- Well, yes and no. I also experienced, that the brightness was always reset to the level, that the widget was set. But with a recent update, but seems to be resolved. Closing for now, will open it again, if it comes back. Thanks a lot -- 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.
[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&action=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.
[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.
[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&action=edit Subtitle not loading -- 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 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&action=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 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.
[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.
[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.
[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.
[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 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] 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.
[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&action=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.
[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&action=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.
[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] 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 #4 from Matthias --- Created attachment 169089 --> https://bugs.kde.org/attachment.cgi?id=169089&action=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 #5 from Matthias --- Created attachment 169090 --> https://bugs.kde.org/attachment.cgi?id=169090&action=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 #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.
[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.
[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 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&action=edit recording of the bug -- 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.
[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 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.
[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.
[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.
[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&action=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.
[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.
[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 #4 from Matthias --- So it will show 'Hide Sidebar' when open? -- 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.
[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.
[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.
[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 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.
[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.
[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.
[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 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.
[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 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 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 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 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.
[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&action=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.
[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&action=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.
[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 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&action=edit Move windows to other screen -- 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.
[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.
[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&action=edit KCM -- 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 #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.
[kdenlive] [Bug 453489] New: Timeline unable to load any files
https://bugs.kde.org/show_bug.cgi?id=453489 Bug ID: 453489 Summary: Timeline unable to load any files Product: kdenlive Version: 22.04.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- Created attachment 148628 --> https://bugs.kde.org/attachment.cgi?id=148628&action=edit kdenliverc (rename to that, in order to bugtrack, this can overwrite your personal setup. backup that one by renaming it similary.) SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I provide a kdenliverc, that deleted all my files from the timeline after a save & restart (the first I had done after working on this project) The project lost all of its files from the timeline and couldn't accept any others into it as well. It simply wouldn't drop/accept. Notice, that once I deleted/renamed kdenliverc, and restarted, all worked fine again. Both restoring the old .kdenlive, as well as loading files from the file bin. Notice, that loading the old .kdenlive, the timeline wouldn't be restored, on both my computer and that from Massimo Stella, whom I reached on Telegram/Matrix. So I am confused about that, since he has obviously another kdenliverc, so it might be worth investigating his file of that name as well. Maybe there is some misconfiguration. I suspect that is happening when the kdenliverc is loaded, since the issue only occurred after me saving and restarting (for the purpose of potentially fixing another issue, uff :)) Thanks a lot ADDITIONAL INFORMATION I am on Garuda Linux, Arch. All current versions and fully updated and rebooted system. Operating System: Garuda Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.17.5-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 6 × AMD Ryzen 5 3500X 6-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 453489] Timeline unable to load any files
https://bugs.kde.org/show_bug.cgi?id=453489 --- Comment #1 from Matthias --- Created attachment 148629 --> https://bugs.kde.org/attachment.cgi?id=148629&action=edit I also add the kdenlive -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 452368] New: KSnip/KImageeditor dont follow fullscreen setting
https://bugs.kde.org/show_bug.cgi?id=452368 Bug ID: 452368 Summary: KSnip/KImageeditor dont follow fullscreen setting Product: Spectacle Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: shaloksha...@protonmail.ch CC: k...@david-redondo.de Target Milestone: --- Created attachment 148023 --> https://bugs.kde.org/attachment.cgi?id=148023&action=edit Setting SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I have set all my windows to open by default maximized. Both Spectacle (I dont care) and the Annotation feature, backed by KSnip or KImageeditor are not following this, similar as the KDE file dialog. When editing a picture, the small window that is provided by default, is not enough, and I always need to manually maximize the window. Thanks a lot -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 385270] Disable volume slider by scroll function optionally
https://bugs.kde.org/show_bug.cgi?id=385270 --- Comment #13 from Matthias --- I dont see, how adding some configuration makes KDE worse. Simple by default, powerful when needed. I do agree, that bat is hyperbolic and the issue not that gravitational, but I do agree, that adding the feature might help some people. I also get caught in wonders, when I scroll down in eg Kate, and suddenly I find myself in tab number 7 instead the first one. This is highly confusing and definitely something, that the KDE promise of configurability aims to solve. I love more configurability, and all the arguments of Nate against it, basically speak against the very essence of KDE. There needs to be no compromised, when a configuration can solve it. Configuration first, compromise second. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 456456] New: Make it possible to move to up, back and forward
https://bugs.kde.org/show_bug.cgi?id=456456 Bug ID: 456456 Summary: Make it possible to move to up, back and forward Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: shaloksha...@protonmail.ch CC: kfm-de...@kde.org Target Milestone: --- Created attachment 150475 --> https://bugs.kde.org/attachment.cgi?id=150475&action=edit Screenshot SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Drag a file to the back, forward or upwards button. OBSERVED RESULT Currently, no file is moved EXPECTED RESULT File moves to the desired location. ADDITIONAL INFORMATION See screenshot -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 456456] Make it possible to move files and directories to the up, back and forward locations.
https://bugs.kde.org/show_bug.cgi?id=456456 Matthias changed: What|Removed |Added Summary|Make it possible to move to |Make it possible to move |up, back and forward|files and directories to ||the up, back and forward ||locations. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458372] New: Notify about crashed compositor
https://bugs.kde.org/show_bug.cgi?id=458372 Bug ID: 458372 Summary: Notify about crashed compositor Product: plasmashell Version: master Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: shaloksha...@protonmail.ch CC: k...@privat.broulik.de Target Milestone: 1.0 Created attachment 151628 --> https://bugs.kde.org/attachment.cgi?id=151628&action=edit Screenshot SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Bring your compositor to crash 2. Dont get notified about it. OBSERVED RESULT No notification EXPECTED RESULT Notification **in the systray/via popup) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Operating System: Garuda Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.3-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 6 × AMD Ryzen 5 3500X 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics Manufacturer: ASUS ADDITIONAL INFORMATION I got no notification, that my composition broke due to a misaligned device driver. I just lost transparency of my latte dock, and got no clue, why. In the Garuda forum (https://forum.garudalinux.org/t/transparency-effect-for-latte/21956/14) I got pitched about the composition settings, where an extensive and pretty informative explanation of the case waited for me. I would love to see a notification, including it being clickable and linking to said settings page, in the notification widget. There are a lot of little details listed there and such a major crash - that doesnt solve itself by waiting or so - does get hidden away at the current time. Thanks a lot -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442815] New: Open KFind symbol cannot be changed
https://bugs.kde.org/show_bug.cgi?id=442815 Bug ID: 442815 Summary: Open KFind symbol cannot be changed Product: dolphin Version: 21.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: shaloksha...@protonmail.ch CC: kfm-de...@kde.org Target Milestone: --- SUMMARY The icon of 'Open KFind' cannot be changed permanently. STEPS TO REPRODUCE 1. Put the KFind action into the toolbar 2. Change its icon 3. Close Dolphin and reopen it OBSERVED RESULT Old logo EXPECTED RESULT Chosen alternative is shown SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I am using KaOS. This is not selectable in the drop down menu -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 451157] New: Visual representation of CPU temp
https://bugs.kde.org/show_bug.cgi?id=451157 Bug ID: 451157 Summary: Visual representation of CPU temp Product: plasma-systemmonitor Version: 5.24.2 Platform: Archlinux Packages OS: Other Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: shaloksha...@protonmail.ch CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 147289 --> https://bugs.kde.org/attachment.cgi?id=147289&action=edit temp See the attachment. The visual representation shows a full graph, despite the low temperature. That not indicative for the relative temp. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 451334] New: presence of steam-libs-i386 breaks distro upgrade
https://bugs.kde.org/show_bug.cgi?id=451334 Bug ID: 451334 Summary: presence of steam-libs-i386 breaks distro upgrade Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: matthias.behr...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY *** the fact that steam-libs-i386 is installed renders the installation unusable after a system upgrade *** STEPS TO REPRODUCE 1. install steam-libs-i386 2. upgrade to latest version of kde neon via the system upgrade in discover 3. go through with the requested reboots (was 2 reboots for me) OBSERVED RESULT starting a x.org session results in immediate termination of the x server. the user gets presented with the graphical login again EXPECTED RESULT i expected auto login to just start my x server SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.24 (available in About System) KDE Plasma Version: 5.24 ADDITIONAL INFORMATION i upgraded from a 5.2x to 5.24. i have done so before without major trouble only after i ran sudo pkcon remove steam-libs-i386 and sudo pkcon -y update was i able to start my x server again. a novice user would have been completely overwhelmed by the problem. thats why i marked it as critical there was no hint to the user about what is the root of the problem manually trying to start a xserver by tying startx in the terminal resulted in no error message and a advise to look at /var/log/x.org.1/somelog.file but there no /var/log/x.org* present. i was unable to find logfiles that could help me the fact that the log file hint points in the wrong direction makes it even difficult for an advanced user to solve the problem -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 451877] New: njk files not supported
https://bugs.kde.org/show_bug.cgi?id=451877 Bug ID: 451877 Summary: njk files not supported 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 147717 --> https://bugs.kde.org/attachment.cgi?id=147717&action=edit Showcase SUMMARY *** NJK files are not syntax highlighted *** STEPS TO REPRODUCE 1. Open a njk file https://github.com/ShalokShalom/friedensvolksbegehrenJAM/blob/main/src/site/best-practices.njk 2. See the syntax highlighting not being present OBSERVED RESULT no SH EXPECTED RESULT Highlighting (like on Github) SOFTWARE/OS VERSIONS Operating System: Garuda Linux KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.16.16-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 6 × AMD Ryzen 5 3500X 6-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics ADDITIONAL INFORMATION Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[docs] [Bug 457549] New: docs.kde.org are outdated
https://bugs.kde.org/show_bug.cgi?id=457549 Bug ID: 457549 Summary: docs.kde.org are outdated Product: docs Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: major Priority: NOR Component: docs.kde.org Assignee: kde-doc-engl...@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** The docs.kde.org page is hugely outdated. The logo is still from KDE 3, the shipped documentation seems to at least 3 years old, sometimes even 10 years: https://docs.kde.org/stable5/en/kdevelop/kdevelop/index.html Since this is, what people find when they google (how I just did) would I recommend to take this site down. I hope somebody has access to it (or can even update it with the current state of the documentation) -- You are receiving this mail because: You are watching all bug changes.
[docs] [Bug 457549] docs.kde.org are outdated
https://bugs.kde.org/show_bug.cgi?id=457549 --- Comment #3 from Matthias --- And also updating the logo. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440656] New: Sort mechanism disturbed (by size)
https://bugs.kde.org/show_bug.cgi?id=440656 Bug ID: 440656 Summary: Sort mechanism disturbed (by size) Product: dolphin Version: 21.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: shaloksha...@protonmail.ch CC: kfm-de...@kde.org Target Milestone: --- Created attachment 140557 --> https://bugs.kde.org/attachment.cgi?id=140557&action=edit The next folder in line, thirdparty, is 90mb big. SUMMARY The sort by size option brings irregular results. STEPS TO REPRODUCE 1. Sort by size 2. 3. OBSERVED RESULT Doesn't sort by size EXPECTED RESULT Sorts by size SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: https://i.imgur.com/5fAeJ5k.png (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.
[dolphin] [Bug 440656] Sort mechanism disturbed (by size)
https://bugs.kde.org/show_bug.cgi?id=440656 --- Comment #1 from Matthias --- Created attachment 140558 --> https://bugs.kde.org/attachment.cgi?id=140558&action=edit Another folder, this time with the sort window -- You are receiving this mail because: You are watching all bug changes.
[Planet KDE] [Bug 382265] Add option to direct link
https://bugs.kde.org/show_bug.cgi?id=382265 Matthias changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #7 from Matthias --- Great, seems solved for me. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435292] New: Improve description for "Keep above" tool tip
https://bugs.kde.org/show_bug.cgi?id=435292 Bug ID: 435292 Summary: Improve description for "Keep above" tool tip Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: shaloksha...@protonmail.ch CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY The more experienced KDE users probably understand, what the tooltip 'Keep above' is meant for. Still, even for seasoned users, this sounds a little bit too generalized. The tooltip, that appears when you hover over the title bar button, that keeps windows over the others, is sparse, and can lead to additional confusion, since it can be read in activated state, and then suggests doing the opposite of what it truly does. Let`s improve this. STEPS TO REPRODUCE 1. Add a "keep above" title button to the title bar. 2. Hover over the button. 3. Activate it, and hover again over the button, assuming you are a user, who is just figuring out, what this button does. OBSERVED RESULT Confusion EXPECTED RESULT Clarity ADDITIONAL INFORMATION Operating System: KaOS (2021) KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 SUGGESTION I suggest the following sentence as a replacement for the current one's; Keep this window always above others. Do not keep this window above others. -- You are receiving this mail because: You are watching all bug changes.
