[valgrind] [Bug 419054] Unhandled syscall getcpu on arm32
https://bugs.kde.org/show_bug.cgi?id=419054 Mark Wielaard changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||m...@klomp.org --- Comment #1 from Mark Wielaard --- Thanks for the patch, works. Applied as: commit b8a9da078b21be2d110adbd563e1c07fc3f8d74b (HEAD -> master) Author: Igor Nunes Date: Fri Mar 20 17:12:13 2020 + Enable getcpu on arm 32 https://bugs.kde.org/show_bug.cgi?id=419054 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 464680] Show issues caused by memory policies like selinux deny_execmem
https://bugs.kde.org/show_bug.cgi?id=464680 Mark Wielaard changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Mark Wielaard --- commit f32cc294e363f9ea953b22cddcb290954725d83b Author: Mark Wielaard Date: Sun Jan 22 23:18:18 2023 +0100 Propagate memory allocation failure to out_of_memory_NORETURN Provide the user with a hint of what caused an out of memory error. And explain that some memory policies, like selinux deny_execmem might cause Permission denied errors. Add an err argument to out_of_memory_NORETURN. And change am_shadow_alloc to return a SysRes (all three callers were already checking for errors and calling out_of_memory_NORETURN). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 393062] Reading build-id ELF note through phdrs triggers "debuginfo reader: ensure_valid failed"
https://bugs.kde.org/show_bug.cgi?id=393062 Mark Wielaard changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Mark Wielaard --- The original issue was fixed by: commit f1f543a224eec5afd8cfddea70c1307ed0a20c55 Author: Mark Wielaard Date: Mon Apr 16 16:53:56 2018 +0200 Don't read build-id ELF Note in .debug file through phdrs. Bug #393062 - Reading build-id ELF note through phdrs triggers "debuginfo reader: ensure_valid failed" Skip the phdrs when we have to search the shdrs. In separate .debug files the phdrs might not be valid (they are a copy of the main ELF file) and might trigger assertions when getting image notes based on them. The report in comment #2 seems unrelated and there has been no follow-up on questions about platform. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398649] New s390x z13 support doesn't build with older gcc/binutils
https://bugs.kde.org/show_bug.cgi?id=398649 Mark Wielaard changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED --- Comment #6 from Mark Wielaard --- (In reply to Julian Seward from comment #5) > What's the situation here? Do we want/need to fix this? Current distros do support z13 just fine. This was an issue with rhel/centos6 and older rhel/centos7 (which is about to be deprecated too). I don't think we want to workaround this anymore but will just tell people they need a more modern toolchain if they are building valgrind for s390x. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 444487] hginfo test detects an extra lock inside data symbol "_rtld_local"
https://bugs.kde.org/show_bug.cgi?id=87 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||philippe.waroquiers@skynet. ||be --- Comment #1 from Mark Wielaard --- This comes from pthread_create: (gdb) monitor accesshistory 0x4035a58 ==30485== ---Thread-Announcement-- ==30485== ==30485== Thread #1 is the program's root thread ==30485== ==30485== ---Thread-Announcement-- ==30485== ==30485== Thread #1 is the program's root thread ==30485== read of size 4 at 0x4035A58 by thread #1 tid 1 ==30485== Locks held: none ==30485==at 0x48FFC72: lll_mutex_unlock_optimized (pthread_mutex_unlock.c:43) ==30485==by 0x48FFC72: __pthread_mutex_unlock_usercnt (pthread_mutex_unlock.c:68) ==30485==by 0x484BD2C: mutex_unlock_WRK (hg_intercepts.c:1182) ==30485==by 0x484FF3E: pthread_mutex_unlock (hg_intercepts.c:1200) ==30485==by 0x4011CDD: _dl_allocate_tls_init (dl-tls.c:620) ==30485==by 0x48FBCFE: allocate_stack (allocatestack.c:423) ==30485==by 0x48FBCFE: pthread_create@@GLIBC_2.34 (pthread_create.c:650) ==30485==by 0x484E5D4: pthread_create_WRK (hg_intercepts.c:445) ==30485==by 0x484FAF5: pthread_create@* (hg_intercepts.c:478) ==30485==by 0x40125D: main (hg01_all_ok.c:41) So I propose to run the test with --ignore-thread-creation=yes diff --git a/gdbserver_tests/hginfo.vgtest b/gdbserver_tests/hginfo.vgtest index 5d00e1e21..0ea8ab4b3 100644 --- a/gdbserver_tests/hginfo.vgtest +++ b/gdbserver_tests/hginfo.vgtest @@ -1,7 +1,7 @@ # test helgrind monitor command # test 'v.info location' monitor command prog: ../helgrind/tests/hg01_all_ok -vgopts: --tool=helgrind --vgdb=yes --vgdb-error=0 --vgdb-prefix=./vgdb-prefix-hginfo -q +vgopts: --tool=helgrind --ignore-thread-creation=yes --vgdb=yes --vgdb-error=0 --vgdb-prefix=./vgdb-prefix-hginfo -q prereq: test -e gdb.eval stdout_filter: filter_make_empty stderr_filter: filter_stderr $ perl tests/vg_regtest gdbserver_tests/hginfo.vgtest hginfo: valgrind --tool=helgrind --ignore-thread-creation=yes --vgdb=yes --vgdb-error=0 --vgdb-prefix=./vgdb-prefix-hginfo -q ./../helgrind/tests/hg01_all_ok (progB: ./gdb --quiet -l 60 --nx ../helgrind/tests/hg01_all_ok) == 1 test, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466454] Vulkan and OpenGL windows not being created properly with fraction scale factors
https://bugs.kde.org/show_bug.cgi?id=466454 --- Comment #22 from Mark Richardson --- (In reply to Zamundaaa from comment #21) > > However on native wayland, the max extant is always 16k. not what I would > > call optimal usage > I thought this was obvious but maybe I didn't describe it well: When picking > a swapchain size, Vulkan requires you to do > > extends = min(maxExtends, max(desiredSize, minExtends)) > which will handle this and any other situations with restricted size options > correctly. Ah, thats makes sense now. Now there is only the little matter of every single other 3D game not working. I know the usual attitude of Wayland developers when considering changing protocol/compositor behaviour vs. every single application being written wrong is to usually stick to thier guns, But I think kwin would really benefit from being able to display the windows of the tens of thousands of games already out there, and I belive the best ssolution for the users of kwin is for it to not return different swapchain extants depending on the scaling factor. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466454] Vulkan and OpenGL windows not being created properly with fraction scale factors
https://bugs.kde.org/show_bug.cgi?id=466454 --- Comment #20 from Mark Richardson --- Created attachment 158165 --> https://bugs.kde.org/attachment.cgi?id=158165=edit xwayland_swapchain_kwin_150scale -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466454] Vulkan and OpenGL windows not being created properly with fraction scale factors
https://bugs.kde.org/show_bug.cgi?id=466454 --- Comment #19 from Mark Richardson --- (In reply to David Edmundson from comment #18) > > I don't see a cross platform way to set the swapchain size, unless kwin > > gives a surface of either 1px-16384px like it does on wayland, or exactly > > matching the window size like on xwayland with no scaling active. > > We've got a few crossed paths: > > - kwin isn't setting this surface capabilities sizes, this all comes from > mesa and this 721px values is based on the current window size > we can change mesa. > > - from the output it strongly suggests kwin is resizing the window (which > is a silly rounding bug we need to fix) but that would be the same if the > user resized things by dragging a corner and resized a window > > The crossplatform way to do things is to make sure clients build your > swapchain size is also based on the *current* window size, watching for the > window being resized as external factors can resize things. All SDL window queries say the window size is 1280x720 with a min/max swapchain extant of 1280x721 to 1280x721. SDL_GetWindowSize(); SDL_GetWindowSizeInPixels(); SDL_Vulkan_GetDrawableSize(); However on native wayland, the max extant is always 16k. not what I would call optimal usage. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466454] Vulkan and OpenGL windows not being created properly with fraction scale factors
https://bugs.kde.org/show_bug.cgi?id=466454 --- Comment #17 from Mark Richardson --- (In reply to Zamundaaa from comment #15) > > What specific game and Proton version did you use? This is not happening for > me and afaict from the dxvk code, it's handling the min/max surface extends > correctly. I can reproduce this issue with thedarkmod, a linux native opengl game, under virtualbox with both SVGA3D and llvmpipe gl drivers -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466454] Vulkan and OpenGL windows not being created properly with fraction scale factors
https://bugs.kde.org/show_bug.cgi?id=466454 --- Comment #16 from Mark Richardson --- (In reply to Zamundaaa from comment #15) > (In reply to Mark Richardson from comment #13) > > What can/should an app do about being lied to about the window size? > You need to query the surface capabilities with > vkGetPhysicalDeviceSurfaceCapabilitiesKHR, and choose a swapchain size > that's bigger than or equal to the minimum, and smaller than or equal to the > maximum swapchain extends. on wayland, that could be anything from 1-16k, on xwayland its a specific size, that sometimes doesn't match the window size depending on the scaling setting for kwin. I don't see a cross platform way to set the swapchain size, unless kwin gives a surface of either 1px-16384px like it does on wayland, or exactly matching the window size like on xwayland with no scaling active. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466454] Vulkan and OpenGL windows not being created properly with fraction scale factors
https://bugs.kde.org/show_bug.cgi?id=466454 --- Comment #13 from Mark Richardson --- (In reply to David Edmundson from comment #11) > I strongly suspect our window is configured to the 1280x721size; at which > point it's partly client side problems for not handling that correctly. > Turning a harmless though non-ideal quirk into a user-breakage. What can/should an app do about being lied to about the window size? And only under certain circumstances? All An app can do is request a window of a given size and try to create a swapchain of that size. For native wayland windows, the min/max is always 1-16k, so its fine, and under xwayland it should be the same, or match exactly like it usually does, otherwise there's nothing you can do without writing platform specific code. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466454] Vulkan and OpenGL windows not being created properly with fraction scale factors
https://bugs.kde.org/show_bug.cgi?id=466454 --- Comment #12 from Mark Richardson --- (In reply to David Edmundson from comment #10) > Can you confirm that "X applications scale themselves" setting is currently > checked, and that unchecking it avoids the problem? makes no difference -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 468556] Build failure for vgdb
https://bugs.kde.org/show_bug.cgi?id=468556 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED CC||m...@klomp.org --- Comment #1 from Mark Wielaard --- Sigh, Solaris only got pipe2 in 11.4. I tried to fix it with: commit 932332e660a458e51068937130d557fb4acc6630 Author: Mark Wielaard Date: Sun Apr 16 13:15:03 2023 +0200 Use pipe in vgdb if system doesn't have pipe2 Add a configure check for pipe2. If it isn't available use pipe and fcntl F_SETFD FD_CLOEXEC in vgdb.c. https://bugs.kde.org/show_bug.cgi?id=468556 But don't have access to a Solaris setup -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466454] Vulkan and OpenGL windows not being created properly with fraction scale factors
https://bugs.kde.org/show_bug.cgi?id=466454 --- Comment #9 from Mark Richardson --- testing with the latest tumbleweed under virtualbox shows the same problem with both llvmpipe and SVGA3D GL drivers. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 464671] Default glibc suppression shouldn't use @GLIBC_VERSION@ anymore with glibc >= 2.34
https://bugs.kde.org/show_bug.cgi?id=464671 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #7 from Mark Wielaard --- Sorry I didn't look at this earlier. The original commit that adapted things to the glibc 2.34 naming change did say: The same could be done for the glibc-2.X.supp.in file, but hasn't yet because it looks like most suppressions in that file are obsolete. And some of those suppressions are horribly broad. Is this just for strcmp in ld.so? In that case the intercept in shared/vg_replace_strmem.c should in theory fix that. But it looks like it is too early. Which means we might want to create a hardwire for it in coregrind/m_redir.c -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 467036] Add time cost statistics for Regtest
https://bugs.kde.org/show_bug.cgi?id=467036 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED CC||m...@klomp.org Status|REPORTED|RESOLVED --- Comment #1 from Mark Wielaard --- Nice idea. I did had to tweak the patch a bit to make the dashes match up again. Pushed as: commit f7ddfc7cfd750978f405d7e2be8f76412fd1653d (HEAD -> master, origin/master, origin/HEAD) Author: Mark Wielaard Date: Sat Apr 15 00:59:26 2023 +0200 Regtest: add time cost statistics Add running time of each (sub) directory in seconds https://bugs.kde.org/show_bug.cgi?id=467036 Contributed-by: Jojo R Thanks -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 467714] fdleak_* and rlimit tests fail when parent process has more than 64 descriptors opened.
https://bugs.kde.org/show_bug.cgi?id=467714 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Mark Wielaard --- commit 16be0ca4ba53154642bd45e6aa60ffba57369a0c Author: Mark Wielaard Date: Sat Apr 15 00:13:57 2023 +0200 tests fdleak.h close all open file descriptors > 2 Use sysconf (_SC_OPEN_MAX) to find the upper limit. Or use 1024 if that fails. https://bugs.kde.org/show_bug.cgi?id=467714 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 467839] Gdbserver: Improve compatibility of library directory name
https://bugs.kde.org/show_bug.cgi?id=467839 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Mark Wielaard --- I never saw such a system, but this should also work fine for existing systems. Applied as: commit fb6fbe4e8446ec7dd4a01662dbefc48f9349160b Author: Mark Wielaard Date: Sat Apr 15 00:00:36 2023 +0200 gdbserver_tests: Improve compatibility of library directory name Some linux os make softlink from customized directory like lib64xxx into standard system lib64 directory. https://bugs.kde.org/show_bug.cgi?id=467839 Contributed-by: JojoR -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 374814] VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting
https://bugs.kde.org/show_bug.cgi?id=374814 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #2 from Mark Wielaard --- (In reply to Greg from comment #1) > Created attachment 157914 [details] > The output file from valgrind when it crashed the 2nd time > > Im writing a game, and before the code for generating and copying part of > the 2d array of enums worked fine, but it started erroring, then valgrind > crashed and I can't run it again. There is an Invalid write in your program before the internal valgrind issue. Please resolve that error first. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 459392] warning: The macro `AC_PROG_CC_C99' is obsolete
https://bugs.kde.org/show_bug.cgi?id=459392 Mark Wielaard changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||m...@klomp.org Resolution|--- |FIXED --- Comment #4 from Mark Wielaard --- This has been fixed by: commit 092d9085442a2519d7b1bdbc79334a307ad55574 Author: Mark Wielaard Date: Sat Jan 28 21:11:35 2023 +0100 configure.ac: Update AC_PROG_CC checks AM_PROG_CC_C_O has been obsolete since automake 1.14. AC_PROG_CC does the same check. With autoconf 2.70 we must use AC_PROG_CC (which will check for c11 and c99), for earlier versions we'll use AC_PROG_CC_C99. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 464609] Valgrind memcheck should support Linux pidfd_open
https://bugs.kde.org/show_bug.cgi?id=464609 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED CC||m...@klomp.org Status|REPORTED|RESOLVED --- Comment #2 from Mark Wielaard --- Thank you, looks good. Applied as: commit d387566dd7dbb2ebe6fea5bfb4b2353bd5ab86ba Author: Earl Chew Date: Fri Apr 14 22:56:16 2023 +0200 Support Linux syscall 434 pidfd_open -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 434057] Add stdio mode to valgrind's gdbserver
https://bugs.kde.org/show_bug.cgi?id=434057 Mark Wielaard changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #29 from Mark Wielaard --- commit 0432ce486d61f84f6fcbeab0d812bb1f61c57561 Author: Alexandra Petlanova Hajkova Date: Thu Mar 3 04:46:03 2022 -0500 vgdb: implement the extended-remote protocol Executing vgdb --multi makes vgdb talk the gdb extended-remote protocol. This means that the gdb run command is supported and vgdb will start up the program under valgrind. Which means you don't need to run gdb and valgrind from different terminals. Also vgdb keeps being connected to gdb after valgrind exits. So you can easily rerun the program with the same breakpoints in place. vgdb now implements a minimal gdbserver that just recognizes a few extended-remote protocol packets. Once it starts up valgrind it sets up noack and qsupported then it will forward packets between gdb and valgrind gdbserver. After valgrind shutsdown it resumes handling gdb packets itself. https://bugs.kde.org/show_bug.cgi?id=434057 Co-authored-by: Mark Wielaard -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466454] Vulkan and OpenGL windows not being created properly with fraction scale factors
https://bugs.kde.org/show_bug.cgi?id=466454 --- Comment #8 from Mark Richardson --- Just tested ubuntu 23.04 beta, absolutely no problems with any scaling factors on gnome/whatever they are using. This is solely a Kwin problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466454] Vulkan and OpenGL windows not being created properly with fraction scale factors
https://bugs.kde.org/show_bug.cgi?id=466454 --- Comment #7 from Mark Richardson --- Still happens on Plasma 5.27.4, is anyone looking into this? I would like to continue using Linux and KDE, and am more than willing to help test images and builds as long as this bug isn't going to rot or be closed as WONTFIX. This seems like the kind of bug that is going to get written off and ignored as a edge case, until a seemingly unrelated DRM/wayland change happens, followed by a panicked and embarrasing rush to haphazardly fix the issue as half the userbase can't see any of thier windows in a future release. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 434057] Add stdio mode to valgrind's gdbserver
https://bugs.kde.org/show_bug.cgi?id=434057 Mark Wielaard changed: What|Removed |Added Status|REPORTED|ASSIGNED Assignee|jsew...@acm.org |m...@klomp.org Ever confirmed|0 |1 --- Comment #28 from Mark Wielaard --- (In reply to Alexandra Hajkova from comment #27) > Created attachment 158030 [details] > patch > > this version updates: > - fix Darwin compilation > - Correct vargv arguments, last element should be NULL > - cleanup_fifos_and_shared_mem > - read_from_gdb_write_to_pid let gdb know it there was an error writing This looks good. I like to integrate it now. I'll fix up the Author, the commit message and add a NEWS entry. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 434057] Add stdio mode to valgrind's gdbserver
https://bugs.kde.org/show_bug.cgi?id=434057 --- Comment #25 from Mark Wielaard --- (In reply to Tom Tromey from comment #22) > (In reply to Paul Floyd from comment #21) > > > I also tried to make the startup even easier and after searching a bit and > > getting some info on SO I came up with > > I don't know the exact problem here -- I don't use "extended-remote" much > if at all The basic difference between target remote and target extended-remote is whether the target can (re)start the program. Basically with target remote gdb connects to an already running/starting program and the target disconnects when the program ends, while with target extended-remote gdb connects to a target that can (re)start a program and keeps connected to the target even after to program ends, so it can restart the program or run another. > -- but we could write a new "target valgrind" command in Python > (shipped with valgrind) that automates some of this. Doing it as a python script is an interesting idea. The next valgrind will ship with some gdb python scripts already. The question is how to auto-load it when gdb starts up. > > eval "set remote exec-file %s", $programname > > Like this bit could be done automatically. > Though it occurs to me that it might be even nicer to give > gdb some mode like "gdbserver but we know it shares the filesystem", > so that "remote exec-file" and "sysroot" aren't needed at all. Yes, that plus a way to share the tty or have stdin/stdout redirected to some alternative file descriptors (currently they are used by the pipe to talk the so you cannot directly get input/output to/from the program) https://sourceware.org/bugzilla/show_bug.cgi?id=28916 > > Again I don't know how to do it, but this gdb function would be nicer if > > there's a way to pass args to the vgdb line to pass on to valgrind. > > I would have thought this was handled by extended-remote? Unless you mean > some kind of valgrind-specific args, not args to the inferior? > > The latter could be done by the putative "target valgrind" easily - it could > parse its own arguments and do whatever it likes. The idea is that any arguments passed to vgdb --vargs will be passed to valgrind when it starts up. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 434057] Add stdio mode to valgrind's gdbserver
https://bugs.kde.org/show_bug.cgi?id=434057 --- Comment #24 from Mark Wielaard --- (In reply to Paul Floyd from comment #21) > It seems quite intermittent. I've only reproduced it once, and without > debug/verbose. Too bad, those are the worst bugs to debug. > I had a very quick look on Illumos and Darwin and Illumos has a man page for > accept4 but not Darwin. Does that also mean it doesn't build on Darwin? We can use accept on Darwin in that case. It just means it will possibly leak a file descriptor on exec. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 434057] Add stdio mode to valgrind's gdbserver
https://bugs.kde.org/show_bug.cgi?id=434057 --- Comment #20 from Mark Wielaard --- I wonder if there is still a timing issue if it works with extra verbose/debug output. We tried to remove any explicit waiting/spinning. Could you show a full session (gdb command line plus arguments and gdb prompts you did) where things fail, and where you added the extra -v and -d to make it work? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 434057] Add stdio mode to valgrind's gdbserver
https://bugs.kde.org/show_bug.cgi?id=434057 --- Comment #16 from Mark Wielaard --- Thanks, last patch looks pretty nice. I threw it at the try builder and it at least compiles cleanly: https://builder.sourceware.org/buildbot/#/changes/23263 That of course is all different GNU/Linux setups, maybe Paul can try it on FreeBSD. P.S. It is probably more accurate to make you the main author and add me as Co-authored-by: -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468075] New: Closing Investment Accounts causes program crash
https://bugs.kde.org/show_bug.cgi?id=468075 Bug ID: 468075 Summary: Closing Investment Accounts causes program crash Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: markm10...@gmail.com Target Milestone: --- SUMMARY Closing Investment account causes program crash NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports I have removed all securities from an investment account and sub-accounts and added the same securities to a new investment account, with similar sub-accounts. I used the entry of a symbol for security without a name to ensure same security was added to the new sub-accounts. I tried to close the various sub-accounts and all attempts to any of the sub-accounts result in program crashing. I get a segmentation fault. I can successfully re-open and re-close non-investment accounts (ie: bank accounts) STEPS TO REPRODUCE 1. Go to Security account or investment sub-account 2. Make sure there are no balances or schedules for items 3. Close account OBSERVED RESULT Program crashes EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 (built against 5.15.8) ADDITIONAL INFORMATION System: Kernel: 5.15.0-69-generic x86_64 bits: 64 compiler: gcc v: 11.3.0 Desktop: Cinnamon 5.6.8 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 434057] Add stdio mode to valgrind's gdbserver
https://bugs.kde.org/show_bug.cgi?id=434057
--- Comment #12 from Mark Wielaard ---
(In reply to Paul Floyd from comment #11)
> When I saw this
>
> +/* For accept4 and execvpe. */
> +#define _GNU_SOURCE
> #include "vgdb.h"
>
> I had a bit of a bad feeling, which was confirmed when I tried to build.
>
> vgdb.c:1185:16: warning: implicit declaration of function 'execvpe' is
> invalid in C99 [-Wimplicit-function-declaration]
> res = execvpe ("valgrind",
>^
> vgdb.c:1186:35: error: use of undeclared identifier 'environ'
> val_argv, environ);
> ^
Aha, yeah execvpe and environ are GNU extensions.
But since we aren't really handling changes in environment at the moment
(although there is some code there in case gdb tells us about it) we can use
execvp for now.
I see accept4 (which is used to set SOCK_CLOEXEC) is also a GNU extension. But
that does also work on other systems?
> I tried plain execvp (since environ isn't uyet being used) and I could get
> as far as a gdb prompt but couldn't do much, getting errors like
>
> relaying data between gdb and process 57204
> Protocol error: qXfer:features:read (target-features) conflicting enabled
> responses.
>
> Cannot find bounds of current function
That is interesting. We have an XXX for propagating the qSupported response and
it might be this is caused by that missing.
> + DEBUG(1, "packed recieved: '%s'\n", buf);
> ^^^
> That should be "packet received"
Thanks, fixed.
> Will the option "--launched-with-multi" ever be used by humans? If not no
> worry, but if it is then it should be more self explanatory.
--launched-with-multi is only supposed to be used by vgdb when running
valgrind, so it is only documented with valgrind --help-debug:
--launched-with-multi=no|yes valgrind launched in vgdb multi mode [no]
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 466454] Vulkan and OpenGL windows not being created properly with fraction scale factors
https://bugs.kde.org/show_bug.cgi?id=466454 --- Comment #4 from Mark Richardson --- (In reply to Mark Richardson from comment #3) > None of this happens on the lavapipe vulkan driver, min/max extant always > matches the window size exactly on Xorg and XWayland, and always returns min > of (1,1) and max of (16384,16384) on wayland actually, I had the scale set wrong when I tested lvp, the problem happens with xWayland windows on lvp with 150% and 250% scaling just like with RADV. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466454] Vulkan and OpenGL windows not being created properly with fraction scale factors
https://bugs.kde.org/show_bug.cgi?id=466454 --- Comment #3 from Mark Richardson --- After even more testing this appears to only happen with XWayland windows and a scale set to 150%, or 250%, no other fractional scale factors trigger the disconnect between the window size, and the vulkan surface extent. Just to be clear what's happening, with XWayland windows on kwin_wayland and scale values of 150% or 250%, vkGetPhysicalDeviceSurfaceCapabilitiesKHR returns a min and max extent of (1280,721) on a window of size (1280,720). This breaks most Vulkan apps, including almost every Steam/Proton game. The solution can not be to create the swapchain based on either the min/max extent instead of the window size, because with SDL2's native Wayland backend, the min/max reported extants are always (1,1),(16384,16384). This still happens on the latest KDE(opensuse tumbleweed), with the stock amdgpu kernel driver with RADV, and started on Plasma 5.26, before the new fractional scaling protocol. None of this happens on the lavapipe vulkan driver, min/max extant always matches the window size exactly on Xorg and XWayland, and always returns min of (1,1) and max of (16384,16384) on wayland -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 467714] fdleak_* and rlimit tests fail when parent process has more than 64 descriptors opened.
https://bugs.kde.org/show_bug.cgi?id=467714
--- Comment #2 from Mark Wielaard ---
Tested with:
#include
#include
int main (int argc, char *const argv[])
{
for (int i = 0; i < 100; ++i)
dup (1);
execvp (argv[1], argv + 1);
exit (1);
}
gcc -o dup100 dup100.c
./dup100 valgrind --track-fds=yes /bin/true
==673839== FILE DESCRIPTORS: 103 open (3 std) at exit.
==673839== Open file descriptor 102: /dev/pts/5
==673839==
[...]
./dup100 perl tests/vg_regtest none/tests/fdleak*vgtest
all fail
with patch all succeed
\o/
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 467714] fdleak_* and rlimit tests fail when parent process has more than 64 descriptors opened.
https://bugs.kde.org/show_bug.cgi?id=467714 Mark Wielaard changed: What|Removed |Added Assignee|jsew...@acm.org |m...@klomp.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||m...@klomp.org --- Comment #1 from Mark Wielaard --- Created attachment 157527 --> https://bugs.kde.org/attachment.cgi?id=157527=edit close all file descriptors > 2 with CLOSE_INHERITED_FDS -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467298] New: kwin_wayland segfaults in KWaylandServer::OutputInterface::handle() on screen off when system is locked
https://bugs.kde.org/show_bug.cgi?id=467298 Bug ID: 467298 Summary: kwin_wayland segfaults in KWaylandServer::OutputInterface::handle() on screen off when system is locked Classification: Plasma Product: kwin Version: 5.27.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: wolfendea...@gmail.com Target Milestone: --- Created attachment 157244 --> https://bugs.kde.org/attachment.cgi?id=157244=edit kwin_wayland lockscreen crash stacktrace SUMMARY `kwin_wayland` segfaults in `KWaylandServer::OutputInterface::handle()` if computer sits on the lock screen for the amount of time set in `System Settings > Power Management > Energy Saving > On AC Power > Screen Energy Saving`. This happens sometimes on closing and opening the lid of the laptop as well, but it's less frequent whereas the steps described below reproduce the problem 100% of the time for me. Stack trace of dumped core is in attached file `kwin_wayland-lockscreen-crash-stacktrace.txt`. Backtrace from `debuginfod` and `gdb`: ``` #0 0x7f65999d2f14 in KWaylandServer::OutputInterface::handle() const () at /usr/lib/libkwin.so.5 #1 0x7f65999c59c0 in () at /usr/lib/libkwin.so.5 #2 0x7f65999c5d5a in () at /usr/lib/libkwin.so.5 #3 0x7f6597ebea71 in () at /usr/lib/libQt5Core.so.5 #4 0x7f65997c495e in KWin::Output::setState(KWin::Output::State const&) () at /usr/lib/libkwin.so.5 #5 0x7f659997ccba in KWin::DrmOutput::updateDpmsMode(KWin::Output::DpmsMode) () at /usr/lib/libkwin.so.5 #6 0x7f659997dd64 in KWin::DrmOutput::setDrmDpmsMode(KWin::Output::DpmsMode) () at /usr/lib/libkwin.so.5 #7 0x7f6597ebea71 in () at /usr/lib/libQt5Core.so.5 #8 0x7f6597ec0fcf in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #9 0x7f6597eb1b56 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #10 0x7f6597578b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #11 0x7f6597e8df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #12 0x7f6597ed84b3 in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #13 0x7f6597ed8962 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #14 0x55c6dfaf95f2 in () #15 0x7f6597e866ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #16 0x7f6597e91219 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #17 0x55c6dfa16242 in () #18 0x7f6596e3c790 in () at /usr/lib/libc.so.6 #19 0x7f6596e3c84a in __libc_start_main () at /usr/lib/libc.so.6 #20 0x55c6dfa17e95 in () ``` STEPS TO REPRODUCE 1. In `System Settings > Power Management > Energy Saving > On AC Power` set a time for `Screen Energy Saving` (mine was set for 30 minutes) 2. (_likely_ optional) On the same page, uncheck `Suspend Session` 3. Lock the machine and let it sit for the time set in step 1 OBSERVED RESULT One of two things happens: 1. Upon entering the correct password on the lock screen, the login prompt it replaced with a button that says "Unlock" that doesn't do anything. 2. Upon waking up the machine the 'The screen locker is broken and unlocking is not possible anymore.` screen is present. For both outcomes, only `sudo loginctl unlock-sessions` in a separate tty is able to restore the session. Once the session is unlocked, all applications have closed (in `journalctl` after the segfault, all services report `kactivitymanagerd[1213]: The Wayland connection broke. Did the Wayland compositor die?` but with the appropriate service name/number). EXPECTED RESULT Able to log back in as normal. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.2-arch1-g14-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 9 6900HS with Radeon Graphics Memory: 38.4 GiB of RAM Graphics Processor: AMD Radeon RX 6700S Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Zephyrus G14 GA402RJ_GA402RJ System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 436413] Warn about realloc of size zero
https://bugs.kde.org/show_bug.cgi?id=436413 --- Comment #21 from Mark Wielaard --- Looks good to me. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466485] Window Decoration Crashes, network and network panel issues
https://bugs.kde.org/show_bug.cgi?id=466485 --- Comment #3 from Mark Rebholz --- Created attachment 157012 --> https://bugs.kde.org/attachment.cgi?id=157012=edit New crash information added by DrKonqi systemsettings (5.26.4) using Qt 5.15.7 fedora 36 plasma 5.26.4 oberer rechter fensterbalken durchsichtig -- Backtrace (Reduced): #4 0x7f9ad64a0e84 in KDecoration2::Decoration::shadow() const () at /lib64/libkdecorations2.so.5 #5 0x7f9ad6035a55 in KDecoration2::Preview::PreviewItem::hoverLeaveEvent(QHoverEvent*) () at /usr/lib64/qt5/qml/org/kde/kwin/private/kdecoration/libkdecorationprivatedeclarative.so #6 0x7f9afee96d68 in QQuickItem::event(QEvent*) () at /lib64/libQt5Quick.so.5 #7 0x7f9b019aed12 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #8 0x7f9b00ca8278 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466485] Window Decoration Crashes, network and network panel issues
https://bugs.kde.org/show_bug.cgi?id=466485 Mark Rebholz changed: What|Removed |Added CC||mark.rebh...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 465707] Menu bar items not working
https://bugs.kde.org/show_bug.cgi?id=465707 --- Comment #4 from Mark Medoff --- Jack I tried full path with appimage. I went to console and did a "whereis" to confirm path for gnome-calculator. I copied that path and pasted it into settings for program. Got the below error when I tried to use calculator from menu bar: [image: image.png] I then ran program from console as you suggested with full path in the settings. Calculator worked fine from menu bar. I then removed the path from the calculator setting and ran again from console. Calculator ran fine without path from menu bar with console. Hope that will help you figure out what the problem is. Mark On Wed, Mar 1, 2023 at 11:13 AM Jack wrote: > https://bugs.kde.org/show_bug.cgi?id=465707 > > Jack changed: > >What|Removed |Added > > > CC| > |ostroffjh@users.sourceforge >||.net > > --- Comment #3 from Jack --- > Just a guess, but try putting in the full path to gnome-calculator. Also, > is > there any console output when you get that error? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463356] Audio indicators are displayed for some flatpaks that aren't running audio
https://bugs.kde.org/show_bug.cgi?id=463356 Mark Duncan changed: What|Removed |Added Version|5.26.4 |5.27.2 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 465707] Menu bar items not working
https://bugs.kde.org/show_bug.cgi?id=465707 --- Comment #2 from Mark Medoff --- I downloaded the latest appimage (408) for linux and tried the calculator from the menu. I now get the below dialog box which I never got before, but calculator still doesn't launch from menu but does when the same command is given in Terminal. [image: image.png] Mark -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466454] New: Vulkan and OpenGL windows not being created properly with fraction scale factors
https://bugs.kde.org/show_bug.cgi?id=466454 Bug ID: 466454 Summary: Vulkan and OpenGL windows not being created properly with fraction scale factors Classification: Plasma Product: kwin Version: 5.27.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: oldkentuckym...@gmail.com Target Milestone: --- Created attachment 156749 --> https://bugs.kde.org/attachment.cgi?id=156749=edit example image Trying to create a window of a given size(ex. 1280x720) results in being given a surface one exaclty 1 pixel too tall (1280x721). Happens only on wayland with amdgpu, on the radeon mesa opengl driver, and both RADV and lavapipe drivers, with fractional scaling factors such as 150%. Does not happen on kwin_x11 nor on wayland with integer scale factors. Was happening on plasma 5.26 before the new fractional scaling protocol merge. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 466172] SIGTRAP crash whenever getaddrinfo call is issued by valgrind
https://bugs.kde.org/show_bug.cgi?id=466172 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #2 from Mark Wielaard --- (In reply to Paul Floyd from comment #1) > This might be fairly tricky to reproduce. I can't reproduce this on a RHEL > 7.9 machine using vas4 ldap. I also am unable to reproduce. It might be helpful to install the glibc debuginfo to get a better idea where the issue comes from. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 465537] Firefox Plasma Integration only works in the live iso, doesn't work after install.
https://bugs.kde.org/show_bug.cgi?id=465537 Mark changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 465537] Firefox Plasma Integration only works in the live iso, doesn't work after install.
https://bugs.kde.org/show_bug.cgi?id=465537 --- Comment #2 from Mark --- I can confirm it works again after the latest set of updates for Neon. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 465435] m_libcfile.c:66 (vgPlain_safe_fd): Assertion 'newfd >= VG_(fd_hard_limit)' failed.
https://bugs.kde.org/show_bug.cgi?id=465435
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #11 from Mark Wielaard ---
(In reply to Paul Floyd from comment #10)
> (In reply to Corentin Noël from comment #9)
>
> > In this case it seems that I'm getting an error on file descriptor
> > duplication so having a errno/errmsg would also help understanding it a bit.
>
> We can't provide anything from errno as we don't have it. Valgrind does not
> link with libc and makes system calls like
>
>SysRes res = VG_(do_syscall3)(__NR_fcntl, fd, cmd, arg);
>
> directly itself.
We cannot use errno (which is indeed a glibc concept), but we can extract the
kernel error from the SysRes with something like:
if (sr_isError (res))
VG_(umsg) ("fcntl error %lu %s\n", sr_Err(res), VG_(strerror)
(sr_Err(res)));
--
You are receiving this mail because:
You are watching all bug changes.
[kmymoney] [Bug 465707] New: Menu bar items not working
https://bugs.kde.org/show_bug.cgi?id=465707 Bug ID: 465707 Summary: Menu bar items not working Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: markm10...@gmail.com Target Milestone: --- SUMMARY Calculator and Report A Bug don't launch from menu bar 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 In settings, I have set gnome-calculator as my default calculator in the program. It will not launch. Help > Report A Bug launches Chrome and then instantly crashes Chrome. STEPS TO REPRODUCE 1. Set gnome-calculator in Settings 2. Click on calculator in Menu Bar 3. OBSERVED RESULT Calculator doesn't launch If I type gnome-calculator in Terminal, Calculator launches as expected. EXPECTED RESULT KMyMoney Menu Bar used to launch Calculator correctly in Linux Mint. It no longer does. Report a bug from help menu used to properly launch Chrome and sent to this site to report bugs. It no longer does. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux Mint 21.1 (available in About System) KDE Plasma Version: KDE Frameworks Version: Version 5.102.0 Qt Version: Version 5.15.8 (built against 5.15.8) ADDITIONAL INFORMATION KMyMoney Version 5.1.3-bff48dab5 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465545] New: Add an option to play new files immediately instead of queue
https://bugs.kde.org/show_bug.cgi?id=465545 Bug ID: 465545 Summary: Add an option to play new files immediately instead of queue Classification: Applications Product: Elisa Version: 22.12.2 Platform: Neon OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: idkwtf2...@outlook.com Target Milestone: --- SUMMARY Double clicking a new music file will add it to the end of the queue instead of playing immediately. An option to play immediately should be added. STEPS TO REPRODUCE 1. Listen to something 2. Double click on something else OBSERVED RESULT New file gets added to the end of the queue. EXPECTED RESULT New file should be played immediately. ADDITIONAL INFORMATION Ad option should be added to achieve this behavior. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 457504] Add LOONGARCH64/Linux port to Valgrind
https://bugs.kde.org/show_bug.cgi?id=457504 --- Comment #14 from Mark Wielaard --- (In reply to Feiyang Chen from comment #12) > Most of these files were introduced by the v4-0104 patch. > I don't know why these empty files are missing :) > Or can I just remove them from my local tree and EXTRA_DIST? If the tests expect no output, then an empty .exp file is needed. You can just git add them to the commit (it looks like you did for most, but not all new .exp files). And they should all be listed under EXTRA_DIST. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 465537] New: Firefox Plasma Integration only works in the live iso, doesn't work after install.
https://bugs.kde.org/show_bug.cgi?id=465537 Bug ID: 465537 Summary: Firefox Plasma Integration only works in the live iso, doesn't work after install. Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: idkwtf2...@outlook.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY *** Firefox Plasma Integration extension doesn't work. Says "Failed to connect to the Native Host". Strange thing: it work in the live iso. STEPS TO REPRODUCE 1. Boot from the live iso, install Browser Integration to Firefox 2. Open Youtube or whatever 3. It works 4. Install the operating system, even from the same iso 5. Install Browser Integration 6. Open Youtube or whatever 7. It doesn't work I tried on my own PC and on a virtual machine within Windows. Same result. The extension only works in the live iso, no longer works after install. OBSERVED RESULT Should work. EXPECTED RESULT Does not work. SOFTWARE/OS VERSIONS Kde Neon downloaded from neon.kde.org: https://files.kde.org/neon/images/user/20230209-0714/neon-user-20230209-0714.iso ADDITIONAL INFORMATION I don't know anything about Linux so I don't know how to troubleshoot this. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 465465] Eviction Emulation in Cachegrind for Detecting Cache Conflicts
https://bugs.kde.org/show_bug.cgi?id=465465 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #6 from Mark Wielaard --- (In reply to Ivica from comment #5) > I created a github mirror of valgrind, and created a patch as a Pull > Request, so it can be reviewed more easily. I sent you an invitation on > GitHub for the repository, so we can perform the review there. Please do make sure that all patches and reviews/comments are also added to this bug or at least posted to the valgrind-developers mailinglist. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 457780] Konsole crashes on launch.
https://bugs.kde.org/show_bug.cgi?id=457780 --- Comment #3 from Mark N Carpenter Jr --- Thanks For pinging this, the issue has been resolved. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 457780] Konsole crashes on launch.
https://bugs.kde.org/show_bug.cgi?id=457780 Mark N Carpenter Jr changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 452758] Valgrind does not read properly DWARF5 as generated by Clang14
https://bugs.kde.org/show_bug.cgi?id=452758 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #49 from Mark Wielaard --- Looks like I never properly closed this. Apologies. All Luboš have been committed and made it into valgrind 3.20.0 commit 026cda6c8111ef6ff79bd5c6e083ab50ccf3ded6 Author: Luboš Luňák Date: Tue Apr 26 13:53:14 2022 +0200 support DW_FORM_addrx3 and DW_FORM_strx3 Apparently these may get used after all with large enough binaries, despite being somewhat tricky with regard to endianess. commit 4bb0164e6b2067376f085452a40137f13436384c Author: Luboš Luňák Date: Mon Apr 25 22:11:27 2022 +0200 implement support for missing DW_LLE_* and DW_RLE_* values commit e95904b99c87606eae1372ee4661e9db03833f08 Author: Luboš Luňák Date: Tue Apr 26 08:35:16 2022 +0200 treat DW_TAG_skeleton_unit like DW_TAG_compile_unit It's basically the same, except for being split-dwarf. Handling it is required e.g. for reading line info. commit d19bbdf1200685ddbb6976cf915fba25f2097162 Author: Luboš Luňák Date: Tue Apr 19 12:20:16 2022 +0200 read dwarf5 DW_FORM_rnglistx and DW_FORM_loclistx The .debug_rnglists/.debug_loclists sections first have a list of offsets and then a list of the actual data that those offsets point to. commit 383f36462fdc25a0e849391cf845e22703a95c08 Author: Luboš Luňák Date: Mon Apr 25 22:11:27 2022 +0200 avoid warning about missing DW_AT_*_base in skip_DIE() Similarly to setup_cu_bases(), DW_FORM_addrx etc. may depend on DW_AT_addr_base etc. that have not been read yet. commit 61dfba4232d795c00603c74e6d0573f2d16641e2 Author: Luboš Luňák Date: Tue Apr 19 11:14:52 2022 +0200 read dwarf5 DW_FORM_addrx* and DW_FORM_strx* as generated by Clang14 DW_FORM_addrx* are offsets into .debug_addr containing addresses. DW_FORM_strx* are offsets into .debug_str_offsets, which contain offsets into .debug_str. Support for these also requires reading DW_AT_addr_base and DW_AT_str_offsets_base before any other field in the abbrev table entry, as those may use this form. commit 61ddbc1fc395c787192e569d8f2238f713bdfd8e Author: Luboš Luňák Date: Tue Apr 19 10:58:44 2022 +0200 read properly unit headers depending on dwarf5 unit_type There may be additional fields that need to be skipped over, otherwise further reading will interpret these incorrectly. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 464969] D language demangling
https://bugs.kde.org/show_bug.cgi?id=464969 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #2 from Mark Wielaard --- coregrind/m_demangle/d-demangle.c provides dlang_demangle it comes from libiberty from which we import the demangler from time to time. See auxprogs/update-demangler. Last import was: commit e0b62fe05559003b731b4d786f3b71e9a66fb94d Author: Mark Wielaard Date: Thu Feb 17 18:35:38 2022 +0100 Update libiberty demangler Update the libiberty demangler using the auxprogs/update-demangler script to gcc git commit d3b2ead595467166c849950ecd3710501a5094d9. This update includes: - libiberty rust-demangle, ignore .suffix - libiberty: Fix infinite recursion in rust demangler - Update copyright years - libiberty: support digits in cpp mangled clone names - d-demangle: properly skip anonymous symbols - d-demangle: remove parenthesis where it is not needed -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 436413] Warn about realloc of size zero
https://bugs.kde.org/show_bug.cgi?id=436413
--- Comment #16 from Mark Wielaard ---
diff --git a/coregrind/m_syswrap/syswrap-freebsd.c
b/coregrind/m_syswrap/syswrap-freebsd.c
index 401a7ba8e..13d3b6bf2 100644
--- a/coregrind/m_syswrap/syswrap-freebsd.c
+++ b/coregrind/m_syswrap/syswrap-freebsd.c
@@ -6468,8 +6468,9 @@ PRE(sys___sysctlbyname)
SET_STATUS_Success(0);
}
- // @todo PJF kern.proc.pathname
- // how is that done? jusr a pid or -1 in the string?
+ // kern.proc.pathname doesn't seem to be handled
+ // makes sense as the pid is variable and using
+ // a MIB is easier than generating a string
// read number of ints specified in ARG2 from mem pointed to by ARG1
PRE_MEM_READ("__sysctlbyname(name)", (Addr)ARG1, ARG2 * sizeof(int));
This part seems unrelated
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 436413] Warn about realloc of size zero
https://bugs.kde.org/show_bug.cgi?id=436413 --- Comment #15 from Mark Wielaard --- ...checking header files and include directives *** File coregrind/m_replacemalloc/vg_replace_malloc.c must not include pub_tool_options.h Only core headers are allowed in non-tool source files. I assume this is for checking info.clo_realloc_zero_bytes_frees This seems to work, but I don't fully understand how. This is part of the vgpreload library, how does that have access to the tools variables? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 436413] Warn about realloc of size zero
https://bugs.kde.org/show_bug.cgi?id=436413 Mark Wielaard changed: What|Removed |Added Attachment #155510|0 |1 is obsolete|| -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 436413] Warn about realloc of size zero
https://bugs.kde.org/show_bug.cgi?id=436413 Mark Wielaard changed: What|Removed |Added Attachment #155503|1 |0 is obsolete|| -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 436413] Warn about realloc of size zero
https://bugs.kde.org/show_bug.cgi?id=436413 Mark Wielaard changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #12 from Mark Wielaard --- (In reply to Paul Floyd from comment #11) > Created attachment 155510 [details] > warn about realloc zero > > fix EXTRA_DIST This looks like the patch from bug #452802 (which has already been applied). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463122] Crash removing mpris engine
https://bugs.kde.org/show_bug.cgi?id=463122 --- Comment #3 from Mark --- Created attachment 155547 --> https://bugs.kde.org/attachment.cgi?id=155547=edit New crash information added by DrKonqi plasmashell (5.26.5) using Qt 5.15.6 As requested, here is the repeated behavior using a supported version of Plasma (5.26.5) -- Backtrace (Reduced): #4 0x7f1317109427 in QHashData::nextNode(QHashData::Node*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 [...] #6 0x7f13194c5716 in Plasma::DataEngine::removeSource(QString const&) () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 [...] #9 0x7f1317ddf893 in QDBusServiceWatcher::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 [...] #11 0x7f1317de068b in QDBusServiceWatcher::qt_metacall(QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 [...] #13 0x7f13172e7b30 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463122] Crash removing mpris engine
https://bugs.kde.org/show_bug.cgi?id=463122 Mark changed: What|Removed |Added CC||mwate...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 464680] New: Show issues caused by memory policies like selinux deny_execmem
https://bugs.kde.org/show_bug.cgi?id=464680 Bug ID: 464680 Summary: Show issues caused by memory policies like selinux deny_execmem Classification: Developer tools Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: m...@klomp.org Target Milestone: --- Created attachment 155524 --> https://bugs.kde.org/attachment.cgi?id=155524=edit Propagate memory allocation failure to out_of_memory_NORETURN Some memory policies, like selinux deny_execmem cause hard to understand error messages. Provide the user with a hint of what caused an out of memory error. And explain that some memory policies, like selinux deny_execmem might cause Permission denied errors. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438943] Update not recognised and re-performed
https://bugs.kde.org/show_bug.cgi?id=438943 --- Comment #5 from Mark Stanton --- (In reply to Nate Graham from comment #4) > Is this still happening to you with Fedora 37? If so we can do a deep-dive > investigation. Sorry for not doing so before. I haven't seen it on F37, nor in fact F36 before that, so I think it would be a fair assumption that it's no longer an issue. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 464185] readlink("/proc/self/exe") failed when debug systemd(pid 1)
https://bugs.kde.org/show_bug.cgi?id=464185 Mark Wielaard changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WAITINGFORINFO --- Comment #6 from Mark Wielaard --- The issue is that you don't seem to have a /proc file system. Please let us know what the systemd people tell you. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 464185] readlink("/proc/self/exe") failed when debug systemd(pid 1)
https://bugs.kde.org/show_bug.cgi?id=464185 --- Comment #3 from Mark Wielaard --- *** Bug 464184 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 464184] readlink("/proc/self/exe") failed when debug systemd(pid 1)
https://bugs.kde.org/show_bug.cgi?id=464184 Mark Wielaard changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||m...@klomp.org --- Comment #1 from Mark Wielaard --- *** This bug has been marked as a duplicate of bug 464185 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 464185] readlink("/proc/self/exe") failed when debug systemd(pid 1)
https://bugs.kde.org/show_bug.cgi?id=464185 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #2 from Mark Wielaard --- (In reply to hguo3 from comment #1) > Is there anything missing in my valgrind? I think this question is really for the systemd project. The problem that you are observing is that the way you are running/starting systemd causes the /proc filesystem not being available. You might look in the systemd bug report https://github.com/systemd/systemd/issues/2187 or ask the systemd project how you are supposed to run/start systemd under valgrind to get proper results. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 460962] KDE Neon install fails to boot when using btrfs
https://bugs.kde.org/show_bug.cgi?id=460962 Mark Penner changed: What|Removed |Added CC||mrpen...@mailbox.org --- Comment #5 from Mark Penner --- I also installed to a btrfs partition and the booting process hung with the same error messages. I fixed it by rebooting into another linux installation on that computer, mounted the partition with neon installed on it, and edited /etc/fstab, changing space_cache to space_cache=v2 in the mount options for both / and /home. I could then reboot into neon with no problems. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451540] Dophin crashes if I try to create a new folder with KDE KIO gdrive
https://bugs.kde.org/show_bug.cgi?id=451540 --- Comment #3 from Mark Nefedov --- Created attachment 155209 --> https://bugs.kde.org/attachment.cgi?id=155209=edit New crash information added by DrKonqi dolphin (22.12.1) using Qt 5.15.7 Dolphin crashes when trying to create new folder in google drive, and network perfomance is not great. (Expreiancing signifigant lag in any operations) -- Backtrace (Reduced): #4 0x7fe9230ed27a in QLineEdit::text() const () from /lib64/libQt5Widgets.so.5 [...] #7 0x7fe923688e55 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib64/libKF5CoreAddons.so.5 #8 0x7fe92368d0bb in KJob::finishJob(bool) () from /lib64/libKF5CoreAddons.so.5 [...] #10 0x7fe923e55906 in KIO::SlaveInterface::error(int, QString const&) () from /lib64/libKF5KIOCore.so.5 #11 0x7fe923e5abd8 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib64/libKF5KIOCore.so.5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451540] Dophin crashes if I try to create a new folder with KDE KIO gdrive
https://bugs.kde.org/show_bug.cgi?id=451540 Mark Nefedov changed: What|Removed |Added CC||mark_nefe...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381819] amd64: unhandled instruction bextr (0x8F 0xEA 0x78 0x10 0xD0 0x8 0x4) from BMI1
https://bugs.kde.org/show_bug.cgi?id=381819 Mark Wielaard changed: What|Removed |Added CC||ikoro...@gmail.com --- Comment #27 from Mark Wielaard --- *** Bug 463992 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 463992] Valgrind fails to run
https://bugs.kde.org/show_bug.cgi?id=463992 Mark Wielaard changed: What|Removed |Added Resolution|--- |DUPLICATE CC||m...@klomp.org Status|REPORTED|RESOLVED --- Comment #1 from Mark Wielaard --- This is a duplicate bug #381819 which contains a possible fix. *** This bug has been marked as a duplicate of bug 381819 *** -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 432895] Cover art sometimes disappears from current track after rating track
https://bugs.kde.org/show_bug.cgi?id=432895 Mark Fraser changed: What|Removed |Added Platform|Other |Ubuntu -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 432895] Cover art sometimes disappears from current track after rating track
https://bugs.kde.org/show_bug.cgi?id=432895 --- Comment #2 from Mark Fraser --- Still seeing this with: KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.3 When it happens, the artwork is embedded. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463122] New: Plasma Crashes When Switching KVM Switch
https://bugs.kde.org/show_bug.cgi?id=463122 Bug ID: 463122 Summary: Plasma Crashes When Switching KVM Switch Classification: Plasma Product: plasmashell Version: 5.25.5 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mwate...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.25.5) Qt Version: 5.15.6 Frameworks Version: 5.98.0 Operating System: Linux 5.19.0-26-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.10 DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: Behavior is very repeatable. KVM switch does not do EDID emulation, and is connected to a DP MST hub. When switching back to machine running Kubuntu, monitors are often improperly configured, so resetting orientation and positions with xrandr is required. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7fe353909427 in QHashData::nextNode(QHashData::Node*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe355c61e7a in ?? () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #6 0x7fe355c60df6 in Plasma::DataEngine::removeSource(QString const&) () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #7 0x7fe2f441cdbc in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/dataengine/plasma_engine_mpris2.so #8 0x7fe353af36ff in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fe3545df893 in QDBusServiceWatcher::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7fe3545e01d2 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #11 0x7fe3545e068b in QDBusServiceWatcher::qt_metacall(QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #12 0x7fe35459123b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #13 0x7fe353ae7b30 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fe35476bf32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7fe353abae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fe353abdeb1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7fe353b15427 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7fe351e734f9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7fe351ec8228 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7fe351e70cb0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7fe353b14aea in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7fe353ab97cb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7fe353ac1c2a in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x5579d049f567 in ?? () #25 0x7fe353023510 in __libc_start_call_main (main=main@entry=0x5579d049e6b0, argc=argc@entry=1, argv=argv@entry=0x7fff744f1578) at ../sysdeps/nptl/libc_start_call_main.h:58 #26 0x7fe3530235c9 in __libc_start_main_impl (main=0x5579d049e6b0, argc=1, argv=0x7fff744f1578, init=, fini=, rtld_fini=, stack_end=0x7fff744f1568) at ../csu/libc-start.c:381 #27 0x5579d049f685 in ?? () [Inferior 1 (process 23239) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462728] New: Dolphin crashes when unmounting external hard drive
https://bugs.kde.org/show_bug.cgi?id=462728 Bug ID: 462728 Summary: Dolphin crashes when unmounting external hard drive Classification: Applications Product: dolphin Version: 22.08.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: marxtev...@netscape.net CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.08.3) Qt Version: 5.15.7 Frameworks Version: 5.100.0 Operating System: Linux 6.0.11-200.fc36.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 36 (Server Edition) DrKonqi: 5.26.4 [KCrashBackend] -- Information about the crash: Un/Mounting USB drive and Dolphin crashed. Not sure which it was doing as KDE message is ambiguous. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f0febcc4ad0 in KCoreDirListerCache::slotUpdateResult(KJob*) () from /lib64/libKF5KIOCore.so.5 #5 0x7f0fea0dbc26 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #6 0x7f0feb48e4c9 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib64/libKF5CoreAddons.so.5 #7 0x7f0feb493f2b in KJob::finishJob(bool) () from /lib64/libKF5CoreAddons.so.5 #8 0x7f0fea0dbc26 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #9 0x7f0febc6cda0 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib64/libKF5KIOCore.so.5 #10 0x7f0febc67cca in KIO::SlaveInterface::dispatch() () from /lib64/libKF5KIOCore.so.5 #11 0x7f0febc6a651 in KIO::Slave::gotInput() () from /lib64/libKF5KIOCore.so.5 #12 0x7f0fea0dbc26 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #13 0x7f0fea0d2ec4 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #14 0x7f0feadaed12 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #15 0x7f0fea0a8278 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #16 0x7f0fea0ab5e4 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #17 0x7f0fea0f9897 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #18 0x7f0fe7de5faf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #19 0x7f0fe7e3b2c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #20 0x7f0fe7de3940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #21 0x7f0fea0f938a in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #22 0x7f0fea0a6cca in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #23 0x7f0fea0aed92 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #24 0x564b2b6a0a57 in main () [Inferior 1 (process 15973) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 461519] Launching .desktop applications causes empty new tab "Loading cancelled"
https://bugs.kde.org/show_bug.cgi?id=461519 Mark Capella changed: What|Removed |Added CC||markcape...@twcny.rr.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 462023] Akonadi and KWin crashed when launching "icons" system settings
https://bugs.kde.org/show_bug.cgi?id=462023 Mark A Stevens changed: What|Removed |Added CC||marxtev...@netscape.net --- Comment #2 from Mark A Stevens --- I had this happen on 03 December 2022. I was restarting Firefox, which I run up to 9 Activities, with multiple tabs each. It had crashed overnight. GKRELLM crashed about the same time. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 462430] New: Konsole crashed at tab close
https://bugs.kde.org/show_bug.cgi?id=462430 Bug ID: 462430 Summary: Konsole crashed at tab close Classification: Applications Product: konsole Version: 22.08.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: sigs...@protonmail.com Target Milestone: --- Application: konsole (22.08.3) Qt Version: 5.15.7 Frameworks Version: 5.100.0 Operating System: Linux 6.0.10-300.fc37.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 37 (KDE Plasma) DrKonqi: 5.26.3 [KCrashBackend] -- Information about the crash: I had several Konsole windows open. In one of them, the window was split vertically. While closing the split with a standard keyboard shortcut, an error report appeared. The split was closed and the rest of the Konsole continued to run normally. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Konsole (konsole), signal: Aborted [KCrash Handler] #4 0x7f5dbcaafe7c in __pthread_kill_implementation () from /lib64/libc.so.6 #5 0x7f5dbca5faa6 in raise () from /lib64/libc.so.6 #6 0x7f5dbca497fc in abort () from /lib64/libc.so.6 #7 0x7f5dbccd7e80 in std::__glibcxx_assert_fail(char const*, int, char const*, char const*) () from /lib64/libstdc++.so.6 #8 0x7f5dbe879257 in Konsole::Screen::setSelectionEnd(int, int, bool) () from /lib64/libkonsoleprivate.so.1 #9 0x7f5dbe8d2abe in Konsole::TerminalDisplay::extendSelection(QPoint const&) () from /lib64/libkonsoleprivate.so.1 #10 0x7f5dbe8d71c3 in Konsole::TerminalDisplay::mousePressEvent(QMouseEvent*) () from /lib64/libkonsoleprivate.so.1 #11 0x7f5dbdff1818 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #12 0x7f5dbdfaed12 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #13 0x7f5dbdfb7382 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #14 0x7f5dbd2a8278 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #15 0x7f5dbdfb5482 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib64/libQt5Widgets.so.5 #16 0x7f5dbe00ab7c in QWidgetWindow::handleMouseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #17 0x7f5dbe00df40 in QWidgetWindow::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #18 0x7f5dbdfaed12 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #19 0x7f5dbd2a8278 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #20 0x7f5dbd76ae7d in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib64/libQt5Gui.so.5 #21 0x7f5dbd74a02c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib64/libQt5Gui.so.5 #22 0x7f5dbb3e23f4 in userEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5WaylandClient.so.5 #23 0x7f5dbb666cbf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #24 0x7f5dbb6bc598 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #25 0x7f5dbb663f40 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #26 0x7f5dbd2f938a in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #27 0x7f5dbd2a6cca in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #28 0x7f5dbd2aed92 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #29 0x56042c8997d1 in main () [Inferior 1 (process 9394) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 434057] Add stdio mode to valgrind's gdbserver
https://bugs.kde.org/show_bug.cgi?id=434057 --- Comment #8 from Mark Wielaard --- We reviewed (about half) of the patch and found a couple of things to cleanup: - There is a sleep(3) after fork, before execve in the parent (vgdb) to wait for valgrind to fully startup This should be replaced with looking for the shared_mem file to appear - write_to_gdb should retry short writes. - send_packet is badly indented. - receive_packet should try again if the checksum is bad (very unlikely since we only use reliable transports) - do_multi_mode () closes down too soon. When the run is over (the valgrind side closes), it should restart listening on the gdb side. That way the user can run again without setting up the target again. - QEnvironmentHexEncoded, QEnvironmentReset, QEnvironmentUnset and QSetWorkingDir aren't really handled. Specifically split_hexdecode only checks the arguments can be decoded and split. But the arguments aren't actually returned. This might be fine if setting the environment and cwd will be handled differently (on the gdb side). But could use a comment in that case. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462115] xdg_popup sent excessive configure events on parent window move
https://bugs.kde.org/show_bug.cgi?id=462115 --- Comment #2 from Mark Bolhuis --- (In reply to Vlad Zahorodnii from comment #1) > > The popup should only receive a configure sequence if the popup needs to be > > re-constrained. > > Does the spec say so? Relevant parts of the spec are: xdg_popup.configure: "For version 2 or older, the configure event for an xdg_popup is only ever sent once for the initial configuration. Starting with version 3, it may be sent again if the popup is setup with an xdg_positioner with set_reactive requested, or in response to xdg_popup.reposition requests." xdg_positioner.set_reactive: "If the conditions changed and the popup was reconstrained, an xdg_popup.configure event is sent with updated geometry, followed by an xdg_surface.configure event." xdg_popup.reposition: "The popup will be placed given the details in the passed xdg_positioner object, and a xdg_popup.repositioned followed by xdg_popup.configure and xdg_surface.configure will be emitted in response." Technically speaking the spec doesn't explicitly forbid sending the configure event arbitrarily, only that it must if the popup needs re-constraining. However, I argue that sending arbitrary events like this is not the point, especially since its in response to window position, something Wayland windows aren't aware of. Also the parameters are identical, so the client can't do anything meaningful with it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462115] New: xdg_popup sent excessive configure events on parent window move
https://bugs.kde.org/show_bug.cgi?id=462115 Bug ID: 462115 Summary: xdg_popup sent excessive configure events on parent window move Classification: Plasma Product: kwin Version: 5.26.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: m...@bolhuis.dev Target Milestone: --- SUMMARY When a xdg_popup is created with set_reactive kwin sends a configure sequence every time the parent window moves, even if the movement of the window doesn't result in needing to re-constrain the popup. STEPS TO REPRODUCE 1. Create a xdg_popup with set_reactive. 2. Move the parent window. OBSERVED RESULT The popup is sent a configure sequence continuously as the parent window moves even if it does not need to be re-constrained. EXPECTED RESULT The popup should only receive a configure sequence if the popup needs to be re-constrained. SOFTWARE/OS VERSIONS Linux: 6.0.9-arch1-1 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 RELATED BUGS https://bugs.kde.org/show_bug.cgi?id=461997 https://bugs.kde.org/show_bug.cgi?id=461994 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461994] A xdg_popup does not follow it's parent surface unless set_reactive is called
https://bugs.kde.org/show_bug.cgi?id=461994 Mark Bolhuis changed: What|Removed |Added Platform|Other |Archlinux -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 462007] Implicit int in none/tests/faultstatus.c
https://bugs.kde.org/show_bug.cgi?id=462007 Mark Wielaard changed: What|Removed |Added Status|REPORTED|RESOLVED CC||m...@klomp.org Resolution|--- |FIXED --- Comment #1 from Mark Wielaard --- Thanks, that was not intended. Fixed by: commit 0811a612dd7ce0c02a5dd699b34e660c742df8fe (HEAD -> master) Author: Mark Wielaard Date: Fri Nov 18 20:12:06 2022 +0100 Implicit int in none/tests/faultstatus.c There is a definition in faultstatus.c that is not accepted by C99 compilers (implicit ints were removed in that language revision). https://bugs.kde.org/show_bug.cgi?id=462007 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461997] xdg_positioner.set_constraint_adjustment(none) is ignored
https://bugs.kde.org/show_bug.cgi?id=461997 --- Comment #2 from Mark Bolhuis --- (In reply to David Edmundson from comment #1) > What's the user-facing bug we're trying to fix? That if the popup is created with a constraint_adjustment of none that the popup isn't constrained, as per the spec. Based on that code snippet I assume then don't call c->keepInArea(screen); -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461997] New: xdg_positioner.set_constraint_adjustment(none) is ignored
https://bugs.kde.org/show_bug.cgi?id=461997 Bug ID: 461997 Summary: xdg_positioner.set_constraint_adjustment(none) is ignored Classification: Plasma Product: kwin Version: 5.26.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: m...@bolhuis.dev Target Milestone: --- SUMMARY A xdg_popup with set_reactive called, and with a constraint_adjustment of none is still adjusted by slide_x and slide_y rules. STEPS TO REPRODUCE 1. Create a xdg_positioner with a constraint adjustment of none and is reactive. 2. Create a xdg_toplevel and xdg_popup child with that positioner. 3. Move the window such that the popup will be constrained. OBSERVED RESULT The popup slides in both the x and y axis as if slide_x and slide_y were passed to set_constraint_adjustment EXPECTED RESULT The popup should stay fixed relative to the anchor point on the parent. SOFTWARE/OS VERSIONS Linux: arch6.0.8-arch1-1 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461994] New: A xdg_popup does not follow it's parent surface unless set_reactive is called
https://bugs.kde.org/show_bug.cgi?id=461994 Bug ID: 461994 Summary: A xdg_popup does not follow it's parent surface unless set_reactive is called Classification: Plasma Product: kwin Version: 5.26.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: m...@bolhuis.dev Target Milestone: --- SUMMARY An xdg_popup should always follow the parent surface regardless of the xdg_positioner.set_reactive request being called or not. The set_reactive request only concerns re-constraining the popup if the constraints change, which may happen by moving the window. STEPS TO REPRODUCE 1. Create a xdg_toplevel and xdg_popup child 2. Do not call set_reactive on the associated xdg_positioner 3. Move the parent toplevel window OBSERVED RESULT The window moves and the popup doesn't. EXPECTED RESULT The popup should follow the parent. SOFTWARE/OS VERSIONS Linux: arch6.0.9-arh1-1 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461987] New: Window resizing snaps to the edge of a hidden panel
https://bugs.kde.org/show_bug.cgi?id=461987 Bug ID: 461987 Summary: Window resizing snaps to the edge of a hidden panel Classification: Plasma Product: kwin Version: 5.26.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: m...@bolhuis.dev Target Milestone: --- SUMMARY When resizing a window towards a panel the edge of the window snaps to a line where the edge of the panel would be if visible. STEPS TO REPRODUCE Assume that the panel is placed along the bottom, although the bug appears for all placements. 1. Configure the panel to auto-hide. 2. Open any GUI app. 2. Resize the window from the bottom down to where the top edge of the panel would be if visible. OBSERVED RESULT The window edge snaps to a line offset by the height of the panel above the output edge. EXPECTED RESULT The window should snap to the edge of the output. NOTES Occurs on both Wayland and X11 Does not occur when dragging the entire window down, only when resizing down. SOFTWARE/OS VERSIONS Linux arch 6.0.8-arch1-1 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 461751] Elisa crashes on start
https://bugs.kde.org/show_bug.cgi?id=461751 --- Comment #2 from Mark --- (In reply to Tobias Fella from comment #1) > This means that libvlc_new failed; unfortunately, libvlc does not seem to > have any logging in these functions. I found the source of the issue with some help with strace. libvlc requires vlc-plugin-base on Kubuntu 22.10. Installing Elisa will install the libvlc and libvlccore dependency, but it won't install the vlc-plugin-base dependency for libvlc which causes the crash at the start. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 461751] New: Elisa crashes on start
https://bugs.kde.org/show_bug.cgi?id=461751 Bug ID: 461751 Summary: Elisa crashes on start Classification: Applications Product: Elisa Version: 22.08.3 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: m...@leyva.me Target Milestone: --- Created attachment 153704 --> https://bugs.kde.org/attachment.cgi?id=153704=edit Elisa crash logs SUMMARY Elisa crashes on startup. Refer to the attached backtrace for further details. STEPS TO REPRODUCE 1. Run Elisa OBSERVED RESULT Shouldn't crash EXPECTED RESULT Crashes. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.10 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 444488] Use glibc.pthread.stack_cache_size tunable
https://bugs.kde.org/show_bug.cgi?id=88 Mark Wielaard changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Mark Wielaard --- (In reply to Philippe Waroquiers from comment #1) > In the discussion on valgrind-users mailing list, > Paul reported tthat: > 'It looks like "stack_cache_actsize" in libc moved to be > _dl_stack_cache_actsize in ld-linux-x86-64.so.2' > > Is there a way to modify the glibc glibc.pthread.stack_cache_size tunable > from valgrind ? tunables are set by the GLIBC_TUNABLES environment variable https://www.gnu.org/software/libc/manual/html_node/Tunables.html We can set/add to that GLIBC_TUNABLES environment variable in coregrind/m_initimg/initimg-linux.c setup_client_env () where we also set the LD_PRELOAD environment variable. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 351857] confusing error message about valid command line option
https://bugs.kde.org/show_bug.cgi?id=351857 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Mark Wielaard --- Patch looks good to me. Thanks. + VG_(fmsg_bad_option)(qq_arg, + "Missing boolean value, did you mean '%s=yes'?\n", + qq_arg); We could consider (as a followup?) to just interpret this as =yes instead of having a warning. Please just remove the old #define VG_BOOL_CLOM instead of #if 0 ... -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 459476] address already in use when using vgdb
https://bugs.kde.org/show_bug.cgi?id=459476 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||m...@klomp.org --- Comment #1 from Mark Wielaard --- Looks good, thanks. Pushed as: commit ea919973941e5dddc3a9611946b7cc6ca9d87a4f (HEAD -> master) Author: Alexandra Petlanova Hajkova Date: Wed Sep 7 05:46:55 2022 -0400 vgdb: allow address reuse to avoid "address already in use" errors https://bugs.kde.org/show_bug.cgi?id=459476 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 461716] New: crash on laptop waking from sleep
https://bugs.kde.org/show_bug.cgi?id=461716 Bug ID: 461716 Summary: crash on laptop waking from sleep Classification: Applications Product: systemsettings Version: 5.26.3 Platform: OpenSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mr.mark.stari...@gmail.com Target Milestone: --- Application: systemsettings (5.26.3) Qt Version: 5.15.7 Frameworks Version: 5.99.0 Operating System: Linux 6.0.7-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.26.3 [KCrashBackend] -- Information about the crash: closed lid, opened it back up, logged back in and widget reported a crash The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7efcb55bcf00 in QOpenGLContext::isValid (this=this@entry=0x561e02e097d0) at kernel/qopenglcontext.cpp:723 #5 0x7efcb55bddd2 in QOpenGLContext::doneCurrent (this=0x561e02e097d0) at kernel/qopenglcontext.cpp:1058 #6 0x7efcb55c10e6 in QGuiGLThreadContext::~QGuiGLThreadContext (this=0x7efca0007f90, __in_chrg=) at kernel/qopenglcontext.cpp:231 #7 qThreadStorage_deleteData (d=0x7efca0007f90) at ../../include/QtCore/../../src/corelib/thread/qthreadstorage.h:92 #8 QThreadStorage::deleteData (x=0x7efca0007f90) at ../../include/QtCore/../../src/corelib/thread/qthreadstorage.h:135 #9 0x7efcb4efae9f in QThreadStorageData::finish (p=p@entry=0x561e009b04d0) at thread/qthreadstorage.cpp:200 #10 0x7efcb50dec9f in QCoreApplicationPrivate::cleanupThreadData (this=this@entry=0x561e009dce90) at kernel/qcoreapplication.cpp:501 #11 0x7efcb556df32 in QGuiApplicationPrivate::~QGuiApplicationPrivate (this=0x561e009dce90, __in_chrg=) at kernel/qguiapplication.cpp:1710 #12 0x7efcb5da3f59 in QApplicationPrivate::~QApplicationPrivate (this=0x561e009dce90, __in_chrg=) at kernel/qapplication.cpp:163 #13 0x561dffd16fe2 in main (argc=, argv=) at /usr/src/debug/systemsettings-5.26.3/app/main.cpp:189 [Inferior 1 (process 6558) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379509] Message not found
https://bugs.kde.org/show_bug.cgi?id=379509 --- Comment #2 from Mark Stanton --- I'm very pleased that it appears someone is now attending to reported bugs, but, as I said in my other report that has just been looked at, I was looking for an answer for this five years ago so, after not receiving a response for a long time, I simply stopped using KMail and therefore cannot reproduce the issue any more. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461476] New: Issues with maximized windows in Konsole and Okular
https://bugs.kde.org/show_bug.cgi?id=461476 Bug ID: 461476 Summary: Issues with maximized windows in Konsole and Okular Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: m...@anonymoose.net CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Installed latest KDE neon 5.26 updates; Windows misbehave when maximized: So far the following are affected: (I started seeing this with Konsole because I live there. I've tried other applications and include them here.) - Konsole - Okular - KeepassXC - KInfoCenter - KRDC - System Settings Unaffected: - Dolphin - Brave browser None of them updates the window when max'ed. It takes input and produces output but nothing changes in the window is restored. OK, I give up. I'll stop maximizing ;) Konsole STEPS TO REPRODUCE 1. Maximize windows 2. Enter a shell command 3. Restore window Konsole OBSERVED RESULT Window updates with shell command and result only when restored Okular STEPS TO REPRODUCE 1. Maximize window 2. Click to open recent file: Doesn't accept click 3. Click Menu to open file: File opens in another window but isn't displayed 4. Alt-tab to new window shows only the window title until it's restored 5. Restore window and open a file 6. Maximize and try to scroll. Window doesn't change 7. Restore window and see that scrolling did, in fact, occur Both EXPECTED RESULT Updates in realtime OTHER NOTES Menus and hotkeys seem to work, but no window updates occur until the window is restored. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 Kernel Version: 5.15.0-52-generic (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION I flagged this as "minor" because there's no "weird" severity. The workaround is simple: Don't do that. I max most everything for focus and everything remembers to re-max when I open a new window. *Addendum: Well, nuts. I just opened KInfoCenter and it opened maximized and worked fine. UNTIL I restored and re-maxed. Ditto with System Settings. I got nothing... -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 377818] QIF import does not support ContribX and WithdrwX transactions
https://bugs.kde.org/show_bug.cgi?id=377818 Mark changed: What|Removed |Added Status|NEEDSINFO |REPORTED Version|4.8.0 |5.1.2 Resolution|WAITINGFORINFO |--- --- Comment #3 from Mark --- ContribX and WithdrwX transaction types are ignored on QIF import in version 5.1.2. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 461288] New: Next scheduled loan due date changes to wrong date
https://bugs.kde.org/show_bug.cgi?id=461288 Bug ID: 461288 Summary: Next scheduled loan due date changes to wrong date Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: markm10...@gmail.com Target Milestone: --- SUMMARY My scheduled loan has been properly working since I started using KMy$ several years ago. In the last couple of months since updating to the latest appimages, I have had a problem that the next scheduled loan date changes to an incorrect date after entering the latest payment. My loan was set up with an initial loan date on the 18th of the month and payments due on the first of each month. This worked correctly for over 2 years and then recently changed that after I enter a payment on the first of the month, the next payment is now scheduled for the 18th of the following month. I can save my file as an xml file and change the scheduled payment for the next month and it will display correctly in KMy$ but after I enter the scheduled transaction on the first of the month, it reverts to the 18th of the month for future months again. 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. Create a loan on the 18th of the month. 2. Schedule payment on the first of month 3. Enter payment on the first of month OBSERVED RESULT Future scheduled payments schedule on 18th of month EXPECTED RESULT Future payments should remain on 1st of month SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Version 5.98.0 Qt Version: Version 5.15.5 (built against 5.15.5) ADDITIONAL INFORMATION currently using appimage 5.1-271 -- You are receiving this mail because: You are watching all bug changes.
