[plasma-pa] [Bug 456164] When adjusting the volume of kde via a bluetooth headset the volume hud does not appear.
https://bugs.kde.org/show_bug.cgi?id=456164 fanzhuyi...@gmail.com changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-pa/-/commit/00657 ||6a7c1ada5dd7a225498636b9666 ||d510af81 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #3 from fanzhuyi...@gmail.com --- Git commit 006576a7c1ada5dd7a225498636b9666d510af81 by Yifan Zhu, on behalf of Bharadwaj Raju. Committed on 17/12/2023 at 08:52. Pushed by fanzhuyifan into branch 'master'. Always show volume OSD for preferred sink M +7-0applet/contents/ui/main.qml https://invent.kde.org/plasma/plasma-pa/-/commit/006576a7c1ada5dd7a225498636b9666d510af81 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478628] Plasmashell segfaults when trying to remove the Kicker (application menu) widget from the desktop
https://bugs.kde.org/show_bug.cgi?id=478628 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478628] Plasmashell segfaults when trying to remove the Kicker (application menu) widget from the desktop
https://bugs.kde.org/show_bug.cgi?id=478628 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478629] Kate is very slow to Launch, and very slow to open even a simple Text file with a couple paragraphs (even on a fresh Win11 install)
https://bugs.kde.org/show_bug.cgi?id=478629 Waqar Ahmed changed: What|Removed |Added CC||waqar@gmail.com --- Comment #1 from Waqar Ahmed --- The first launch of Kate is slow because I assume we are loading a lot of libs. I have noticed this as well. But in my experience, subsequent launches were faster. Is it not the case? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478511] Switch to Tab per shortcut
https://bugs.kde.org/show_bug.cgi?id=478511 Waqar Ahmed changed: What|Removed |Added CC||waqar@gmail.com --- Comment #1 from Waqar Ahmed --- You can use Alt+left/right for quick nav between tabs -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478528] Kate editor can't validate XML files ("Error: Failed to find xmllint"), even though the plugin is activated and libxml2 is present.
https://bugs.kde.org/show_bug.cgi?id=478528 Waqar Ahmed changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #5 from Waqar Ahmed --- Like I said, you need to install xmllint. That is what kates error msg says. Xmllint is a program just like Kate. Its not a dll/library. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476554] a window will appear on all virtual desktops when showing desktop grid randomly
https://bugs.kde.org/show_bug.cgi?id=476554 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from fanzhuyi...@gmail.com --- (In reply to jmestreraclosa from comment #3) > Additionally, I have not encountered the bug since I posted this. Closing as fixed then.. Feel free to reopen if you see this again! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478630] New: When scrolling on taskbar, scrolling up is left and down is right. I would like to have an option for the opposite behavior.
https://bugs.kde.org/show_bug.cgi?id=478630 Bug ID: 478630 Summary: When scrolling on taskbar, scrolling up is left and down is right. I would like to have an option for the opposite behavior. Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Ubuntu OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: tmiller0...@gmail.com CC: qydwhotm...@gmail.com Target Milestone: 1.0 SUMMARY When scrolling on taskbar, scrolling up switches one app left and down switches right. I would like to have an option for the opposite behavior. I just personally find it easier to conceptualize down=left and up=right than the other way around. Scrolling over the desktop/pager to switch virtual desktops works the same way, so it would be ideal to have an option there too. STEPS TO REPRODUCE 1. Enable mouse wheel in task manager config 2. No option for inverted scroll 3. Scroll over the taskbar SOFTWARE/OS VERSIONS Linux: Kubuntu 23.10 (Wayland session) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477539] Snapping a window to maximize on screen 1 when another application on second is maximized creates artifacts on the screen next to it
https://bugs.kde.org/show_bug.cgi?id=477539 fanzhuyi...@gmail.com changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||fanzhuyi...@gmail.com --- Comment #4 from fanzhuyi...@gmail.com --- Could you share your display settings when you can produce this? e.g., the output of `kscreen-doctor -o`. Thanks! I am suspecting that this might be related to the fractional scaling stuff, like https://bugs.kde.org/show_bug.cgi?id=477791 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478629] New: Kate is very slow to Launch, and very slow to open even a simple Text file with a couple paragraphs (even on a fresh Win11 install)
https://bugs.kde.org/show_bug.cgi?id=478629 Bug ID: 478629 Summary: Kate is very slow to Launch, and very slow to open even a simple Text file with a couple paragraphs (even on a fresh Win11 install) Classification: Applications Product: kate Version: 23.08.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: zacch...@gmail.com 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 *** STEPS TO REPRODUCE 1. Open a simple Text file with 2 paragraphs of texts 2. Wait, and wait, and wiat 3. It opens only after between 10-15s, OBSERVED RESULT This lag when opening a simple Text file is huge compared to Notepad++ and others. EXPECTED RESULT Opening Kate in less than a second, even less... SOFTWARE/OS VERSIONS Windows: 11 22H2 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I've tried Kate on a fresh setup of Win11, and same issue. Very slow at launching the app itself, or opening a file. It's so irritating that sometimes I wish I could find an alternative (but Kate is the most well thought-out text editor out there, and I've tested SublimeText, Atom, and so on... Notepad++ is great but its UI is aweful, not as refined and tasteful as Kate IMO) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477684] dolphin --daemon Crashes Peacefully After Opening First Window Through DBus
https://bugs.kde.org/show_bug.cgi?id=477684 yranjeetyadav1234567...@gmail.com changed: What|Removed |Added CC||yranjeetyadav1234567890@gma ||il.com --- Comment #3 from yranjeetyadav1234567...@gmail.com --- (In reply to John Hao from comment #0) > SUMMARY > Dolphin does not spawn a window when called with DBus using FileManager1 > (through Firefox or directly) without an active process, and the process > crashes peacefully when interacting with it through DBus after opening its > first window. > > (I may not be using the right term of crash as the exit may be intentional, > but the exit incorrectly interferes with using Dolphin from DBus) > > I cannot upload the backtrace: I am unfamiliar with gdb and when following > the guide, backtrace.txt is empty due to the crashing process crashing > peacefully. > > STEPS TO REPRODUCE > 1. Override /usr/share/dbus-1/services/org.freedesktop.FileManager1.service > in .local > ~/.local/share/dbus-1/services/org.freedesktop.FileManager1.service: > ``` > [D-BUS Service] > Name=org.freedesktop.FileManager1 > Exec=/usr/bin/dolphin --daemon > SystemdService=plasma-dolphin.service > ``` > 2. Use Firefox's "open in folder" for Downloads > > OBSERVED RESULT > Dolphin window does not appear, except for the first time after a reboot. > > EXPECTED RESULT > Dolphin window appears. > > SOFTWARE/OS VERSIONS > Linux: Fedora 39 Sericea, SwayWM (not KDE Plasma) > Qt Version: 5.15.11 / 6.6.0 > > ADDITIONAL INFORMATION > Upon spamming the open in folder button at a rapid pace, the dolphin window > appears. > Firefox appears to be using DBus for "open in folder". Using d-feet, I > interacted with the org.freedesktop.FileManager1, which shows it spawns a > dolphin process. Using its ShowFolders interface removes the dolphin process > and shows nothing. > Running dolphin --daemon in a terminal connects it to the FileManager1 DBus > and allows Firefox to open a folder once, but after opening this folder, > dolphin --daemon peacefully exits. The peaceful exit after opening folder > also happens when using FileManager1 DBus directly through d-feet, and using > org.kde.dolphin-pid through d-feet. It does not happen when running dolphin > --new-window from another command line. It also happens on Hyprland/sway/gnome using any browser it can be chromiuim or firefox "show in folder" doesnt launch dolphin window and in journelctl it show starting dolphin but there is no window if i manually start "dolphin --daemon" it launch for one time and daemon exits with this "kf.windowsystem: Could not find any platform plugin" . any other filemanger works . -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 449233] Only one line is saved when multiple lines are scrolled up
https://bugs.kde.org/show_bug.cgi?id=449233 fanzhuyi...@gmail.com changed: What|Removed |Added Latest Commit||https://invent.kde.org/util ||ities/konsole/-/merge_reque ||sts/589/diffs?commit_id=04d ||99f7cdcb4fb1973ecc58901c49a ||189494c492 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED CC||fanzhuyi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 465556] copy command output - shortcut
https://bugs.kde.org/show_bug.cgi?id=465556 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG CC||fanzhuyi...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- I don't think this is implemented. You could use xclip (https://github.com/astrand/xclip) under X and wl-clipboard (https://github.com/bugaevc/wl-clipboard) under wayland. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 466237] How to fix garbled text in konsole?
https://bugs.kde.org/show_bug.cgi?id=466237 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||fanzhuyi...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #2 from fanzhuyi...@gmail.com --- Hi, thank you for your bug report. The seems to be caused by the font you are using. Could you go to system settings-fonts and share what you see there? Also does this happen if you reset the fonts back to the defaults? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459373] Maximized XWayland apps leave pixel gaps when using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=459373 fanzhuyi...@gmail.com changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=464281 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 464281] 1px gaps in Konsole with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=464281 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com See Also||https://bugs.kde.org/show_b ||ug.cgi?id=459373 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 473185] after reordering tabs, Ctrl+tab consider the original next/previous tab order, not the current
https://bugs.kde.org/show_bug.cgi?id=473185 fanzhuyi...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Version|22.12.3 |24.01.80 Severity|normal |minor CC||fanzhuyi...@gmail.com Status|REPORTED|CONFIRMED --- Comment #1 from fanzhuyi...@gmail.com --- Can reproduce. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458233] In some games, controlling the camera with mouse, camera occasionally snaps into a different position when using Wayland
https://bugs.kde.org/show_bug.cgi?id=458233 --- Comment #45 from Yao Mitachi --- (In reply to Fun from comment #44) > I also have this problem, I've tested Final Fantasy XIV with lutris and > ge-wine-8.x, someone mentioned downgrading wine and that's what i did, i > tried with lutris-fshack-7.2 and the problem is gone. The Steam version might be different, I tried Proton-GE 7.2 and there was no difference. Also I can't get the vanilla launcher to work right now, Steam keeps saying there's a missing executable but ffxivboot.exe is right there. So I'm using XIVLauncher. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477570] When using a stylus the cursor is shown as a cross when hovering over native-Wayland Qt software
https://bugs.kde.org/show_bug.cgi?id=477570 --- Comment #4 from Raghavendra kamath --- The cursor doesn't change when hovering over the edge of the window so resize and other operations become troublesome. Also I think applications do provide cursors like firefox provides adwaita cursors. krita will provide the tool cursor I think But on the desktop the crosshair cursor as a default is not so much useful in my opinion. If the user needs they should be able to choose it I think. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478628] New: Plasmashell segfaults when trying to remove the Kicker (application menu) widget from the desktop
https://bugs.kde.org/show_bug.cgi?id=478628 Bug ID: 478628 Summary: Plasmashell segfaults when trying to remove the Kicker (application menu) widget from the desktop Classification: Plasma Product: plasmashell Version: 5.90.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: plasma-b...@kde.org Reporter: adam.m.fontenot+...@gmail.com Target Milestone: 1.0 Created attachment 164241 --> https://bugs.kde.org/attachment.cgi?id=164241=edit backtrace SUMMARY I added the application menu to my desktop itself (*not* a panel). Removing it crashes plasmashell. Trying to remove any other widget that I've tested (including Kickoff) does not crash plasmashell. For some reason plasmashell seems to crash "harder" than normal. Usually when I've seen a crash the desktop background doesn't disappear and the panel comes back after a couple seconds. In this case, the crash handler appears immediately but the background stays black for 5+ seconds. Backtrace attached. STEPS TO REPRODUCE 1. Add a kicker widget to your desktop. Should appear as a large button. Click it to make sure it works. (No issues for me.) 2. Right click the widget and select "remove application menu". SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 Kernel Version: 6.6.6-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFO If anyone wants to tell me how to remove a widget from the desktop manually that would be cool of you :-) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 462436] On Ctrl+Shift+V it often inserts "![[~200~" before and "~" after the inserted command
https://bugs.kde.org/show_bug.cgi?id=462436 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from fanzhuyi...@gmail.com --- Cannot reproduce. Could you verify if you are accidentally pressing just Ctrl V before the paste? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 473848] The cursor in vim running in konsole should not move if I accidentally touch the laptop's touchpad
https://bugs.kde.org/show_bug.cgi?id=473848 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #3 from fanzhuyi...@gmail.com --- This sounds like intended behavior -- some people may want to use the touchpad to scroll in vim, and you can disable it by unsetting TERM. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 473285] Final stop interpreted as part of URL
https://bugs.kde.org/show_bug.cgi?id=473285 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 471852] Desktop freezes on every login of Plasma 6 Wayland, (KDE Neon) using Nouveau Nvidia driver
https://bugs.kde.org/show_bug.cgi?id=471852 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||fanzhuyi...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #2 from fanzhuyi...@gmail.com --- Hi, thank you for your bug report! Can you still reproduce this issue with the latest neon unstable? There have been many updates to kwin, and this bug may have already been fixed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 478457] kioslave5 process causes high IOwait and hangs dolphin when browsing SMB share with hundreds of media files
https://bugs.kde.org/show_bug.cgi?id=478457 --- Comment #13 from Eddie J Carswell II --- (In reply to Eddie J Carswell II from comment #12) > I'll attach the stdout and stderr log (apparently the debug output ended up > in both places). During this time, I browsed a directory containing a few > dozen twitch stream captures. If there's anything in particular you want me > to try or a more rigorous test, let me know. Neglected to mention, with the smb:// protocol path, no thumbnails were generated (as expected), and when I browsed via the mount path after, kioslave5 happily generated thumbnails during this time (without putting undue pressure on the system, thanks to the wrapper). I do notice that the thumbnail generation is a bit slower, but still acceptable. -- You are receiving this mail because: You are watching all bug changes.
[Ocean] [Bug 477125] Sound notification for adjusting volume is quite loud compared to other audio sources
https://bugs.kde.org/show_bug.cgi?id=477125 --- Comment #4 from fanzhuyi...@gmail.com --- (In reply to Nate Graham from comment #3) > Yes, I can reproduce that. However the new one also feels a bit more harsh > in general, besides just the volume. Yeah I agree. Should the maintainer @raploz be pinged somehow? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 478524] Konsole is not allowing me to write scripts/programs that print the standard output to a file. I'm writing a program that includes
https://bugs.kde.org/show_bug.cgi?id=478524 fanzhuyi...@gmail.com changed: What|Removed |Added Severity|critical|normal CC||fanzhuyi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 478457] kioslave5 process causes high IOwait and hangs dolphin when browsing SMB share with hundreds of media files
https://bugs.kde.org/show_bug.cgi?id=478457 --- Comment #12 from Eddie J Carswell II --- (In reply to Harald Sitter from comment #8) > You've basically taken away the CPU weight from all KIO IO by doing this. Ah I see, I've tweaked it to only impact the thumbnail task: > $ cat /usr/libexec/kf5/kioslave5 > #!/bin/sh > [ $2 != "thumbnail" ] && exec $0.orig "$@" || exec nice -n 19 ionice -c 3 > $0.orig "$@" That should minimize any side effects of this hack. (In reply to Harald Sitter from comment #9) > After some research I'm even less convinced of this. From what I can tell > cifs is not subject to any IO scheduling what with being network based. IO > scheduling only comes into play when the request is routed into a block > device. cifs communication directly goes out into the network stack and > would be subject to the queuing discipline, which seems not interested in > IOPRIO. Perhaps this actually makes all perfect sense. We request a PNG to > create a preview, cifs is happy to oblige and issues (multiple concurrent?) > network requests, the remote is dreadfully slow and iowaiting on its disk, > translating to us iowaiting on the network sockets coming back with the > data. I can kind of replicate this by cgroup limiting smbd IO, but even with > very aggressive limits my system stays responsive. So, I'm rather thinking > there is a problem with your kernel/configuration. Hmm do you have any ideas on what would be impacting this? I'm running Fedora stock kernel 6.6.6-100.fc38.x86_64 and the scheduling settings are default, as far as I can tell. > Indeed, you are accessing it through the file:// protocol. That makes it > inherently local. I suppose I'll just have to deal with that behavior then, or probably set a file size limit acceptable for local and remote files. > I have the suspicion that this has to do with why things are misbehaving for > you to begin with. smb:// is performing close to the same transfer speed as > windows, if it doesn't for you that points at a problem elsewhere. Straight transfer speed was not the main issue. Aside from being unable to use the protocol path outside of KDE programs (e.g. terminal), there was also the slower response times enumerating directories, moving/renaming files, and sometimes dolphin would even go unresponsive for a few seconds. I tested a file transfer with the fstab mount and using smb:// and the throughput was similar. The transfer speed sending a ~1GB video file to the server via mount path was 60s (+20s for server IO to settle), and protocol path was 45s (+40s for server IO to settle). Pulling that file took 22s via mount path and 35s via protocol path (in both cases writing to an NVMe, waiting for all IO to settle between). To remove the disks from the equation, I mounted a ramdisk at both ends and did the test again. Download from the mount path was 20s, protocol path 30s. Upload to the mount path was 40s, protocol path was 50s. So closer numbers this time. It appears to me that in cases where both ends are nearly idle, they aren't that different, but when the server is under higher IO loads, the mount seems to behave better (more responsive, doesn't put the server under as high an IO load). > Perhaps let's get our ducks in a row > > What's the output of > $ tc qdisc show > qdisc noqueue 0: dev lo root refcnt 2 > qdisc noqueue 0: dev wlan0 root refcnt 2 > qdisc fq_codel 0: dev enp10s0u1u2 root refcnt 2 limit 10240p flows > 1024 > quantum 1514 target 5ms interval 100ms memory_limit 32Mb ecn > drop_batch 64 > qdisc noqueue 0: dev virbr0 root refcnt 2 > qdisc noqueue 8005: dev vnet4 root refcnt 2 > $ ls -lah "$(qtpaths --plugin-dir)/kf5/thumbcreator" > total 752K > drwxr-xr-x. 2 root root 4.0K Nov 28 06:55 . > drwxr-xr-x. 21 root root 4.0K Nov 13 06:50 .. > -rwxr-xr-x. 1 root root 44K Nov 13 19:00 audiothumbnail.so > -rwxr-xr-x. 1 root root 28K Nov 13 19:00 blenderthumbnail.so > -rwxr-xr-x. 1 root root 40K Nov 13 19:00 comicbookthumbnail.so > -rwxr-xr-x. 1 root root 20K Nov 13 19:00 cursorthumbnail.so > -rwxr-xr-x. 1 root root 32K Nov 13 19:00 djvuthumbnail.so > -rwxr-xr-x. 1 root root 44K Nov 13 19:00 ebookthumbnail.so > -rwxr-xr-x. 1 root root 32K Nov 13 19:00 exrthumbnail.so > -rwxr-xr-x. 1 root root 81K Nov 13 19:00 ffmpegthumbs.so > -rwxr-xr-x. 1 root root 32K Nov 24 19:00 fontthumbnail.so > -rwxr-xr-x. 1 root root 77K Nov 13 19:00 gsthumbnail.so > -rwxr-xr-x. 1 root root 24K Nov 13 19:00 imagethumbnail.so > -rwxr-xr-x. 1 root root 32K Nov 13 19:00 jpegthumbnail.so > -rwxr-xr-x. 1 root root 20K Nov 13 19:00 kraorathumbnail.so > -rwxr-xr-x. 1 root root 41K Nov 13 19:00 mltpreview.so > -rwxr-xr-x. 1 root root 20K Nov 13 19:00 mobithumbnail.so > -rwxr-xr-x. 1 root root 28K Nov 13 19:00 opendocumentthumbnail.so > -rwxr-xr-x. 1 root root 24K Nov 13 19:00 rawthumbnail.so > -rwxr-xr-x. 1 root root 20K Nov 13 19:00 svgthumbnail.so > -rwxr-xr-x. 1 root root 32K Nov 13 19:00 textthumbnail.so >
[frameworks-kio] [Bug 478457] kioslave5 process causes high IOwait and hangs dolphin when browsing SMB share with hundreds of media files
https://bugs.kde.org/show_bug.cgi?id=478457 --- Comment #11 from Eddie J Carswell II --- Created attachment 164240 --> https://bugs.kde.org/attachment.cgi?id=164240=edit debug log from dolphin -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 478457] kioslave5 process causes high IOwait and hangs dolphin when browsing SMB share with hundreds of media files
https://bugs.kde.org/show_bug.cgi?id=478457 --- Comment #10 from Eddie J Carswell II --- Created attachment 164239 --> https://bugs.kde.org/attachment.cgi?id=164239=edit debug log from dolphin -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478616] [NVIDIA] System hangs dead on sddm start: "kwin_core: Failed to open /dev/dri/card0 device (Did not receive a reply. ..."
https://bugs.kde.org/show_bug.cgi?id=478616 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com Summary|System hangs dead on sddm |[NVIDIA] System hangs dead |start: "kwin_core: Failed |on sddm start: "kwin_core: |to open /dev/dri/card0 |Failed to open |device (Did not receive a |/dev/dri/card0 device (Did |reply. ..."|not receive a reply. ..." -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 478162] Spectacle freezes after capturing a screenshot
https://bugs.kde.org/show_bug.cgi?id=478162 --- Comment #2 from Frederick Zhang --- > I'm unable to reproduce this with the latest unreleased version of Spectacle. > Is this still a problem with Spectacle 23.08 and 24.01.80 (24.02 beta)? I reported this issue using 23.08.3 as shown. Arch now is on 23.08.4 and the issue still persists. In terms of 24.01.80, I wasn't able to compile it as it requires KF 5.240.0. I'll probably have some time around Christmas to enable Arch's KDE-Unstable repo temporarily to give it a shot. PS: Is reply by email broken? I initially replied via email and got a 'Your message did not contain any text, as far as we could tell.' response. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 478008] Ark does not support deflate64
https://bugs.kde.org/show_bug.cgi?id=478008 2wxsy5823...@opayq.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from 2wxsy5823...@opayq.com --- *** This bug has been marked as a duplicate of bug 441608 *** -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 441608] Ark fails to unzip file with message about compression method not supported
https://bugs.kde.org/show_bug.cgi?id=441608 2wxsy5823...@opayq.com changed: What|Removed |Added CC||antti.s...@gmail.com --- Comment #7 from 2wxsy5823...@opayq.com --- *** Bug 478008 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland on VMs (VMWare, VirtualBox, ...)
https://bugs.kde.org/show_bug.cgi?id=427060 Bug Janitor Service changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 477891] Digest authentication failure
https://bugs.kde.org/show_bug.cgi?id=477891 --- Comment #5 from Dan Fandrich --- For the record, the Qt issue seems to be https://bugreports.qt.io/browse/QTBUG-98280 -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 478627] Kasts on Windows 11
https://bugs.kde.org/show_bug.cgi?id=478627 RKD changed: What|Removed |Added OS|Other |Microsoft Windows -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 478627] New: Kasts on Windows 11
https://bugs.kde.org/show_bug.cgi?id=478627 Bug ID: 478627 Summary: Kasts on Windows 11 Classification: Applications Product: kasts Version: 23.08.4 Platform: Other OS: Other Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: arkady...@gmail.com Target Milestone: --- Created attachment 164238 --> https://bugs.kde.org/attachment.cgi?id=164238=edit Event Viewer log I downloaded and installed Windows version of Kasts on Windows 11 with latest updates. Downloaded what was labeled as stable build (kasts-23.08.4-89-windows-cl-msvc2019-x86_64.exe) from https://binary-factory.kde.org/job/Kasts_Release_win64/. It worked for the first 5 minutes after launching; allowed me to connect to Nextcloud Sync and began syncing the podcasts; then it crashed, and since then when I launch it it stays minimized in the taskbar. Reinstalling multiple times did not help. There were two events logged related to the crash (attached). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478623] MetadataEdit contents are disabled.
https://bugs.kde.org/show_bug.cgi?id=478623 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Metadata editor contents|MetadataEdit contents are |are disabled|disabled. Component|Metadata-Iptc |Plugin-Generic-MetadataEdit -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478623] Metadata editor contents are disabled
https://bugs.kde.org/show_bug.cgi?id=478623 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Summary|Metadata (CTRL-ALT-M) |Metadata editor contents |disabled|are disabled -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland on VMs (VMWare, VirtualBox, ...)
https://bugs.kde.org/show_bug.cgi?id=427060 guimarcalsi...@gmail.com changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #50 from guimarcalsi...@gmail.com --- (In reply to guimarcalsilva from comment #49) > *** Bug 478614 has been marked as a duplicate of this bug. *** There's a brand new duplicate of this bug report on Plasma 6. I'll reopen it because it seems it might not be fixed for everyone. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland on VMs (VMWare, VirtualBox, ...)
https://bugs.kde.org/show_bug.cgi?id=427060 guimarcalsi...@gmail.com changed: What|Removed |Added CC||kritom...@gmail.com --- Comment #49 from guimarcalsi...@gmail.com --- *** Bug 478614 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478614] Cursor is rendered at the wrong position on wayland (QEMU)
https://bugs.kde.org/show_bug.cgi?id=478614 guimarcalsi...@gmail.com changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from guimarcalsi...@gmail.com --- *** This bug has been marked as a duplicate of bug 427060 *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 477891] Digest authentication failure
https://bugs.kde.org/show_bug.cgi?id=477891 Dan Fandrich changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #4 from Dan Fandrich --- I traced the Akregator code and found that it seems to use the QtNetwork classes to perform HTTP requests. I created a standalone Qt application to perform a similar request and discovered that it truncates the response field to 128 bits as well. So, it seems to be a problem in Qt itself (I tried both 5.15.2 and 5.15.7). -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 429408] kde-open5 changes case of argument
https://bugs.kde.org/show_bug.cgi?id=429408
André Werlang changed:
What|Removed |Added
CC||bepp...@gmail.com
--- Comment #19 from André Werlang ---
(In reply to Connor Schunk from comment #6)
> In QUrl (https://code.woboq.org/qt5/qtbase/src/corelib/io/qurl.cpp.html), I
> notice "nameprepping" and RFCs related to normalization are mentioned a few
> times, e.g.
> > Note that the case folding rules in \l{RFC 3491}{Nameprep}, which QUrl
> > conforms to, require host names to always be converted to lower case,
> > regardless of the Qt::FormattingOptions used
Except RFC 3491 doesn't make any mention to "case folding". RFC 3490 mentions
> 4) Whenever two labels are compared, they MUST be considered to match
> if and only if they are equivalent, that is, their ASCII forms
> (obtained by applying ToASCII) match using a case-insensitive
> ASCII comparison. Whenever two names are compared, they MUST be
> considered to match if and only if their corresponding labels
> match, regardless of whether the names use the same forms of label
> separators.
I don't think this applies to QUrl as no comparison between labels takes place.
(In reply to Oded Arbel from comment #10)
> I believe the correct RFC for QURL implementations - in this case - is RFC
> 3986: URI Generic Syntax, where section 3.2.2 says: "The host subcomponent
> is case-insensitive". Granted that a reading of the spec to mean "fold
> everything to lowercase" is reaching a bit, but as per RFC 1122, p1.2.2 -
> receivers should accept lowercased host names.
It's not reaching a bit, RFC recommends lowercasing domain names in section
3.2.2:
> Although host is case-insensitive, producers and normalizers should use
> lowercase for registered names and hexadecimal addresses for the sake of
> uniformity, while only using uppercase letters for percent-encodings.
Keyword here is SHOULD. QUrl is not _required_ to do so.
TLDR; Thunderbird should avoid the authority component and use a single "/"
character or none at all after the ":". kde-open5 probably doesn't need to
normalize anything just to figure out the correct scheme handler.
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 477127] review tool settings get lost after reload
https://bugs.kde.org/show_bug.cgi?id=477127 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 469400] high consumption of RAM and CPU
https://bugs.kde.org/show_bug.cgi?id=469400 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 474811] kscreenlocker often breaks when waking up and unlocking after screen arrangement changed while asleep
https://bugs.kde.org/show_bug.cgi?id=474811 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #8 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 477947] KDE System Monitor crashes every time I select another category within it.
https://bugs.kde.org/show_bug.cgi?id=477947 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477177] Strange scaling behavior with xwayland scaling settings on mixed DPI setups
https://bugs.kde.org/show_bug.cgi?id=477177 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471364] Sharing window with OBS causes periodic desktop stuttering
https://bugs.kde.org/show_bug.cgi?id=471364 --- Comment #6 from deadmeu --- (In reply to toby from comment #5) > deadmeu, is one of you CPU cores pinned at 100% or close to it when you > screen share? As I believe this issue is related to > https://bugs.kde.org/show_bug.cgi?id=469777 as I get 100% on one core when > screen sharing on Plasma, I don't experience this on other Wayland > compositors. Thanks for commenting toby. Yes, when any window/screen sharing occurs, regardless of whether it's by the portal sharing selection dialog or a currently active source, I can see a single thread being pinned at max utilisation. I can see the kwin_wayland process maxing out at 4% utilisation which, on my CPU with 24 threads, lines up with the almost 100% utilisation I'm seeing on a single thread. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469777] KWin since 5.27.5 uses 1 CPU core at 100% whenever something is using PipeWire to capture the screen
https://bugs.kde.org/show_bug.cgi?id=469777 deadmeu changed: What|Removed |Added CC||dead...@dmu.gg -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 451018] Slack users on KDE Plasma unable to open workspace in desktop app via Chromium based browsers
https://bugs.kde.org/show_bug.cgi?id=451018 André Werlang changed: What|Removed |Added CC||bepp...@gmail.com --- Comment #7 from André Werlang --- A simple experiment demonstrates how xdg-open works: [code] $ xdg-mime query default x-scheme-handler/mock mock.desktop $ cat .local/share/applications/mock.desktop [Desktop Entry] Name=Mock URI Handler Exec=echo %u >> ~/mockfile Type=Application MimeType=x-scheme-handler/mock $ xdg-open mock://SLACKISBUGGY $ xdg-open mock:/SLACKISBUGGY $ xdg-open mock:SLACKISBUGGY $ cat mockfile mock://slackisbuggy mock:/SLACKISBUGGY mock:SLACKISBUGGY [/code] RFC 3986 defines whats between "//" and "/" as an authority (*The host subcomponent is case-insensitive. The presence of a host subcomponent within a URI does not imply that the scheme requires access to the given host on the Internet.* and *Although host is case-insensitive, producers and normalizers should use lowercase for registered names and hexadecimal addresses for the sake of uniformity, while only using uppercase letters for percent-encodings.*). As such, Slack, as a consumer of an URI needs to handle the host part of the authority component case-insensitive. Or opt into other URI forms that don't rely on authority component e.g. "slack:" or "slack:/". Also, notice the verbiage used (normalizers SHOULD use lowercase). If QUrl did not lowercase hostnames, that wouldn't make QUrl less conformant to the RFC as the final consumer should be guaranteeing that. TLDR; Slack is clearly non-complaint to URI RFC, QUrl doesn't need to be so strict and is it even necessary to rely on QUrl to figure out the scheme handler? -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 438996] Effect goes through the scroll bar when I hover over a color scheme in hamburger menu of Elisa
https://bugs.kde.org/show_bug.cgi?id=438996 --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/qqc2-desktop-style/-/merge_requests/343 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478625] Plasma crashed when I disabled the notification widget in the system tray
https://bugs.kde.org/show_bug.cgi?id=478625 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 478626] Wrong thumbnail picture in project content list when copying title tracks
https://bugs.kde.org/show_bug.cgi?id=478626 --- Comment #1 from Thomas Murach --- Apologies, I hit "enter" to upload attachment, but then the report was submitted already :-/ STEPS TO REPRODUCE 1. Create a title track with just a little text in the bottom left corner, see attachment picture, track 1. Thumbnail picture seems correct. 2. Copy that title track, rename it, add text in the top left corner, see thumbnail picture, track 2. Thumbnail picture seems correct. 3. Copy track _1_ once more, rename it, do _not_ add text in the top left corner; see track 3. The thumbnail should resemble the thumbnail of track 1, not the thumbnail of track 2. OBSERVED RESULT Thumbnail of track 3 resembles thumbnail of track 2. EXPECTED RESULT Thumbnail should resemble thumbnail of track 1. SOFTWARE/OS VERSIONS Windows: macOS: Linux: OpenSuSE Leap 15.5, Kernel 5.14.21 (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 478626] New: Wrong thumbnail picture in project content list when copying title tracks
https://bugs.kde.org/show_bug.cgi?id=478626 Bug ID: 478626 Summary: Wrong thumbnail picture in project content list when copying title tracks Classification: Applications Product: kdenlive Version: 22.12.3 Platform: openSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: asiasuppenes...@gmx.de Target Milestone: --- Created attachment 164237 --> https://bugs.kde.org/attachment.cgi?id=164237=edit Problem with preview of clip 3 SUMMARY In my workflow I copy title tracks often, rename the copies and change contents slightly. In the project content list (German: Projektinhalt) view the thumbnail picture of these copies is sometimes wrong, as described below. To me this issue is reproducible and has been there for a long time. Last but not least: Thanks so much for providing and maintaining this fantastic piece of software!!! It is truly amazing. 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.
[kdenlive] [Bug 476471] My GPU codec is not supported
https://bugs.kde.org/show_bug.cgi?id=476471 2wxsy5823...@opayq.com changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 476471] My GPU codec is not supported
https://bugs.kde.org/show_bug.cgi?id=476471 2wxsy5823...@opayq.com changed: What|Removed |Added Attachment #163490|0 |1 is obsolete|| --- Comment #10 from 2wxsy5823...@opayq.com --- Created attachment 164236 --> https://bugs.kde.org/attachment.cgi?id=164236=edit vainfo output (Extracted from Attachment 163490) -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 463696] System Tray Integration
https://bugs.kde.org/show_bug.cgi?id=463696 Joshua Goins changed: What|Removed |Added CC||k...@mva.name --- Comment #9 from Joshua Goins --- *** Bug 478574 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 478574] [Feature Request] minimize to tray function
https://bugs.kde.org/show_bug.cgi?id=478574 Joshua Goins changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Joshua Goins --- *** This bug has been marked as a duplicate of bug 463696 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478421] The panel disappeared after entering full screen mode in GNOME Boxes VMs
https://bugs.kde.org/show_bug.cgi?id=478421 --- Comment #13 from Matt Fagnani --- I built kwin 5.90.0 with the patch at https://invent.kde.org/plasma/kwin/-/merge_requests/4799 added. I updated the kwin rpms in GNOME Boxes VM using Fedora-KDE-Live-x86_64-Rawhide-20231216.n.0.iso as in Comment 10. The guest's panel was still shown in full screen mode after doing that, and Plasma covered the full screen without the black bands at the top and bottom that I reported. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478625] Plasma crashed when I disabled the notification widget in the system tray
https://bugs.kde.org/show_bug.cgi?id=478625 Fushan Wen changed: What|Removed |Added Component|generic-crash |System Tray CC||mate...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478625] Plasma crashed when I disabled the notification widget in the system tray
https://bugs.kde.org/show_bug.cgi?id=478625 --- Comment #1 from Fushan Wen --- Created attachment 164235 --> https://bugs.kde.org/attachment.cgi?id=164235=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478625] New: Plasma crashed when I disabled the notification widget in the system tray
https://bugs.kde.org/show_bug.cgi?id=478625 Bug ID: 478625 Summary: Plasma crashed when I disabled the notification widget in the system tray Classification: Plasma Product: plasmashell Version: master Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: qydwhotm...@gmail.com Target Milestone: 1.0 Application: plasmashell (5.90.90) Qt Version: 6.6.1 Frameworks Version: 5.247.0 Operating System: Linux 6.6.3-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.90.90 [CoredumpBackend] -- Information about the crash: 1. Open the systray config dialog 2. Disable the notification widget in Items 3. Click OK The crash can be reproduced every time. -- Backtrace (Reduced): #4 0x7f75890762bb in QQmlContextData::get(QQmlContext*) (context=, context=) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/build/include/QtQml/6.6.1/QtQml/private/../../../../../../src/qml/qml/qqmlcontextdata_p.h:64 #5 QQuickListViewPrivate::setSectionHelper(QQmlContext*, QQuickItem*, QString const&) (context=0x0, sectionItem=0x563f1d991a20, section=...) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/quick/items/qquicklistview.cpp:2006 #6 0x7f7589083f1e in QQuickListViewPrivate::updateInlineSection(FxListItemSG*) (listItem=0x563f18cf6550, this=0x563f1dfb0910) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/quick/items/qquicklistview_p.h:50 #7 QQuickListViewPrivate::updateSections() (this=0x563f1dfb0910) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/quick/items/qquicklistview.cpp:1313 #8 0x7f7589069ed5 in QQuickItemViewPrivate::applyModelChanges(QQuickItemViewPrivate::ChangeResult*, QQuickItemViewPrivate::ChangeResult*) (totalRemovalResult=0x7ffcd7bc2da0, totalInsertionResult=0x7ffcd7bc2dd0, this=) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/quick/items/qquickitemview.cpp:2137 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471364] Sharing window with OBS causes periodic desktop stuttering
https://bugs.kde.org/show_bug.cgi?id=471364 toby changed: What|Removed |Added CC||to...@sent.com --- Comment #5 from toby --- deadmeu, is one of you CPU cores pinned at 100% or close to it when you screen share? As I believe this issue is related to https://bugs.kde.org/show_bug.cgi?id=469777 as I get 100% on one core when screen sharing on Plasma, I don't experience this on other Wayland compositors. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 478624] Valgrind incompatibility with binutils-2.42 on x86 with new nop patterns (unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26)
https://bugs.kde.org/show_bug.cgi?id=478624 Sam James changed: What|Removed |Added See Also||http://bugs.debian.org/1057 ||693 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 478624] Valgrind incompatibility with binutils-2.42 on x86 with new nop patterns (unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26)
https://bugs.kde.org/show_bug.cgi?id=478624 Sam James changed: What|Removed |Added Summary|Valgrind incompatibility|Valgrind incompatibility |with binutils-2.42 on x86 |with binutils-2.42 on x86 ||with new nop patterns ||(unhandled instruction ||bytes: 0x2E 0x8D 0xB4 0x26) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 478624] Valgrind incompatibility with binutils-2.42 on x86
https://bugs.kde.org/show_bug.cgi?id=478624 --- Comment #1 from Sam James --- For a testcase we probably should just have a simple assembly/byte sequence of all the "nops" used in https://sourceware.org/cgit/binutils-gdb/tree/gas/config/tc-i386.c#n1256 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 478624] New: Valgrind incompatibility with binutils-2.42 on x86
https://bugs.kde.org/show_bug.cgi?id=478624 Bug ID: 478624 Summary: Valgrind incompatibility with binutils-2.42 on x86 Classification: Developer tools Product: valgrind Version: 3.22 GIT Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: s...@gentoo.org CC: aurel...@aurel32.net, debfx-...@fobos.de, s...@extundo.com Target Milestone: --- [Forgive me, as I've not yet hit this myself, but reporting it based on the Debian bug after discussing it with mjw.] The upcoming binutils-2.42 release [0] seems to be incompatible with Valgrind on x86 after a commit landed [1] to emit additional nop patterns which Valgrind doesn't yet recognise. This was originally reported in Debian [2] (CC'd some of the participants whose emails I could find on here). In the linked Debian bug, Simon gives a simple reproducer w/ output: ``` 117s vex x86->IR: unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26 117s ==5711== valgrind: Unrecognised instruction at address 0x4d285c8. 117s ==5711==at 0x4D285C8: ??? (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711==by 0x4D27893: ??? (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711==by 0x4D27B0E: ??? (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711==by 0x4D27069: gss_import_name (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711==by 0x486BA0F: ??? (in /usr/lib/i386-linux-gnu/libgsasl.so.18.0.0) 117s ==5711==by 0x485757C: gsasl_step (in /usr/lib/i386-linux-gnu/libgsasl.so.18.0.0) 117s ==5711==by 0x4857623: gsasl_step64 (in /usr/lib/i386-linux-gnu/libgsasl.so.18.0.0) 117s ==5711==by 0x10B387: ??? (in /usr/bin/gsasl) 117s ==5711==by 0x4ADE7C4: (below main) (libc_start_call_main.h:58) 117s ==5711== Your program just tried to execute an instruction that Valgrind 117s ==5711== did not recognise. There are two possible reasons for this. 117s ==5711== 1. Your program has a bug and erroneously jumped to a non-code 117s ==5711==location. If you are running Memcheck and you just saw a 117s ==5711==warning about a bad jump, it's probably your program's fault. 117s ==5711== 2. The instruction is legitimate but Valgrind doesn't handle it, 117s ==5711==i.e. it's Valgrind's fault. If you think this is the case or 117s ==5711==you are not sure, please let us know and we'll try to fix it. 117s ==5711== Either way, Valgrind will now raise a SIGILL signal which will 117s ==5711== probably kill your program. 117s ==5711== 117s ==5711== Process terminating with default action of signal 4 (SIGILL) 117s ==5711== Illegal opcode at address 0x4D285C8 117s ==5711==at 0x4D285C8: ??? (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711==by 0x4D27893: ??? (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711==by 0x4D27B0E: ??? (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711==by 0x4D27069: gss_import_name (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711==by 0x486BA0F: ??? (in /usr/lib/i386-linux-gnu/libgsasl.so.18.0.0) 117s ==5711==by 0x485757C: gsasl_step (in /usr/lib/i386-linux-gnu/libgsasl.so.18.0.0) 117s ==5711==by 0x4857623: gsasl_step64 (in /usr/lib/i386-linux-gnu/libgsasl.so.18.0.0) 117s ==5711==by 0x10B387: ??? (in /usr/bin/gsasl) 117s ==5711==by 0x4ADE7C4: (below main) (libc_start_call_main.h:58) ``` with steps to reproduce: ``` podman run --arch 386 -it --rm debian:unstable-slim apt update apt install valgrind gsasl apt dist-upgrade valgrind --error-exitcode=1 /usr/bin/gsasl -m GSSAPI -d --no-starttls --imap no-such-domain.example 143 ``` [0] https://inbox.sourceware.org/binutils/0f118fd8-5630-4742-a353-3309e6285...@redhat.com/T/#u [1] https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=ad9f3230565ca40bfa1d9a3106272cb125f2 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057693 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478623] New: Metadata (CTRL-ALT-M) disabled
https://bugs.kde.org/show_bug.cgi?id=478623 Bug ID: 478623 Summary: Metadata (CTRL-ALT-M) disabled Classification: Applications Product: digikam Version: 8.2.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Metadata-Iptc Assignee: digikam-bugs-n...@kde.org Reporter: j...@acm.org 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 *** STEPS TO REPRODUCE 1. Select one or more JPG, MPG, or TIFF files 2. Item->Edit Metadata OBSERVED RESULT Everything is disabled. EXPECTED RESULT To be able to edit medatada. SOFTWARE/OS VERSIONS Windows: Windows 11. 21H2. 22000.2538 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Build date: 9/14/2023 5:03 AM (target: RelWithDebInfo) Revision: 570beca211ea0a294243aa46c06f3d3cb8dbf7e5 Branch: master -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478620] Mouse navigation with numpad doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=478620 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 312843] Konsole does not use transparency when background image set
https://bugs.kde.org/show_bug.cgi?id=312843 --- Comment #17 from Kurt Hindenburg --- Git commit 8939910b61f2b9fd035a9bf9292dcdbda7ef17eb by Kurt Hindenburg, on behalf of Luis Javier Merino Morán. Committed on 16/12/2023 at 18:25. Pushed by hindenburg into branch 'master'. Show wallpaper on non-translucent top-levels For reasons, showing the background image (wallpaper) has become dependant on the ability of the top-level window to be translucent. This does not need to be so. Since 5bac30ab3, to draw the wallpaper, first a background color is used to fill the dirty region, and then the wallpaper is drawn, and the opacity of the background color and the wallpaper are separate, so we can fill with a totally opaque background color, and then draw a maybe translucent wallpaper over that, and no glitches should appear. Related: bug 477800, bug 157882 M +2-2src/terminalDisplay/TerminalPainter.cpp https://invent.kde.org/utilities/konsole/-/commit/8939910b61f2b9fd035a9bf9292dcdbda7ef17eb -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 477800] konsole does not use background images if opacity is not supported
https://bugs.kde.org/show_bug.cgi?id=477800 Kurt Hindenburg changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/util ||ities/konsole/-/commit/8939 ||910b61f2b9fd035a9bf9292dcdb ||da7ef17eb Resolution|--- |FIXED --- Comment #2 from Kurt Hindenburg --- Git commit 8939910b61f2b9fd035a9bf9292dcdbda7ef17eb by Kurt Hindenburg, on behalf of Luis Javier Merino Morán. Committed on 16/12/2023 at 18:25. Pushed by hindenburg into branch 'master'. Show wallpaper on non-translucent top-levels For reasons, showing the background image (wallpaper) has become dependant on the ability of the top-level window to be translucent. This does not need to be so. Since 5bac30ab3, to draw the wallpaper, first a background color is used to fill the dirty region, and then the wallpaper is drawn, and the opacity of the background color and the wallpaper are separate, so we can fill with a totally opaque background color, and then draw a maybe translucent wallpaper over that, and no glitches should appear. Related: bug 312843, bug 157882 M +2-2src/terminalDisplay/TerminalPainter.cpp https://invent.kde.org/utilities/konsole/-/commit/8939910b61f2b9fd035a9bf9292dcdbda7ef17eb -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 157882] Set background image in konsole 2.0 (kde4)
https://bugs.kde.org/show_bug.cgi?id=157882 --- Comment #30 from Kurt Hindenburg --- Git commit 8939910b61f2b9fd035a9bf9292dcdbda7ef17eb by Kurt Hindenburg, on behalf of Luis Javier Merino Morán. Committed on 16/12/2023 at 18:25. Pushed by hindenburg into branch 'master'. Show wallpaper on non-translucent top-levels For reasons, showing the background image (wallpaper) has become dependant on the ability of the top-level window to be translucent. This does not need to be so. Since 5bac30ab3, to draw the wallpaper, first a background color is used to fill the dirty region, and then the wallpaper is drawn, and the opacity of the background color and the wallpaper are separate, so we can fill with a totally opaque background color, and then draw a maybe translucent wallpaper over that, and no glitches should appear. Related: bug 477800, bug 312843 M +2-2src/terminalDisplay/TerminalPainter.cpp https://invent.kde.org/utilities/konsole/-/commit/8939910b61f2b9fd035a9bf9292dcdbda7ef17eb -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478620] Mouse navigation with numpad doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=478620 Nicolas Fella changed: What|Removed |Added Keywords|qt6 | --- Comment #2 from Nicolas Fella --- bad bot -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478620] Mouse navigation with numpad doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=478620 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478622] New: Provide an option to turn off stylus indicator on screen
https://bugs.kde.org/show_bug.cgi?id=478622 Bug ID: 478622 Summary: Provide an option to turn off stylus indicator on screen Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_tablet Assignee: plasma-b...@kde.org Reporter: anditosan1...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY *** I wanted to suggest having a feature in the tablet KCM to turn off the graphic that appears to indicate the stylus position on the screen. I think sometimes, this graphic can get in the way. I think sometimes users want to work through touch and there are very few people who don't touch the screen with a stylus before they interact with the screen. The graphic helps appears before users touch the screen and I don't see a lot of value there. However, I know it's good for a few people so that's why I wanted to suggest having this as an option and not the default. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 475412] akonadi_mail_dispatcher_agent closed unexcpectedly
https://bugs.kde.org/show_bug.cgi?id=475412 --- Comment #8 from tprotopope...@gmail.com --- My apologies for the multiple postings. The automatic bug submission did not confirm anything was submitted (just the spiny wheel), after trying three times and (apparently) failing I logged in to submit it and found it had already. I suppose that's a bug in dr Konqi... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478620] Mouse navigation with numpad doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=478620 Nicolas Fella changed: What|Removed |Added Keywords|qt6 | -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 470797] Kdenlive monitor full-screen stuttering
https://bugs.kde.org/show_bug.cgi?id=470797 Bohdan changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Bohdan --- Fixed in newest kdenlive/gnome/mutter/xwayland, not sure, but now it's okay. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478620] Mouse navigation with numpad doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=478620 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 475412] akonadi_mail_dispatcher_agent closed unexcpectedly
https://bugs.kde.org/show_bug.cgi?id=475412 --- Comment #7 from tprotopope...@gmail.com --- Created attachment 164234 --> https://bugs.kde.org/attachment.cgi?id=164234=edit New crash information added by DrKonqi akonadi_maildispatcher_agent (5.22.3 (22.12.3)) using Qt 5.15.8 The maildispatcher-agent crashes whenever I try to send an email. This happens every time since I switched from the opensuse 15.5 standard packages to the KDE repos. -- Backtrace (Reduced): #4 MailTransport::TransportAttribute::transportId() const (this=this@entry=0x0) at /usr/src/debug/kmailtransport-22.12.3-bp155.1.5.x86_64/src/kmailtransportakonadi/transportattribute.cpp:49 #5 0x560947f745af in SendJob::doTransport() (this=0x560948a66690) at /usr/src/debug/kdepim-runtime-22.12.3-bp155.1.7.x86_64/agents/maildispatcher/sendjob.cpp:56 #6 0x7fbdc357a50b in QObject::event(QEvent*) (this=0x560948a66690, e=0x560948a67f20) at kernel/qobject.cpp:1347 #7 0x7fbdc39dd53c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x560948862a80, receiver=receiver@entry=0x560948a66690, e=e@entry=0x560948a67f20) at kernel/qapplication.cpp:3640 #8 0x7fbdc39e42ff in QApplication::notify(QObject*, QEvent*) (this=, receiver=0x560948a66690, e=0x560948a67f20) at kernel/qapplication.cpp:3164 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476579] Crashed upon login
https://bugs.kde.org/show_bug.cgi?id=476579 cheery.idea2...@fastmail.com changed: What|Removed |Added CC||cheery.idea2...@fastmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478621] New: Plamsa crash upon screen resume
https://bugs.kde.org/show_bug.cgi?id=478621 Bug ID: 478621 Summary: Plamsa crash upon screen resume Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: cheery.idea2...@fastmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.10) Qt Version: 5.15.11 Frameworks Version: 5.112.0 Operating System: Linux 6.6.6-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.10 [CoredumpBackend] -- Information about the crash: Left computer running for a while, the screen blanked after the set time (via the power settings), and when I woke the screen back up, I saw that plasma had crashed and the error report window was up. Everything seems to be working fine, except some windows were minimized. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 2258 (plasmashell) UID: 1000 (gabe) GID: 1000 (gabe) Signal: 11 (SEGV) Timestamp: Sat 2023-12-16 17:17:38 EST (1min 1s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (gabe) Boot ID: af320fc21d22464797999634a961eddb Machine ID: 11150b9ebfd44d8a81a411c66e9200ea Hostname: melinoe.local Storage: /var/lib/systemd/coredump/core.plasmashell.1000.af320fc21d22464797999634a961eddb.2258.170276505800.zst (present) Size on Disk: 57.7M Message: Process 2258 (plasmashell) of user 1000 dumped core. Stack trace of thread 2258: #0 0x7f52128972a8 pthread_sigmask@GLIBC_2.2.5 (libc.so.6 + 0x972a8) #1 0x7f521283f3ad sigprocmask (libc.so.6 + 0x3f3ad) #2 0x7f52154878db _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x58db) #3 0x7f5215489d93 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x7d93) #4 0x7f521283f190 __restore_rt (libc.so.6 + 0x3f190) #5 0x7f5214e78832 _ZN17QQuickItemPrivate14addToDirtyListEv (libQt5Quick.so.5 + 0x278832) #6 0x7f5214e7d07e _ZN17QQuickItemPrivate5dirtyENS_9DirtyTypeE (libQt5Quick.so.5 + 0x27d07e) #7 0x7f5214e7d653 _ZN10QQuickItem8setWidthEd (libQt5Quick.so.5 + 0x27d653) #8 0x7f5214905b43 n/a (libQt5Qml.so.5 + 0x305b43) #9 0x7f5214906a3e n/a (libQt5Qml.so.5 + 0x306a3e) #10 0x7f5214904454 _ZN11QQmlBinding6updateE6QFlagsIN16QQmlPropertyData9WriteFlagEE (libQt5Qml.so.5 + 0x304454) #11 0x7f52148e1405 _ZN12QQmlNotifier10emitNotifyEP20QQmlNotifierEndpointPPv (libQt5Qml.so.5 + 0x2e1405) #12 0x7f5213324d2d n/a (libQt5Core.so.5 + 0x324d2d) #13 0x7f521488960c _ZN17QQmlVMEMetaObject8metaCallEP7QObjectN11QMetaObject4CallEiPPv (libQt5Qml.so.5 + 0x28960c) #14 0x7f521489ce81 _ZN19QQmlPropertyPrivate5writeEP7QObjectRK16QQmlPropertyDataRK8QVariantP15QQmlContextData6QFlagsINS2_9WriteFlagEE (libQt5Qml.so.5 + 0x29ce81) #15 0x7f5214903d9c _ZN11QQmlBinding9slowWriteERK16QQmlPropertyDataS2_RKN3QV45ValueEb6QFlagsINS0_9WriteFlagEE (libQt5Qml.so.5 + 0x303d9c) #16 0x7f52149051e0 n/a (libQt5Qml.so.5 + 0x3051e0) #17 0x7f5214906a3e n/a (libQt5Qml.so.5 + 0x306a3e) #18 0x7f5214904454 _ZN11QQmlBinding6updateE6QFlagsIN16QQmlPropertyData9WriteFlagEE (libQt5Qml.so.5 + 0x304454) #19 0x7f52148e1405 _ZN12QQmlNotifier10emitNotifyEP20QQmlNotifierEndpointPPv (libQt5Qml.so.5 + 0x2e1405) #20 0x7f5213324d2d n/a (libQt5Core.so.5 + 0x324d2d) #21 0x7f5214e8022b _ZN10QQuickItem15geometryChangedERK6QRectFS2_ (libQt5Quick.so.5 + 0x28022b) #22 0x7f5214e7d828 _ZN10QQuickItem7setSizeERK6QSizeF (libQt5Quick.so.5 + 0x27d828) #23 0x7f5214e6913e n/a (libQt5Quick.so.5 + 0x26913e) #24 0x7f5214e801b3 _ZN10QQuickItem15geometryChangedERK6QRectFS2_ (libQt5Quick.so.5 + 0x2801b3) #25 0x7f5214e7d828 _ZN10QQuickItem7setSizeERK6QSizeF (libQt5Quick.so.5 + 0x27d828) #26 0x7f5214e6913e n/a (libQt5Quick.so.5 + 0x26913e) #27 0x7f5214e801b3 _ZN10QQuickItem15geometryChangedERK6QRectFS2_ (libQt5Quick.so.5 + 0x2801b3)
[kdeconnect] [Bug 478605] pairing with my Android phone does not succeed. Firewall is not a problem, since a TCP port is open. Tried pairing by IP address without success.
https://bugs.kde.org/show_bug.cgi?id=478605 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Severity|critical|normal -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 478607] As configurações de ocultação inteligente pararam de funcionar, e temos que ficar reinstalando o aplicativo. Por favor corrijam isso.
https://bugs.kde.org/show_bug.cgi?id=478607 Nicolas Fella changed: What|Removed |Added Severity|critical|normal CC||nicolas.fe...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478620] Mouse navigation with numpad doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=478620 Nicolas Fella changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Keywords|qt6 | CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- See https://invent.kde.org/plasma/kwin/-/merge_requests/3362 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 478417] System Monitor doesn't display any CPU usage for most applications
https://bugs.kde.org/show_bug.cgi?id=478417 --- Comment #6 from ly...@bune.city --- (In reply to Arjen Hiemstra from comment #2) > It's not intentional, but it seems something is messed up with your CGroup > hierarchy. Can you share the output of `systemd-cgls`? I've attached the output of the command here: https://bugs.kde.org/attachment.cgi?id=164232 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 478417] System Monitor doesn't display any CPU usage for most applications
https://bugs.kde.org/show_bug.cgi?id=478417 --- Comment #5 from ly...@bune.city --- (In reply to fanzhuyifan from comment #1) > I think that is intended behavior. The applications having the blank entries > just mean they basically have no CPU usage. Do you see a significant > difference between the numbers reported by system monitor and htop? I do, yes. I've attached a screenshot comparing the two. See this attachment: https://bugs.kde.org/attachment.cgi?id=164233 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 478417] System Monitor doesn't display any CPU usage for most applications
https://bugs.kde.org/show_bug.cgi?id=478417 --- Comment #4 from ly...@bune.city --- Created attachment 164233 --> https://bugs.kde.org/attachment.cgi?id=164233=edit htop output vs plasma system monitor -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 478417] System Monitor doesn't display any CPU usage for most applications
https://bugs.kde.org/show_bug.cgi?id=478417 --- Comment #3 from ly...@bune.city --- Created attachment 164232 --> https://bugs.kde.org/attachment.cgi?id=164232=edit systemd-cgls output -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478084] Digikam 8.x language issue on macOS
https://bugs.kde.org/show_bug.cgi?id=478084 --- Comment #11 from Maik Qualmann --- Git commit 450573361ed3b377eec06d11aef72e61d8ebc561 by Maik Qualmann. Committed on 16/12/2023 at 22:44. Pushed by mqualmann into branch 'master'. try to fix the loading of the set language Related: bug 478550 M +12 -4core/app/utils/digikam_globals_bundles.cpp https://invent.kde.org/graphics/digikam/-/commit/450573361ed3b377eec06d11aef72e61d8ebc561 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478550] localization - main language settings are not used (can't change from German to US-English)
https://bugs.kde.org/show_bug.cgi?id=478550 --- Comment #5 from Maik Qualmann --- Git commit 450573361ed3b377eec06d11aef72e61d8ebc561 by Maik Qualmann. Committed on 16/12/2023 at 22:44. Pushed by mqualmann into branch 'master'. try to fix the loading of the set language Related: bug 478084 M +12 -4core/app/utils/digikam_globals_bundles.cpp https://invent.kde.org/graphics/digikam/-/commit/450573361ed3b377eec06d11aef72e61d8ebc561 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478620] New: Mouse navigation with numpad doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=478620 Bug ID: 478620 Summary: Mouse navigation with numpad doesn't work under Wayland Classification: Applications Product: systemsettings Version: 5.90.0 Platform: Other OS: Linux Status: REPORTED Keywords: qt6, wayland Severity: normal Priority: NOR Component: kcm_accessibility Assignee: plasma-b...@kde.org Reporter: jan.rathm...@gmx.de Target Milestone: --- SUMMARY Using the numpad to move the mouse cursor currently doesn't work in the Wayland session. STEPS TO REPRODUCE 1. Start P6 Wayland session 2. Go to Systemsettings -> Accessibility -> Mouse Navigation 3. Check "Use number pad to move cursor" 4. Try to move the cursor with the numpad OBSERVED RESULT Nothing happens when pressing numpad keys to move the cursor. EXPECTED RESULT Cursor should move when pressing numpad keys. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.90 KDE Frameworks Version: 5.247 Qt Version: 6.6.1 ADDITIONAL INFORMATION Reproduced with Neon Unstable installation and openSuse Krypton live image. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478617] kwin scripting reports needing ';' or ',' in lines of good javascript code seen in the declaration 'async' as well as the 'await' operator.
https://bugs.kde.org/show_bug.cgi?id=478617 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- QJSEngine, which KWin uses for the script evaluation, doesn't support async/await. See https://bugreports.qt.io/browse/QTBUG-58620 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477570] When using a stylus the cursor is shown as a cross when hovering over native-Wayland Qt software
https://bugs.kde.org/show_bug.cgi?id=477570 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #3 from Nicolas Fella --- Technically speaking it's up to the application to provide a (tablet) cursor image. That means some amount of inconsistencies are likely unavoidable. Qt doesn't seem to specify a tablet cursor at all, so KWin uses the fallback crosshair cursor. Changing that to another xcursor shape would be trivial. Personally speaking I kind of like the crosshair cursor though -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 478619] New: UI buttons confusingly do not look like buttons
https://bugs.kde.org/show_bug.cgi?id=478619 Bug ID: 478619 Summary: UI buttons confusingly do not look like buttons Classification: Applications Product: kdeconnect Version: 24.01.80 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: spamless.9v...@simplelogin.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- The desktop window of KDE Connect uses a list menu to display features/options available to the user, but some of them open up a sub-menu "Multimedia control, Remote input, etc" while others are actually buttons "Lock, Send Clipboard, etc". This causes issues such as making a user think "Send Clipboard" is not working because nothing seems to happen when you click on it. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 403684] SpeedDial - Add option to lock dials positions
https://bugs.kde.org/show_bug.cgi?id=403684 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/network/falkon/-/merge_requests/66 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 478618] New: "Open with" menu doesn't work with zsh
https://bugs.kde.org/show_bug.cgi?id=478618 Bug ID: 478618 Summary: "Open with" menu doesn't work with zsh Classification: Applications Product: konsole Version: 23.08.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: med.medin.2...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Launch Konsole with zsh profile 2. Right click inside it OBSERVED RESULT "Open With..." entry appears without any sub menu of related applications EXPECTED RESULT "Open Folder With" entry appears with a sub menu that contains related applications 3. Select "Open With", "Choose Application - Konsole" window appears 4. Select any suitable application like Dolphin or VSCode OBSERVED RESULT The selected app doesn't open EXPECTED RESULT The selected app opens with the provided current folder SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.7-1-MANJARO (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
