[valgrind] [Bug 451843] valgrind fails to start on a FreeBSD system which enforces W^X.
https://bugs.kde.org/show_bug.cgi?id=451843 Amit changed: What|Removed |Added CC||akami...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 451843] New: valgrind fails to start on a FreeBSD system which enforces W^X.
https://bugs.kde.org/show_bug.cgi?id=451843 Bug ID: 451843 Summary: valgrind fails to start on a FreeBSD system which enforces W^X. Product: valgrind Version: 3.18.1 Platform: FreeBSD Ports OS: FreeBSD Status: REPORTED Severity: critical Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: akami...@hotmail.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 *** valgrind fails to start on a FreeBSD system which enforces W^X. Looks like memcheck is trying to mmap with PROT_WRITE|PROT_EXEC, permissions. Is it really needed ? Or is there a option in Makefile to avoid this ? STEPS TO REPRODUCE 1. FreeBSD 13+ with W^X enforced "sysctl kern.elf64.allow_wx=0" 2. launch valgrind 3. OBSERVED RESULT ➜ ~ valgrind --version --23644:0: aspacem <<< SHOW_SEGMENTS: out_of_memory (15 segments) --23644:0: aspacem 1 segment names in 1 slots --23644:0: aspacem freelist is empty --23644:0: aspacem (0,4,5) /usr/local/libexec/valgrind/memcheck-amd64-freebsd --23644:0: aspacem 0: RSVN 00-0003ff 64m - SmFixed --23644:0: aspacem 1: 000400-0037ff832m --23644:0: aspacem 2: FILE 003800-00380c1fff 794624 r d=0x99ef79a8 i=329107 o=0 (0,4) --23644:0: aspacem 3: FILE 00380c2000-0038273fff 1777664 r-x-- d=0x99ef79a8 i=329107 o=790528 (0,4) --23644:0: aspacem 4: FILE 0038274000-0038274fff4096 rw--- d=0x99ef79a8 i=329107 o=2564096 (0,4) --23644:0: aspacem 5: ANON 0038275000-003a849fff 37m rw--- --23644:0: aspacem 6: 003a84a000-0401ff 15479m --23644:0: aspacem 7: RSVN 040200-0402000fff4096 - SmFixed --23644:0: aspacem 8: 0402001000-07 16351m --23644:0: aspacem 9: RSVN 08-0839075fff912m - SmFixed --23644:0: aspacem 10: ANON 0839076000-0859055fff511m - --23644:0: aspacem 11: ANON 0859056000-0859075fff 131072 rw--- --23644:0: aspacem 12: RSVN 0859076000-7fffefff 131038g - SmFixed --23644:0: aspacem 13: ANON 7000-7fff4096 r-x-- --23644:0: aspacem 14: RSVN 8000- 16383e - SmFixed --23644:0: aspacem >>> --23644-- core: 0/0 max/curr mmap'd, 0/0 unsplit/split sb unmmap'd, 0/0 max/curr, 0/ 0 totalloc-blocks/bytes, 0 searches 8 rzB --23644-- dinfo : 0/0 max/curr mmap'd, 0/0 unsplit/split sb unmmap'd, 0/0 max/curr, 0/ 0 totalloc-blocks/bytes, 0 searches 8 rzB --23644-- (null) : 0/0 max/curr mmap'd, 0/0 unsplit/split sb unmmap'd, 0/0 max/curr, 0/ 0 totalloc-blocks/bytes, 0 searches 0 rzB --23644-- demangle: 0/0 max/curr mmap'd, 0/0 unsplit/split sb unmmap'd, 0/0 max/curr, 0/ 0 totalloc-blocks/bytes, 0 searches 8 rzB --23644-- ttaux : 0/0 max/curr mmap'd, 0/0 unsplit/split sb unmmap'd, 0/0 max/curr, 0/ 0 totalloc-blocks/bytes, 0 searches 8 rzB --23644-- translate: 0 guest insns, 0 traces, 0 uncond chased, 0 cond chased --23644-- translate: no SP updates identified --23644-- translate: PX: SPonly 0, UnwRegs 0, AllRegs 0, AllRegsAllInsns 0 --23644-- tt/tc: 0 tt lookups requiring 0 probes --23644-- tt/tc: 0 fast-cache updates, 0 flushes --23644-- transtab: new0 (0 -> 0; ratio 0.0) [0 scs] avg tce size 0 --23644-- transtab: dumped 0 (0 -> ??) (sectors recycled 0) --23644-- transtab: discarded 0 (0 -> ??) --23644-- scheduler: 0 event checks. --23644-- scheduler: 0 indir transfers, 0 misses (1 in 0) .. --23644-- scheduler: .. of which: 0 hit0, 0 hit1, 0 hit2, 0 hit3, 0 missed --23644-- scheduler: 0/0 major/minor sched events. --23644--sanity: 0 cheap, 0 expensive checks. ==23644== ==23644== Valgrind's memory management: out of memory: ==23644==newSuperblock's request for 4194304 bytes failed. ==23644== 576,544,768 bytes have already been mmap-ed ANONYMOUS. ==23644== Valgrind cannot continue. Sorry. ==23644== ==23644== There are several possible reasons for this. ==23644== - You have some kind of memory limit in place. Look at the ==23644== output of 'ulimit -a'. Is there a limit on the size of ==23644== virtual memory or address space? ==23644== - You have run out of swap space. ==23644== - Valgrind has a bug. If you think this is the case or you are ==23644== not sure, please let us know and we'll try to fix it. ==23644== Please
[plasmashell] [Bug 450875] Panel bounces between two sizes and becomes unusable
https://bugs.kde.org/show_bug.cgi?id=450875 --- Comment #8 from ratijas --- > It slightly less than 2 minutes, how can I upload it? I'm usually doing YouTube upload + link-only access (so that it does not appear in search results, and thus won't hurt Plasma brand — especially after the problem is fixed). > Could it be this one? Yep, thanks. I'll try to apply it on second user account later, when I get back from job. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 445917] CPU-Tctl and Tccd missing from filtered sensors
https://bugs.kde.org/show_bug.cgi?id=445917 Bill Sun changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||billk...@gmail.com Ever confirmed|0 |1 --- Comment #3 from Bill Sun --- Can we not remove the filter and just add labels to show that these redundant CPU sensors are from another plugin? k10temp doesn't display per core temps, so technically it's not even redundant. I have a Ryzen 9 5900X and it's really annoying that I cannot get the overall CPU temp by looking at CCD1 and CCD2. I prefer to put my CPU temp monitor as a widget in my panel as I do overclocking and want to quickly get a feel of the temp behavior with different settings. Without CCD1 and CCD2 temps, I am forced to pick one particular core out of 24(!) and I know that's not a good representation especially when I run single threaded applications. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447524] Set the Fuzziness of the Contiguous Selection Tool to 1, and the actual Fuzziness is not 1 after restarting krita.
https://bugs.kde.org/show_bug.cgi?id=447524 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1387 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 424207] Screen Edges: Toggle window switching does not work when set to left side of screen
https://bugs.kde.org/show_bug.cgi?id=424207 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 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.
[okular] [Bug 451113] Add Shortcut CRTL-W for closing tabs
https://bugs.kde.org/show_bug.cgi?id=451113 --- 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 450644] KWIN's bad azerty handling
https://bugs.kde.org/show_bug.cgi?id=450644 --- Comment #5 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.
[Spectacle] [Bug 451842] New: Spectacle Won't Work on Fedora - on Gnome
https://bugs.kde.org/show_bug.cgi?id=451842 Bug ID: 451842 Summary: Spectacle Won't Work on Fedora - on Gnome Product: Spectacle Version: 21.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: lg_ninj...@yahoo.com CC: k...@david-redondo.de 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. Install from official fedora repositories 2. Start application 3. OBSERVED RESULT Application options are incomplete (no option to select area, only "full window" and "window under mouse" are there) EXPECTED RESULT Application window to be complete 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.
[kwin] [Bug 451268] Kwin crashes in KWin::OutputLayer::addRepaint() if computer wakes up right after going to sleep
https://bugs.kde.org/show_bug.cgi?id=451268 --- Comment #7 from Nate Graham --- Oh ok then. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451015] Non-maximized non-centered panel fails to stick to a screen edge as it should
https://bugs.kde.org/show_bug.cgi?id=451015 Nate Graham changed: What|Removed |Added Summary|Panel doesn't sticking to |Non-maximized non-centered |the edge of screen |panel fails to stick to a ||screen edge as it should Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 --- Comment #7 from Nate Graham --- I can reproduce this issue if I make the panel right-aligned and not maximized. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 449735] Printable and shareable and readable RSS feeds
https://bugs.kde.org/show_bug.cgi?id=449735 --- Comment #7 from genghisk...@gmx.ca --- The following, was never done in any similar implementation... Idea: Slideshow - Use CSS Carousel/Slideshow to move from a newer entry to an older one. Consideration: Print mode - Set current CSS to media="print". This will make the web feed experience pleasurable and not overwhelming by avoiding "TL;DR". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451268] Kwin crashes in KWin::OutputLayer::addRepaint() if computer wakes up right after going to sleep
https://bugs.kde.org/show_bug.cgi?id=451268 --- Comment #6 from guimarcalsi...@gmail.com --- (In reply to Nate Graham from comment #5) > Thanks. Those look like a different issue; could you file a separate bug > report about it? You mean the other 2 crashdumps I sent or the freeze in Wayland? If you're talking about what happened in Wayland I couldn't reproduce it anymore, so I don't have enough information to file a new bug report. If you're talking about the crashdumps then I wouldn't consider them to be different issues, as the cause for the crashes is the same as in this bug: waking up the PC too soon after sleep. I don't really know the difference between them and the original backtrace, the only thing I noticed was the missing addRepaint() But if you still think I should make another report then I can make it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451268] Kwin crashes in KWin::OutputLayer::addRepaint() if computer wakes up right after going to sleep
https://bugs.kde.org/show_bug.cgi?id=451268 --- Comment #5 from Nate Graham --- Thanks. Those look like a different issue; could you file a separate bug report about it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451293] [wayland] graphical issues after standby mode
https://bugs.kde.org/show_bug.cgi?id=451293 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |UPSTREAM Status|NEEDSINFO |RESOLVED --- Comment #6 from Nate Graham --- Thank you. These graphical glitches are caused by bugs in the NVIDIA proprietary driver for that GPU. Please report this issue to the NVIDIA folks, either by sending an email to linux-b...@nvidia.com or making a post at https://forums.developer.nvidia.com/c/gpu-unix-graphics/linux/ It would be helpful to the NVIDIA developers if you could run nvidia-bug-report.sh and attach the resulting file in your report. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444993] Incorrect ColorScheme set in kdeglobals after applying Breeze Dark Global Theme
https://bugs.kde.org/show_bug.cgi?id=444993 Nate Graham changed: What|Removed |Added Version Fixed In||5.24 Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #12 from Nate Graham --- This was fixed in Plasma 5.24 with a re-work of how Global Themes are applied. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 448411] Corruption of textual presentation during utilisation of ''/usr/bin/flatpak-spawn' --host '/usr/bin/pwsh' -noexit -command 'start-transcript -append -noclobber -includeinvocatio
https://bugs.kde.org/show_bug.cgi?id=448411 BEEDELL ROKE JULIAN LOCKHART changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |MOVED --- Comment #2 from BEEDELL ROKE JULIAN LOCKHART --- "http://github.com/PowerShell/PowerShell/issues/16746#issuecomment-1076995838; is my rationale for closure of "http://bugs.kde.org/show_bug.cgi?id=448411;. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 451841] New: Today I had to move to a new account and it is giving me an error
https://bugs.kde.org/show_bug.cgi?id=451841 Bug ID: 451841 Summary: Today I had to move to a new account and it is giving me an error Product: kmymoney Version: 5.1.2 Platform: PCLinuxOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: mark.s.hunter6...@gmail.com Target Milestone: --- Created attachment 147694 --> https://bugs.kde.org/attachment.cgi?id=147694=edit Screen shot of the error msg SUMMARY Today I had to move some transaction over to a new named account (with the same account number), which I did. When I created it it asked for an opening date, which I did a couple of days before the first transaction that was moved to it. Now when I go to save it, it gives me an error that one of the transaction is in error (it appears to be the first transaction for opening balance, which I had a credit). It seems to save the file but the error keeps occurring. Can you take a look at the screenshot and let me know how I can fix it? I tried changing the opening date backwards further but that didn't fix it. (it just moved the opening transaction to the date I moved it back to.) Thanks so much. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: yes (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION None. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451061] Menu lines become invisible until hovering them on a scaled screen (wayland)
https://bugs.kde.org/show_bug.cgi?id=451061 --- Comment #7 from Andrew Shark --- I have made another video: https://www.youtube.com/watch?v=B1o-mAgp6W8 It is sufficient to have just two full hd monitors. Decreasing the value of right monitor scaling sometimes makes menu to appear normally. And increasing it sometimes makes menu to appear misbehavely. But there is no exact point of switching from normal to misbehaved and vice versa. It is always at different values. I checked that with the context menu at the desktop. Also it affected the items in kickoff start menu, but in video it started behaving normal even while the desktop context menu is misbehaving. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427278] Panel & desktop config of secondary monitor lost after ScreenConnectors renumbering
https://bugs.kde.org/show_bug.cgi?id=427278 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #20 from Nate Graham --- It's probably a slightly different issue, unless you can point to unnecessary renumbering in the [ScreenConnectors] group of your ~/.config/plasmashellrc file as specifically still happening. If not, can you file a new bug report? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451061] Menu lines become invisible until hovering them on a scaled screen (wayland)
https://bugs.kde.org/show_bug.cgi?id=451061 --- Comment #6 from Nate Graham --- No worries! If the video is very long and it won't fit here, uploading it to YouTube is fine. But mention the URL in a comment as it's easy to get missed if it's in the URL field. :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451061] Menu lines become invisible until hovering them on a scaled screen (wayland)
https://bugs.kde.org/show_bug.cgi?id=451061 --- Comment #5 from Andrew Shark --- Yeah, sorry if that was not obvious. Isn't that field meant to be used for that? If no, I can attach video directly to bugzilla next time. In other places there is also a problem. Should I upload another video to YouTube or here in bugzilla? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 450970] The "back" and "forth" arrows don't work like the "link bar clicks", one way double-click switch, doesnt remember paths between sessions
https://bugs.kde.org/show_bug.cgi?id=450970 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Nate Graham --- Thanks. I am not able to reproduce the issue, but I'm not 100% sure I've understood it. Can you please attach a screen recording that shows the issue happening? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451061] Menu lines become invisible until hovering them on a scaled screen (wayland)
https://bugs.kde.org/show_bug.cgi?id=451061 --- Comment #4 from Nate Graham --- Thank you for the video. Strange issue. Does it only affect the Audio Volume applet, or other applets too? What about the Desktop context menu, or the context menu for Task Manager tasks or apps in Kickoff? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451061] Menu lines become invisible until hovering them on a scaled screen (wayland)
https://bugs.kde.org/show_bug.cgi?id=451061 --- Comment #3 from Nate Graham --- But what's the URL? Oh! I see you added it to the URL field lol -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451840] New: Plasmashell sluggish after waking from sleep on Wayland
https://bugs.kde.org/show_bug.cgi?id=451840 Bug ID: 451840 Summary: Plasmashell sluggish after waking from sleep on Wayland Product: plasmashell Version: 5.24.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mattyhoffm...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 147693 --> https://bugs.kde.org/attachment.cgi?id=147693=edit Demonstration of Kickoff being slow SUMMARY After waking from sleep (not hibernate) on Wayland, pressing the Super key to open Kickoff will cause it to appear but be unresponsive for a few seconds. Any input that is typed into Kickoff won't appear immediately but instead after it becomes responsive again. Also, switching virtual desktops causes the panel to freeze (which is why this is not marked as a Kickoff bug exclusively) so this is possibly related to https://bugs.kde.org/show_bug.cgi?id=451631 After a certain amount of time woken from sleep Kickoff and the panel return to normal. I'm not sure if this bug occurs EVERY time after suspend but it has happened enough that it's noticeable. Has happened to me on both openSUSE Tumbleweed on an AMD GPU and Fedora 35 on an Intel GPU. AFAIK does not happen on X11. STEPS TO REPRODUCE 1. Start a Plasma Wayland session 2. Suspend the computer 3. Wake the computer 4. Attempt to use Kickoff or switch virtual desktops OBSERVED RESULT Kickoff and the panel are slow and unresponsive EXPECTED RESULT Kickoff and the panel respond as normal SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.16-200.fc35.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 450976] Dell non recognize charged show as Fully charged instead of connected but not charge
https://bugs.kde.org/show_bug.cgi?id=450976 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UPSTREAM --- Comment #10 from Nate Graham --- >From UPower's perspective, the battery is charging: battery present: yes state: charging If that does not accurately reflect the true charging status, there is an issue much deeper in the stack. Seems like this restriction must happen at the firmware or PMU level. I suspect this is a scummy intentional limitation that Dell imposes just to be assholes to their customers. :( Some laptop manufacturers periodically do this; HP has also done it in the past. There isn't any way we can work around this. If you feel that you can't live with this limitation, the best advice I can give is to avoid Dell's hardware in the future, or return it and get something from another manufacturer. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 450932] Needs a reset option
https://bugs.kde.org/show_bug.cgi?id=450932 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |INTENTIONAL Status|NEEDSINFO |RESOLVED --- Comment #3 from Nate Graham --- Sounds like you found what you needed. A GUI "reset everything" button is tracked by Bug 389568. Being able to reset only your KScreen configuration from the GUI is a bit too niche, I think. In the future, we'd like bug reports on individual issues so we can try to fix them! :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451839] New: Plasma Crashed
https://bugs.kde.org/show_bug.cgi?id=451839 Bug ID: 451839 Summary: Plasma Crashed Product: plasmashell Version: 5.24.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nmadn...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.24.3) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 5.13.0-37-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.24 DrKonqi: 5.24.3 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I was running a update in the terminal as it starting installing Plasma crashe KDE-Neon The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 1471] [New LWP 1569] [New LWP 1607] [New LWP 1634] [New LWP 1641] [New LWP 1674] [New LWP 1679] [New LWP 1699] [New LWP 1793] [New LWP 1794] [New LWP 3213] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x563b47fa37b4) at ../sysdeps/nptl/futex-internal.h:183 __preamble__ [Current thread is 1 (Thread 0x7febcb0d69c0 (LWP 1453))] Thread 12 (Thread 0x7feb76ffe700 (LWP 3213)): #0 0x7febcef8a9cf in __GI___poll (fds=0x7feb6c000fb0, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7feb9e9621d6 in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7feb9e953841 in pa_mainloop_poll () from /lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7feb9e953ec3 in pa_mainloop_iterate () from /lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7feb9e953f70 in pa_mainloop_run () from /lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7feb9e96211d in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7feb9e8fe72c in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #7 0x7febcecae609 in start_thread (arg=) at pthread_create.c:477 #8 0x7febcef97163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7febacdca700 (LWP 1794)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x563b49c20574) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x563b49c20520, cond=0x563b49c20548) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x563b49c20548, mutex=0x563b49c20520) at pthread_cond_wait.c:638 #3 0x7febcf32068b in QWaitConditionPrivate::wait (deadline=..., this=0x563b49c20520) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=this@entry=0x563b490415a8, mutex=mutex@entry=0x563b490415a0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7febd0fa0074 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x563b49041598) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68 #6 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x563b49041500) at scenegraph/qsgthreadedrenderloop.cpp:936 #7 0x7febd0fa04e9 in QSGRenderThread::run (this=0x563b49041500) at scenegraph/qsgthreadedrenderloop.cpp:1053 #8 0x7febcf31a623 in QThreadPrivate::start (arg=0x563b49041500) at thread/qthread_unix.cpp:331 #9 0x7febcecae609 in start_thread (arg=) at pthread_create.c:477 #10 0x7febcef97163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7febad5cb700 (LWP 1793)): [KCrash Handler] #4 0x7febd0f51f5e in QSGOpaqueTextureMaterialShader::updateState (this=0x7feba4080790, state=..., newEffect=, oldEffect=0x0) at scenegraph/util/qsgtexturematerial.cpp:112 #5 0x7febd0f353d9 in QSGBatchRenderer::Renderer::renderMergedBatch (this=0x7feba4005410, batch=0x7feba400d460) at ../../include/QtQuick/5.15.3/QtQuick/private/../../../../../src/quick/scenegraph/coreapi/qsgrenderer_p.h:197 #6 0x7febd0f3af8d in QSGBatchRenderer::Renderer::renderBatches (this=this@entry=0x7feba4005410) at scenegraph/coreapi/qsgbatchrenderer.cpp:4025 #7 0x7febd0f3b67a in QSGBatchRenderer::Renderer::render (this=) at scenegraph/coreapi/qsgbatchrenderer.cpp:4337 #8 0x7febd0f1f614 in QSGRenderer::renderScene (bindable=..., this=0x7feba4005410) at scenegraph/coreapi/qsgrenderer.cpp:264 #9 QSGRenderer::renderScene (this=0x7feba4005410, bindable=...) at scenegraph/coreapi/qsgrenderer.cpp:220 #10 0x7febd0f1fae3 in QSGRenderer::renderScene (this=, fboId=) at scenegraph/coreapi/qsgrenderer.cpp:212 #11 0x7febd0f8e4d7 in QSGDefaultRenderContext::renderNextFrame (this=0x563b4875ead0, renderer=0x7feba4005410, fboId=) at scenegraph/qsgdefaultrendercontext.cpp:228 #12 0x7febd0ffc189 in QQuickWindowPrivate::renderSceneGraph (this=this@entry=0x563b4859e1b0, size=...,
[frameworks-knewstuff] [Bug 451165] Error message when clicking "Get new icons..." in system settings when using a non-English language
https://bugs.kde.org/show_bug.cgi?id=451165 --- Comment #18 from Justin Zobel --- If this patch cleanly applies to the current frameworks release I guess there's no need for a separate release. I've already proposed the use of the patch for Fedora KDE. On Thu, Mar 24, 2022, 10:13 AM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=451165 > > --- Comment #17 from Nate Graham --- > That would be up to distro packagers or the Frameworks folks. Frameworks > doesn't get automatic bugfix releases, just the normal monthly releases. So > someone would need to request one. Would you be interested in doing so? > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 451165] Error message when clicking "Get new icons..." in system settings when using a non-English language
https://bugs.kde.org/show_bug.cgi?id=451165 --- Comment #17 from Nate Graham --- That would be up to distro packagers or the Frameworks folks. Frameworks doesn't get automatic bugfix releases, just the normal monthly releases. So someone would need to request one. Would you be interested in doing so? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 451165] Error message when clicking "Get new icons..." in system settings when using a non-English language
https://bugs.kde.org/show_bug.cgi?id=451165 --- Comment #16 from Justin Zobel --- No bugfix release? On Thu, Mar 24, 2022, 9:32 AM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=451165 > > Nate Graham changed: > >What|Removed |Added > > >Version Fixed In||5.93 > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 451838] New: [wayland] Rectangle Select displays notifications on top
https://bugs.kde.org/show_bug.cgi?id=451838 Bug ID: 451838 Summary: [wayland] Rectangle Select displays notifications on top Product: Spectacle Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: indecisiveautoma...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY If a notification is on-screen or later appears on-screen and a rectangle select is activated, the notification will overlay without going behind the darkened background. A good way to test is `notify-send test` and then activating a rectangle select. You can also see this by doing `sleep 3; notify-send test`, then activating a rectangle select and then waiting for the notification to appear above the darkened area. STEPS TO REPRODUCE 1. `notify-send test` 2. Activate rectangle select 3. Notification appears above rectangle area. OBSERVED RESULT Notification appears above the rectangle screenshot area, whether it was there before or after activating the rectangle select. If the rectangle select is activated *before* the notification appears, and then the notification appears over it, then the notification will *not* be included in the screenshot. Taking a screenshot when a notification appears, the screenshot will capture the notification as it was when the rectangle select was activated. That is, say the notification timeout circle around the close button is 1/4 of the way down when the rectangle screenshot is initiated. The region the screenshot is in is selected for a screenshot. And then at the time of capture, once the user presses enter, the overlayed notification timeout circle is 3/4 of the way down. The resulting screenshot will show the notification with 1/4 of its timeout, as it was when the rectangle screenshot was activated. That is all to say, the notification will display over the rectangle select area, but the actual resulting screenshot will correctly capture the "frozen" desktop as it was when the effect is activated. The notification simply appears and is still active when over the selection area when it shouldn't be. EXPECTED RESULT The notification does not stay active or above the rectangle screenshot area. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.16.16-arch1-1 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Have not tested X11. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-karchive] [Bug 450597] Incorrect handling of zip files with data descriptors
https://bugs.kde.org/show_bug.cgi?id=450597 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/karchive/-/merge_requests/34 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 447532] Kate 21.12.0 on Windows doesn't save user color scheme
https://bugs.kde.org/show_bug.cgi?id=447532 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #10 from Nicolas Fella --- https://invent.kde.org/utilities/kate/-/merge_requests/668 should fix this. We probably should include that in 22.04 https://invent.kde.org/frameworks/kconfigwidgets/-/merge_requests/117 is also related -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 385270] Disable volume slider by scroll function optionally
https://bugs.kde.org/show_bug.cgi?id=385270 --- Comment #12 from Nate Graham --- Making it configurable only helps the people who know that it's configurable, care to configure it, and remember that they configured it. If we made it configurable but left "change-on-scroll" enabled by default, then it wouldn't change for new users just switching, so your claim would still stand. Most people don't configure anything. If we made it configurable but disabled it by default, this would have the effect of removing the feature for 99.99% of people because, again, most people never configure anything. And it would be quite annoying for the people who like this feature, most of whom would not know that it is configurable or where to configure it. And disabling this feature for views that aren't scrollable would be totally pointless since there is no problem there. The potential problem exists only in scrollable views; for non-scrollable views, it is a nice timer-saver. So making it configurable wouldn't really help there. In the end, I think our compromise is a good one. It was actually conceptualized by a UX designer. So perhaps he's the one who knows what he's doing, and you should have more faith in our design process. :) Anyway, I just wanted to give some explanation and am not really in the mood to argue, so this will be my last response. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 451828] When importing Online transactions using OFX, transactions may be skipped if occurred on the day of the last update
https://bugs.kde.org/show_bug.cgi?id=451828 --- Comment #3 from Jack --- Thomas would know better than I, but I thought when you selected date of last update, it actually did use a date three days earlier. However, making that extra window configurable could be useful in cases like this. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 385270] Disable volume slider by scroll function optionally
https://bugs.kde.org/show_bug.cgi?id=385270
--- Comment #11 from bat ---
(In reply to Nate Graham from comment #10)
> The way this is now implemented
> is supposed to be just such a balance between the use cases of scrolling
> views and changing controls by scrolling. You shouldn't experience the issue
> anymore unless your cursor *begins* over a scrollable control when you
> scroll; the control should not be changed by a scroll when it happens to
> pass under the stationary cursor while the view is being scrolled.
>
> If this isn't what you see, then it sounds like there is a bug, and I would
> encourage you to file a bug report about it.
>
> If this is what you see but you don't like it, them I'm sorry to hear that
> and you have a few options:
> 1. Manually edit the files on disk for Plasma controls to set `wheelEnabled:
> false` on the controls that change when scrolled
> 2. Use a different desktop environment
This is exactly the problem, because KDE Plasma is the only desktop environment
that really makes sense on Linux, and the EXACT problem is when I begin
scrolling when my cursor is over a scrollable element, then it does not scroll,
but changes option.
If this is as simple as changing wheelEnabled to false, I see no argument why
not update it globally to something like this pseudocode:
wheelEnabled: getConfig("wheelEnabled")
This will make everyone happy and make more users switch to KDE Plasma and
Linux in general.
I don't think you realize how bad the actual behaviour is and your own opinion
and lack of action makes a huge impact on the future of KDE Plasma market
share.
Really, you don't know what you are doing. Seems Microsoft will always have
better market share, because they know and understand UI/UX. They also didn't
ever think that middle button as paste is a good idea.
You really need someone who knows UI/UX for real and consult your ideas. KDE
Plasma should be for people, not for developers, because developers don't think
like people.
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 447532] Kate 21.12.0 on Windows doesn't save user color scheme
https://bugs.kde.org/show_bug.cgi?id=447532 Nicolas Fella changed: What|Removed |Added CC||renanmartin...@hotmail.com --- Comment #9 from Nicolas Fella --- *** Bug 451600 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 451600] Kate doesn't save "Color Theme" under "Settings"
https://bugs.kde.org/show_bug.cgi?id=451600 Nicolas Fella changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Nicolas Fella --- *** This bug has been marked as a duplicate of bug 447532 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 451165] Error message when clicking "Get new icons..." in system settings when using a non-English language
https://bugs.kde.org/show_bug.cgi?id=451165 Nate Graham changed: What|Removed |Added Version Fixed In||5.93 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 451165] Error message when clicking "Get new icons..." in system settings when using a non-English language
https://bugs.kde.org/show_bug.cgi?id=451165 Nate Graham changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/knewstuff/commit/693 ||a2ea3926400b1482888a2df2c53 ||2852b8f971 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #15 from Nate Graham --- Git commit 693a2ea3926400b1482888a2df2c532852b8f971 by Nate Graham, on behalf of Alexander Lohnau. Committed on 23/03/2022 at 22:58. Pushed by ngraham into branch 'master'. Do not set user-visible name as additional agent information Instead we want the filename, which is more useful as an identifier anyways, because we would otherwise have to check which user-visible names originate from which knsrc file. M +4-1src/core/engine.cpp https://invent.kde.org/frameworks/knewstuff/commit/693a2ea3926400b1482888a2df2c532852b8f971 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356446] [Meta] Enable Qt scaling on X11
https://bugs.kde.org/show_bug.cgi?id=356446 --- Comment #78 from Nate Graham --- If your issue was purely about differences in scaling relating to modesetting, feel free to un-dupe it. I might have gotten confused because you mentioned PLASMA_USE_QT_SCALING. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 451242] "Could not take a screenshot" error
https://bugs.kde.org/show_bug.cgi?id=451242 Nate Graham changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #6 from Nate Graham --- I had a feeling it was going to be something like that. :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451167] Wrong menu positioning under wayland
https://bugs.kde.org/show_bug.cgi?id=451167 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Nate Graham --- Ok, I think that's up-to-date enough. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 451254] Close animation not shown
https://bugs.kde.org/show_bug.cgi?id=451254 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Nate Graham --- Well that's strange. Thanks for the info. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 451828] When importing Online transactions using OFX, transactions may be skipped if occurred on the day of the last update
https://bugs.kde.org/show_bug.cgi?id=451828 --- Comment #2 from Dawid Wróbel --- This actually isn’t an alternative, as it sets the period of time to a fixed T minus X. If the last time I downloaded transactions was anywhere earlier than in the last X days, some transactions will be ignored. What I want is for KMM to remember when I last downloaded (which it does in default setup), but also assume extra margin of a few days, so that any backdated transactions are also included. On Wed, Mar 23, 2022 at 6:29 PM Thomas Baumgart wrote: > https://bugs.kde.org/show_bug.cgi?id=451828 > > --- Comment #1 from Thomas Baumgart --- > Created attachment 147685 > --> https://bugs.kde.org/attachment.cgi?id=147685=edit > OFX import options > > Please see attached screenshot. Such an option is already available. If it > is > not working, then please state that here or close it as not a bug. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451235] right click menu entries not readable in wayland
https://bugs.kde.org/show_bug.cgi?id=451235 --- Comment #3 from Tobias G. --- (In reply to Nate Graham from comment #2) > Are you using menu transparency? If so, does the issue go away if you make > menus opaque again? Yes, I'm using transparency, no, it doesn't go away when making it opaque again :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451232] Broken font rendering in wayland
https://bugs.kde.org/show_bug.cgi?id=451232 --- Comment #4 from Tobias G. --- (In reply to Nate Graham from comment #3) > And it doesn't happen with anything in Plasma itself, right? Like text in > Kickoff of the Task Manager or icons on the desktop? No, neither in kickoff, icons on the desktop nor in the task manager in the panel. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385135] Monitor connection names differ across X11 and Wayland, causing multi-monitor containment mappings to break when switching session types
https://bugs.kde.org/show_bug.cgi?id=385135 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 447532] Kate 21.12.0 on Windows doesn't save user color scheme
https://bugs.kde.org/show_bug.cgi?id=447532 --- Comment #8 from a...@absolutelyfree.me --- I am seeing this same issue with version 21.12.3 on my Windows 10 (version 21H1) system. I have confirmed that my katerc file shows the correct theme (breeze dark) as the default but it always opens using the regular breeze color theme. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 449948] After kwin_wayland crashes and restarts or is manually restarted, Reboot, shutdown and logout do not work due to ksmserver relying on XWayland which also died and did not come
https://bugs.kde.org/show_bug.cgi?id=449948 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 451793] Blue Ocean-style tabs
https://bugs.kde.org/show_bug.cgi?id=451793 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Summary|Blue Ocean-style tabs not |Blue Ocean-style tabs |implemented | Severity|normal |wishlist Ever confirmed|0 |1 CC||agrine...@gmail.com, ||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451333] Windows open in awkward sizes when the display resolutions are not equal
https://bugs.kde.org/show_bug.cgi?id=451333 --- Comment #3 from Nate Graham --- Gotcha. So it seems like the issue is that KWin thinks the viewport is too small to center the window, so it maximizes it instead. I guess it makes that calculation based on the size of the wrong screen. Does this all work properly on Wayland, or is it broken for you there too? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 447532] Kate 21.12.0 on Windows doesn't save user color scheme
https://bugs.kde.org/show_bug.cgi?id=447532 a...@absolutelyfree.me changed: What|Removed |Added CC||a...@absolutelyfree.me -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450875] Panel bounces between two sizes and becomes unusable
https://bugs.kde.org/show_bug.cgi?id=450875 --- Comment #7 from kdereport.fireha...@slmail.me --- Created attachment 147689 --> https://bugs.kde.org/attachment.cgi?id=147689=edit plasma-org.kde.plasma.desktop-appletsrc Could it be this one? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450875] Panel bounces between two sizes and becomes unusable
https://bugs.kde.org/show_bug.cgi?id=450875 --- Comment #6 from kdereport.fireha...@slmail.me --- Can you give me another hint on what to search for in config files? I'm on Arch Linux I have just realized a video showing all the bugs together from plasma start till the panel disappears and then the wallpaper gets totally black. It slightly less than 2 minutes, how can I upload it? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 446924] Support distribution upgrades on Fedora
https://bugs.kde.org/show_bug.cgi?id=446924 --- Comment #5 from Nate Graham --- Please do. In fact every distro needs to be individually supported. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 451837] When profiling this specific executable, valgrind fails to break down 0x62 0xF1 0x7F 0x28 0x7F 0x2 0xF 0x87 0x95 0xA1 into 2 separate instructions
https://bugs.kde.org/show_bug.cgi?id=451837 ytr...@sdf-eu.org changed: What|Removed |Added CC||ytr...@sdf-eu.org -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 446924] Support distribution upgrades on Fedora
https://bugs.kde.org/show_bug.cgi?id=446924 john changed: What|Removed |Added CC||johnmaveric...@mail.com --- Comment #4 from john --- (In reply to Nate Graham from comment #1) > openSUSE Leap Correction: System upgrades using Discover are not available in openSUSE Leap :( (I WISH!!! -> https://hackweek.opensuse.org/projects/easy-opensuse-upgrade ) Should I open a bug report for openSUSE as well? (I don't think it's a good idea cause we'll end up with one bug per distro) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 451837] New: When profiling this specific executable, valgrind fails to break down 0x62 0xF1 0x7F 0x28 0x7F 0x2 0xF 0x87 0x95 0xA1 into 2 separate instructions
https://bugs.kde.org/show_bug.cgi?id=451837 Bug ID: 451837 Summary: When profiling this specific executable, valgrind fails to break down 0x62 0xF1 0x7F 0x28 0x7F 0x2 0xF 0x87 0x95 0xA1 into 2 separate instructions Product: valgrind Version: 3.19 GIT Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: callgrind Assignee: josef.weidendor...@gmx.de Reporter: ytr...@sdf-eu.org Target Milestone: --- Created attachment 147688 --> https://bugs.kde.org/attachment.cgi?id=147688=edit Attached executable for reproducing the bug. I built the latest btrfsprogs on my system with profile feedback (-fprofile-use), the program runs normally on my cpu but when I try to perform [liveuser@localhost-live btrfs-progs-v5.16.2]$ valgrind --tool=callgrind --dump-instr=yes --branch-sim=yes --collect-jumps=yes ./btrfs.static check -p --init-csum-tree /tmp/newly_btrfs_volume_example_with_sha256 with the executable attached, it fails with : Starting repair. Opening filesystem to check... vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0x7F 0x28 0x7F 0x2 0xF 0x87 0x95 0xA1 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=NONE vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 ==63828== valgrind: Unrecognised instruction at address 0x45dade. ==63828==at 0x45DADE: btrfs_csum_data.constprop.0.isra.0 (disk-io.c:147) ==63828==by 0x45D949: btrfs_check_super (disk-io.c:1666) ==63828==by 0x45D876: btrfs_read_dev_super (disk-io.c:1879) ==63828==by 0x45D5A9: btrfs_scan_one_device (volumes.c:548) ==63828==by 0x45D4E3: check_mounted_where.constprop.0 (open-utils.c:61) ==63828==by 0x45D489: check_mounted (open-utils.c:130) ==63828==by 0x45CD93: cmd_check (main.c:10455) ==63828==by 0x45C6DD: main (commands.h:125) ==63828== Your program just tried to execute an instruction that Valgrind ==63828== did not recognise. There are two possible reasons for this. ==63828== 1. Your program has a bug and erroneously jumped to a non-code ==63828==location. If you are running Memcheck and you just saw a ==63828==warning about a bad jump, it's probably your program's fault. ==63828== 2. The instruction is legitimate but Valgrind doesn't handle it, ==63828==i.e. it's Valgrind's fault. If you think this is the case or ==63828==you are not sure, please let us know and we'll try to fix it. ==63828== Either way, Valgrind will now raise a SIGILL signal which will ==63828== probably kill your program. ==63828== ==63828== Process terminating with default action of signal 4 (SIGILL): dumping core ==63828== Illegal opcode at address 0x45DADE ==63828==at 0x45DADE: btrfs_csum_data.constprop.0.isra.0 (disk-io.c:147) ==63828==by 0x45D949: btrfs_check_super (disk-io.c:1666) ==63828==by 0x45D876: btrfs_read_dev_super (disk-io.c:1879) ==63828==by 0x45D5A9: btrfs_scan_one_device (volumes.c:548) ==63828==by 0x45D4E3: check_mounted_where.constprop.0 (open-utils.c:61) ==63828==by 0x45D489: check_mounted (open-utils.c:130) ==63828==by 0x45CD93: cmd_check (main.c:10455) ==63828==by 0x45C6DD: main (commands.h:125) ==63828== ==63828== Events: Ir Bc Bcm Bi Bim ==63828== Collected : 791898 132272 8055 1806 620 ==63828== ==63828== I refs: 791,898 ==63828== ==63828== Branches: 134,078 (132,272 cond + 1,806 ind) ==63828== Mispredicts: 8,675 ( 8,055 cond + 620 ind) ==63828== Mispred rate: 6.5% (6.1% + 34.3% ) But unlike what valgrind says 0x62 0xF1 0x7F 0x28 0x7F 0x2 0xF 0x87 0x95 0xA1 consists of 2 instructions instead of 1 and thus in reality isn’t a single invalid instruction but : 0045dac0 : 45dade: 62 f1 7f 28 7f 02 vmovdqu8 YMMWORD PTR [rdx],ymm0 45dae4: 0f 87 95 a1 fa ff ja 407c7f SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 37. Rpms executables only Please fix this ! -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 376563] Kleopatra crashes with segmentation fault on startup after importing PEM file
https://bugs.kde.org/show_bug.cgi?id=376563 --- Comment #10 from Guido Winkelmann --- (In reply to Guido Winkelmann from comment #9) > As of 2022-03-23, the bug is still present in the released version 21.08.3, > but does appear to be fixed in the newest git version. Does anybody happen to know which commit fixed it, and whether it was in kleopatra itself or in libkleo? -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 376563] Kleopatra crashes with segmentation fault on startup after importing PEM file
https://bugs.kde.org/show_bug.cgi?id=376563 --- Comment #9 from Guido Winkelmann --- As of 2022-03-23, the bug is still present in the released version 21.08.3, but does appear to be fixed in the newest git version. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 317335] Missing the writeConfig in order to write in the configuration
https://bugs.kde.org/show_bug.cgi?id=317335 Natalie Clarius changed: What|Removed |Added CC||natalie_clar...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 299276] Support Plasma API Extensions in KWin Scripting
https://bugs.kde.org/show_bug.cgi?id=299276 Natalie Clarius changed: What|Removed |Added CC||natalie_clar...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409889] Staking order is not accessible in KWin scripts
https://bugs.kde.org/show_bug.cgi?id=409889 --- Comment #5 from Natalie Clarius --- I don't know if this has been recently implemented or always been there and just never documented, but it works for me: > client.stackingOrder -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451268] Kwin crashes in KWin::OutputLayer::addRepaint() if computer wakes up right after going to sleep
https://bugs.kde.org/show_bug.cgi?id=451268 guimarcalsi...@gmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450875] Panel bounces between two sizes and becomes unusable
https://bugs.kde.org/show_bug.cgi?id=450875 --- Comment #5 from ratijas --- I'm unironically getting goose bumps just by reading this bug report, lol. Which applets do you have on the panel? Could you please share with us your Plasma config? It's something inside ~/.config named as "plasma", "applet" or "desktop" and probably with "rc" suffix. Inspect them via text editor, and you'll find the one that contains applets configuration. Also, which distro is that? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445129] Provide an ability to emit dbus signals and react to the method calls, so that other programs could interact with a KWin Script
https://bugs.kde.org/show_bug.cgi?id=445129 Natalie Clarius changed: What|Removed |Added CC||natalie_clar...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450963] Only unfocused desktop thumbnails show the panel
https://bugs.kde.org/show_bug.cgi?id=450963 --- Comment #5 from Michael D --- Ah, is that what's going on? The panel is 40px wide, so not exactly skinny, but the outline should definitely be drawn around the thumbnail. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450963] Only unfocused desktop thumbnails show the panel
https://bugs.kde.org/show_bug.cgi?id=450963 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 --- Comment #4 from Nate Graham --- Ah! I see the issue. The focus outline is drawn inside the thumbnail rather than outside of it, so it completely covers skinny panels. Should be an easy fix. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450875] Panel bounces between two sizes and becomes unusable
https://bugs.kde.org/show_bug.cgi?id=450875 --- Comment #4 from kdereport.fireha...@slmail.me --- Created attachment 147687 --> https://bugs.kde.org/attachment.cgi?id=147687=edit More weird movements of the panel, and the coloring of the wallpaper I couldn't take a screenshot because if I open a window the wallpaper returns normally colored. Here's a video showing the other weird movement of the panel and the fact that everytime I close all windows the wallpaper gets weirdly colored, as you can see in the video the color transitions from normal to strange and I can see that transition everytime I close the last opened window. After sometimes the panel freezes and if I try to hoover the cursor on it it disappears till next Plasma restart. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable, and if you force-resize them, they forget their size after the computer or plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=332512 --- Comment #112 from Luca Carlon --- Thank you Nate for your feedback. I'm currently stuck with the Wayland implementation. It seems that this technique works in Wayland when only Qt is involved, but does not seem to work when applied to the PlasmaQuick::Dialog. I suspect the reason is related to the fact that the popup in Wayland is somehow wrapped in a KWayland::Client::PlasmaShellSurface, so resize events should be redirected there instead. I'm digging into KWayland to find out how this works, but if someone had a hint, it would be helpful. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 451836] Unable to sync podcasts more than once
https://bugs.kde.org/show_bug.cgi?id=451836 bugs@nordcomputer.de changed: What|Removed |Added Platform|Debian testing |Flatpak -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 451306] I can't sync Kasts with gpodder.net
https://bugs.kde.org/show_bug.cgi?id=451306 bugs@nordcomputer.de changed: What|Removed |Added CC||bugs@nordcomputer.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448220] One or both dual monitors powers off after login to Wayland KDE
https://bugs.kde.org/show_bug.cgi?id=448220 SP changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448220] One or both dual monitors powers off after login to Wayland KDE
https://bugs.kde.org/show_bug.cgi?id=448220 --- Comment #53 from SP --- (In reply to Zamundaaa from comment #44) > The only suspicious thing I can see here is that in some areas of the log > there's commits without any pipelines printed: > > kwin_wayland_drm: committing pipelines > > kwin_wayland_drm: (list done) > but the rest of the log suggests that's not a behavior bug of KWin but > probably some weirdness with logging instead. > Both monitors still get presented and KWin gets responses from the kernel > that the presentations do in fact happen. So from the PoV of KWin everything > is completely fine - this would suggest that it's a kernel bug. > > There's two more data points we can gather: > 1. the output of drm_info when you're in SDDM (you can get it by logging in > via ssh and executing drm_info with sudo) and when you're in the broken > session > 2. if you uninstall xf86-video-amdgpu, reboot and let the default Xorg > driver take over, which uses the same driver interface as kwin_wayland, do > sddm and the Plasma X11 session start exhibiting broken behavior as well, or > does it continue working fine? The removal of xorg-x11-drv-amdgpu definitely resolved the problem. There must exist some conflict between this and the built-in kernel amdgpu driver . As I am using Wayland I would have thought this irrelevant - but since deinstalling the xorg-x11-drv-amdgp driver I have not had a recurrence of this problem on either of our computers with dual monitors. Thank you @Zamundaaa for the tip. I will mark this as resolved. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 451836] Unable to sync podcasts more than once
https://bugs.kde.org/show_bug.cgi?id=451836 bugs@nordcomputer.de changed: What|Removed |Added CC||bugs@nordcomputer.de -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 451836] New: Unable to sync podcasts more than once
https://bugs.kde.org/show_bug.cgi?id=451836 Bug ID: 451836 Summary: Unable to sync podcasts more than once Product: kasts Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: bugs@nordcomputer.de Target Milestone: --- SUMMARY When configuring the sync function (nextcloud sync), the sync just works until kasts gets closed. When reopen the software, sync is disabled. When trying to login again, the password field is empty and even if it gets set again, sync stays disabled. Running the flatpak as root (sudo -i) works as expected. STEPS TO REPRODUCE 1. Install Kasts Flatpak and open it 2. Configure Synchronization for nextcloud-gpodder sync. 3. Sync your podcasts 4. Close Kasts 5. Reopen Kasts OBSERVED RESULT Synchronizsation is disabled and sync is not working anymore, even if you try to re-enter your credentials and url. EXPECTED RESULT Sync should work, even after closing and reopening Kasts. SOFTWARE/OS VERSIONS Linux: Debian Bookworm Kasts Version: 22.02 (Flatpak) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440417] Really high CPU usage when many files are updated
https://bugs.kde.org/show_bug.cgi?id=440417
--- Comment #4 from tagwer...@innerjoin.org ---
(In reply to lemaitre from comment #3)
> ... To be noted that the bug does not seem to appear at the file creation
> (even
> creating 10 000 files in one go), but at the update of the files ...
I noticed a difference between running
touch testfile{1..1}
a first time and repeating it. Dolphin worked a little harder but it was still
just a second or so of high CPU.
Baloo spent a while catching up with changes and baloo_file_extractor had a
look at the "touched" files (in batches of 40). Nothing excessive though...
Could there be an issue with large numbers of thumbnails? (How big is
.cache/thumbnails/normal?)
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 451835] New: Dolphin fails to rename file in remote encrypted vault accessed through SFTP
https://bugs.kde.org/show_bug.cgi?id=451835 Bug ID: 451835 Summary: Dolphin fails to rename file in remote encrypted vault accessed through SFTP Product: dolphin Version: 19.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: cont...@yannsalmon.fr CC: kfm-de...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. On computer A, create an encrypted vault, mount it and put a simple file "test" in it. 2. From computer B, use Dolphin's SFTP to access the (mounted) vault on computer A. 3. Using Dolphin (right-click, rename), rename "test" into say "test2". OBSERVED RESULT Dolphin displays an error dialog saying "internal problem" and to report a bug here. File is not renamed. EXPECTED RESULT File should be renamed in the remote vault. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.8 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION Problems also appear when copying a file to the remote vault, creating a file or modifying/saving an existing file with Kate : Dolphin displays an error bar above the main view, saying it could not rename the partial file and to verify my access rights. Indeed, I can see a file with .partial at the end, which in each case has the intended content. Setting up a SSH-connexion from computer B to computer A in a terminal to the same vault and issuing rename (mv) command there works. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451834] New: Plasma Desktop Crash during Wifi Sign-In
https://bugs.kde.org/show_bug.cgi?id=451834 Bug ID: 451834 Summary: Plasma Desktop Crash during Wifi Sign-In Product: plasmashell Version: 5.24.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jwbradley2...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.24.3) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 5.16.16-arch1-1 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 5.24.3 [KCrashBackend] -- Information about the crash: While connecting to an AT network that was offline, the plasma desktop crashed. This occured twice and I have not been able to replicate it reliably since. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7fdd33412054 in QTransform::operator=(QTransform const&) () at /usr/lib/libQt5Gui.so.5 #5 0x7fdd333a9ab9 in QRasterPaintEngine::updateOutlineMapper() () at /usr/lib/libQt5Gui.so.5 #6 0x7fdd333adfc1 in QRasterPaintEngine::begin(QPaintDevice*) () at /usr/lib/libQt5Gui.so.5 #7 0x7fdd333c3777 in QPainter::begin(QPaintDevice*) () at /usr/lib/libQt5Gui.so.5 #8 0x7fdd30a1cc8f in QtWaylandClient::QWaylandShmBackingStore::beginPaint(QRegion const&) () at /usr/lib/libQt5WaylandClient.so.5 #9 0x7fdd332e4c6e in QBackingStore::beginPaint(QRegion const&) () at /usr/lib/libQt5Gui.so.5 #10 0x7fdd339d29b7 in () at /usr/lib/libQt5Widgets.so.5 #11 0x7fdd339fd855 in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #12 0x7fdd339c71c6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #13 0x7fdd32d745aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #14 0x7fdd32d750a9 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #15 0x7fdd32dbc678 in () at /usr/lib/libQt5Core.so.5 #16 0x7fdd31171163 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #17 0x7fdd311c79e9 in () at /usr/lib/libglib-2.0.so.0 #18 0x7fdd3116e6c5 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #19 0x7fdd32dc057a in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #20 0x7fdd32d6c88b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #21 0x7fdd33bc1776 in QDialog::exec() () at /usr/lib/libQt5Widgets.so.5 #22 0x7fdd31d76859 in KMessageBox::createKMessageBox(QDialog*, QDialogButtonBox*, QIcon const&, QString const&, QStringList const&, QString const&, bool*, QFlags, QString const&, QMessageBox::Icon) () at /usr/lib/libKF5WidgetsAddons.so.5 #23 0x7fdd31d76f55 in KMessageBox::createKMessageBox(QDialog*, QDialogButtonBox*, QMessageBox::Icon, QString const&, QStringList const&, QString const&, bool*, QFlags, QString const&) () at /usr/lib/libKF5WidgetsAddons.so.5 #24 0x7fdd31d796f7 in () at /usr/lib/libKF5WidgetsAddons.so.5 #25 0x7fdd31d79a99 in KMessageBox::warningYesNoCancel(QWidget*, QString const&, QString const&, KGuiItem const&, KGuiItem const&, KGuiItem const&, QString const&, QFlags) () at /usr/lib/libKF5WidgetsAddons.so.5 #26 0x7fdd3231d028 in KIO::JobUiDelegate::requestMessageBox(KIO::JobUiDelegateExtension::MessageBoxType, QString const&, QString const&, QString const&, QString const&, QString const&, QString const&, QString const&, KIO::MetaData const&) () at /usr/lib/libKF5KIOWidgets.so.5 #27 0x7fdd30c46b12 in () at /usr/lib/libKF5KIOCore.so.5 #28 0x7fdd32d987d6 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #29 0x7fdd339c71c6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #30 0x7fdd32d745aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #31 0x7fdd32d750a9 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #32 0x7fdd32dbc678 in () at /usr/lib/libQt5Core.so.5 #33 0x7fdd31171163 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #34 0x7fdd311c79e9 in () at /usr/lib/libglib-2.0.so.0 #35 0x7fdd3116e6c5 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #36 0x7fdd32dc057a in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #37 0x7fdd32d6c88b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #38 0x7fdd32bcfa56 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #39 0x7fdd3457ddff in () at /usr/lib/libQt5Quick.so.5 #40 0x7fdd32bcc8cc in () at /usr/lib/libQt5Core.so.5 #41 0x7fdd327455c2 in start_thread () at /usr/lib/libc.so.6 #42
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable, and if you force-resize them, they forget their size after the computer or plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=332512 --- Comment #111 from Nate Graham --- Seems like a sane approach overall. I'd encourage you to keep polishing it and eventually submit it! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440417] Really high CPU usage when many files are updated
https://bugs.kde.org/show_bug.cgi?id=440417 --- Comment #3 from lemaitre --- Yes, I still have the bug. To be noted that the bug does not seem to appear at the file creation (even creating 10 000 files in one go), but at the update of the files. Here are the version I am now running: Dolphin: 21.12.2 Linux/KDE Plasma: NixOS/22.05pre KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.3 Kernel Version: 5.15.26 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 418517] Titlebar text does not update correctly when title is fully to the left and no buttons are placed there.
https://bugs.kde.org/show_bug.cgi?id=418517 Nate Graham changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/breeze/commit/03b29c9fe9 |ma/breeze/commit/5fa8abe6fb |325f6ede8eaafe050650112acad |9405fe26c7ce955c76c126e80c1 |705 |30d --- Comment #10 from Nate Graham --- Git commit 5fa8abe6fb9405fe26c7ce955c76c126e80c130d by Nate Graham, on behalf of Paul McAuley. Committed on 23/03/2022 at 20:26. Pushed by ngraham into branch 'master'. Use correct spacing factor for TitleBar_SideMargin This commit fixes the glitches in titlebar caption when it is updated near the edge. These glitches were caused by the Titlebar_SideMargin being multiplied by the incorrect largeSpacing factor when smallSpacing is used in every other instance. M +2-2kdecoration/breezedecoration.cpp https://invent.kde.org/plasma/breeze/commit/5fa8abe6fb9405fe26c7ce955c76c126e80c130d -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440417] Really high CPU usage when many files are updated
https://bugs.kde.org/show_bug.cgi?id=440417 tagwer...@innerjoin.org changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from tagwer...@innerjoin.org --- (In reply to Thiago Sueto from comment #1) > Is this still reproducible for you with current Plasma? I can't reproduce > this one. I had to create 10,000 files before it would reach 90% CPU on my > machine, and it stops after a moment. That what it looked like for me as well (Neon). Checked to see if it might be different on NixOS (Dolphin 21.08.3) and that also seemed well behaved. NixOS is like... Wow... -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 442422] Cannot install org.kde.Sdk.Debug/5.15
https://bugs.kde.org/show_bug.cgi?id=442422 jonathan...@web.de changed: What|Removed |Added CC||jonathan...@web.de -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 451689] window-close-symbolic uses the circled style which no longer matches the window decoration close button's default appearance
https://bugs.kde.org/show_bug.cgi?id=451689 Nate Graham changed: What|Removed |Added Component|gtk theme |Icons Assignee|uhh...@gmail.com|visual-des...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 451689] window-close-symbolic uses the circled style which no longer matches the window decoration close button's default appearance
https://bugs.kde.org/show_bug.cgi?id=451689 Nate Graham changed: What|Removed |Added Component|Icons |gtk theme Ever confirmed|0 |1 Summary|Breeze icons provide|window-close-symbolic uses |circled closed button by|the circled style which no |default |longer matches the window ||decoration close button's ||default appearance Assignee|visual-des...@kde.org |uhh...@gmail.com Status|REPORTED|CONFIRMED Severity|normal |minor CC||n...@kde.org, ||plasma-b...@kde.org --- Comment #1 from Nate Graham --- In that window, the button in question is just an ordinary button, not an actual window decoration button. Seems like it's using the `window-close-symbolic` icon, which indeed uses the circled style. We could consider changing that. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451802] GPX files fails to load
https://bugs.kde.org/show_bug.cgi?id=451802 Maik Qualmann changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/d3ce44e ||9de912b33627235fd910c846599 ||705a19 Status|REPORTED|RESOLVED Version Fixed In||8.0.0 Resolution|--- |FIXED --- Comment #8 from Maik Qualmann --- Git commit d3ce44e9de912b33627235fd910c846599705a19 by Maik Qualmann. Committed on 23/03/2022 at 20:00. Pushed by mqualmann into branch 'master'. fix reading child elements FIXED-IN: 8.0.0 M +2-1NEWS M +1-1core/utilities/geolocation/geoiface/tracks/trackreader.cpp https://invent.kde.org/graphics/digikam/commit/d3ce44e9de912b33627235fd910c846599705a19 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 451242] "Could not take a screenshot" error
https://bugs.kde.org/show_bug.cgi?id=451242 Lyubomir <88zo26...@mozmail.com> changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Lyubomir <88zo26...@mozmail.com> --- Removing the .desktop file that was converted by Firejail fixed it! Strange as I was not using the .desktop but was launching directly using the terminal, I think the command inside the .desktop file should not have been executed... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451802] GPX files fails to load
https://bugs.kde.org/show_bug.cgi?id=451802 --- Comment #7 from Maik Qualmann --- Git commit 6280a012ee10a9e588271568ff17aeaf825a1060 by Maik Qualmann. Committed on 23/03/2022 at 19:53. Pushed by mqualmann into branch 'master'. remove dead code and variables M +18 -201 core/utilities/geolocation/geoiface/tracks/trackreader.cpp M +0-17 core/utilities/geolocation/geoiface/tracks/trackreader.h https://invent.kde.org/graphics/digikam/commit/6280a012ee10a9e588271568ff17aeaf825a1060 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 418996] Dark Telegram icon on dark Breeze theme
https://bugs.kde.org/show_bug.cgi?id=418996 Nate Graham changed: What|Removed |Added Status|REOPENED|CONFIRMED Severity|minor |normal Priority|NOR |HI --- Comment #23 from Nate Graham --- Yeah, agreed. Not clear who's at fault here though. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 451833] New: Support to exclude vendor (or other) directory from Class Browser, but still have it parsed for code completion
https://bugs.kde.org/show_bug.cgi?id=451833 Bug ID: 451833 Summary: Support to exclude vendor (or other) directory from Class Browser, but still have it parsed for code completion Product: kdevelop Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: Language Support: PHP Assignee: kdevelop-bugs-n...@kde.org Reporter: mail+...@branleb.de Target Milestone: --- SUMMARY *** It would be great if the Class Browser supported an (Project) Option to exclude code from specific directories. Those directories should still be parsed for code completion purposes, but ignored otherwise. (Handled like system include/library directories, if you will). Typical Usecase would be the vendor directory used in composer projects. It is usually located within the project folder, but basically consists only of external code which is used within the current project. It would be great, if code completion, jump to etc would still work on classes and functions defined there but if those would not fill up the class browser of the current project because those classes are not actually "classes in the project" but classes of libraries used by the project. *** STEPS TO REPRODUCE 1. checkout a or create a composer based project 2. let composer install some external libraries 3. use kdevelop with that project OBSERVED RESULT Class Browser lists all classes from vendor/ EXPECTED RESULT Should only list actual project classes SOFTWARE/OS VERSIONS: ALL ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450637] Wayland: Menus in LibreOffice are shown as decorated separate windows when LibreOffice window was not focussed
https://bugs.kde.org/show_bug.cgi?id=450637 ActualDisaster2447 changed: What|Removed |Added CC||suliman.shahin...@gmail.com --- Comment #7 from ActualDisaster2447 --- Can reproduce this as well on openSUSE Tumbleweed with Plasma Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 451832] New: KDevelop crash on exit: in QHash::constBegin()
https://bugs.kde.org/show_bug.cgi?id=451832 Bug ID: 451832 Summary: KDevelop crash on exit: in QHash::constBegin() Product: kdevelop Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: rjvber...@gmail.com Target Milestone: --- Application: kdevelop (5.6.1-11-gf02541572b) (Compiled from sources) Qt Version: 5.9.8 Frameworks Version: 5.60.0 Operating System: Linux 4.14.23-ck1-mainline-core2-rjvb x86_64 Windowing system: X11 Distribution: Ubuntu 14.04.6 LTS -- Information about the crash: - What I was doing when the application crashed: I quit KDevelop. I have my personal patch that helps prevent most ?DUContext-related crashes on exit (presented on a different ticket) but I've seen this one a few times now. The reason for filing this as an issue is that I hope to get some feedback on how a crash could occur when accessing `m_referenceCounts.constBegin()`, i.e. `QHash::constBegin()`. The backtrace shows a this pointer that's not null in qhash.h so I assume that this is a case of a stale KDevelop::DUChainPrivate instance, for instance because it was freed while `doMoreCleanup()` was still executing? Shouldn't there be more extensive checking of DUChain::m_deleted in the DUChain class methods? Post-mortem debugging of this crashed instance (with lldb) suggests DUChain::m_deleted is false, but also doesn't give me a slightly different backtrace, claiming that the crash occured trying to lock `m_referenceCountsMutex` 2 lines earlier. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f04771854c0 (LWP 24651))] Thread 18 (Thread 0x7f0418cfb700 (LWP 25963)): #0 0x7f046d541404 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f046e4ef93b in QWaitConditionPrivate::wait (this=0x7f0446fa8a80, time=) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.9.8/qtbase/src/corelib/thread/qwaitcondition_unix.cpp:143 #2 0x7f046e4ef6e5 in QWaitCondition::wait (this=0x7f04468c0868, mutex=0x7f0449101ee0, time=18446744073709551615) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.9.8/qtbase/src/corelib/thread/qwaitcondition_unix.cpp:215 #3 0x7f047537a1fd in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=0x7f0446fbe0e0, th=0x7f041ea14220) at /opt/local/var/lnxports/build/_opt_local_site-ports_kf5_KF5-Frameworks/kf5-threadweaver/work/threadweaver-5.60.0/src/weaver.cpp:594 #4 ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned (this=0x7f0446fbe0e0, th=0x7f041ea14220) at /opt/local/var/lnxports/build/_opt_local_site-ports_kf5_KF5-Frameworks/kf5-threadweaver/work/threadweaver-5.60.0/src/weaver.cpp:581 #5 0x7f047537e3d4 in non-virtual thunk to ThreadWeaver::SuspendedState::applyForWork(ThreadWeaver::Thread*, bool) () at /opt/local/var/lnxports/build/_opt_local_site-ports_kf5_KF5-Frameworks/kf5-threadweaver/work/threadweaver-5.60.0/src/suspendedstate.cpp:56 #6 0x7f047537a0fe in ThreadWeaver::Weaver::applyForWork (this=, th=0xa7, wasBusy=false) at /opt/local/var/lnxports/build/_opt_local_site-ports_kf5_KF5-Frameworks/kf5-threadweaver/work/threadweaver-5.60.0/src/weaver.cpp:568 #7 0x7f047537e003 in ThreadWeaver::WorkingHardState::applyForWork (this=0x7f04490e8520, th=0x7f041ea14220, wasBusy=) at /opt/local/var/lnxports/build/_opt_local_site-ports_kf5_KF5-Frameworks/kf5-threadweaver/work/threadweaver-5.60.0/src/workinghardstate.cpp:73 #8 0x7f047537e0a0 in non-virtual thunk to ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /opt/local/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f047537a0fe in ThreadWeaver::Weaver::applyForWork (this=, th=0xa7, wasBusy=false) at /opt/local/var/lnxports/build/_opt_local_site-ports_kf5_KF5-Frameworks/kf5-threadweaver/work/threadweaver-5.60.0/src/weaver.cpp:568 #10 0x7f047537e003 in ThreadWeaver::WorkingHardState::applyForWork (this=0x7f04490e8520, th=0x7f041ea14220, wasBusy=) at /opt/local/var/lnxports/build/_opt_local_site-ports_kf5_KF5-Frameworks/kf5-threadweaver/work/threadweaver-5.60.0/src/workinghardstate.cpp:73 #11 0x7f047537e0a0 in non-virtual thunk to ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /opt/local/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7f047537a0fe in ThreadWeaver::Weaver::applyForWork (this=, th=0xa7, wasBusy=true) at
[digikam] [Bug 451802] GPX files fails to load
https://bugs.kde.org/show_bug.cgi?id=451802 --- Comment #6 from Maik Qualmann --- It's certainly a possibility, but there's an easier way. Maik -- You are receiving this mail because: You are watching all bug changes.
[OCS] [Bug 450668] store.kde.org seems to be down
https://bugs.kde.org/show_bug.cgi?id=450668 a...@notowany.pl changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #5 from a...@notowany.pl --- Still not working Endevouros: Plasma 5.24.3 Mar 23 20:18:00 Piend plasmashell[655]: trying to show an empty dialog Mar 23 20:18:01 Piend kwin_x11[614]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 29372, resource id: 48234682, major code: 73 (GetImage), > Mar 23 20:18:01 Piend kwin_x11[614]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 29373, resource id: 48234682, major code: 73 (GetImage), > Mar 23 20:18:01 Piend kwin_x11[614]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 29374, resource id: 48234682, major code: 73 (GetImage), > Mar 23 20:18:01 Piend kwin_x11[614]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 29375, resource id: 48234682, major code: 73 (GetImage), > Mar 23 20:18:01 Piend kwin_x11[614]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 29376, resource id: 48234682, major code: 73 (GetImage), > Mar 23 20:18:05 Piend plasmashell[655]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:366: Unable to assign [undefined] to > Mar 23 20:18:05 Piend systemd[527]: Started Ustawienia systemowe - Ustawienia systemowe. Mar 23 20:18:05 Piend plasmashell[655]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:366: Unable to assign [undefined] to > Mar 23 20:18:06 Piend systemsettings[1418]: file:///usr/lib/qt/qml/org/kde/kirigami.2/ApplicationItem.qml:151:9: QML Shortcut: Shortcut: Only binding to one of > Mar 23 20:18:06 Piend systemsettings[1418]: file:///usr/lib/qt/qml/org/kde/kirigami.2/ApplicationItem.qml:147:9: QML Shortcut: Shortcut: Only binding to one of > Mar 23 20:18:06 Piend systemsettings[1418]: file:///usr/lib/qt/qml/org/kde/kirigami.2/PageRow.qml:674:5: QML Shortcut: Shortcut: Only binding to one of multiple> Mar 23 20:18:06 Piend systemsettings[1418]: file:///usr/lib/qt/qml/org/kde/kirigami.2/PageRow.qml:670:5: QML Shortcut: Shortcut: Only binding to one of multiple> Mar 23 20:18:06 Piend systemsettings[1418]: QQmlEngine::setContextForObject(): Object already has a QQmlContext Mar 23 20:18:06 Piend systemsettings[1418]: file:///usr/lib/qt/qml/org/kde/kirigami.2/ApplicationItem.qml:151:9: QML Shortcut: Shortcut: Only binding to one of > Mar 23 20:18:06 Piend systemsettings[1418]: file:///usr/lib/qt/qml/org/kde/kirigami.2/ApplicationItem.qml:147:9: QML Shortcut: Shortcut: Only binding to one of > Mar 23 20:18:06 Piend systemsettings[1418]: file:///usr/lib/qt/qml/org/kde/kirigami.2/PageRow.qml:674:5: QML Shortcut: Shortcut: Only binding to one of multiple> Mar 23 20:18:06 Piend systemsettings[1418]: file:///usr/lib/qt/qml/org/kde/kirigami.2/PageRow.qml:670:5: QML Shortcut: Shortcut: Only binding to one of multiple> Mar 23 20:18:06 Piend kwin_x11[614]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31236, resource id: 58720268, major code: 18 (ChangePropert> Mar 23 20:18:06 Piend plasma-discover[1430]: qrc:/qml/DiscoverWindow.qml:116:19: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated> Mar 23 20:18:06 Piend plasma-discover[1430]: file:///usr/lib/qt/qml/org/kde/kirigami.2/PageRow.qml:674:5: QML Shortcut: Shortcut: Only binding to one of multipl> Mar 23 20:18:06 Piend plasma-discover[1430]: file:///usr/lib/qt/qml/org/kde/kirigami.2/PageRow.qml:670:5: QML Shortcut: Shortcut: Only binding to one of multipl> Mar 23 20:18:06 Piend plasma-discover[1430]: QQmlContext: Cannot set context object on invalid context. Mar 23 20:18:06 Piend plasma-discover[1430]: QQmlComponent: Cannot create a component in an invalid context Mar 23 20:18:06 Piend kwin_x11[614]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31630, resource id: 16790212, major code: 3 (GetWindowAttri> Mar 23 20:18:06 Piend kwin_x11[614]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 31631, resource id: 16790212, major code: 14 (GetGeometry> Mar 23 20:18:06 Piend kwin_x11[614]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31653, resource id: 56623127, major code: 18 (ChangePropert> Mar 23 20:18:09 Piend systemsettings[1418]: QQmlEngine::setContextForObject(): Object already has a QQmlContext Mar 23 20:18:09 Piend systemsettings[1418]: file:///usr/lib/qt/qml/QtQuick/Controls.2/org.kde.desktop/ScrollView.qml:85:25: QML ScrollBar: Binding loop detected> Mar 23 20:18:09 Piend systemsettings[1418]: file:///usr/lib/qt/qml/org/kde/kirigami.2/ApplicationItem.qml:151:9: QML Shortcut: Shortcut: Only binding to one of > Mar 23 20:18:09 Piend systemsettings[1418]:
[Spectacle] [Bug 431915] Rectangular region: resizing with keyboard shortcuts doesn't work properly
https://bugs.kde.org/show_bug.cgi?id=431915 --- Comment #4 from Nate Graham --- You can submit that patch at https://invent.kde.org/graphics/spectacle/-/merge_requests. To learn how, see https://community.kde.org/Infrastructure/GitLab#Submitting_a_Merge_Request -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451802] GPX files fails to load
https://bugs.kde.org/show_bug.cgi?id=451802
--- Comment #5 from Kristian Karl ---
Inserting this code after
https://invent.kde.org/graphics/digikam/-/blob/master/core/utilities/geolocation/geoiface/tracks/trackreader.cpp#L332
seems to be one solution to the problem.
if (xml.name() == QLatin1String("extensions"))
{
do {
xml.readNext();
}
while (!(xml.tokenType() == QXmlStreamReader::EndElement && xml.name() ==
QLatin1String("extensions")) && !xml.hasError()) ;
continue;
}
Also, I don't think this code is used anymore?
https://invent.kde.org/graphics/digikam/-/blob/master/core/utilities/geolocation/geoiface/tracks/trackreader.cpp#L147-290
--
You are receiving this mail because:
You are watching all bug changes.
