overview for KaKi87

[KDE neon 6.3] I have to wait for the login screen to black out and reappear before logging in in c/[email protected]

[–] [email protected] 2 points 4 days ago (1 children)

Hi,

Did you get a chance to look at my logs ?

Thank you

[KDE neon 6.3] I have to wait for the login screen to black out and reappear before logging in in c/[email protected]

[–] [email protected] 2 points 1 week ago

(part 2/2)

Stack trace of thread 1409:
#0  0x000075d797b1b4cd __GI___poll (libc.so.6 + 0x11b4cd)
#1  0x000075d79783666e n/a (libglib-2.0.so.0 + 0xbc66e)
#2  0x000075d7977d6a53 g_main_context_iteration (libglib-2.0.so.0 + 0x5ca53)
#3  0x000075d79846e6ef _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x26e6ef)
#4  0x000075d7986b14d3 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x4b14d3)
#5  0x000075d7985c8df7 _ZN7QThread4execEv (libQt6Core.so.6 + 0x3c8df7)
#6  0x000075d79a0a4272 n/a (libQt6Quick.so.6 + 0x4a4272)
#7  0x000075d798586915 n/a (libQt6Core.so.6 + 0x386915)
#8  0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#9  0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)

Stack trace of thread 1439:
#0  0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1  0x000075d797a9bc8e __pthread_cond_wait_common (libc.so.6 + 0x9bc8e)
#2  0x000075d79858d058 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x38d058)
#3  0x000075d798587a36 n/a (libQt6Core.so.6 + 0x387a36)
#4  0x000075d798586915 n/a (libQt6Core.so.6 + 0x386915)
#5  0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6  0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)

Stack trace of thread 1444:
#0  0x000075d797a98f0b futex_wait (libc.so.6 + 0x98f0b)
#1  0x000075d797a47a90 __run_exit_handlers (libc.so.6 + 0x47a90)
#2  0x000075d797a47bbe __GI_exit (libc.so.6 + 0x47bbe)
#3  0x000075d797900bd7 _XDefaultIOError (libX11.so.6 + 0x3dbd7)
#4  0x000075d79790390c _XIOError (libX11.so.6 + 0x4090c)
#5  0x000075d797909932 _XReply (libX11.so.6 + 0x46932)
#6  0x000075d7978e0e18 XGetGeometry (libX11.so.6 + 0x1de18)
#7  0x000075d792dbf5c8 n/a (libGLX_mesa.so.0 + 0x305c8)
#8  0x000075d7898e1d33 n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0xe1d33)
#9  0x000075d7898e9365 n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0xe9365)
#10 0x000075d7899be915 n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x1be915)
#11 0x000075d7899bf865 n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x1bf865)
#12 0x000075d789c3136e n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x43136e)
#13 0x000075d789c36360 n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x436360)
#14 0x000075d79901fa1b n/a (libQt6Gui.so.6 + 0x61fa1b)
#15 0x000075d799023b9f n/a (libQt6Gui.so.6 + 0x623b9f)
#16 0x000075d798ee3440 _ZN4QRhi8endFrameEP13QRhiSwapChain6QFlagsINS_12EndFrameFlagEE (libQt6Gui.so.6 + 0x4e3440)
#17 0x000075d79a0083af n/a (libQt6Quick.so.6 + 0x4083af)
#18 0x000075d798586915 n/a (libQt6Core.so.6 + 0x386915)
#19 0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#20 0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)

Stack trace of thread 1361:
#0  0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1  0x000075d797a9b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2  0x000075d78995040d n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15040d)
#3  0x000075d789fec04b n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x7ec04b)
#4  0x000075d78995033c n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15033c)
#5  0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6  0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)
ELF object binary architecture: AMD x86-64

[KDE neon 6.3] I have to wait for the login screen to black out and reappear before logging in in c/[email protected]

[–] [email protected] 2 points 1 week ago* (last edited 1 week ago) (1 children)

Hi,

Here's what I found :

(part 1/2)

Process 1323 (sddm-greeter-qt) of user 122 dumped core.

