[frameworks-kglobalaccel] [Bug 453423] Numpad shortcuts don't work in wayland sessions.

[Kyle B.]

https://bugs.kde.org/show_bug.cgi?id=453423

--- Comment #17 from Kyle B.  ---
Possible duplicate of :

https://bugs.kde.org/show_bug.cgi?id=413310
https://bugs.kde.org/show_bug.cgi?id=446389
https://bugs.kde.org/show_bug.cgi?id=461291

These all describe the same problem.

According to the latest comment on 413310 this appears to be a bug in QT
specifically.

That bug here claims to be "RESOLVED UPSTREAM", but I do not believe this to be
the case.

The QT bug pages are both not listed as resolved at the time of this posting.

https://bugreports.qt.io/browse/QTBUG-57661

https://bugreports.qt.io/browse/QTBUG-94892

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kded] [Bug 495107] Plasma reports multiple crashes after logging in

[Kyle B.]

https://bugs.kde.org/show_bug.cgi?id=495107

--- Comment #1 from Kyle B.  ---
Attempting to uninstall wacomtablet-kcm6 did not resolve the issue. 

Affected services are: kded6, xdg-desktop-portal-kde, kactivitymanagerd, KDE
Power Management System. They all report "closing unexpectedly" on every
startup. 

The Plasma desktop environment still seems to load and operate normally
otherwise, however.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kded] [Bug 495107] New: Plasma reports multiple crashes after logging in

[Kyle B.]

https://bugs.kde.org/show_bug.cgi?id=495107

Bug ID: 495107
   Summary: Plasma reports multiple crashes after logging in
Classification: Frameworks and Libraries
   Product: frameworks-kded
   Version: 6.7.0
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kio-bugs-n...@kde.org
  Reporter: arcangelze...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Application: kded6 (6.7.0)

ApplicationNotResponding [ANR]: false
Qt Version: 6.8.0
Frameworks Version: 6.7.0
Operating System: Linux 6.11.3-1-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 6.2.1 [CoredumpBackend]

-- Information about the crash:
After updating the system approximately 10/18/2024, logging into the system
shows several crash reports from KDE (Power management, Kactivitymanagerd,
KDEConnect,and others) that all seem to have the exact same crash reports. 

Uncertain if it's related but a KDEWallet prompt is now coming up where it
hasn't before as well.

It appears to be related to
QtWaylandClient::QWaylandTabletPadV2::zwp_tablet_pad_v2_removed(), but I'm
completely unsure from there.

I do have an XP-Pen Deco Pro MW drawing tablet installed.

The crash can be reproduced every time.

-- Backtrace:
Application: kded6 (kded6), signal: Segmentation fault


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.

warning: Can't open file /memfd:pulseaudio (deleted) during file-backed mapping
note processing

warning: Can't open file /var/lib/nscd/passwd during file-backed mapping note
processing

warning: Can't open file /memfd:kwin-dmabuf-feedback-table (deleted) during
file-backed mapping note processing
[New LWP 2288]
[New LWP 2306]
[New LWP 2318]
[New LWP 2321]
[New LWP 2320]
[New LWP 2307]
[New LWP 2297]
[New LWP 2319]
[New LWP 2323]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/kded6'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7ff25749a25c in __pthread_kill_implementation () from
/lib64/libc.so.6
[Current thread is 1 (Thread 0x7ff257615980 (LWP 2288))]
python sentry-sdk not installed :(
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7ff257615980 (LWP 2288))]

Thread 9 (Thread 0x7ff23a2006c0 (LWP 2323)):
#0  0x7ff25750ebcf in poll () at /lib64/libc.so.6
#1  0x7ff244ae1451 in ??? () at /lib64/libpulse.so.0
#2  0x7ff244acb634 in pa_mainloop_poll () at /lib64/libpulse.so.0
#3  0x7ff244ad5be6 in pa_mainloop_iterate () at /lib64/libpulse.so.0
#4  0x7ff244ad5c90 in pa_mainloop_run () at /lib64/libpulse.so.0
#5  0x7ff244ae6104 in ??? () at /lib64/libpulse.so.0
#6  0x7ff244a84bbf in ??? () at
/usr/lib64/pulseaudio/libpulsecommon-17.0.so
#7  0x7ff2574983b2 in start_thread () at /lib64/libc.so.6
#8  0x7ff25751d5fc in __clone3 () at /lib64/libc.so.6

Thread 8 (Thread 0x7ff23c4006c0 (LWP 2319)):
#0  0x7ff25750f186 in ppoll () at /lib64/libc.so.6
#1  0x7ff257712d9f in ??? () at /lib64/libglib-2.0.so.0
#2  0x7ff2577134bc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7ff257713501 in ??? () at /lib64/libglib-2.0.so.0
#4  0x7ff25774249e in ??? () at /lib64/libglib-2.0.so.0
#5  0x7ff2574983b2 in start_thread () at /lib64/libc.so.6
#6  0x7ff25751d5fc in __clone3 () at /lib64/libc.so.6

