[policykit-kde-agent-1] [Bug 485407] polkit-kde-agent crashes with nullptr in PolicyKitListener::finishObtainPrivilege() when run in Hyprland
https://bugs.kde.org/show_bug.cgi?id=485407 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de --- Comment #22 from Alois Wohlschlager --- *** Bug 486519 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 486519] Segmentation fault after authentication
https://bugs.kde.org/show_bug.cgi?id=486519 Alois Wohlschlager changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Alois Wohlschlager --- *** This bug has been marked as a duplicate of bug 485407 *** -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 486519] New: Segmentation fault after authentication
https://bugs.kde.org/show_bug.cgi?id=486519 Bug ID: 486519 Summary: Segmentation fault after authentication Classification: Plasma Product: policykit-kde-agent-1 Version: 6.0.4 Platform: NixOS OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: alo...@gmx-topmail.de CC: d...@kde.org, jgrul...@redhat.com, jrez...@redhat.com Target Milestone: --- SUMMARY After any authentication attempt (successful or not), polkit-kde-authentication-agent-1 segfaults. STEPS TO REPRODUCE 1. Run `journalctl --user -f -u plasma-polkit-agent.service` in a terminal to obtain log messages (keep this running) 2. Perform any action that requires polkit authentication (for example, run `pkexec true` in a second terminal) 3. Finish or cancel the authentication OBSERVED RESULT As evidenced by the log messages showing up in the terminal from the first step, polkit-kde-authentication-agent-1 terminates as the result of a segmentation fault. EXPECTED RESULT The polkit agent keeps running, ready to accept another authentication request. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Backtrace (please tell me if you need a better one): #0 0x751d33c4 in QObject::deleteLater() () from /nix/store/az08nlbvpaxrgl07scysk36vscpxkzx4-qtbase-6.7.0/lib/libQt6Core.so.6 #1 0x00409d31 in PolicyKitListener::finishObtainPrivilege (this=0x7c8660) at /build/polkit-kde-agent-1-6.0.4/policykitlistener.cpp:205 #2 0x751e4f10 in void doActivate(QObject*, int, void**) () from /nix/store/az08nlbvpaxrgl07scysk36vscpxkzx4-qtbase-6.7.0/lib/libQt6Core.so.6 #3 0x751e4f10 in void doActivate(QObject*, int, void**) () from /nix/store/az08nlbvpaxrgl07scysk36vscpxkzx4-qtbase-6.7.0/lib/libQt6Core.so.6 #4 0x772456df in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /nix/store/d6q42lq8m8sskbn17hjq75xwdyai7jfl-qtdeclarative-6.7.0/lib/libQt6Qml.so.6 #5 0x7719dc13 in QQmlObjectOrGadget::metacall(QMetaObject::Call, int, void**) const () from /nix/store/d6q42lq8m8sskbn17hjq75xwdyai7jfl-qtdeclarative-6.7.0/lib/libQt6Qml.so.6 #6 0x7704d14e in QV4::CallPrecise(QQmlObjectOrGadget const&, QQmlPropertyData const&, QV4::ExecutionEngine*, QV4::CallData*, QMetaObject::Call) () from /nix/store/d6q42lq8m8sskbn17hjq75xwdyai7jfl-qtdeclarative-6.7.0/lib/libQt6Qml.so.6 #7 0x7704f771 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /nix/store/d6q42lq8m8sskbn17hjq75xwdyai7jfl-qtdeclarative-6.7.0/lib/libQt6Qml.so.6 #8 0x770a8719 in QV4::Moth::VME::interpret(QV4::JSTypesStackFrame*, QV4::ExecutionEngine*, char const*) () from /nix/store/d6q42lq8m8sskbn17hjq75xwdyai7jfl-qtdeclarative-6.7.0/lib/libQt6Qml.so.6 #9 0x770aba67 in QV4::Moth::VME::exec(QV4::JSTypesStackFrame*, QV4::ExecutionEngine*) () from /nix/store/d6q42lq8m8sskbn17hjq75xwdyai7jfl-qtdeclarative-6.7.0/lib/libQt6Qml.so.6 #10 0x76ff590e in QV4::doCall(QV4::Function*, QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext*) () from /nix/store/d6q42lq8m8sskbn17hjq75xwdyai7jfl-qtdeclarative-6.7.0/lib/libQt6Qml.so.6 #11 0x76ff60bb in QV4::Function::call(QObject*, void**, QMetaType const*, int, QV4::ExecutionContext*) () from /nix/store/d6q42lq8m8sskbn17hjq75xwdyai7jfl-qtdeclarative-6.7.0/lib/libQt6Qml.so.6 #12 0x7715bbb5 in QQmlJavaScriptExpression::evaluate(void**, QMetaType const*, int) () from /nix/store/d6q42lq8m8sskbn17hjq75xwdyai7jfl-qtdeclarative-6.7.0/lib/libQt6Qml.so.6 #13 0x770fe895 in QQmlBoundSignalExpression::evaluate(void**) () from /nix/store/d6q42lq8m8sskbn17hjq75xwdyai7jfl-qtdeclarative-6.7.0/lib/libQt6Qml.so.6 #14 0x770ff270 in QQmlBoundSignal_callback(QQmlNotifierEndpoint*, void**) () from /nix/store/d6q42lq8m8sskbn17hjq75xwdyai7jfl-qtdeclarative-6.7.0/lib/libQt6Qml.so.6 #15 0x771883da in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /nix/store/d6q42lq8m8sskbn17hjq75xwdyai7jfl-qtdeclarative-6.7.0/lib/libQt6Qml.so.6 #16 0x751e4658 in void doActivate(QObject*, int, void**) () from /nix/store/az08nlbvpaxrgl07scysk36vscpxkzx4-qtbase-6.7.0/lib/libQt6Core.so.6 #17 0x776c0bff in QQuickWindowQmlImpl::visibleChanged(bool) () from /nix/store/d6q42lq8m8sskbn17hjq75xwdyai7jfl-qtdeclarative-6.7.0/lib/libQt6Quick.so.6 #18 0x751e4cc3 in void doActivate(QObject*, int, void**) () from /nix/store/az08nlbvpaxrgl07scysk36vscpxkzx4-qtbase-6.7.0/lib/libQt6Core.so.6 #19 0x75a2da42 in QWindow::visibleChanged(bool) () from
[systemsettings] [Bug 484682] Since 6.0.3, global shortcuts do not persist settings across sessions and behave erratically
https://bugs.kde.org/show_bug.cgi?id=484682 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 474848] Toolbar items sometimes move to weird places when creating split view
https://bugs.kde.org/show_bug.cgi?id=474848
--- Comment #2 from Alois Wohlschlager ---
The behavior seems very erratic to me as well, that's why I reported the bug to
begin with. If this wasn't clear from my description ("the session toolbar and
hamburger menu remain where they belong"), I meant that it should stay in the
toolbar where it was before creating the splits.
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 474848] New: Toolbar items sometimes move to weird places when creating split view
https://bugs.kde.org/show_bug.cgi?id=474848 Bug ID: 474848 Summary: Toolbar items sometimes move to weird places when creating split view Classification: Applications Product: konsole Version: 23.08.1 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: split-view Assignee: konsole-de...@kde.org Reporter: alo...@gmx-topmail.de Target Milestone: --- SUMMARY When creating a split view in Konsole, toolbar items (most often the hamburger menu or the session toolbar) sometimes move to places where they don't belong at all. STEPS TO REPRODUCE 1. Open Konsole, and ensure that session toolbar is enabled and menu bar disabled (the latter is not required, ignore steps talking about the hamburger button then) 2. Create a vertical split view 3. Right-click in the left part of the split, without left-clicking into it first OBSERVED RESULT The session toolbar now weirdly floats above the left part of the split. The hamburger menu is now moved to the right-click menu of the left part of the split. EXPECTED RESULT Both the session toolbar and the hamburger button remain where they belong. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.5.4 (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION When the bug happens, "Adding a KHamburgerMenu directly to a QMenu. This will look odd. Use addToMenu() instead." is logged four times. But I think that's a symptom rather than a cause of the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 449265] Can not connect any device to WAP/WAP2/WAP3 shared network created through plasma-nm
https://bugs.kde.org/show_bug.cgi?id=449265 --- Comment #10 from Alois Wohlschlager --- > Thanks a lot. I tried to mail hostap but it keeps blocking my mail for some > reason and I couldn't figure out where I should report them the bug. I have no experience with this list in particular, but it is likely that the first message sent from a new email address needs moderator approval (this is a common process to prevent spam). > Also, I have issue with both WPA2 and WPA3 encryption. You actually don't. When you tell NetworkManager to create a WPA2 access point, it actually creates a hybrid WPA2/WPA3 access point. Your other device prefers to connect to WPA3 and subsequently fails. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 449265] Can not connect any device to WAP/WAP2/WAP3 shared network created through plasma-nm
https://bugs.kde.org/show_bug.cgi?id=449265 --- Comment #8 from Alois Wohlschlager --- My adapter broke, and I cannot reproduce the bug with the new device any more. Since we already figured out the bug is likely not in Plasma, I'd try the hostap mailing list. The problem appears to be that some device/driver/wpa_supplicant combinations fail to set up a WPA3 access point properly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466017] Tiling Shortcut (Shift) not working with Keyboard-Layout German (Neo, QWERTZ)
https://bugs.kde.org/show_bug.cgi?id=466017 --- Comment #4 from Alois Wohlschlager --- I think the /usr/share/kbd/keymaps/i386/neo/neoqwertz.map.gz difference is a red herring. This is the console keymap. `xkbcli` tells me about `Shift_L` and `Shift_R` with both standard QWERTZ layout (which works) and Neo (which doesn't work). My guess would be that the Neo caps-lock implementation (pressing both shift keys at the same time) somehow leads to a difference in the state machine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466017] Tiling Shortcut (Shift) not working with Keyboard-Layout German (Neo, QWERTZ)
https://bugs.kde.org/show_bug.cgi?id=466017 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 449265] Can not connect any device to WAP/WAP2/WAP3 shared network created through plasma-nm
https://bugs.kde.org/show_bug.cgi?id=449265 --- Comment #5 from Alois Wohlschlager --- This is likely unrelated, try running on a fixed channel by adding a line "channel=1" (without quotes) to the hostapd.conf. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 449265] Can not connect any device to WAP/WAP2/WAP3 shared network created through plasma-nm
https://bugs.kde.org/show_bug.cgi?id=449265 --- Comment #3 from Alois Wohlschlager --- I think this is wpa_supplicant somehow failing to create a WPA3 hotspot properly. To confirm, can you please try the following (adjust and appropriately): $ cat > hostapd.conf < ssid=hotspot wpa=2 wpa_key_mgmt=SAE wpa_passphrase= EOF $ sudo hostapd hostapd.conf Then try to connect to the hotspot using a different device after the AP-ENABLED message appears. Then, please report whether hostapd prints anything else. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 449265] Can not connect any device to WAP/WAP2/WAP3 shared network created through plasma-nm
https://bugs.kde.org/show_bug.cgi?id=449265 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de --- Comment #1 from Alois Wohlschlager --- What distribution does this happen on for you? I have a feeling this bug depends heavily on non-KDE components. Also to be clear, unencrypted hotspot works, right? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448062] New: Crash in operator()
https://bugs.kde.org/show_bug.cgi?id=448062 Bug ID: 448062 Summary: Crash in operator() Product: kwin Version: 5.23.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: platform-drm Assignee: kwin-bugs-n...@kde.org Reporter: alo...@gmx-topmail.de Target Milestone: --- SUMMARY KWin suddenly crashed. I obtained the provided backtrace. STEPS TO REPRODUCE 1. I was using the computer normally. Multiple windows were open, and I was moving the mouse around. I do not remember anything particularly special. 2. Maybe it is relevant that a system upgrade was running in a background terminal, but at least the main part of the upgrade was already finished when the crash happened judging by the logs. 3. I was unable to reproduce the crash. OBSERVED RESULT KWin crashed. EXPECTED RESULT KWin keeps running. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Backtrace: #0 0x7f5d41a7a9f8 in operator() (obj=0x6d00720064005f, __closure=) at /usr/src/debug/kwin5-5.23.4-1.3.x86_64/src/plugins/platforms/drm/drm_pipeline.cpp:193 #1 __gnu_cxx::__ops::_Iter_pred >::operator() (__it=0x5590bcc4fd40, this=) at /usr/include/c++/11/bits/predefined_ops.h:318 #2 std::__find_if > > (__pred=..., __last=0x5590bcc7a9a8, __first=0x5590bcc4fd40) at /usr/include/c++/11/bits/stl_algobase.h:2081 #3 std::__find_if > > (__pred=..., __last=0x5590bcc7a9a8, __first=) at /usr/include/c++/11/bits/stl_algobase.h:2114 #4 std::find_if > (__pred=..., __last=0x5590bcc7a9a8, __first=) at /usr/include/c++/11/bits/stl_algo.h:3910 #5 std::none_of > (__pred=..., __last=0x5590bcc7a9a8, __first=) at /usr/include/c++/11/bits/stl_algo.h:471 #6 std::any_of > (__pred=..., __last=0x5590bcc7a9a8, __first=) at /usr/include/c++/11/bits/stl_algo.h:490 #7 KWin::DrmPipeline::populateAtomicValues(_drmModeAtomicReq*, unsigned int&) (flags=@0x7ffe1bc217b4: 1, req=0x5590bcd7b280, this=0x5590bc452950) at /usr/src/debug/kwin5-5.23.4-1.3.x86_64/src/plugins/platforms/drm/drm_pipeline.cpp:193 #8 KWin::DrmPipeline::commitPipelines(QVector const&, KWin::DrmPipeline::CommitMode) (pipelines=..., mode=mode@entry=KWin::DrmPipeline::CommitMode::Commit) at /usr/src/debug/kwin5-5.23.4-1.3.x86_64/src/plugins/platforms/drm/drm_pipeline.cpp:150 #9 0x7f5d41a7b5d4 in KWin::DrmPipeline::atomicCommit() (this=0x5590bc452950) at /usr/src/debug/kwin5-5.23.4-1.3.x86_64/src/plugins/platforms/drm/drm_pipeline.cpp:117 #10 0x7f5d41a70a95 in KWin::DrmPipeline::present(QSharedPointer const&) (buffer=..., this=) at /usr/src/debug/kwin5-5.23.4-1.3.x86_64/src/plugins/platforms/drm/drm_pipeline.cpp:97 #11 KWin::DrmOutput::present(QSharedPointer const&, QRegion) (damagedRegion=..., buffer=..., this=) at /usr/src/debug/kwin5-5.23.4-1.3.x86_64/src/plugins/platforms/drm/drm_output.cpp:398 #12 KWin::DrmOutput::present(QSharedPointer const&, QRegion) (this=this@entry=0x5590bb8d9c40, buffer=..., damagedRegion=...) at /usr/src/debug/kwin5-5.23.4-1.3.x86_64/src/plugins/platforms/drm/drm_output.cpp:389 #13 0x7f5d41a7c97f in KWin::EglGbmBackend::endFrame(KWin::AbstractOutput*, QRegion const&, QRegion const&) (this=, drmOutput=, renderedRegion=, damagedRegion=) at /usr/src/debug/kwin5-5.23.4-1.3.x86_64/src/plugins/platforms/drm/egl_gbm_backend.cpp:584 #14 0x7f5d4057f660 in KWin::SceneOpenGL::paint(KWin::AbstractOutput*, QRegion const&, QList const&, KWin::RenderLoop*) (renderLoop=, toplevels=, damage=, output=0x5590bb8d9c40, this=0x5590bba9f180) at /usr/src/debug/kwin5-5.23.4-1.3.x86_64/src/plugins/scenes/opengl/scene_opengl.cpp:462 #15 KWin::SceneOpenGL::paint(KWin::AbstractOutput*, QRegion const&, QList const&, KWin::RenderLoop*) (this=0x5590bba9f180, output=0x5590bb8d9c40, damage=, toplevels=, renderLoop=) at /usr/src/debug/kwin5-5.23.4-1.3.x86_64/src/plugins/scenes/opengl/scene_opengl.cpp:361 #16 0x7f5d49d1dd71 in KWin::Compositor::composite(KWin::RenderLoop*) (this=0x5590bb9a2400, renderLoop=0x5590bb9eaac0) at /usr/src/debug/kwin5-5.23.4-1.3.x86_64/src/composite.cpp:623 #17 0x7f5d484fc393 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffe1bc21d60, r=0x5590bb9a2400, this=0x5590bc1b4ee0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #18 doActivate(QObject*, int, void**) (sender=0x5590bb9eaac0, signal_index=5, argv=0x7ffe1bc21d60) at kernel/qobject.cpp:3886 #19 0x7f5d484f585f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7f5d49f47560 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffe1bc21d60) at kernel/qobject.cpp:3946 #20 0x7f5d49cdb502 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*) (this=, _t1=) at
[Powerdevil] [Bug 438716] Lid close leads to suspend even when external monitor is attached
https://bugs.kde.org/show_bug.cgi?id=438716 --- Comment #11 from Alois Wohlschlager --- > This is Wayland-only, correct? I cannot reproduce the bug any more, but it definitely did happen on Wayland. I don't remember checking whether it worked on X11. > Does it show "your computer is configured not to suspend while an external > monitor is plugged in" in Battery Monitor? Yes, it did. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 442122] New: Connection registration gets stuck when server supports no capabilities
https://bugs.kde.org/show_bug.cgi?id=442122 Bug ID: 442122 Summary: Connection registration gets stuck when server supports no capabilities Product: konversation Version: 1.8.21081 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: protocol Assignee: konversation-de...@kde.org Reporter: alo...@gmx-topmail.de Target Milestone: --- SUMMARY When connecting to a server which supports capability negotiation but no capabilities, Konversation never resumes the connection registration process, so the connection gets stuck. STEPS TO REPRODUCE 1. Write an IRC server which sends "CAP * LS :" as response to "CAP LS 302" 2. Connect to that server OBSERVED RESULT Konversation sends NICK, USER, then connection registration gets stuck. EXPECTED RESULT Konversation sends NICK, USER and then CAP END to resume (and finish) connection registration with the server. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: n/a KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 442121] New: Noncompliant line ending in outgoing messages
https://bugs.kde.org/show_bug.cgi?id=442121 Bug ID: 442121 Summary: Noncompliant line ending in outgoing messages Product: konversation Version: 1.8.21081 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: protocol Assignee: konversation-de...@kde.org Reporter: alo...@gmx-topmail.de Target Milestone: --- SUMMARY Konversation sends outgoing IRC messages with LF termination. The IRC protocol specifications demand CRLF termination. STEPS TO REPRODUCE 1. Start traffic capture in Wireshark 2. Use Konversation to connect to an IRC server without TLS encryption (same bug happens with TLS, but it's easier to observe without) 3. Check traffic in wireshark OBSERVED RESULT Outgoing messages are sent with LF (0a) line ending EXPECTED RESULT Outgoing messages are sent with CRLF (0d 0a) line ending SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: n/a KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 440743] New: Socketpair wrapper does not handle emulated resource limit properly
https://bugs.kde.org/show_bug.cgi?id=440743
Bug ID: 440743
Summary: Socketpair wrapper does not handle emulated resource
limit properly
Product: valgrind
Version: unspecified
Platform: Other
OS: Unspecified
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: alo...@gmx-topmail.de
Target Milestone: ---
SUMMARY
The syscall wrapper for socketpair returns success if the emulated resource
limit for open files is exhausted. It should fail with error EMFILE.
STEPS TO REPRODUCE
1. Compile the following test program:
#include
#include
#include
#include
int main()
{
struct rlimit lim;
getrlimit(RLIMIT_NOFILE, );
lim.rlim_cur = 3;
setrlimit(RLIMIT_NOFILE, );
int sv[2];
printf("%d\n", socketpair(AF_UNIX, SOCK_STREAM, 0, sv));
}
2. Run the compiled program with valgrind (the tool does not matter)
OBSERVED RESULT
Test program prints 0
EXPECTED RESULT
Test program prints -1
SOFTWARE/OS VERSIONS
Valgrind: 3.17.0
--
You are receiving this mail because:
You are watching all bug changes.
[Powerdevil] [Bug 438716] Lid close leads to suspend even when external monitor is attached
https://bugs.kde.org/show_bug.cgi?id=438716 --- Comment #2 from Alois Wohlschlager --- > This gets more annoying if you start your laptop with the lid closed > resulting in it going to sleep immediately after logging in. I cannot reproduce this behavior. In fact, logging in with the lid closed is how I work around this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439712] Plasma Wayland crashed after turning hdmi monitor off
https://bugs.kde.org/show_bug.cgi?id=439712 Alois Wohlschlager changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||alo...@gmx-topmail.de --- Comment #1 from Alois Wohlschlager --- This looks like a KWin crash. There was a kwin_wayland crash related to plugging external monitors fixed in 5.22, can you check whether this is still reproducible using a 5.22 version? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439674] Launches a wrong program
https://bugs.kde.org/show_bug.cgi?id=439674 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Alois Wohlschlager --- This is not relevant any more in the new Kickoff. It's a pity that Debian will not ship that for two more years. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439629] kwin/plasma does not start with wayland x11 backend on Devuan
https://bugs.kde.org/show_bug.cgi?id=439629 Alois Wohlschlager changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM CC||alo...@gmx-topmail.de --- Comment #1 from Alois Wohlschlager --- > WORKAROUND / SOLUTION > Install "kwin-wayland-backend-drm" and have it use the DRM backend. That's not a workaround, it's the correct solution. The X11 backend enables running kwin_wayland in windowed mode, nested in an X11 session. The DRM backend enables running a standalone session. If the dependency resolver chose to install the wrong backend on its own, please file a packaging bug against your distribution. -- You are receiving this mail because: You are watching all bug changes.
[plasma-disks] [Bug 439569] SMART: Healthy drive with ABRT error log records leads to warning about possible hard drive malfunction
https://bugs.kde.org/show_bug.cgi?id=439569 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439563] KMail completely breaks when running on Wayland
https://bugs.kde.org/show_bug.cgi?id=439563 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de --- Comment #3 from Alois Wohlschlager --- You can use Help>About KMail>Libraries to get KMail, Frameworks and Qt versions. -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 436864] Grayscale antialiasing in apps using KDE Platform
https://bugs.kde.org/show_bug.cgi?id=436864 Alois Wohlschlager changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/pack ||aging/flatpak-kde-runtime/c ||ommit/41108d25592dfff573717 ||310670997f3e9c9d2f6 --- Comment #2 from Alois Wohlschlager --- Git commit 41108d25592dfff573717310670997f3e9c9d2f6 by Alois Wohlschlager. Committed on 09/07/2021 at 14:07. Pushed by apol into branch 'qt5.15lts'. Allow reading fontconfig settings from host Fontconfig settings were not visible inside the sandbox, leading to subpar font rendering. Make the host settings available to flatpaked apps to enable better font rendering. M +1-0org.kde.Sdk.json.in https://invent.kde.org/packaging/flatpak-kde-runtime/commit/41108d25592dfff573717310670997f3e9c9d2f6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439408] Dirty shadows around certain panes, bars & application menus
https://bugs.kde.org/show_bug.cgi?id=439408 --- Comment #12 from Alois Wohlschlager --- I think I have a reliable reproducer now (I use a left panel with Kickoff at the top and Digital Clock at the bottom, to put the locations of the mirrored shadows into context). * When the first thing I do with a fresh plasmashell (i.e. after login or plasmashell restart) is opening Kickoff, subsequent popups will have mirrored shadows at the bottom and right sides. Kickoff itself only gets the mirrored shadow after another popup has appeared in the meantime. * If the first thing I do is opening the calendar, subsequent popus will have mirrored shadows at the top and right sides. Similar to above, the calendar itself only displays mirrored shadows if something else was popped up in the meantime. * If any popup other than the two mentioned before opens first (including the tooltip of Kickoff or Digital Clock), all shadows display in the correct orientation. * Panel and window shadows are unaffected in any case. The behavior is completely reproducible in my setup. Deleting the cache files does not seem to have any impact in any way. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439408] Dirty shadows around certain panes, bars & application menus
https://bugs.kde.org/show_bug.cgi?id=439408 --- Comment #9 from Alois Wohlschlager --- > Can you confirm if this is "resolved" by removing ~/.cache/*.kcache and > restarting plasmashell In fact, just restarting plasmashell seemed to be enough. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439408] Dirty shadows around certain panes, bars & application menus
https://bugs.kde.org/show_bug.cgi?id=439408 --- Comment #8 from Alois Wohlschlager --- > possibly duplicate of bug 429057 Might be related, but the glitch there looks pretty different to me. Bug 438696 is probably a duplicate of the present issue instead. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 439245] Breeze GTK still has a grey close button
https://bugs.kde.org/show_bug.cgi?id=439245 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de --- Comment #2 from Alois Wohlschlager --- The wrong icon is actually not Wayland-specific, but kde-gtk-config masks the issue on X11 and does not work properly on Wayland (https://bugs.kde.org/show_bug.cgi?id=437082). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439267] Frequent freezes since switching to Wayland
https://bugs.kde.org/show_bug.cgi?id=439267 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de --- Comment #3 from Alois Wohlschlager --- Could you check whether you can reproduce the issue on Xorg with your new system configuration? That will tell us at least whether it's a btrfs issue or a KWin/Wayland issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439408] Dirty shadows around certain panes, bars & application menus
https://bugs.kde.org/show_bug.cgi?id=439408 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de --- Comment #5 from Alois Wohlschlager --- The shadows seem to be mirrored. I sometimes observe the same behavior as well. It does not happen all the time, but it seems to be consistent within one session. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439138] Some Flatpak applications are not showing in application launcher
https://bugs.kde.org/show_bug.cgi?id=439138 Alois Wohlschlager changed: What|Removed |Added Status|REPORTED|RESOLVED CC||alo...@gmx-topmail.de Resolution|--- |INTENTIONAL --- Comment #1 from Alois Wohlschlager --- > OnlyShowIn=GNOME; All your affected apps specifically request only being shown in GNOME. Plasma honors that request and does not show them. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439070] Unable to copy/paste when using Wayland
https://bugs.kde.org/show_bug.cgi?id=439070 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de --- Comment #7 from Alois Wohlschlager --- > So it's just copying to xwayland clients from the list there. Krita runs on XWayland as well as far as I know and the reporter has indicated that pasting into Krita does not work either. Based on my own testing, it seems to me that pasting into Wayland clients never works, while pasting to XWayland client sometimes works and sometimes not. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 438965] ELF Extensions need mimetype icons.
https://bugs.kde.org/show_bug.cgi?id=438965 Alois Wohlschlager changed: What|Removed |Added CC||kain...@gmail.com Status|REPORTED|CONFIRMED Assignee|mp...@kde.org |visual-des...@kde.org Component|general |Icons Product|frameworks-kcoreaddons |Breeze Version|unspecified |5.22.2 Ever confirmed|0 |1 --- Comment #3 from Alois Wohlschlager --- I have reported the .mod issue against shared-mime-info [0], since this is where the mimetype detection is specified. Breeze explicitly ships the "unknown file type" icon for application/x-object (which is what .ko files get detected as), which I think is very suboptimal. Hence I have marked this bug as confirmed. [0] https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/165 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438990] Better detection of unresponsive applications
https://bugs.kde.org/show_bug.cgi?id=438990 --- Comment #3 from Alois Wohlschlager --- I'm on openSUSE Tumbleweed 20210623 with Plasma 5.22.1 and standard KWin. I'm running a Wayland session on an Intel GPU. Screen content was never reused with my setup. I now retried with Xorg and can reproduce the reuse of screen content there. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438990] Better detection of unresponsive applications
https://bugs.kde.org/show_bug.cgi?id=438990 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de --- Comment #1 from Alois Wohlschlager --- While I agree that the current behavior is not ideal, I cannot reproduce the bug entirely with your steps. What happens in my case is the following: * Screen content is not reused, the Kate window displays like it did the last time before the SIGSTOP. * The desaturation is applied after a couple of seconds even without any interaction with the Kate window (apart from minimizing and unminimizing). * The dialog does not show up at all, instead the window closes after some seconds while leaving the stopped kate process hanging around. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 438965] ELF Extensions need mimetype icons.
https://bugs.kde.org/show_bug.cgi?id=438965 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de --- Comment #1 from Alois Wohlschlager --- I think there are multiple different bugs here. * The file tool thinks that .ko files are object files (not ideal), and object files are missing a mimetype icon. * .mod files are also object files according to the file tool, but it shows up as "Amiga SoundTracker Audio" in Dolphin. Can you reproduce this behavior? In this case, the .mod issue should probably be filed separately. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 438954] Crashes after showing background activity warning
https://bugs.kde.org/show_bug.cgi?id=438954 Alois Wohlschlager changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE CC||alo...@gmx-topmail.de --- Comment #1 from Alois Wohlschlager --- I don't see an "allow" button, do you mean the close button or the "find out more" button? Please try to create a backtrace again after cleaning the debuginfod cache (sometimes, stale or corrupt entries there seem to make gdb hang). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438950] When I click on the Kickoff menu plasmoid and hover over the first few application categories it doesn't switches to first few categories instantly
https://bugs.kde.org/show_bug.cgi?id=438950 Alois Wohlschlager changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||alo...@gmx-topmail.de --- Comment #2 from Alois Wohlschlager --- I can confirm this behavior when moving the mouse slightly diagonally. I think this is the triangle filter being a bit too eager to think the user wants to move the mouse to the application list on the right. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438909] Multinegation in “Inhibit automatic sleep and screen locking” checkbox confuses me.
https://bugs.kde.org/show_bug.cgi?id=438909 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de --- Comment #2 from Alois Wohlschlager --- I don't see multiple negation involved here. The screen normally locks automatically, which can be prevented under 2 circumstances: * The checkbox you mentioned is checked. * An application requests it (e.g. when video is playing). Given your description, I can see 3 potential problems: * The wording and placement of the label and its behavior when the checkbox is checked can confuse users. * When an application requests to inhibit the screen lock, there is no way for the user to re-enable automatic screen locking anyway. * "I want to disable screen locking." - given this premise I think there is a different bug that actually prevents the inhibition from working. The screen should not lock in any case while the video is playing. -- You are receiving this mail because: You are watching all bug changes.
[plasma-disks] [Bug 438732] New: There should be a way to dismiss error log entries
https://bugs.kde.org/show_bug.cgi?id=438732 Bug ID: 438732 Summary: There should be a way to dismiss error log entries Product: plasma-disks Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: alo...@gmx-topmail.de CC: sit...@kde.org Target Milestone: --- SUMMARY Since the update to 5.22, plasma-disks can read the SMART error log of disks, and display a warning about disk instability in case of error entries. Some hard disks are shipped with not all unreliable sectors detected in the factory, leading to uncorrectable errors on first access which show up in the error log. This leaves the user with two options: 1. Keep seeing a notification that a disk is unstable at every login. 2. Exempt plasma-disks from watching that disk, suppressing further errors as well. Both options are bad, because they do not enable the user to distinguish between the status quo on the (still perfectly fine) disk, and the disk actually beginning to fail later. A functionality should be added that allows a user to dismiss error log entries. Then, only when further errors are logged or SMART health indicators begin to fail, the warning should be displayed again. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436367] kwin_wayland crashes occasionally when enabling monitor
https://bugs.kde.org/show_bug.cgi?id=436367 Alois Wohlschlager changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Alois Wohlschlager --- I have not been able to reproduce the bug any more on 5.22, so I assume it is fixed. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 438716] New: Lid close leads to suspend even when external monitor is attached
https://bugs.kde.org/show_bug.cgi?id=438716 Bug ID: 438716 Summary: Lid close leads to suspend even when external monitor is attached Product: Powerdevil Version: 5.22.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: alo...@gmx-topmail.de Target Milestone: --- SUMMARY Since the upgrade to 5.22, when I have an external monitor attached and close the laptop lid, the machine suspends despite the setting "even when an external screen is connected" being unchecked. I have not observed this behavior with 5.21. STEPS TO REPRODUCE 1. Connect external monitor to laptop 2. Close lid OBSERVED RESULT Machine suspends immediately EXPECTED RESULT Machine keeps running SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438626] New: Killing malfunctions in tree mode
https://bugs.kde.org/show_bug.cgi?id=438626 Bug ID: 438626 Summary: Killing malfunctions in tree mode Product: plasma-systemmonitor Version: 5.22.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: alo...@gmx-topmail.de CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY When invoking the "end process" function in tree mode, the system monitor wants to kill a different process from the selected one. STEPS TO REPRODUCE 1. Open system monitor (process page) 2. Ensure tree mode is active 3. Select a process and try to kill it (with Del key, context menu or End Process button) OBSERVED RESULT System monitor displays a dialog which shows it wants to kill a different process (usually systemd or kthreadd). When confirming this window, it actually attempts to send SIGTERM to the wrong process (which obviously fails). Sometimes, it does not display a process name, and displays "PID %1, User %2". No SIGTERM is sent in that case. I believe this is a symptom of the same underlying issue. EXPECTED RESULT System monitor displays the correct process in the confirmation dialog, and SIGTERM goes to the intended process. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION The kill functionality seems to work fine in list mode. The bug also happens on git master. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436528] kwin_wayland crashes when starting full-screen recording with OBS
https://bugs.kde.org/show_bug.cgi?id=436528 Alois Wohlschlager changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Alois Wohlschlager --- Seems like one of the fixes that went into 5.22 applies here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438075] clicking on a running program in icons-only task manager widget doesn't do anything if the program has two windows open
https://bugs.kde.org/show_bug.cgi?id=438075 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Alois Wohlschlager --- This issue should already be fixed in 5.22. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437925] Crash or hang when either opening or closing a VirtualBox VM
https://bugs.kde.org/show_bug.cgi?id=437925 Alois Wohlschlager changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO CC||alo...@gmx-topmail.de --- Comment #2 from Alois Wohlschlager --- Please use coredumpctl to fetch a backtrace of the kwin_wayland crash when you open or close the VM. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 437448] Alignment issues in tables
https://bugs.kde.org/show_bug.cgi?id=437448 --- Comment #3 from Alois Wohlschlager --- While centering everything may look a bit cleaner, there are downsides as well. When numerical values are right-aligned, it is very easily visible which number is bigger (and in fact most proportional fonts still have equal-width digits to support this). In the context of the system monitor, I can easily spot the memory hogs. Centering (or left-alignment) makes this harder. Maybe this is not as relevant for PID (which is just an identifier and not a size indicator) or CPU (as it is very short). For the command column, some programs (e.g. postgres) have whitespace padding at the end of their command lines, so centering does not really work anyway. With username, centering is probably not too bad. In general, I think it is a common expectation (from other system monitors, spreadsheet applications or the real world) that English text is left-aligned and numbers are right-aligned. When this expectation is broken, there should be a compelling benefit. Finally, I don't think centering everything even solves huge whitespace gaps, at least not as much as a reasonable column width and column order do. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.
https://bugs.kde.org/show_bug.cgi?id=316734 Alois Wohlschlager changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 437450] New: Line chart not working in tree mode
https://bugs.kde.org/show_bug.cgi?id=437450 Bug ID: 437450 Summary: Line chart not working in tree mode Product: plasma-systemmonitor Version: 5.21.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: alo...@gmx-topmail.de CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY When the process table is set to tree mode, line charts only display text. STEPS TO REPRODUCE 1. Open process page 2. Ensure CPU usage is set to line chart mode (does not matter if normalized) 3. Ensure tree mode is active OBSERVED RESULT Only text in CPU column. EXPECTED RESULT Line chart in addition to text in CPU column, like in list mode. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Also happens on git master. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 437449] New: Sorting order not applied on start in some cases
https://bugs.kde.org/show_bug.cgi?id=437449 Bug ID: 437449 Summary: Sorting order not applied on start in some cases Product: plasma-systemmonitor Version: 5.21.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: alo...@gmx-topmail.de CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY In some cases, when starting plasma-systemmonitor, the remembered sorting order in the process table is not applied correctly. STEPS TO REPRODUCE 1. Sort process table by PID 2. Close system monitor 3. Reopen system monitor OBSERVED RESULT Processes are displayed in random order, while sorting indicator appears on "PID" column EXPECTED RESULT Processes are sorted by PID SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Similar behavior is observed when sorting by username. Also happens on git master. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 437448] New: Alignment issues in tables
https://bugs.kde.org/show_bug.cgi?id=437448 Bug ID: 437448 Summary: Alignment issues in tables Product: plasma-systemmonitor Version: 5.21.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: alo...@gmx-topmail.de CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY Currently, everything in the tables (processes and applications) is centered except for the first column. Numeric values in tables should be right-aligned, text should be left-aligned. STEPS TO REPRODUCE 1. Open system monitor 2. Switch to processes page 3. Ensure that one numeric column (e.g. "Memory" or "PID") and one text column (e.g. "Username" or "Command") are enabled OBSERVED RESULT In both columns, the text is centered. EXPECTED RESULT In the numeric column, text should be right-aligned. In the text column, text should be left-aligned. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Also happens on git master -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 437012] LSP function autocompletion gets in the way for Haskell
https://bugs.kde.org/show_bug.cgi?id=437012 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de --- Comment #1 from Alois Wohlschlager --- Can't reproduce this with the OCaml language server. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437082] gtk3 csd apps do not respect third-party window decoration theme on Wayland
https://bugs.kde.org/show_bug.cgi?id=437082 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Alois Wohlschlager --- This issue is due to GTK ignoring the gtk-modules directive in settings.ini when running on Wayland. Unfortunately, bugs like [1] need to be sorted out before. [1] https://bugs.kde.org/show_bug.cgi?id=428322 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.
https://bugs.kde.org/show_bug.cgi?id=316734 --- Comment #27 from Alois Wohlschlager --- For me it is the opposite behavior. With GPU rendering, I cannot reproduce the bug reliably. Sometimes I see the session content before the lockscreen appears, sometimes I see a black screen with mouse cursor. In software rendering mode, the session is always visible briefly. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 436914] (Re-)attaching tabs does not work on Wayland
https://bugs.kde.org/show_bug.cgi?id=436914 Alois Wohlschlager changed: What|Removed |Added Summary|Allow (re-)attaching tabs |(Re-)attaching tabs does ||not work on Wayland --- Comment #3 from Alois Wohlschlager --- I found the culprit now. The feature is broken on Wayland. On X, including when running Konsole through Xwayland, it works as expected. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 436914] Allow (re-)attaching tabs
https://bugs.kde.org/show_bug.cgi?id=436914 Alois Wohlschlager changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Alois Wohlschlager --- It does not work regardless of the single process mode setting. Note that in both scenarios I described, all Konsole windows run in a common process anyway. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 436914] New: Allow (re-)attaching tabs
https://bugs.kde.org/show_bug.cgi?id=436914 Bug ID: 436914 Summary: Allow (re-)attaching tabs Product: konsole Version: 21.04.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: alo...@gmx-topmail.de Target Milestone: --- SUMMARY Konsole already has a feature where tabs can be detached into a new window by dragging a tab outside the current window. It would be nice if tabs could be moved between open Konsole windows in a similar way, by dropping them onto the tab bar. STEPS TO REPRODUCE (Scenario 1) 1. Open Konsole 2. Create a second window 3. Try to drag the tab of the second window onto the tab bar of the first window OBSERVED RESULT No drag-and-drop operation started EXPECTED RESULT Tab is attached to the first window, second window is closed STEPS TO REPRODUCE (Scenario 2) 1. Open Konsole 2. Create a second tab 3. Create a second window 4. Try to drag one tab of the first window onto the tab bar of the second window OBSERVED RESULT Tab is detached into a third window EXPECTED RESULT Tab is moved to the second window SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436907] [Wayland] clicking on task manager icon to bring windows to the front doesn't work
https://bugs.kde.org/show_bug.cgi?id=436907 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Alois Wohlschlager --- Same behavior happens on openSUSE Tumbleweed, also on Wayland only. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436700] Plasma crashed after lock screen using xWayland
https://bugs.kde.org/show_bug.cgi?id=436700 --- Comment #9 from Alois Wohlschlager --- You almost got it, but you missed two things: * You need to use "coredumpctl" with the PID of the crash *after* you have made the modification to the config file. * You forgot to enter "bt" into the gdb prompt. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436835] Closing session and relogging causes black screen
https://bugs.kde.org/show_bug.cgi?id=436835 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de --- Comment #1 from Alois Wohlschlager --- Are you using systemd startup? If so, the issue might already be fixed by https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/773 . -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.
https://bugs.kde.org/show_bug.cgi?id=316734 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de --- Comment #24 from Alois Wohlschlager --- Could the issue described in comment 6 be worked around by blocking the suspend util two (or maybe even three) frames of the lockscreen have been rendered? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.
https://bugs.kde.org/show_bug.cgi?id=316734 Alois Wohlschlager changed: What|Removed |Added CC||icohen2...@zoho.com --- Comment #23 from Alois Wohlschlager --- *** Bug 436751 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436751] Screen shows before lockscreen on resuming from sleep
https://bugs.kde.org/show_bug.cgi?id=436751 Alois Wohlschlager changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||alo...@gmx-topmail.de --- Comment #1 from Alois Wohlschlager --- *** This bug has been marked as a duplicate of bug 316734 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436700] Plasma crashed after lock screen using xWayland
https://bugs.kde.org/show_bug.cgi?id=436700 --- Comment #7 from Alois Wohlschlager --- I'm sorry, you don't have a useful coredump because I forgot to mention one step. Please edit the file /etc/systemd/coredump.conf the following way: * Find a line like "#ExternalSizeMax=2G". * Replace it with "ExternalSizeMax=6G" (do not include the quote signs). After that, try to make it crash again. Then, run "coredumpctl" again and note the PID column of kwin_wayland (it was 3247 in your example). Run "coredumpctl debug PID" where you replace PID with that number. Then enter "bt" when the GDB prompt appears and copy the backtrace that appears. -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 436864] New: Grayscale antialiasing in apps using KDE Platform
https://bugs.kde.org/show_bug.cgi?id=436864 Bug ID: 436864 Summary: Grayscale antialiasing in apps using KDE Platform Product: Qt/KDE Flatpak Runtime Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: alo...@gmx-topmail.de CC: aa...@kde.org Target Milestone: --- SUMMARY Flatpaks using the KDE platform only use greyscale antialiasing. STEPS TO REPRODUCE 1. Install flatpak app using the KDE platform (I tried with OBS from flathub and Massif-Visualizer from kdeapps) 2. Launch the app OBSERVED RESULT All font rendering in the app uses grayscale antialiasing EXPECTED RESULT Fonts are rendered properly, including RGB antialiasing SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.5 (host) KDE Frameworks Version: 5.81.0 (host and sandbox) Qt Version: 5.15.2 (host), "5.15.3" (sandbox) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436641] I can't move or maximize the native wayland error window and wayland windows are buggy in general
https://bugs.kde.org/show_bug.cgi?id=436641 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de --- Comment #2 from Alois Wohlschlager --- That window seems to be not maximizable by design, and the "maximize" option in the window menu is greyed out. I think the maximize button in the titlebar should be hidden in this situation. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436700] Plasma crashed after lock screen using xWayland
https://bugs.kde.org/show_bug.cgi?id=436700 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO --- Comment #5 from Alois Wohlschlager --- Looks like a KWin crash. You can check this by installing systemd-coredump and reproducing the crash. Then, coredumpctl can be used to fetch a backtrace of kwin_wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435690] [Wayland] Kickoff, Krunner, and other applets open in the wrong place
https://bugs.kde.org/show_bug.cgi?id=435690 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 436559] GTK3 CSD buttons are noticeably smaller than regular Breeze Qt style
https://bugs.kde.org/show_bug.cgi?id=436559 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de --- Comment #10 from Alois Wohlschlager --- (In reply to Nate Graham from comment #5) > Now that I see the issue in your screenshots, it magically becomes obvious > to me on my system too. Confirmed. > > Maybe you can try your hand at submitting a merge request at > https://invent.kde.org/plasma/breeze-gtk/-/merge_requests/? This should be implemented in kde-gtk-config, not in breeze-gtk. The current size (18px) is fine for the buttons breeze-gtk ships, but not for the ones kde-gtk-config generates. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436303] Qt and XWayland apps don't respect cursor settings on Wayland
https://bugs.kde.org/show_bug.cgi?id=436303
Alois Wohlschlager changed:
What|Removed |Added
Status|NEEDSINFO |CONFIRMED
Resolution|WAITINGFORINFO |---
--- Comment #11 from Alois Wohlschlager ---
env output:
SHELL=/bin/bash
CAML_LD_LIBRARY_PATH=/home/alois/.local/share/opam/4.11.1/lib/stublibs:/home/alois/.local/share/opam/4.11.1/lib64/stublibs:/home/alois/.local/share/opam/4.11.1/lib64
WINDOWID=1
OCAML_TOPLEVEL_PATH=/home/alois/.local/share/opam/4.11.1/lib/toplevel
COLORTERM=truecolor
SDK_HOME=/usr/lib64/jvm/java
XDG_CONFIG_DIRS=/etc/xdg:/usr/etc/xdg
LESS=-M -I -R
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session1
JDK_HOME=/usr/lib64/jvm/java
GTK_IM_MODULE=fcitx
MACHTYPE=x86_64-suse-linux
G_BROKEN_FILENAMES=1
HOSTNAME=genesis
HISTSIZE=1000
LANGUAGE=de:en_US
FROM_HEADER=
MINICOM=-c on
TEXMFHOME=/home/alois/.local/share/texmf
JAVA_ROOT=/usr/lib64/jvm/java
JAVA_HOME=/usr/lib64/jvm/java
JRE_HOME=/usr/lib64/jvm/java
INPUT_METHOD=fcitx
CPU=x86_64
SHELL_SESSION_ID=e68ee2a7b324453782cf42a09f8a136e
JAVA_BINDIR=/usr/lib64/jvm/java/bin
XMODIFIERS=@im=fcitx
DESKTOP_SESSION=/usr/share/wayland-sessions/plasmafullwayland
XCURSOR_SIZE=24
GPG_TTY=/dev/pts/4
EDITOR=/usr/bin/nvim
XDG_SEAT=seat0
PWD=/home/alois
XDG_SESSION_DESKTOP=KDE
LOGNAME=alois
XDG_SESSION_TYPE=wayland
CCACHE_DIR=/home/alois/.cache/ccache
MANPATH=/usr/local/man:/usr/local/share/man:/usr/share/man:/home/alois/.local/share/opam/4.11.1/man
STACK_ROOT=/home/alois/.local/share/stack
XAUTHORITY=/run/user/1000/xauth_IvMsSG
LS_OPTIONS=-N --color=tty -T 0
OPAM_SWITCH_PREFIX=/home/alois/.local/share/opam/4.11.1
XKEYSYMDB=/usr/X11R6/lib/X11/XKeysymDB
XKB_DEFAULT_MODEL=microsoftpro
GTK2_RC_FILES=/home/alois/.config/gtk-2.0/gtkrc
XNLSPATH=/usr/share/X11/nls
HOME=/home/alois
LANG=de_DE.UTF-8
LS_COLORS=no=00:fi=00:di=01;34:ln=00;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=41;33;01:ex=00;32:*.cmd=00;32:*.exe=01;32:*.com=01;32:*.bat=01;32:*.btm=01;32:*.dll=01;32:*.tar=00;31:*.tbz=00;31:*.tgz=00;31:*.rpm=00;31:*.deb=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.lzma=00;31:*.zip=00;31:*.zoo=00;31:*.z=00;31:*.Z=00;31:*.gz=00;31:*.bz2=00;31:*.tb2=00;31:*.tz2=00;31:*.tbz2=00;31:*.xz=00;31:*.avi=01;35:*.bmp=01;35:*.dl=01;35:*.fli=01;35:*.gif=01;35:*.gl=01;35:*.jpg=01;35:*.jpeg=01;35:*.mkv=01;35:*.mng=01;35:*.mov=01;35:*.mp4=01;35:*.mpg=01;35:*.pcx=01;35:*.pbm=01;35:*.pgm=01;35:*.png=01;35:*.ppm=01;35:*.svg=01;35:*.tga=01;35:*.tif=01;35:*.webm=01;35:*.webp=01;35:*.wmv=01;35:*.xbm=01;35:*.xcf=01;35:*.xpm=01;35:*.aiff=00;32:*.ape=00;32:*.au=00;32:*.flac=00;32:*.m4a=00;32:*.mid=00;32:*.mp3=00;32:*.mpc=00;32:*.ogg=00;32:*.voc=00;32:*.wav=00;32:*.wma=00;32:*.wv=00;32:
XDG_CURRENT_DESKTOP=KDE
CARGO_HOME=/home/alois/.local/share/cargo
KONSOLE_DBUS_SERVICE=:1.161
PYTHONSTARTUP=/etc/pythonstart
WAYLAND_DISPLAY=wayland-0
KONSOLE_DBUS_SESSION=/Sessions/1
PROFILEHOME=
OSTYPE=linux
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
LESS_ADVANCED_PREPROCESSOR=no
INVOCATION_ID=7e2ced5a982f4539b883ed48e50ad295
KONSOLE_VERSION=210400
MANAGERPID=13980
QT_QPA_PLATFORM=wayland
KDE_SESSION_UID=1000
XKB_DEFAULT_LAYOUT=de
GRADLE_USER_HOME=/home/alois/.local/share/gradle
LESSCLOSE=lessclose.sh %s %s
XDG_SESSION_CLASS=user
TERM=xterm-256color
G_FILENAME_ENCODING=@locale,UTF-8,ISO-8859-15,CP1252
HOST=genesis
RUSTUP_HOME=/home/alois/.local/share/rustup
XAUTHLOCALHOSTNAME=genesis
LESSOPEN=lessopen.sh %s
USER=alois
COLORFGBG=15;0
PLASMA_USE_QT_SCALING=1
KDE_SESSION_VERSION=5
PAM_KWALLET5_LOGIN=/run/user/1000/kwallet5.socket
MORE=-sl
NPM_CONFIG_USERCONFIG=/home/alois/.config/npm/npmrc
QT_WAYLAND_FORCE_DPI=96
PIPEWIRE_LATENCY=128/48000
CSHEDIT=emacs
DISPLAY=:1
RUSTC_WRAPPER=sccache
SHLVL=1
WINDOWMANAGER=/usr/bin/startplasma-x11
PAGER=less
QT_IM_MODULE=fcitx
CVS_RSH=ssh
XDG_VTNR=2
XDG_SESSION_ID=2
LD_LIBRARY_PATH=/usr/${LIB}/pipewire-0.3/jack
LC_CTYPE=de_DE.UTF-8
XDG_RUNTIME_DIR=/run/user/1000
DEBUGINFOD_URLS=https://debuginfod.opensuse.org/
XKB_DEFAULT_VARIANT=neo
QT_AUTO_SCREEN_SCALE_FACTOR=0
JOURNAL_STREAM=8:57377
XCURSOR_THEME=breeze_cursors
GTK3_MODULES=window-decorations-gtk-module:colorreload-gtk-module
XDG_DATA_DIRS=/home/alois/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
KDE_FULL_SESSION=true
GDK_BACKEND=wayland
CONFIG_SITE=/usr/share/site/x86_64-unknown-linux-gnu
PATH=/home/alois/kde/src/kdesrc-build:/home/alois/.local/share/opam/4.11.1/bin:/usr/lib64/ccache:/home/alois/kde/src/kdesrc-build:/usr/local/bin:/usr/bin:/bin:/home/alois/.local/bin:/home/alois/.local/share/cargo/bin:/home/alois/.local/share/go/bin:/home/alois/.local/share/npm/bin:/home/alois/.local/share/hacky-debug-tools/bin
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
PROFILEREAD=true
OPAMNOENVNOTICE=true
KDE_APPLICATIONS_AS_SCOPE=1
MAIL=/var/spool/mail/alois
HOSTTYPE=x86_64
OPAMROOT=/home
[kwin] [Bug 436520] Crash at computer wakeup
https://bugs.kde.org/show_bug.cgi?id=436520 Alois Wohlschlager changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO CC||alo...@gmx-topmail.de --- Comment #1 from Alois Wohlschlager --- The Konsole crash is known in this situation. Please provide the backtrace of kwin_wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436528] New: kwin_wayland crashes when starting full-screen recording with OBS
https://bugs.kde.org/show_bug.cgi?id=436528 Bug ID: 436528 Summary: kwin_wayland crashes when starting full-screen recording with OBS Product: kwin Version: 5.21.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: alo...@gmx-topmail.de Target Milestone: --- SUMMARY When attempting to start screen recording with OBS in full-screen mode, kwin_wayland aborts. STEPS TO REPRODUCE 1. Install OBS Studio from Flathub 2. QT_QPA_PLATFORM=xcb flatpak run com.obsproject.Studio 3. Add "Desktop Screencast (X11/Wayland)" source 4. Select monitor in the window that appears OBSERVED RESULT kwin_wayland aborts. EXPECTED RESULT kwin_wayland keeps running and the recording can be started. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Backtrace: #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #1 0x7fd05b4ef914 in __GI_abort () at abort.c:100 #2 0x7fd05b9d71e5 in gl_provider_resolver (name=0x7fd05ba3aae7 "glCopyTextureSubImage2D", providers=0x7fd05ba4af40 , entrypoints=) at src/gl_generated_dispatch.c:75797 #3 0x7fd05b9df448 in epoxy_glCopyTextureSubImage2D_resolver () at src/gl_generated_dispatch.c:80848 Unfortunately, gdb hangs at that point, so here is the same backtrace without debug symbols: #0 0x7fd05b5064a5 in raise () at /lib64/libc.so.6 #1 0x7fd05b4ef914 in abort () at /lib64/libc.so.6 #2 0x7fd05b9d71e5 in () at /usr/lib64/libepoxy.so.0 #3 0x7fd05b9df448 in () at /usr/lib64/libepoxy.so.0 #4 0x55b772c8dc2b in KWin::PipeWireStream::recordFrame(KWin::GLTexture*, QRegion const&) () #5 0x55b772c8df44 in () #6 0x7fd05cfd1c17 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fd05ca47f85 in KWin::AbstractWaylandOutput::outputChange(QRegion const&) () at /usr/lib64/libkwin.so.5 #8 0x7fd0a508 in () at /usr/lib64/qt5/plugins/org.kde.kwin.waylandbackends/KWinWaylandDrmBackend.so #9 0x7fd05554da2d in () at /usr/lib64/qt5/plugins/org.kde.kwin.waylandbackends/KWinWaylandDrmBackend.so #10 0x7fd0543d1490 in KWin::SceneOpenGL::paint(int, QRegion const&, QList const&, KWin::RenderLoop*) () at /usr/lib64/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #11 0x7fd05ca923de in KWin::Compositor::handleFrameRequested(KWin::RenderLoop*) () at /usr/lib64/libkwin.so.5 #12 0x7fd05cfd1c17 in () at /usr/lib64/libQt5Core.so.5 #13 0x7fd05ca56e92 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*) () at /usr/lib64/libkwin.so.5 #14 0x7fd05cb1b333 in KWin::RenderLoopPrivate::dispatch() () at /usr/lib64/libkwin.so.5 #15 0x7fd05cfd1c17 in () at /usr/lib64/libQt5Core.so.5 #16 0x7fd05cfd5b9a in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib64/libQt5Core.so.5 #17 0x7fd05cfc794f in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #18 0x7fd05bfa2aff in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #19 0x7fd05cf9b13a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #20 0x7fd05cff20f3 in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5 #21 0x7fd05cff0587 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #22 0x55b772cc1c1d in () #23 0x7fd05cf99b7b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #24 0x7fd05cfa1db0 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #25 0x55b772c6552c in () #26 0x7fd05b4f0b25 in __libc_start_main () at /lib64/libc.so.6 #27 0x55b772c65b7e in _start () -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436367] New: kwin_wayland crashes occasionally when enabling monitor
https://bugs.kde.org/show_bug.cgi?id=436367 Bug ID: 436367 Summary: kwin_wayland crashes occasionally when enabling monitor Product: kwin Version: 5.21.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: alo...@gmx-topmail.de Target Milestone: --- SUMMARY I was running a Wayland session with an external monitor connected and the laptop lid closed, so the external monitor was the only output. When I opened the lid, kwin_wayland aborted. STEPS TO REPRODUCE 1. Connect external screen 2. Close lid 3. Open lid OBSERVED RESULT kwin_wayland aborts and crashes. EXPECTED RESULT kwin_wayland continues running. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I got the same crash in a slightly different situation as well [1]. There, the laptop monitor was black when I opened the lid, and the crash happened when I tried to enable the internal monitor from system settings. Backtrace: #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #1 0x7f1cac700914 in __GI_abort () at abort.c:100 #2 0x7f1cac700749 in __assert_fail_base (fmt=0x7f1ca5ee5554 "%s%s%s:%u: %s%sZusicherung »%s« nicht erfüllt.\n%n", assertion=0x7f1cacc65750 "0 && \"Couldn't find current GLX or EGL context.\\n\"", file=0x7f1cacc65829 "../src/dispatch_common.c", line=858, function=) at assert.c:92 #3 0x7f1cac70f9b6 in __GI___assert_fail (assertion=assertion@entry=0x7f1cacc65750 "0 && \"Couldn't find current GLX or EGL context.\\n\"", file=file@entry=0x7f1cacc65829 "../src/dispatch_common.c", line=line@entry=858, function=function@entry=0x7f1cacc65c80 <__PRETTY_FUNCTION__.0.lto_priv.0> "epoxy_get_proc_address") at assert.c:101 #4 0x7f1cacc41df7 in epoxy_get_proc_address (name=0x7f1cacc4c139 "glDeleteProgram") at ../src/dispatch_common.c:858 #5 0x7f1cacbf105a in epoxy_glDeleteProgram_resolver () at src/gl_generated_dispatch.c:81668 #6 epoxy_glDeleteProgram_global_rewrite_ptr (program=30) at src/gl_generated_dispatch.c:49458 #7 0x7f1ca4bcba40 in QScopedPointerDeleter::cleanup(KWin::GLShader*) (pointer=0x564d95405b40) at /usr/include/qt5/QtCore/qscopedpointer.h:52 #8 QScopedPointerDeleter::cleanup(KWin::GLShader*) (pointer=0x564d95405b40) at /usr/include/qt5/QtCore/qscopedpointer.h:52 #9 QScopedPointer >::~QScopedPointer() (this=0x564d953d0838, this=) at /usr/include/qt5/QtCore/qscopedpointer.h:107 #10 KWin::LanczosFilter::~LanczosFilter() (this=0x564d953d0810, this=) at /usr/src/debug/kwin5-5.21.4-1.2.x86_64/plugins/scenes/opengl/lanczosfilter.cpp:47 #11 0x7f1ca4bd6cd0 in KWin::LanczosFilter::~LanczosFilter() (this=0x564d953d0810, this=) at /usr/src/debug/kwin5-5.21.4-1.2.x86_64/plugins/scenes/opengl/lanczosfilter.cpp:47 #12 operator() (__closure=0x564d951c8ee0) at /usr/src/debug/kwin5-5.21.4-1.2.x86_64/plugins/scenes/opengl/scene_opengl.cpp:1042 #13 QtPrivate::FunctorCall, QtPrivate::List<>, void, KWin::SceneOpenGL2::performPaintWindow(KWin::EffectWindowImpl*, int, const QRegion&, KWin::WindowPaintData&):: >::call (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #14 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #15 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x564d951c8ed0, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #16 0x7f1cae1e2c17 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffca5e27b50, r=0x564d9432c0a0, this=0x564d951c8ed0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #17 doActivate(QObject*, int, void**) (sender=0x564d93d79c10, signal_index=4, argv=0x7ffca5e27b50) at kernel/qobject.cpp:3886 #18 0x7f1cae1e2c17 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffca5e27c30, r=0x564d93d79c10, this=0x564d93d67840) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #19 doActivate(QObject*, int, void**) (sender=0x564d93c57360, signal_index=3, argv=0x7ffca5e27c30, argv@entry=0x0) at kernel/qobject.cpp:3886 #20 0x7f1cae1dbf60 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x564d93c57360, m=m@entry=0x7f1cadebe100, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #21 0x7f1cadc67a30 in KWin::Platform::screensQueried() (this=this@entry=0x564d93c57360) at /usr/src/debug/kwin5-5.21.4-1.2.x86_64/build/kwin_autogen/EWIEGA46WW/moc_platform.cpp:359 #22 0x7f1ca6752242 in
[systemsettings] [Bug 436303] Qt and XWayland apps don't respect cursor settings on Wayland
https://bugs.kde.org/show_bug.cgi?id=436303 Alois Wohlschlager changed: What|Removed |Added Summary|GTK apps don't respect |Qt and XWayland apps don't |cursor settings on Wayland |respect cursor settings on ||Wayland --- Comment #7 from Alois Wohlschlager --- Nate, this is the opposite bug. Gtk apps do respect the custom setting, while Qt and XWayland apps continue to use Breeze. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436303] Some applications don't respect cursor settings
https://bugs.kde.org/show_bug.cgi?id=436303 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de --- Comment #3 from Alois Wohlschlager --- I can reproduce this, the cursor is Breeze over Qt and XWayland apps, and Adwaita over titlebars and Gtk apps. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397825] [Wayland] Message viewer displays only a black rectangle
https://bugs.kde.org/show_bug.cgi?id=397825 --- Comment #33 from Alois Wohlschlager --- I cannot reproduce the bug on 21.04 any more either. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428268] kwin_wayland crashes when pipewire stopped
https://bugs.kde.org/show_bug.cgi?id=428268 --- Comment #14 from Alois Wohlschlager --- As indicated in the "Version Fixed In" field, the fix will be included 5.22. In addition, it was backported to be part of 5.21.5. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436095] crash on display sleep (maybe disconnect?)
https://bugs.kde.org/show_bug.cgi?id=436095 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de --- Comment #3 from Alois Wohlschlager --- Looks like the crash supposedly fixed in commit 618c330ca80d525ff76c17cc4568ba5675fe, was that fix incomplete? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435941] Crash on sleep
https://bugs.kde.org/show_bug.cgi?id=435941 --- Comment #3 from Alois Wohlschlager --- Unlikely that this is an amdgpu problem, I have an Intel GPU. Unfortunately, I don't have a dmesg available since I have turned the machine off by now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435941] Crash on sleep
https://bugs.kde.org/show_bug.cgi?id=435941 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de --- Comment #1 from Alois Wohlschlager --- Seems related to the crash I got today after enabling a monitor. I'm using openSUSE Tumbleweed with Plasma 5.21.4 and Wayland. #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #1 0x7f119c2d3914 in __GI_abort () at abort.c:100 #2 0x7f119c2d3749 in __assert_fail_base (fmt=0x7f1195ac6554 "%s%s%s:%u: %s%sZusicherung »%s« nicht erfüllt.\n%n", assertion=0x7f119c835750 "0 && \"Couldn't find current GLX or EGL context.\\n\"", file=0x7f119c835829 "../src/dispatch_common.c", line=858, function=) at assert.c:92 #3 0x7f119c2e29b6 in __GI___assert_fail (assertion=assertion@entry=0x7f119c835750 "0 && \"Couldn't find current GLX or EGL context.\\n\"", file=file@entry=0x7f119c835829 "../src/dispatch_common.c", line=line@entry=858, function=function@entry=0x7f119c835c80 <__PRETTY_FUNCTION__.0.lto_priv.0> "epoxy_get_proc_address") at assert.c:101 #4 0x7f119c811df7 in epoxy_get_proc_address (name=0x7f119c81c139 "glDeleteProgram") at ../src/dispatch_common.c:858 #5 0x7f119c7c105a in epoxy_glDeleteProgram_resolver () at src/gl_generated_dispatch.c:81668 #6 epoxy_glDeleteProgram_global_rewrite_ptr (program=31) at src/gl_generated_dispatch.c:49458 #7 0x7f11947aca30 in QScopedPointerDeleter::cleanup(KWin::GLShader*) (pointer=0x5601a20850d0) at /usr/include/qt5/QtCore/qscopedpointer.h:52 #8 QScopedPointerDeleter::cleanup(KWin::GLShader*) (pointer=0x5601a20850d0) at /usr/include/qt5/QtCore/qscopedpointer.h:52 #9 QScopedPointer >::~QScopedPointer() (this=0x5601a2182fe8, this=) at /usr/include/qt5/QtCore/qscopedpointer.h:107 #10 KWin::LanczosFilter::~LanczosFilter() (this=0x5601a2182fc0, this=) at /usr/src/debug/kwin5-5.21.4-1.1.x86_64/plugins/scenes/opengl/lanczosfilter.cpp:47 #11 0x7f11947b7cc0 in KWin::LanczosFilter::~LanczosFilter() (this=0x5601a2182fc0, this=) at /usr/src/debug/kwin5-5.21.4-1.1.x86_64/plugins/scenes/opengl/lanczosfilter.cpp:47 #12 operator() (__closure=0x5601a1ccd220) at /usr/src/debug/kwin5-5.21.4-1.1.x86_64/plugins/scenes/opengl/scene_opengl.cpp:1042 #13 QtPrivate::FunctorCall, QtPrivate::List<>, void, KWin::SceneOpenGL2::performPaintWindow(KWin::EffectWindowImpl*, int, const QRegion&, KWin::WindowPaintData&):: >::call (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #14 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #15 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x5601a1ccd210, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #16 0x7f119ddb2c17 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffbe025f00, r=0x5601a0e7c770, this=0x5601a1ccd210) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #17 doActivate(QObject*, int, void**) (sender=0x5601a0b99820, signal_index=4, argv=0x7fffbe025f00) at kernel/qobject.cpp:3886 #18 0x7f119ddb2c17 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffbe025fe0, r=0x5601a0b99820, this=0x5601a0baaff0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #19 doActivate(QObject*, int, void**) (sender=0x5601a0a55f60, signal_index=3, argv=0x7fffbe025fe0, argv@entry=0x0) at kernel/qobject.cpp:3886 #20 0x7f119ddabf60 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x5601a0a55f60, m=m@entry=0x7f119da8e100, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #21 0x7f119d838a30 in KWin::Platform::screensQueried() (this=this@entry=0x5601a0a55f60) at /usr/src/debug/kwin5-5.21.4-1.1.x86_64/build/kwin_autogen/EWIEGA46WW/moc_platform.cpp:359 #22 0x7f1196333232 in KWin::DrmBackend::enableOutput(KWin::DrmOutput*, bool) (this=0x5601a0a55f60, output=, enable=) at /usr/src/debug/kwin5-5.21.4-1.1.x86_64/plugins/platforms/drm/drm_backend.cpp:521 #23 0x7f119634275c in KWin::DrmOutput::atomicEnable() (this=) at /usr/src/debug/kwin5-5.21.4-1.1.x86_64/plugins/platforms/drm/drm_output.cpp:488 #24 0x7f119d8f39f0 in KWin::Platform::requestOutputsChange(KWaylandServer::OutputConfigurationInterface*) (this=0x5601a0a55f60, config=0x5601a2c5f060) at /usr/src/debug/kwin5-5.21.4-1.1.x86_64/platform.cpp:135 #25 0x7f119ddb2c17 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffbe026240, r=0x5601a0a3b7e0, this=0x5601a0a6e3b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl
[systemsettings] [Bug 435733] sys settings crashed upon open
https://bugs.kde.org/show_bug.cgi?id=435733 Alois Wohlschlager changed: What|Removed |Added CC||j...@joetech.com --- Comment #5 from Alois Wohlschlager --- *** Bug 435817 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435817] System Settings crashes upon open
https://bugs.kde.org/show_bug.cgi?id=435817 Alois Wohlschlager changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||alo...@gmx-topmail.de --- Comment #1 from Alois Wohlschlager --- *** This bug has been marked as a duplicate of bug 435733 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398440] plasmashell crashes on wayland in DeclarativeMimeData::DeclarativeMimeData() when dragging a file from dolphin over a panel
https://bugs.kde.org/show_bug.cgi?id=398440 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de --- Comment #42 from Alois Wohlschlager --- I got an interesting variant of the backtrace today, pasting it here: #0 __GI___pthread_sigmask (how=how@entry=1, newmask=, newmask@entry=0x7ffe050704d0, oldmask=oldmask@entry=0x0) at pthread_sigmask.c:44 #1 0x7f313694b76d in __GI___sigprocmask (how=how@entry=1, set=set@entry=0x7ffe050704d0, oset=oset@entry=0x0) at ../sysdeps/unix/sysv/linux/sigprocmask.c:25 #2 0x7f3138392feb in KCrash::setCrashHandler(void (*)(int)) (handler=handler@entry=0x0) at /usr/src/debug/kcrash-5.80.0-1.1.x86_64/src/kcrash.cpp:379 #3 0x7f3138394e8a in KCrash::defaultCrashHandler(int) (sig=11) at /usr/src/debug/kcrash-5.80.0-1.1.x86_64/src/kcrash.cpp:575 #4 0x7f313694b530 in () at /lib64/libc.so.6 #5 DeclarativeMimeData::DeclarativeMimeData(QMimeData const*) (this=0x55b90fd7f7b0, copy=0x55b912b99a70, this=, copy=) at /usr/src/debug/kdeclarative-5.80.0-1.1.x86_64/src/qmlcontrols/draganddrop/DeclarativeMimeData.cpp:40 #6 0x7f3114509081 in DeclarativeDragDropEvent::mimeData() (this=0x7ffe05072c20) at /usr/src/debug/kdeclarative-5.80.0-1.1.x86_64/src/qmlcontrols/draganddrop/DeclarativeDragDropEvent.cpp:52 #7 DeclarativeDragDropEvent::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_a=, _id=, _c=, _o=0x7ffe05072c20) at /usr/src/debug/kdeclarative-5.80.0-1.1.x86_64/build/src/qmlcontrols/draganddrop/draganddropplugin_autogen/EWIEGA46WW/moc_DeclarativeDragDropEvent.cpp:121 #8 DeclarativeDragDropEvent::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x7ffe05072c20, _c=, _id=, _a=) at /usr/src/debug/kdeclarative-5.80.0-1.1.x86_64/build/src/qmlcontrols/draganddrop/draganddropplugin_autogen/EWIEGA46WW/moc_DeclarativeDragDropEvent.cpp:93 #9 0x7f3138545071 in QQmlPropertyData::readPropertyWithArgs(QObject*, void**) const (args=0x7ffe05070e90, target=0x7ffe05072c20, this=0x55b913501508) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-3.1.x86_64/include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/qml/qqmlpropertydata_p.h:363 #10 QQmlPropertyData::readProperty(QObject*, void*) const (property=0x7ffe05070e70, target=0x7ffe05072c20, this=0x55b913501508) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-3.1.x86_64/include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/qml/qqmlpropertydata_p.h:357 #11 loadProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData const&) (v4=0x55b90d45cf60, object=0x7ffe05072c20, property=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-3.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:138 #12 0x7f30f095a944 in () #13 0x in () I think #0-#4 can be explained by KCrash interfering, but the corruption starting at #12 might be relevant. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435760] Plasma Shell crashes during heavy HDD utilisation
https://bugs.kde.org/show_bug.cgi?id=435760 Alois Wohlschlager changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED CC||alo...@gmx-topmail.de --- Comment #2 from Alois Wohlschlager --- This is Qt aborting because the Wayland connection breaks, here because one end takes too long to respond. It is being worked on in Qt. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397825] [Wayland] Message viewer displays only a black rectangle
https://bugs.kde.org/show_bug.cgi?id=397825 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435713] KWin crashes after window manipulation
https://bugs.kde.org/show_bug.cgi?id=435713 Alois Wohlschlager changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||alo...@gmx-topmail.de --- Comment #1 from Alois Wohlschlager --- *** This bug has been marked as a duplicate of bug 428149 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428149] exit full screen
https://bugs.kde.org/show_bug.cgi?id=428149 Alois Wohlschlager changed: What|Removed |Added CC||va...@sincore.ru --- Comment #6 from Alois Wohlschlager --- *** Bug 435713 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428268] kwin_wayland crashes when pipewire stopped
https://bugs.kde.org/show_bug.cgi?id=428268 Alois Wohlschlager changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/59f6b77612d3 ||e80fa579064ebdcccfd2127158c ||9 Resolution|--- |FIXED --- Comment #11 from Alois Wohlschlager --- Git commit 59f6b77612d3e80fa579064ebdcccfd2127158c9 by Alois Wohlschlager. Committed on 13/04/2021 at 08:28. Pushed by davidedmundson into branch 'master'. Fix crash when stopping PipeWire streaming The stream object was deleted from a slot connected to its stopStreaming signal. This is unsafe and can lead to memory corruption and ultimately crashes when PipWwire streaming is stopped. Use deleteLater instead. Related: bug 435588 M +1-1src/plugins/screencast/screencastmanager.cpp https://invent.kde.org/plasma/kwin/commit/59f6b77612d3e80fa579064ebdcccfd2127158c9 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435588] kwin_wayland crashed while I was hovering over previews of Konsoles grouped in task manager
https://bugs.kde.org/show_bug.cgi?id=435588 Alois Wohlschlager changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/59f6b77612d3 ||e80fa579064ebdcccfd2127158c ||9 --- Comment #3 from Alois Wohlschlager --- Git commit 59f6b77612d3e80fa579064ebdcccfd2127158c9 by Alois Wohlschlager. Committed on 13/04/2021 at 08:28. Pushed by davidedmundson into branch 'master'. Fix crash when stopping PipeWire streaming The stream object was deleted from a slot connected to its stopStreaming signal. This is unsafe and can lead to memory corruption and ultimately crashes when PipWwire streaming is stopped. Use deleteLater instead. Related: bug 428268 M +1-1src/plugins/screencast/screencastmanager.cpp https://invent.kde.org/plasma/kwin/commit/59f6b77612d3e80fa579064ebdcccfd2127158c9 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435312] System settings craches while selecting "Desktop Session" section in "Startup and Shutdown" cetegory
https://bugs.kde.org/show_bug.cgi?id=435312 Alois Wohlschlager changed: What|Removed |Added CC||kdebugzilla@t0mmy.anonaddy. ||com --- Comment #3 from Alois Wohlschlager --- *** Bug 435662 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435662] System Settings crashed while switching between menus
https://bugs.kde.org/show_bug.cgi?id=435662 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Alois Wohlschlager --- *** This bug has been marked as a duplicate of bug 435312 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435618] Plasmashell crashes when clicking a widget in the system notification area
https://bugs.kde.org/show_bug.cgi?id=435618 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO --- Comment #1 from Alois Wohlschlager --- Please provide a backtrace of the crash. The user logs are not very useful. -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 435543] In create dc in AS1 error is is coming
https://bugs.kde.org/show_bug.cgi?id=435543 Alois Wohlschlager changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||alo...@gmx-topmail.de Resolution|--- |WAITINGFORINFO --- Comment #1 from Alois Wohlschlager --- Please be more specific. What error? What did you do before you got the error message? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435437] system setting crash when switching between Appearance sub categories
https://bugs.kde.org/show_bug.cgi?id=435437 Alois Wohlschlager changed: What|Removed |Added Status|REPORTED|RESOLVED CC||alo...@gmx-topmail.de Resolution|--- |DUPLICATE --- Comment #1 from Alois Wohlschlager --- *** This bug has been marked as a duplicate of bug 435312 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435312] System settings craches while selecting "Desktop Session" section in "Startup and Shutdown" cetegory
https://bugs.kde.org/show_bug.cgi?id=435312 Alois Wohlschlager changed: What|Removed |Added CC||bednarczyk.pa...@outlook.co ||m --- Comment #2 from Alois Wohlschlager --- *** Bug 435437 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435405] The system crash when i was use plasma wayland session
https://bugs.kde.org/show_bug.cgi?id=435405 Alois Wohlschlager changed: What|Removed |Added CC||alo...@gmx-topmail.de Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Alois Wohlschlager --- So everything crashed, and this is in the same crash wave as https://bugs.kde.org/show_bug.cgi?id=435406 ? In this case, it is a known bug in Qt that happens when the Wayland compositor (kwin_wayland in this case) vanishes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 434452] Segfault when restarting pipewire while window preview is shown
https://bugs.kde.org/show_bug.cgi?id=434452 --- Comment #2 from Alois Wohlschlager --- The same crash also happens for other situations where KWin is transporting screen content over Pipewire. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435371] Crash when restarting pipewire while a xdg-desktop-portal screencast is in progress
https://bugs.kde.org/show_bug.cgi?id=435371 Alois Wohlschlager changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||alo...@gmx-topmail.de --- Comment #1 from Alois Wohlschlager --- *** This bug has been marked as a duplicate of bug 434452 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 434452] Segfault when restarting pipewire while window preview is shown
https://bugs.kde.org/show_bug.cgi?id=434452 Alois Wohlschlager changed: What|Removed |Added CC||k...@ashka.me --- Comment #1 from Alois Wohlschlager --- *** Bug 435371 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
