[kpat] [Bug 493630] New: KPat consumes a lot of cpu ressources, after a few parties (of spider) where played
https://bugs.kde.org/show_bug.cgi?id=493630 Bug ID: 493630 Summary: KPat consumes a lot of cpu ressources, after a few parties (of spider) where played Classification: Applications Product: kpat Version: 24.05.2 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: co...@kde.org Reporter: sno...@ilnet.ch CC: kde-games-b...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. open kPatience 2. play a few games (mabe 4 or 5) OBSERVED RESULT After every game, X consumes more CPU. You could close the game and open it again, the the consuming starts again, like there is someting in the background, that will not be given free (it seems not to be the memory). Only reboot helps. EXPECTED RESULT X consumes not more CPU. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.4.0-150600.23.22-default (64-bit) KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION 2 × 13th Gen Intel® Core™ i7-13850HX, 8GB memory I could give more informations, if I now, what you need to analyze it. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 493383] Game shows "no winning" while winning is still possible (like bug 378263)
https://bugs.kde.org/show_bug.cgi?id=493383 --- Comment #10 from Markus Grob --- Created attachment 174064 --> https://bugs.kde.org/attachment.cgi?id=174064&action=edit saveGame Spider win Now I got now, where winning is possible after no win was shown. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 493383] Game shows "no winning" while winning is still possible (like bug 378263)
https://bugs.kde.org/show_bug.cgi?id=493383 --- Comment #9 from Markus Grob --- Created attachment 174063 --> https://bugs.kde.org/attachment.cgi?id=174063&action=edit saveGame Spider noWin -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 493383] Game shows "no winning" while winning is still possible (like bug 378263)
https://bugs.kde.org/show_bug.cgi?id=493383 --- Comment #8 from Markus Grob --- The attached game is maybe not winnable, but it shows the change from "no win" back to "not sure". Because of the screenshots, isn't it possible to set the cards into the arrays in the memory like they are seen on the screen to debug the game? -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 493383] Game shows "no winning" while winning is still possible (like bug 378263)
https://bugs.kde.org/show_bug.cgi?id=493383 --- Comment #7 from Markus Grob --- Created attachment 174003 --> https://bugs.kde.org/attachment.cgi?id=174003&action=edit saveGame Spider notSure -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 493383] Game shows "no winning" while winning is still possible (like bug 378263)
https://bugs.kde.org/show_bug.cgi?id=493383 --- Comment #6 from Markus Grob --- Created attachment 174002 --> https://bugs.kde.org/attachment.cgi?id=174002&action=edit saveGame Spider noWin -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 493383] Game shows "no winning" while winning is still possible (like bug 378263)
https://bugs.kde.org/show_bug.cgi?id=493383 --- Comment #5 from Markus Grob --- I add now a saveGame which shows "no win" and after a "not sure". I think, it doesn't counts possibilities with shuffle "good" rows into shuffled rows to empty a line. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 493383] Game shows "no winning" while winning is still possible (like bug 378263)
https://bugs.kde.org/show_bug.cgi?id=493383 --- Comment #3 from Markus Grob --- Created attachment 173976 --> https://bugs.kde.org/attachment.cgi?id=173976&action=edit Screenshot winning again -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 493383] Game shows "no winning" while winning is still possible (like bug 378263)
https://bugs.kde.org/show_bug.cgi?id=493383 --- Comment #2 from Markus Grob --- Created attachment 173975 --> https://bugs.kde.org/attachment.cgi?id=173975&action=edit Screenshot no winning game shows no winning -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 493383] Game shows "no winning" while winning is still possible (like bug 378263)
https://bugs.kde.org/show_bug.cgi?id=493383 --- Comment #1 from Markus Grob --- Tried to add screenshots (jpeg), but get every time an error of a malformatted document with data truncate. Sincerely Markus -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 493383] New: Game shows "no winning" while winning is still possible (like bug 378263)
https://bugs.kde.org/show_bug.cgi?id=493383 Bug ID: 493383 Summary: Game shows "no winning" while winning is still possible (like bug 378263) Classification: Applications Product: kpat Version: 24.05.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: solver Assignee: co...@kde.org Reporter: sno...@ilnet.ch CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY Programm clains no winning possibility, but in the next move, win is possible again STEPS TO REPRODUCE 1. use game 582007501 2. play it until the same situation as in the screenshots OBSERVED RESULT Winning seems to be not possible EXPECTED RESULT show only "no possibility" if there is no winning possible SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: 6.4.0-150600.23.17-default (64-bit) KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 491890] Button `Expand results` doesn't expand results
https://bugs.kde.org/show_bug.cgi?id=491890 Markus Pister changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #2 from Markus Pister --- Indeed, my search had matches in > 300 files, actually. Thanks for explaining. Just rechecked with a different search and there, the button works as expected. I agree that probably nobody checks soo many matches in the result list. My intention was to open the list and do a very fast scroll over if the matches look reasonable to me. >From my point of view, no need to relax that limit. I was just surprised cause I was not aware of the limit. >From that perspective, the bug report is invalid. I switch the status to "not a bug". Thanks again for the fast reply. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 491890] New: Button `Expand results` doesn't expand results
https://bugs.kde.org/show_bug.cgi?id=491890 Bug ID: 491890 Summary: Button `Expand results` doesn't expand results Classification: Applications Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: kwrite-bugs-n...@kde.org Reporter: i...@markus-pister.de Target Milestone: --- SUMMARY I was used to use the button `Expand results` in the search plugin to both collapse and expand the result list. I just noticed that the button now only collapses the results, no expansion happens anymore when again hitting the button. Found in branch 'master' (current HEAD: commit 41e0a495). STEPS TO REPRODUCE 1. Perform some search with the search plugin that has results 2. Hit button `Expand results` multiple times OBSERVED RESULT Results are collapsed (if state was expanded before), but no expansion happens anymore. EXPECTED RESULT Hitting the button previously toggled expanded and collapsed state of the result list. Would be nice to have that behavior back. SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 488688] No warning, if new game will be started in an active game
https://bugs.kde.org/show_bug.cgi?id=488688 --- Comment #3 from Markus Grob --- I updated now to Leap 15.6 which has kpat 23.08.5, but still gets the "error". I will try now with your link and report later. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 488688] No warning, if new game will be started in an active game
https://bugs.kde.org/show_bug.cgi?id=488688 Markus Grob changed: What|Removed |Added Version|21.12.3 |23.08.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488627] plasma desktop background disturbed after reconnect displays
https://bugs.kde.org/show_bug.cgi?id=488627 Markus changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Markus --- Sorry, I was running 6.0.90 at that point. Running 6.1.1 for a few days now. Didnt happen again so far, so you seem to be right. ;) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469265] Wrong window moves while draging from pager
https://bugs.kde.org/show_bug.cgi?id=469265 Markus changed: What|Removed |Added CC||m4rkus...@web.de --- Comment #1 from Markus --- Also seeing this with plasma 6.1 on wayland. Never noticed it with xorg. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 488688] No warning, if new game will be started in an active game
https://bugs.kde.org/show_bug.cgi?id=488688 Markus Grob changed: What|Removed |Added CC||sno...@ilnet.ch -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 488688] New: No warning, if new game will be started in an active game
https://bugs.kde.org/show_bug.cgi?id=488688 Bug ID: 488688 Summary: No warning, if new game will be started in an active game Classification: Applications Product: kpat Version: 21.12.3 Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: co...@kde.org Reporter: sno...@ilnet.ch CC: kde-games-b...@kde.org Target Milestone: --- Created attachment 170609 --> https://bugs.kde.org/attachment.cgi?id=170609&action=edit Screenshot *** 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 STEPS TO REPRODUCE 1. Start a game 2. Press "new cards" instead of "get a step back", because it is the next button OBSERVED RESULT No warning and no possibility to go back to the old game EXPECTED RESULT warning (do you really want...) or back button is possible SOFTWARE/OS VERSIONS Linux/KDE Plasma ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488627] New: plasma desktop background disturbed after reconnect displays
https://bugs.kde.org/show_bug.cgi?id=488627 Bug ID: 488627 Summary: plasma desktop background disturbed after reconnect displays Classification: Plasma Product: plasmashell Version: 6.1.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: m4rkus...@web.de CC: notm...@gmail.com Target Milestone: 1.0 Created attachment 170572 --> https://bugs.kde.org/attachment.cgi?id=170572&action=edit Screenshot of the bug SUMMARY After switching off and on of the displays the background not scaled correctly, but huge black borders are visible. Before (plasma 5.27.11) the problem already existed, but the black border was actually currupted, in a way that everything that was drawn there from some window remained in that area across desktops. STEPS TO REPRODUCE 1. Use wayland with a fhd display @100% and a 4k display @150%. 2. Switch both displays off and on again. OBSERVED RESULT Background of the 4k screen has a huge black border on bottom and right. (See attached screenshot.) Changing the background picture itself does not recover it. But changing between e.g. picture and folder background solves it for the moment. EXPECTED RESULT Background is displayed as before, correctly over the full screen area. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 486015] "The name org.kde.kwalletd6 was not provided by any .service files")
https://bugs.kde.org/show_bug.cgi?id=486015 Markus changed: What|Removed |Added Alias||testbuero57 -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 486015] New: "The name org.kde.kwalletd6 was not provided by any .service files")
https://bugs.kde.org/show_bug.cgi?id=486015
Bug ID: 486015
Summary: "The name org.kde.kwalletd6 was not provided by any
.service files")
Classification: Applications
Product: kwalletmanager
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: va...@kde.org
Reporter: reichelt.mar...@icloud.com
Target Milestone: ---
Created attachment 168834
--> https://bugs.kde.org/attachment.cgi?id=168834&action=edit
Screenshot
Guten Tag,
Kwallet startet nicht, folgende Meldung erscheint:
Couldn't start kwalletd:
QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name
org.kde.kwalletd6 was not provided by any .service files")
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Couldn't start kwalletd:
QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name
org.kde.kwalletd6 was not provided by any .service files")
Beste Grüße
Markus
***
OS: openSUSE Leap 15.5 x86_64
Host: MS-7A70 1.0
Kernel: 5.14.21-150500.55.52-default
Uptime: 16 mins
Packages: 2501 (rpm), 10 (flatpak), 7 (snap)
Shell: bash 4.4.23
Resolution: 1920x1080
DE: Plasma 5.27.9
WM: KWin
WM Theme: ROUNDED
Theme: [Plasma], Breeze [GTK2/3]
Icons: [Plasma], breeze [GTK2/3]
Terminal: konsole
CPU: Intel i5-7500 (4) @ 3.800GHz
GPU: AMD ATI FirePro W4100
Memory: 2425MiB / 32058MiB
--
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 Markus changed: What|Removed |Added CC||m4rkus...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 473700] Support passkeys with kwalletmanager
https://bugs.kde.org/show_bug.cgi?id=473700 Markus changed: What|Removed |Added CC||m4rkus...@web.de -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 281975] Memcheck crashes on the Cortex A9 Armv7 processor executing unsupported VMD instructions
https://bugs.kde.org/show_bug.cgi?id=281975 Markus Gothe changed: What|Removed |Added Attachment #167661|0 |1 is obsolete|| --- Comment #8 from Markus Gothe --- Created attachment 167713 --> https://bugs.kde.org/attachment.cgi?id=167713&action=edit Updated attachement Updated attachment so the end-user can override configure variables to disable the ARM NEON and VFP checks, for asymmetrical systems. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 281975] Memcheck crashes on the Cortex A9 Armv7 processor executing unsupported VMD instructions
https://bugs.kde.org/show_bug.cgi?id=281975
--- Comment #7 from Markus Gothe ---
Comment on attachment 167661
--> https://bugs.kde.org/attachment.cgi?id=167661
Support for ARMv7 w/o NEON and VFP
>From 8fbd691e7f8a79983b8dbec1ee89cdf32d6b3c41 Mon Sep 17 00:00:00 2001
From: Dave Lerner
Date: Fri, 22 Mar 2024 17:34:15 +0100
Subject: [PATCH] Support ARMv7 w/o NEON and VFP
Don't try to cleanup the fpscr register that is not available and has
no opcode support for armv7 processors that are without
the SIMD and VFP extensions, since the fmxr/fmrx instructions will throw
a SIGILL, illegal opcode, killing valgrind before it executes the
first instruction of the application under test.
Make it possible to disable NEON and VFP auto-detection
on ARMv7. There are asymmetrical devices where one or more
cores doesn't support the NEON and VFP extensions. These
devices needs a special workaround.
Signed-off-by: Dave Lerner
Co-authored-by: Markus Gothe
---
configure.ac | 9 +
coregrind/m_dispatch/dispatch-arm-linux.S | 11 +++
coregrind/m_machine.c | 13 ++---
coregrind/pub_core_machine.h | 1 +
4 files changed, 31 insertions(+), 3 deletions(-)
diff --git a/configure.ac b/configure.ac
index 8279683ac..0d0a35089 100755
--- a/configure.ac
+++ b/configure.ac
@@ -3789,6 +3789,15 @@ CFLAGS="$save_CFLAGS"
AM_CONDITIONAL(BUILD_ARMV82_DOTPROD_TESTS, test
x$ac_have_armv82_dotprod_feature = xyes)
+# Enable VFP and NEON auto-detection on ARM
+AC_CACHE_CHECK([for VFP auto-detection on ARM], vg_cv_arm_vfp_autodetection,
[vg_cv_arm_vfp_autodetection=yes])
+AC_CACHE_CHECK([for NEON auto-detection on ARM], vg_cv_arm_neon_autodetection,
[vg_cv_arm_neon_autodetection=yes])
+if test "x${vg_cv_arm_vfp_autodetection}" = "xyes"; then
+ AC_DEFINE(ENABLE_ARM_VFP, 1, [Define to 1 if auto-detection of ARM VFP
capabilities should be used.])
+fi
+if test "x${vg_cv_arm_neon_autodetection}" = "xyes"; then
+ AC_DEFINE(ENABLE_ARM_NEON, 1, [Define to 1 if auto-detection of ARM NEON
capabilities should be used.])
+fi
# XXX JRS 2010 Oct 13: what is this for? For sure, we don't need this
# when building the tool executables. I think we should get rid of it.
diff --git a/coregrind/m_dispatch/dispatch-arm-linux.S
b/coregrind/m_dispatch/dispatch-arm-linux.S
index 40629017c..284df0513 100644
--- a/coregrind/m_dispatch/dispatch-arm-linux.S
+++ b/coregrind/m_dispatch/dispatch-arm-linux.S
@@ -65,10 +65,16 @@ VG_(disp_run_translations):
order to keep the stack 8-aligned. */
push {r0, r3, r4, r5, r6, r7, r8, r9, r10, r11, r12, lr}
+ldr r4, =VG_(machine_arm_has_fpscr)
+ldr r4, [r4]
+cmp r4, #0
+beq no_fpscr_setup
+
/* set FPSCR to vex-required default value */
mov r4, #0
fmxr fpscr, r4
+no_fpscr_setup:
/* Set up the guest state pointer */
mov r8, r1
@@ -93,6 +99,11 @@ postamble:
/* We're leaving. Check that nobody messed with
FPSCR in ways we don't expect. */
+ldr r4, =VG_(machine_arm_has_fpscr)
+ldr r4, [r4]
+cmp r4, #0
+beq remove_frame
+
fmrx r4, fpscr
bic r4, #0xF800 /* mask out NZCV and QC */
bic r4, #0x009F /* mask out IDC,IXC,UFC,OFC,DZC,IOC */
diff --git a/coregrind/m_machine.c b/coregrind/m_machine.c
index a4c2218bf..8fc82eb81 100644
--- a/coregrind/m_machine.c
+++ b/coregrind/m_machine.c
@@ -472,6 +472,7 @@ ULong VG_(machine_ppc64_has_VMX) = 0;
#endif
#if defined(VGA_arm)
Int VG_(machine_arm_archlevel) = 4;
+UInt VG_(machine_arm_has_fpscr) = 0;
#endif
@@ -1673,7 +1674,7 @@ Bool VG_(machine_get_hwcaps)( void )
tmp_sigfpe_act.sa_flags |= VKI_SA_NODEFER;
tmp_sigfpe_act.ksa_handler = handler_unsup_insn;
VG_(sigaction)(VKI_SIGFPE, &tmp_sigfpe_act, NULL);
-
+#ifdef ENABLE_ARM_VFP
/* VFP insns */
have_VFP = True;
if (VG_MINIMAL_SETJMP(env_unsup_insn)) {
@@ -1681,11 +1682,14 @@ Bool VG_(machine_get_hwcaps)( void )
} else {
__asm__ __volatile__(".word 0xEEB02B42"); /* VMOV.F64 d2, d2 */
}
+#else
+ have_VFP = False;
+#endif
/* There are several generation of VFP extension but they differs very
little so for now we will not distinguish them. */
have_VFP2 = have_VFP;
have_VFP3 = have_VFP;
-
+#ifdef ENABLE_ARM_NEON
/* NEON insns */
have_NEON = True;
if (VG_MINIMAL_SETJMP(env_unsup_insn)) {
@@ -1693,7 +1697,9 @@ Bool VG_(machine_get_hwcaps)( void )
} else {
__asm__ __volatile__(".word 0xF2244154"); /* VMOV q2, q2 */
}
-
+#else
+ have_NEON = False;
+#endif
/* ARM architecture level */
archlevel = 5; /* v5 will be base level */
if (archlevel < 7) {
@@ -1737,6 +1743,7 @@ Bool VG_(machine_get_hwcaps)( void )
[valgrind] [Bug 281975] Memcheck crashes on the Cortex A9 Armv7 processor executing unsupported VMD instructions
https://bugs.kde.org/show_bug.cgi?id=281975 --- Comment #6 from Markus Gothe --- (In reply to Paul Floyd from comment #4) > Wouldn't it be better to do this check at compile time? The reason why we need run-time detection is that openssl and other code uses run-time detection of VFP/NEON extensions. I've an AArch64 setup which runs AArch64 in kernel-space and EABI5 / AArch32 in user-space. Two different toolchains, the SoC supports both VFP and NEON and this leads to unwanted consequences. Hence we will need to follow the rest of the code base to guarantee the code will work as expected. BR, Markus -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 281975] Memcheck crashes on the Cortex A9 Armv7 processor executing unsupported VMD instructions
https://bugs.kde.org/show_bug.cgi?id=281975 --- Comment #5 from Markus Gothe --- (In reply to Paul Floyd from comment #4) > Wouldn't it be better to do this check at compile time? Interesting idea... I guess it could be done, but since there already exist dynamic detection of both VFP and NEON capabilities we can just piggyback on them and make the code less intrusive. I have seen some asymmetrical systems with multiple cores, where only one core has the NEON extension. I'll give it some testing. BR, Markus -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 281975] Memcheck crashes on the Cortex A9 Armv7 processor executing unsupported VMD instructions
https://bugs.kde.org/show_bug.cgi?id=281975 Markus Gothe changed: What|Removed |Added Ever confirmed|0 |1 CC||markus.go...@genexis.eu Assignee|jsew...@acm.org |markus.go...@genexis.eu Status|REPORTED|CONFIRMED --- Comment #3 from Markus Gothe --- Created attachment 167661 --> https://bugs.kde.org/attachment.cgi?id=167661&action=edit Support for ARMv7 w/o NEON and VFP Hi, I've cleaned up the patch a bit so it applies cleanly on latest Valgrind. I've also removed the dynamic detection of the FPSCR since it might create issues on cores with functional capabilities, instead we check if NEON or VFP is supported. BR, Markus -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 474129] Restore previously selected side bar when closing git history view
https://bugs.kde.org/show_bug.cgi?id=474129 Markus Pister changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #4 from Markus Pister --- Just checked the implemented behavior on a fresh master build. Works perfectly. Thanks for implementing this. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469232] Ability to bind mouse click types (left-click, right-click, etc) to drawing tablet pen buttons
https://bugs.kde.org/show_bug.cgi?id=469232 Felix Markus changed: What|Removed |Added CC||fe...@markus-bw.de --- Comment #1 from Felix Markus --- Hey there! Do I understand correctly that https://invent.kde.org/plasma/kwin/-/merge_requests/3055 implements the "behind the scenes" work for this and that now "only" a way to use this, like https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/920 implements for remapping mouse buttons is needed? (For clarity, I don't really have the skills/knowledge to actually help here. Just curious, and would be very happy to be able to use my stylus buttons the way they are most useful outside of dedicated painting apps :D ) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478575] When opening the Setting / Setting Dialog, then main window crashes
https://bugs.kde.org/show_bug.cgi?id=478575 --- Comment #3 from Markus Hainz --- Sorry for the delay, 8.2 isn't available via the Ubuntu softwarecenter, I had to install it by downloading manually from the digikam website. In 8.2 the issue is not reproducible, and in this version the German language adaptation is also complete; in version 8.1 from the Ubuntu software center the localization is incomplete. Thanks for your quick help! Best Regards Markus Hainz -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478575] When opening the Setting / Setting Dialog, then main window crashes
https://bugs.kde.org/show_bug.cgi?id=478575 --- Comment #1 from Markus Hainz --- Created attachment 164208 --> https://bugs.kde.org/attachment.cgi?id=164208&action=edit Screenshot of the behaviour -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478575] New: When opening the Setting / Setting Dialog, then main window crashes
https://bugs.kde.org/show_bug.cgi?id=478575 Bug ID: 478575 Summary: When opening the Setting / Setting Dialog, then main window crashes Classification: Applications Product: digikam Version: 8.1.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: Setup-Misc Assignee: digikam-bugs-n...@kde.org Reporter: mar...@familie-hainz.de Target Milestone: --- After opening the 'Settings' - Dialog, the programs window content crashes, and the titlebar disappears, too. The menubar keeps visible and functional. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476375] Powerdevil fails to start with ddcutil-2.0.0, spikes cpu usage to max every few seconds
https://bugs.kde.org/show_bug.cgi?id=476375
Markus changed:
What|Removed |Added
CC||m...@markusweimar.de
--- Comment #39 from Markus ---
For me, powerdevil only crashes when an Apple Cinema Display (model A1267) is
connected. Brightness control of this display requires acdcontrol
(https://github.com/jenrik/acdcontrol).
Linux/KDE Plasma: Arch Linux (current)
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.112.0
Qt Version: 5.15.11
This line is printed in gdb when running /usr/lib/org_kde_powerdevil:
org.kde.powerdevil: org.kde.powerdevil.backlighthelper.brightness failed
# gdb.txt
Starting program: /usr/lib/org_kde_powerdevil
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7f2794c276c0 (LWP 23350)]
[New Thread 0x7f2786c0 (LWP 23351)]
[New Thread 0x7f278f7fe6c0 (LWP 23354)]
[New Thread 0x7f278effd6c0 (LWP 23355)]
[New Thread 0x7f278e7fc6c0 (LWP 23356)]
[Detaching after vfork from child process 23376]
[Detaching after vfork from child process 23378]
[Detaching after vfork from child process 23380]
[Detaching after vfork from child process 23382]
[Thread 0x7f2794c276c0 (LWP 23350) exited]
Thread 1 "org_kde_powerde" received signal SIGABRT, Aborted.
__pthread_kill_implementation (threadid=, signo=signo@entry=6,
no_tid=no_tid@entry=0) at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
Thread 6 (Thread 0x7f278e7fc6c0 (LWP 23356) "gdbus"):
#0 0x7f279a720f6f in __GI___poll (fds=0x7f2778000b90, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
sc_ret = -516
sc_cancel_oldtype = 0
#1 0x7f279976c276 in () at /usr/lib/libglib-2.0.so.0
#2 0x7f279970eb97 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
#3 0x7f279563414c in () at /usr/lib/libgio-2.0.so.0
#4 0x7f279973f9f5 in () at /usr/lib/libglib-2.0.so.0
#5 0x7f279a6aa9eb in start_thread (arg=) at
pthread_create.c:444
ret =
pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139808071132944,
-7240220390079944981, -232, 11, 140730525680576, 139807862800384,
7334830064921388779, 7334856633901295339}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
#6 0x7f279a72e7cc in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Thread 5 (Thread 0x7f278effd6c0 (LWP 23355) "gmain"):
#0 0x7f279a720f6f in __GI___poll (fds=0x5615360b3ec0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
sc_ret = -516
sc_cancel_oldtype = 0
#1 0x7f279976c276 in () at /usr/lib/libglib-2.0.so.0
#2 0x7f279970c162 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3 0x7f279970c1b2 in () at /usr/lib/libglib-2.0.so.0
#4 0x7f279973f9f5 in () at /usr/lib/libglib-2.0.so.0
#5 0x7f279a6aa9eb in start_thread (arg=) at
pthread_create.c:444
ret =
pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139808071132944,
-7240220390079944981, -232, 2, 140730525680688, 139807871193088,
7334828969167857387, 7334856633901295339}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
#6 0x7f279a72e7cc in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Thread 4 (Thread 0x7f278f7fe6c0 (LWP 23354) "pool-spawner"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x7f27997672b7 in g_cond_wait () at /usr/lib/libglib-2.0.so.0
#2 0x7f27996d91b4 in () at /usr/lib/libglib-2.0.so.0
#3 0x7f2799741a7e in () at /usr/lib/libglib-2.0.so.0
#4 0x7f279973f9f5 in () at /usr/lib/libglib-2.0.so.0
#5 0x7f279a6aa9eb in start_thread (arg=) at
pthread_create.c:444
ret =
pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139808071132944,
-7240220390079944981, -232, 2, 140730525680896, 139807879585792,
7334832267165869803, 7334856633901295339}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
#6 0x7f279a72e7cc in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Thread 3 (Thread 0x7f2786c0 (LWP 23351) "QXcbEventQueue"):
#0 0x7f279a720f6f in __GI___poll (fds=fds@entry=0x7f278fffebc8,
nfds=nfds@entry=1, timeout=timeout@entry=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
sc_ret = -516
sc_cancel_oldtype = 0
#1 0x7f279aa9f20b in poll (__timeout=-1, __nfds=1, __fds=0x7f278fffebc8)
at /usr/include/bits/poll2.h:39
ret =
fd = {fd = 6, events = 1, reven
[digikam] [Bug 477707] Face detection stays on 0% and cannot be canceled
https://bugs.kde.org/show_bug.cgi?id=477707 --- Comment #3 from Markus --- Thanks, with 8.2.0 it seems to work: the progress bar is now around 3% and the cancel button works as well. Great, thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477707] New: Face detection stays on 0% and cannot be canceled
https://bugs.kde.org/show_bug.cgi?id=477707 Bug ID: 477707 Summary: Face detection stays on 0% and cannot be canceled Classification: Applications Product: digikam Version: 8.1.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Faces-Detection Assignee: digikam-bugs-n...@kde.org Reporter: markusd...@web.de Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. start face detection 2. wait as long as you want 3. press the cancel button right of the progress bar OBSERVED RESULT There is no progress visible, the bar remains on 0%. When pressing the cancel button, nothing happens: the task won't be canceled, I have to kill the digikam process hard to continue work. EXPECTED RESULT There should be some progress visible, the cancel button should really cancel the action SOFTWARE/OS VERSIONS Windows: 11 Pro KDE Frameworks Version: 5.106.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 473733] Dolphin unable to copy or move files "The file or folder Message recipient disconnected from message bus without replying does not exist."
https://bugs.kde.org/show_bug.cgi?id=473733 --- Comment #6 from Markus Schmits --- Forgot to print the version: dolphin --version dolphin 23.08.1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 473733] Dolphin unable to copy or move files "The file or folder Message recipient disconnected from message bus without replying does not exist."
https://bugs.kde.org/show_bug.cgi?id=473733
--- Comment #5 from Markus Schmits ---
$ gdb dolphin
GNU gdb (GDB) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from dolphin...
(No debugging symbols found in dolphin)
(gdb) run
Starting program: /usr/x86_64-pc-linux-gnu/bin/dolphin
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/usr/x86_64-pc-linux-gnu/lib/libthread_db.so.1".
[New Thread 0x702bc6c0 (LWP 1654)]
[New Thread 0x7fffef8556c0 (LWP 1655)]
[New Thread 0x7fffef0546c0 (LWP 1656)]
[New Thread 0x7fffed26f6c0 (LWP 1657)]
[New Thread 0x7fffec92d6c0 (LWP 1658)]
[New Thread 0x7fffd75a26c0 (LWP 1659)]
[New Thread 0x7fffd6da16c0 (LWP 1660)]
[New Thread 0x7fffd61a06c0 (LWP 1661)]
[New Thread 0x7fffd599f6c0 (LWP 1662)]
[New Thread 0x7fffd519e6c0 (LWP 1663)]
[New Thread 0x7fffd499d6c0 (LWP 1664)]
[Thread 0x7fffd499d6c0 (LWP 1664) exited]
[Thread 0x7fffd519e6c0 (LWP 1663) exited]
[Thread 0x7fffd599f6c0 (LWP 1662) exited]
[Thread 0x7fffd61a06c0 (LWP 1661) exited]
[New Thread 0x7fffd61a06c0 (LWP 1665)]
[Detaching after fork from child process 1667]
[Detaching after fork from child process 1669]
[New Thread 0x7fffd599f6c0 (LWP 1671)]
[New Thread 0x7fffd519e6c0 (LWP 1672)]
[New Thread 0x7fffd499d6c0 (LWP 1674)]
[New Thread 0x7fffb5a546c0 (LWP 1675)]
[Detaching after fork from child process 1676]
[New Thread 0x7fffb52536c0 (LWP 1681)]
kf.coreaddons: Some files could not be exported.
QDBusError("org.freedesktop.DBus.Error.NoReply", "Message recipient
disconnected from message bus without replying")
[Thread 0x7fffd519e6c0 (LWP 1672) exited]
[Thread 0x7fffb5a546c0 (LWP 1675) exited]
[Thread 0x7fffd599f6c0 (LWP 1671) exited]
[Thread 0x7fffb52536c0 (LWP 1681) exited]
[Thread 0x7fffd499d6c0 (LWP 1674) exited]
[Thread 0x7fffd75a26c0 (LWP 1659) exited]
[Thread 0x7fffd6da16c0 (LWP 1660) exited]
[Thread 0x7fffec92d6c0 (LWP 1658) exited]
[Thread 0x7fffed26f6c0 (LWP 1657) exited]
[Thread 0x7fffef8556c0 (LWP 1655) exited]
[Thread 0x7fffef0546c0 (LWP 1656) exited]
[Thread 0x702bc6c0 (LWP 1654) exited]
[Thread 0x70606a40 (LWP 1651) exited]
[Thread 0x7fffd61a06c0 (LWP 1665) exited]
[New process 1651]
[Inferior 1 (process 1651) exited normally]
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 473733] Dolphin unable to copy or move files "The file or folder Message recipient disconnected from message bus without replying does not exist."
https://bugs.kde.org/show_bug.cgi?id=473733
Markus Schmits changed:
What|Removed |Added
CC||marsh.exhe...@gmail.com
--- Comment #4 from Markus Schmits ---
Operating System: Exherbo
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.5.3 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics
Memory: 30.6 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Starting Dolphin in Konsole gives following output, after trying to drag/ copy
a file:
$ dolphin
kf.coreaddons: Some files could not be exported.
QDBusError("org.freedesktop.DBus.Error.NoReply", "Message recipient
disconnected from message bus without replying")
--
You are receiving this mail because:
You are watching all bug changes.
[KSystemLog] [Bug 474830] New: Make default sort direction configurable
https://bugs.kde.org/show_bug.cgi?id=474830 Bug ID: 474830 Summary: Make default sort direction configurable Classification: Applications Product: KSystemLog Version: 23.08.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: nicolas.ternis...@gmail.com Reporter: markus.elfr...@web.de Target Milestone: --- I would often prefer to sort log messages by time descending (in the provided list widget). Would you like to support a corresponding property in the common application configuration (so that program users can choose the preferred sort direction as a default setting)? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 474129] New: Restore previously selected side bar when closing git history view
https://bugs.kde.org/show_bug.cgi?id=474129 Bug ID: 474129 Summary: Restore previously selected side bar when closing git history view Classification: Applications Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: i...@markus-pister.de Target Milestone: --- SUMMARY When closing the git history view of a file, the left sidebar is closed. Usually (at least in my workflow), there was a selected sidebar opened before starting to look at the git history, e.g. the project view from which the git history view was opened. It would be very convenient, to restore the sidebar used before the git history view got opened. STEPS TO REPRODUCE 1. Open project view sidebar 2. Use context menu "Show Git History" on an arbitrary file 3. Hit close button of displayed git history sidebar OBSERVED RESULT No left sidebar is displayed, all are closed. EXPECTED RESULT The sidebar is opened that was used before hitting the "Show Git History" context menu entry. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Endeavour OS using KDE/Plasma (wayland) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 461085] CR: Please add an option to disable the SSH manager plugin
https://bugs.kde.org/show_bug.cgi?id=461085 Markus Wernig changed: What|Removed |Added See Also||https://bugs.gentoo.org/sho ||w_bug.cgi?id=908444 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 461085] CR: Please add an option to disable the SSH manager plugin
https://bugs.kde.org/show_bug.cgi?id=461085 --- Comment #14 from Markus Wernig --- (In reply to July Tikhonov from comment #13) > Apparently, such flags already exist. Konsole's CMakeLists.txt has those > lines: > > option(ENABLE_PLUGIN_SSHMANAGER "Build the SSHManager plugin" ON) > option(ENABLE_PLUGIN_QUICKCOMMANDS "Build the Quick Commands plugin" ON) Thank you very much! I was now able to patch the Gentoo ebuild for konsole so that the ssh manager plugin is no longer compiled, and have opened an according change request in the Gentoo bug tracker. See https://bugs.gentoo.org/show_bug.cgi?id=908444 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 461085] CR: Please add an option to disable the SSH manager plugin
https://bugs.kde.org/show_bug.cgi?id=461085 --- Comment #12 from Markus Wernig --- (In reply to tcanabrava from comment #10) > I do understand your concerns and I plan to implement a way to disable / > unload plugins in the future, but time has been complex at the moment so I > ask for a bit of patience (or help on the code). > *I* ould personally accept a patch that allows to unload plugins (such the > one in kate) so people can use the plugins if they want, and not being > forced to. Another suggestion (also viable for me as a Gentoo Linux user) would be a compile-time make or CFLAG to disable compilation of the plugin. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 461085] CR: Please add an option to disable the SSH manager plugin
https://bugs.kde.org/show_bug.cgi?id=461085 --- Comment #11 from Markus Wernig --- (In reply to tcanabrava from comment #10) > I did indeed consider a less intrusive way to develop the plugin, but then > I realized that a lot of people that answered my request to "how do you use > profiles in konsole" were using the *profile* manager as a way to interact > with different SSH connections (some of them having over 20 - 40 profiles > that differed only in name and the ssh command. This made me think that a > plugin *for* ssh was needed. OK, so there already *was* a way to manage SSH connections in a graphical interface (albeit not perfect). >From my point of view, this approach only lacked the possibility to separate the connections into groups/categories, else it was quite viable (and less error-prone than the current plugin approach). So a (presumably) lightweight CSS update to the Konsole Profiles widget could have achieved much of the same effect the sshmanager plugin strives for. I still do not understand how the profile hack people were using to manage SSH lead to the intrusive approach that was taken with the plugin. Even if there was a general need for a SSH plugin, why choose to make it compulsory for all Konsole users and even make it parse the command line (which, in my opinion, was a less than wise design choice)? After all, Konsole is a TERMINAL emulator, not a SHELL. As such, it should respond only to defined control/escape sequences, and nothing else. > I do understand your concerns and I plan to implement a way to disable / > unload plugins in the future, I would very, very much appreciate that! But using that approach would require writing an entire plugin manager for Konsole, which seems rather unlikely to happen (given that there are no more than two "plugins" at the moment). So I would rather suggest a flag to be stored in the global section of konsolesshconfig, which should tell the plugin whether to be active or not: [Global plugin config] manageProfile=false -> enablePlugin=true|false > *I* ould personally accept a patch that allows to unload plugins (such the > one in kate) so people can use the plugins if they want, and not being > forced to. I have no meaningful experience in graphical widget frameworks more recent than BorlandC and MFC. But I will try to support any of your efforts to remedy the current situation by all means available to me. Best /m -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 461085] CR: Please add an option to disable the SSH manager plugin
https://bugs.kde.org/show_bug.cgi?id=461085 --- Comment #9 from Markus Wernig --- (In reply to tcanabrava from comment #7) > Please take in consideration the time I did put on the plugin system, to > not say things like "I was fortunate to not realize that the plugins > exist", I understand that some frustration can exist, but understand also > that this is helping a lot of people that were used to have a visual aid to > ssh in other systems - such as windows - to migrate to konsole and linux in > general. Dear @tcanabrava I did not want to belittle your work. I am sure the plugin was developped with much expertise, diligence and the best intentions. I also see your point (potentially alleviating the switch to Linux for users of graphical SSH managers like putty or SecureCRT). But is there not also the point of long-standing Linux users who do not require such alleviation? Is it fair to force them to use the plugin even if they did not choose in any way to install it? I personally do not think so. Users should have a choice, which software they want to use. SSH is a central part of my everyday work, and I choose to manage it in a way that best fits my needs. Since the sshmanager plugin cannot be configured to do the same, I do not want to use it. But that is currently not possible. Mostly, because you chose to integrate it so tightly with Konsole. It even parses the command line and acts upon that (which, by the way, is something neither putty nor SecureCRT have ever done - and rightly so). I fail to see how that would help any Linux novice, on the contrary. In the best of cases it will make them get used to a way of managing SSH that exists nowhere else and will be useless to them once they switch to another terminal emulator or desktop system. In the worst of cases it will interfere with what they want to do and drive them away. Have you ever considered a less intrusive way of integrating sshmanager with Konsole? I think if it were more of a standalone application (that could still use the konsole framework, profiles etc.), it would be even more useful - to Linux novices and existing users alike. For the time being, I stand with my request for a way to disable the plugin. This does not mean, however, that I do not appreciate the great work that you and the other KDE devs are doing! Currently, I have to do this after every Plasma update: chmod 700 /usr/lib64/qt5/plugins/konsoleplugins/konsole_sshmanagerplugin.so (Which, by the way, also disables the Ctrl-Shift-F2 shortcut). Best regards Markus -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 451876] bloated user-places.xbel causes poor performing dolphin, file open dialogs, gvenview, krusader and other apps
https://bugs.kde.org/show_bug.cgi?id=451876 Markus S. changed: What|Removed |Added CC||markus.schwarzenberg@gmail. ||com --- Comment #7 from Markus S. --- Same issue here. Ca. 10 seconds delay for the file dialog. After deleting the
[gwenview] [Bug 156042] seperate preview window for gwenview
https://bugs.kde.org/show_bug.cgi?id=156042 Markus changed: What|Removed |Added CC||markusbauer@users.sourcefor ||ge.net -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 295575] Standard directory context menu options not available in folder panel
https://bugs.kde.org/show_bug.cgi?id=295575 Markus changed: What|Removed |Added CC||markusbauer@users.sourcefor ||ge.net --- Comment #5 from Markus --- I also think those two context menus should be the same. But what I miss in particular are the "create new" and "action" menu entries. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 270360] "Create new folder" in the folder panel
https://bugs.kde.org/show_bug.cgi?id=270360 Markus changed: What|Removed |Added CC||markusbauer@users.sourcefor ||ge.net --- Comment #6 from Markus --- I second the request. This option is still not available in version 22.12.3. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 468412] New: Custom date format in details view
https://bugs.kde.org/show_bug.cgi?id=468412 Bug ID: 468412 Summary: Custom date format in details view Classification: Applications Product: dolphin Version: 22.12.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: view-engine: details mode Assignee: dolphin-bugs-n...@kde.org Reporter: markusba...@users.sourceforge.net CC: kfm-de...@kde.org Target Milestone: --- Currently dolphin in the details view uses the date format from the regional settings to format its dates. I would like to define my own format here, different from the global settings. Then it would for example be possible to add seconds to the displayed modified date. The setting could be a third option to the already existing date format settings. The clock widget could serve as reference as it already has such a setting. But for me a simple entry in the configuration file would be enough. SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466567] Kded crash at startup in KDecoration2::Decoration::setSettings()
https://bugs.kde.org/show_bug.cgi?id=466567 Markus Laker changed: What|Removed |Added CC||markus.la...@gmail.com --- Comment #2 from Markus Laker --- I suffered from the same bug. In addition, systemsettings crashed (and still does crash) when I went into the Window Decorations module. After several retries, I managed to change the window decorations from Plastik to Translucent; then I logged out and logged back in again. This has stopped kded5 from crashing. In systemsettings, you may be able to change window decorations without going into the Window Decorations module: go into "Appearance — Global Theme", click on a theme, and then click "Choose what to apply...". -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 391532] The program “KTorrent” does not display an application window.
https://bugs.kde.org/show_bug.cgi?id=391532 Markus Elfring changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #9 from Markus Elfring --- (In reply to Justin Zobel from comment #8) I can not reproduce undesirable software behaviour with the program “KTorrent 22.12.1” at the moment. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 325262] Quoting for project names (and mapping to alternative identifiers?)
https://bugs.kde.org/show_bug.cgi?id=325262 --- Comment #8 from Markus Elfring --- (In reply to Igor Kushnir from comment #7) Will any contributors get into the mood to respond with more constructive information to my initial question for this bug report? https://bugs.kde.org/show_bug.cgi?id=325262#c0 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 325262] Quoting for project names (and mapping to alternative identifiers?)
https://bugs.kde.org/show_bug.cgi?id=325262 --- Comment #6 from Markus Elfring --- (In reply to Igor Kushnir from comment #5) I would appreciate another bit of clarification according to affected aspects for desirable progress also for this bug report. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 325262] Quoting for project names (and mapping to alternative identifiers?)
https://bugs.kde.org/show_bug.cgi?id=325262 Markus Elfring changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Markus Elfring --- (In reply to Justin Zobel from comment #3) Will the chances grow to fix questionable implementation details? https://invent.kde.org/kdevelop/kdevelop/-/blob/b9cb571ab09402c624f4cf21286710a00c521c9d/app_templates/cpp/CMake/cmake_plaincpp/CMakeLists.txt -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450447] Synology Drive Client doesn't autostart
https://bugs.kde.org/show_bug.cgi?id=450447 Markus changed: What|Removed |Added CC||m.b.p...@web.de --- Comment #18 from Markus --- For anyone still having this issue, I found a workaround. Create a script which starts synology drive client and add a sleep infinity at the end. Add the script to your autostart. It's not pretty but it works for me. I've tried shorter sleeps, but this causes the drive client to close after the sleep is over. My script looks like this: #! /bin/sh synology-drive autostart sleep infinity -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 400168] Recheck tab repositioning for open files
https://bugs.kde.org/show_bug.cgi?id=400168 --- Comment #4 from Markus Elfring --- (In reply to Igor Kushnir from comment #3) I am unsure if the switcher plugin would really matter for the reported software behaviour. Did you ever check if the scroll status would be automatically adjusted for the tab list in undesirable ways? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 400168] Recheck tab repositioning for open files
https://bugs.kde.org/show_bug.cgi?id=400168 Markus Elfring changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |REOPENED Resolution|WAITINGFORINFO |--- --- Comment #2 from Markus Elfring --- (In reply to Justin Zobel from comment #1) I would appreciate a more helpful answer for my clarification request. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 317496] Fix signal handler
https://bugs.kde.org/show_bug.cgi?id=317496 Markus Elfring changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 from Markus Elfring --- (In reply to Justin Zobel from comment #5) Would you like to help any more with a proper source code review? https://github.com/KDE/plasma-workspace/blob/0ecf1cbfaa583f84a53e8710af6dcdb57bf81310/ksmserver/server.cpp#L436 -- You are receiving this mail because: You are watching all bug changes.
[kdemultimedia] [Bug 156800] Protect against spurious wakeups
https://bugs.kde.org/show_bug.cgi?id=156800 Markus Elfring changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #11 from Markus Elfring --- (In reply to Justin Zobel from comment #10) Would you like to help any more with a proper source code review? https://github.com/KDE/libkcompactdisc/blob/1771e180811d8a3f87f3e1a0003ab0360564c021/src/wmlib/cdda.c#L287 -- You are receiving this mail because: You are watching all bug changes.
[kdemultimedia] [Bug 195248] Completion of data initialisation for WorkMan
https://bugs.kde.org/show_bug.cgi?id=195248 Markus Elfring changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Markus Elfring --- (In reply to Justin Zobel from comment #3) Did you notice that the mentioned implementation details were not reconsidered so far? https://github.com/KDE/libkcompactdisc/blob/1771e180811d8a3f87f3e1a0003ab0360564c021/src/wmlib/cdda.c#L52 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 399293] Check code navigation display of parameters for a function template
https://bugs.kde.org/show_bug.cgi?id=399293 Markus Elfring changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Markus Elfring --- (In reply to Justin Zobel from comment #2) I could not reproduce the reported display situation together with the program “KDevelop 22.08.3-1.2” on my current system configuration. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 399015] Recheck indication for subitems in tree view for debug variable display
https://bugs.kde.org/show_bug.cgi?id=399015 Markus Elfring changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REOPENED Ever confirmed|0 |1 --- Comment #2 from Markus Elfring --- (In reply to Justin Zobel from comment #1) I would appreciate a more helpful answer for my clarification request. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385058] A file search result becomes unreadable.
https://bugs.kde.org/show_bug.cgi?id=385058 Markus Elfring changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 from Markus Elfring --- (In reply to Justin Zobel from comment #5) I could not reproduce the reported display situation together with the program “KDevelop 22.08.3-1.2” on my current system configuration. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 462140] OLED display brightness cannot be increased again once it reaches zero
https://bugs.kde.org/show_bug.cgi?id=462140 --- Comment #1 from Markus Krötzsch --- After checking with a colleague, I can further confirm that the same laptop model (ThinkPad X1 Yoga Gen 7) exhibits no such problem on Gnome 42.5 (from Ubuntu 22.04.1 LTS). -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 462140] OLED display brightness cannot be increased again once it reaches zero
https://bugs.kde.org/show_bug.cgi?id=462140 Markus Krötzsch changed: What|Removed |Added CC||markus@semantic-mediawiki.o ||rg -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 462140] New: OLED display brightness cannot be increased again once it reaches zero
https://bugs.kde.org/show_bug.cgi?id=462140 Bug ID: 462140 Summary: OLED display brightness cannot be increased again once it reaches zero Classification: Plasma Product: Powerdevil Version: 5.26.3 Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mar...@semantic-mediawiki.org CC: m...@ratijas.tk Target Milestone: --- SUMMARY KDE brightness controls work correctly on OLED display until the brightness reaches zero. After this, it is impossible to increase the brightness again. The bug is triggered whenever KDE sets brightness to zero (via brightness key, brightness slider, or automatically when dimming the screen after inactivity). If the laptop is closed (sleep) and openen again (waking up), the display is coming back to normal. This problem is also discussed in the KDE forum: https://forum.kde.org/viewtopic.php?f=17&t=175470 STEPS TO REPRODUCE 0. My laptop: Lenovo ThinkPad X1 Yoga Gen 7 (further OLED laptops were reported to show the same issue, see formum thread) 1. Start laptop 2. Use brightness key to decrease brightness to 0 3. Try to increase brightness again Alternatively: wait on battery power until screen is disabled, then try to re-activate the display by any key. OBSERVED RESULT Screen stays dark. EXPECTED RESULT Screen lights back up. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.26 (Kernel 5.15.0-53-generic, X11) KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION - Sending the laptop to sleep and waking it up again will restore the display (until dimmed again) - The following commands also deactivate the display, but also succeed in activating it again: xrandr --output eDP-1 --brightness 0; sleep 1; xrandr --output eDP-1 --brightness 1 - If the screen is disabled by xrandr --output eDP-1 --brightness 0, then it can also be re-activated by running xrandr --output eDP-1 --brightness 1 through a custom global shortcut. In contrast, KDE brightness controls do not work in this situation either. - However, if the screen was disabled through KDE, then even xrandr --output eDP-1 --brightness 1 does not fix it. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378883] Source code editor can become unresponsive temporarily.
https://bugs.kde.org/show_bug.cgi?id=378883 Markus Elfring changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Markus Elfring --- (In reply to Justin Zobel from comment #1) Will development experiences trigger further software adjustments also for this issue? Another example: 2019-07-31 Unable to parse Linux kernel sources https://bugs.kde.org/show_bug.cgi?id=410455 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378490] Checking column display for the position of the editor cursor
https://bugs.kde.org/show_bug.cgi?id=378490 Markus Elfring changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #8 from Markus Elfring --- (In reply to Justin Zobel from comment #7) The application “KDevelop 22.08.2” shows also a column number which might be interesting for further considerations according to the handling og “special” characters like tabs. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 359449] Selected channel name is unreadable.
https://bugs.kde.org/show_bug.cgi?id=359449 Markus Elfring changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Markus Elfring --- (In reply to Justin Zobel from comment #2) I can not reproduce the reported questionable software behaviour with the version 1.9.22082 (at the moment). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 461085] CR: Please add an option to disable the SSH manager plugin
https://bugs.kde.org/show_bug.cgi?id=461085 Markus Wernig changed: What|Removed |Added CC||pub...@wernig.net -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 461085] New: CR: Please add an option to disable the SSH manager plugin
https://bugs.kde.org/show_bug.cgi?id=461085 Bug ID: 461085 Summary: CR: Please add an option to disable the SSH manager plugin Classification: Applications Product: konsole Version: 22.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: sshmanager Assignee: konsole-de...@kde.org Reporter: pub...@wernig.net Target Milestone: --- SUMMARY *** The new SSH manager plugin interferes in many ways - some of them unexpected and confusing - with existing SSH shortcuts that users have set up over the years, as well as with ssh commands executed in the konsole terminal. On the other hand, the SSH manager plugin does not implement all functionality that was available without it (eg. via profiles, keyboard shortcuts, ssh .config file etc.). I would strongly advocate adding an option to konsole to disable the SSH manager plugin. Forcing users to tediously adapt themselves to a new way of handling their SSH setup, without any benefit, but with numerous shortcomings, is not good practice. *** STEPS TO REPRODUCE 1. Have an existing setup that uses konsole for handling SSH connections OBSERVED RESULT SSH manager plugin seemingly parses the command line executed within konsole and triggers certain actions (or blocks them) if that command appears to be ssh-related. This breaks existing setups, and there is no way of disabling the plugin. EXPECTED RESULT It should be possible to disable the SSH manager plugin. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.5 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 461084] When the command executed at konsole startup is SSH, the "Clone Tab" action does not work
https://bugs.kde.org/show_bug.cgi?id=461084 Markus Wernig changed: What|Removed |Added CC||pub...@wernig.net -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 461084] New: When the command executed at konsole startup is SSH, the "Clone Tab" action does not work
https://bugs.kde.org/show_bug.cgi?id=461084
Bug ID: 461084
Summary: When the command executed at konsole startup is SSH,
the "Clone Tab" action does not work
Classification: Applications
Product: konsole
Version: 22.04.3
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: sshmanager
Assignee: konsole-de...@kde.org
Reporter: pub...@wernig.net
Target Milestone: ---
SUMMARY
***
When konsole is given a command to execute at startup, and that command is ssh,
the "Clone Tab" action just opens a new tab and executes bash instead of the
ssh command. Funnily enough, if a profile was also given at startup, that
profile is maintained in the new tab.
***
STEPS TO REPRODUCE
1. konsole --profile someprofile -e "ssh somehost"
2. Choose File->Clone Tab or enter Ctrl-shift-Z
OBSERVED RESULT
In the first tab, the command "ssh somehost" is executed, and the tab uses the
given profile.
The second tab also uses the given profile, but does not execute "ssh
somehost", but /bin/bash.
EXPECTED RESULT
The new ("cloned") tab should also execute "ssh somehost".
This has been the behaviour for many years before the SSH manager plugin was
introduced.
When disabling the SSH manager plugin (eg. via "sudo chmod 700
/usr/lib64/qt5/plugins/konsoleplugins/konsole_sshmanagerplugin.so"), the ssh
command is executed in the new tab.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Gentoo Linux amd64
(available in About System)
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 6.96.0
Qt Version: 5.15.5
ADDITIONAL INFORMATION
Graphics platform: X11
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 460885] “Current local time zone” text does not update after being changed until you click the Apply button a second time.
https://bugs.kde.org/show_bug.cgi?id=460885 Markus Elfring changed: What|Removed |Added Summary|“Current local time zone” |“Current local time zone” |text does not update after |text does not update after |being changes until you |being changed until you |click the Apply button a|click the Apply button a |second time |second time. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 459705] Connecting to a remote host via a SSH jump host changes custom profile back to the Konsole default profile
https://bugs.kde.org/show_bug.cgi?id=459705 --- Comment #3 from Markus Wernig --- Just found another "solution". Edit ~/.config/konsolesshconfig. Somehow all entries from .ssh/config are mirrored there. And each entry has a profileName attribute that points to the name of the default konsole profile. Manually replacing them with the correct profile name "fixed" the issue for me. Unfortunately, the "solution" is incomplete, as each new alias in .ssh/config will show up there again with the default profile. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 459705] Connecting to a remote host via a SSH jump host changes custom profile back to the Konsole default profile
https://bugs.kde.org/show_bug.cgi?id=459705 Markus Wernig changed: What|Removed |Added Ever confirmed|0 |1 CC||pub...@wernig.net Status|REPORTED|CONFIRMED --- Comment #2 from Markus Wernig --- This is an extremely annoying bug that breaks users' working setups. Please fix it soon or add a possibility to disable the SSH Manager plugin. Thanks in advance -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 453545] Konsole resets font size after disconnecting from SSH session
https://bugs.kde.org/show_bug.cgi?id=453545 Markus Wernig changed: What|Removed |Added CC||pub...@wernig.net --- Comment #11 from Markus Wernig --- Removing the read bit for group/others also does the trick: chmod 700 /usr/lib64/qt5/plugins/konsoleplugins/konsole_sshmanagerplugin.so -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460885] New: Fix display for changing the setting “Current local time zone”
https://bugs.kde.org/show_bug.cgi?id=460885 Bug ID: 460885 Summary: Fix display for changing the setting “Current local time zone” Classification: Applications Product: systemsettings Version: 5.26.1 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_clock Assignee: p...@taniwha.com Reporter: markus.elfr...@web.de CC: plasma-b...@kde.org Target Milestone: --- SUMMARY I tried time property adjustments out with the image “openSUSE-Tumbleweed-KDE-Live-x86_64-Snapshot20221021-Media.iso”. STEPS TO REPRODUCE 1. I started the application “System Settings 5.26.1” where I activated the tab “Time Zone” of the configuration area “Date & Time”. 2. I searched and selected an other geographical area. 3. I clicked on the button “Apply”. OBSERVED RESULT I saw that the initially configured value was kept as the display was not updated besides the label “Current local time zone:”. EXPECTED RESULT I would appreciate that the button “Apply” does not need to be pressed twice for the activation of a different setting here. SOFTWARE VERSIONS Linux: 6.0.2-1-default KDE Frameworks: 5.99.0 Qt: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 460884] Gwenview snap is unable to generate thumbs for video files due to missing serviceType "ThumbCreator"
https://bugs.kde.org/show_bug.cgi?id=460884 Markus Ueberall changed: What|Removed |Added Summary|Gwenview snap is unable to |Gwenview snap is unable to |generate tumbs for video|generate thumbs for video |files due to missing|files due to missing |serviceType "ThumbCreator" |serviceType "ThumbCreator" -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 460884] Gwenview snap is unable to generate tumbs for video files due to missing serviceType "ThumbCreator"
https://bugs.kde.org/show_bug.cgi?id=460884 Markus Ueberall changed: What|Removed |Added CC||ueberall@projektzentrisch.d ||e -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 460884] New: Gwenview snap is unable to generate tumbs for video files due to missing serviceType "ThumbCreator"
https://bugs.kde.org/show_bug.cgi?id=460884 Bug ID: 460884 Summary: Gwenview snap is unable to generate tumbs for video files due to missing serviceType "ThumbCreator" Classification: Applications Product: gwenview Version: 22.08.1 Platform: Snap OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: ueber...@projektzentrisch.de Target Milestone: --- STEPS TO REPRODUCE 1. Point gwenview to a directory with video files OBSERVED RESULT No thumbs are created, error `kf.service.services: KServiceTypeTrader: serviceType "ThumbCreator" not found` displayed on command line twice for every encountered video file. EXPECTED RESULT Thumbs are being created/displayed (works for native version of gwenview). SOFTWARE/OS VERSIONS Linux/KDE Plasma: (Ubuntu Focal 20.04 LTS) KDE Frameworks Version: 5.96.0 (according to gwenview snap) Qt Version: 5.15.5 (according to gwenview snap) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 423540] Fix error source for a SIGSEGV crash after opening another Dolphin window
https://bugs.kde.org/show_bug.cgi?id=423540 Markus Elfring changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #2 from Markus Elfring --- (In reply to Justin Zobel from comment #1) I can not reproduce undesirable behaviour for the program “klauncher” (from the software package “kinit 5.98.0”) at the moment. -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 419386] KDE Menu Editor crashed after saving the menu using 'Restore to System Menu'
https://bugs.kde.org/show_bug.cgi?id=419386 Markus Schmits changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 from Markus Schmits --- The issue cannot be reproduced in a recent version of the software. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456745] Task Manager icons go to second row and become invisible when using a size-constrained panel
https://bugs.kde.org/show_bug.cgi?id=456745 Markus Heß changed: What|Removed |Added CC||hess...@googlemail.com --- Comment #8 from Markus Heß --- Created attachment 152347 --> https://bugs.kde.org/attachment.cgi?id=152347&action=edit Task Manager with Icon in second row Same issue here on KDE neon. In my case the last icon isn't even visible and therefore it is not possible to select the application (see Screenshot). My Theme is Materia. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 458554] LSP plugin quickfix action has no effect anymore
https://bugs.kde.org/show_bug.cgi?id=458554 Markus Pister changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #5 from Markus Pister --- Thanks for integrating the patch. Checked again with a compile of current master (565b1004). Works as expected. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 458116] Articles spilling from one feed to another
https://bugs.kde.org/show_bug.cgi?id=458116 Markus changed: What|Removed |Added CC||m4rkus...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 458554] LSP plugin quickfix action has no effect anymore
https://bugs.kde.org/show_bug.cgi?id=458554 --- Comment #2 from Markus Pister --- Created attachment 151777 --> https://bugs.kde.org/attachment.cgi?id=151777&action=edit Experimental patch that solves the reported issue The attached patch solves the issue for me locally. However, I'm not sure whether the patch is correct in call cases. If the only code actions that can be triggered are such quickfix actions, it might be okay. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 458554] LSP plugin quickfix action has no effect anymore
https://bugs.kde.org/show_bug.cgi?id=458554
--- Comment #1 from Markus Pister ---
To help in identifying the issue cause in the code, I bisected kate with the
following result:
bccf9a58ab1bb6f435eb942b46a2931dd9aedd0d is the first bad commit
commit bccf9a58ab1bb6f435eb942b46a2931dd9aedd0d
Author: Mark Nauwelaerts
Date: Wed Feb 9 21:47:26 2022 +0100
lspclient: use multiple items for a diagnostic item with embedded newlines
addons/lspclient/lspclientpluginview.cpp | 30 ++
1 file changed, 26 insertions(+), 4 deletions(-)
Funnily, my proposed test code did not exhibit a quickfix action anymore, so I
worked on the following test code (put into test.cpp):
int sensor;
int main()
{
senSor = 0;
return 0;
}
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 458554] New: LSP plugin quickfix action has no effect anymore
https://bugs.kde.org/show_bug.cgi?id=458554
Bug ID: 458554
Summary: LSP plugin quickfix action has no effect anymore
Product: kate
Version: Git
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: application
Assignee: kwrite-bugs-n...@kde.org
Reporter: i...@markus-pister.de
Target Milestone: ---
SUMMARY
Double-clicking an [quickfix] action item in the LSP Diagnostics view has no
effect anymore.
STEPS TO REPRODUCE
1. Consider the following sample C++ code with activated LSP plugin
int main()
{
std::string someString { "foo" };
return 0;
}
2. Open the LSP diagnostics view
The view should show the following content:
[clang] (undeclared_var_use) Use of undeclared identifier 'std' (fix available)
-> [quickfix] Include for symbol std::string
3. Double-click on the line entry [quickfix]
OBSERVED RESULT
Nothing happens.
EXPECTED RESULT
The quickfix should be executed, i.e. the appropriate include statement should
be inserted.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 5.24.6
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.5
ADDITIONAL INFORMATION
Kate has been compiled with HEAD == e1b4bc5c
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 Markus Heß changed: What|Removed |Added CC|hess...@googlemail.com | -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 457577] Better support for time series diagram with trilean values
https://bugs.kde.org/show_bug.cgi?id=457577 --- Comment #4 from Markus Elfring --- (In reply to Alexander Semke from comment #3) > … but I need to see the input data. … Trilean values will be used for the mentioned diagram type. How will (graphical) representations evolve then for concrete data variations? -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 457577] Better support for time series diagram with trilean values
https://bugs.kde.org/show_bug.cgi?id=457577 --- Comment #2 from Markus Elfring --- (In reply to Alexander Semke from comment #1) How much do you understand data processing requirements for trilean values according to (digital) timing diagrams? -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 457577] New: Better support for time series diagram with trilean values
https://bugs.kde.org/show_bug.cgi?id=457577 Bug ID: 457577 Summary: Better support for time series diagram with trilean values Product: LabPlot2 Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: markus.elfr...@web.de Target Milestone: --- Trilean values can be displayed by the chart software already in principle. But I imagine that ternary data can be configured and presented in more convenient ways for clearer diagrams of multiple time series. * Variations exist for the representation of this data type. https://en.wikipedia.org/wiki/Three-valued_logic#Representation_of_values It would be nice to support it without adding transformations in extra columns (or rows). Can any known conversions become built-in for such input data? * Intermediate increments should not be displayed as in comparison to regular line chart types. Specific lines or filled rectangles should be shown in lanes. Example: https://en.wikipedia.org/wiki/Digital_timing_diagram -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 452758] Valgrind does not read properly DWARF5 as generated by Clang14
https://bugs.kde.org/show_bug.cgi?id=452758 Markus Stange changed: What|Removed |Added CC||mstange@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 439940] Support time-based data types
https://bugs.kde.org/show_bug.cgi?id=439940 --- Comment #2 from Markus Elfring --- (In reply to Oliver Kellogg from comment #1) > By "attributes" to you mean state members in data types? Probably, yes. https://en.wikipedia.org/wiki/Attribute_(computing) Will the support grow also for items in the time dimension? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442723] Dolphin slow to list SMB folder content
https://bugs.kde.org/show_bug.cgi?id=442723 --- Comment #3 from Markus Elfring --- (In reply to MarcSerra from comment #2) > Are you a developer Yes, too. > and do you need me to do some testing? It depends on involved goals. Do you notice any improvements together with more recent software components? > Or you experimented the same issue Not directly. I can become affected also by undesirable side-effects of some (software) evolution. > and only want to stay up to date for this bug discussion? Mainly, yes. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 452989] Dolphin can not connect to a specific SMB share any more (since Samba 4.16.0)?
https://bugs.kde.org/show_bug.cgi?id=452989 --- Comment #4 from Markus Elfring --- (In reply to Nate Graham from comment #3) Would you like to point any additional possibilities out for the determination of further background information and the clarification of software components which are currently used by Dolphin 22.04.0 according to evolving SMB support? -- You are receiving this mail because: You are watching all bug changes.