Module libudev.so.1 from deb systemd-255.4-1ubuntu8.6.amd64
Module libnss_systemd.so.2 from deb systemd-255.4-1ubuntu8.6.amd64
Module libgomp.so.1 from deb gcc-14-14.2.0-4ubuntu2~24.04.amd64
Module libzstd.so.1 from deb libzstd-1.5.5+dfsg2-2build1.1.amd64
Module libgcc_s.so.1 from deb gcc-14-14.2.0-4ubuntu2~24.04.amd64
Module libstdc++.so.6 from deb gcc-14-14.2.0-4ubuntu2~24.04.amd64
Module libsystemd.so.0 from deb systemd-255.4-1ubuntu8.6.amd64
Stack trace of thread 1323:
#0  0x000075d797a4798b __run_exit_handlers (libc.so.6 + 0x4798b)
#1  0x000075d797a47bbe __GI_exit (libc.so.6 + 0x47bbe)
#2  0x000075d793b7da31 n/a (libQt6XcbQpa.so.6 + 0x4fa31)
#3  0x000075d793b95baf n/a (libQt6XcbQpa.so.6 + 0x67baf)
#4  0x000075d7977d75b5 n/a (libglib-2.0.so.0 + 0x5d5b5)
#5  0x000075d797836717 n/a (libglib-2.0.so.0 + 0xbc717)
#6  0x000075d7977d6a53 g_main_context_iteration (libglib-2.0.so.0 + 0x5ca53)
#7  0x000075d79846e6ef _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x26e6ef)
#8  0x000075d7986b14d3 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x4b14d3)
#9  0x000075d7986b2ffd _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x4b2ffd)
#10 0x00005cf22e4bd5b9 n/a (sddm-greeter-qt6 + 0x175b9)
#11 0x000075d797a2a1ca __libc_start_call_main (libc.so.6 + 0x2a1ca)
#12 0x000075d797a2a28b __libc_start_main_impl (libc.so.6 + 0x2a28b)
#13 0x00005cf22e4c2835 n/a (sddm-greeter-qt6 + 0x1c835)

Stack trace of thread 1344:
#0  0x000075d797b1b4cd __GI___poll (libc.so.6 + 0x11b4cd)
#1  0x000075d79783666e n/a (libglib-2.0.so.0 + 0xbc66e)
#2  0x000075d7977d6a53 g_main_context_iteration (libglib-2.0.so.0 + 0x5ca53)
#3  0x000075d79846e6ef _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x26e6ef)
#4  0x000075d7986b14d3 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x4b14d3)
#5  0x000075d7985c8df7 _ZN7QThread4execEv (libQt6Core.so.6 + 0x3c8df7)
#6  0x000075d79775c02d n/a (libQt6DBus.so.6 + 0x9c02d)
#7  0x000075d798586915 n/a (libQt6Core.so.6 + 0x386915)
#8  0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#9  0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)

Stack trace of thread 1355:
#0  0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1  0x000075d797a9b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2  0x000075d78995040d n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15040d)
#3  0x000075d789fefbc3 n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x7efbc3)
#4  0x000075d78995033c n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15033c)
#5  0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6  0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)

Stack trace of thread 1359:
#0  0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1  0x000075d797a9b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2  0x000075d78995040d n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15040d)
#3  0x000075d789fec04b n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x7ec04b)
#4  0x000075d78995033c n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15033c)
#5  0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6  0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)

Stack trace of thread 1413:
#0  0x000075d797b2725d syscall (libc.so.6 + 0x12725d)
#1  0x000075d7985895da _ZN10QSemaphore7acquireEi (libQt6Core.so.6 + 0x3895da)
#2  0x000075d76c6c5524 n/a (libQt6HunspellInputMethod.so.6 + 0x10524)
#3  0x000075d798586915 n/a (libQt6Core.so.6 + 0x386915)
#4  0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#5  0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)

Stack trace of thread 1423:
#0  0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1  0x000075d797a9b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2  0x000075d79858d0db _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x38d0db)
#3  0x000075d76c50e9bd n/a (libQt6LabsFolderListModel.so.6 + 0xf9bd)
#4  0x000075d798586915 n/a (libQt6Core.so.6 + 0x386915)
#5  0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6  0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)

Stack trace of thread 1441:
#0  0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1  0x000075d797a9bc8e __pthread_cond_wait_common (libc.so.6 + 0x9bc8e)
#2  0x000075d79858d058 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x38d058)
#3  0x000075d798587a36 n/a (libQt6Core.so.6 + 0x387a36)
#4  0x000075d798586915 n/a (libQt6Core.so.6 + 0x386915)
#5  0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6  0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)

Stack trace of thread 1442:
#0  0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1  0x000075d797a9bc8e __pthread_cond_wait_common (libc.so.6 + 0x9bc8e)
#2  0x000075d79858d058 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x38d058)
#3  0x000075d798587a36 n/a (libQt6Core.so.6 + 0x387a36)
#4  0x000075d798586915 n/a (libQt6Core.so.6 + 0x386915)
#5  0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6  0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)

