[digikam] [Bug 485979] Expose Yolo Resizing Parameter to Improve Face Detection Accuracy
https://bugs.kde.org/show_bug.cgi?id=485979 --- Comment #2 from kde-bugzi...@benjamin-portner.de --- Created attachment 168818 --> https://bugs.kde.org/attachment.cgi?id=168818&action=edit image for which face detection does not work -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485786] Moving a directory/file with the cursor crashes Dolphin
https://bugs.kde.org/show_bug.cgi?id=485786 SolidCapo changed: What|Removed |Added CC||jorgenava...@gmail.com --- Comment #1 from SolidCapo --- Created attachment 168817 --> https://bugs.kde.org/attachment.cgi?id=168817&action=edit This is what happens to me when moving files to the bread crumbs of dolphin, it crashes. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468775] Import files - Preview not available
https://bugs.kde.org/show_bug.cgi?id=468775 --- Comment #7 from Maik Qualmann --- There should be something in the debug output in the terminal if thumbnails are not created for some images. A log would be interesting. Regarding the creation date when metadata is deactivated, you cannot generally say that the creation and modification dates are different, that depends on many factors, e.g. camera model. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 485981] "Open in File Manager" causes 100% CPU usage in process: kde-open5 file://
https://bugs.kde.org/show_bug.cgi?id=485981 Maik Qualmann changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 485981] "Open in File Manager" causes 100% CPU usage in process: kde-open5 file://
https://bugs.kde.org/show_bug.cgi?id=485981 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- I'm already on a KF6 desktop. But I can also confirm the problem with the AppImage, Dolphin does not open. However, I don't have 100% system load, but I see these messages: /usr/bin/dolphin: /tmp/.mount_digiKaO1moPr/usr/lib/libQt6Gui.so.6: version `Qt_6.7.0_PRIVATE_API' not found (required by /usr/bin/dolphin) /usr/bin/dolphin: /tmp/.mount_digiKaO1moPr/usr/lib/libQt6Core.so.6: version `Qt_6.7.0_PRIVATE_API' not found (required by /lib64/libQt6Core5Compat.so.6) With my native Qt6 developer version there are no problems opening Dolphin. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 485982] Crashed NetworkManager disappears from taskbar
https://bugs.kde.org/show_bug.cgi?id=485982 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485736] Dolphin crashes due to memory leak
https://bugs.kde.org/show_bug.cgi?id=485736 DN changed: What|Removed |Added CC||mlggot...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485792] Gigabytes of log spam after cutting and pasting a file
https://bugs.kde.org/show_bug.cgi?id=485792 DN changed: What|Removed |Added CC||mlggot...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 485669] Drkonqi crashes while generating the backtrace
https://bugs.kde.org/show_bug.cgi?id=485669 DN changed: What|Removed |Added CC||mlggot...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485983] New: Clicking system tray icons results in tiny (1x1?) pop-out menus
https://bugs.kde.org/show_bug.cgi?id=485983 Bug ID: 485983 Summary: Clicking system tray icons results in tiny (1x1?) pop-out menus Classification: Plasma Product: plasmashell Version: 6.0.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: a...@digitalsignalperson.com CC: mate...@gmail.com Target Milestone: 1.0 Created attachment 168816 --> https://bugs.kde.org/attachment.cgi?id=168816&action=edit after clicking the volume tray icon, a small circle appears SUMMARY After clicking a tray icon, a small circle appears instead of e.g. the pop out window with volume sliders. STEPS TO REPRODUCE 1. Vertical panel on right side of screen 2. Click volume tray icon OBSERVED RESULT Small circle appears next to tray. See attachment. If you hover the mouse over it, the mouse cursor turns into arrows. Clicking and dragging the arrows makes the window appear (not in the right place). EXPECTED RESULT Pop out window with volume sliders appears. SOFTWARE/OS VERSIONS Operating System: Arch Linux vmlinuz-linux.arch.20240415.1019.efi KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.5-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 485982] New: Crashed NetworkManager disappears from taskbar
https://bugs.kde.org/show_bug.cgi?id=485982 Bug ID: 485982 Summary: Crashed NetworkManager disappears from taskbar Classification: Plasma Product: plasma-nm Version: 6.0.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: mikar_gibb...@yahoo.com Target Milestone: --- SUMMARY If NetworkManager crashes, "Networks" disappears from the bottom-right taskbar (task manager) and should only be a button click to restart. STEPS TO REPRODUCE 1. Find the "Networks" icon in the bottom-right taskbar (task manager). 2. To reproduces what happened when it randomly crashed on me: $ sudo systemctl stop NetworkManager OBSERVED RESULT 3. Notice "Networks" has completely disappeared after a crash. EXPECTED RESULT 4. NetworkManager tries to automatically recover itself from this errored state. 5. If NetworkManager cannot automatically recover, still display "Networks" in the taskbar (with an alert symbol/color overlay of some kind) but have it only inform the user of NetworkManager's Status/Error and have a single button that runs: $ sudo systemctl restart NetworkManager 6. This restart fixed my initial issue and the step 2. reproduction of the issue. SOFTWARE/OS VERSIONS Operating System: Bazzite 40 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.7-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 32 × 13th Gen Intel® Core™ i9-13980HX Memory: 15.2 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: Vivobook_ASUSLaptop K6604JI_K6604JI System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 485981] "Open in File Manager" causes 100% CPU usage in process: kde-open5 file://
https://bugs.kde.org/show_bug.cgi?id=485981 MarcP changed: What|Removed |Added CC||iwannaber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 485981] New: "Open in File Manager" causes 100% CPU usage in process: kde-open5 file://
https://bugs.kde.org/show_bug.cgi?id=485981 Bug ID: 485981 Summary: "Open in File Manager" causes 100% CPU usage in process: kde-open5 file:// Classification: Applications Product: digikam Version: 8.4.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: iwannaber...@gmail.com Target Milestone: --- SUMMARY I noticed that when I right click on a picture, and select Open in File Manager, instead of Dolphin showing the contents of the folder where the picture is located, nothing happens. Upon inspecting the running processes, I noticed that there's a stuck process that is using all the CPU: kde-open5 file:// I don´t know when it started. I'm currently using the digiKam-8.4.0-20240421T104710-Qt6-x86-64.appimage, but it used to work in previous versions. I thought it might have something to do with the folder path having spaces or special characters, but it doesn't seem to matter. Also, running that kde-open5 command directly on a bash console seems to open Dolphin to that folder. STEPS TO REPRODUCE 1. Right click on a picture. Open in File Manager. OBSERVED RESULT Nothing happens EXPECTED RESULT File browser should open at that location. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 LTS digiKam-8.4.0-20240421T104710-Qt6-x86-64.appimage (available in About System) KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413196] Cannot export files with more as 4 MB to OneDrive
https://bugs.kde.org/show_bug.cgi?id=413196 --- Comment #12 from Nicofo --- (In reply to Maik Qualmann from comment #11) > No, according to Microsoft API documentation it is still limited to 4MB in > simple item upload mode. > > Maik I believe you, but try by yourself, this limit is not correct anymore ;) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468775] Import files - Preview not available
https://bugs.kde.org/show_bug.cgi?id=468775 --- Comment #6 from Nicofo --- (In reply to Maik Qualmann from comment #5) > No preview image, image broken? No: the image is not broken. And when downloaded, they are displayed correctly in digikam. > In order to get a correct creation date in the thumbnail, the metadata must > be read. To do this, the corresponding option must be activated in the > digiKam camera settings, with the addition "makes the connection slower". If > you click on an image, the “live” data will be displayed in the metadata > viewer. > As of digiKam-8.0.0, reading the exact metadata is no longer necessary; all > date operations are now carried out after the download. Yes you are right, I forgot to activate the option "Use file metedata (makes the connection slower)". So the date is correct with this option activated. But not correct with the option deactivated (possible to rename "Cretaed" into "Modified" in this case ?). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413196] Cannot export files with more as 4 MB to OneDrive
https://bugs.kde.org/show_bug.cgi?id=413196 --- Comment #11 from Maik Qualmann --- No, according to Microsoft API documentation it is still limited to 4MB in simple item upload mode. Maik -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 485922] KMail is trying to load external resource of the message despite it being disabled
https://bugs.kde.org/show_bug.cgi?id=485922 --- Comment #2 from beanbo --- this issue might be a part of the following problem: https://bugs.webkit.org/show_bug.cgi?id=259787 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413196] Cannot export files with more as 4 MB to OneDrive
https://bugs.kde.org/show_bug.cgi?id=413196 --- Comment #10 from Nicofo --- As stated in #comment 7: > I am even able to export a video of 98.4 Mb. > (...) > So the limit is somewhere between 98.4 and 168.5 Mb (100Mb maybe ? Possible > to check that on Microsoft documentation ?)" So this bug can be closed for me. But you should remove the remark in the documentation that you introduced in #comment 5 : "OneDrive file storage is currently limited to host only files with a size lower than 4Mb." -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468775] Import files - Preview not available
https://bugs.kde.org/show_bug.cgi?id=468775 --- Comment #5 from Maik Qualmann --- No preview image, image broken? In order to get a correct creation date in the thumbnail, the metadata must be read. To do this, the corresponding option must be activated in the digiKam camera settings, with the addition "makes the connection slower". If you click on an image, the “live” data will be displayed in the metadata viewer. As of digiKam-8.0.0, reading the exact metadata is no longer necessary; all date operations are now carried out after the download. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 485979] Expose Yolo Resizing Parameter to Improve Face Detection Accuracy
https://bugs.kde.org/show_bug.cgi?id=485979 Maik Qualmann changed: What|Removed |Added OS|Unspecified |Microsoft Windows Platform|unspecified |Microsoft Windows -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 485979] Expose Yolo Resizing Parameter to Improve Face Detection Accuracy
https://bugs.kde.org/show_bug.cgi?id=485979 Maik Qualmann changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- What they picked out in the source code is not the scaled image size that is used. There are fixed values for the face model data. Upload a image in which not all faces are detected, if not publicly, then to my private email. At the moment I can't imagine that not all faces will be detectedf they have YoloV3 activated. Maik -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 485980] New: No Desktop Icon for kmymoney during install
https://bugs.kde.org/show_bug.cgi?id=485980 Bug ID: 485980 Summary: No Desktop Icon for kmymoney during install Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Microsoft Windows OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: davidv...@gmail.com Target Milestone: --- SUMMARY I just heard about Kmymoney, went to your website and downloaded it. I have a desktop gaming PC with Windows 11. After installation, I discovered there was no desktop icon on my desktop. When I went into the Windows app launcher, I found Kmymoney, but there is no icon to install on the desktop - there is one for the Windows taskbar. EXPECTED RESULT: I expected to have an application icon of Kmymoney on my desktop with my other frequently used applications. SOFTWARE/OS VERSIONS Windows: 11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468775] Import files - Preview not available
https://bugs.kde.org/show_bug.cgi?id=468775 caulier.gil...@gmail.com changed: What|Removed |Added Version|8.0.0 |8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485978] Plasma 6 Wayland: cyan/azure line glitch
https://bugs.kde.org/show_bug.cgi?id=485978 --- Comment #4 from mikar_gibb...@yahoo.com --- https://discord.com/channels/1072614816579063828/1231641944732729404 This isn't "System Settings/Mouse & Touchpad/Screen Edges". Changing every setting (Themes/Schemes/Style/Decorations) in "System Settings/Color & Themes" did not effect this line. "Screen Edges" bottom of the screen effect is 10px tall (not 1px), and doesn't cover the entire width of the screen. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 485979] New: Expose Yolo Resizing Parameter to Improve Face Detection Accuracy
https://bugs.kde.org/show_bug.cgi?id=485979 Bug ID: 485979 Summary: Expose Yolo Resizing Parameter to Improve Face Detection Accuracy Classification: Applications Product: digikam Version: 8.3.0 Platform: unspecified OS: Unspecified Status: REPORTED Severity: wishlist Priority: NOR Component: Faces-Detection Assignee: digikam-bugs-n...@kde.org Reporter: kde-bugzi...@benjamin-portner.de Target Milestone: --- SUMMARY Face detection in large images can be improved by increasing the re-sizing parameter in the detection pipeline. To strike a balance between accuracy and performance, the parameter shouldn't be fixed. I propose exposing it to the user for manual adjustment. STEPS TO REPRODUCE 1. Load a large image (many pixels) into digikam 2. Use the facial detection feature OBSERVED RESULT Not all faces are found EXPECTED RESULT All faces are found SOFTWARE/OS VERSIONS Windows: Windows 11 Pro KDE Frameworks: 5.248.0 Qt: 6.6.1 ADDITIONAL INFORMATION Image re-scaling is an important part of the face detection pipeline because it improves the computation speed. Currently, the final image size after resizing is hard-coded in the source code (e.g. https://invent.kde.org/graphics/digikam/-/blob/master/core/libs/facesengine/detection/opencv-dnn/dnnfacedetectoryolo.cpp#L42 for the Yolo model). This is problematic, because if an image is very big initially (many pixels), redical rescaling to the given size can make face detection impossible. By making this parameter adjustable by the user, we could improve the detection accuracy in such cases greatly. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 485959] Spectacle doesn't open when there are two screens
https://bugs.kde.org/show_bug.cgi?id=485959 --- Comment #1 from Noah Davis --- > Two screens 4K external + 1080p internal Can you post their arrangement and scale factors? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485978] Plasma 6 Wayland: cyan/azure line glitch
https://bugs.kde.org/show_bug.cgi?id=485978 mikar_gibb...@yahoo.com changed: What|Removed |Added Attachment #168811|0 |1 is obsolete|| --- Comment #3 from mikar_gibb...@yahoo.com --- Created attachment 168815 --> https://bugs.kde.org/attachment.cgi?id=168815&action=edit Frame 2 smudges that are reading from discord's texture that flashes with the cursor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485978] Plasma 6 Wayland: cyan/azure line glitch
https://bugs.kde.org/show_bug.cgi?id=485978 --- Comment #2 from mikar_gibb...@yahoo.com --- Created attachment 168814 --> https://bugs.kde.org/attachment.cgi?id=168814&action=edit Frame 1 smudges that are reading from discord's texture that flashes with the cursor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485978] Plasma 6 Wayland: cyan/azure line glitch
https://bugs.kde.org/show_bug.cgi?id=485978 --- Comment #1 from mikar_gibb...@yahoo.com --- Created attachment 168813 --> https://bugs.kde.org/attachment.cgi?id=168813&action=edit bottom-right corner of screen showing glitch's line and hook -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468775] Import files - Preview not available
https://bugs.kde.org/show_bug.cgi?id=468775 --- Comment #4 from Nicofo --- Created attachment 168812 --> https://bugs.kde.org/attachment.cgi?id=168812&action=edit Missing preview of some pictures + wrong label "created" Hi Gilles, I tested with digiKam-8.4.0-20240421T172117-Qt6-x86-64.appimage: Following #comment 0 : 1) Preview mode not available: -> not working. But normal according to Maik's answer #comment 1 2) Thumbnails are not well rotated: -> is now working well, thanks ! But I have other problems (more or less related to original problem, so I keep it on this bug report. Tell me if you prefer a dedicated bug report) 3) Not all pictures have their preview visible: see attachment -> After scrolling up and down, the majority of the pictures have their preview appearing, but for a few of them, the preview never appears. This is really annoying because the preview button is not working and nothing happens when you click on the picture (see problem 1) -> it is hard to guess what is the picture. 4) The reported date (labelled "created" below the preview) seems to be the date of the file (last modification of the file on the camera), but not the creation date : see attachment -> so either rename "created" by "modified" -> or better correct it to be the real "created" date of the picture (info from the metadata). Use case: I want to sort the files according to the moment they were taken, not the date of modification. This is important in this window if you want to select all the pictures from a dedicated date. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485978] New: Plasma 6 Wayland: cyan/azure line glitch
https://bugs.kde.org/show_bug.cgi?id=485978 Bug ID: 485978 Summary: Plasma 6 Wayland: cyan/azure line glitch Classification: Plasma Product: kwin Version: 6.0.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: mikar_gibb...@yahoo.com Target Milestone: --- Created attachment 168811 --> https://bugs.kde.org/attachment.cgi?id=168811&action=edit bottom-right corner of screen showing glitch's line and hook. Frame 1 and 2 smudges that are reading from discord's texture that flashes with the cursor. SUMMARY On Plasma 6 Wayland there is rendering glitch at the bottom of the screen showing a raw 1px tall cyan/azure line. This line is raw reading the GPU textures of other programs like Discord, sometimes having smudged flashing pixels (about 10px wide) matching the cursor in the discord window. Line has a hook at the bottom right corner of screen, so this is definitely a glitch and not an edge of screen theme line. STEPS TO REPRODUCE 1. Login to bazzite-asus-nvidia:40 from a Vivobook_ASUSLaptop K6604JI_K6604JI. 2. Open flatpak Discord and have the blinking cursor be visible. OBSERVED RESULT Plasma 6 Wayland 1px tall cyan/azure line rendering glitch. This is going to cause burn-in on my OLED screen. This line is not visible in Plasma (X11) 6's desktop, but Plasma (X11) 6's desktop's Lock screen displays a black screen and crashes my device. EXPECTED RESULT Not having a cyan line at the bottom of my screen causing burn-in. SOFTWARE/OS VERSIONS Operating System: Bazzite 40 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.7-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 32 × 13th Gen Intel® Core™ i9-13980HX Memory: 15.2 GiB of RAM Graphics Processor: Mesa Intel® Graphics (This used to say NVidia with Fedora atomic 39) Manufacturer: ASUSTeK COMPUTER INC. Product Name: Vivobook_ASUSLaptop K6604JI_K6604JI System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 461291] In-app keyboard shortcuts definitions using the Numeric Keypad keys are not possible
https://bugs.kde.org/show_bug.cgi?id=461291 Sdar changed: What|Removed |Added CC||s...@vivaldi.net -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 485782] Krita 5.2.2 snap rev 104 crashes on attempting to open or create a document
https://bugs.kde.org/show_bug.cgi?id=485782 Scarlett Moore changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #2 from Scarlett Moore --- Hello, First this is the first i am hearing of the bug. Our store interface does NOT show reviews. So thanks for reporting the bug. I have fixed the unrelated python error, however the actual bug is krita(419714)/(default) \[31mKisImageConfig::safelyGetWritableTempLocation\[0m: WARNING: configured swap location is not writable, using a fall-back location "" -> "/home/scarlett/snap/krita/x6" [New Thread 0x756624ff9640 (LWP 420106)] [New Thread 0x756607fff640 (LWP 420107)] krita(419714)/(default) \[31munknown\[0m: QOpenGLShaderProgram: could not create shader program krita(419714)/(default) \[31m\[34mKisOpenGLCanvasRenderer::reportFailedShaderCompilation\[0m: Shader Compilation Failure: "Failed to add vertex shader source from file: matrix_transform.vert - Cause: " Thread 1 "krita" received signal SIGSEGV, Segmentation fault. 0x7566e24b0034 in QOpenGLFramebufferObject::handle() const () from target:/snap/krita/x6/kf5/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 I don't currently know if it is the /tmp dir issue or the opengl issue but I am working on it. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 485976] Can't run Rescue Mode
https://bugs.kde.org/show_bug.cgi?id=485976 --- Comment #1 from mikar_gibb...@yahoo.com --- 10.1. Adding "systemd.unit=rescue" to the end of the "linux" line in GRUB didn't work. The device booting normally, didn't give any indication that it was in rescue mode, and it didn't ignore Session Restore Settings like rescue mode is suppose to. 10.2. Ctrl+Alt+F#, in the Login Screen, to run a terminal then using "systemctl rescue" didn't work: You are in rescue mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, or "exit" to continue booting. Cannot open access to console, the root account is locked. See sulogin(8) man page for more details. Press Enter to continue. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 482128] kontact does not show antialiased fonts in mail content (and in akregator)
https://bugs.kde.org/show_bug.cgi?id=482128 --- Comment #7 from Iyán Méndez Veiga --- *** Bug 482445 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 482445] kmail font rendering broken on plasma 6 and HiDPI (scaled) display
https://bugs.kde.org/show_bug.cgi?id=482445 Iyán Méndez Veiga changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REOPENED|RESOLVED --- Comment #5 from Iyán Méndez Veiga --- I can confirm as well. But I think it was correctly marked as a duplicate of Bug 482128, which is caused by this Qt bug https://bugreports.qt.io/browse/QTBUG-113574 Operating System: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-arch1-2 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 7900X3D 12-Core Processor Memory: 93.5 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XT Manufacturer: ASUS *** This bug has been marked as a duplicate of bug 482128 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 482445] kmail font rendering broken on plasma 6 and HiDPI (scaled) display
https://bugs.kde.org/show_bug.cgi?id=482445 Iyán Méndez Veiga changed: What|Removed |Added CC||m...@iyanmv.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 485974] Session Restore Hangs
https://bugs.kde.org/show_bug.cgi?id=485974 mikar_gibb...@yahoo.com changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=485976 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 485976] Can't run Rescue Mode
https://bugs.kde.org/show_bug.cgi?id=485976 mikar_gibb...@yahoo.com changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=485974 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485977] Moving files by dragging and dropping them is crashing dolphin
https://bugs.kde.org/show_bug.cgi?id=485977 --- Comment #1 from ali --- (In reply to ali from comment #0) > Created attachment 168810 [details] > this is a video of the bug, hope it helps > > SUMMARY > Moving files by dragging and dropping them in the navigation is crashing > dolphin (Wayland) > > STEPS TO REPRODUCE > 1. make sure you're on a wayland session > 2. open dolphin > 3. open a folder with files > 4. drag one of the files to the parent folder using the navigation bar > > OBSERVED RESULT > Dolphin crashes > > EXPECTED RESULT > The file moved to the parent folder > > SOFTWARE/OS VERSIONS > OS: EndeavourOS Linux x86_64 > DE: Plasma 6.0.4 > KDE Plasma Version: 6.0.4 > KDE Frameworks Version: 6.1.0 > Qt Version: 6.7.0 > Graphics Platform: Wayland > > ADDITIONAL INFORMATION > I think this happens on wayland only -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485977] New: Moving files by dragging and dropping them is crashing dolphin
https://bugs.kde.org/show_bug.cgi?id=485977 Bug ID: 485977 Summary: Moving files by dragging and dropping them is crashing dolphin Classification: Applications Product: dolphin Version: 24.02.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: ali93...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 168810 --> https://bugs.kde.org/attachment.cgi?id=168810&action=edit this is a video of the bug, hope it helps *** 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 Moving files by dragging and dropping them in the navigation is crashing dolphin (Wayland) STEPS TO REPRODUCE 1. make sure you're on a wayland session 2. open dolphin 3. open a folder with files 4. drag one of the files to the parent folder using the navigation bar OBSERVED RESULT Dolphin crashes EXPECTED RESULT The file moved to the parent folder SOFTWARE/OS VERSIONS OS: EndeavourOS Linux x86_64 DE: Plasma 6.0.4 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Graphics Platform: Wayland ADDITIONAL INFORMATION I think this happens on wayland only -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 485636] ref: Bug 451787 this bug referes to chapters in m4b files, they can also be applied in mp3 files
https://bugs.kde.org/show_bug.cgi?id=485636 --- Comment #14 from Lee --- that sounds promising idealy it should be possible to move between chapter text with a single click in the same way you can move between the track title field and the artist text having the chapter data in a seperate location is while not ideal it is ok, but more than a single click to select the text field to enter chapter text -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 485973] Metadata (DateTimeOriginal) not read from MTS video files
https://bugs.kde.org/show_bug.cgi?id=485973 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- digiKam definitely reads the video’s metadata. Here the metadata appears to be in an H264 container. Can you please send me a very short sample video? It's best to film a local digital clock. Maik -- 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 #3 from george fb --- And? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 485974] Session Restore Hangs
https://bugs.kde.org/show_bug.cgi?id=485974 --- Comment #3 from mikar_gibb...@yahoo.com --- *edit, sorry* SUMMARY: Session Restore Hangs when incorrectly reopening apps with multiple tabbed windows. -- 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.
[Breeze] [Bug 485976] New: Can't run Rescue Mode
https://bugs.kde.org/show_bug.cgi?id=485976 Bug ID: 485976 Summary: Can't run Rescue Mode Classification: Plasma Product: Breeze Version: 6.0.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mikar_gibb...@yahoo.com CC: uhh...@gmail.com Target Milestone: --- SUMMARY Unable to run Rescue Mode. This should be an option in the Login Screen: 1. Always available, could be added to the "Plasma", "Plasma (X11)", "Plasma (Rescue once)", "Plasma (X11, Rescue once)". 2. Always available, could be a checkbox if you click the button to enter your user name manually. 3. Shown only if the previous boot didn't finish, lasted less then 5 minutes, the CPU never reduced to less then 50% after boot, Session Restore never stopped opening new windows, etc. STEPS TO REPRODUCE 1. Enabling "System Settings/Session/Desktop Session/Session Restore/On login, launch apps that were open:" to "On last logout". 2. Open flatpak Notepadqq 2.0.0~beta (flathub-beta) with multiple tabs, some unsaved. 3. Open flatpak LibreWolf 124.0.1-1 (flathub) with multiple tabs in multiple windows. 4. Reboot to login screen. 5. Login. OBSERVED RESULT 6. Device Hangs. Many more windows of Notepadqq and LibreWolf will open then before. For T Notepadqq last session tabs, Notepadqq is opening T windows, each containing the T previous tabs. For T tabs from W LibreWolf last session windows, LibreWolf is opening the W previous windows plus many more windows that just contain an empty new tab (It may be opening T windows but hangs before I can find out). EXPECTED RESULT *unreported bug exists* Repeat Steps 1. to 6. 7. Hold down power button for 5 seconds til device loses power. 8. Boot device to login screen. 9. Displayed in the login screen, is either an always present option or present after an incomplete/questionable last boot option to boot into "Rescue Mode" that ignores the Session Restore Settings while in Rescue Mode (or if needed reboot with "systemd.unit=rescue"). 10. Disable Session Restore, fixing system without using another device to search for hours for a solution, like entering rescue mode, but none of which actually work to enter Rescue Mode. (Adding "systemd.unit=rescue" to the end of the "linux" line in GRUB didn't work. Using Ctrl+Alt+F2, in the Login Screen, to run a terminal then using "systemctl rescue" didn't work). 11. Create new account with kde and file a bug report. 12. Wait (for Session Restore fix, then wait for upstream to patch, then wait for my distro plus DE to patch). *reported bug fixed* 13. Enable Session Restore. 14. Reboot. Session Restore correctly reopens apps with multiple tabbed windows and doesn't hang. SOFTWARE/OS VERSIONS Linux/KDE Plasma: bazzite-asus-nvidia:40 (Fedora Atomic 40) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485975] New: kwin crashed when opening multiple .ar files
https://bugs.kde.org/show_bug.cgi?id=485975 Bug ID: 485975 Summary: kwin crashed when opening multiple .ar files Classification: Plasma Product: kwin Version: 5.27.11 Platform: Other OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: k...@assez.biz Target Milestone: --- Application: kwin_x11 (5.27.11) Qt Version: 5.15.13 Frameworks Version: 5.115.0 Operating System: Linux 6.6.12-calculate x86_64 Windowing System: X11 Distribution: Calculate Linux Desktop 23 KDE DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: kwin crashed when opening multiple (29) .ar files at once to browse their contents The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [KCrash Handler] #4 0x55a98316d866 in ?? () #5 0x55a98316e01b in ?? () #6 0x7f57a90951ca in KWin::EffectsHandlerImpl::prePaintWindow(KWin::EffectWindow*, KWin::WindowPrePaintData&, std::chrono::duration >) () from /usr/lib64/libkwin.so.5 #7 0x7f57a91329e4 in KWin::WorkspaceScene::preparePaintSimpleScreen() () from /usr/lib64/libkwin.so.5 #8 0x7f57a9132e95 in KWin::WorkspaceScene::prePaint(KWin::SceneDelegate*) () from /usr/lib64/libkwin.so.5 #9 0x7f57a905098f in KWin::Compositor::prePaintPass(KWin::RenderLayer*) () from /usr/lib64/libkwin.so.5 #10 0x7f57a9053ae3 in KWin::Compositor::composite(KWin::RenderLoop*) () from /usr/lib64/libkwin.so.5 #11 0x7f57a90558bb in KWin::X11Compositor::composite(KWin::RenderLoop*) () from /usr/lib64/libkwin.so.5 #12 0x7f57a78b92cd in ?? () from /usr/lib64/libQt5Core.so.5 #13 0x7f57a9008802 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*) () from /usr/lib64/libkwin.so.5 #14 0x7f57a905d693 in KWin::RenderLoopPrivate::dispatch() () from /usr/lib64/libkwin.so.5 #15 0x7f57a78b92cd in ?? () from /usr/lib64/libQt5Core.so.5 #16 0x7f57a78bd3ea in QTimer::timeout(QTimer::QPrivateSignal) () from /usr/lib64/libQt5Core.so.5 #17 0x7f57a78b14eb in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #18 0x7f57a6f67d6e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #19 0x7f57a7887688 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #20 0x7f57a78d66b1 in QTimerInfoList::activateTimers() () from /usr/lib64/libQt5Core.so.5 #21 0x7f57a78d6f44 in ?? () from /usr/lib64/libQt5Core.so.5 #22 0x7f57a53134d4 in ?? () from /usr/lib64/libglib-2.0.so.0 #23 0x7f57a5316527 in ?? () from /usr/lib64/libglib-2.0.so.0 #24 0x7f57a5316b1c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #25 0x7f57a78d72b6 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #26 0x7f57a788618b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #27 0x7f57a788dff0 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #28 0x55a9830fe1f1 in ?? () #29 0x7f57a6442c8a in ?? () from /lib64/libc.so.6 #30 0x7f57a6442d45 in __libc_start_main () from /lib64/libc.so.6 #31 0x55a9830ff7a1 in ?? () [Inferior 1 (process 3830) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 484938] Okular sidebar will not save
https://bugs.kde.org/show_bug.cgi?id=484938 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/okular/-/merge_requests/975 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 485974] Session Restore Hangs
https://bugs.kde.org/show_bug.cgi?id=485974 --- Comment #2 from mikar_gibb...@yahoo.com --- *edit* 14: Reboot. Session Restore correctly reopens apps with multiple tabbed windows and doesn't hang. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 485531] Glich and crackling
https://bugs.kde.org/show_bug.cgi?id=485531 --- Comment #1 from kailed --- If may help, it doesn't happen with the "old" Kmix -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 485974] Session Restore Hangs
https://bugs.kde.org/show_bug.cgi?id=485974 --- Comment #1 from mikar_gibb...@yahoo.com --- *Edit* 10. Using Ctrl-Alt-F2 in the Login Screen. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 485974] New: Session Restore Hangs
https://bugs.kde.org/show_bug.cgi?id=485974 Bug ID: 485974 Summary: Session Restore Hangs Classification: Plasma Product: Breeze Version: 6.0.3 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mikar_gibb...@yahoo.com CC: uhh...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Enabling "System Settings/Session/Desktop Session/Session Restore/On login, launch apps that were open:" to "On last logout". 2. Open flatpak Notepadqq 2.0.0~beta (flathub-beta) with multiple tabs, some unsaved. 3. Open flatpak LibreWolf 124.0.1-1 (flathub) with multiple tabs in multiple windows. 4. Reboot to login screen. 5. Login. OBSERVED RESULT 6. Device Hangs. Many more windows of Notepadqq and LibreWolf will open then before. For T Notepadqq last session tabs, Notepadqq is opening T windows, each containing the T previous tabs. For T tabs from W LibreWolf last session windows, LibreWolf is opening the W previous windows plus many more windows that just contain an empty new tab (It may be opening T windows but hangs before I can find out). EXPECTED RESULT *unreported bug exists* Repeat Steps 1. to 6. 7. Hold down power button for 5 seconds til device loses power. 8. Boot device to login screen. 9. Displayed in the login screen, is either an always present option or present after an incomplete/questionable last boot option to boot into "Rescue Mode" that ignores the Session Restore Settings while in Rescue Mode (or if needed reboot with "systemd.unit=rescue"). 10. Disable Session Restore, fixing system without using another device to search for hours for a solution, like entering rescue mode, but none of which actually work to enter Rescue Mode. (Adding "systemd.unit=rescue" to the end of the "linux" line in GRUB didn't work. Using Ctrl+Alt+F2 to run a terminal then using "systemctl rescue" didn't work). 11. Create new account with kde and file a bug report. 12. Wait (for Session Restore fix, then wait for upstream to patch, then wait for my distro plus DE to patch). *reported bug fixed* 13. Enable Session Restore. 14. Reboot and device doesn't hang. SOFTWARE/OS VERSIONS Linux/KDE Plasma: bazzite-asus-nvidia:40 (Fedora Atomic 40) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364321] GUI to switch between JEDEC and SI units
https://bugs.kde.org/show_bug.cgi?id=364321 Méven Car changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/875135ef11bc62f239943f59f ||ef780e2a92b9f44 Resolution|--- |FIXED --- Comment #33 from Méven Car --- Git commit 875135ef11bc62f239943f59fef780e2a92b9f44 by Méven Car. Committed on 22/04/2024 at 17:57. Pushed by meven into branch 'master'. regionandlang kcm: add binary dialect setting M +1-0kcms/region_language/CMakeLists.txt A +97 -0kcms/region_language/binarydialectmodel.cpp [License: GPL(v2.0+)] A +22 -0kcms/region_language/binarydialectmodel.h [License: GPL(v2.0+)] M +1-1kcms/region_language/kcm_regionandlang.json M +93 -47 kcms/region_language/kcmregionandlang.cpp M +2-0kcms/region_language/kcmregionandlang.h M +4-0kcms/region_language/localelistmodel.cpp M +92 -28 kcms/region_language/optionsmodel.cpp M +17 -0kcms/region_language/optionsmodel.h M +7-2kcms/region_language/regionandlangsettings.cpp M +1-1kcms/region_language/settingtype.h M +79 -1kcms/region_language/ui/main.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/875135ef11bc62f239943f59fef780e2a92b9f44 -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 485636] ref: Bug 451787 this bug referes to chapters in m4b files, they can also be applied in mp3 files
https://bugs.kde.org/show_bug.cgi?id=485636 --- Comment #13 from Urs Fleisch --- I understand your point. For MP4 chapters, I have re/ab-used the dialog from synchronized lyrics and event timing codes. This has quite a few advantages, you can see and add chapters on the fly when the track is played, and you can import and export LRC files. Probably, it would have been better to just use one of this two mentioned frames for chapters in an audio book instead of inventing such a complicated frame structure. I will have a look if I can provide an alternative view with such a dialog for MP3 chapters too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483000] File dialog totally different in Wayland vs X11
https://bugs.kde.org/show_bug.cgi?id=483000 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #10 from Zamundaaa --- It's up to the apps whether or not they use the GTK file dialog, or the system (xdg portal) one, which is the correct one for KDE. This has to be fixed in the apps themselves, there's nothing we can do about that -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 485973] Metadata (DateTimeOriginal) not read from MTS video files
https://bugs.kde.org/show_bug.cgi?id=485973 MarcP changed: What|Removed |Added CC||iwannaber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 485973] New: Metadata (DateTimeOriginal) not read from MTS video files
https://bugs.kde.org/show_bug.cgi?id=485973 Bug ID: 485973 Summary: Metadata (DateTimeOriginal) not read from MTS video files Classification: Applications Product: digikam Version: 8.4.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Metadata-ExifTool Assignee: digikam-bugs-n...@kde.org Reporter: iwannaber...@gmail.com Target Milestone: --- Created attachment 168809 --> https://bugs.kde.org/attachment.cgi?id=168809&action=edit Screenshot showing that digikam uses file modification date rather than exiftool's creation date. SUMMARY Hi. I noticed that the .MTS videos that my Sony camera films, when imported into Digikam, the creation date (dateTimeOriginal) is not read. Instead, the file modification date is used. I have attached a screenshot as a reference. STEPS TO REPRODUCE 1. Import MTS video file 2. Check date of file in digikam 3. Check date of file in exiftool. OBSERVED RESULT - Digikam uses modification date rather than date in the metadata. EXPECTED RESULT The date in the metadata should be used instead. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 LTS digiKam-8.4.0-20240421T104710-Qt6-x86-64.appimage -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481736] On X11, Notifications pop up in the middle of the screen after being away from pc for a while
https://bugs.kde.org/show_bug.cgi?id=481736 --- Comment #33 from Knut Eirik --- (In reply to Till Seifert from comment #32) > also affected with 6.0.4. > i can fix it by adjusting the height of my panel by 1px. > then current *and* future notification appear at the correct place. Can also confirm that the notification goes to the correct position after resizing. It goes back to the wrong position after coming back from the lock screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485971] Keepass tray icon breaks nearby icon, also tooltip is messed up
https://bugs.kde.org/show_bug.cgi?id=485971 --- Comment #7 from Gábor Katona --- Created attachment 168808 --> https://bugs.kde.org/attachment.cgi?id=168808&action=edit xprop output for keepass window Attached the output of xprop for the visible keepass window. (sorry, the previous xprop output should have been attached also) Or do you need other info? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485971] Keepass tray icon breaks nearby icon, also tooltip is messed up
https://bugs.kde.org/show_bug.cgi?id=485971 --- Comment #6 from Gábor Katona --- What do you mean by full xprop? I got the window id of the tray icon by running xwininfo and clicking on the icon than xprop -id -root said: _NET_SHOWING_DESKTOP(CARDINAL) = 0 _QT_GET_TIMESTAMP(INTEGER) = GDK_VISUALS(INTEGER) = 1022, 857 _NET_WORKAREA(CARDINAL) = 0, 0, 1920, 1036, 0, 0, 1920, 1036, 0, 0, 1920, 1036, 0, 0, 1920, 1036 RESOURCE_MANAGER(STRING) = "Xcursor.size:\t24\nXcursor.theme:\tbreeze_cursors\nXft.antialias:\t1\nXft.dpi:\t96\nXft.hinting:\t-1\nXft.rgba:\tnone\n" _KDE_NET_WM_BACKGROUND_CONTRAST_REGION(_KDE_NET_WM_BACKGROUND_CONTRAST_REGION) = 0x0 _KDE_NET_WM_BLUR_BEHIND_REGION(_KDE_NET_WM_BLUR_BEHIND_REGION) = 0x0 _KDE_WINDOW_HIGHLIGHT(_KDE_WINDOW_HIGHLIGHT) = 0x0 _KDE_SLIDE(_KDE_SLIDE) = 0x0 _NET_CLIENT_LIST_STACKING(WINDOW): window id # 0x107, 0x0, 0x0, 0x0, 0x0, 0x23a, 0x1ec, 0x0, 0x0 _NET_CLIENT_LIST(WINDOW): window id # 0x107, 0x23a, 0x1ec _NET_DESKTOP_GEOMETRY(CARDINAL) = 1920, 1080 _NET_ACTIVE_WINDOW(WINDOW): window id # 0x0 _NET_DESKTOP_NAMES(UTF8_STRING) = "Desktop 1", "Desktop 2", "Desktop 3", "Desktop 4" _NET_CURRENT_DESKTOP(CARDINAL) = 2 _NET_DESKTOP_VIEWPORT(CARDINAL) = 0, 0, 0, 0, 0, 0, 0, 0 _NET_NUMBER_OF_DESKTOPS(CARDINAL) = 4 _NET_DESKTOP_LAYOUT(CARDINAL) = 0, 2, 2, 0 _NET_SUPPORTING_WM_CHECK(WINDOW): window id # 0x21 _NET_SUPPORTED(ATOM) = _NET_SUPPORTED, _NET_SUPPORTING_WM_CHECK, _NET_CLIENT_LIST, _NET_CLIENT_LIST_STACKING, _NET_NUMBER_OF_DESKTOPS, _NET_DESKTOP_GEOMETRY, _NET_CURRENT_DESKTOP, _NET_DESKTOP_NAMES, _NET_ACTIVE_WINDOW, _NET_WORKAREA, _NET_DESKTOP_LAYOUT, _NET_CLOSE_WINDOW, _NET_RESTACK_WINDOW, _NET_SHOWING_DESKTOP, _NET_WM_MOVERESIZE, _NET_MOVERESIZE_WINDOW, _NET_WM_NAME, _NET_WM_VISIBLE_NAME, _NET_WM_DESKTOP, _NET_WM_WINDOW_TYPE, _NET_WM_WINDOW_TYPE_NORMAL, _NET_WM_WINDOW_TYPE_DESKTOP, _NET_WM_WINDOW_TYPE_DOCK, _NET_WM_WINDOW_TYPE_TOOLBAR, _NET_WM_WINDOW_TYPE_MENU, _NET_WM_WINDOW_TYPE_DIALOG, _NET_WM_WINDOW_TYPE_UTILITY, _NET_WM_WINDOW_TYPE_SPLASH, _KDE_NET_WM_WINDOW_TYPE_OVERRIDE, _NET_WM_STATE, _NET_WM_STATE_MODAL, _NET_WM_STATE_MAXIMIZED_VERT, _NET_WM_STATE_MAXIMIZED_HORZ, _NET_WM_STATE_SHADED, _NET_WM_STATE_SKIP_TASKBAR, _NET_WM_STATE_SKIP_PAGER, _KDE_NET_WM_STATE_SKIP_SWITCHER, _NET_WM_STATE_HIDDEN, _NET_WM_STATE_FULLSCREEN, _NET_WM_STATE_ABOVE, _NET_WM_STATE_STAYS_ON_TOP, _NET_WM_STATE_BELOW, _NET_WM_STATE_DEMANDS_ATTENTION, _NET_WM_STATE_FOCUSED, _NET_WM_STRUT, _NET_WM_STRUT_PARTIAL, _NET_WM_ICON_GEOMETRY, _NET_WM_ICON, _NET_WM_PID, _NET_WM_PING, _NET_WM_USER_TIME, _NET_STARTUP_ID, _NET_WM_WINDOW_OPACITY, _NET_WM_FULLSCREEN_MONITORS, _NET_WM_ALLOWED_ACTIONS, _NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE, _NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_SHADE, _NET_WM_ACTION_MAXIMIZE_VERT, _NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE, _NET_FRAME_EXTENTS, _KDE_NET_WM_FRAME_STRUT, _NET_WM_FULL_PLACEMENT, _KDE_NET_WM_ACTIVITIES, _KDE_NET_WM_SHADOW, _NET_WM_OPAQUE_REGION, _GTK_FRAME_EXTENTS, _GTK_SHOW_WINDOW_MENU _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "", "" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485971] Keepass tray icon breaks nearby icon, also tooltip is messed up
https://bugs.kde.org/show_bug.cgi?id=485971 --- Comment #5 from Gábor Katona --- Created attachment 168807 --> https://bugs.kde.org/attachment.cgi?id=168807&action=edit Output of xwininfo -tree -root Attached the output of xwininfo -tree -root. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485708] KDE panel system tray pop ups become non-functioning when panel switches from floating to not floating or floating turned off
https://bugs.kde.org/show_bug.cgi?id=485708 --- Comment #2 from bailey.walt...@bixal.com --- I can confirm the same issue and the workaround worked for me as well, thank you! Operating System: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 PRO 7840HS w/ Radeon 780M Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: HP -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485708] KDE panel system tray pop ups become non-functioning when panel switches from floating to not floating or floating turned off
https://bugs.kde.org/show_bug.cgi?id=485708 bailey.walt...@bixal.com changed: What|Removed |Added CC||bailey.walt...@bixal.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433077] plasma-firewall is in section "KDE" instead of "kde"
https://bugs.kde.org/show_bug.cgi?id=433077 Adrien Beau changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Adrien Beau --- This was apparently fixed some time ago, this is all correct in Plasma 6.0.4. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 485972] crash after invocation and upon close from krunner: QMimeProviderBase::isMimeTypeGlobsExcluded()
https://bugs.kde.org/show_bug.cgi?id=485972 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484682] Since 6.0.3, global shortcuts do not persist settings across sessions and behave erratically
https://bugs.kde.org/show_bug.cgi?id=484682
--- Comment #13 from Dmitrii Chermnykh ---
(In reply to Nicolas Fella from comment #10)
> (In reply to Naxdy from comment #5)
> > I've been able to confirm that simply commenting out this line (
> > https://invent.kde.org/plasma/kglobalacceld/-/merge_requests/47/
> > diffs?view=inline#014186ddf2dd1aa75709115400e25e06ba6e2d47_260_262 ) fixes
> > the issues on NixOS. Both shortcuts resetting and the glitchy behavior of
> > duplicate entries being present.
> >
> > It seems that either component->uniqueName() is not correctly resolving to
> > the .desktop file's name, or that
>
> Can you tell what the value of component->uniqueName() is?
>
> > QStandardPaths::locate(QStandardPaths::GenericDataLocation,
> > QLatin1String("kglobalaccel/") + component->uniqueName()).isEmpty()
> >
> > is not looking in the right place for desktop files.
For me in PyQT it resolves to the correct file and qdbus shows that
`component->uniqueName()` for spectacle is `org.kde.spectacle.desktop`
In [17]:
QStandardPaths.locate(QStandardPaths.StandardLocation.GenericDataLocation,
"kglobalaccel/org.kde.spectacle.desktop")
Out[17]: '/run/current-system/sw/share/kglobalaccel/org.kde.spectacle.desktop'
qdbus org.kde.kglobalaccel /component/org_kde_spectacle_desktop
org.kde.kglobalaccel.Component.uniqueName
org.kde.spectacle.desktop
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 485971] Keepass tray icon breaks nearby icon, also tooltip is messed up
https://bugs.kde.org/show_bug.cgi?id=485971 --- Comment #4 from David Edmundson --- Do you have any scaling set? Can I see output of: ` xwininfo -tree -root` (note this will have the titles of any open X11 windows, I'm only after the keepass icon) If you can get the full xprop for that it would be great. Otherwise I'll have to try to reproduce it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485971] Keepass tray icon breaks nearby icon, also tooltip is messed up
https://bugs.kde.org/show_bug.cgi?id=485971 David Edmundson changed: What|Removed |Added Resolution|FIXED |--- Component|System Tray |XembedSNIProxy Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 472453] krfb asserts in PWFrameBuffer::cursorPosition
https://bugs.kde.org/show_bug.cgi?id=472453 Yaroslav Sidlovsky changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/netw ||ork/krfb/-/commit/6e7a5ba56 ||966ea1b67400be9ab7c82885abb ||76be --- Comment #10 from Yaroslav Sidlovsky --- Git commit 6e7a5ba56966ea1b67400be9ab7c82885abb76be by Yaroslav Sidlovsky. Committed on 22/04/2024 at 14:06. Pushed by alexeymin into branch 'master'. Fixed crash calling PWFrameBuffer::cursorPosition() Return default QPoint when `d->cursor` is not set. M +6-1framebuffers/pipewire/pw_framebuffer.cpp https://invent.kde.org/network/krfb/-/commit/6e7a5ba56966ea1b67400be9ab7c82885abb76be -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485971] Keepass tray icon breaks nearby icon, also tooltip is messed up
https://bugs.kde.org/show_bug.cgi?id=485971 Gábor Katona changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #3 from Gábor Katona --- (In reply to David Edmundson from comment #2) > Whilst this is open can you run > > systemctl --user stop plasma-xembedsniproxy.service > > > and confirm if the icon goes away? Yes, the keepass icon goes away when running this and restores if using start. Additional info that the non responding parts of the nearby systray-x icon seem to have some strange shape. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484682] Since 6.0.3, global shortcuts do not persist settings across sessions and behave erratically
https://bugs.kde.org/show_bug.cgi?id=484682 --- Comment #12 from Dmitrii Chermnykh --- On NixOS: If I do "edit application" in plasma menu it shows the location of .desktop file as "/nix/store/.../share/applications", but if I try to find the .desktop item in XDG_DATA_DIRS it resolves into "/run/current-system/sw/share": fd spectacle.desktop $(echo $XDG_DATA_DIRS | sd ':' ' ') [fd error]: Search path '/home/chermnyx/.local/share/flatpak/exports/share' is not a directory. [fd error]: Search path '/home/chermnyx/.nix-profile/share' is not a directory. [fd error]: Search path '/nix/profile/share' is not a directory. [fd error]: Search path '/home/chermnyx/.local/state/nix/profile/share' is not a directory. [fd error]: Search path '/nix/var/nix/profiles/default/share' is not a directory. /run/current-system/sw/share/applications/org.kde.spectacle.desktop /run/current-system/sw/share/kglobalaccel/org.kde.spectacle.desktop It seems that the symlinks are getting resolved somewhere and plasma gets confused by nix store paths It also makes any existing .desktop entry cache invalid on each nixos system rebuild (nixos does `rm -fv $HOME/.cache/ksycoca*` as a workaround: https://github.com/NixOS/nixpkgs/pull/292748/files) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485849] Plasmashell freezes in X11 but works again after right click
https://bugs.kde.org/show_bug.cgi?id=485849 --- Comment #1 from Guido --- Mmmmh it doesn't seem to be entirely causal. The problem occurs if I launch an app from the menu while if I launch it from the panel it doesn't. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485971] Keepass tray icon breaks nearby icon, also tooltip is messed up
https://bugs.kde.org/show_bug.cgi?id=485971 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- Whilst this is open can you run systemctl --user stop plasma-xembedsniproxy.service and confirm if the icon goes away? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483912] Overview, Flip Switch, Show FPS, other OpenGL effects render as black screen when KWIN_OPENGL_INTERFACE=egl
https://bugs.kde.org/show_bug.cgi?id=483912 --- Comment #6 from Guido --- (In reply to Conor Dockry from comment #5) > (In reply to Guido from comment #4) > > intel-media-driver > intel-vaapi-driver > > > lspci -k > 00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-P [Iris Xe > Graphics] (rev 04) > Subsystem: Lenovo Device 2309 > Kernel driver in use: i915 > Kernel modules: i915, xe In my case: 00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) DeviceName: Onboard - Video Subsystem: Dell Device 0a02 Kernel driver in use: i915 Kernel modules: i915, xe -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483912] Overview, Flip Switch, Show FPS, other OpenGL effects render as black screen when KWIN_OPENGL_INTERFACE=egl
https://bugs.kde.org/show_bug.cgi?id=483912 --- Comment #5 from Conor Dockry --- (In reply to Guido from comment #4) intel-media-driver intel-vaapi-driver > lspci -k 00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-P [Iris Xe Graphics] (rev 04) Subsystem: Lenovo Device 2309 Kernel driver in use: i915 Kernel modules: i915, xe -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485966] Implement freedesktop wallpaper API
https://bugs.kde.org/show_bug.cgi?id=485966 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from David Edmundson --- > the wallpaper interface of the freedesktop specification. What are you referring to? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483912] Overview, Flip Switch, Show FPS, other OpenGL effects render as black screen when KWIN_OPENGL_INTERFACE=egl
https://bugs.kde.org/show_bug.cgi?id=483912 --- Comment #4 from Guido --- (In reply to Conor Dockry from comment #0) What graphics card do you have? What drivers are you using? In my case (Intel igpu Tigerlake) kwin totally crashes. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 485972] New: crash after invocation and upon close from krunner: QMimeProviderBase::isMimeTypeGlobsExcluded()
https://bugs.kde.org/show_bug.cgi?id=485972 Bug ID: 485972 Summary: crash after invocation and upon close from krunner: QMimeProviderBase::isMimeTypeGlobsExcluded() Classification: Applications Product: gwenview Version: 24.02.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: gb...@bzb.us Target Milestone: --- Description of problem: https://bugzilla.redhat.com/show_bug.cgi?id=2276475 Open krunner and search for jpg to display. Enter statue_liberty Click on statue_liberty to open in gwenview gwenview opens and displays jpg close gwenview a few moments after gwenview is closed, application crashes This happens not everytime I open gwenview through krunner in this manner, however it happens more often than not. Started occuring with Plasma 6 - F40 Version-Release number of selected component: gwenview-1:24.02.2-2.fc40 Additional info: reporter: libreport-2.17.15 type: CCpp reason: gwenview killed by SIGSEGV journald_cursor: s=3bf00287d3fd48eb9f1d293c6e6dec90;i=5c8d785;b=a855101d7d834545b08c5d01c38da671;m=cb5befaf9;t=616b025631f85;x=80cf2893ee48ea78 executable: /usr/bin/gwenview cmdline:/usr/bin/gwenview /var/www/html/actors/Statue_Liberty.jpg cgroup: 0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.gwenview-c2653f9b22494e11a2029af1a3122548.scope rootdir:/ uid:1000 kernel: 6.8.7-300.fc40.x86_64 package:gwenview-1:24.02.2-2.fc40 runlevel: N 5 backtrace_rating: 4 crash_function: QMimeProviderBase::isMimeTypeGlobsExcluded Truncated backtrace: Thread no. 1 (11 frames) #0 QMimeProviderBase::isMimeTypeGlobsExcluded at /usr/src/debug/qt6-qtbase-6.7.0-3.fc40.x86_64/src/corelib/mimetypes/qmimeprovider.cpp:105 #1 QMimeBinaryProvider::matchGlobList at /usr/src/debug/qt6-qtbase-6.7.0-3.fc40.x86_64/src/corelib/mimetypes/qmimeprovider.cpp:261 #2 QMimeBinaryProvider::addFileNameMatches at /usr/src/debug/qt6-qtbase-6.7.0-3.fc40.x86_64/src/corelib/mimetypes/qmimeprovider.cpp:222 #3 QMimeDatabasePrivate::findByFileName at /usr/src/debug/qt6-qtbase-6.7.0-3.fc40.x86_64/src/corelib/mimetypes/qmimedatabase.cpp:209 #4 QMimeDatabasePrivate::mimeTypeForFileNameAndData at /usr/src/debug/qt6-qtbase-6.7.0-3.fc40.x86_64/src/corelib/mimetypes/qmimedatabase.cpp:366 #5 QMimeDatabasePrivate::mimeTypeForFile at /usr/src/debug/qt6-qtbase-6.7.0-3.fc40.x86_64/src/corelib/mimetypes/qmimedatabase.cpp:492 #6 QMimeDatabase::mimeTypeForFile at /usr/src/debug/qt6-qtbase-6.7.0-3.fc40.x86_64/src/corelib/mimetypes/qmimedatabase.cpp:646 #7 createUDSEntry at /usr/src/debug/kf6-kio-6.1.0-2.fc40.x86_64/src/kioworkers/file/file_unix.cpp:477 #8 FileProtocol::listDir at /usr/src/debug/kf6-kio-6.1.0-2.fc40.x86_64/src/kioworkers/file/file_unix.cpp:1112 #9 KIO::WorkerSlaveBaseBridge::listDir at /usr/src/debug/kf6-kio-6.1.0-2.fc40.x86_64/src/core/workerbase_p.h:121 #10 KIO::SlaveBase::dispatch at /usr/src/debug/kf6-kio-6.1.0-2.fc40.x86_64/src/core/slavebase.cpp:1229 -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 482594] Screen sharing/recording fails with error message "Failed to connect PipeWire context"
https://bugs.kde.org/show_bug.cgi?id=482594 Andrew Simmons changed: What|Removed |Added CC||agsimmo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 485965] Konsole line numbers do not adhere to LTR/RTL text preference.
https://bugs.kde.org/show_bug.cgi?id=485965 --- Comment #5 from Roke Julian Lockhart Beedell <4wy78...@rokejulianlockhart.addy.io> --- (In reply to Matan Ziv-Av from comment #3) I can understand that being a problem when enabling it *during* a session, but I'd never do that, so if enabled permanently, the user could start the session with it already on the left, if that makes sense. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485971] Keepass tray icon breaks nearby icon, also tooltip is messed up
https://bugs.kde.org/show_bug.cgi?id=485971 --- Comment #1 from Gábor Katona --- Created attachment 168806 --> https://bugs.kde.org/attachment.cgi?id=168806&action=edit Broken tooltip over nerby icon -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 485965] Konsole line numbers do not adhere to LTR/RTL text preference.
https://bugs.kde.org/show_bug.cgi?id=485965 --- Comment #4 from Roke Julian Lockhart Beedell <4wy78...@rokejulianlockhart.addy.io> --- (In reply to Matan Ziv-Av from comment #3) That's a good point. However, in that case, although my rationale doesn't stand, the issue does - I doubt that it renders on the left when the user is using RTL text? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485971] New: Keepass tray icon breaks nearby icon, also tooltip is messed up
https://bugs.kde.org/show_bug.cgi?id=485971 Bug ID: 485971 Summary: Keepass tray icon breaks nearby icon, also tooltip is messed up Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: kato...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 Created attachment 168805 --> https://bugs.kde.org/attachment.cgi?id=168805&action=edit Bad tooltip in upper left screen corner SUMMARY I use keepass2 under wine (not mono). Keepass2 has a minimize to tray option and it works (and worked in KDE5) fine. Since KDE6 however the tray icon is somehow broken: 1. After it is first started the tooltip of any window or desktop icon in the upper left corner of the screen will be the tooltip of Keepass (see keepass1.jpg). When Keepass is maximized and minimized it resolves. 2. The tray icon (the padlock) affects the nearby systray-x (Thunderbird) icon: hoovering over the systray-x icon the tooltip of keepass appears (keepass2.jpg) and clicking the icon act as clicking on keepass2 icon. However this does not always happen, because in some cases only some part of the systray-x icon is not clickable at all while other parts function normally. Some the keepass icon extends over the systray-x icon. STEPS TO REPRODUCE 1. Run Thunderbird with systray-x, so we have a tray icon for it 2. Run keepass with wine 3. Hover to the upper left corner after starting 4. Hover over Tb icon and try to click different parts. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20240418 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 405752] Make Konsole search field longer, better if it fill all width of a Konsole window
https://bugs.kde.org/show_bug.cgi?id=405752 Roke Julian Lockhart Beedell <4wy78...@rokejulianlockhart.addy.io> changed: What|Removed |Added CC||4wy78uwh@rokejulianlockhart ||.addy.io -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 485923] Make line numbers discoverable in Konsole.
https://bugs.kde.org/show_bug.cgi?id=485923 Roke Julian Lockhart Beedell <4wy78...@rokejulianlockhart.addy.io> changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=485970 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 485970] Konsole line numbers render atop command output.
https://bugs.kde.org/show_bug.cgi?id=485970 Roke Julian Lockhart Beedell <4wy78...@rokejulianlockhart.addy.io> changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=485923 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 485970] Konsole line numbers render atop command output.
https://bugs.kde.org/show_bug.cgi?id=485970 --- Comment #1 from Roke Julian Lockhart Beedell <4wy78...@rokejulianlockhart.addy.io> --- Created attachment 168804 --> https://bugs.kde.org/attachment.cgi?id=168804&action=edit Depiction of the problem. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 485970] New: Konsole line numbers render atop command output.
https://bugs.kde.org/show_bug.cgi?id=485970 Bug ID: 485970 Summary: Konsole line numbers render atop command output. Classification: Applications Product: konsole Version: 24.02.2 Platform: Fedora RPMs URL: https://discuss.kde.org/t/how-to-enable-line-numbers-i n-konsole/14435#always-3 OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: emulation Assignee: konsole-de...@kde.org Reporter: 4wy78...@rokejulianlockhart.addy.io Target Milestone: --- Flags: performance- STEPS TO REPRODUCE 1. Install the Fedora 40 Beta KDE Spin from https://download.fedoraproject.org/pub/fedora/linux/releases/test/40_Beta/Spins/x86_64/iso/Fedora-KDE-Live-x86_64-40_Beta-1.10.iso 2. Install konsole-24.02.2-1.fc40.x86_64.rpm from https://kojipkgs.fedoraproject.org//packages/konsole/24.02.2/1.fc40/x86_64/konsole-24.02.2-1.fc40.x86_64.rpm 3. Enable "Always" mode, as https://discuss.kde.org/t/how-to-enable-line-numbers-in-konsole/14435#always-3 describes. 4. Shorten the width of the terminal so that command output wraps. OBSERVED RESULT The line numbers render over the command output. EXPECTED RESULT They shouldn't. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: ASRock Product Name: X670E Taichi -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 485969] Konsole line numbers render behind the scrollbar at large values.
https://bugs.kde.org/show_bug.cgi?id=485969 --- Comment #1 from Roke Julian Lockhart Beedell <4wy78...@rokejulianlockhart.addy.io> --- Created attachment 168803 --> https://bugs.kde.org/attachment.cgi?id=168803&action=edit Depiction of the problem. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 485923] Make line numbers discoverable in Konsole.
https://bugs.kde.org/show_bug.cgi?id=485923 Roke Julian Lockhart Beedell <4wy78...@rokejulianlockhart.addy.io> changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=485969 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 485969] New: Konsole line numbers render behind the scrollbar at large values.
https://bugs.kde.org/show_bug.cgi?id=485969 Bug ID: 485969 Summary: Konsole line numbers render behind the scrollbar at large values. Classification: Applications Product: konsole Version: 24.02.2 Platform: Fedora RPMs URL: https://discuss.kde.org/t/how-to-enable-line-numbers-i n-konsole/14435#always-3 OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: emulation Assignee: konsole-de...@kde.org Reporter: 4wy78...@rokejulianlockhart.addy.io Target Milestone: --- Flags: performance- SUMMARY The last few numbers render behind the scrollbar, rendering them invisible. STEPS TO REPRODUCE 1. Install the Fedora 40 Beta KDE Spin from https://download.fedoraproject.org/pub/fedora/linux/releases/test/40_Beta/Spins/x86_64/iso/Fedora-KDE-Live-x86_64-40_Beta-1.10.iso 2. Install konsole-24.02.2-1.fc40.x86_64.rpm from https://kojipkgs.fedoraproject.org//packages/konsole/24.02.2/1.fc40/x86_64/konsole-24.02.2-1.fc40.x86_64.rpm 3. Enable "Always" mode, as https://discuss.kde.org/t/how-to-enable-line-numbers-in-konsole/14435#always-3 describes. OBSERVED RESULT The last few numbers render behind the scrollbar, rendering them invisible. EXPECTED RESULT They shouldn't. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: ASRock Product Name: X670E Taichi -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 485968] New: Clazy doesn't build against Clang 18+
https://bugs.kde.org/show_bug.cgi?id=485968 Bug ID: 485968 Summary: Clazy doesn't build against Clang 18+ Classification: Developer tools Product: clazy Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: t...@ngus.net CC: smart...@kde.org Target Milestone: --- SUMMARY Attempts to build Clazy against Clang 18 and later fail. STEPS TO REPRODUCE 1. Install Clang 18. 2. Checkout Clazy master branch. 3. Build Clazy OBSERVED RESULT ... [120/120] Linking CXX executable bin/clazy-standalone FAILED: bin/clazy-standalone : && /usr/bin/c++ -fno-common -Woverloaded-virtual -Wcast-qual -fno-strict-aliasing -pedantic -Wno-long-long -Wall -W -Wno-unused-parameter -Wwrite-strings -fno-exceptions -fno-rtti -fPIC -O3 -DNDEBUG CMakeFiles/clazy-standalone.dir/src/ClazyStandaloneMain.cpp.o -o bin/clazy-standalone -L/usr/lib/llvm-18/lib -Wl,-rpath,/usr/lib/llvm-18/lib:/home/runner/work/graphia/graphia/clazy/lib: lib/ClazyPlugin.so /usr/lib/llvm-18/lib/libclangFrontend.a /usr/lib/llvm-18/lib/libclangDriver.a /usr/lib/llvm-18/lib/libclangCodeGen.a /usr/lib/llvm-18/lib/libclangSema.a /usr/lib/llvm-18/lib/libclangAnalysis.a /usr/lib/llvm-18/lib/libclangRewriteFrontend.a /usr/lib/llvm-18/lib/libclangRewrite.a /usr/lib/llvm-18/lib/libclangAST.a /usr/lib/llvm-18/lib/libclangASTMatchers.a /usr/lib/llvm-18/lib/libclangParse.a /usr/lib/llvm-18/lib/libclangLex.a /usr/lib/llvm-18/lib/libclangBasic.a /usr/lib/llvm-18/lib/libclangARCMigrate.a /usr/lib/llvm-18/lib/libclangEdit.a /usr/lib/llvm-18/lib/libclangFrontendTool.a /usr/lib/llv /usr/bin/ld: lib/ClazyPlugin.so: undefined reference to `clang::api_notes::APINotesManager::~APINotesManager()' /usr/bin/ld: lib/ClazyPlugin.so: undefined reference to `clang::api_notes::APINotesManager::loadCurrentModuleAPINotes(clang::Module*, bool, llvm::ArrayRef, std::allocator > >)' /usr/bin/ld: lib/ClazyPlugin.so: undefined reference to `clang::api_notes::APINotesManager::APINotesManager(clang::SourceManager&, clang::LangOptions const&)' collect2: error: ld returned 1 exit status EXPECTED RESULT Successful build. SOFTWARE/OS VERSIONS Ubuntu 20.04 LTS Clang 18 installed via https://apt.llvm.org/ -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 485923] Make line numbers discoverable in Konsole.
https://bugs.kde.org/show_bug.cgi?id=485923 Roke Julian Lockhart Beedell <4wy78...@rokejulianlockhart.addy.io> changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=485967 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 485967] New: Konsole line numbers render random numbers in margin when scrolling from large to small values.
https://bugs.kde.org/show_bug.cgi?id=485967 Bug ID: 485967 Summary: Konsole line numbers render random numbers in margin when scrolling from large to small values. Classification: Applications Product: konsole Version: 24.02.2 Platform: Fedora RPMs URL: https://discuss.kde.org/t/how-to-enable-line-numbers-i n-konsole/14435#always-3 OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: emulation Assignee: konsole-de...@kde.org Reporter: 4wy78...@rokejulianlockhart.addy.io Target Milestone: --- Flags: performance- Created attachment 168802 --> https://bugs.kde.org/attachment.cgi?id=168802&action=edit Depiction of the problem. SUMMARY Line numbers in Konsole render with a gap between them and seemingly random numbers to their right when the user scrolls from a large line number value to a small one. They disappear when the focus of the scrollbar is returned. STEPS TO REPRODUCE 1. Install the Fedora 40 Beta KDE Spin from https://download.fedoraproject.org/pub/fedora/linux/releases/test/40_Beta/Spins/x86_64/iso/Fedora-KDE-Live-x86_64-40_Beta-1.10.iso 2. Install konsole-24.02.2-1.fc40.x86_64.rpm from https://kojipkgs.fedoraproject.org//packages/konsole/24.02.2/1.fc40/x86_64/konsole-24.02.2-1.fc40.x86_64.rpm 3. Enable "Always" mode, as https://discuss.kde.org/t/how-to-enable-line-numbers-in-konsole/14435#always-3 describes. OBSERVED RESULT The line numbers render with a gap between them and seemingly random numbers to their right when the user scrolls from a large line number value to a small one. They disappear when the focus of the scrollbar is returned. EXPECTED RESULT This artefact shouldn't be present whilst scrolling. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: ASRock Product Name: X670E Taichi -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 485965] Konsole line numbers do not adhere to LTR/RTL text preference.
https://bugs.kde.org/show_bug.cgi?id=485965 Matan Ziv-Av changed: What|Removed |Added CC||ma...@svgalib.org --- Comment #3 from Matan Ziv-Av --- (In reply to Roke Julian Lockhart Beedell from comment #1) > (In reply to Roke Julian Lockhart Beedell from comment #0) > EXPECTED RESULT > They should render on the left, like all other text editors and terminals > that I've used, with a 1-px line to separate them (like KWrite, Kate, and > KDevelop). I am not sure this is an expected behaviour. I do not have the numbers always enabled, but only show them (rarely) when needed. If they were on the left, they might need to change the terminal size when shown, which is undesirable. See similar discussion here: https://invent.kde.org/utilities/konsole/-/merge_requests/972 . That's why the line numbers are actually an overlay, which is usually less problematic when on the right. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 485936] filelight not working after system update QQmlComponent: Component is not ready org.kde.kcoreaddons not installed on gentoo+gnome45
https://bugs.kde.org/show_bug.cgi?id=485936 Andreas Sturmlechner changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED CC||ast...@gentoo.org --- Comment #1 from Andreas Sturmlechner --- Thanks. This is a downstream bug, which is where it is going to be fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485966] Implement freedesktop wallpaper API
https://bugs.kde.org/show_bug.cgi?id=485966 Lorenz Hoffmann changed: What|Removed |Added Keywords||junior-jobs -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485966] Implement freedesktop wallpaper API
https://bugs.kde.org/show_bug.cgi?id=485966 --- Comment #1 from Lorenz Hoffmann --- There is already org.kde.plasmashell PlasmaShell/org.kde.PlasmaShell/setWallpaper, so it should be pretty straightforward. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485966] New: Implement freedesktop wallpaper API
https://bugs.kde.org/show_bug.cgi?id=485966 Bug ID: 485966 Summary: Implement freedesktop wallpaper API Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: hoffmann_lor...@protonmail.com CC: k...@davidedmundson.co.uk 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 This is a feature request. I am not sure if this belongs here, let me know. As far as I can tell, Plasma does not implement the wallpaper interface of the freedesktop specification. This would be very useful, as it gives a desktop-independent API to developers. -- You are receiving this mail because: You are watching all bug changes.