Thread 7 (Thread 0x7ff2562006c0 (LWP 2297)):
#0  0x7ff25750f186 in ppoll () at /lib64/libc.so.6
#1  0x7ff257712d9f in ??? () at /lib64/libglib-2.0.so.0
#2  0x7ff2577134bc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7ff257ffdd23 in QEventDispatcherGlib::processEvents
(this=0x7ff25ba0, flags=...) at
/usr/src/debug/qtbase-everywhere-src-6.8.0/src/corelib/kernel/qeventdispatcher_glib.cpp:396
#4  0x7ff257db6402 in QEventLoop::exec (this=0x7ff2561ffba0, flags=...) at
/usr/src/debug/qtbase-everywhere-src-6.8.0/src/corelib/global/qflags.h:34
#5  0x7ff257ea290c in QThread::exec (this=) at
/usr/src/debug/qtbase-everywhere-src-6.8.0/src/corelib/global/qflags.h:74
#6  0x7ff258e1322e in ??? () at /lib64/libQt6DBus.so.6
#7  0x7ff257f1cb39 in operator() (__closure=) at
/usr/src/debug/qtbase-everywhere-src-6.8.0/src/corelib/thread/qthread_unix.cpp:335
#8  (anonymous
namespace)::terminate_on_exception >
(t=) at
/usr/src/debug/qtbase-everywhere-src-6.8.0/src/corelib/thread/qthread_unix.cpp:263
#9  QThreadPrivate::start (arg=0x7ff258e9ab20) at
/usr/src/debug/qtbase-everywhere-src-6.8.0/src/corelib/thread/qthread_unix.cpp:294
#10 

[frameworks-kded] [Bug 495107] Multiple Plasma services report segfault crashes upon login

[Kyle B.]

https://bugs.kde.org/show_bug.cgi?id=495107

Kyle B.  changed:

   What|Removed |Added

Summary|Plasma reports multiple |Multiple Plasma services
   |crashes after logging in|report segfault crashes
   ||upon login
   Keywords||qt6, wayland

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kded] [Bug 495107] Multiple Plasma services report segfault crashes upon login

[Kyle B.]

https://bugs.kde.org/show_bug.cgi?id=495107

Kyle B.  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #3 from Kyle B.  ---
I'm glad you found my report, and thank you for adding your experience!

You're right, I think our issue is specifically with: 
[KCrash Handler]
#4  0x7ff2563aa497 in QtWayland::zwp_tablet_pad_v2::handle_removed

I suspect the same as you do: That somehow upon initializing the tablet, it
counts as a "removal" first, and triggers this bug. The WEIRD thing is that
simply logging out the user (not shutting down) and logging back in, will have
a normal startup as expected.

I tried removing the tablet's USB dongle before booting, and everything booted
up normally as well. Weirdly, I did not encounter this bug when pulling the
dongle during a running session.

As a workaround, you can try either logging out and back in before starting
your session, or maybe try removing the dongle first on first boot?
I had to restart the proprietary driver when I did this too. Either way, it's a
bit of a pain. :(

Using XP-Pen's 3.4.9 driver at the moment. Maybe there's a way to reach out to
them as well. (As one of my pen buttons does nothing, too lol.)

But something definitely isn't playing right with QT!

This seems like a reproducible bug with a consistent source, so I apologize if
I'm doing this in error, but I'm going to set this bug as "CONFIRMED."

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 496057] Spectacle can't screen rectangle region as normal in multimonitor setup after update to 24.08.3

[Kyle B.]

https://bugs.kde.org/show_bug.cgi?id=496057

Kyle B.  changed:

   What|Removed |Added

 CC||arcangelze...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kded] [Bug 495107] Multiple Plasma services report segfault crashes upon login

[Kyle B.]

https://bugs.kde.org/show_bug.cgi?id=495107

--- Comment #4 from Kyle B.  ---
(In reply to DaydreamerKite from comment #2)

I'm able to start my session without crashes now! Pardon my poor reporting
skills but one of several solutions may have fixed it:

1. I ran   
"zypper in -f plasma6-desktop libQt6WaylandClient6 libqt5-qtwayland libQt6Xdg*"

to force reinstall those components. 

2. I put the tablet's wireless dongle into a different USB port. It was in a
USB 3.2 slot, now it's in a 3.0 slot? But I'm not sure if that made a
difference.

3. I installed the .RPM version of XP-PEN's latest drivers, instead of the
general purpose shell-script version they had previously.

I sincerely hope any of this is helpful!

-- 
You are receiving this mail because:
You are watching all bug changes.