Stack trace of thread 1356:
#0  0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1  0x000075d797a9b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2  0x000075d78995040d n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15040d)
#3  0x000075d789fefbc3 n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x7efbc3)
#4  0x000075d78995033c n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15033c)
#5  0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6  0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)

Stack trace of thread 1357:
#0  0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1  0x000075d797a9b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2  0x000075d78995040d n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15040d)
#3  0x000075d789fefbc3 n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x7efbc3)
#4  0x000075d78995033c n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15033c)
#5  0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6  0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)

Stack trace of thread 1360:
#0  0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1  0x000075d797a9b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2  0x000075d78995040d n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15040d)
#3  0x000075d789fec04b n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x7ec04b)
#4  0x000075d78995033c n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15033c)
#5  0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6  0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)

Stack trace of thread 1362:
#0  0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1  0x000075d797a9b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2  0x000075d78995040d n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15040d)
#3  0x000075d789fec04b n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x7ec04b)
#4  0x000075d78995033c n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15033c)
#5  0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6  0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)

Stack trace of thread 1365:
#0  0x000075d797b1b4cd __GI___poll (libc.so.6 + 0x11b4cd)
#1  0x000075d79783666e n/a (libglib-2.0.so.0 + 0xbc66e)
#2  0x000075d7977d6a53 g_main_context_iteration (libglib-2.0.so.0 + 0x5ca53)
#3  0x000075d79846e6ef _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x26e6ef)
#4  0x000075d7986b14d3 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x4b14d3)
#5  0x000075d7985c8df7 _ZN7QThread4execEv (libQt6Core.so.6 + 0x3c8df7)
#6  0x000075d798586915 n/a (libQt6Core.so.6 + 0x386915)
#7  0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#8  0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)

Stack trace of thread 1440:
#0  0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1  0x000075d797a9bc8e __pthread_cond_wait_common (libc.so.6 + 0x9bc8e)
#2  0x000075d79858d058 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x38d058)
#3  0x000075d798587a36 n/a (libQt6Core.so.6 + 0x387a36)
#4  0x000075d798586915 n/a (libQt6Core.so.6 + 0x386915)
#5  0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6  0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)

Stack trace of thread 1358:
#0  0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1  0x000075d797a9b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2  0x000075d78995040d n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15040d)
#3  0x000075d789fefbc3 n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x7efbc3)
#4  0x000075d78995033c n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15033c)
#5  0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6  0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)

Stack trace of thread 1363:
#0  0x000075d797a98d71 __futex_abstimed_wait_common64 (libc.so.6 + 0x98d71)
#1  0x000075d797a9b7ed __pthread_cond_wait_common (libc.so.6 + 0x9b7ed)
#2  0x000075d78995040d n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15040d)
#3  0x000075d78992ed0b n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x12ed0b)
#4  0x000075d78995033c n/a (libgallium-24.2.8-1ubuntu1~24.04.1.so + 0x15033c)
#5  0x000075d797a9caa4 start_thread (libc.so.6 + 0x9caa4)
#6  0x000075d797b29c3c __clone3 (libc.so.6 + 0x129c3c)

Breeze for VSCode no longer works for the header in c/[email protected]

[–] [email protected] 2 points 1 week ago

I'm one of those who like clicking window controls 😅 -- including an always-on-top button that I added.

Breeze for VSCode no longer works for the header in c/[email protected]

[–] [email protected] 2 points 1 week ago

Indeed, more specifically in View ➔ Appearance ➔ Custom Title Bar. Thank you !

29

Breeze for VSCode no longer works for the header (lemmynsfw.com)

submitted 1 week ago by [email protected] to c/[email protected]

5 comments fedilink

Hi,

Since the VSCode header changed, the official KDE Breeze theme no longer works for it.

Thanks

[KDE neon 6.3] I have to wait for the login screen to black out and reappear before logging in in c/[email protected]

[–] [email protected] 1 points 2 weeks ago

Nope, just the laptop monitor.

[KDE neon 6.3] I have to wait for the login screen to black out and reappear before logging in in c/[email protected]

[–] [email protected] 2 points 2 weeks ago (1 children)

are you using any sddm themes? splash screens?

Nope, all default.

Also check/share the logs (you can use ksystemlogs or gnome logs if you prefer guis).

I'm guessing you don't want the last few lines, what am I looking for ?

