[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.
[valgrind] [Bug 477198] Add fchmodat2 syscall on linux
https://bugs.kde.org/show_bug.cgi?id=477198 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Mark Wielaard --- Tested on a linux 6.6 kernel (x86_64) and pushed as: commit 372d09fd9a8d76847c81092ebff71c80fd6c145d 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 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 477719] vgdb incorrectly replies to qRcmd packet
https://bugs.kde.org/show_bug.cgi?id=477719 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED CC||m...@klomp.org Status|REPORTED|RESOLVED --- Comment #1 from Mark Wielaard --- Thanks, looks good. Pushed as: commit aed6de1a943d2beae5ba6180552d410922f9b8bd Author: Alexandra Petlanova Hajkova Date: Wed Nov 29 05:40:13 2023 -0500 vgdb.c: Encode the qRcmd reply as hex string When vgdb replies to qRcmd packet recieved from GDB, it used to send the reply as simple string. This is wrong, GDB expects to get a hex encoded string. https://bugs.kde.org/show_bug.cgi?id=477719 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476855] Apps crash when I screen-lock and power off the screen + desktop freezes after a few hours
https://bugs.kde.org/show_bug.cgi?id=476855 Mark B changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |REPORTED Ever confirmed|1 |0 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 281059] Cannot connect to Oracle using valgrind
https://bugs.kde.org/show_bug.cgi?id=281059 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||m...@klomp.org --- Comment #7 from Mark Wielaard --- Agreed that there is not much we can do for this situation except producing a better error message like suggested in comment #6. The following patch does that: commit 132b9eca80b36e9368dc806d8144d0846de2298c Author: Mark Wielaard Date: Sun Nov 26 18:22:01 2023 +0100 launcher-linux.c (find_client): barf if we don't have read permission for executable For such an executable valgrind will now report: valgrind: Cannot continue: Need read permission on /usr/local/bin/exec-no-read https://bugs.kde.org/show_bug.cgi?id=281059 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 237920] valgrind segfault on fork failure
https://bugs.kde.org/show_bug.cgi?id=237920 Mark Wielaard changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|CONFIRMED |RESOLVED --- Comment #8 from Mark Wielaard --- This was finally closed downstream https://bugzilla.redhat.com/show_bug.cgi?id=587817 -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 477221] The program kasts fails to launch. It crashes.
https://bugs.kde.org/show_bug.cgi?id=477221 --- Comment #2 from Mark Grieveson --- (In reply to bart from comment #1) > Is this happening with the postmarketOS Kasts package, or with a manually > compiled version? If it's the official package, could you report this bug > with postmarketOS, please? > > These kinds of faults tend to happen when a library that Kasts depends on > gets updated without Kasts itself getting recompiled. Then you can end up > with an instruction that has changed in the underlying lib without Kasts > knowing about this, leading to a crash. So, I would think it's simply a > matter of recompiling the package. > > If that still doesn't help, then please let me know, and so we can futher > debug this. Hello. Thank you for your feedback. Yes, this is happening with the postmarketOS Kasts package. I'm not sure where exactly I should report this to, but I did mention it on the [postmarketOS Lemmy site](https://lemmy.ca/post/991); so, hopefully someone from there will be made aware of it. Thanks again for your feedback. I appreciate all the work that people are doing to provide open source alternatives to us. -- 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 Attachment #127438|0 |1 is obsolete|| CC||m...@klomp.org --- Comment #4 from Mark Wielaard --- Created attachment 163356 --> https://bugs.kde.org/attachment.cgi?id=163356=edit Patch - Adds support for xml output of --track-fds This is a rebase of the patch to current (VALGRIND_3_22_0-61-gb748cc9e1) git. It seems to work, but I haven't fully reviewed it yet. It would also need a bit of documentation about the proposed xml structure output. And indeed some tests would be nice. It is a pity the none tool doesn't do xml output. Maybe it should? or should we just stick some new tests under the memcheck tool? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477293] New: systemsettings crash on printers
https://bugs.kde.org/show_bug.cgi?id=477293 Bug ID: 477293 Summary: systemsettings crash on printers Classification: Applications Product: systemsettings Version: 5.27.4 Platform: Ubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mark.vanros...@nottingham.ac.uk Target Milestone: --- Application: systemsettings (5.27.4) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.0-36-generic x86_64 Windowing System: X11 Distribution: Ubuntu 23.04 DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: Not running plasma, but after starting systemsettings5 from commandline. Other components work fine. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7fc32c33ed5f in PrinterModel::updateDest(QStandardItem*, KCupsPrinter const&) () from /lib/x86_64-linux-gnu/libkcupslib.so #5 0x7fc32c33ff8f in PrinterModel::getDestsFinished(KCupsRequest*) () from /lib/x86_64-linux-gnu/libkcupslib.so #6 0x7fc36b4e7de0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc36c16bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7fc36b4bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fc36b4bdea1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fc36b5157b7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fc369d1549d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7fc369d70178 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7fc369d141b0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fc36b514e7a in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fc36b4b97cb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fc36b4c1c1a in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x555dacf5c5ea in ?? () #18 0x7fc36aa23a90 in __libc_start_call_main (main=main@entry=0x555dacf5bac0, argc=argc@entry=1, argv=argv@entry=0x7ffea0032658) at ../sysdeps/nptl/libc_start_call_main.h:58 #19 0x7fc36aa23b49 in __libc_start_main_impl (main=0x555dacf5bac0, argc=1, argv=0x7ffea0032658, init=, fini=, rtld_fini=, stack_end=0x7ffea0032648) at ../csu/libc-start.c:360 #20 0x555dacf5cf55 in ?? () [Inferior 1 (process 941210) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 477221] New: The program kasts fails to launch. It crashes.
https://bugs.kde.org/show_bug.cgi?id=477221 Bug ID: 477221 Summary: The program kasts fails to launch. It crashes. Classification: Applications Product: kasts Version: 23.08.3 Platform: postmarketOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: markgrieve...@yahoo.ca Target Milestone: --- The program crashed. *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** (gdb) run Starting program: /usr/bin/kasts Program received signal SIGILL, Illegal instruction 0xfdae000 in ?? () from /lib/libcrypto.so.3 STEPS TO REPRODUCE 1. enter "gdb kasts" in the terminal 2. then at the prompt, type "run" --> (gdb) run 3. the result will be as I typed it above OBSERVED RESULT (gdb) run Starting program: /usr/bin/kasts Program received signal SIGILL, Illegal instruction 0xfdae000 in ?? () from /lib/libcrypto.so.3 EXPECTED RESULT I expected the program to run rather than crash. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION This is on a Pinephone Pro running postmarketOS Edge. The kernel: 6.6.0 OS: postmarketOS edge aarch64 Shell: ash Resolution: 720x1440 wm: dwc -- 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 Mark Wielaard changed: What|Removed |Added Assignee|jsew...@acm.org |m...@klomp.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Mark Wielaard --- Created attachment 163278 --> https://bugs.kde.org/attachment.cgi?id=163278=edit Add fchmodat2 syscall on linux Initial, untested, patch. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 477198] New: Add fchmodat2 syscall on linux
https://bugs.kde.org/show_bug.cgi?id=477198 Bug ID: 477198 Summary: Add fchmodat2 syscall on linux Classification: Developer tools Product: valgrind Version: 3.22 GIT Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: m...@klomp.org Target Milestone: --- The linux 6.6 kernel added a new syscall fchmodat2 which is a variant of fchmodat with an extra flag argument: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=09da082b07bbae1c11d9560c8502800039aebcea https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=78252deb023cf0879256fcfbafe37022c390762b https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=78252deb023cf0879256fcfbafe37022c390762b glibc will probably start using it in the next release (2.39): https://inbox.sourceware.org/libc-alpha/20230928165621.372548-1-adhemerval.zane...@linaro.org/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477174] New: Dismissing a notification at startup caused Plasmashell to crash
https://bugs.kde.org/show_bug.cgi?id=477174 Bug ID: 477174 Summary: Dismissing a notification at startup caused Plasmashell to crash Classification: Plasma Product: plasmashell Version: 5.27.9 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 Created attachment 163258 --> https://bugs.kde.org/attachment.cgi?id=163258=edit kwin_wayland backtrace SUMMARY Unsure if it's because of the specific notification content, or that it was at startup. I have Joplin set to run at startup and when it runs, Plasma notifies me of Joplin running in the background. When I dismiss it, it caused Plasmashell to crash. Unsure if I can reproduce this issue, but I outlined the steps below. Backtrace is included. STEPS TO REPRODUCE 1. Login to desktop 2. Dismiss notification 3. Crash? OBSERVED RESULT Plasmashell crashed. EXPECTED RESULT Dismissed the notification. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20231116 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.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 N/A -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476708] valgrind-monitor.py regular expressions should use raw strings
https://bugs.kde.org/show_bug.cgi?id=476708
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED|RESOLVED
--- Comment #3 from Mark Wielaard ---
commit 0fbfbe05028ad18efda786a256a2738d2c231ed4
Author: Mark Wielaard
Date: Fri Nov 17 13:31:52 2023 +0100
valgrind-monitor.py regular expressions should use raw strings
With python 3.12 gdb will produce the following SyntaxWarning when
loading valgrind-monitor-def.py:
/usr/share/gdb/auto-load/valgrind-monitor-def.py:214:
SyntaxWarning: invalid escape sequence '\['
if re.fullmatch("^0x[0123456789ABCDEFabcdef]+\[[^\[\]]+\]$", arg_str):
In a future python version this will become an SyntaxError.
Use a raw strings for the regular expression.
https://bugs.kde.org/show_bug.cgi?id=476708
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 476708] valgrind-monitor.py regular expressions should use raw strings
https://bugs.kde.org/show_bug.cgi?id=476708 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Assignee|jsew...@acm.org |m...@klomp.org Status|REPORTED|ASSIGNED --- Comment #2 from Mark Wielaard --- (In reply to Paul Floyd from comment #1) > I'm not sure what the \[ is doing in the complemented character set. I > assume that this is looking for > > 'literal [' > 'a bunch of non-square bracket characters' > 'literal ]' Yes, that is what it is for. But \[ is a valid escape for the regular expression string, but not in a regular python string. That is why we get that SyntaxWarning. Using raw strings makes sure python doesn't try to interpret escape sequences. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 253383] [PATCH] several LTP testcases trigger VALGRIND INTERNAL ERROR
https://bugs.kde.org/show_bug.cgi?id=253383 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #2 from Mark Wielaard --- The second patch was fixed slightly differently: commit f7cce36efe5223ae2766141552143441018780f3 Author: Mark Wielaard Date: Tue Feb 23 21:27:19 2016 + Bug 359724 getsockname might crash - deref_UInt should call safe_to_deref git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15809 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 200829] Ptrcheck doesn't work on Mac OS X
https://bugs.kde.org/show_bug.cgi?id=200829 Mark Wielaard changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED CC||m...@klomp.org --- Comment #1 from Mark Wielaard --- Sorry, exp-sgcheck (named exp-ptrcheck prior to version 3.7), was removed in version 3.16.0. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 206618] ptrcheck complains about things allocated with alloca
https://bugs.kde.org/show_bug.cgi?id=206618 Mark Wielaard changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||m...@klomp.org Resolution|--- |UNMAINTAINED --- Comment #2 from Mark Wielaard --- Sorry, exp-sgcheck (named exp-ptrcheck prior to version 3.7), was removed in version 3.16.0. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 308027] Warning: negative range in .debug_loc section
https://bugs.kde.org/show_bug.cgi?id=308027 Mark Wielaard changed: What|Removed |Added Status|REPORTED|RESOLVED CC||m...@klomp.org Resolution|--- |NOT A BUG --- Comment #7 from Mark Wielaard --- The exp-sgcheck tool isn't part of valgrind anymore and the warning was correct, it was a gcc bug. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 306340] parse_var_DIE confused by DWARF from clang-3.1
https://bugs.kde.org/show_bug.cgi?id=306340 Mark Wielaard changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #7 from Mark Wielaard --- The llvm bug is still open https://github.com/llvm/llvm-project/issues/13723 but I think it might have been fixed since we haven't seen this issue in a very long time. sgcheck isn't part of valgrind anymore. But you can still trigger this with valgrind 3.21.0 using --read-var-info=yes: $ valgrind --read-var-info=yes /tmp/frob ==8280== Memcheck, a memory error detector ==8280== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==8280== Using Valgrind-3.21.0 and LibVEX; rerun with -h for copyright info ==8280== Command: /tmp/frob ==8280== parse DIE(readdwarf3.c:3025): confused by: <0><10d>: Abbrev Number: 1 (DW_TAG_compile_unit) DW_AT_producer: (indirect string, offset: 0xab): clang version 3.1 (branches/release_31) DW_AT_language: 12 DW_AT_name: (indirect string, offset: 0xd3): ../a.c DW_AT_low_pc : 0x0 DW_AT_stmt_list : 136 DW_AT_comp_dir: (indirect string, offset: 0xda): /home/uabpath/tmp parse_var_DIE: --8280-- WARNING: Serious error when reading debug info --8280-- When reading debug info from /tmp/frob: --8280-- confused by the above DIE It won't trigger for valgrind 3.22.0 since that has lazy debuginfo reading by default and since the debuginfo isn't actually needed it won't parse it... Since this is just a warning and a real bug in llvm produced debuginfo I am closing this bug. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 266045] Slackware 10.2 make fails
https://bugs.kde.org/show_bug.cgi?id=266045 Mark Wielaard changed: What|Removed |Added Resolution|--- |UNMAINTAINED CC||m...@klomp.org Status|CONFIRMED |RESOLVED --- Comment #6 from Mark Wielaard --- Slackware 10.2 was EOLed on 2012-08-01 valgrind 3.6.0 was released on 21 October 2010 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476855] Apps crash when I screen-lock and power off the screen + desktop freezes after a few hours
https://bugs.kde.org/show_bug.cgi?id=476855 --- Comment #6 from Mark B --- (In reply to Nate Graham from comment #5) > Can you attach a backtrace of what's crashing? Sorry, I have downgraded to stable plasma5 and for 3 DAYS straight have been running up to 7 shutter-encoder jobs in parallel 24h/24 non-stop (and even tested playing heavy proton games at the same time to test the stability) -> it is ROCK STABLE on plasma5 (X11). My encodings are for work & aren't finished, so I can't go back to the plasma-alpha right now. But to make it fast for you so you can trace this very quickly: 1. Download this: https://www.shutterencoder.com/Shutter%20Encoder%2017.6%20Linux%2064bits.AppImage (or the .deb). 2. Load a video to encode in wayland (I encode to AV1). 3. Startkey+L to lock the screen 4. Power off the screen 5. After a few seconds I head the fans spin down (-> this means the encode has crashed) 6. Power on the screen 7. Unlock the screen (with password) 8. The shutter encoder & ffmpeg processes have disappeared. (I am on full AMD zen4 + AMD rx6000 series). -> please tell me if you can reproduce the problem. I am currently blocked with my encoding work, but if you cannot reproduce this (I am sure you will be able to), we will see how I can help you further. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476895] [aarch64] unhandled instruction 0xF8BFC273
https://bugs.kde.org/show_bug.cgi?id=476895 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #1 from Mark Wielaard --- Have you tried running under vgdb https://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver so you can disassemble from gdb? Or use objdump -d to see which instruction this is? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 345414] Missing seccomp support (WARNING: unhandled syscall: 317)
https://bugs.kde.org/show_bug.cgi?id=345414 Mark Wielaard changed: What|Removed |Added See Also||https://bugzilla.mozilla.or ||g/show_bug.cgi?id=1288726 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 471340] callgrind Error: can not open cache simulation output file callgrind.out.pid
https://bugs.kde.org/show_bug.cgi?id=471340 Mark Wielaard changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=345414 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 345414] Missing seccomp support (WARNING: unhandled syscall: 317)
https://bugs.kde.org/show_bug.cgi?id=345414 Mark Wielaard changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=471340 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 380183] WARNING: unhandled amd64-linux syscall: 317 (seccomp)
https://bugs.kde.org/show_bug.cgi?id=380183 Mark Wielaard changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Mark Wielaard --- *** This bug has been marked as a duplicate of bug 345414 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 345414] Missing seccomp support (WARNING: unhandled syscall: 317)
https://bugs.kde.org/show_bug.cgi?id=345414 Mark Wielaard changed: What|Removed |Added CC||toralf.foers...@gmx.de --- Comment #16 from Mark Wielaard --- *** Bug 380183 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 345414] Missing seccomp support (WARNING: unhandled syscall: 317)
https://bugs.kde.org/show_bug.cgi?id=345414 --- Comment #15 from Mark Wielaard --- Also note this patch that implements more of seccomp: https://sourceforge.net/p/valgrind/mailman/message/46305485/ -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476978] [SSE4.1] missing support for PMAXUD (x86)
https://bugs.kde.org/show_bug.cgi?id=476978
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
Summary|[SSE4.1] missing support|[SSE4.1] missing support
|for PMAXUD |for PMAXUD (x86)
--- Comment #1 from Mark Wielaard ---
Note that this is implemented for amd64, just not for x86 (32bit).
See VEX/priv/guest_amd64_toIR.c (dis_ESC_0F38__SSE4):
case 0x3B:
case 0x3F:
/* 66 0F 38 3B /r = PMINUD xmm1, xmm2/m128
Minimum of Packed Unsigned Doubleword Integers (XMM)
66 0F 38 3F /r = PMAXUD xmm1, xmm2/m128
Maximum of Packed Unsigned Doubleword Integers (XMM)
*/
if (have66noF2noF3(pfx) && sz == 2) {
/* FIXME: this needs an alignment check */
Bool isMAX = opc == 0x3F;
delta = dis_SSEint_E_to_G(
vbi, pfx, delta,
isMAX ? "pmaxud" : "pminud",
isMAX ? Iop_Max32Ux4 : Iop_Min32Ux4,
False
);
goto decode_success;
}
break;
With tests in none/tests/amd64/sse4-64.c.
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-wayland-protocols] [Bug 476855] Apps crash when I screen-lock and power off the screen + desktop freezes after a few hours
https://bugs.kde.org/show_bug.cgi?id=476855 Mark B changed: What|Removed |Added Summary|Apps crash when I |Apps crash when I |screen-lock and power off |screen-lock and power off |the screen |the screen + desktop ||freezes after a few hours --- Comment #4 from Mark B --- Did some more testing: When logging back in (from the lock screen) after a few hours (X11), the desktop is frozen (icons, kde bar, etc... are unresponsive) but I can move the mouse. And the ffmpeg and shutter encoder processes have disappeared (they have crashed in the middle of an encoding job). THIS PROBLEM DOESN'T EXIST with the stable plasma (I have been running ffmpeg/shutter encoder jobs for days without any issues). -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 462548] Weather widgets shows non-sensible data values (3276, 3277, 3276.69)
https://bugs.kde.org/show_bug.cgi?id=462548 Mark B changed: What|Removed |Added Version|5.26.4 |5.27.80 --- Comment #3 from Mark B --- This was reported with version 5.6.4. I changed it to 5.27.80 as it still isn't fixed in this version (and all the previous versions). -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 462548] Weather widgets shows non-sensible data values (3276, 3277, 3276.69)
https://bugs.kde.org/show_bug.cgi?id=462548 Mark B changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||kde.pp...@slmail.me --- Comment #2 from Mark B --- Same problem here. Using wetter.com. Sometimes the values are correct (i.ex: 7 °C), and sometimes they are not (i.ex: 3277 °C). It changes/happens randomly. One moment the values are wrong (3277 °C), a little later they are correct (7 °C), and later it changes again to 3277 °C This has been going on for more than a year and is the same in the new Plasma 6 alpha. X11 & Wayland same problem. kdeplasma-addons : 5.27.80 (stable plasma 5 had the same problem) Kde plasma: 5.27.80 (stable plasma 5 had the same problem) Kde frameworks: 5.245.0 (stable frameworks 5 had the same problem) Qt: 6.6.0 (qt5 had the same problem) -- You are receiving this mail because: You are watching all bug changes.
[plasma-wayland-protocols] [Bug 476855] Apps crash when I screen-lock and power off the screen
https://bugs.kde.org/show_bug.cgi?id=476855 --- Comment #3 from Mark B --- BTW Shutter encoder uses java. So this would be a bug in java? -- You are receiving this mail because: You are watching all bug changes.
[plasma-wayland-protocols] [Bug 476855] Apps crash when I screen-lock and power off the screen
https://bugs.kde.org/show_bug.cgi?id=476855 Mark B changed: What|Removed |Added Resolution|DOWNSTREAM |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #2 from Mark B --- (In reply to David Edmundson from comment #1) > This is a bug in shutter encoder GUI or the toolkit used there. Please > report there. Just did some more testing: it also crashes with X11 (kde alpha) after the screen auto-locks & the screen powers off (but not always). With stable KDE it WORKS FINE. Doesn't crash (Have tested many times for days). -> please confirm if you are still sure that this is downstream. -- You are receiving this mail because: You are watching all bug changes.
[plasma-wayland-protocols] [Bug 476855] New: Apps crash when I screen-lock and power off the screen
https://bugs.kde.org/show_bug.cgi?id=476855 Bug ID: 476855 Summary: Apps crash when I screen-lock and power off the screen Classification: Plasma Product: plasma-wayland-protocols Version: 1.11.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kde.pp...@slmail.me CC: aleix...@kde.org Target Milestone: --- SUMMARY Running an ffmpeg encode with Shutter encoder, Shutter encoder & ffmpeg crash when I power off the screen (after locking the screen). STEPS TO REPRODUCE 1. Login to the wayland session 2. Start an ffmpeg encode with Shutter encoder (https://aur.archlinux.org/packages/shutter-encoder) & minimize shutter encoder. 3. Startkey+L to lock the screen 4. Power off the screen 5. After a few seconds I head the fans spin down (-> this means the encode has crashed) 6. Power on the screen 7. Unlock the screen (with password) 8. The shutter encoder & ffmpeg processes have disappeared. OBSERVED RESULT ffmpeg & shutter encoder gui have crashed EXPECTED RESULT Shutter encoder should continue working after logging out & powering off the screen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Plasma 5.27.80 , archlinux kernel 6.6.1 (available in About System) KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 ADDITIONAL INFORMATION: With the X11 session it works. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401284] False positive "Source and destination overlap in strncat"
https://bugs.kde.org/show_bug.cgi?id=401284
--- Comment #11 from Mark Wielaard ---
(In reply to Paul Floyd from comment #9)
> > src_orig, \
> > (Addr)dst-(Addr)dst_orig+1, \
> > - (Addr)src-(Addr)src_orig+1)) \
> > + n)) \
> > RECORD_OVERLAP_ERROR("strncat", dst_orig, src_orig, n); \
>
> We need to keep the calculated lengths - either or both sting can be shorter
> than n.
ah, yes. Thanks for double checking and pushing this fix through.
I think what you pushed is correct.
But I think in general "overlap" in these string functions is not well defined
because it isn't always clear of the NUL terminator is part of the
string/operation or not (like in this case). And for code that does what this
example code does the mem/byte functions are more clear.
BTW. The gcc 13 does produce a pretty clear warning for this code if we help it
see the exact length:
#include
#include
#include
int main(int argc, char* argv[])
{
size_t len = strlen(argv[1]);
if (len == 7) {
char* buf = (char*) malloc(2 * len + 1);
memcpy(buf, argv[1], len + 1);
strncat(buf + len, buf, len);
printf("%s\n", buf);
free(buf);
}
return 0;
}
$ gcc -g -O2 -Wall -o vbug vbug.c
vbug.c: In function ‘main’:
vbug.c:11:5: warning: ‘strncat’ output truncated before terminating nul copying
7 bytes from a string of the same length [-Wstringop-truncation]
11 | strncat(buf + len, buf, len);
| ^~~~
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 460616] disInstr(arm64): unhandled instruction 0x4E819402 (dotprod/ASIMDDP)
https://bugs.kde.org/show_bug.cgi?id=460616 Mark Wielaard changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Mark Wielaard --- This was a really good patch. Thanks. Only added a NEWS entry, then pushed as: commit f42b9a434e12bc14ec821183a69b86e91da0577c Author: William Ashley Date: Fri Nov 10 17:51:12 2023 +0100 Bug 460616 - Add support for aarch64 dotprod instructions This change adds support for the FEAT_DotProd instructions SDOT ., ., .4B[] SDOT ., ., . UDOT ., ., .4B[] UDOT ., ., . -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 460616] disInstr(arm64): unhandled instruction 0x4E819402 (dotprod/ASIMDDP)
https://bugs.kde.org/show_bug.cgi?id=460616 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Summary|disInstr(arm64): unhandled |disInstr(arm64): unhandled |instruction 0x4E819402 |instruction 0x4E819402 ||(dotprod/ASIMDDP) --- Comment #4 from Mark Wielaard --- Found a cfarm machine that supports ASIMDDP. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401284] False positive "Source and destination overlap in strncat"
https://bugs.kde.org/show_bug.cgi?id=401284 --- Comment #4 from Mark Wielaard --- (In reply to AL from comment #3) > My point was that strncat() will never even encounter the terminating '\0' > byte in the source string because its counter (5) will be depleted to 0 > before then (or, in a generic case, the '\0' would have been encountered in > the source string earlier -- causing strncat() to return). Which means that > technically the pointers used in such an operation will have never crossed > the paths of each other (in this case, the source pointer will never be used > to extract anything that goes into the area where the destination pointer > was operating). Technically you are right. But I would worry about the string terminator overlap. An implementation might copy 8 bytes at a time if len == 7 (or any n * 8 - 1) . Which would have overlap. It probably would still be fine. There would probably be an explicit zero terminating byte that fixed up any overlap confusion. But it does feel you are just on the edge of what is "allowed". > I still consider that warning as excessive in the reported case. You might well be right. And I wouldn't complain if the overlap check was adjusted to just account for the maximum n chars in src. But the code as given does make warning flags go off in other tools as well. e.g. gcc 13 (didn't test with other versions) will also insist there is a possible 1 byte overlap: $ gcc -O2 -Wall -g -o vbug vbug.c vbug.c: In function ‘main’: vbug.c:10:5: warning: ‘strncat’ accessing between 1 and 9223372036854775805 bytes at offsets [0, 9223372036854775805] and 0 may overlap 1 byte at offset [0, 9223372036854775807] [-Wrestrict] 10 | strncat(buf + len, buf, len); | ^~~~ -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401284] False positive "Source and destination overlap in strncat"
https://bugs.kde.org/show_bug.cgi?id=401284
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #2 from Mark Wielaard ---
I do think this is somewhat questionable. You could see it as if strncat copies
over the trailing zero terminator from the source to the destination. In which
case there is overlap. If you insist that zero terminator isn't being copied,
but a new zero terminator is added to the destination after n chars of the
original have been copied, then the following should fix it:
diff --git a/shared/vg_replace_strmem.c b/shared/vg_replace_strmem.c
index 79e640189..8dd5b6368 100644
--- a/shared/vg_replace_strmem.c
+++ b/shared/vg_replace_strmem.c
@@ -370,7 +370,7 @@ static inline void my_exit ( int x )
if (is_overlap(dst_orig, \
src_orig, \
(Addr)dst-(Addr)dst_orig+1, \
- (Addr)src-(Addr)src_orig+1)) \
+ n)) \
RECORD_OVERLAP_ERROR("strncat", dst_orig, src_orig, n); \
\
return dst_orig; \
Note that we also intercept strlcat. But there you give the size of the dst
buffer, which should include space for the terminator. So there this kind of
concat would always be considered an overlap.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 463859] valgrind hangs and is totally unresponsive running a very "simple" Rust program that uses glommio
https://bugs.kde.org/show_bug.cgi?id=463859 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #4 from Mark Wielaard --- See also Bug #439226 Multiple io_urings per thread not supported and Bug #428364 Signals inside io_uring_enter not handled -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 444224] Missing io_uring syscall
https://bugs.kde.org/show_bug.cgi?id=444224 Mark Wielaard changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||m...@klomp.org --- Comment #2 from Mark Wielaard --- This was added in 3.17.0. So lets close this. There are some followup bugs for more functionality. e.g. Bug #439226 Multiple io_urings per thread not supported and Bug #428364 Signals inside io_uring_enter not handled If there are other issues please open a new bug. commit 97fa86915e717dc68123f05b668b73adfe8885a9 Author: Bart Van Assche Date: Mon Jul 1 15:09:04 2019 -0700 Add support for the Linux io_uring system calls Man pages and test code are available in the following git repository: http://git.kernel.dk/cgit/liburing/ commit b918f710208889d579026627830a80b24be1513d Author: Mark Wielaard Date: Thu Feb 4 17:21:56 2021 +0100 PR423361 Adds io_uring support on arm64/aarch64 (and all other arches) io_uring syscalls only work on x86/amd64, but they can be enabled on all arches. Based on a patch by Nathan Ringo . https://bugs.kde.org/show_bug.cgi?id=423361 commit c90561e20f7df2e9c5ae30f1cdafd330b0172345 Author: Mark Wielaard Date: Wed Feb 9 23:37:53 2022 +0100 Do not try to record fd name for io_uring_setup In POST(sys_io_uring_setup) we tried to use record_fd_open_with_given_name with ARG1 as name. But ARG1 isn't a char pointer. So this might crash with --track-fds=yes. Since no (file) name is associated with the fd returned by io_uring_setup use record_fd_open_nameless instead. https://bugs.kde.org/show_bug.cgi?id=449838 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476662] vex amd64->IR: unhandled instruction bytes: 0x66 0x9D (popf)
https://bugs.kde.org/show_bug.cgi?id=476662 --- Comment #2 from Mark Wielaard --- Is this only an issue with this hand assembly? It would be interesting to see real code that uses this. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476708] New: valgrind-monitor.py regular expressions should use raw strings
https://bugs.kde.org/show_bug.cgi?id=476708
Bug ID: 476708
Summary: valgrind-monitor.py regular expressions should use raw
strings
Classification: Developer tools
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: m...@klomp.org
Target Milestone: ---
/usr/share/gdb/auto-load/valgrind-monitor-def.py:214: SyntaxWarning: invalid
escape sequence '\['
if re.fullmatch("^0x[0123456789ABCDEFabcdef]+\[[^\[\]]+\]$", arg_str):
Loaded /usr/share/gdb/auto-load/valgrind-monitor.py
According to
https://docs.python.org/dev/whatsnew/3.12.html#other-language-changes
A backslash-character pair that is not a valid escape sequence now generates a
SyntaxWarning, instead of DeprecationWarning. For example,
re.compile("\d+\.\d+") now emits a SyntaxWarning ("\d" is an invalid escape
sequence, use raw strings for regular expression: re.compile(r"\d+\.\d+")). In
a future Python version, SyntaxError will eventually be raised, instead of
SyntaxWarning. (Contributed by Victor Stinner in gh-98401.)
Using a raw string does indeed get rid of the SyntaxWarning:
if re.fullmatch(r"^0x[0123456789ABCDEFabcdef]+\[[^\[\]]+\]$", arg_str):
Probably all regexps should use raw strings if they contain escape sequences.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 476662] vex amd64->IR: unhandled instruction bytes: 0x66 0x9D (popf)
https://bugs.kde.org/show_bug.cgi?id=476662 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Mark Wielaard --- This looks like the size == 2 issue in VEX/priv/guest_amd64_toIR.c (dis_ESC_NONE): case 0x9D: /* POPF */ /* Note. There is no encoding for a 32-bit popf in 64-bit mode. So sz==4 actually means sz==8. */ if (haveF2orF3(pfx)) goto decode_failure; vassert(sz == 2 || sz == 4 || sz == 8); if (sz == 4) sz = 8; if (sz != 8) goto decode_failure; // until we know a sz==2 test case exists So here is an example where sz == 2. Question is if it is a valid example. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476553] RPM build of Valgrind 3.22.0 fails under RHEL8
https://bugs.kde.org/show_bug.cgi?id=476553 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #1 from Mark Wielaard --- I created 3.22.0 rpms for epel8: https://copr.fedorainfracloud.org/coprs/mjw/valgrind-3.22.0/ The system gdb is too old to support the valgrind python monitor commands, so it is build with --without-gdbscripts-dir. Does that help? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 402833] memcheck/tests/overlap testcase fails, memcpy seen as memmove
https://bugs.kde.org/show_bug.cgi?id=402833 --- Comment #10 from Mark Wielaard --- (In reply to Mark Wielaard from comment #9) > Created attachment 162737 [details] > disable overlap check and test for linux-amd64 > > More subtle workaround patch that only disables the overlap check (and test) > on linux-amd64 This workaround is now committed: commit 53e101f562fa89bbf92d658fba626e2397862a16 Author: Mark Wielaard Date: Mon Oct 30 23:30:06 2023 +0100 Disable memcpy overlap check and test on amd64 linux Almost all newer distros have ifunc based memcpy/memmove glibc implementation which cause false positives. Disable the overlap check and test on these systems for now. https://bugs.kde.org/show_bug.cgi?id=402833 But it is just a workaround to get rid of the false positives. Real solution still needed. So keeping bug open. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417993] vbit-test fail on s390x with Iop_Add32: spurious dependency on uninitialised value
https://bugs.kde.org/show_bug.cgi?id=417993 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #15 from Mark Wielaard --- Very nice, this also fixes the s390x case. Pushed as: commit 0625fee9e49ebfeba0c805b00f7428e0a40ec75a Author: Eyal Soha Date: Mon Oct 30 10:46:38 2023 -0600 Clear vbits after the test is done. https://bugs.kde.org/show_bug.cgi?id=417993 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 352364] ppc64: --expensive-definedness-checks=yes is not quite working here
https://bugs.kde.org/show_bug.cgi?id=352364 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #6 from Mark Wielaard --- Added a prereq to skip memcheck/tests/bug340392.vgtest on power: commit 94960fae328bc82fb1ea51ffb9273ad5f25936d2 (HEAD -> master) Author: Mark Wielaard Date: Mon Oct 30 21:41:57 2023 +0100 bug340392 doesn't work on power because of bug352364 Add a prereq to bug340392.vgtest to skip on Power for now. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 352364] ppc64: --expensive-definedness-checks=yes is not quite working here
https://bugs.kde.org/show_bug.cgi?id=352364 Mark Wielaard changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=340392 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 340392] Incorrect "Conditional jump..." message
https://bugs.kde.org/show_bug.cgi?id=340392 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org See Also||https://bugs.kde.org/show_b ||ug.cgi?id=352364 --- Comment #8 from Mark Wielaard --- Note that there is a variant of this bug for power: https://bugs.kde.org/show_bug.cgi?id=352364 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 402833] memcheck/tests/overlap testcase fails, memcpy seen as memmove
https://bugs.kde.org/show_bug.cgi?id=402833 --- Comment #9 from Mark Wielaard --- Created attachment 162737 --> https://bugs.kde.org/attachment.cgi?id=162737=edit disable overlap check and test for linux-amd64 More subtle workaround patch that only disables the overlap check (and test) on linux-amd64 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476333] New: helgrind/tests/getaddrinfo.vgtest fails randomly
https://bugs.kde.org/show_bug.cgi?id=476333 Bug ID: 476333 Summary: helgrind/tests/getaddrinfo.vgtest fails randomly Classification: Developer tools Product: valgrind Version: 3.22 GIT Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: helgrind Assignee: jsew...@acm.org Reporter: m...@klomp.org Target Milestone: --- Running perl tests/vg_regtest helgrind/tests/getaddrinfo.vgtest seems to randomly fail on various arches/distros. I now also got it to fail on x86_64 (RHEL8). I am on a bad wifi network at the moment, which might impact this. I suspect there really is a datarace in at least some versions of glibc when dns lookups are retried. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476331] New: clean up generated/distributed filter scripts
https://bugs.kde.org/show_bug.cgi?id=476331 Bug ID: 476331 Summary: clean up generated/distributed filter scripts Classification: Developer tools Product: valgrind Version: 3.22 GIT Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: m...@klomp.org Target Milestone: --- https://sourceforge.net/p/valgrind/mailman/message/49958270/ There are a couple of filter scripts generated for configure.ac but also included in the dist tar ball. drd/tests/filter_error_count drd/tests/filter_error_summary drd/tests/filter_stderr lter_stderr_and_thread_no_and_offset drd/tests/filter_thread_no drd/tests/filter_xml_and_thread_no gdbserver_tests/filter_gdb filter_memcheck_monitor gdbserver_tests/filter_stderr gdbserver_tests/filter_vgdb helgrind/tests/filter_stderr memcheck/tests/filter_dw4 memcheck/tests/filter_overlaperror memcheck/tests/filter_stderr memcheck/tests/x86/filter_pushfpopf tests/filter_discards tests/filter_stderr_basic All those filter scripts generated by configure.ac by AC_CONFIG_FILES from the .in files should not be in dist_noinst_SCRIPTS but in noinst_SCRIPTS. When doing this also update the tests/check_headers_and_includes script which is run at the end of make regtest and will check the scripts are listed correctly in the Makefile.am files: $ make post-regtest-checks ...checking makefile consistency memcheck/tests/Makefile.am:1: error: filter_dw4 is missing in dist_noinst_SCRIPTS -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417993] vbit-test fail on s390x with Iop_Add32: spurious dependency on uninitialised value
https://bugs.kde.org/show_bug.cgi?id=417993 --- Comment #12 from Mark Wielaard --- I think your analysis is correct. We already seem to do this when printing out a complaint about a real mismatch. See memcheck/tests/vbits-test/util.c (print_opnd): /* The value itself might be partially or fully undefined, so take a copy, paint the copy as defined, and print the copied value. This is so as to avoid error messages from Memcheck, which are correct, but confusing. */ And testing your 3 line fix on s390x it does seem to work as expected: $ perl tests/vg_regtest memcheck/tests/vbit-test/vbit-test.vgtest vbit-test: valgrind -q --expensive-definedness-checks=yes ./vbit-test == 1 test, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == I think my only question is whether we should "clear" all of data or just the value fields of the result and opnds[] of the test_data_t? I guess it doesn't matter whether the rest of the test_data_t struct values are cleared too, but it might "hide" other/real bugs? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476125] Valgrind cannot read binaries containing debug symbols in DWARF 64 format
https://bugs.kde.org/show_bug.cgi?id=476125 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #1 from Mark Wielaard --- In theory valgrind should be able to parse DWARF64, see the initial length field reading in readdwarf.c and readdwarf3.c which set an 64bit flag. But it doesn't surprise me that code/path isn't tested and probably fails since by default DWARF32 is used. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476108] vg_replace_malloc DELETE checks size
https://bugs.kde.org/show_bug.cgi?id=476108 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Mark Wielaard --- commit a8b6ee6b5f5efbd759c87fa987e9149800db2899 Author: Mark Wielaard Date: Thu Oct 26 12:25:44 2023 +0200 vg_replace_malloc DELETE should not check size The DELETE replacement functions check the size argument, but this doesn't actually exist. Only the DELETE_SIZED replacement functions get a size (and should check it). On i386 (fedora gnu/linux) this causes the following failures: memcheck/tests/cxx17_aligned_new (stderr) memcheck/tests/leak_cpp_interior (stderr) memcheck/tests/mismatches(stderr) memcheck/tests/mismatches_xml(stderr) memcheck/tests/new_aligned_delete_default (stderr) memcheck/tests/new_nothrow (stderr) memcheck/tests/realloc_size_zero_mismatch (stderr) All showing "size" being undefined: +Conditional jump or move depends on uninitialised value(s) + at 0x: ...operator delete[]... (vg_replace_malloc.c:...) or +Mismatched new/delete size value: 4 + at 0x: ...operator delete... (vg_replace_malloc.c:...) Oddly no other architecture seems to show issues. Maybe we just got lucky? This patch fixes the issues on i386 (and shows no regressions on x86_64) https://bugs.kde.org/show_bug.cgi?id=476108 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476108] New: vg_replace_malloc DELETE checks size
https://bugs.kde.org/show_bug.cgi?id=476108
Bug ID: 476108
Summary: vg_replace_malloc DELETE checks size
Classification: Developer tools
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: m...@klomp.org
CC: pjfl...@wanadoo.fr
Target Milestone: ---
The DELETE replacement functions check the size argument, but this doesn't
actually exist.
Only the DELETE_SIZED replacement functions get a size (and should check it).
On i386 (fedora gnu/linux) this causes the following failures:
memcheck/tests/cxx17_aligned_new (stderr)
memcheck/tests/leak_cpp_interior (stderr)
memcheck/tests/mismatches(stderr)
memcheck/tests/mismatches_xml(stderr)
memcheck/tests/new_aligned_delete_default (stderr)
memcheck/tests/new_nothrow (stderr)
memcheck/tests/realloc_size_zero_mismatch (stderr)
All showing "size" being undefined:
+Conditional jump or move depends on uninitialised value(s)
+ at 0x: ...operator delete[]... (vg_replace_malloc.c:...)
or
+Mismatched new/delete size value: 4
+ at 0x: ...operator delete... (vg_replace_malloc.c:...)
Oddly no other architecture seems to show issues. Maybe we just got lucky?
The following patch fixes the issues on i386 (and shows no regressions on
x86_64):
diff --git a/coregrind/m_replacemalloc/vg_replace_malloc.c
b/coregrind/m_replacemalloc/vg_replace_malloc.c
index e238a52f3..7859f5f32 100644
--- a/coregrind/m_replacemalloc/vg_replace_malloc.c
+++ b/coregrind/m_replacemalloc/vg_replace_malloc.c
@@ -1027,13 +1027,12 @@ extern int * __error(void) __attribute__((weak));
#define DELETE(soname, fnname, vg_replacement, tag) \
\
-void VG_REPLACE_FUNCTION_EZU(10050,soname,fnname) (void *p, SizeT size); \
-void VG_REPLACE_FUNCTION_EZU(10050,soname,fnname) (void *p, SizeT size) \
+void VG_REPLACE_FUNCTION_EZU(10050,soname,fnname) (void *p); \
+void VG_REPLACE_FUNCTION_EZU(10050,soname,fnname) (void *p) \
{ \
struct AlignedAllocInfo aligned_alloc_info = { .mem=p,
.alloc_kind=AllocKind##tag }; \
\
DO_INIT; \
- TRIGGER_MEMCHECK_ERROR_IF_UNDEFINED((UWord)size); \
VERIFY_ALIGNMENT(_alloc_info); \
MALLOC_TRACE(#fnname "(%p)\n", p ); \
if (p == NULL) \
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 456200] Valgrind should not require neon (simd) on armhf
https://bugs.kde.org/show_bug.cgi?id=456200 --- Comment #4 from Mark Wielaard --- I tried on an armbian 23.02.2 Buster, based on Debian 10.13, so fairly old. And with 6.1.11-rockchip, which has half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm. So it "worked" before already. It seems to also "work" with the patch. But, at least none/tests/arm/v6intThumb doesn't build (before/after the patch). And with that commented out, the make regtest results don't look very good (although the results are identical): == 717 tests, 74 stderr failures, 8 stdout failures, 3 stderrB failures, 2 stdoutB failures, 15 post failures == gdbserver_tests/mcblocklistsearch(stderrB) gdbserver_tests/mcinfcallWSRU(stderrB) gdbserver_tests/nlcontrolc (stdoutB) gdbserver_tests/nlgone_exit (stderrB) gdbserver_tests/nlvgdbsigqueue (stdoutB) memcheck/tests/dw4 (stderr) memcheck/tests/err_disable3 (stderr) memcheck/tests/err_disable4 (stderr) memcheck/tests/leak-cases-full (stderr) memcheck/tests/leak-cases-summary(stderr) memcheck/tests/leak-cycle(stderr) memcheck/tests/leak-segv-jmp (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/leak_cpp_interior (stderr) memcheck/tests/lks (stderr) memcheck/tests/new_aligned_delete_default (stderr) memcheck/tests/partiallydefinedeq(stderr) memcheck/tests/sem (stderr) memcheck/tests/sendmsg (stderr) memcheck/tests/supp_unknown (stderr) memcheck/tests/threadname(stderr) memcheck/tests/threadname_xml(stderr) memcheck/tests/varinfo2 (stderr) memcheck/tests/varinfo3 (stderr) memcheck/tests/varinfo4 (stderr) memcheck/tests/varinfo5 (stderr) memcheck/tests/varinfo6 (stderr) memcheck/tests/varinforestrict (stderr) memcheck/tests/vbit-test/vbit-test (stderr) helgrind/tests/annotate_rwlock (stderr) helgrind/tests/bar_bad (stderr) helgrind/tests/bug392331 (stderr) helgrind/tests/free_is_write (stderr) helgrind/tests/hg02_deadlock (stderr) helgrind/tests/hg03_inherit (stderr) helgrind/tests/hg04_race (stderr) helgrind/tests/hg04_race_h9 (stderr) helgrind/tests/hg05_race2(stderr) helgrind/tests/locked_vs_unlocked1_fwd (stderr) helgrind/tests/locked_vs_unlocked1_rev (stderr) helgrind/tests/locked_vs_unlocked2 (stderr) helgrind/tests/locked_vs_unlocked3 (stderr) helgrind/tests/pth_barrier1 (stderr) helgrind/tests/pth_barrier2 (stderr) helgrind/tests/pth_barrier3 (stderr) helgrind/tests/pth_destroy_cond (stderr) helgrind/tests/rwlock_race (stderr) helgrind/tests/tc01_simple_race (stderr) helgrind/tests/tc05_simple_race (stderr) helgrind/tests/tc06_two_races(stderr) helgrind/tests/tc06_two_races_xml(stderr) helgrind/tests/tc09_bad_unlock (stderr) helgrind/tests/tc14_laog_dinphils(stderr) helgrind/tests/tc16_byterace (stderr) helgrind/tests/tc19_shadowmem(stderr) helgrind/tests/tc20_verifywrap (stderr) helgrind/tests/tc21_pthonce (stderr) helgrind/tests/tc22_exit_w_lock (stderr) drd/tests/annotate_trace_memory (stderr) drd/tests/annotate_trace_memory_xml (stderr) drd/tests/atomic_var (stderr) drd/tests/hg03_inherit (stderr) drd/tests/hg05_race2 (stderr) drd/tests/pth_detached (stderr) drd/tests/pth_detached2 (stderr) drd/tests/pth_detached_sem (stderr) drd/tests/rwlock_race(stderr) drd/tests/tc19_shadowmem (stderr) drd/tests/tc21_pthonce (stderr) massif/tests/bug469146 (post) massif/tests/mmapunmap (post) massif/tests/new-cpp (post) massif/tests/overloaded-new (post) none/tests/arm/v6intThumb(stdout) none/tests/arm/v6intThumb(stderr) none/tests/arm/v8crypto_a(stdout) none/tests/arm/v8crypto_a(stderr) none/tests/arm/v8crypto_t(stdout) none/tests/arm/v8crypto_t(stderr) none/tests/arm/v8fpsimd_a(stdout) none/tests/arm/v8fpsimd_a(stderr) none/tests/arm/v8fpsimd_t(stdout) none/tests/arm/v8fpsimd_t(stderr) none/tests/arm/v8memory_a(stdout) none/tests/arm/v8memory_a(stderr) none/tests/arm/v8memory_t(stdout) none/
[valgrind] [Bug 456200] Valgrind should not require neon (simd) on armhf
https://bugs.kde.org/show_bug.cgi?id=456200 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #3 from Mark Wielaard --- The original reason for using -mcpu=cortex-a8 was: commit 68f57d0181acae56adf05e0987990c2b41081f48 Author: Julian Seward Date: Tue May 31 07:17:54 2011 + On arm-linux, give gcc "-mcpu=cortex-a8" so as to persuade it to accept the armv6t2 (I think) insns (movt, movw) in dispatch-arm-linux.S. Some older gccs apparently think they are compiling for armv6 by default and reject them (gcc 4.4.1 on Ubuntu 9.10, for one.) git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11793 So I think generic-armv7-a would be fine too. Have to find an 32bit arm machine to double check. But given that Debian apparently already made this change it is probably correct. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381819] amd64: unhandled instruction bextr (0x8F 0xEA 0x78 0x10 0xD0 0x8 0x4) from BMI1
https://bugs.kde.org/show_bug.cgi?id=381819 --- Comment #28 from Mark Wielaard --- *** Bug 448026 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 448026] unhandled instruction bytes: 0x8F 0x6A 0x78 0x10 0xC8 0x4 0x4 0x0 0x0 0xC1
https://bugs.kde.org/show_bug.cgi?id=448026 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Mark Wielaard --- This is BEXTR, Bit field extract (with register), part of BMI1 *** This bug has been marked as a duplicate of bug 381819 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 475652] Missing suppression for __wcsncpy_avx2 (strncpy-avx2.S:308)?
https://bugs.kde.org/show_bug.cgi?id=475652 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #5 from Mark Wielaard --- Note we already have a wcscpy test in memcheck/tests/wcs.c And a replacement function in shared/vg_replace_strmem.c The simplest fix would be to extend that wcscpy test/replacement to wcsncpy. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 475286] Valgrind won't install (missing archives)
https://bugs.kde.org/show_bug.cgi?id=475286 Mark Wielaard changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED CC||m...@klomp.org --- Comment #1 from Mark Wielaard --- This is a bug with your distro setup. Please report it there https://help.ubuntu.com/community/ReportingBugs -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 461074] DWARF2 CFI reader: unhandled DW_OP_ opcode 0x11 (consts) and DW_OP_ opcode 0x92 (bregx)
https://bugs.kde.org/show_bug.cgi?id=461074
Mark Wielaard changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
Summary|valgrind: |DWARF2 CFI reader:
|m_debuginfo/readdwarf.c:239 |unhandled DW_OP_ opcode
|6 |0x11 (consts) and DW_OP_
|(copy_convert_CfiExpr_tree) |opcode 0x92 (bregx)
|: Assertion 'srcix >= 0 && |
|srcix < VG_(sizeXA)(srcxa)' |
|failed. |
--- Comment #10 from Mark Wielaard ---
Thanks, that implementation of DW_OP_bregx is almost literally the same as what
I came up with.
I also implemented DW_OP_consts, which was reported in comment #1. And
DW_OP_const8s,
DW_OP_const8u and DW_OP_constu since they are fairly similar and were also
missing.
commit 9dd5db3cb1c46c50d29bf11a495a77e2669b847a
Author: Mark Wielaard
Date: Mon Oct 2 00:37:24 2023 +0200
Implement DW_OP_{bregx,consts,const8s,const8u,constu} in dwarfexpr_to_dag
readdwarf.c (dwarfexpr_to_dag) didn't hanle various DW_OP expressions
causing Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode and errors
m_debuginfo/readdwarf.c:2822 (copy_convert_CfiExpr_tree): Assertion
'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.
Implement DW_OP_bregx and DW_OP_consts as reported in bug #461074.
Also add implementations for DW_OP_const8s, DW_OP_const8u and
DW_OP constu.
https://bugs.kde.org/show_bug.cgi?id=461074
--
You are receiving this mail because:
You are watching all bug changes.
[kid3] [Bug 475055] Kid3 can't find file tag
https://bugs.kde.org/show_bug.cgi?id=475055 --- Comment #2 from Mark Fraser --- (In reply to Urs Fleisch from comment #1) > Without an example file, it is a bit hard to reproduce. Could you answer the > following questions: > > - M4A files can be parsed by both TagLib and mp4v2, what metadata plugins > are enabled in your settings? Does it happen with both? Note that you have > to restart Kid3 after changing plugin settings. If the "Mp4v2Metadata" > plugin is not listed, it is because libmp4v2 is not provided by your distro > and you could try the binary kid3-3.9.4-Linux.tgz from > https://kid3.kde.org/#download. I am using TagLib and Mp4v2Metadata isn't available, but I am using kid3 from the PPA. > - Could it be that this is the same situation as in > https://invent.kde.org/multimedia/kid3/-/issues/566? Could you compare the > output of `file` with those in that report? It could be as I've been using SoundKreator to rip the CDs, but in this case I found a copy of the file on another drive and that's fine. I do have some other files that are unreadable, but the smallest is 4.2M. -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 475055] New: Kid3 can't find file tag
https://bugs.kde.org/show_bug.cgi?id=475055 Bug ID: 475055 Summary: Kid3 can't find file tag Classification: Applications Product: kid3 Version: 3.9.x Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: mfraz74+...@gmail.com Target Milestone: --- SUMMARY I've viewed an album in mp4 format in Kid3 and it says that some tracks have no tags even though they are visible when using ffmpeg. STEPS TO REPRODUCE 1. Open directory in Kid3 2. See that some tracks say "No Tag" 3. Run ffmpeg -i and see that the tags are visible. ffmpeg -i 03Look\ What\ You\ Dun.m4a ffmpeg version 6.0-0ubuntu1~22.04.sav3 Copyright (c) 2000-2023 the FFmpeg developers [mov,mp4,m4a,3gp,3g2,mj2 @ 0x55ac5e1ca6c0] stream 0, timescale not set Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '03Look What You Dun.m4a': Metadata: major_brand : M4A minor_version : 512 compatible_brands: isomiso2 album_artist: Slade disc: 1 track : 3/20 artist : Slade album : The Very Best Of Slade date: 2005 genre : Glam Rock title : Look What You Dun Duration: 00:02:58.82, start: 0.00, bitrate: 147 kb/s Stream #0:0[0x1](eng): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 141 kb/s (default) Metadata: handler_name: SoundHandler vendor_id : [0][0][0][0] Stream #0:1[0x0]: Video: mjpeg (Baseline), yuvj444p(pc, bt470bg/unknown/unknown), 600x589, 90k tbr, 90k tbn (attached pic) SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-84-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 474863] New: Dropdown location does not center
https://bugs.kde.org/show_bug.cgi?id=474863 Bug ID: 474863 Summary: Dropdown location does not center Classification: Applications Product: yakuake Version: 22.12.3 Platform: Kubuntu OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: h...@kde.org Reporter: mjnijl...@gmail.com Target Milestone: --- SUMMARY When using a wide screen as a second screen e.g. 38-inch Dell, and Yakuake is set to drop down from the top in the center (30% width, 30% height), it drops down in the center of the primary screen dimension but to the left on the second, wider screen. STEPS TO REPRODUCE 1. Laptop screen 1 2. Dell widescreen screen 2 3. Set to dropdown at screen center on screen with the mouse pointer 4. Trigger dropdown by moving to screen edge or F12 OBSERVED RESULT The dropdown is shifted to the left on the widescreen (screen 2), and is in the center on the laptop screen (screen 1) EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 23.04 (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 461074] valgrind: m_debuginfo/readdwarf.c:2396 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.
https://bugs.kde.org/show_bug.cgi?id=461074 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #8 from Mark Wielaard --- Thanks that makes clear what is going wrong. The full expression is: def_cfa_expression 10 [ 0] breg31 0 [ 2] bregx 46 0 [ 5] lit8 [ 6] mul [ 7] plus_uconst 80 [ 9] plus And we do indeed not handle DW_OP_bregx (0x92). But since we do handle DW_OP_breg0 ... DW_OP_breg31 it shouldn't be too hard to handle DW_OP_bregx too (the difference is in how the register argument is part of the opcode in the first, but encoded as a uleb128 argument in the second. See dwarfexpr_to_dag in coregrind/m_debuginfo/readdwarf.c (and somewhat identical code, that does handle DW_OP_bregx in evaluate_Dwarf3_Expr coregrind/m_debuginfo/d3basics.c. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 461074] valgrind: m_debuginfo/readdwarf.c:2396 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.
https://bugs.kde.org/show_bug.cgi?id=461074 --- Comment #5 from Mark Wielaard --- Actually we have valgrind --debug-dump=frames so if you could rerun with that option and attach the output that would also be helpful. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 461074] valgrind: m_debuginfo/readdwarf.c:2396 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.
https://bugs.kde.org/show_bug.cgi?id=461074 --- Comment #4 from Mark Wielaard --- Thanks, so that is in libhwy_contrib.so.1.0.7 which is https://packages.debian.org/sid/libhwy1 and can be downloaded through http://ftp.debian.org/debian/pool/main/h/highway/libhwy1_1.0.7-7_arm64.deb Without an arm64 debian setup trying to unpack that and looking for the any DW_CFA expressions with suspecious DW_OP expressions might be helpful. Could you maybe attach the output of readelf --debug-dump=frames libhwy_contrib.so.1.0.7 ? grepping that output for DW_OP might also provide some clues. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 461074] valgrind: m_debuginfo/readdwarf.c:2396 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.
https://bugs.kde.org/show_bug.cgi?id=461074 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #2 from Mark Wielaard --- The first issue seems to be because we cannot handle the CFI from this libamath.so library. For the second it isn't clear which library causes the issue. Could you rerun with -v ? -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 332799] KTimeTracker Add/Edit task dialog uses non-standard theme for OK/Cancel buttons
https://bugs.kde.org/show_bug.cgi?id=332799 Mark Penner changed: What|Removed |Added Status|REOPENED|RESOLVED CC||mrpen...@mailbox.org Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kguiaddons] [Bug 467631] kguiaddons fails to build with qt6/kde6
https://bugs.kde.org/show_bug.cgi?id=467631 Mark Penner changed: What|Removed |Added CC||mrpen...@mailbox.org --- Comment #3 from Mark Penner --- I ran into this also with Qt 6.6 compiled with kdesrc-build on Debian unstable. To fix it I needed to add `-DQT_FEATURE_xcb=ON` to `cmake-options` and rebuild qt6-set (I'm not sure if rebuilding only qtbase would have been enough, so I built it all). I added it in `~/kde/src/kdesrc-build/qt6-build-include` but I think you could use `kdesrc-build qt6-set --cmake-options="-DQT_FEATURE_xcb=ON"` like it says on https://community.kde.org/Get_Involved/development/More#Build_Qt6_using_kdesrc-build, near the end of the section. I tried to find where QX11Application was defined, and I found https://invent.kde.org/qt/qt/qtbase/-/blob/6.6/src/gui/kernel/qguiapplication_platform.h?ref_type=heads#L41 in a `#if QT_CONFIG(xcb) || defined(Q_QDOC)` block. I'm not familiar with the Qt codebase and all the macros, but that's what made me try setting `-DQT_FEATURE_xcb=ON`, and kguiaddons compiled fine after rebuilding Qt. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443404] Mousewheel scroll does not work in full page size and non-continous mode for some mouses
https://bugs.kde.org/show_bug.cgi?id=443404 --- Comment #19 from Mark Fraser --- (In reply to an.inbox from comment #17) > Hi all, the issue is related to the use of the Logitech dongle. When using > Bluetooth there is no problem. > > I use the same mouse (Logitech M2S) on two machines. The laptop came first, > using BT: never had a problem. > Then I installed a PC, same OS (Debian Bookworm) but I got this same issue. > This PC has no BT so I used the dongle and this is when the scrolling issue > in okular appeared. > If I use the dongle on the laptop, there's a problem there too. > So those you can use BT, use BT as a work-around. > > So I don't know the reason for this, but the issue only comes when using the > mouse with its dongle. And it's only okular having this issue, only in page > mode. Okular in continuous mode or all other applications are OK. Still not working properly here even with Bluetooth. I have to scroll the wheel quite a bit to get it to move to the next page. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449620] Pointer constraints protocol not honored when switching from server side decorations to client side
https://bugs.kde.org/show_bug.cgi?id=449620 --- Comment #4 from Mark Bolhuis --- (In reply to David Edmundson from comment #3) > This bug was reported against an outdated version of KWin. We have made many > changes since the. > If the issue persists in newer versions can you reopen the bug report > updating the version number. I've run some tests again on 5.27.7 and can confirm that the bug no longer appears. I'm not sure what the problem was but I think it was something to do with Kwin preserving the entire frame size when toggling between SSD and CSD. IIRC on 5.23 the window was maintaining the same client area size, and the client area wasn't moved or resized until another configure cycle, but the frame bounds were moved, meaning that the pointer was being confined to a region that didn't match where the client area was. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 432801] Valgrind 3.16.1 reports a jump based on uninitialized memory somehow related to clang and signals
https://bugs.kde.org/show_bug.cgi?id=432801 --- Comment #53 from Mark Wielaard --- (In reply to Eyal from comment #52) > Y'all need CI, I can't even build the master branch. :-( We do have CI against various distros and arches: https://builder.sourceware.org/buildbot/#/builders?tags=valgrind And although some tests are failing it does seem to build everywhere. What is wrong with the build for you? How does it fail? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 473745] must-be-redirected function - strlen - for valgrind 3.22 but not 3.21
https://bugs.kde.org/show_bug.cgi?id=473745 Mark Wielaard changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #10 from Mark Wielaard --- commit 8228fe7f696b30c7b6b6daf576fc189bf8d6f8c2 Author: Mark Wielaard Date: Fri Sep 1 19:10:17 2023 +0200 Explicitly load libc and any sonames that contain mandatory specs We really need symtab for glibc and ld.so libraries early for redir. Some distros move these into separate debuginfo files, which means we need to fully load them early. https://bugs.kde.org/show_bug.cgi?id=473745 -- You are receiving this mail because: You are watching all bug changes.
