[valgrind] [Bug 486180] [Valgrind][MIPS] 'VexGuestArchState' has no member named 'guest_IP_AT_SYSCALL'
https://bugs.kde.org/show_bug.cgi?id=486180 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Mark Wielaard --- Urgh, this is unfortunate. We didn't have a mips builder and didn't find this during CI testing. This should probably have been implemented as VG_(client_extension) see coregrind/m_extension/extension-main.c which is only done for s390x now. There is precedent in fixup_guest_state_to_restart_syscall -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 362680] --error-exitcode not honored when file descriptor leaks are found
https://bugs.kde.org/show_bug.cgi?id=362680 Mark Wielaard changed: What|Removed |Added CC||v...@altlinux.org --- Comment #6 from Mark Wielaard --- *** Bug 482358 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 482358] Feature Request: Add --track-fds=error
https://bugs.kde.org/show_bug.cgi?id=482358 Mark Wielaard changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Mark Wielaard --- *** This bug has been marked as a duplicate of bug 362680 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 485924] No support for pidfd_send_signal system call
https://bugs.kde.org/show_bug.cgi?id=485924 --- Comment #3 from Mark Wielaard --- So the only tricky part is that we want to mimic this part of the (generic) PRE(sys_kill): /* If we're sending SIGKILL, check to see if the target is one of our threads and handle it specially. */ if (ARG2 == VKI_SIGKILL && ML_(do_sigkill)(ARG1, -1)) SET_STATUS_Success(0); In the pidfd_send_signal case ARG2 is the signo, just like the kill syscall. But ARG1 is a pidfd and do_sigkill wants an pid (tid). So we have to somehow translate the pidfd to a pid number. It isn't immediately clear how to do that. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 485924] No support for pidfd_send_signal system call
https://bugs.kde.org/show_bug.cgi?id=485924 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||m...@klomp.org --- Comment #2 from Mark Wielaard --- There was a preliminary implementation posted to the mailinglist: https://sourceforge.net/p/valgrind/mailman/message/52515225/ -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 486025] New: Imported google groupware doesn't immediately show after import
https://bugs.kde.org/show_bug.cgi?id=486025 Bug ID: 486025 Summary: Imported google groupware doesn't immediately show after import Classification: Applications Product: Merkuro Version: 24.02.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: mspuban...@fastmail.us CC: c...@carlschwan.eu Target Milestone: --- SUMMARY Importing a new calendar (google groupware) did not show the imported calendar until after restart STEPS TO REPRODUCE 1. Have a Merkuro instance that lacks a google groupware calendar (ie after fresh Fedora install on system) 2. Start Merkuro and import the Google calendar 3. Current calendar in view doesn't update, must exit merkuro and restart it OBSERVED RESULT Google Groupware calendar doesn't automatically show after newly imported, must exit and restart Merkuro EXPECTED RESULT Update event after import in the app should make the calendar redraw with the newly imported calendar's events. This would be preferred from a usability standpoint, since the calendar was newly linked and imported it would verify the success of the operation. However, restarting Merkuro does make the Google events show. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Fedora 40 Kernel Linux 6.8.7-300.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Micro-Star International Co., Ltd Bravo 15 A4DDR Linux msi 6.8.7-300.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Apr 17 19:21:08 UTC 2024 x86_64 GNU/Linux Firmware Version: E16WKAMS.110 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 485991] New: [1] Star positions are still in daylight Savings Time [2] Cursor is not visible on application, visible in other screen areas
https://bugs.kde.org/show_bug.cgi?id=485991 Bug ID: 485991 Summary: [1] Star positions are still in daylight Savings Time [2] Cursor is not visible on application, visible in other screen areas Classification: Applications Product: kstars Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: mark.george.mur...@gmail.com Target Milestone: --- SUMMARY [1] star positions are shown for DST, which ended at beginning of April STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Ubuntu 23.10 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[knights] [Bug 429654] Cant's disable voice
https://bugs.kde.org/show_bug.cgi?id=429654 --- Comment #8 from Mark Capella --- I'd like to also suggest https://invent.kde.org/markcapella/knights/-/commit/248010a9a134c4268bce0ae518e4a94b723e50af Which removes leftover qDebug STDERR message. "background key "Background"" And corrects three STDERR messages generated on open of Settings -> Configure Knights. "edit: editing failed" "edit: editing failed" "edit: editing failed" -- You are receiving this mail because: You are watching all bug changes.
[knights] [Bug 429654] Cant's disable voice
https://bugs.kde.org/show_bug.cgi?id=429654 --- Comment #7 from Mark Capella --- I've had to refresh my repo after botching it locally. Here's a new commit: https://invent.kde.org/markcapella/knights/-/commit/551027d73e05928c85a5a3d84d2078d463fa1c49 -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 482482] Merkuro Calandar starting wrong week in week-view
https://bugs.kde.org/show_bug.cgi?id=482482 Mark S changed: What|Removed |Added CC||mspuban...@fastmail.us --- Comment #4 from Mark S --- I happened to make a duplicate bug on redhat bugzilla for this, see: https://bugzilla.redhat.com/show_bug.cgi?id=2276317 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 485778] Crash with --track-fds=all and --gen-suppressions=all
https://bugs.kde.org/show_bug.cgi?id=485778 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from Mark Wielaard --- commit d68d584cead390c339b9575c5c9679e8ce50c37f Author: Mark Wielaard Date: Fri Apr 19 22:46:11 2024 +0200 core errors suppression support Add two new functions core_get_extra_suppression_info and core_get_error_name as alternatives for tool suppression callbacks. These functions are used in gen_suppression. Instead of a tool name, a core error component name is "CoreError". Two new suppression kinds FdBadCloseSupp and FdNotClosedSupp were added. Corresponding to the FdBadClose and FdNotClosed error kinds. core_error_matches_suppression matches these suppression kinds with error kinds. core_get_extra_suppression_info and core_print_extra_suppression_use are noops for core errors. is_suppressible_error, supp_matches_error, load_one_suppressions_file and show_used_suppressions have been adjusted to work with core error kinds. A new function VG_(found_or_suppressed_errs) helps to not output an empty error summary if only core errors are requested, but no errors were detected. VG_(clo_track_fds) has been moved from pub_core_options.h to pub_tool_options.h. And VG_(needs_core_errors) now takes a Bool that can be set to false in the tool post_clo_init handler. This is used in the none tool to request core errors, but disable all reporting if no option has been given that enables such errors. This make sure only the none/tests/fdleak_ipv4.stderr.exp needs adjustment. For all other tests the output is exactly as before. https://bugs.kde.org/show_bug.cgi?id=485778 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 485778] Crash with --track-fds=all and --gen-suppressions=all
https://bugs.kde.org/show_bug.cgi?id=485778
Mark Wielaard changed:
What|Removed |Added
Attachment #168679|0 |1
is obsolete||
--- Comment #3 from Mark Wielaard ---
Created attachment 168690
--> https://bugs.kde.org/attachment.cgi?id=168690=edit
core errors suppression support
This version handles both generating and using suppressions. So now you can
also add something like:
{
core-bad-close
CoreError:FdBadClose
fun:close
fun:closefile
fun:main
}
And it will suppress the error as expected.
It also adds VG_(needs_core_errors) to all tools that support tool_errors and
to the none tool.
No testcases yet though
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 485778] Crash with --track-fds=all and --gen-suppressions=all
https://bugs.kde.org/show_bug.cgi?id=485778
--- Comment #2 from Mark Wielaard ---
Created attachment 168679
--> https://bugs.kde.org/attachment.cgi?id=168679=edit
core errors gensuppressions support
Initial implementation for --gen-suppressions support for core errors
With this the testcase ../../vg-in-place --track-fds=all --tool=none
--gen-suppressions=all ./fdleak_creat produces:
==381147== Bad option: --gen-suppressions=yes
==381147== Can't use --gen-suppressions= with Nulgrind
==381147== because it doesn't generate errors.
==381147== Use --help for more information or consult the user manual.
==381147== Nulgrind, the minimal Valgrind tool
==381147== Copyright (C) 2002-2017, and GNU GPL'd, by Nicholas Nethercote.
==381147== Using Valgrind-3.23.0.GIT and LibVEX; rerun with -h for copyright
info
==381147== Command: ./fdleak_creat
==381147==
==381147==
==381147== FILE DESCRIPTORS: 4 open (3 std) at exit.
==381147== Open file descriptor 3: /tmp/file.381147
==381147==at 0x495B9C4: creat (creat64.c:28)
==381147==by 0x401249: main (fdleak_creat.c:13)
==381147==
{
CoreError:FdNotClosed
fun:creat
fun:main
}
==381147== Open file descriptor 2: /dev/pts/4
==381147==
==381147==
==381147== (No origin, error cannot be suppressed)
==381147== Open file descriptor 1: /dev/pts/4
==381147==
==381147==
==381147== (No origin, error cannot be suppressed)
==381147== Open file descriptor 0: /dev/pts/4
==381147==
==381147==
==381147== (No origin, error cannot be suppressed)
==381147==
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 485778] Crash with --track-fds=all and --gen-suppressions=all
https://bugs.kde.org/show_bug.cgi?id=485778 Mark Wielaard changed: What|Removed |Added Assignee|jsew...@acm.org |m...@klomp.org Status|REPORTED|CONFIRMED CC||ahajk...@redhat.com, ||m...@klomp.org Ever confirmed|0 |1 --- Comment #1 from Mark Wielaard --- (In reply to Paul Floyd from comment #0) > Are we planning on adding suppressions to core errors? If so this message > will also need to change: > ==32134== Bad option: --gen-suppressions=yes > ==32134== Can't use --gen-suppressions= with Nulgrind > ==32134== because it doesn't generate errors. > ==32134== Use --help for more information or consult the user manual. > > (it says it can't use it and then it does use it!) There are a couple of extra callbacks needed to support suppressions for core errors. But they shouldn't be hard to add. There also needs to be a special check for core errors that have a NULL where (e.g. when reporting with --track-fds=all on inherited file descriptors). Working on it now. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 328563] make track-fds support xml output
https://bugs.kde.org/show_bug.cgi?id=328563 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #7 from Mark Wielaard --- commit 09b5ad416c5ddf1375f269f6ea2253e90fa08f01 Author: Alexandra Hájková Date: Thu Apr 18 05:21:49 2024 -0400 Improve file descriptor xml output, add fd and path elements Add needs_xml_output to none tool so it can also output xml when --track-fds enabled. Use xml protocolversion 5 when clo_track_fds is enabled Split OpenFD pathname and description. Add description when a file descriptor is closed so it can be used in a future error. On error print element and (if known) a element. Add docs/internals/xml-output-protocol5.txt. https://bugs.kde.org/show_bug.cgi?id=328563 Co-Authored-By: Mark Wielaard -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 362680] --error-exitcode not honored when file descriptor leaks are found
https://bugs.kde.org/show_bug.cgi?id=362680 Mark Wielaard changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Mark Wielaard --- commit 34e9e4957ada1ba0a51266faee23f61724935fcb Author: Mark Wielaard Date: Wed Mar 20 01:44:23 2024 -0400 Add core errors and use them to implement file descriptor tracker All the tool error callbacks now have a core error equivalent. core errors are negative (while tool errors are positive). There are two new ones for tracking issues with file descriptors. FdBadClose (-2) and FdNotClosed (-3). Add following core error functions with delegates to file descriptor specific functions (implemented in syswrap-generic): - core_eq_Error (fd_eq_Error) Compares core errors to detect duplicates - core_before_pp_Error (fd_before_pp_Error) Currently prints nothing for known core errors and exists with FATAL for unknown core errors - core_pp_Error (fd_pp_Error) For FdBadClose prints the backtraces for the file descriptor was opened, where it was originally closed and where it was closed again. For FdNotClosed prints where the file descriptor was opened. - core_update_extra (fd_update_extra) Returns the size of the BadCloseExtra or FdNotClosedExtra struct which data needs to be saved (the fd number, pathname/description and previous backtraces). We now accept the error (ExeContext) where to be NULL. This is necessary for reporting not closed file descriptors when the descriptor is inherited from the parent (so wasn't actually created and doesn't have a 'where' in the current process code). All the testcases still pass since the (stderr) output is the same. But now they count as "real" errors. And so --error-exitcode does now also work for file descriptor errors or leaks. https://bugs.kde.org/show_bug.cgi?id=362680 Co-authored-by: Alexandra Hájková -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 362680] --error-exitcode not honored when file descriptor leaks are found
https://bugs.kde.org/show_bug.cgi?id=362680 --- Comment #4 from Mark Wielaard --- bug #328563 has an attachment that implements this -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 450705] s390x: Add NNPA support (arch14)
https://bugs.kde.org/show_bug.cgi?id=450705 --- Comment #8 from Mark Wielaard --- (In reply to Andreas Arnez from comment #7) > (In reply to Andreas Arnez from comment #6) > > Created attachment 168623 [details] > > Updated version of the extension proposal > I pushed this now, as a preparation to adding NNPA support. If there are > still any issues with this, please let me know. Looks good on both x86_64 and s390x (both fedora 39). On s390x the ppno.vgtest succeeds. x86_64 had zero failures. s390x had one failure (also before you patch): drd/tests/tc04_free_lock (stderr) I did push two small fixups: commit 02bca4fa3a62dafbc8f051a0f766f9d5763f6e1c Author: Mark Wielaard Date: Thu Apr 18 15:58:37 2024 +0200 Add pub_core_extension.h to coregrind/Makefile.am noinst_HEADERS commit 381e2a25fbf8e7d16d66851a5d0e1f919cf69505 (HEAD -> master) Author: Mark Wielaard Date: Thu Apr 18 17:45:16 2024 +0200 Don't include pub_tool_tooliface.h in priv_types_n_macros.h post-regtest-checks complains: *** File coregrind/m_extension/priv_types_n_macros.h must not include pub_tool_tooliface.h Which isn't really necessary anyway since priv_types_n_macros.h already includes pub_core_tooliface.h. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 450705] s390x: Add NNPA support (arch14)
https://bugs.kde.org/show_bug.cgi?id=450705
--- Comment #5 from Mark Wielaard ---
I haven't reviewed the fully proposal, but in general I like the idea of using
the same mechanism as the syscalls for instrumenting these more complex
instructions. It is at least familiar. You might want to rename
guest_IP_AT_SYSCALL (it looks like it has the right semantics, but looks funny)
and you might want to look at what defines VG_(client_extension). Currently it
is only defined for s390x, so building scheduler.c will break on any other
arch. It should probably be its own function inside scheduler.c with something
like #if defined(VGA_s390x) x390x_... #else VG_(core_panic)("arch doesn't
implement...") #endif.
It would be nice to get this in this week so it makes valgrind -3.23.0-RC1 and
can get a bit wider testing.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 450705] s390x: Add NNPA support (arch14)
https://bugs.kde.org/show_bug.cgi?id=450705 --- Comment #3 from Mark Wielaard --- Extension idea was posted to the mailinglist: https://sourceforge.net/p/valgrind/mailman/message/58753610/ -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 485276] std::optional use: "Conditional jump or move depends on uninitialised value(s)" (clang) aarch64
https://bugs.kde.org/show_bug.cgi?id=485276 --- Comment #4 from Mark Wielaard --- (In reply to Mark Wielaard from comment #3) > I am unable to replicate this with either clang version 17.0.6 or 18.1.2, > not with -O2 or -O1. On x86_64. Missed that the original report was against arm64 (sorry). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 485276] std::optional use: "Conditional jump or move depends on uninitialised value(s)" (clang) aarch64
https://bugs.kde.org/show_bug.cgi?id=485276 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #3 from Mark Wielaard --- I am unable to replicate this with either clang version 17.0.6 or 18.1.2, not with -O2 or -O1. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 472329] std::optional use: "Conditional jump or move depends on uninitialised value(s)" (g++)
https://bugs.kde.org/show_bug.cgi?id=472329 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 CC||m...@klomp.org Status|REPORTED|CONFIRMED --- Comment #8 from Mark Wielaard --- I can replicate with the code of comment #4 and g++ 13.2.1 or 14.0.1 (prerelease) but only with -O1. -O0 and -O2 don't show the issue. -- You are receiving this mail because: You are watching all bug changes.
[knights] [Bug 429654] Cant's disable voice
https://bugs.kde.org/show_bug.cgi?id=429654 --- Comment #5 from Mark Capella --- Sure! It looks like this changeset: https://invent.kde.org/markcapella/knights/-/commit/fe457fe5af3b99e59206dfb6e2d266ccc264cbce -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 481874] Add arm64 support for FreeBSD
https://bugs.kde.org/show_bug.cgi?id=481874 --- Comment #17 from Mark Wielaard --- .git-blame-ignore-revs references a clang-format rev that doesn't exist in tree. Makefile.all.am and Makefile.tool.am look correct. NEWS OK. VEX changes OK, except for unnecessarily extending VexGuestARM64State for non-freebsd systems. Would be really nice if that VEX/auxprogs/genoffsets.c GENOFFSET(ARM64,arm64,SETC); could only be done of freebsd. configure.ac looks OK (but not a fan of the reindentations, it makes looking for the actual changes a bit of a pain) coregrind/launcher-freebsd.c OK coregrind/m_aspacemgr changes OK (aspacemgr-linux.c is clearly a bad name, but lets not rename it for now). coregrind/m_coredump/coredump-elf.c looks correct (do we have any tests for this? I don't believe we do). coregrind/m_debuginfo changes look OK. coregrind/m_debuglog.c dunno why there is a clang and gcc variant of local_sys_write_stderr. One uses SizeT the other Unt (should be Int). coregrind/m_dispatch/dispatch-arm64-freebsd.S Not sure I am qualified to review this voodoo. coregrind/m_initimg/initimg-freebsd.c looks OK coregrind/m_libcassert.c, coregrind/m_libcfile.c, coregrind/m_libcsetjmp.c OK -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp
https://bugs.kde.org/show_bug.cgi?id=485487 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #9 from Mark Wielaard --- commit dad279b80c1da4fb2c842cca9783ad0e49339ddc Author: Florian Weimer Date: Sun Apr 14 21:56:03 2024 +0200 add_hardwired_spec for ld-linux-x86-64.so.2 strcmp glibc built with -march=x86-64-v3 does not work due to ld.so strcmp https://bugs.kde.org/show_bug.cgi?id=485487 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp
https://bugs.kde.org/show_bug.cgi?id=485487 --- Comment #7 from Mark Wielaard --- There is now also an fedora eln build: https://koji.fedoraproject.org/koji/buildinfo?buildID=2437715 Since eln is build with -march=x86-64-v3 this might be a good testing environment. Please let me know if you are able to build/test a glibc against one of the above packages with this patch applied. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp
https://bugs.kde.org/show_bug.cgi?id=485487 --- Comment #6 from Mark Wielaard --- (In reply to Mark Wielaard from comment #5) > I'll add it to the next fedora rawhide valgrind build so we can test it a > bit more. There is now valgrind-3.22.0-8.fc41 with this and some other (x86-64-v3) fixes to try out. https://bodhi.fedoraproject.org/updates/FEDORA-2024-7579427715 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp
https://bugs.kde.org/show_bug.cgi?id=485487 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #5 from Mark Wielaard --- (In reply to Florian Weimer from comment #4) > Based on a further suggestion from H.J., I put the strcmp implementation > posted here into glibc and ran its strcmp test suite against it. It passes. > For such a simple implementation it should have really good coverage. So I > think the posted implementation should be okay. Yes. The license would be fine. But simpler is actually better for valgrind. The code will run on the virtual machine and will be instrumented by tools. I'll add it to the next fedora rawhide valgrind build so we can test it a bit more. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp
https://bugs.kde.org/show_bug.cgi?id=485487 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #1 from Mark Wielaard --- The proposed patch looks reasonable. Did you test it? Is there a (fedora?) glibc build that triggers this issue? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 463458] memcheck/tests/vcpu_fnfns fails when glibc is built for x86-64-v3 target
https://bugs.kde.org/show_bug.cgi?id=463458 Mark Wielaard changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Mark Wielaard --- commit a5693c1203c3a26443af13182a8082c2e9152f6c Author: Mark Wielaard Date: Sat Apr 13 14:33:19 2024 +0200 amd64: Implement VFMADD213 for Iop_MAddF32 and Iop_MAddF64 Speed up F32 and F64 FMA on amd64. Add priv/host_amd64_maddf.c implementing h_amd64_calc_MAddF32_fma4 and h_amd64_calc_MAddF64_fma4 to be used instead of the generic variants h_generic_calc_MAddF32 and h_generic_calc_MAddF64 when host has VEX_HWCAPS_AMD64_FMA4. Add fma3 and fma4 detection m_machine.c (machine_get_hwcaps). This patch also fixes the memcheck/tests/vcpu_fnfns and none/tests/amd64/fma testcases when run on a x86-64-v3 system. Patch contributed by Grazvydas Ignotas and Bruno Lathuilière https://bugs.kde.org/show_bug.cgi?id=481127 https://bugs.kde.org/show_bug.cgi?id=463463 https://bugs.kde.org/show_bug.cgi?id=463458 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 463463] none/tests/amd64/fma fails when executed under valgrind on a x86-64-v3 system
https://bugs.kde.org/show_bug.cgi?id=463463 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Mark Wielaard --- commit a5693c1203c3a26443af13182a8082c2e9152f6c Author: Mark Wielaard Date: Sat Apr 13 14:33:19 2024 +0200 amd64: Implement VFMADD213 for Iop_MAddF32 and Iop_MAddF64 Speed up F32 and F64 FMA on amd64. Add priv/host_amd64_maddf.c implementing h_amd64_calc_MAddF32_fma4 and h_amd64_calc_MAddF64_fma4 to be used instead of the generic variants h_generic_calc_MAddF32 and h_generic_calc_MAddF64 when host has VEX_HWCAPS_AMD64_FMA4. Add fma3 and fma4 detection m_machine.c (machine_get_hwcaps). This patch also fixes the memcheck/tests/vcpu_fnfns and none/tests/amd64/fma testcases when run on a x86-64-v3 system. Patch contributed by Grazvydas Ignotas and Bruno Lathuilière https://bugs.kde.org/show_bug.cgi?id=481127 https://bugs.kde.org/show_bug.cgi?id=463463 https://bugs.kde.org/show_bug.cgi?id=463458 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 481127] [PATCH] amd64: Implement VFMADD213 for Iop_MAddF32
https://bugs.kde.org/show_bug.cgi?id=481127 Mark Wielaard changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #12 from Mark Wielaard --- commit a5693c1203c3a26443af13182a8082c2e9152f6c Author: Mark Wielaard Date: Sat Apr 13 14:33:19 2024 +0200 amd64: Implement VFMADD213 for Iop_MAddF32 and Iop_MAddF64 Speed up F32 and F64 FMA on amd64. Add priv/host_amd64_maddf.c implementing h_amd64_calc_MAddF32_fma4 and h_amd64_calc_MAddF64_fma4 to be used instead of the generic variants h_generic_calc_MAddF32 and h_generic_calc_MAddF64 when host has VEX_HWCAPS_AMD64_FMA4. Add fma3 and fma4 detection m_machine.c (machine_get_hwcaps). This patch also fixes the memcheck/tests/vcpu_fnfns and none/tests/amd64/fma testcases when run on a x86-64-v3 system. Patch contributed by Grazvydas Ignotas and Bruno Lathuilière https://bugs.kde.org/show_bug.cgi?id=481127 https://bugs.kde.org/show_bug.cgi?id=463463 https://bugs.kde.org/show_bug.cgi?id=463458 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 481127] [PATCH] amd64: Implement VFMADD213 for Iop_MAddF32
https://bugs.kde.org/show_bug.cgi?id=481127 --- Comment #10 from Mark Wielaard --- Created attachment 168440 --> https://bugs.kde.org/attachment.cgi?id=168440=edit valgrind.fma_arm64.diff This is the variant of the patch that I tested. It looks good to me. How should we credit this when applying? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 481127] [PATCH] amd64: Implement VFMADD213 for Iop_MAddF32
https://bugs.kde.org/show_bug.cgi?id=481127 Mark Wielaard changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||m...@klomp.org --- Comment #9 from Mark Wielaard --- On a distro compiled with gcc -march=x86-64-v3 this patch fixes: bug #463463 none/tests/amd64/fma bug #463458 memcheck/tests/vcpu_fnfns -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 463458] memcheck/tests/vcpu_fnfns fails when glibc is built for x86-64-v3 target
https://bugs.kde.org/show_bug.cgi?id=463458 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #1 from Mark Wielaard --- Confirmed. But also seems to be fixed with the patch from https://bugs.kde.org/show_bug.cgi?id=481127 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 463456] memcheck/tests/origin6-fp fails when building for x86-64-v3 target
https://bugs.kde.org/show_bug.cgi?id=463456 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #1 from Mark Wielaard --- Confirmed. With gcc -march=x86-64-v3 memcheck is unable to track the origin. Even when build with -O0 (instead of -O). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 463463] none/tests/amd64/fma fails when executed under valgrind on a x86-64-v3 system
https://bugs.kde.org/show_bug.cgi?id=463463 --- Comment #2 from Mark Wielaard --- These seem rounding issues, fixed by https://bugs.kde.org/show_bug.cgi?id=481127 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 463463] none/tests/amd64/fma fails when executed under valgrind on a x86-64-v3 system
https://bugs.kde.org/show_bug.cgi?id=463463 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #1 from Mark Wielaard --- I am also seeing this. It seems to depend on glibc being compiled with -march=x86-64-v3. If only the fma testcase is compiled with gcc -march=x86-64-v3 but the rest of the system is not, then the testcase does pass under valgrind. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 377966] arm64 unhandled instruction dc zva
https://bugs.kde.org/show_bug.cgi?id=377966 Mark Wielaard changed: What|Removed |Added Summary|Error message said to |arm64 unhandled instruction |report |dc zva -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 479600] Segmentation fault launching the valgrind (mipsel-openwrt-linux-musl-gcc)
https://bugs.kde.org/show_bug.cgi?id=479600 Mark Wielaard changed: What|Removed |Added Summary|Segmentation fault |Segmentation fault |launching the valgrind |launching the valgrind ||(mipsel-openwrt-linux-musl- ||gcc) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 481874] Add arm64 support for FreeBSD
https://bugs.kde.org/show_bug.cgi?id=481874 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #9 from Mark Wielaard --- This is such a huge patch that I don't really know where to start. Can this be split up a little? Maybe have the changes needed to compile with clang instead of gcc separate from the rest? Or does freebsd arm64 only support building with clang? Likewise maybe separate the VEX/corgrind stuff from the tools and the tests? I randomly looked at the sbrk changes for the testcases. Which seems necessary because freebsd doesn't have sbrk on arm64 or riscv. That configure check and disabling of dw4 and pages_as_heap seem fine. In VEX. What are the priv/guest_arm64_toIR.c changes for? You need LibVEX_GuestARM64_put_nzcv_c to signal syscall success/failure. I am not fully clear what the guest_SETC is for. The guest_SC_CLASS seems to be to determine how syscall numbers are passed. Would it make sense to only include those fields, and padding, for freebsd? -- You are receiving this mail because: You are watching all bug changes.
[knights] [Bug 429654] Cant's disable voice
https://bugs.kde.org/show_bug.cgi?id=429654 --- Comment #3 from Mark Capella --- I was hoping to patch this but it looks already corrected here: https://invent.kde.org/games/knights/-/commit/bc828eb7e7ec50392b0bfe9118bb367d84d540a7 If confirmed can we close? My failing build as delivered in my distro & and my succeeding clean build off kdesrc (no patches of my own). -- You are receiving this mail because: You are watching all bug changes.
[knights] [Bug 429654] Cant's disable voice
https://bugs.kde.org/show_bug.cgi?id=429654 Mark Capella changed: What|Removed |Added CC||markcape...@twcny.rr.com --- Comment #2 from Mark Capella --- Created attachment 168038 --> https://bugs.kde.org/attachment.cgi?id=168038=edit Before / After -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484838] New: Clicking on notifications occasionally crashes Plasmashell
https://bugs.kde.org/show_bug.cgi?id=484838
Bug ID: 484838
Summary: Clicking on notifications occasionally crashes
Plasmashell
Classification: Plasma
Product: plasmashell
Version: 6.0.3
Platform: openSUSE
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: Notifications
Assignee: plasma-b...@kde.org
Reporter: m...@leyva.me
CC: k...@privat.broulik.de
Target Milestone: 1.0
SUMMARY
After unlocking my desktop, I tried to click on the notification applet which
resulted in some stutter before Plasmashell crashed. I'm unsure if the
following steps can reproduce it.
STEPS TO REPRODUCE
1. Lock desktop
2. Unlock desktop
3. Click on notification applet if present
OBSERVED RESULT
Notification applet opens without crashing Plasmashell
EXPECTED RESULT
Plasmashell crashes.
SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240329
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Kernel Version: 6.8.1-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B450M DS3H
ADDITIONAL INFORMATION
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
tid =
ret = 0
pd =
old_mask = {__val = {94513001237136}}
ret =
#1 0x7effc4894a73 in __pthread_kill_internal (signo=11,
threadid=) at pthread_kill.c:78
#2 0x7effc4841176 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
ret =
#3 0x7effc7ad3b93 in KCrash::defaultCrashHandler(int) (sig=11) at
/usr/src/debug/kcrash-6.0.0/src/kcrash.cpp:586
data = { = {_vptr.MetadataWriter =
0x7effc7ad87d8 }, argv = {_M_elems = {0x0,
0x7effc7ad63f9 "--glrenderer", 0x55f5861461c0 "NVIDIA GeForce GTX 1660
SUPER/PCIe/SSE2", 0x7effc7ad6406 "--platform", 0x55f5936e58b0 "wayland",
0x7effc7ad6437 "--appname", 0x55f585ddbb30 "plasmashell", 0x7effc7ad6441
"--apppath", 0x55f585dd0120 "/usr/bin", 0x7effc7ad644e "--signal",
0x7ffd874c7626 "11", 0x7effc7ad645c "--pid", 0x7ffd874c7630 "2861",
0x7effc7ad6462 "--appversion", 0x55f585dd2b70 "6.0.3", 0x7effc7ad646f
"--programname", 0x55f584f37a18 "", 0x7effc7ad647d
"--bugaddress", 0x55f585dd8a90 "sub...@bugs.kde.org", 0x0 }},
argc = 19, m_writer = 0x7ffd874c75d0}
platformName = {d = {d = 0x55f5936e58a0, ptr = 0x55f5936e58b0
"wayland", size = 7}, static _empty = 0 '\000'}
about = 0x55f586148350
argv = 0x7ffd874c7658
ini = { = {_vptr.MetadataWriter =
0x7effc7ad8808 }, writable = false, fd
= 68}
sigtxt = "11\000zL\207\375\177\000"
pidtxt = "2861\000\177\000\000\001vL\207\375\177\000\000\002\000\000"
argc =
crashRecursionCounter = 2
#4 0x7effc4841240 in () at /lib64/libc.so.6
#5 0x7effc64aa3ea in QQmlContextData::contextObject() const
(this=, this=) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.3/src/qml/qml/qqmlcontextdata_p.h:128
contextObject =
#6 QQmlContextData::ContextGuard::objectDestroyedImpl(QQmlGuardImpl*)
(impl=0x55f595691878) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.3/src/qml/qml/qqmlcontextdata_p.h:455
contextObject =
#7 0x7effc64b6e72 in QQmlData::destroyed(QObject*) (this=0x55f58db318c0,
object=0x55f58db318a0) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.3/src/qml/qml/qqmlengine.cpp:1489
guard =
binding =
signalHandler =
#8 0x7effc51cf702 in QObject::~QObject() (this=0x55f58db318a0,
this=) at
/usr/src/debug/qtbase-everywhere-src-6.6.3/src/corelib/kernel/qobject.cpp:1065
d = 0x55f595663650
sharedRefcount = 0x55f594164190
cd =
#9 0x7effc6c006e5 in
QQmlPrivate::QQmlElement::~QQmlElement() (this=0x55f58db318a0,
this=) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.3/src/qml/qml/qqmlprivate.h:99
#10 QQmlPrivate::QQmlElement::~QQmlElement()
(this=0x55f58db318a0, this=) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.3/src/qml/qml/qqmlprivate.h:99
#11 0x7effc51caba7 in QObject::event(QEvent*) (this=0x55f58db318a0,
e=0x55f594c881d0) at
/usr/src/debug/qtbase-everywhere-src-6.6.3/src/corelib/kernel/qobject.cpp:1424
#12 0x7effc71c1a7e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55f58db318a0, e=0x55f594c881d0) at
/usr/src/debug/qtbase-everywhere-src-6.6.3/src/widgets/kernel/qapplication.cpp:3296
consumed = false
filtered = false
#13 0x7effc5187998 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55f58db318a0, event=0x55f594c881d0) at
/usr/src/debug/qtbase-everywhere-src-6.6.3/src/corelib/kernel/qcoreapplication.cpp:1121
selfRequired = true
result =
[plasma-browser-integration] [Bug 484681] New: Unable to log in to bank website when kde plasma Chrome extension is enabled
https://bugs.kde.org/show_bug.cgi?id=484681 Bug ID: 484681 Summary: Unable to log in to bank website when kde plasma Chrome extension is enabled Classification: Plasma Product: plasma-browser-integration Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Chrome Assignee: k...@privat.broulik.de Reporter: mark.richa...@gmail.com Target Milestone: --- SUMMARY With the Plasma Chrome extension installed (which installs by default on Fedora when you install the KDE environment and Chrome), I am unable to sign in to my bank website. This error does not occur on Chrome when running in Gnome on the same computer. STEPS TO REPRODUCE 1. Install an up-to-date version of Fedora 39 2. Install Google Chrome 3. Log into bank website OBSERVED RESULT The website login fails with a 403 error shown in the console. The login works on the same computer in Gnome. Turning off the KDE Chrome extension resolves the issue. EXPECTED RESULT The login should succeed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 39 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 484426] aarch64: 0.5 gets rounded to 0
https://bugs.kde.org/show_bug.cgi?id=484426 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #6 from Mark Wielaard --- This looks good to me. But I have not tested it. And I have to trust you on the emit code (too lazy to look up the instr enc) It looks like none/tests/arm64/fp_and_simd.c already has tests for both frinti and frinta. Did they just happen to work just fine with the existing code? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468180] Plasmashell crashed in QQuickTransition::prepare() after closing a notification
https://bugs.kde.org/show_bug.cgi?id=468180 Mark changed: What|Removed |Added CC|m...@leyva.me | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481622] plasmashell crashes when multiple wallpapers are applied (without closing the selection applet)
https://bugs.kde.org/show_bug.cgi?id=481622 --- Comment #8 from Mark Rooks --- Issue mo longer occurs for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481622] plasmashell crashes when multiple wallpapers are applied (without closing the selection applet)
https://bugs.kde.org/show_bug.cgi?id=481622 --- Comment #7 from Mark Rooks --- Not sure if I put this up earlier but I have Qt6 installed. The issue no longer occurs. Could it be related? yes possibly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481622] plasmashell crashes when multiple wallpapers are applied (without closing the selection applet)
https://bugs.kde.org/show_bug.cgi?id=481622 --- Comment #6 from Mark Rooks --- I'm sorry I just don't have time at the moment, this is my prod. machine and is handling a bunch of other workloads. Doesn't this mean I'm on plasma6? mrooks@rooksy:~> kded5 --version Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. QSocketNotifier: Can only be used with threads started with QThread kded5 5.115.0 mrooks@rooksy:~> kded6 --version kded6 6.0.0 I have a couple of suma based reproducers for work to do over the weekend and will then enure I am running version 6 of Plasma. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480248] Plasma shell crashed with signal 11 (segfault)
https://bugs.kde.org/show_bug.cgi?id=480248 Mark Rooks changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 from Mark Rooks --- It's TW, like Rawhide. It changes almost every day. The issue no longer occurs on the current QT version. I am not going to bother raising bugs against TW any more. It's futile. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 484002] Add suppression for invalid read in glibc's __wcpncpy_avx2() via wcsxfrm()
https://bugs.kde.org/show_bug.cgi?id=484002
--- Comment #5 from Mark Wielaard ---
Comment on attachment 167483
--> https://bugs.kde.org/attachment.cgi?id=167483
first attempt at a patch
Very nice.
Before the patch:
$ ~/src/valgrind/vg-in-place ./t
==66177== Memcheck, a memory error detector
==66177== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==66177== Using Valgrind-3.23.0.GIT and LibVEX; rerun with -h for copyright
info
==66177== Command: ./t
==66177==
0x1ffefff9f0 0x1ffefff9e0
3
0x4a58480 0x1ffefff9e0
3
0x4a584d0 0x1ffefff9e0
==66177== Invalid read of size 32
==66177==at 0x49D6A2E: __wcpncpy_avx2 (strncpy-avx2.S:85)
==66177==by 0x4938560: wcsxfrm_l (strxfrm_l.c:679)
==66177==by 0x4012A1: main (t.c:25)
==66177== Address 0x4a584d0 is 0 bytes inside a block of size 16 alloc'd
==66177==at 0x484278B: malloc (vg_replace_malloc.c:446)
==66177==by 0x401258: main (t.c:22)
==66177==
3
==66177==
==66177== HEAP SUMMARY:
==66177== in use at exit: 0 bytes in 0 blocks
==66177== total heap usage: 3 allocs, 3 frees, 1,056 bytes allocated
==66177==
==66177== All heap blocks were freed -- no leaks are possible
==66177==
==66177== For lists of detected and suppressed errors, rerun with: -s
==66177== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
After the patch:
$ ~/src/valgrind/vg-in-place ./t
==67120== Memcheck, a memory error detector
==67120== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==67120== Using Valgrind-3.23.0.GIT and LibVEX; rerun with -h for copyright
info
==67120== Command: ./t
==67120==
0x1ffefff9e0 0x1ffefff9d0
3
0x4a58480 0x1ffefff9d0
3
0x4a584d0 0x1ffefff9d0
3
==67120==
==67120== HEAP SUMMARY:
==67120== in use at exit: 0 bytes in 0 blocks
==67120== total heap usage: 3 allocs, 3 frees, 1,056 bytes allocated
==67120==
==67120== All heap blocks were freed -- no leaks are possible
==67120==
==67120== For lists of detected and suppressed errors, rerun with: -s
==67120== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Implementation looks correct. Two small comments.
+ /* This checks for overlap after copying, unavoidable without */ \
+ /* pre-counting length... should be ok */ \
+ /* +4 because sizeof(wchar_t) == 4 */ \
+ SizeT srclen = ((m < n) ? m+1 : n)*4; \
+ RECORD_COPY(srclen); \
I found the comment a little confusing until I understood that the +4 really
meant *4.
+ RECORD_OVERLAP_ERROR("wcspcpy", dst_orig, src_orig, 0); \
^wcpncpy
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 484002] Add suppression for invalid read in glibc's __wcpncpy_avx2() via wcsxfrm()
https://bugs.kde.org/show_bug.cgi?id=484002 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #2 from Mark Wielaard --- We already have an override for wcsncpy and stpncpy. But not wcpncpy. See shared/vg_replace_strmem.c -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 483791] Weather Report Widget occasionally crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=483791
--- Comment #2 from Mark ---
Managed to see it again. I got a better stack trace this time around. It
appears I was missing some debug sources.
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
tid =
ret = 0
pd =
old_mask = {__val = {94298586877808}}
ret =
#1 0x7f7b45694a73 in __pthread_kill_internal (signo=11,
threadid=) at pthread_kill.c:78
#2 0x7f7b45641176 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
ret =
#3 0x7f7b48a88b93 in KCrash::defaultCrashHandler(int) (sig=11) at
/usr/src/debug/kcrash-6.0.0/src/kcrash.cpp:586
data = { = {_vptr.MetadataWriter =
0x7f7b48a8d7d8 }, argv = {_M_elems = {0x0,
0x7f7b48a8b3f9 "--glrenderer", 0x55c399c5ef10 "NVIDIA GeForce GTX 1660
SUPER/PCIe/SSE2", 0x7f7b48a8b406 "--platform", 0x55c399b9ccc0 "wayland",
0x7f7b48a8b437 "--appname", 0x55c3998fa320 "plasmashell", 0x7f7b48a8b441
"--apppath", 0x55c3998f9da0 "/usr/bin", 0x7f7b48a8b44e "--signal",
0x7fffe358d0e6 "11", 0x7f7b48a8b45c "--pid", 0x7fffe358d0f0 "22641",
0x7f7b48a8b462 "--appversion", 0x55c399c5ef80 "6.0.2", 0x7f7b48a8b46f
"--programname", 0x55c3988c0a58 "", 0x7f7b48a8b47d
"--bugaddress", 0x55c399c60f70 "sub...@bugs.kde.org", 0x0 }},
argc = 19, m_writer = 0x7fffe358d090}
platformName = {d = {d = 0x55c399b9ccb0, ptr = 0x55c399b9ccc0
"wayland", size = 7}, static _empty = 0 '\000'}
about = 0x55c399c60e90
argv = 0x7fffe358d118
ini = { = {_vptr.MetadataWriter =
0x7f7b48a8d808 }, writable = false, fd
= 116}
sigtxt = "11\000\324X\343\377\177\000"
pidtxt = "22641\000\000\000;4\260F{\177\000\000`\3627\241"
argc =
crashRecursionCounter = 2
#4 0x7f7b45641240 in () at /lib64/libc.so.6
#5 QHashPrivate::hash(unsigned long, unsigned long) (seed=Python Exception
: Cannot access memory at address 0x1bba5850fa1e100b
#6 qHash(unsigned long long, unsigned long) (seed=Python Exception : Cannot access memory at address 0x1bba5850fa1e100b
#7 qHash(QObject* (*)(QObject*), unsigned long) (seed=Python Exception : Cannot access memory at address 0x1bba5850fa1e100b
#8 QHashPrivate::calculateHash(QObject* (*
const&)(QObject*), unsigned long) (seed=Python Exception : Cannot access memory at address 0x1bba5850fa1e100b
#9 QHashPrivate::Data
>::findBucket(QObject* (* const&)(QObject*)) const [clone .isra.0]
(this=0x1bba5850fa1e0ff3, key=) at
/usr/include/qt6/QtCore/qhash.h:683
hash =
bucket = {span = , index = }
#10 0x7f7b4747a2b6 in QHashPrivate::Data >::findNode(QObject* (* const&)(QObject*)) const
(key=, this=) at
/usr/include/qt6/QtCore/qhash.h:700
bucket = {span = , index = }
n =
v =
rv = 0x0
data =
#11 QHash::valueImpl(QObject* (*
const&)(QObject*)) const (this=, key=:
) at /usr/include/qt6/QtCore/qhash.h:1037
n =
v =
rv = 0x0
data =
#12 QHash::value(QObject* (*
const&)(QObject*)) const (key=: ,
this=) at /usr/include/qt6/QtCore/qhash.h:1046
v =
rv = 0x0
data =
#13 resolveAttachedProperties (create=false, object=0x55c3a73f93e0,
data=0x7f7b477287b0 , pf=0x7f7b38186320
) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.2/src/qml/qml/qqml.cpp:90
rv = 0x0
data =
#14 qmlAttachedPropertiesObject(QObject*, QObject* (*)(QObject*), bool)
(object=0x55c3a73f93e0, func=0x7f7b38186320
, create=false) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.2/src/qml/qml/qqml.cpp:122
data =
#15 0x7f7b38188efa in qmlAttachedPropertiesObject(QObject
const*, bool) (obj=, create=create@entry=false) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.2/src/qml/qml/qqml.h:670
func = 0x7f7b38186320
#16 0x7f7b3818c036 in attachedLayoutObject(QQuickItem*, bool)
(create=false, item=) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.2/src/quicklayouts/qquicklayout_p.h:377
#17 QQuickGridLayoutItem::sizePolicy(Qt::Orientation) const
(this=0x55c3a04eb810, orientation=Qt::Horizontal) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.2/src/quicklayouts/qquickgridlayoutengine_p.h:68
#18 0x7f7b46aa2e87 in QGridLayoutItem::stretchFactor(Qt::Orientation) const
(orientation=, this=) at
/usr/src/debug/qtbase-everywhere-src-6.6.2/src/gui/util/qgridlayoutengine.cpp:533
policy = {i = }
stretch =
#19 QGridLayoutItem::stretchFactor(Qt::Orientation) const (this=, orientation=) at
/usr/src/debug/qtbase-everywhere-src-6.6.2/src/gui/util/qgridlayoutengine.cpp:527
stretch =
#20 0x7f7b46aad49d in QGridLayoutEngine::fillRowData(QGridLayoutRowData*,
double const*, double const*, Qt::Orientat
[kwin] [Bug 438315] Kwin crashed in KWin::FocusChain::isUsableFocusCandidate()
https://bugs.kde.org/show_bug.cgi?id=438315 Mark changed: What|Removed |Added CC|m...@leyva.me | -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 483791] Weather Report Widget occasionally crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=483791 Mark changed: What|Removed |Added CC||m...@leyva.me -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 483791] New: Weather Report Widget occasionally crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=483791 Bug ID: 483791 Summary: Weather Report Widget occasionally crashes plasmashell Classification: Plasma Product: kdeplasma-addons Version: 6.0.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Weather Assignee: plasma-b...@kde.org Reporter: m...@leyva.me Target Milestone: --- Created attachment 167340 --> https://bugs.kde.org/attachment.cgi?id=167340=edit Backtrace SUMMARY Occasionally, clicking on weather report widget in the taskbar causes plasmashell to crash. Unsure how to reproduce, but I have seen it a few times. STEPS TO REPRODUCE 1. Use plasmashell. 2. Click on the weather report widget. 3. Crash. OBSERVED RESULT Plasmashell crashes. EXPECTED RESULT Plasmashell does not crash and the weather report widget opens. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240314 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B450M DS3H ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 483711] -m32 flag breaks Valgrind
https://bugs.kde.org/show_bug.cgi?id=483711
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #5 from Mark Wielaard ---
Various x86_64 (amd64) builders on builder.sourceware.org are docker based. I
think valgrind works fine under a linux container/docker setup. But none of
them run x86 (32bit).
The comments around the assert read:
case VG_TRC_INVARIANT_FAILED:
/* This typically happens if, after running generated code,
it is detected that host CPU settings (eg, FPU/Vector
control words) are not as they should be. Vex's code
generation specifies the state such control words should
be in on entry to Vex-generated code, and they should be
unchanged on exit from it. Failure of this assertion
usually means a bug in Vex's code generation. */
//{ UInt xx;
// __asm__ __volatile__ (
// "\t.word 0xEEF12A10\n" // fmrx r2,fpscr
// "\tmov %0, r2" : "=r"(xx) : : "r2" );
// VG_(printf)(" new fpscr = %08x\n", xx);
//}
vg_assert2(0, "VG_(scheduler), phase 3: "
"run_innerloop detected host "
"state invariant failure", trc);
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 482943] Missing setting for notification sounds
https://bugs.kde.org/show_bug.cgi?id=482943 --- Comment #11 from Mark S --- I've just now confirmed that unchecking: "Play audio feedback for changes to: [ ] audio volume" checkbox correctly ends the audio feedback system sound for volume changes. I'm not sure what to do about the Status on this. My bug was generally that I thought there was no way at all to turn off the volume control sound, but this shows there is. But there seems to be some comments about adding a slider somewhere. I'll leave the Status at REPORTED for now -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482943] Missing setting for notification sounds
https://bugs.kde.org/show_bug.cgi?id=482943 --- Comment #9 from Mark S --- Calling these "feedback" is ambiguous and confusing, I'd prefer KDE call the noises that the volume control makes "system sounds" or "sound effects". The term feedback is too general. The fact those feedback checkboxes are in the configure volume panel conveys what feedback means so it's probably okay in this case. I wrote this bug because the volume sound effect didn't seem to obey the "system sounds" volume slider or mute. When I mute the system sounds in pulseaudio volume control I expect the volume change "bong" to go away, that is, to me the volume effect IS a system sound. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 471222] support tracking of file descriptors being double closed
https://bugs.kde.org/show_bug.cgi?id=471222 Mark Wielaard changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #18 from Mark Wielaard --- commit 6a28e665f8dd7c031aef5aa0eaa4acbbd8ba27a9 Author: Alexandra Hájková Date: Wed Feb 28 09:02:15 2024 +0100 With --track-fds=yes warn when file descriptor is closed a second time We moved the record_fd_close call from POST to PRE sys_close handler, because the POST handler is only called on success. Even if the close syscall fails the file descriptor is still really closed/invalid. In the PRE handler the file descriptor is about to be closed, but hasn't been yet so we can capture also the description. This patch add new field fd_closed to OpenFd structure to record if the file descriptor was already closed. We now capture a backtrace when closing file descriptors to be able to print it in a case of a double close. Always add '<' brackets '>' around "unbound" in the description for consistency. getsockdetails now takes and returns a buffer describing the socket because we want to record it, not just print it. Note that close_range is handled similar to closing each descriptor individually. But the case when the close_range is called with an infinite end (~0U) is treated special. Add a new record_fd_close_range function which handles close_range with an infinite end so double close by close_range isn't an error because we don't want to loop over such a wide range. Add a new test cases: - none/tests/socket_close.vgtest - tests double closing a socket - none/tests/double_close_range.vgtest - uses close_range to double close the file descriptors - none/tests/file_dclose.vgtest - double closing regular file with regular close syscall https://bugs.kde.org/show_bug.cgi?id=471222 Co-Authored-By: Mark Wielaard -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 471222] support tracking of file descriptors being double closed
https://bugs.kde.org/show_bug.cgi?id=471222 --- Comment #17 from Mark Wielaard --- (In reply to Paul Floyd from comment #14) > On second thoughts, isn't the fdleak_ipv4 double close message expected? Yes, it is. It also failed for me locally. I added it to the none/tests/fdleak_ipv4.stderr.exp file. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 471222] support tracking of file descriptors being double closed
https://bugs.kde.org/show_bug.cgi?id=471222 --- Comment #16 from Mark Wielaard --- (In reply to Paul Floyd from comment #13) > I had to modify double_close_range.c and socket_close.c like this > > #if defined(__linux__) > #include > #endif > > I get 3 new failures > > The first one has two things. Line number changes because of the Linux > header. close/_close needs filtering. I added that to none/tests/double_close_range.c none/tests/socket_close.c doesn't need it, since it doesn't use any of the constants. I did it so the expected line numbers stay the same (removed two unused headers, added an extra line of whitespace) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 471222] support tracking of file descriptors being double closed
https://bugs.kde.org/show_bug.cgi?id=471222 --- Comment #15 from Mark Wielaard --- I needed the following on a system that didn't have close_range: diff --git a/none/tests/Makefile.am b/none/tests/Makefile.am index f56eb7faab67..a37bb27257a6 100644 --- a/none/tests/Makefile.am +++ b/none/tests/Makefile.am @@ -282,8 +282,11 @@ check_PROGRAMS = \ process_vm_readv_writev \ sigprocmask \ socket_close \ - file_dclose \ - double_close_range + file_dclose + +if HAVE_CLOSE_RANGE + check_PROGRAMS += double_close_range +endif if HAVE_NESTED_FUNCTIONS check_PROGRAMS += nestedfns -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 483373] New: baloo file extractor crashes multiple times on start up
https://bugs.kde.org/show_bug.cgi?id=483373 Bug ID: 483373 Summary: baloo file extractor crashes multiple times on start up Classification: Frameworks and Libraries Product: frameworks-baloo Version: 5.115.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: roo...@gmail.com Target Milestone: --- Application: baloo_file_extractor (5.115.0) Qt Version: 5.15.12 Frameworks Version: 5.115.0 Operating System: Linux 6.7.7-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.10 [CoredumpBackend] -- Information about the crash: After starting up, every time, through many many updates, the crash happens every time. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted PID: 1400 (baloo_file_extr) UID: 1000 (mrooks) GID: 1000 (mrooks) Signal: 6 (ABRT) Timestamp: Wed 2024-03-13 06:21:28 AEST (39s ago) Command Line: /usr/libexec/baloo_file_extractor Executable: /usr/libexec/baloo_file_extractor Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-baloo_file-22196.scope Unit: user@1000.service User Unit: app-gnome-baloo_file-22196.scope Slice: user-1000.slice Owner UID: 1000 (mrooks) Boot ID: b55fb286a6bf40d29cf8192f1e3fc5ce Machine ID: ae64c79858954d6fbd05339e10667247 Hostname: rooksy Storage: /var/lib/systemd/coredump/core.baloo_file_extr.1000.b55fb286a6bf40d29cf8192f1e3fc5ce.1400.171027488800.zst (present) Size on Disk: 1.3M Message: Process 1400 (baloo_file_extr) of user 1000 dumped core. Stack trace of thread 1400: #0 0x7f62344949ec __pthread_kill_implementation (libc.so.6 + 0x949ec) #1 0x7f6234441176 raise (libc.so.6 + 0x41176) #2 0x7f6235b15d9a _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x7d9a) #3 0x7f6234441240 __restore_rt (libc.so.6 + 0x41240) #4 0x7f62344949ec __pthread_kill_implementation (libc.so.6 + 0x949ec) #5 0x7f6234441176 raise (libc.so.6 + 0x41176) #6 0x7f6234428917 abort (libc.so.6 + 0x28917) #7 0x7f6234a73d4d n/a (liblmdb-0.9.30.so + 0x5d4d) #8 0x7f6234a72158 n/a (liblmdb-0.9.30.so + 0x4158) #9 0x7f6234a7f8d6 n/a (liblmdb-0.9.30.so + 0x118d6) #10 0x7f6234a77103 n/a (liblmdb-0.9.30.so + 0x9103) #11 0x7f6234a78d07 n/a (liblmdb-0.9.30.so + 0xad07) #12 0x7f6234a7b816 mdb_cursor_put (liblmdb-0.9.30.so + 0xd816) #13 0x7f6234a7c757 mdb_put (liblmdb-0.9.30.so + 0xe757) #14 0x7f6235b32296 _ZN5Baloo9PostingDB3putERK10QByteArrayRK7QVectorIyE (libKF5BalooEngine.so.5 + 0x18296) #15 0x7f6235b3e827 _ZN5Baloo16WriteTransaction6commitEv (libKF5BalooEngine.so.5 + 0x24827) #16 0x7f6235b34c69 _ZN5Baloo11Transaction6commitEv (libKF5BalooEngine.so.5 + 0x1ac69) #17 0x55f81d89aeac n/a (baloo_file_extractor + 0x15eac) #18 0x7f6234f29a52 _ZN9QtPrivate15QSlotObjectBase4callEP7QObjectPPv (libQt5Core.so.5 + 0x329a52) #19 0x7f6234f195fb _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x3195fb) #20 0x7f6234eed938 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2ed938) #21 0x7f6234f45c69 _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x345c69) #22 0x7f6234f4654c timerSourceDispatch (libQt5Core.so.5 + 0x34654c) #23 0x7f6233b13f30 n/a (libglib-2.0.so.0 + 0x5bf30) #24 0x7f6233b15b58 n/a (libglib-2.0.so.0 + 0x5db58) #25 0x7f6233b1620c g_main_context_iteration (libglib-2.0.so.0 + 0x5e20c) #26 0x7f6234f46876 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x346876) #27 0x7f6234eec3cb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2ec3cb) #28 0x7f6234ef4860 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2f4860) #29 0x55f81d890e33 n/a (baloo_file_extractor + 0xbe33) #30 0x7f623442a1f0 __libc_start_call_main (libc.so.6 + 0x2a1f0) #31 0x7f623442a2b9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a2b9) #32 0x55f81d890f65 n/a (baloo_file_extractor + 0xbf65) Stack trace of thread
[kde] [Bug 482943] System sounds play even when muted in PulseAudio Volume Control on KDE6.0.1
https://bugs.kde.org/show_bug.cgi?id=482943 --- Comment #3 from Mark S --- >If you go to System Settings Audio, you'll see a thing named "Notification >sounds". If that's not muted or set to 0%, do that. >Does that fix the issue? I'm not sure what you mean, my System Settings in Fedora 40 when you put "sound" in the search tool only shows "System Sounds" and "Sound" as related to this problem. The former has a check box labeled "Enable notification sounds" which is not checked. The Sounds selection just shows the Playback Devices page, there's nothing there to turn system sounds or notification sounds on or off. There's just the volume slider for Speakers there and the configuration menu, "Test" button and "Balance" control. The HDMI card shows as "inactive" -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482943] System sounds play even when muted in PulseAudio Volume Control on KDE6.0.1
https://bugs.kde.org/show_bug.cgi?id=482943 --- Comment #1 from Mark S --- Alsa, pipewire and wireplumber info API: ALSA v: k6.8.0-0.rc6.49.fc40.x86_64 status: kernel-api Server-1: PipeWire v: 1.0.3 status: active with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482943] New: System sounds play even when muted in PulseAudio Volume Control on KDE6.0.1
https://bugs.kde.org/show_bug.cgi?id=482943 Bug ID: 482943 Summary: System sounds play even when muted in PulseAudio Volume Control on KDE6.0.1 Classification: I don't know Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mspuban...@fastmail.us Target Milestone: --- SUMMARY *** I system-upgraded to Fedora 40 develop which upgraded my laptop to KDE 6.0.1 I have a problem where I can’t turn off the “bong” system sounds that occurs when the desktop volume is changed by either rolling the mouse wheel when hovering over the volume or sliding the volume. I’ve set the System Sounds in pavucontrol (pulseaudio volume control) to 0% volume and muted it but the sounds still occurs. I also unchecked the “Enable notification sounds” checkbox in “global themes”-> "System Sounds" but I think that’s unrelated to System Sounds. qpwgraph shows that when the sound is produced it's coming from libcanberra *** STEPS TO REPRODUCE 1. Install Fedora 40 Develop OS, upgrade via 'dnf upgrade' afterwards to KDE 6.0.1 2. Turn off System Sounds in Pulseaudio Volume Control Playback tab by muting "System Sounds" 3. Change desktop Volume via the taskbar volume (roll mouse wheel over the widget or slide slider) OBSERVED RESULT Changing the desktop volume via the volume widget results in a system sound even if system sounds was muted EXPECTED RESULT System Sounds should not occur if System Sounds is muted SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Kernel 6.8.0-0.rc6.49.fc40.x86_64 MSI Bravo 15 A4DDR laptop Wayland -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 482358] Feature Request: Add --track-fds=error
https://bugs.kde.org/show_bug.cgi?id=482358 --- Comment #2 from Mark Wielaard --- See also https://bugs.kde.org/show_bug.cgi?id=362680 which contains a description how to resurrect CoreErrors (but no patch yet?) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 482358] Feature Request: Add --track-fds=error
https://bugs.kde.org/show_bug.cgi?id=482358 Mark Wielaard changed: What|Removed |Added CC||ahajk...@redhat.com, ||m...@klomp.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480248] Plasma shell crashed with signal 11 (segfault)
https://bugs.kde.org/show_bug.cgi?id=480248 --- Comment #4 from Mark Rooks --- Tumbleweed is an "evergeeen" distro. Releases come every other day or daily. What "after some new patches were applied" means, is that on the date that I raised this bug, I applied some updates to the system using: zypper dup, or zypper up, depending on whether it was just updates to rpms or also an update to the distro version. You can see the changelogs for yourself. I was just raising it bc it was an easy thing to do. I don't really care if you fix it or not TBH. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 471222] support tracking of file descriptors being double closed
https://bugs.kde.org/show_bug.cgi?id=471222 --- Comment #8 from Mark Wielaard --- BTW. In that testcase memcheck/tests/freebsd/close_range.c it has: /* It looks like close_range was initially implemented for FreeBSD 13 * but without CLOSE_RANGE_CLOEXEC * That implementation got back ported to FreeBSD 12.2 * And then CLOSE_RANGE_CLOEXEC added to 13 but not backported * so 12 has close_range but not CLOSE_RANGE_CLOEXEC */ #if !defined(CLOSE_RANGE_CLOEXEC) #define CLOSE_RANGE_CLOEXEC 1 #endif Shouldn't that be 0 instead of 1? Real CLOSE_RANGE_CLOEXEC is 4. What does 1 mean in this case? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 471222] support tracking of file descriptors being double closed
https://bugs.kde.org/show_bug.cgi?id=471222 --- Comment #7 from Mark Wielaard --- I forgot about freebsd, sorry. But I see the close_range wrappers are almost identical, so that is good. We can adapt them together. And freebsd already has ./memcheck/tests/freebsd/close_range.vgtest Lets see if we can make that a generic testcase, I see there is already a close_range configure check. I note that freebsd also has a closefrom syscall plus wrapper. But this doesn't seem to implement file descriptor tracking? It should probably use the newly introduced record_fd_close_range. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 481698] New: Discover crashed when hitting the X button
https://bugs.kde.org/show_bug.cgi?id=481698 Bug ID: 481698 Summary: Discover crashed when hitting the X button Classification: Applications Product: Discover Version: 5.27.10 Platform: Unlisted Binaries OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: roo...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.27.10) Qt Version: 5.15.12 Frameworks Version: 5.115.0 Operating System: Linux 6.7.5-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.10 [CoredumpBackend] -- Information about the crash: Did a dup last night. Started discover, closed it Opened discover again, clicked on a package and clicked close - Crash occurred Opened discover again, clicked on a package and clicked close - Crash occurred Tumbleweed The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Trace/breakpoint trap PID: 3258 (plasma-discover) UID: 1000 (mrooks) GID: 1000 (mrooks) Signal: 5 (TRAP) Timestamp: Fri 2024-02-23 07:08:18 AEST (38s ago) Command Line: /usr/bin/plasma-discover Executable: /usr/bin/plasma-discover Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-org.kde.discover-3258.scope Unit: user@1000.service User Unit: app-gnome-org.kde.discover-3258.scope Slice: user-1000.slice Owner UID: 1000 (mrooks) Boot ID: 4756d8375bff45b5889c7d4873b5dbd7 Machine ID: ae64c79858954d6fbd05339e10667247 Hostname: rooksy Storage: /var/lib/systemd/coredump/core.plasma-discover.1000.4756d8375bff45b5889c7d4873b5dbd7.3258.170863609800.zst (present) Size on Disk: 197.3M Message: Process 3258 (plasma-discover) of user 1000 dumped core. Stack trace of thread 3276: #0 0x7fefde71dc77 g_log_structured_array (libglib-2.0.so.0 + 0x65c77) #1 0x7fefde71e0ce g_log_default_handler (libglib-2.0.so.0 + 0x660ce) #2 0x7fefde71e340 g_logv (libglib-2.0.so.0 + 0x66340) #3 0x7fefde71e5ef g_log (libglib-2.0.so.0 + 0x665ef) #4 0x7fefde5bb1b7 n/a (libgio-2.0.so.0 + 0x1541b7) #5 0x7fefde5bb265 n/a (libgio-2.0.so.0 + 0x154265) #6 0x7fefde713f30 n/a (libglib-2.0.so.0 + 0x5bf30) #7 0x7fefde715b58 n/a (libglib-2.0.so.0 + 0x5db58) #8 0x7fefde71620c g_main_context_iteration (libglib-2.0.so.0 + 0x5e20c) #9 0x7fefde716251 n/a (libglib-2.0.so.0 + 0x5e251) #10 0x7fefde74249e n/a (libglib-2.0.so.0 + 0x8a49e) #11 0x7fefdf692bb2 start_thread (libc.so.6 + 0x92bb2) #12 0x7fefdf71400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 3258: #0 0x7fefdf68effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x7fefdf691d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x7fefdff09afb _ZN21QWaitConditionPrivate4waitE14QDeadlineTimer (libQt5Core.so.5 + 0x109afb) #3 0x7fefdff06997 _ZN18QThreadPoolPrivate11waitForDoneERK14QDeadlineTimer (libQt5Core.so.5 + 0x106997) #4 0x7fefdff06d87 _ZN18QThreadPoolPrivate11waitForDoneEi (libQt5Core.so.5 + 0x106d87) #5 0x7fefdff06e3c _ZN11QThreadPoolD2Ev (libQt5Core.so.5 + 0x106e3c) #6 0x7fefb5a3c290 n/a (flatpak-backend.so + 0x22290) #7 0x7fefb5a3c5b9 n/a (flatpak-backend.so + 0x225b9) #8 0x7fefe22200de _ZN14ResourcesModelD2Ev (libDiscoverCommon.so + 0x440de) #9 0x7fefe22201d9 _ZN14ResourcesModelD0Ev (libDiscoverCommon.so + 0x441d9) #10 0x7fefe01194b7 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x3194b7) #11 0x7fefe1ba51ae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x1a51ae) #12 0x7fefe00ed938 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2ed938) #13 0x7fefe00f0f31 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2f0f31) #14 0x7fefe00f487a _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2f487a) #15 0x562ebbd792c0 n/a (plasma-discover + 0x192c0) #16 0x7fefdf62a1f0 __libc_start_call_main (libc.so.6 + 0x2a1f0) #17 0x7fefdf62a2b9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a2b9) #18 0x562ebbd79cb5 n/a (plasma-discover +
[plasmashell] [Bug 481622] plasmashell crashes when multiple wallpapers are applied (without closing the selection applet)
https://bugs.kde.org/show_bug.cgi?id=481622 --- Comment #1 from Mark Rooks --- Created attachment 165971 --> https://bugs.kde.org/attachment.cgi?id=165971=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481622] New: plasmashell crashes when multiple wallpapers are applied (without closing the selection applet)
https://bugs.kde.org/show_bug.cgi?id=481622 Bug ID: 481622 Summary: plasmashell crashes when multiple wallpapers are applied (without closing the selection applet) Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: roo...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.10) Qt Version: 5.15.12 Frameworks Version: 5.115.0 Operating System: Linux 6.7.5-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.10 [CoredumpBackend] -- Information about the crash: Opened "configure desktop and wallpaper" by right clicking desktop Selected a number of difference wallpapers after installing them. Hit the "apply" button but didn't close the applet After selecting and applying a few different wallpapers, clicked "OK" and shell/applet crashed (repeatable) The crash can be reproduced every time. -- Backtrace (Reduced): #5 0x7fddbd7bb22e in QQmlData::wasDeleted (object=0x55e00cc2f790) at ../../include/QtQml/5.15.12/QtQml/private/../../../../../../src/qml/qml/qqmldata_p.h:338 #6 QV4::QObjectWrapper::wrap (object=0x55e00cc2f790, engine=0x55e00cb867b0) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/qml/jsruntime/qv4qobjectwrapper_p.h:213 #7 loadProperty (v4=0x55e00cb867b0, object=0x7fdda800ed30, property=...) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/qml/jsruntime/qv4qobjectwrapper.cpp:139 #8 0x7fddbd7bc5f3 in QV4::QObjectWrapper::virtualResolveLookupGetter (object=0x7fdd74703758, engine=0x55e00cb867b0, lookup=0x55e014f4c4e0) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/qml/jsruntime/qv4qobjectwrapper.cpp:880 #9 0x7fddbd7dbca1 in QV4::Moth::VME::interpret (frame=0x55e00bd4b4e4, frame@entry=0x7fffa124ae20, engine=0x55e00cb867b0, code=0x7fdd85dfc73c ":\033\322") at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/qml/jsruntime/qv4vme_moth.cpp:641 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 480774] New: crash occurs on hitting "apllications"
https://bugs.kde.org/show_bug.cgi?id=480774 Bug ID: 480774 Summary: crash occurs on hitting "apllications" Classification: Applications Product: plasma-systemmonitor Version: 5.27.10 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: roo...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Application: plasma-systemmonitor (5.27.10) Qt Version: 5.15.12 Frameworks Version: 5.114.0 Operating System: Linux 6.7.2-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: This not in gnome-system-monotir shell Occurs on starting the "system-monitor (which prolly calls the already crashing shell The crash can be reproduced every time. -- Backtrace: Application: System Monitor (plasma-systemmonitor), signal: Segmentation fault [KCrash Handler] #4 0x in ?? () #5 0x7f6911870e87 in QQuickItemLayer::~QQuickItemLayer (this=0x56227981a390, __in_chrg=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/quick/items/qquickitem.cpp:8473 #6 0x7f6911870ef9 in QQuickItemLayer::~QQuickItemLayer (this=0x56227981a390, __in_chrg=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/quick/items/qquickitem.cpp:8475 #7 0x7f69119f9321 in QAccessibleQuickItem::role (this=0x56227982dcd0) at ../../include/QtQuick/../../../src/quick/items/qquickitem.h:468 #8 0x7f691297a441 in AtSpiAdaptor::pathForInterface (this=this@entry=0x5622781478c0, interface=0x56227982dcd0) at atspiadaptor.cpp:1586 #9 0x7f691297d254 in AtSpiAdaptor::notifyStateChange (this=this@entry=0x5622781478c0, interface=, state=..., value=1) at atspiadaptor.cpp:878 #10 0x7f691297eb61 in AtSpiAdaptor::notify (this=0x5622781478c0, event=) at atspiadaptor.cpp:903 #11 0x7f691187ebe3 in QQuickItemPrivate::setEffectiveVisibleRecur (this=this@entry=0x56227981a450, newEffectiveVisible=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/quick/items/qquickitem.cpp:6121 #12 0x7f6911885f45 in QQuickItem::setParentItem (this=this@entry=0x56227981a390, parentItem=parentItem@entry=0x0) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/quick/items/qquickitem.cpp:2737 #13 0x7f691188643f in QQuickItem::~QQuickItem (this=this@entry=0x56227981a390, __in_chrg=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/quick/items/qquickitem.cpp:2335 #14 0x7f69110cec0f in QQuickControl::~QQuickControl (this=, this=) at /usr/src/debug/qtquickcontrols2-everywhere-src-5.15.12+kde5/src/quicktemplates2/qquickcontrol.cpp:1009 #15 0x7f690144bed5 in QQmlPrivate::QQmlElement::~QQmlElement (this=, this=) at /usr/include/qt5/QtQml/qqmlprivate.h:144 #16 QQmlPrivate::QQmlElement::~QQmlElement (this=, this=) at /usr/include/qt5/QtQml/qqmlprivate.h:144 #17 0x7f6910fb53b7 in QQmlTableInstanceModel::destroyModelItem (this=, modelItem=0x5622797e0140, mode=QQmlTableInstanceModel::Immediate) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/qmlmodels/qqmltableinstancemodel.cpp:245 #18 0x7f6910fdc861 in std::function::operator()(QQmlDelegateModelItem*) const (__args#0=0x5622797e0140, this=0x7ffdfcaabfa0) at /usr/include/c++/13/bits/std_function.h:591 #19 QQmlReusableDelegateModelItemsPool::drain(int, std::function) (this=0x5622797d9a98, maxPoolTime=0, releaseItem=...) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/qmlmodels/qqmldelegatemodel.cpp:3846 #20 0x7f6910fb4de5 in QQmlTableInstanceModel::drainReusableItemsPool (this=, maxPoolTime=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/qmlmodels/qqmltableinstancemodel.cpp:290 #21 0x7f69119710ec in QQuickTableView::geometryChanged (this=0x5622797c1fe0, newGeometry=..., oldGeometry=...) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/quick/items/qquicktableview.cpp:2951 #22 0x7f691187d7d8 in QQuickItem::setSize (this=this@entry=0x5622797c1fe0, size=...) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/quick/items/qquickitem.cpp:7091 #23 0x7f69110cff49 in QQuickControlPrivate::resizeContent (this=) at /usr/src/debug/qtquickcontrols2-everywhere-src-5.15.12+kde5/src/quicktemplates2/qquickcontrol.cpp:410 #24 0x7f69110d29a6 in QQuickControl::geometryChanged (this=0x5622797ac2c0, newGeometry=..., oldGeometry=...) at /usr/src/debug/qtquickcontrols2-everywhere-src-5.15.12+kde5/src/quicktemplates2/qquickcontrol.cpp:2260 #25 0x7f691187d7d8 in QQuickItem::setSize (this=0x5622797ac2c0, size=...) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/quick/items/qquickitem.cpp:7091 #26 0x7f69118690fe in QQuickAnchorsPrivate::setItemSize (v=...,
[plasmashell] [Bug 402820] Unable to remove/unpin documents/apps from Application Menu after deleting the document/app from system
https://bugs.kde.org/show_bug.cgi?id=402820 Mark Fraser changed: What|Removed |Added CC||mfraz74+...@gmail.com --- Comment #3 from Mark Fraser --- Still there in KDE Plasma Version: 5.27.10. Only way to delete it is to manually edit .config/kactivitymanagerd-statsrc Log out and then log back in again. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 480347] New: System seeming to have high latency with keyboard strokes taking ages. When opening the applications tab, it crashes
https://bugs.kde.org/show_bug.cgi?id=480347 Bug ID: 480347 Summary: System seeming to have high latency with keyboard strokes taking ages. When opening the applications tab, it crashes Classification: Applications Product: plasma-systemmonitor Version: 5.27.10 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: roo...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Application: plasma-systemmonitor (5.27.10) Qt Version: 5.15.12 Frameworks Version: 5.114.0 Operating System: Linux 6.7.1-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: I did a distirbution upgrade today to the build from 24/01/2024. After rebooting, the system seemed a bit sluggish, with cursor taking a long time on terminal. In top, memory and CPU looked fine. There was a process I didn't recognise called just "exe", running as root. To investigate I opened gnome-system-monitor. I clicked on the "Appplications" tab abd the crash occurred. I didn't makr this as a duplicate of 476488 even though it sounds the same, reason being all the bugs I followed were resolved either with a fix or as duplicates of a resolved one. Also the backtrace looks different. The crash can be reproduced every time. -- Backtrace: Application: System Monitor (plasma-systemmonitor), signal: Segmentation fault [KCrash Handler] #4 0x in ?? () #5 0x7fbb7e270e87 in QQuickItemLayer::~QQuickItemLayer (this=0x55ad26fa7340, __in_chrg=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/quick/items/qquickitem.cpp:8473 #6 0x7fbb7e270ef9 in QQuickItemLayer::~QQuickItemLayer (this=0x55ad26fa7340, __in_chrg=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/quick/items/qquickitem.cpp:8475 #7 0x7fbb7e3f9321 in QAccessibleQuickItem::role (this=0x55ad26fba9a0) at ../../include/QtQuick/../../../src/quick/items/qquickitem.h:468 #8 0x7fbb811c0441 in AtSpiAdaptor::pathForInterface (this=this@entry=0x55ad258c89e0, interface=0x55ad26fba9a0) at atspiadaptor.cpp:1586 #9 0x7fbb811c3254 in AtSpiAdaptor::notifyStateChange (this=this@entry=0x55ad258c89e0, interface=, state=..., value=1) at atspiadaptor.cpp:878 #10 0x7fbb811c4b61 in AtSpiAdaptor::notify (this=0x55ad258c89e0, event=) at atspiadaptor.cpp:903 #11 0x7fbb7e27ebe3 in QQuickItemPrivate::setEffectiveVisibleRecur (this=this@entry=0x55ad26fa7400, newEffectiveVisible=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/quick/items/qquickitem.cpp:6121 #12 0x7fbb7e285f45 in QQuickItem::setParentItem (this=this@entry=0x55ad26fa7340, parentItem=parentItem@entry=0x0) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/quick/items/qquickitem.cpp:2737 #13 0x7fbb7e28643f in QQuickItem::~QQuickItem (this=this@entry=0x55ad26fa7340, __in_chrg=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/quick/items/qquickitem.cpp:2335 #14 0x7fbb7da52c0f in QQuickControl::~QQuickControl (this=, this=) at /usr/src/debug/qtquickcontrols2-everywhere-src-5.15.12+kde5/src/quicktemplates2/qquickcontrol.cpp:1009 #15 0x7fbb741b2ed5 in QQmlPrivate::QQmlElement::~QQmlElement (this=, this=) at /usr/include/qt5/QtQml/qqmlprivate.h:144 #16 QQmlPrivate::QQmlElement::~QQmlElement (this=, this=) at /usr/include/qt5/QtQml/qqmlprivate.h:144 #17 0x7fbb7d9393b7 in QQmlTableInstanceModel::destroyModelItem (this=, modelItem=0x55ad26f6cf00, mode=QQmlTableInstanceModel::Immediate) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/qmlmodels/qqmltableinstancemodel.cpp:245 #18 0x7fbb7d960861 in std::function::operator()(QQmlDelegateModelItem*) const (__args#0=0x55ad26f6cf00, this=0x7fffbe588a40) at /usr/include/c++/13/bits/std_function.h:591 #19 QQmlReusableDelegateModelItemsPool::drain(int, std::function) (this=0x55ad26f66878, maxPoolTime=0, releaseItem=...) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/qmlmodels/qqmldelegatemodel.cpp:3846 #20 0x7fbb7d938de5 in QQmlTableInstanceModel::drainReusableItemsPool (this=, maxPoolTime=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/qmlmodels/qqmltableinstancemodel.cpp:290 #21 0x7fbb7e3710ec in QQuickTableView::geometryChanged (this=0x55ad26f4e880, newGeometry=..., oldGeometry=...) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/quick/items/qquicktableview.cpp:2951 #22 0x7fbb7e27d7d8 in QQuickItem::setSize (this=this@entry=0x55ad26f4e880, size=...) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/quick/items/qquickitem.cpp:7091 #23 0x7fbb7da53f49 in
[plasmashell] [Bug 480248] New: Plasma shell crashed with signal 11 (segfault)
https://bugs.kde.org/show_bug.cgi?id=480248 Bug ID: 480248 Summary: Plasma shell crashed with signal 11 (segfault) Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: roo...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.10) Qt Version: 5.15.12 Frameworks Version: 5.114.0 Operating System: Linux 6.6.11-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.10 [CoredumpBackend] -- Information about the crash: I had just imported 3 new VPN connections. I was (quickly) jumping between one connection to another, testing particular functions, around curl and openssl on each. I have done the same behaviour on three seoarate occassions over the last two days and only today, after some new patches were applied, did this start to happen. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #6 0x7f70209f04ea in VDMModelDelegateDataType::notify (this=, items=..., index=, count=, roles=...) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/qmlmodels/qqmladaptormodel.cpp:175 #7 0x7f70209f929b in QQmlAdaptorModel::notify (roles=..., count=14, index=0, items=..., this=0x55824bbd0310) at ../../include/QtQmlModels/5.15.12/QtQmlModels/private/../../../../../../src/qmlmodels/qqmladaptormodel_p.h:163 #8 QQmlDelegateModel::_q_itemsChanged (this=this@entry=0x55824bbd01d0, index=index@entry=0, count=14, roles=...) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/qmlmodels/qqmldelegatemodel.cpp:1499 #9 0x7f7020a03cf9 in QQmlDelegateModel::_q_layoutChanged (this=0x55824bbd01d0, parents=..., hint=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.12+kde31/src/qmlmodels/qqmldelegatemodel.cpp:2057 #10 0x7f7020a04643 in QQmlDelegateModel::qt_metacall (this=0x55824bbd01d0, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7ffc6c258b60) at .moc/moc_qqmldelegatemodel_p.cpp:371 The reporter indicates this bug may be a duplicate of or related to bug 407304, bug 407984, bug 408030, bug 409305, bug 406459, bug 410435, bug 410901, bug 411610, bug 412449, bug 411639, bug 412198, bug 412531, bug 412938, bug 415451, bug 418687, bug 426126, bug 427570, bug 431718, bug 433067, bug 436765, bug 468183, bug 471420, bug 477403, bug 479882. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480248] Plasma shell crashed with signal 11 (segfault)
https://bugs.kde.org/show_bug.cgi?id=480248 --- Comment #1 from Mark Rooks --- Created attachment 165173 --> https://bugs.kde.org/attachment.cgi?id=165173=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 478624] Valgrind incompatibility with binutils-2.42 on x86 with new nop patterns (unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26)
https://bugs.kde.org/show_bug.cgi?id=478624 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Mark Wielaard --- Gentoo, Debian and Fedora already pulled in this patch. Now also added to VALGRIND_3_22_BRANCH: commit 41ff9aa49f6c54c66d0e6b37f265fd9cb0176057 Author: Paul Floyd Date: Sun Dec 17 14:18:51 2023 +0100 Bug 478624 - Valgrind incompatibility with binutils-2.42 on x86 with new nop patterns (unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26) It was a bit of a struggle to get the testcase to build with both clang and gcc (oddly enough gcc was more difficult) so I just resorted to using .byte arrays. (cherry picked from commit d35005cef8ad8207542738812705ceabf137d7e0) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 480126] Build failure on Raspberry Pi 5 / OS 6.1.0-rpi7-rpi-v8
https://bugs.kde.org/show_bug.cgi?id=480126 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #1 from Mark Wielaard --- This looks like a 32bit armhf compiler is used but the system is 64 aarch64? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446654] Feature Request: mirror a panel on all monitors
https://bugs.kde.org/show_bug.cgi?id=446654 Mark changed: What|Removed |Added CC||szauer.m...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 331311] Valgrind shows open files in /proc/self/fd that don't work for the process
https://bugs.kde.org/show_bug.cgi?id=331311 Mark Wielaard changed: What|Removed |Added CC||ahajk...@redhat.com, ||m...@klomp.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 362680] --error-exitcode not honored when file descriptor leaks are found
https://bugs.kde.org/show_bug.cgi?id=362680 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 337388] fcntl works on Valgrind's own file descriptors
https://bugs.kde.org/show_bug.cgi?id=337388 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 CC||ahajk...@redhat.com, ||m...@klomp.org Status|REPORTED|CONFIRMED --- Comment #1 from Mark Wielaard --- looks like PRE(sys_fcntl) and PRE(sys_fcntl64) don't check ML_(fd_allowed) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 162848] --log-file output isn't split when a program forks
https://bugs.kde.org/show_bug.cgi?id=162848 Mark Wielaard changed: What|Removed |Added CC||borntrae...@de.ibm.com --- Comment #24 from Mark Wielaard --- *** Bug 253308 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 253308] --log-file and --xml-file dont work well with --trace-children=yes
https://bugs.kde.org/show_bug.cgi?id=253308 Mark Wielaard changed: What|Removed |Added Resolution|--- |DUPLICATE CC||m...@klomp.org Status|REPORTED|RESOLVED --- Comment #2 from Mark Wielaard --- *** This bug has been marked as a duplicate of bug 162848 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 471222] support tracking of file descriptors being double closed
https://bugs.kde.org/show_bug.cgi?id=471222 Mark Wielaard changed: What|Removed |Added CC||ahajk...@redhat.com, ||m...@klomp.org Status|REPORTED|ASSIGNED Assignee|jsew...@acm.org |ahajk...@redhat.com Ever confirmed|0 |1 --- Comment #1 from Mark Wielaard --- Sasha has been working on this. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 202770] open fd at exit --log-socket=127.0.0.1:1500 with --track-fds=yes and --trace-children=yes with a program that calls fork then exec
https://bugs.kde.org/show_bug.cgi?id=202770 Mark Wielaard changed: What|Removed |Added CC||ahajk...@redhat.com, ||m...@klomp.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 311655] --log-file=FILE leads to apparent fd leak ("Open file descriptor 3: $LOGFILE")
https://bugs.kde.org/show_bug.cgi?id=311655 Mark Wielaard changed: What|Removed |Added CC||ahajk...@redhat.com, ||m...@klomp.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 479661] Valgrind leaks file descriptors
https://bugs.kde.org/show_bug.cgi?id=479661 Mark Wielaard changed: What|Removed |Added CC||ahajk...@redhat.com, ||m...@klomp.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 477992] compiler generated overlapping memcpy diagnosed
https://bugs.kde.org/show_bug.cgi?id=477992 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||m...@klomp.org --- Comment #5 from Mark Wielaard --- (In reply to Barnabás Pőcze from comment #0) > GCC (and apparently clang as well) specifically requires that memcpy() with > an exact overlap does not trigger undefined behaviour > (https://gcc.godbolt.org/z/E4rqz7bn6): > > > Contrary to the standards covering memcpy GCC expects the case of an exact > > overlap of source and destination to work and not invoke undefined > > behavior. > > (from https://gcc.gnu.org/onlinedocs/gcc.pdf) So that is from the GCC user manual, chapter 2 Language Standards Supported by GCC, 2.1 C Language. I haven't seen it stated so explicitly elsewhere for GCC. Do you happen to have other references or are there any C standard DRs that address this? Asking because a lot of references bugs seem to be unsure whether this really is the case. It would be good if something like the above statement was made for clang also and/or acknowledged by the C or Posix standards. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 477198] Add fchmodat2 syscall on linux
https://bugs.kde.org/show_bug.cgi?id=477198 --- Comment #3 from Mark Wielaard --- Also added to the VALGRIND_3_22_BRANCH as: commit a43e62dddcf51ec6578a90c5988a41e856b44b05 (HEAD -> VALGRIND_3_22_BRANCH) Author: Mark Wielaard Date: Sat Nov 18 21:17:02 2023 +0100 Add fchmodat2 syscall on linux fchmodat2 is a new syscall on linux 6.6. It is a variant of fchmodat that takes an extra flags argument. https://bugs.kde.org/show_bug.cgi?id=477198 (cherry picked from commit 372d09fd9a8d76847c81092ebff71c80fd6c145d) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476465] AArch64 ARMv8.3 LDAPR/LDAPRH/LDAPRB instructions not supported
https://bugs.kde.org/show_bug.cgi?id=476465 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||m...@klomp.org --- Comment #6 from Mark Wielaard --- Thanks for the patch. Still looking for a machine to test it on. Although with your patch I can now run the testcase under valgrind while my test machine doesn't actually support LDAPR. I am not really familiar with the arm64 code, but the patch does look reasonable. I find the arm documentation hard to navigate, which variants exactly are we missing and which are required to be supported? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 478211] Redundant code for vgdb.c and Valgrind core tools
https://bugs.kde.org/show_bug.cgi?id=478211 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #1 from Mark Wielaard --- Very nice. Hopefully we can share more utility functions in the future. Since remote-utils-shared.c is based on some functions from remote-utils.c I have also copied the Copyright header from that file. commit ec73dcb1826091b3cbdd43a4a37522e33c3ce786 (HEAD -> master, origin/master, origin/HEAD) Author: Alexandra Petlanova Hajkova Date: Wed Dec 6 03:14:53 2023 -0500 remote-utils-shared: Created files for sharing code between vgdb.c and m_gdbserver/server.c. This removes code redundancies that was introduced for vgdb.c by vgdb --multi implementation. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476548] valgrind 3.22.0 fails on assertion when loading debuginfo file produced by mold
https://bugs.kde.org/show_bug.cgi?id=476548 --- Comment #9 from Mark Wielaard --- Also pushed to VALGRIND_3_22_BRANCH as: commit 1d00e5ce0fb069911c4b525ec38289fb5d9021b0 Author: Paul Floyd Date: Sat Nov 18 08:49:34 2023 +0100 Bug 476548 - valgrind 3.22.0 fails on assertion when loading debuginfo file produced by mold (cherry picked from commit 9ea4ae66707a4dcc6f4328e11911652e4418c585) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476548] valgrind 3.22.0 fails on assertion when loading debuginfo file produced by mold
https://bugs.kde.org/show_bug.cgi?id=476548 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #8 from Mark Wielaard --- Found the same issue on Fedora 38 while loading /usr/lib64/ossl-modules/fips.so which has: [16] .rodata PROGBITS 00105000 00105000 fa90 0 A 0 0 64 [17] .rodata1 PROGBITS 00114aa0 00114aa0 0020 0 A 0 0 32 commit 9ea4ae66707a4dcc6f4328e11911652e4418c585 fixes it We might want to backport this to the VALGRIND_3_22_BRANCH -- You are receiving this mail because: You are watching all bug changes.
