https://bugs.kde.org/show_bug.cgi?id=487439
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #8 from Mark
https://bugs.kde.org/show_bug.cgi?id=487296
--- Comment #3 from Mark Wielaard ---
For each inherited fd VG_(init_preopened_fds) calls
ML_(record_fd_open_named)(-1, fd);
So the ThreadId will be -1. Which ML_(record_fd_open_with_given_name) documents
as
"If the tid is -1, this indi
https://bugs.kde.org/show_bug.cgi?id=487296
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=487296
--- Comment #1 from Mark Wielaard ---
Nice. Thanks for catching this.
Yeah, it makes sense to start "tracking" std fds once they are closed (and
reopened).
One thought I had was that maybe this shouldn't be special cased for just
stdin/out/
https://bugs.kde.org/show_bug.cgi?id=487296
Mark Wielaard changed:
What|Removed |Added
CC||ahajk...@redhat.com
https://bugs.kde.org/show_bug.cgi?id=486876
Mark Penner changed:
What|Removed |Added
CC||mrpen...@mailbox.org
--- Comment #3 from Mark
https://bugs.kde.org/show_bug.cgi?id=486857
Mark changed:
What|Removed |Added
Summary|KWritesetting dynamic word |KWrite settings, dynamic
|wrap should
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: mark...@gmail.com
Target Milestone: ---
SUMMARY
So I was making this bug report to report dynamic word wrapping
https://bugs.kde.org/show_bug.cgi?id=317127
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #18 from Mark
https://bugs.kde.org/show_bug.cgi?id=479659
Mark Capella changed:
What|Removed |Added
CC||markcape...@twcny.rr.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=486586
Mark Fraser changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=486586
Bug ID: 486586
Summary: Can't delete tracks from media sources
Classification: Applications
Product: amarok
Version: 3.0.0
Platform: Ubuntu
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=486575
Bug ID: 486575
Summary: Alpaka can't select/copy text
Classification: Applications
Product: Alpaka
Version: unspecified
Platform: Arch Linux
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=486574
Bug ID: 486574
Summary: Alpaka doesn't work properly with the ollama systemd
service (it always repeats the first answer)
Classification: Applications
Product: Alpaka
Version:
https://bugs.kde.org/show_bug.cgi?id=486341
--- Comment #1 from Mark ---
Sorry, step 3 should say "Right-click a image from Geolocation Edit dialog list
and choose Edit Bookmarks"
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=486341
Bug ID: 486341
Summary: Edit Bookmarks menu item does nothing
Classification: Applications
Product: digikam
Version: 8.4.0
Platform: macOS (DMG)
OS: macOS
Status:
https://bugs.kde.org/show_bug.cgi?id=429654
--- Comment #9 from Mark Capella ---
I had fun learning how to add that panel ! :B
Ok, this is simpler :)
https://invent.kde.org/markcapella/knights/-/commit/4228eb38be92ce125e363b7a1d188a1364dd088a
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=459163
--- Comment #28 from Mark ---
(In reply to Maik Qualmann from comment #27)
> The map in the right sidebar is for viewing only. Like the metadata viewer,
> you cannot change this one either.
> The geolocation is edited in a separate window tha
https://bugs.kde.org/show_bug.cgi?id=459163
Mark changed:
What|Removed |Added
CC||m...@octabode.com
--- Comment #26 from Mark ---
I
https://bugs.kde.org/show_bug.cgi?id=486180
Mark Wielaard changed:
What|Removed |Added
CC||ar...@linux.ibm.com
--- Comment #7 from Mark
https://bugs.kde.org/show_bug.cgi?id=486293
Bug ID: 486293
Summary: memccpy false positives
Classification: Developer tools
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=486180
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=362680
Mark Wielaard changed:
What|Removed |Added
CC||v...@altlinux.org
--- Comment #6 from Mark
https://bugs.kde.org/show_bug.cgi?id=482358
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
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
https://bugs.kde.org/show_bug.cgi?id=485924
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
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
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
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"
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
https://bugs.kde.org/show_bug.cgi?id=482482
Mark S changed:
What|Removed |Added
CC||mspuban...@fastmail.us
--- Comment #4 from Mark S
https://bugs.kde.org/show_bug.cgi?id=485778
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=485778
Mark Wielaard changed:
What|Removed |Added
Attachment #168679|0 |1
is obsolete
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 testc
https://bugs.kde.org/show_bug.cgi?id=485778
Mark Wielaard changed:
What|Removed |Added
Assignee|jsew...@acm.org |m...@klomp.org
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=328563
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=362680
Mark Wielaard changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
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.
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
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
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.
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
https://bugs.kde.org/show_bug.cgi?id=485276
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #3 from Mark
https://bugs.kde.org/show_bug.cgi?id=472329
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
CC
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.
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
https://bugs.kde.org/show_bug.cgi?id=485487
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
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
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)
https://bugs.kde.org/show_bug.cgi?id=485487
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=485487
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #1 from Mark
https://bugs.kde.org/show_bug.cgi?id=463458
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=463463
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=481127
Mark Wielaard changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
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 w
https://bugs.kde.org/show_bug.cgi?id=481127
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=463458
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #1 from Mark
https://bugs.kde.org/show_bug.cgi?id=463456
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #1 from Mark
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.
https://bugs.kde.org/show_bug.cgi?id=463463
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #1 from Mark
https://bugs.kde.org/show_bug.cgi?id=377966
Mark Wielaard changed:
What|Removed |Added
Summary|Error message said to |arm64 unhandled instruction
https://bugs.kde.org/show_bug.cgi?id=479600
Mark Wielaard changed:
What|Removed |Added
Summary|Segmentation fault |Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=481874
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #9 from Mark
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
https://bugs.kde.org/show_bug.cgi?id=429654
Mark Capella changed:
What|Removed |Added
CC||markcape...@twcny.rr.com
--- Comment #2 from
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
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
https://bugs.kde.org/show_bug.cgi?id=484426
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #6 from Mark
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
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.
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.
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: Ignor
https://bugs.kde.org/show_bug.cgi?id=480248
Mark Rooks changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
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 detec
https://bugs.kde.org/show_bug.cgi?id=484002
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #2 from Mark
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
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
https://bugs.kde.org/show_bug.cgi?id=483791
Mark changed:
What|Removed |Added
CC||m...@leyva.me
--
You are receiving this mail because
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
https://bugs.kde.org/show_bug.cgi?id=483711
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #5 from Mark
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
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
https://bugs.kde.org/show_bug.cgi?id=471222
Mark Wielaard changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
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.
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
>
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
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:
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 Se
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
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:
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.
https://bugs.kde.org/show_bug.cgi?id=482358
Mark Wielaard changed:
What|Removed |Added
CC||ahajk...@redhat.com
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
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
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
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
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:
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
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
https://bugs.kde.org/show_bug.cgi?id=402820
Mark Fraser changed:
What|Removed |Added
CC||mfraz74+...@gmail.com
--- Comment #3 from Mark
1 - 100 of 2085 matches
Mail list logo