[kde] [Bug 490839] SOME SOFTWARE MAKES MY PC SLOW
https://bugs.kde.org/show_bug.cgi?id=490839 Paul Weyant changed: What|Removed |Added URL||https://oceanofgamees.com/ -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 490839] New: SOME SOFTWARE MAKES MY PC SLOW
https://bugs.kde.org/show_bug.cgi?id=490839 Bug ID: 490839 Summary: SOME SOFTWARE MAKES MY PC SLOW Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: oceanofgam...@gmail.com Target Milestone: --- "Hi there, I'm experiencing slow performance on my PC. I think it might be due to some software I have installed. Could you help me identify and potentially remove any programs that are causing the slowdown?" If you know specific software that might be the culprit, you can also add: "I suspect that [software name] might be contributing to the problem." Be ready to provide additional information like: When did the slowdowns start? What specific actions make the PC slow? Have you recently installed any new software or hardware? The more details you can give, the better equipped the technician will be to help you. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489180] plasma crashed in QtWaylandClient::QWaylandWindow::waylandScreen() when external monitor lost power
https://bugs.kde.org/show_bug.cgi?id=489180 Paul changed: What|Removed |Added CC|pwar...@pwarren.id.au | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490803] Digital clock - Wayland session - clipboard empty after copy date
https://bugs.kde.org/show_bug.cgi?id=490803 Paul Worrall changed: What|Removed |Added CC||p.r.worr...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 487081] Dark theme, Print Preview shows empty, prints white text on white background.
https://bugs.kde.org/show_bug.cgi?id=487081 Paul Worrall changed: What|Removed |Added CC||p.r.worr...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 487081] Dark theme, Print Preview shows empty, prints white text on white background.
https://bugs.kde.org/show_bug.cgi?id=487081 Paul Worrall changed: What|Removed |Added CC||erentar2...@gmail.com --- Comment #3 from Paul Worrall --- *** Bug 490734 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 490734] Printing from dark theme results in light text on light paper
https://bugs.kde.org/show_bug.cgi?id=490734 Paul Worrall changed: What|Removed |Added CC||p.r.worr...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Paul Worrall --- *** This bug has been marked as a duplicate of bug 487081 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 482568] Links don't convert cursor to a hand, and don't open when clicked
https://bugs.kde.org/show_bug.cgi?id=482568 Paul Worrall changed: What|Removed |Added CC||p.r.worr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 490520] Unsupported instruction in amd test
https://bugs.kde.org/show_bug.cgi?id=490520
--- Comment #3 from Paul Floyd ---
I've been using LLVM compilers for several years without any issues.
Are you seeing configure passing this test:
# does the x86/amd64 assembler understand the LOOPNEL instruction?
# Note, this doesn't generate a C-level symbol. It generates a
# automake-level symbol (BUILD_LOOPNEL_TESTS), used in test Makefile.am's
AC_MSG_CHECKING([if x86/amd64 assembler supports 'loopnel'])
AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[]], [[
do {
__asm__ __volatile__("1: loopnel 1b\n");
} while (0)
]])], [
ac_have_as_loopnel=yes
AC_MSG_RESULT([yes])
], [
ac_have_as_loopnel=no
AC_MSG_RESULT([no])
])
AM_CONDITIONAL([BUILD_LOOPNEL_TESTS], [test x$ac_have_as_loopnel = xyes])
and hence none/tests/amd64/Makefile gets a rule to build the loopnel test, but
then "make check" fails to build the loopnel testcase?
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 490375] No layer is selected on opening a document in Krita
https://bugs.kde.org/show_bug.cgi?id=490375 --- Comment #9 from Paul Stenning --- Thank you Dmitry for investigating and fixing this bug. Will this fix be released as part of 5.2.4 or as an update to 5.2.3? Sorry, I'm a new user and don't know how the releases and bug fixes work. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 490520] Unsupported instruction in amd test
https://bugs.kde.org/show_bug.cgi?id=490520 Paul Floyd changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 490538] some apps making my computer run slow
https://bugs.kde.org/show_bug.cgi?id=490538 Paul Worrall changed: What|Removed |Added Component|general |Spam Status|REPORTED|RESOLVED URL|https://netboxgold.net/ | Assignee|unassigned-b...@kde.org |n...@kde.org Product|kde |Spam CC||p.r.worr...@gmail.com Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 490520] Unsupported instruction in amd test
https://bugs.kde.org/show_bug.cgi?id=490520
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #1 from Paul Floyd ---
The testcase has been there for 13 years. There is a configure test for loopnel
and if the assembler does not support it the testcase does not get built.
Does that mean that AMD are now making CPUs that have removed this opcode?
GCC supports it https://godbolt.org/z/5Wrqrqev1 and it works fine on my old
Xeon PC.
LLVM doesn't support it
paulf> clang -g -o loopnel loopnel.c
loopnel.c:8:17: error: invalid instruction mnemonic 'loopnel'
asm volatile ("1: addq $1, %0; loopnel 1b" : "+a" (rax), "+c" (rcx) : :
"cc");
^
:1:20: note: instantiated into assembly here
1: addq $1, %rax; loopnel 1b
I ought to look at that one day.
Finally I just tested on a machine that is
Model name: AMD EPYC 7773X 64-Core Processor
and it works OK.
Other than AMD not documenting it (and LLVM not accepting the mnemonic) I don't
see any problem.
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 490473] Discover won't install packages from Arch repos
https://bugs.kde.org/show_bug.cgi?id=490473 Paul Worrall changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 490488] spam
https://bugs.kde.org/show_bug.cgi?id=490488 Paul Worrall changed: What|Removed |Added Product|kde |Spam Component|general |Spam Assignee|unassigned-b...@kde.org |n...@kde.org CC||p.r.worr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 490473] Discover won't install packages from Arch repos
https://bugs.kde.org/show_bug.cgi?id=490473 Paul Worrall changed: What|Removed |Added CC||p.r.worr...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Paul Worrall --- Have you installed packagekit-qt6? Also, worth reading the warning at: https://wiki.archlinux.org/title/KDE#Discover_does_not_show_any_applications -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 490485] Travel Agent In Sikkim
https://bugs.kde.org/show_bug.cgi?id=490485 Paul Worrall changed: What|Removed |Added Resolution|--- |NOT A BUG CC||p.r.worr...@gmail.com Status|REPORTED|RESOLVED Assignee|unassigned-b...@kde.org |n...@kde.org Component|general |Spam URL|https://www.traveltourister | |.com/india/sikkim-tour-pack | |ages/ | Product|kde |Spam -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 490436] Andaman Travel Agent specializes in creating unforgettable island experiences, offering tailored packages that highlight pristine beaches, adventurous activities, and cultural insi
https://bugs.kde.org/show_bug.cgi?id=490436 Paul Worrall changed: What|Removed |Added Assignee|unassigned-b...@kde.org |n...@kde.org Resolution|--- |NOT A BUG Product|kde |Spam Status|REPORTED|RESOLVED Component|general |Spam -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 490396] Impossible validation of exiftool.exe even though it is present in the Digikam folder.
https://bugs.kde.org/show_bug.cgi?id=490396 --- Comment #1 from Jean Paul Eby --- Created attachment 171730 --> https://bugs.kde.org/attachment.cgi?id=171730=edit Log install 8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 490396] New: Impossible validation of exiftool.exe even though it is present in the Digikam folder.
https://bugs.kde.org/show_bug.cgi?id=490396 Bug ID: 490396 Summary: Impossible validation of exiftool.exe even though it is present in the Digikam folder. Classification: Applications Product: digikam Version: 8.4.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Bundle-Windows Assignee: digikam-bugs-n...@kde.org Reporter: jp...@orange.fr Target Milestone: --- Created attachment 171729 --> https://bugs.kde.org/attachment.cgi?id=171729=edit Screenshot V 8.4.0 Hi, After installing digiKam-8.4.0-Qt6-Win64.exe under Windows 10 exiftool.exe considered missing. However exiftool.exe is still present in the Digikam folder despite a selection via open, it remains absent.. Best regard, -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490381] Digital Clock manual font chooser white text on white background in dark mode
https://bugs.kde.org/show_bug.cgi?id=490381 Paul Worrall changed: What|Removed |Added CC||p.r.worr...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 490254] Health, Tech, Travel, Finance, Environment, Education
https://bugs.kde.org/show_bug.cgi?id=490254 Paul Worrall changed: What|Removed |Added Assignee|unassigned-b...@kde.org |n...@kde.org CC||p.r.worr...@gmail.com Product|kde |Spam Component|general |Spam -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 490182] memcheck fails with message "Assertion `offsetB < 4096' failed" when using a large number of active registers and tracking origins on aarch64 machine
https://bugs.kde.org/show_bug.cgi?id=490182
--- Comment #2 from Paul Floyd ---
That's probably this bit
case HRcVec128: {
HReg x21 = hregARM64_X21(); // baseblock
HReg x9 = hregARM64_X9(); // spill temporary
vassert(0 == (offsetB & 15)); // check sane alignment
vassert(offsetB < 4096);
It looks like
vreg_state[v_idx].spill_offset
= toShort(con->guest_sizeB * 3 + ss_no * 8);
guest_sizeB is 944, so *3 that's 2832.
ssno is less than this constant
# define N_SPILL64S (LibVEX_N_SPILL_BYTES / 8)
and
#define LibVEX_N_SPILL_BYTES 4096
Lastly
for (ss_no = 0; ss_no < N_SPILL64S; ss_no++) {
if (ss_busy_until_before[ss_no] <= vreg_state[v_idx].live_after)
break;
}
if (ss_no == N_SPILL64S) {
vpanic("N_SPILL64S is too low in VEX. Increase and recompile.");
}
That looks inconsistent with the asserts. ss_no can go up to 512 in the above
code. But the calculation of spill_offset includes guest plus 2 shadows which
leaves only 1264 bytes or 148 spill registers.
Not sure how to fix this.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-baloo] [Bug 490210] New: Baloo File Extractor
https://bugs.kde.org/show_bug.cgi?id=490210
Bug ID: 490210
Summary: Baloo File Extractor
Classification: Frameworks and Libraries
Product: frameworks-baloo
Version: 6.3.0
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: Baloo File Daemon
Assignee: baloo-bugs-n...@kde.org
Reporter: rhodr...@gmail.com
Target Milestone: ---
Application: baloo_file_extractor (6.3.0)
Qt Version: 6.7.2
Frameworks Version: 6.3.0
Operating System: Linux 6.9.8-200.fc40.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 40 (KDE Plasma)"
DrKonqi: 6.1.2 [CoredumpBackend]
-- Information about the crash:
Had setup new Fedora40 Plasma system. Had restored info in /data folder from
Grsync backup. All ok. Installed /home info from borg backup using borg-extract
command. All files are ok but this error started appearing & will not go away.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation
fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[New LWP 21606]
[New LWP 21655]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/libexec/kf6/baloo_file_extractor'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
[Current thread is 1 (Thread 0x7fb300769f40 (LWP 21606))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7fb300769f40 (LWP 21606))]
Thread 2 (Thread 0x7f72f06006c0 (LWP 21655)):
#0 0x7fb30271c67d in __GI___poll (fds=0x564f054cfed0, nfds=2, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x7fb30137cc34 in g_main_context_poll_unlocked (priority=2147483647,
context=0x7f72e8000c60, timeout=, fds=0x564f054cfed0, n_fds=2)
at ../glib/gmain.c:4521
#2 g_main_context_iterate_unlocked.isra.0
(context=context@entry=0x7f72e8000c60, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4212
#3 0x7fb30131c383 in g_main_context_iteration (context=0x7f72e8000c60,
may_block=1) at ../glib/gmain.c:4282
#4 0x7fb3030850a3 in QEventDispatcherGlib::processEvents
(this=0x7f72e8000b70, flags=...) at
/usr/src/debug/qt6-qtbase-6.7.2-3.fc40.x86_64/src/corelib/kernel/qeventdispatcher_glib.cpp:394
#5 0x7fb302da3b03 in QEventLoop::exec (this=this@entry=0x7f72f05ffaa0,
flags=..., flags@entry=...) at
/usr/src/debug/qt6-qtbase-6.7.2-3.fc40.x86_64/src/corelib/global/qflags.h:34
#6 0x7fb302eb7e4f in QThread::exec (this=this@entry=0x7fb302bfecc0
>::instance()::holder>) at
/usr/src/debug/qt6-qtbase-6.7.2-3.fc40.x86_64/src/corelib/global/qflags.h:74
#7 0x7fb302b6fe41 in QDBusConnectionManager::run (this=0x7fb302bfecc0
>::instance()::holder>) at
/usr/src/debug/qt6-qtbase-6.7.2-3.fc40.x86_64/src/dbus/qdbusconnectionmanager.cpp:144
#8 0x7fb302f5463c in operator() (__closure=) at
/usr/src/debug/qt6-qtbase-6.7.2-3.fc40.x86_64/src/corelib/thread/qthread_unix.cpp:326
#9 (anonymous
namespace)::terminate_on_exception >
(t=...) at
/usr/src/debug/qt6-qtbase-6.7.2-3.fc40.x86_64/src/corelib/thread/qthread_unix.cpp:262
#10 QThreadPrivate::start (arg=0x7fb302bfecc0
>::instance()::holder>) at
/usr/src/debug/qt6-qtbase-6.7.2-3.fc40.x86_64/src/corelib/thread/qthread_unix.cpp:285
#11 0x7fb3026a6507 in start_thread (arg=) at
pthread_create.c:447
#12 0x7fb30272a40c in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Thread 1 (Thread 0x7fb300769f40 (LWP 21606)):
[KCrash Handler]
#5 0x7fb302e12693 in QArrayDataPointer::QArrayDataPointer
(this=0x7ffe3825ba10, other=...) at
/usr/src/debug/qt6-qtbase-6.7.2-3.fc40.x86_64/src/corelib/tools/qarraydatapointer.h:38
#6 QString::QString (this=0x7ffe3825ba10, other=...) at
/usr/src/debug/qt6-qtbase-6.7.2-3.fc40.x86_64/src/corelib/text/qstring.h:1186
#7 QVariant::Private::Private (this=0x7ffe3825ba10, t=...) at
/usr/src/debug/qt6-qtbase-6.7.2-3.fc40.x86_64/src/corelib/kernel/qvariant_p.h:98
#8 QVariant::QVariant (this=this@entry=0x7ffe3825ba10, val=...) at
/usr/src/debug/qt6-qtbase-6.7.2-3.fc40.x86_64/src/corelib/kernel/qvariant.cpp:948
#9 0x7fb30214da8c in standardDeclarationForNode (node=...) at
/usr/src/debug/qt6-qtbase-6.7.2-3.fc40.x86_64/src/corelib/tools/qlist.h:183
#10 0x7fb30214ebca in QTextHtmlParser::declarationsForNode
(this=this@entry=0x7ffe3825bdf0, node=1453) at
/usr/src/debug/qt6-qtbase-6.7.2-3.fc40.x86_64/src/gui/text/qtexthtmlparser.cpp:2159
#11 0x7fb30214f8a0 in QTextHtmlParser::parseTag (this=0x7ffe3825bdf0) at
/usr/src/debug/qt6-qtbase-6.7.2-3.fc40.x86_64/src/gui/text/qtexthtmlparser.cpp:676
#12
[valgrind] [Bug 490182] memcheck fails with message "Assertion `offsetB < 4096' failed" when using a large number of active registers and tracking origins on aarch64 machine
https://bugs.kde.org/show_bug.cgi?id=490182 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 Paul Worrall changed: What|Removed |Added CC||p.r.worr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 490158] New: Geolocation additions from XMP files in RAW
https://bugs.kde.org/show_bug.cgi?id=490158 Bug ID: 490158 Summary: Geolocation additions from XMP files in RAW Classification: Applications Product: digikam Version: 8.3.0 Platform: Microsoft Windows OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Geolocation-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jp...@orange.fr Target Milestone: --- Hi, Many RAW photos geocoded from external software, and not when taken by photo equipment, have GPS coordinates in an XML file. In addition, this XML file can be polluted by adjustment or cropping parameters proprietary to software, Lightroom or other. In photo archiving the systematic presence of XML significantly reduces the capacity of hard drives and could be deleted but the geocoding is lost if RAW is taken out of Digikam +=+=+=+ Importing into Digikam supports these coordinates in your database when they exist. Writing GPS data to the RAW is possible via: - "Item" > "Edit Geolocation" but requests a deletion then copies the coordinates and altitudes to write its data in the RAW - "Item > "Write Metadata to File" after selecting all RAW. Could you not offer in the "Edotor Geolocation" screen or in the "Item" menu a "Write Geolocation" from the XMP or information from the database in the RAW list ? Thank you in advance for your arbitration. Best regard -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 490145] My Windows 10 starts to hang when I open big apps
https://bugs.kde.org/show_bug.cgi?id=490145 Shawn Paul changed: What|Removed |Added URL||https://tentackles.com/ -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 490145] New: My Windows 10 starts to hang when I open big apps
https://bugs.kde.org/show_bug.cgi?id=490145 Bug ID: 490145 Summary: My Windows 10 starts to hang when I open big apps Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: tentackles.soc...@gmail.com Target Milestone: --- My Windows 10 starts to hang when I open big apps. It's been happening consistently for the past few days. I've tried restarting and updating the system, but the issue persists. The problem seems worse with high-memory applications. Can you help me identify and fix what's causing this? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 391311] [Patch] Fix arm64 valgrind tests compilation with clang
https://bugs.kde.org/show_bug.cgi?id=391311 --- Comment #2 from Paul Floyd --- Other than the +#if defined(__ARM_FEATURE_CRYPTO) bits all these have been addressed (and sime without using clang conditional blocks). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 391311] [Patch] Fix arm64 valgrind tests compilation with clang
https://bugs.kde.org/show_bug.cgi?id=391311 --- Comment #1 from Paul Floyd --- I may well have reinvented this wheel with the port to FreeBSD arm64, which also uses the LLVM toolchain. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 391311] [Patch] Fix arm64 valgrind tests compilation with clang
https://bugs.kde.org/show_bug.cgi?id=391311 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pjfl...@wanadoo.fr CC||pjfl...@wanadoo.fr -- 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 --- Comment #10 from Paul Floyd --- I have some credits on AWS, so I could probably test it there. -- 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 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489893] Windows on some screens resize to 132 pixels vertical height during screen saver
https://bugs.kde.org/show_bug.cgi?id=489893 --- Comment #3 from Paul Hands --- Created attachment 171467 --> https://bugs.kde.org/attachment.cgi?id=171467=edit Desktop after shrink -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489893] Windows on some screens resize to 132 pixels vertical height during screen saver
https://bugs.kde.org/show_bug.cgi?id=489893 --- Comment #2 from Paul Hands --- Created attachment 171466 --> https://bugs.kde.org/attachment.cgi?id=171466=edit Desktop before shrink -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489893] Windows on some screens resize to 132 pixels vertical height during screen saver
https://bugs.kde.org/show_bug.cgi?id=489893 --- Comment #1 from Paul Hands --- Using xwininfo shows that all windows that get resized all have a vertical height of 132 pixels. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489893] New: Windows on some screens resize to 132 pixels vertical height during screen saver
https://bugs.kde.org/show_bug.cgi?id=489893 Bug ID: 489893 Summary: Windows on some screens resize to 132 pixels vertical height during screen saver Classification: Plasma Product: kwin Version: 6.1.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: jpha...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Some windows on some screens resize to 132 pixels height (width unchanged) and move to the top of the screen, some time after the system has been in screen saver. Not all windows get resized. Not all windows for a certain application get resized. One monitor's (the lowest priority) windows don't seem to get resized at all. It happens on all 6 of my virtual desktops. It occurs some time after the system switches to screen saver mode, but not immediately...switching the screen saver off quickly shows that the resizing hasn't yet happens, but I haven't any idea when it happens, or how to find out. Before and after screenshots are attached. SOFTWARE/OS AND Hardware INFO Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-41-generic (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 46.9 GiB of RAM Graphics Processor: AMD Radeon RX 6600 Manufacturer: ASUS ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 419897] Error when accessing filesystem. sshfs finished with exit code 1
https://bugs.kde.org/show_bug.cgi?id=419897 Paul Worrall changed: What|Removed |Added CC|p.r.worr...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489851] Kwin crashes when dragging an app from Kickoff to desktop
https://bugs.kde.org/show_bug.cgi?id=489851 Paul Worrall changed: What|Removed |Added Resolution|--- |DUPLICATE CC||p.r.worr...@gmail.com Status|REPORTED|RESOLVED --- Comment #2 from Paul Worrall --- *** This bug has been marked as a duplicate of bug 489811 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489811] Plasma shell crashes when dragging an application from application launcher to desktop on Wayland
https://bugs.kde.org/show_bug.cgi?id=489811 Paul Worrall changed: What|Removed |Added CC||jjaruszew...@outlook.com --- Comment #3 from Paul Worrall --- *** Bug 489851 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 489852] System Settings crash after click on "Sound" menu
https://bugs.kde.org/show_bug.cgi?id=489852 Paul Worrall changed: What|Removed |Added CC||p.r.worr...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Paul Worrall --- *** This bug has been marked as a duplicate of bug 487655 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 487655] crash when opening sound KCM for a second time
https://bugs.kde.org/show_bug.cgi?id=487655 Paul Worrall changed: What|Removed |Added CC||tuxb...@tutamail.com --- Comment #13 from Paul Worrall --- *** Bug 489852 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489811] Plasma shell crashes when dragging an application from application launcher to desktop on Wayland
https://bugs.kde.org/show_bug.cgi?id=489811 Paul Worrall changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||p.r.worr...@gmail.com --- Comment #2 from Paul Worrall --- I can reproduce this if desktop layout is Folder View. Works OK in Desktop layout Operating System: Arch Linux KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.7-arch1-1 (64-bit) Graphics Platform: Wayland Graphics Processor: AMD CEDAR -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 255494] illegal opcode memcpy in /lib/ld-2.8.so
https://bugs.kde.org/show_bug.cgi?id=255494 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 317127] Fedora18/x86_64 --sanity-level=3 : aspacem segment mismatch
https://bugs.kde.org/show_bug.cgi?id=317127 Paul Floyd changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #23 from Paul Floyd --- commit 3b06d458ffc5cc8de8d701926e5d86979185fa04 (HEAD -> master, origin/master, origin/HEAD) Author: Mark Wielaard Date: Thu Jul 4 15:21:39 2024 +0200 Avoid dev/inode check on btrfs with --sanity-level=3 With --sanity-level=3 or higher the aspacemgr sanity checks the device/inode numbers from /proc/self/maps to the file stat results. These don't match on btrfs. So detect when a file is on a btrfs volume and ignore the check in that case. https://bugs.kde.org/show_bug.cgi?id=317127 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 463459] Rotated/flipped image is saved incorrectly
https://bugs.kde.org/show_bug.cgi?id=463459 Paul Worrall changed: What|Removed |Added CC||pavel.uru...@gmail.com --- Comment #5 from Paul Worrall --- *** Bug 489733 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 489733] Gwenview corrupts some JPEG files after mirroring and saving
https://bugs.kde.org/show_bug.cgi?id=489733 Paul Worrall changed: What|Removed |Added Resolution|--- |DUPLICATE CC||p.r.worr...@gmail.com Status|CONFIRMED |RESOLVED --- Comment #4 from Paul Worrall --- *** This bug has been marked as a duplicate of bug 463459 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 489707] Conditional jump or move depends on uninitialised value(s)" shouldn't apply to assertions.
https://bugs.kde.org/show_bug.cgi?id=489707 --- Comment #1 from Paul Floyd --- First, are you certain that it was only the change from Valgrind 3.18.1 to Valgrind 3.23 that caused the change? I just checked out the code for 3.18.1 and using GCC 14.1 on RHEL 7..6 I get the same error with both that version and git HEAD. Second, there is no way for us to know when an expression is used in an assert. On amd64 your example code produces 40114a: c6 00 01movb $0x1,(%rax) 40114d: 48 8b 45 f0 mov-0x10(%rbp),%rax 401151: 48 3d ff 00 00 00 cmp$0xff,%rax 401157: 76 19 jbe401172 401159: b9 23 20 40 00 mov$0x402023,%ecx 40115e: ba 09 00 00 00 mov$0x9,%edx 401163: be 04 20 40 00 mov$0x402004,%esi 401168: bf 10 20 40 00 mov$0x402010,%edi 40116d: e8 be fe ff ff call 401030 <__assert_fail@plt> 401172: b8 00 00 00 00 mov$0x0,%eax 401177: c9 leave 401178: c3 ret where the opcodes 401151: 48 3d ff 00 00 00 cmp$0xff,%rax 401157: 76 19 jbe401172 are triggering the error. At the moment of the error we can't tell that the false case leads to a call to __assert_fail. Thirdly, and this is the really fundamental problem, you don't seem to understand the nature of Undefined Behaviour. There are two possibilities. Either your program text is well-formed or it is ill-formed. If it is well-formed then you can reason about it. You can say things like "if A is true then B should happen". If it is ill-formed then that is it. You cannot reason about ill-formed code. See https://en.cppreference.com/w/c/language/behavior and https://youtu.be/yG1OZ69H_-o?feature=shared So, in summary 1. this would be difficult to impllement 2. I think that it would be a serious mistake for us to do anything that masks UB. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 489707] Conditional jump or move depends on uninitialised value(s)" shouldn't apply to assertions.
https://bugs.kde.org/show_bug.cgi?id=489707 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 468575] Add support for RISC-V
https://bugs.kde.org/show_bug.cgi?id=468575 --- Comment #20 from Paul Floyd --- And regtest results == 737 tests, 6 stderr failures, 2 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures == gdbserver_tests/hgtls(stdoutB) memcheck/tests/pointer-trace (stderr) none/tests/double_close_range(stderr) none/tests/double_close_range_sup(stderr) none/tests/double_close_range_xml(stderr) none/tests/riscv64/compressed(stdout) none/tests/riscv64/compressed(stderr) none/tests/riscv64/integer (stdout) none/tests/riscv64/integer (stderr) I've seen memcheck/tests/pointer-trace issues before where the working directory is on NFS. Not riscv related. The double_close_range tests are fairly new and may need some extra filtering. The two riscv64 fails look like a problem with the toolchain. I'll see if trying a local build of the toolchain helps. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 489221] Unrecognized instruction: _mm256_cvtps_ph (vcvtps2ph)
https://bugs.kde.org/show_bug.cgi?id=489221 Paul Floyd changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REOPENED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 489221] Unrecognized instruction: _mm256_cvtps_ph (vcvtps2ph)
https://bugs.kde.org/show_bug.cgi?id=489221 --- Comment #7 from Paul Floyd --- Is it OK to close this item then? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489535] New: Turning off TV and AV Receiver connected via HDMI
https://bugs.kde.org/show_bug.cgi?id=489535 Bug ID: 489535 Summary: Turning off TV and AV Receiver connected via HDMI Classification: Plasma Product: plasmashell Version: 6.1.1 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: pwar...@pwarren.id.au Target Milestone: 1.0 Application: plasmashell (6.1.1) Qt Version: 6.7.2 Frameworks Version: 6.3.0 Operating System: Linux 6.9.6-1-default x86_64 Windowing System: Wayland Distribution: openSUSE Tumbleweed DrKonqi: 6.1.1 [CoredumpBackend] -- Information about the crash: When I turn off my AV reciever and TV, sometimes when I come back I get these plasmashell crashes. But not every time :( Intel graphics -> HDMI 2.0 -> Yamaha RX-A6A -> HDMI 2.1 -> Sony X90L Have the necessary pieces in place for enabling HDR output on the Intel Iris XE integrated graphics on an Asus NUC. OpenSuse Tumbleweed The crash can be reproduced sometimes. -- Backtrace: Application: plasmashell (plasmashell), signal: Segmentation fault Downloading separate debug info for /usr/bin/plasmashell... [New LWP 12479] [New LWP 12490] [New LWP 12480] [New LWP 12492] [New LWP 12481] [New LWP 12483] [New LWP 12489] [New LWP 12482] [New LWP 12484] [New LWP 12491] Downloading separate debug info for /lib64/libKF6DBusAddons.so.6... Downloading separate debug info for /lib64/libKF6StatusNotifierItem.so.6... Downloading separate debug info for /lib64/libKF6XmlGui.so.6... Downloading separate debug info for /lib64/libLayerShellQtInterface.so.6... Downloading separate debug info for /lib64/libKWaylandClient.so.6... Downloading separate debug info for /lib64/libPlasmaQuick.so.6... Downloading separate debug info for /lib64/libkworkspace6.so.6... Downloading separate debug info for /lib64/libKF6UserFeedbackCore.so.6... Downloading separate debug info for /lib64/libxcb.so.1... Downloading separate debug info for /lib64/libKF6Crash.so.6... Downloading separate debug info for /lib64/libKF6Solid.so.6... Downloading separate debug info for /lib64/libKF6Service.so.6... Downloading separate debug info for /lib64/libPlasma.so.6... Downloading separate debug info for /lib64/libKF6GlobalAccel.so.6... Downloading separate debug info for /lib64/libKF6Package.so.6... Downloading separate debug info for /lib64/libKF6Svg.so.6... Downloading separate debug info for /lib64/libKF6CoreAddons.so.6... Downloading separate debug info for /lib64/libKF6WindowSystem.so.6... Downloading separate debug info for /lib64/libPlasmaActivities.so.6... Downloading separate debug info for /lib64/libKF6ConfigQml.so.6... Downloading separate debug info for /lib64/libKF6ConfigGui.so.6... Downloading separate debug info for /lib64/libKF6ConfigCore.so.6... Downloading separate debug info for /lib64/libKF6I18n.so.6... Downloading separate debug info for /lib64/libQt6Quick.so.6... Downloading separate debug info for /lib64/libQt6Qml.so.6... Downloading separate debug info for /lib64/libQt6Gui.so.6... Downloading separate debug info for /lib64/libQt6DBus.so.6... Downloading separate debug info for /lib64/libstdc++.so.6... Downloading separate debug info for /lib64/libc.so.6... Downloading separate debug info for /lib64/libQt6Xml.so.6... Downloading separate debug info for /lib64/libQt6Network.so.6... Downloading separate debug info for /lib64/libQt6PrintSupport.so.6... Downloading separate debug info for /lib64/libKF6ItemViews.so.6... Downloading separate debug info for /lib64/libKF6IconWidgets.so.6... Downloading separate debug info for /lib64/libKF6ConfigWidgets.so.6... Downloading separate debug info for /lib64/libKF6WidgetsAddons.so.6... Downloading separate debug info for /lib64/libKF6IconThemes.so.6... Downloading separate debug info for /lib64/libKF6ColorScheme.so.6... Downloading separate debug info for /lib64/libKF6GuiAddons.so.6... Downloading separate debug info for /lib64/libKF6KIOWidgets.so.6... Downloading separate debug info for /lib64/libKF6KCMUtilsQuick.so.6... Downloading separate debug info for /lib64/libKF6KIOCore.so.6... Downloading separate debug info for /lib64/libKF6Notifications.so.6... Downloading separate debug info for /lib64/libm.so.6... Downloading separate debug info for /lib64/libXau.so.6... Downloading separate debug info for /lib64/libxcb-randr.so.0... Downloading separate debug info for /lib64/libX11.so.6... Downloading separate debug info for /lib64/libgcc_s.so.1... Downloading separate debug info for /lib64/libudev.so.1... Downloading separate debug info for /lib64/libmount.so.1... Downloading separate debug info for /lib64/libimobiledevice-1.0.so.6... Downloading separate debug info for /lib64/libplist-2.0.so.4... Downloading separate debug info for /lib64/libKF6Archive.so.6... Downloading separate debug info for /lib64/libQt6Svg.so.6... Downloading
[valgrind] [Bug 489338] arm64: Instruction fcvtas should round 322.5 to 323, but result is 322.
https://bugs.kde.org/show_bug.cgi?id=489338 Paul Floyd changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Paul Floyd --- Pushed with a small change to use True and False rather than 1 and 0. I'll add a couple of tests as well. commit de4c79ffbcd2d5e89495cee8feadf77d5f3a6ef2 (HEAD -> master, origin/master, origin/HEAD) Author: Bernhard <9C>belacker Date: Thu Jun 27 22:51:09 2024 +0200 arm64: Fix fcvtas instruction. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 489437] When opening jpeg file the background layer is not ticked
https://bugs.kde.org/show_bug.cgi?id=489437 Paul Stenning changed: What|Removed |Added CC||p...@paulstenning.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 489437] New: When opening jpeg file the background layer is not ticked
https://bugs.kde.org/show_bug.cgi?id=489437 Bug ID: 489437 Summary: When opening jpeg file the background layer is not ticked Classification: Applications Product: krita Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: p...@paulstenning.com Target Milestone: --- SUMMARY When opening a jpeg file the Background layer is not ticked, so several tools are not available. This behavour has changed from 5.2.2 where the Background layer was initially ticked. STEPS TO REPRODUCE 1. Open a jpeg file (may also apply to other image files without layers) OBSERVED RESULT The background layer in the layer selector on the right is not ticked EXPECTED RESULT The background layer in the layer selector on the right is should be ticked as it was in 5.2.2 SOFTWARE/OS VERSIONS Windows 10 Pro Krita 5.2.3 (release version) ADDITIONAL INFORMATION This appears to be a change since 5.2.2. Not extensively tested because I have reverted to 5.2.2 for now. Not tested on any other operating systems. I have selected "unspecified" version because 5.2.3 is not listed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489259] Spamming Meta+V causes Plasma to exit with a Wayland protocol error (error 3: no xdg_popup parent surface has been specified)
https://bugs.kde.org/show_bug.cgi?id=489259 Paul Meier changed: What|Removed |Added CC||public.paul.meier+kde@gmail ||.com --- Comment #11 from Paul Meier --- I have the same issue. I first thought it was because of the large amount of history I had set, which was 512 entries. But even after reducing the amount I still have this crash. KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.6-zen1-1-zen (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 489338] arm64: Instruction fcvtas should round 322.5 to 323, but result is 322.
https://bugs.kde.org/show_bug.cgi?id=489338 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr --- Comment #2 from Paul Floyd --- Looks good. One problem with the regtests is that a lot of the numeric tests just use random number generators. That means that they don't cover rounding with ties very well. This also needs doing for the vector version, as noted here case 3: ch = 'a'; irrm = Irrm_NEAREST; break; /* kludge? */ I'll see if I can also knock up a test that covers all 8 combinations of float/double and signed/unsigned scalar. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 489221] Unrecognized instruction: _mm256_cvtps_ph (vcvtps2ph)
https://bugs.kde.org/show_bug.cgi?id=489221 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383010] Add support for AVX-512 instructions
https://bugs.kde.org/show_bug.cgi?id=383010 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 79787] Suppresions files should be auto generated
https://bugs.kde.org/show_bug.cgi?id=79787 Paul Floyd changed: What|Removed |Added Resolution|--- |FIXED CC||pjfl...@wanadoo.fr Status|REPORTED|RESOLVED --- Comment #3 from Paul Floyd --- I think that this was mostly covered by commit 6c9a668a42b0861ca080d0ad0685d52bbfb77480 Author: Julian Seward Date: Mon Jan 10 17:24:47 2005 + Add a new variant for --gen-suppressions: --gen-suppressions=all, which just prints a suppression for all reported errors without asking questions. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3219 There's no separate file option. Printing suppressions can be obtaines=d with -s. The sorting is (I think) based on the order of the suppressoons rather than the count. Personally I feel it's better to make suppression generation not too easy. Lazy developers will just use it to suppress everything and then be able to claim "no Valgrind leaks". -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 226105] Man page does not document --tool
https://bugs.kde.org/show_bug.cgi?id=226105 Paul Floyd changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||pjfl...@wanadoo.fr --- Comment #1 from Paul Floyd --- This has been documented for some time. 09b283bb (Tom Hughes 2011-08-15 08:20:53 + 639) The single most important option. e53a6fba (Donna Robinson 2005-12-03 22:33:29 + 640) 09b283bb (Tom Hughes 2011-08-15 08:20:53 + 641) d3740f94 (Julian Seward 2009-07-15 14:52:52 + 642) d3740f94 (Julian Seward 2009-07-15 14:52:52 + 643) d3740f94 (Julian Seward 2009-07-15 14:52:52 + 644) d5b384f8 (Nicholas Nethercote 2009-08-04 01:16:01 + 645) d3740f94 (Julian Seward 2009-07-15 14:52:52 + 646) d3740f94 (Julian Seward 2009-07-15 14:52:52 + 647) d5b384f8 (Nicholas Nethercote 2009-08-04 01:16:01 + 648) Run the Valgrind tool called toolname, d8b376f4 (Philippe Waroquiers 2014-04-30 20:23:47 + 649) e.g. memcheck, cachegrind, callgrind, helgrind, drd, massif, 40187fcd (Julian Seward 2020-04-17 19:23:26 +0200 650) dhat, lackey, none, exp-bbv, etc. d3740f94 (Julian Seward 2009-07-15 14:52:52 + 651) d3740f94 (Julian Seward 2009-07-15 14:52:52 + 652) d3740f94 (Julian Seward 2009-07-15 14:52:52 + 653) d3740f94 (Julian Seward 2009-07-15 14:52:52 + 654) e53a6fba (Donna Robinson 2005-12-03 22:33:29 + 655) 7a75a9f5 (Nicholas Nethercote 2004-11-30 10:43:45 + 656) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489215] Overview effect doesn't show desktops if there are two rows
https://bugs.kde.org/show_bug.cgi?id=489215 Paul Worrall changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||p.r.worr...@gmail.com --- Comment #1 from Paul Worrall --- Can confirm. If I have two VDs on two rows they appear on the left in overview effect but if I increase to four VDs on two rows they do not appear at all -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 456198] Targets of relative symbolic links are resolved incorrectly in the status bar
https://bugs.kde.org/show_bug.cgi?id=456198 Paul Worrall changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #13 from Paul Worrall --- Seems to be OK now. Operating System: Arch Linux KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 391148] Unhandled AVX instruction vmovq %xmm9,%xmm1
https://bugs.kde.org/show_bug.cgi?id=391148 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417572] vex amd64->IR: unhandled instruction bytes: 0xC5 0x79 0xD6 0xED 0xC5 0xF9 0x51
https://bugs.kde.org/show_bug.cgi?id=417572 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 489025] Cube stops working after first use
https://bugs.kde.org/show_bug.cgi?id=489025 --- Comment #2 from Paul Brown --- Created attachment 170903 --> https://bugs.kde.org/attachment.cgi?id=170903=edit KWin "log" (sort of) I don't know where to find the KWin logs. I read this: https://community.kde.org/KWin/Debugging and I am pretty sure the relevant bit is ``` New LWP 282530] [New LWP 282532] [New LWP 282533] [New LWP 282534] [New LWP 282535] [New LWP 282536] [New LWP 282537] [New LWP 282540] [New LWP 282560] [New LWP 282561] [New LWP 282562] [New LWP 282563] [New LWP 282564] [New LWP 282565] [New LWP 282566] [New LWP 282567] [New LWP 282568] [New LWP 282569] [New LWP 282579] [New LWP 282580] [New LWP 282582] [New LWP 282583] [New LWP 288201] [New LWP 289447] [New LWP 289448] [New LWP 289449] [New LWP 291390] [New LWP 352608] [New LWP 353298] [New LWP 353336] [New LWP 353483] [New LWP 353522] [New LWP 353580] [New LWP 354287] [New LWP 363019] [New LWP 576620] [New LWP 576621] [New LWP 576622] [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". 0x720d17b1c910 in ppoll () from /usr/lib/libc.so.6 Warning: 'set logging on', an alias for the command 'set logging enabled', is deprecated. Use 'set logging enabled on'. [New Thread 0x720c87e006c0 (LWP 582407)] [New Thread 0x720c9ca006c0 (LWP 582408)] [New Thread 0x720c496006c0 (LWP 582409)] [New Thread 0x720c86a006c0 (LWP 582410)] [New Thread 0x720c7a8006c0 (LWP 582559)] [New Thread 0x720c79e006c0 (LWP 582560)] [New Thread 0x720c6de006c0 (LWP 582561)] [New Thread 0x720c6ca006c0 (LWP 582562)] [Thread 0x720c6ca006c0 (LWP 582562) exited] [Thread 0x720c6de006c0 (LWP 582561) exited] [Thread 0x720c79e006c0 (LWP 582560) exited] [Thread 0x720c7a8006c0 (LWP 582559) exited] ``` Is that helpful? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381326] recognize re-convergent fanout before complaining about Uninitialized
https://bugs.kde.org/show_bug.cgi?id=381326 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr --- Comment #12 from Paul Floyd --- I'm loathe to cater to making Undefined Behaviour defined in any way. clang-tidy says it all /home/paulf/x.c:18:44: warning: Branch condition evaluates to a garbage value [clang-analyzer-core.uninitialized.Branch] 18 | for (z=p; n; n--, z++) if (*z) *z=0; | ^~ (browsers are likely to use variable with fonts, the caret is under the *z in the if statement). Who knows what compilers will do with this. Maybe ignore the 'if'. Maybe ignore the initialization. Also how can we be sure that the use of garbage is intentional? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 489088] Valgrind throws unhandled instruction bytes: 0xC5 0x79 0xD6 0xE0 0xC5 0xFA 0x7E 0xDB 0xC5 0xF8
https://bugs.kde.org/show_bug.cgi?id=489088 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489025] New: Cube stops working after first use
https://bugs.kde.org/show_bug.cgi?id=489025 Bug ID: 489025 Summary: Cube stops working after first use Classification: Plasma Product: kwin Version: 6.1.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: paul.br...@kde.org Target Milestone: --- SUMMARY After using the cube effect to switch desktops, it will stop working and you cannot use it again unti you got the System Settings, disable it (and apply changes) and enable it again. STEPS TO REPRODUCE 1. Use the cube (Meta+C) 2. Stop using the cube 3. Try to use the cube again OBSERVED RESULT The second time the cube will not work. EXPECTED RESULT The cube should work every time you try to use it. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.5-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475879] Re-Bind Additional Mouse Buttons menu does not accept bindings to other mouse buttons
https://bugs.kde.org/show_bug.cgi?id=475879 --- Comment #6 from Paul Gideon Dann --- I've made a little progress, with a merge request here: https://invent.kde.org/plasma/kwin/-/merge_requests/5959 This makes it possible to rebind _any_ mouse button by editing the `kcminputrc` config file. This doesn't affect what's possible from the UI, but it is a step. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 468575] Add support for RISC-V
https://bugs.kde.org/show_bug.cgi?id=468575 --- Comment #18 from Paul Floyd --- On a machine that is StarFive JH7100 SoC (2x SiFive U74 at 1.20 GHz) I have a problem with make check. gcc -Winline -Wall -Wshadow -Wno-long-long -g -fno-stack-protector -o compressed compressed.o compressed.o: in function `test_compressed_10': /home/paulf/valgrind-riscv64/none/tests/riscv64/compressed.c:347:(.text+0x56d16): dangerous relocation: The addend isn't allowed for R_RISCV_GOT_HI20 collect2: error: ld returned 1 exit status make[5]: *** [Makefile:741: compressed] Error 1 make[5]: Leaving directory '/home/paulf/valgrind-riscv64/none/tests/riscv64' make[4]: *** [Makefile:899: check-am] Error 2 make[4]: Leaving directory '/home/paulf/valgrind-riscv64/none/tests/riscv64' make[3]: *** [Makefile:2270: check-recursive] Error 1 make[3]: Leaving directory '/home/paulf/valgrind-riscv64/none/tests' make[2]: *** [Makefile:1101: check-recursive] Error 1 make[2]: Leaving directory '/home/paulf/valgrind-riscv64/none' make[1]: *** [Makefile:926: check-recursive] Error 1 make[1]: Leaving directory '/home/paulf/valgrind-riscv64' make: *** [Makefile:1225: check] Error 2 Maybe a GCC problem? gcc --version gcc (Debian 13.2.0-13) 13.2.0 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 488805] Plasma Widget 'Sticky Note' does not lose focus when mouse cursor is clicked outside of the note
https://bugs.kde.org/show_bug.cgi?id=488805 --- Comment #6 from Paul L. --- I can however, confirm that switching to Folder View, the Sticky Note widget behaves as one expects, and clicking anywhere outside of the Sticky Note releases focus from the Sticky Note. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 488805] Plasma Widget 'Sticky Note' does not lose focus when mouse cursor is clicked outside of the note
https://bugs.kde.org/show_bug.cgi?id=488805 --- Comment #5 from Paul L. --- Not sure that I agree with this bug being identified as a duplicate of bug 434090 and indicating this bugs status as RESOLVED. The duplicate cited is over 3-years old, it's status merely CONFIRMED but with no fix/solution given, and reported on Arch Linux that was running earlier versions of Plasma, Frameworks, and Qt. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 478066] Image preview not showing
https://bugs.kde.org/show_bug.cgi?id=478066 Paul Meier changed: What|Removed |Added CC||public.paul.meier+kde@gmail ||.com --- Comment #8 from Paul Meier --- Same, also on EOS and not having this problem. I am missing thumbnails for directories on network shares though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488805] Plasma Widget 'Sticky Note' does not lose focus when mouse cursor is clicked outside of the note
https://bugs.kde.org/show_bug.cgi?id=488805 --- Comment #3 from Paul L. --- Sticky Note behaves as expected in Kubuntu 24.04: KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 QT Version: 5.15.13 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488805] Plasma Widget 'Sticky Note' does not loose focus when mouse cursor is clicked outside of the note
https://bugs.kde.org/show_bug.cgi?id=488805 --- Comment #1 from Paul L. --- I run KDE neon User Edition as a VM in Oracle Virtualbox 7.0, fully updated. I login to the Desktop session with Plasma (X11), as Plasma (Wayland) doesn't load the Desktop. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488805] New: Plasma Widget 'Sticky Note' does not loose focus when mouse cursor is clicked outside of the note
https://bugs.kde.org/show_bug.cgi?id=488805 Bug ID: 488805 Summary: Plasma Widget 'Sticky Note' does not loose focus when mouse cursor is clicked outside of the note Classification: Plasma Product: plasmashell Version: 6.1.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sno...@icloud.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Sticky Note widget doesn't release focus once you begin typing in it. STEPS TO REPRODUCE 1. Add Sticky Note widget to Desktop 2. Start typing in the Sticky Note 3. Click your mouse on the Desktop then start typing 4. Keyboard entries continue in the Sticky Note OBSERVED RESULT Focus isn't released when you click outside of the Sticky Note EXPECTED RESULT Editing of the Sticky Note content ends when you click outside of the Sticky Note (Sticky Note looses focus) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon user Edition 6.0 (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION I've had this behavior confirmed by another user on our Forum (Kubuntu Forums . Net). -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 Paul changed: What|Removed |Added CC||pvt.g...@gmail.com --- Comment #39 from Paul --- For kde6 use: ``` qdbus6 org.kde.kded6 /modules/plasmavault requestImportVault ``` Worked well for me -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 468575] Add support for RISC-V
https://bugs.kde.org/show_bug.cgi?id=468575 --- Comment #17 from Paul Floyd --- On amd64 Linux, one warning that I've opened an issue for on Petr's github. A few other warnings about pointer-to-int-casts. regtest clean. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 488715] support on README_MISSING_SYSCALL_OR_IOCTL for an automatic method?
https://bugs.kde.org/show_bug.cgi?id=488715 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr --- Comment #1 from Paul Floyd --- I wish that this could be automated! The first thing that you can do is use the lax ioctl simhint (--sim-hints=lax-ioctls). If you do that then Valgrind won't complain at all about unhandled ioctls. The second thing that you can do is to make sure that your ioctl has size and direction (or no direction and a size of 0). You can do that using the _IOR _IOW and _IORW macros in asm-generic/ioctl.h. That only covers the call to the ioctl. Then there is the state of the memory that the ioctl refers to. The ioctl encoding gives only a basic indication of what kinds of memory accesses to expect. Often there will be mutilple levels of indirection, numerous subcodes etc. Without all the details Memcheck won't know which memory ranges become initialized by ioctls that write to user memory. That could result in false positive "Conditional jump or move" errors. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 460951] infinite loop in ARM-64 version of instrumentation with ouptput VG_ calls at superblock and instruction level
https://bugs.kde.org/show_bug.cgi?id=460951 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 468575] Add support for RISC-V
https://bugs.kde.org/show_bug.cgi?id=468575 --- Comment #16 from Paul Floyd --- I think it's a regression that I added. Should be fixed. I'll check again when Petr rebases next, and I'll also give Linux amd64 a go and see if I can build and run regtest on riscv. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487832] non-removable storage devices get recognized as removable media
https://bugs.kde.org/show_bug.cgi?id=487832 --- Comment #5 from Paul --- (In reply to g1.jasger from comment #4) > OK- thanks, I'll raise an issue on arch then. This was a regression introduced with the 6.9.* kernel. It has been fixed in 6.10-rc4 "Fix a bug where the SCSI Removable Media Bit (RMB) was incorrectly set for hot-plug capable (and eSATA) ports." https://lore.kernel.org/all/171856227442.1143.13572753599648338171.pr-tracker-...@kernel.org/T/ On openSUSE TW this fix has been backported to the 6.9 kernel and should be in 6.9.6 @g1.jasger you may want to point the arch folk to that commit. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 468575] Add support for RISC-V
https://bugs.kde.org/show_bug.cgi?id=468575 --- Comment #14 from Paul Floyd --- I built and ran regtest on my github clone of https://github.com/petrpavlu/valgrind-riscv64 on FreeBSD amd64. There were a couple of unexpected failures in memcheck/tests/freebsd (one of the scalars and eventfd2). I'll look into them and also try some more platforms. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 487439] SIGILL in JDK11, JDK17
https://bugs.kde.org/show_bug.cgi?id=487439 --- Comment #18 from Paul Floyd --- commit c19d19d34a6dadaf4a9d590f516f813e9cbacdd0 Author: Paul Floyd Date: Sun Jun 16 09:25:51 2024 +0200 Bug 487439 - SIGILL in JDK11, JDK17 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488558] System monitor applets are empty with Qt 6.8
https://bugs.kde.org/show_bug.cgi?id=488558 Paul Worrall changed: What|Removed |Added CC||ferlax...@gmail.com --- Comment #2 from Paul Worrall --- *** Bug 488568 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 488568] CPU and Memory load monitors now showing up in both widgets and the application
https://bugs.kde.org/show_bug.cgi?id=488568 Paul Worrall changed: What|Removed |Added CC||p.r.worr...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Paul Worrall --- *** This bug has been marked as a duplicate of bug 488558 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488558] System monitor applets are empty with Qt 6.8
https://bugs.kde.org/show_bug.cgi?id=488558 Paul Worrall changed: What|Removed |Added CC||p.r.worr...@gmail.com --- Comment #1 from Paul Worrall --- In the System Monitor app the sensors with text output are working OK, it's the graphs that aren't working. Operating System: Arch Linux KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.3.0 Qt Version: 6.8.0 KDE Gear 24.05.1 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 488514] Android OS (Termux) `valgrind /bin/ls` gives `Unrecognised instruction at address X`
https://bugs.kde.org/show_bug.cgi?id=488514 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 488514] Android OS (Termux) `valgrind /bin/ls` gives `Unrecognised instruction at address X`
https://bugs.kde.org/show_bug.cgi?id=488514 --- Comment #3 from Paul Floyd --- As a workaround, if you target something like ARM8.2 (-march=armv8.2 maybe) then does it work? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 488514] Android OS (Termux) `valgrind /bin/ls` gives `Unrecognised instruction at address X`
https://bugs.kde.org/show_bug.cgi?id=488514 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr --- Comment #2 from Paul Floyd --- This looks like ldaprb w9, [x8] which isn't supported (arm64 doesn't have much support of ARM 8.3) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488456] New: The calendar jumps three months/years if the "Previous" or "Next" buttons are clicked
https://bugs.kde.org/show_bug.cgi?id=488456 Bug ID: 488456 Summary: The calendar jumps three months/years if the "Previous" or "Next" buttons are clicked Classification: Plasma Product: plasmashell Version: 6.0.5 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: public.paul.meier+...@gmail.com Target Milestone: 1.0 Created attachment 170474 --> https://bugs.kde.org/attachment.cgi?id=170474=edit Recording showing the bug SUMMARY Opening the calendar and clicking the "Previous" or "Next" button jumps three months or years, depending on the view. So clicking "Previous month" on current date jumps back to March instead of May. Clicking "Next month" jumps to September instead of July. Same with years in the year or month view. From current year it jumps to 2021 or 2027, depending on which button was pressed. STEPS TO REPRODUCE 1. Click on the digital clock to open the calendar 2. Click on the "Previous" or "Next" button in the day, week or year view OBSERVED RESULT The calendar jumps three months/years instead of one EXPECTED RESULT The calendar should show the previous month/year or next month/year SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-zen1-1-zen (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Screen recording showing this bug is attached -- 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 #19 from Paul Floyd --- (In reply to Olly Betts from comment #18) > I'm using valgrind via a testsuite harness and valgrind's output unhelpfully > gets interleaved with other output so it was much much easier to just cut > and paste the three lines that actually seemed relevant. I'll try to get > the full clean output for you, but there was just the banner lines before > that and after that was into functions in the library code being tested. I'd like to see if the call to memmove is getting inlined. We do de-inlining for error reports but not at runtime. That means that if memmove is inlined memcheck won't redirect it. Instead it will redirect __memmove_chk > $ nm -D /usr/lib/x86_64-linux-gnu/libc.so.6|grep 00119f80 > 00119f80 i __memcpy_chk@@GLIBC_2.3.4 > $ nm -D /usr/lib/x86_64-linux-gnu/libc.so.6|grep 0011a090 > 0011a090 i __memmove_chk@@GLIBC_2.3.4 That's not what I was expecting. If the memmove was inlined and __memcpy_chk and __memmove_chk are aliases then Memcheck will only use one of them (__memcpy_chk from the errors you got). If that's the case then your problem was probably fixed by Mark in October 2023: 39c447e4a9 (Bart Van Assche 2013-11-24 17:48:13 + 1716) /* memcpy_chk */ 39c447e4a9 (Bart Van Assche 2013-11-24 17:48:13 + 1717) 53e101f562 (Mark Wielaard 2023-10-30 23:30:06 +0100 1718) /* See https://bugs.kde.org/show_bug.cgi?id=402833 53e101f562 (Mark Wielaard 2023-10-30 23:30:06 +0100 1719)why we disable the overlap check on x86_64. */ 53e101f562 (Mark Wielaard 2023-10-30 23:30:06 +0100 1720) #if defined(VGP_amd64_linux) 53e101f562 (Mark Wielaard 2023-10-30 23:30:06 +0100 1721) #define CHECK_OVERLAP 0 53e101f562 (Mark Wielaard 2023-10-30 23:30:06 +0100 1722) #else 53e101f562 (Mark Wielaard 2023-10-30 23:30:06 +0100 1723) #define CHECK_OVERLAP 1 53e101f562 (Mark Wielaard 2023-10-30 23:30:06 +0100 1724) #endif Try using Valgrind 3.23 and see if the problem goes away. -- 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 #17 from Paul Floyd --- This is getting frustrating. I keep asking questions and you keep (incorrectly) second guessing something else. I'm still waiting to see the exact error. I don't want you to second guess that it means just the top two elements in the callstack. Full Memcheck errors are delimited by lines with just "==PID==" where PID is a number representing the process ID. It's everything between those delimiting lines that I want to see. Is that clear? Secondly I gave an example using "nm -D". You interpreted that as "nm" without "-D". Then you copied some output from Fedora whilst you are using Debian. I have an idea as to what is happening but I'd really prefer not to have to make guesses. -- 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 #15 from Paul Floyd --- Also in your libc, is there more than one function using the same address as __memmove_chk? (And specifically, is __memcpy_chk the same as __memmove_chk). First do something like nm -D /lib/libc.so.7 | grep __memmove_chk Then search for the hex value in column 1. That would be something like paulf> nm -D /lib/libc.so.7 | grep 0017bbc0 0017bbc0 T __mallctl 0017bbc0 W mallctl (different libc and different symbol, just for illustration). -- 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 #14 from Paul Floyd --- (In reply to Olly Betts from comment #13) > ==4137856== Source and destination overlap in memcpy_chk(0x1ffeffb000, > 0x1ffeffb010, 10224) > ==4137856==at 0x484BE22: __memcpy_chk (in > /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) > ==4137856==by 0x495A87B: memmove (string_fortified.h:36) Try again. What exactly is the error message? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487832] non-removable storage devices get recognized as removable media
https://bugs.kde.org/show_bug.cgi?id=487832 Paul changed: What|Removed |Added CC||pip@gmx.com -- 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 #12 from Paul Floyd --- Adding a suppression is probably not the answer. Running under memcheck there shouldn't even be a call to __memcpy_chk from memmove. The question is why Valgrind isn't rediecting the call to memmove? On Linux the memmove may have been replaced by a call to memcpy if the compiler deems it safe to do so. That does cause us problems as our checks are more conservative. What exactly is the error message? -- You are receiving this mail because: You are watching all bug changes.