[KDE neon 6.3] I have to wait for the login screen to black out and reappear before logging in in c/[email protected]

[–] [email protected] 1 points 2 weeks ago

Do the login screens look different from one another?

Nope

KDE Neon isn't really meant as a daily driver

Why not ? It's Plasma and KDE apps on a Ubuntu LTS base with none of Canonical's crap.

And all KDE apps work on it, while other distros running KDE don't necessarily support all KDE apps, especially Discover.

23

[KDE neon 6.3] I have to wait for the login screen to black out and reappear before logging in (jlai.lu)

submitted 2 weeks ago by [email protected] to c/[email protected]

11 comments fedilink

I start my computer ;
The loading screen appears ;
The login screen appears (but logging in will not work) ;
The screen turns black with underscore ;
The login screen reappears (logging in will finally work) ;
I'm logged in.

It has been like that for a while, I expected this bug to be found & fixed eventually, but after running an update today, it still hasn't, which is why I'm now posting here.

So, when the login screen first appears :

either I have time to type my password & press enter, but afterwards the login screen still disappears then reappears as if I never tried to log in ;
or I'm still typing the password while it disappears then it reappears as if I never started typing ;
or I wait for it to disappear & reappear, and only then I can finally log in.

What to do ?

Thank you

6

[neon 6.3] APT error "Conflicting values set for option Signed-By regarding source" (jlai.lu)

submitted 1 month ago* (last edited 1 month ago) by [email protected] to c/[email protected]

0 comments fedilink

Hi,

I suddently encountered this error on Discover while having done nothing for it to happen :

E: Conflicting values set for option Signed-By regarding source https://packages.mozilla.org/apt/ mozilla: /etc/apt/keyrings/packages.mozilla.org.asc != /etc/apt/keyrings/org.kde.neon.packages.mozilla.org.asc E: The list of sources could not be read.

What to do ?

PS : error 2 of 2 is identical to error 1 of 2.

Thanks

[neon 6.3] How to force GNOME apps to display KDE titlebar (even if GNOME titlebar remains, I don't care) ? in c/[email protected]

[–] [email protected] 1 points 1 month ago

Already tried from a Reddit thread : it doesn't work, but also, that window shows that the current value is already No.

23

[neon 6.3] How to force GNOME apps to display KDE titlebar (even if GNOME titlebar remains, I don't care) ? (jlai.lu)

submitted 1 month ago by [email protected] to c/[email protected]

3 comments fedilink

Because I customized KDE to show close/(un)maximize/minimize on the left and most importantly always on top on the right, except GNOME apps show only close and only on the right and the rest require a right-click, this is so annoying.

Basically, I want this :

To become this :

Thanks

[neon 6.3 Wayland] Keystrokes OSD while recording with Spectacle ? in c/[email protected]

[–] [email protected] 1 points 1 month ago

Found it : https://repo.aosc.io/debs/pool/stable/main/s/showmethekey_1.14.0-0_amd64.deb

No luck though :

$ sudo apt install ./showmethekey_1.14.0-0_amd64.deb 
[sudo] password for kaki:         
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'showmethekey' instead of './showmethekey_1.14.0-0_amd64.deb'
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) showmethekey:amd64 < none -> 1.14.0 @un puN Ib >
Broken showmethekey:amd64 Depends on systemd:amd64 < 255.4-1ubuntu8.5 @ii mK > (>= 1:256.4-1)
Broken showmethekey:amd64 Depends on libadwaita:amd64 < none @un H > (>= 1.5.0)
Broken showmethekey:amd64 Depends on libevdev:amd64 < none @un H > (>= 1.11.0)
Broken showmethekey:amd64 Depends on libinput:amd64 < none @un H > (>= 1.26.2-1)
Broken showmethekey:amd64 Depends on gtk-4:amd64 < none @un H > (>= 4.14.2)
Broken showmethekey:amd64 Depends on glib:amd64 < none @un H > (>= 2.80.0-2)
Broken showmethekey:amd64 Depends on json-glib:amd64 < none @un H > (>= 1.8.0)
Broken showmethekey:amd64 Depends on cairo:amd64 < none @un H > (>= 1.18.2)
Broken showmethekey:amd64 Depends on pango:amd64 < none @un H > (>= 1.52.2)
Broken showmethekey:amd64 Depends on libxkbcommon:amd64 < none @un H > (>= 1.7.0)
Broken showmethekey:amd64 Depends on polkit:amd64 < none @un H > (>= 1:125)
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 showmethekey : Depends: systemd (>= 1:256.4-1) but 255.4-1ubuntu8.5 is to be installed
                Depends: libadwaita (>= 1.5.0) but it is not installable
                Depends: libevdev (>= 1.11.0) but it is not installable
                Depends: libinput (>= 1.26.2-1) but it is not installable
                Depends: gtk-4 (>= 4.14.2) but it is not installable
                Depends: glib (>= 2.80.0-2) but it is not installable
                Depends: json-glib (>= 1.8.0) but it is not installable
                Depends: cairo (>= 1.18.2) but it is not installable
                Depends: pango (>= 1.52.2) but it is not installable
                Depends: libxkbcommon (>= 1.7.0) but it is not installable
                Depends: polkit (>= 1:125) but it is not installable
E: Unable to correct problems, you have held broken packages.

[neon 6.3 Wayland] Keystrokes OSD while recording with Spectacle ? in c/[email protected]

[–] [email protected] 1 points 1 month ago

Hmm, I'm looking for the URL of their APT repository but I'm not finding it 🤔

[neon 6.3 Wayland] Keystrokes OSD while recording with Spectacle ? in c/[email protected]

[–] [email protected] 1 points 1 month ago (3 children)

That's interesting, unfortunately there's no packaging at all for Debian-based distros 😭

13

[neon 6.3 Wayland] Keystrokes OSD while recording with Spectacle ? (jlai.lu)

submitted 1 month ago by [email protected] to c/[email protected]

8 comments fedilink

Hi,

I would like to show keyboard shortcuts being pressed while recording my screen with Spectacle on KDE neon 6.3, and I found apps that could do that but not on Wayland...

Does anyone know any ?

Thank you

41

[Plasma] Why audio output device selection at different places ? (jlai.lu)

submitted 2 months ago by [email protected] to c/[email protected]

10 comments fedilink

Hi,

I was used to switching between laptop speakers and Bluetooth speaker on the normal audio menu.

But one day, I needed to use a TV's speakers through HDMI, and couldn't find it, so I initially thought it was a driver issue, but never found a fix, so I had to use a friend's Windows laptop at the last minute because people were waiting to watch something.

Today, months later, I have the same issue, but on a different laptop with more recent hardware, so I was hoping to have better luck, and I didn't... Until I accidentaly notice that the HDMI device is available under a submenu of the laptop's speakers, WTF ?

Attached to this post is a screenshot showing a Bluetooth speaker, the laptop's speakers and HDMI speakers. Why isn't the latter available at the same location as the former two ?

The submenu could be kept for selecting between 2.0/5.1/7.1, just like for Bluetooth devices it's used to select between aptX/LDAC/SBC, but I don't understand what's a whole different device doing in that submenu of the laptop's speakers.

Thanks

12

Allow only one Dolphin instance ? (jlai.lu)

submitted 3 months ago by [email protected] to c/[email protected]

6 comments fedilink

Hi,

When pressing Super-E when Dolphin is already open, I would like for the existing window to be unminimized and for a new tab to be created, rather than a new window.

How to do this ?

Thanks

15

Unattended remote desktop ? (jlai.lu)

submitted 3 months ago* (last edited 3 months ago) by [email protected] to c/[email protected]

14 comments fedilink

Hi,

Is there any remote desktop app that works on KDE neon 6.2 with Wayland ?

Thanks

12

Allow only one Konsole instance ? (jlai.lu)

submitted 3 months ago by [email protected] to c/[email protected]

15 comments fedilink

Hi,

When pressing Ctrl-Alt-T when Konsole is already open, I would like for the existing window to be unminimized and for a new tab to be created, rather than a new window.

How to do this ?

Thanks

9

Analog clock widgets with different timezones ? (jlai.lu)

submitted 3 months ago by [email protected] to c/[email protected]

0 comments fedilink

Hi,

How to add multiple clocks on my KDE neon 6.2 desktop with different timezones ?

Thanks

22

How to make Flatpaked GNOME apps look okay on KDE ? (jlai.lu)

submitted 3 months ago by [email protected] to c/[email protected]

8 comments fedilink

They all look bad for some reason, sometimes even completely unreadable because of the lack of padding between lines of text or dark-on-dark text color.

Thanks

25

KDE neon 6 : "Up to date" vs "install all available updates [...] before upgrading" (jlai.lu)

submitted 6 months ago by [email protected] to c/[email protected]

10 comments fedilink

Hi,

Who's right and what to do ?

Thanks