[konsole] [Bug 439339] Konsole window doesn't honor Initial terminal size columns setting
https://bugs.kde.org/show_bug.cgi?id=439339 Richard Ullger changed: What|Removed |Added CC|rull...@protonmail.com | -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 483073] Crashed after another app crashed
https://bugs.kde.org/show_bug.cgi?id=483073 Richard Ullger changed: What|Removed |Added CC|rull...@protonmail.com | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415364] Implement feature to disable touchpad when mouse is plugged in when using Libinput driver
https://bugs.kde.org/show_bug.cgi?id=415364 Richard Ullger changed: What|Removed |Added CC|rull...@protonmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 394403] Width column list resize every time to restart
https://bugs.kde.org/show_bug.cgi?id=394403 Richard Ullger changed: What|Removed |Added CC|rull...@protonmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 449698] Highlight changed and unsaved lines markers not updated correctly on pressing ctrl-s
https://bugs.kde.org/show_bug.cgi?id=449698 Richard Ullger changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #6 from Richard Ullger --- This is now working in kate 24.02.2 Operating System: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.6-arch1-1 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484108] kwin_x11 coredump
https://bugs.kde.org/show_bug.cgi?id=484108 --- Comment #3 from Richard Ullger --- There were also coredumps from ksmserver and neochat at the same time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484108] kwin_x11 coredump
https://bugs.kde.org/show_bug.cgi?id=484108 --- Comment #2 from Richard Ullger --- This crash also happened at the exact same time. PID: 11197 (xembedsniproxy) UID: 1000 (richard) GID: 1000 (richard) Signal: 6 (ABRT) Timestamp: Wed 2024-03-20 21:23:03 GMT (3h 2min ago) Command Line: /usr/bin/xembedsniproxy Executable: /usr/bin/xembedsniproxy Control Group: /user.slice/user-1000.slice/user@1000.service/background.slice/plasma-xembedsniproxy.service Unit: user@1000.service User Unit: plasma-xembedsniproxy.service Slice: user-1000.slice Owner UID: 1000 (richard) Boot ID: 3dd131e75c424a23ab2bd4382875717d Machine ID: c993dfb5ce9241edb8a5bf0d15e772c4 Hostname: richards-clevo Storage: /var/lib/systemd/coredump/core.xembedsniproxy.1000.3dd131e75c424a23ab2bd4382875717d.11197.171096978300.zst (present) Size on Disk: 391.0K Message: Process 11197 (xembedsniproxy) of user 1000 dumped core. Core was generated by `/usr/bin/xembedsniproxy'. Program terminated with signal SIGABRT, Aborted. #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; [Current thread is 1 (Thread 0x72ee93b5fdc0 (LWP 11197))] (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x72ee95ec4393 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x72ee95e736c8 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x72ee95e5b4b8 in __GI_abort () at abort.c:79 #4 0x72ee9508a924 in qAbort () at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/global/qglobal.cpp:161 #5 qt_message_fatal (message=..., context=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/global/qlogging.cpp:2030 #6 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=..., msg=msg@entry=0x72ee95ca5d52 "%s", ap=ap@entry=0x7ffdbbad3250) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/global/qlogging.cpp:378 #7 0x72ee9508b135 in QMessageLogger::fatal (this=this@entry=0x7ffdbbad3610, msg=msg@entry=0x72ee95ca5d52 "%s") at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/global/qlogging.cpp:901 #8 0x72ee956d9be9 in init_platform (argv=, argc=@0x7ffdbbad396c: 1, platformThemeName=..., platformPluginPath=..., pluginNamesWithArguments=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.cpp:1284 #9 QGuiApplicationPrivate::createPlatformIntegration (this=0x555ddffc3300) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.cpp:1532 #10 0x72ee95774a18 in QGuiApplicationPrivate::createEventDispatcher (this=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.cpp:1551 #11 0x72ee9513db15 in QCoreApplicationPrivate::init (this=this@entry=0x555ddffc3300) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:900 #12 0x72ee95774ac1 in QGuiApplicationPrivate::init (this=0x555ddffc3300) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.cpp:1579 #13 0x72ee9576c4fb in QGuiApplication::QGuiApplication (this=, argc=, argv=, this=, argc=, argv=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.h:172 #14 0x555ddfbcb233 in main (argc=, argv=0x7ffdbbad3b18) at /usr/src/debug/plasma-workspace/plasma-workspace-6.0.2/xembed-sni-proxy/main.cpp:34 (gdb) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484108] kwin_x11 coredump
https://bugs.kde.org/show_bug.cgi?id=484108 --- Comment #1 from Richard Ullger --- This crash happened at the exact same time. PID: 11196 (gmenudbusmenupr) UID: 1000 (richard) GID: 1000 (richard) Signal: 6 (ABRT) Timestamp: Wed 2024-03-20 21:23:03 GMT (2h 51min ago) Command Line: /usr/bin/gmenudbusmenuproxy Executable: /usr/bin/gmenudbusmenuproxy Control Group: /user.slice/user-1000.slice/user@1000.service/background.slice/plasma-gmenudbusmenuproxy.service Unit: user@1000.service User Unit: plasma-gmenudbusmenuproxy.service Slice: user-1000.slice Owner UID: 1000 (richard) Boot ID: 3dd131e75c424a23ab2bd4382875717d Machine ID: c993dfb5ce9241edb8a5bf0d15e772c4 Hostname: richards-clevo Storage: /var/lib/systemd/coredump/core.gmenudbusmenupr.1000.3dd131e75c424a23ab2bd4382875717d.11196.171096978300.zst (present) Size on Disk: 400.7K Message: Process 11196 (gmenudbusmenupr) of user 1000 dumped core. Core was generated by `/usr/bin/gmenudbusmenuproxy'. Program terminated with signal SIGABRT, Aborted. #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; [Current thread is 1 (Thread 0x7d0c04974400 (LWP 11196))] (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7d0c05aab393 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x7d0c05a5a6c8 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x7d0c05a424b8 in __GI_abort () at abort.c:79 #4 0x7d0c0608a924 in qAbort () at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/global/qglobal.cpp:161 #5 qt_message_fatal (message=..., context=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/global/qlogging.cpp:2030 #6 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=..., msg=msg@entry=0x7d0c06ca5d52 "%s", ap=ap@entry=0x7ffc2d5c3380) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/global/qlogging.cpp:378 #7 0x7d0c0608b135 in QMessageLogger::fatal ( this=this@entry=0x7ffc2d5c3740, msg=msg@entry=0x7d0c06ca5d52 "%s") at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/global/qlogging.cpp:901 #8 0x7d0c066d9be9 in init_platform (argv=, --Type for more, q to quit, c to continue without paging--c argc=@0x7ffc2d5c3a9c: 1, platformThemeName=..., platformPluginPath=..., pluginNamesWithArguments=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.cpp:1284 #9 QGuiApplicationPrivate::createPlatformIntegration (this=0x624f67f4a7a0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.cpp:1532 #10 0x7d0c06774a18 in QGuiApplicationPrivate::createEventDispatcher ( this=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.cpp:1551 #11 0x7d0c0613db15 in QCoreApplicationPrivate::init ( this=this@entry=0x624f67f4a7a0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:900 #12 0x7d0c06774ac1 in QGuiApplicationPrivate::init (this=0x624f67f4a7a0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.cpp:1579 #13 0x7d0c0676c4fb in QGuiApplication::QGuiApplication ( this=, argc=, argv=, this=, argc=, argv=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.h:172 #14 0x624f67d97c23 in main (argc=, argv=0x7ffc2d5c3c48) at /usr/src/debug/plasma-workspace/plasma-workspace-6.0.2/gmenu-dbusmenu-proxy/main.cpp:20 (gdb) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484108] New: kwin_x11 coredump
https://bugs.kde.org/show_bug.cgi?id=484108 Bug ID: 484108 Summary: kwin_x11 coredump Classification: Plasma Product: kwin Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-x11-standalone Assignee: kwin-bugs-n...@kde.org Reporter: rull...@protonmail.com Target Milestone: --- SUMMARY Plasma randomly crashes while using the system STEPS TO REPRODUCE Frequent random crashes. Has happened on Alt+Tab, using a custom keyboard shortcut to start Dolphin and other unknown causes while using the system OBSERVED RESULT sddm restarts displaying the login screen EXPECTED RESULT Continue using the system without it crashing SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 Manufacturer: Notebook Product Name: P7xxTM1 ADDITIONAL INFORMATION PID: 10928 (kwin_x11) UID: 1000 (richard) GID: 1000 (richard) Signal: 6 (ABRT) Timestamp: Wed 2024-03-20 21:23:02 GMT (1h 39min ago) Command Line: /usr/bin/kwin_x11 --replace Executable: /usr/bin/kwin_x11 Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_x11.service Unit: user@1000.service User Unit: plasma-kwin_x11.service Slice: user-1000.slice Owner UID: 1000 (richard) Boot ID: 3dd131e75c424a23ab2bd4382875717d Machine ID: c993dfb5ce9241edb8a5bf0d15e772c4 Hostname: richards-clevo Storage: /var/lib/systemd/coredump/core.kwin_x11.1000.3dd131e75c424a23ab2bd4382875717d.10928.171096978200.zst (present) Size on Disk: 1.1M Message: Process 10928 (kwin_x11) of user 1000 dumped core. [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Core was generated by `/usr/bin/kwin_x11 --replace'. Program terminated with signal SIGABRT, Aborted. #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 Downloading source file /usr/src/debug/glibc/glibc/nptl/pthread_kill.c 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; [Current thread is 1 (Thread 0x77c11be1ba00 (LWP 10928))] (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x77c121cab393 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x77c121c5a6c8 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x77c121c424b8 in __GI_abort () at abort.c:79 #4 0x77c120e8a924 in qAbort () at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/global/qglobal.cpp:161 #5 qt_message_fatal (message=..., context=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/global/qlogging.cpp:2030 #6 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=..., msg=msg@entry=0x77c121aa5d52 "%s", ap=ap@entry=0x7ffed28600c0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/global/qlogging.cpp:378 #7 0x77c120e8b135 in QMessageLogger::fatal (this=this@entry=0x7ffed2860480, msg=msg@entry=0x77c121aa5d52 "%s") at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/global/qlogging.cpp:901 #8 0x77c1214d9be9 in init_platform (argv=, argc=@0x7ffed286083c: 2, platformThemeName=..., platformPluginPath=..., pluginNamesWithArguments=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.cpp:1284 #9 QGuiApplicationPrivate::createPlatformIntegration (this=0x5d301553b1b0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.cpp:1532 #10 0x77c121574a18 in QGuiApplicationPrivate::createEventDispatcher (this=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.cpp:1551 #11 0x77c120f3db15 in QCoreApplicationPrivate::init (this=this@entry=0x5d301553b1b0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:900 #12 0x77c121574ac1 in QGuiApplicationPrivate::init (this=this@entry=0x5d301553b1b0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.cpp:1579 #13 0x77c121ef53ee in QApplicationPrivate::init (this=0x5d301553b1b0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:473 #14 0x77c121ef5542 in QApplication::QApplication (this=this@entry=0x7ffed286090
[kontact] [Bug 394403] Width column list resize every time to restart
https://bugs.kde.org/show_bug.cgi?id=394403 Richard Ullger changed: What|Removed |Added CC||rull...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 411753] KDE Connect spams the desktop with a torrent of old notifications.
https://bugs.kde.org/show_bug.cgi?id=411753 Richard Ullger changed: What|Removed |Added CC|rull...@protonmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382604] Plasma must be restarted to for cursor size changes to take effect for the desktop and empty areas of the panel
https://bugs.kde.org/show_bug.cgi?id=382604 Richard Ullger changed: What|Removed |Added CC||rull...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462572] Autohidden top panel does not autohide after startup until hovered or interacted with once
https://bugs.kde.org/show_bug.cgi?id=462572 Richard Ullger changed: What|Removed |Added CC||rull...@protonmail.com --- Comment #14 from Richard Ullger --- I can confirm the autohide behaviour in Arch Linux. On logging into plasma, both my top and left hand side autohide panels do not autohide until I mouse over them. If I open a non full screen app before mousing over the panels, the app is positioned so that it doesn't cover the panels. This behaviour started happening after a recent system update although I can't recall which and occurs without fail. Both my autohide panels are floating. Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.3.1-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 Manufacturer: Notebook Product Name: P7xxTM1 System Version: Not Applicable -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 465266] Cancelling the screen locker within the grace period causes authentication failures (which may cause account lockouts)
https://bugs.kde.org/show_bug.cgi?id=465266 --- Comment #3 from Richard Ullger --- Workaround is to set 'Allow unlocking without password for:' to 0 seconds and let the session lock. You can then immediately log back in without getting a locked account. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 465266] Cancelling the screen locker within the grace period causes authentication failures (which may cause account lockouts)
https://bugs.kde.org/show_bug.cgi?id=465266 Richard Ullger changed: What|Removed |Added CC||rull...@protonmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Richard Ullger --- I can confirm this in 5.27.2. The more failed attempts there are, the longer the users account is locked. After the locked time has elapsed without any further failed attempts, the screen locker doesn't clear the locked error message displayed and it requires a login attempt to clear the error in the screen locker still preventing login and another login attempt to actually log in. Mar 02 18:15:00 richards-clevo kscreenlocker_greet[15138]: pam_faillock(kde:auth): Consecutive login failures for user richard account temporarily locked Mar 02 18:15:00 richards-clevo kscreenlocker_greet[15138]: pam_unix(kde:auth): auth could not identify password for [richard] Mar 02 18:15:00 richards-clevo kscreenlocker_greet[15138]: pam_unix(kde:auth): conversation failed Mar 02 18:15:00 richards-clevo kscreenlocker_greet[15138]: pam_unix(kde:auth): unexpected response from failed conversation function Mar 02 18:15:00 richards-clevo kscreenlocker_greet[15138]: pam_systemd_home(kde:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found. Mar 02 18:13:58 richards-clevo kscreenlocker_greet[14997]: pam_unix(kde:auth): auth could not identify password for [richard] Mar 02 18:13:58 richards-clevo kscreenlocker_greet[14997]: pam_unix(kde:auth): conversation failed Mar 02 18:13:58 richards-clevo kscreenlocker_greet[14997]: pam_unix(kde:auth): unexpected response from failed conversation function Mar 02 18:13:58 richards-clevo kscreenlocker_greet[14997]: pam_systemd_home(kde:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found. Mar 02 18:12:56 richards-clevo kscreenlocker_greet[14846]: pam_unix(kde:auth): auth could not identify password for [richard] Mar 02 18:12:56 richards-clevo kscreenlocker_greet[14846]: pam_unix(kde:auth): conversation failed Mar 02 18:12:56 richards-clevo kscreenlocker_greet[14846]: pam_unix(kde:auth): unexpected response from failed conversation function Mar 02 18:12:55 richards-clevo kscreenlocker_greet[14846]: pam_systemd_home(kde:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found. Mar 02 18:08:40 richards-clevo kscreenlocker_greet[6212]: pam_systemd_home(kde:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found. Operating System: Arch Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.1-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 Manufacturer: Notebook Product Name: P7xxTM1 System Version: Not Applicable -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 464578] Kwin produces window border, despite borders being disabled in breeze.
https://bugs.kde.org/show_bug.cgi?id=464578 --- Comment #8 from Richard Ullger --- Is there somewhere in the theme definition I can change the colour of that line to match the window background? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465098] Cannot turn off window borders
https://bugs.kde.org/show_bug.cgi?id=465098 --- Comment #1 from Richard Ullger --- Created attachment 155837 --> https://bugs.kde.org/attachment.cgi?id=155837&action=edit Window in plasma 5.26.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465098] New: Cannot turn off window borders
https://bugs.kde.org/show_bug.cgi?id=465098 Bug ID: 465098 Summary: Cannot turn off window borders Classification: Plasma Product: kwin Version: 5.26.90 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: rull...@protonmail.com Target Milestone: --- Created attachment 155836 --> https://bugs.kde.org/attachment.cgi?id=155836&action=edit Window in plasma 5.26.90 SUMMARY I have windows set to display with no border. Upgrading to plasma 5.26.90 causes windows to display with a border. STEPS TO REPRODUCE 1. In plasma 5.26.5, set window border size to 'Theme's default (No Borders)' in window decorations 2. Upgrade to 5.26.90 OBSERVED RESULT Windows display with a border EXPECTED RESULT Windows should display without a border as in 5.26.5 SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.8-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 Manufacturer: Notebook Product Name: P7xxTM1 System Version: Not Applicable ADDITIONAL INFORMATION Switching between 'Theme's default (No Borders)' and 'No Borders' and then clicking 'Apply' causes the window borders to disappear and then immediately reappear. Downgrading to 5.26.5 reverts to windows displaying with no borders. Global theme: Breeze Dark Application style: Breeze Plasma style: Breeze (Follows colour scheme) Colours: Krita Dark Window decorations: Breeze -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 449698] Highlight changed and unsaved lines markers not updated correctly on pressing ctrl-s
https://bugs.kde.org/show_bug.cgi?id=449698 --- Comment #5 from Richard Ullger --- Are you leaving the cursor at the second edited line? If I position the cursor at the end of the file before entering the password, both markers remain red. If I position the cursor at the start of the file before entering the password, both markers turn green. If I leave the mouse pointer in the area containing the line numbers before entering the password, as soon as I move the mouse pointer out of that area, the markers turn green. I can make further screen recordings to illustrate the different scenarios if you wish. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 449698] Highlight changed and unsaved lines markers not updated correctly on pressing ctrl-s
https://bugs.kde.org/show_bug.cgi?id=449698 --- Comment #3 from Richard Ullger --- Created attachment 155193 --> https://bugs.kde.org/attachment.cgi?id=155193&action=edit Screen recording showing the issue -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 449698] Highlight changed and unsaved lines markers not updated correctly on pressing ctrl-s
https://bugs.kde.org/show_bug.cgi?id=449698 Richard Ullger changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #2 from Richard Ullger --- I have retested this following the steps described and the issue still exists. Operating System: Arch Linux KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 kde-applications: 22.12.1 Qt Version: 5.15.8 Kernel Version: 6.1.4-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 Manufacturer: Notebook Product Name: P7xxTM1 System Version: Not Applicable -- You are receiving this mail because: You are watching all bug changes.
[basket] [Bug 341120] Select buffer and pasting it with middle-click doesn't work
https://bugs.kde.org/show_bug.cgi?id=341120 Richard Ullger changed: What|Removed |Added CC|rull...@protonmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455885] Firefox & Thunderbird start up with an empty window containing just a title bar and the plasma splash screen
https://bugs.kde.org/show_bug.cgi?id=455885 Richard Ullger changed: What|Removed |Added Summary|Firefox randomly starts up |Firefox & Thunderbird start |with an empty window|up with an empty window |containing just a title bar |containing just a title bar |and the plasma splash |and the plasma splash |screen |screen --- Comment #3 from Richard Ullger --- This is happening with both Firefox and Thunderbird without fail at every startup from autostart. -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 416461] [5.18] KDE wallet not unlocked on login
https://bugs.kde.org/show_bug.cgi?id=416461 Richard Ullger changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #36 from Richard Ullger --- Dear bug janitor service, I reported this bug in Jan 2020 and it was fixed in Aug 2020. Someone else has hijacked this report instead of creating a new one. As per your request, I am closing the original bug as resolved. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453700] dolphin in detailed view open files and folders also if I click elsewhere on the line not only on the filename
https://bugs.kde.org/show_bug.cgi?id=453700 --- Comment #26 from Richard Ullger --- In dolphin 22.04.2, utilising the blank column on the left hand side of the window fixes all my issues. - Deselecting files - Clicking in the blank column to select a pane in split view - Right-click to paste a file into the directory being viewed - Right-click a directory in the list and select paste file to paste a file into that directory - Drag and drop a file into the directory being viewed - Drag and drop a file over a directory in the list to paste the file into that directory -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455885] Firefox randomly starts up with an empty window containing just a title bar and the plasma splash screen
https://bugs.kde.org/show_bug.cgi?id=455885 --- Comment #1 from Richard Ullger --- Created attachment 150117 --> https://bugs.kde.org/attachment.cgi?id=150117&action=edit Firefox window containing wallpaper -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455885] New: Firefox randomly starts up with an empty window containing just a title bar and the plasma splash screen
https://bugs.kde.org/show_bug.cgi?id=455885 Bug ID: 455885 Summary: Firefox randomly starts up with an empty window containing just a title bar and the plasma splash screen Product: kwin Version: 5.25.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: rull...@protonmail.com Target Milestone: --- Created attachment 150116 --> https://bugs.kde.org/attachment.cgi?id=150116&action=edit Firefox window showing plasma splash screen SUMMARY Firefox is set to autostart on login and randomly starts up with an empty window containing just the title bar and initially showing the plasma splash screen. When minimised and then maximised, the wallpaper is displayed instead. The only way to fix this is to close firefox and restart it. Screenshots attached STEPS TO REPRODUCE 1. Add firefox to autostart OBSERVED RESULT Next time you log into plasma, firefox sometimes starts up showing the kde splash screen in the firefox window and other times showing the firefox home screen. EXPECTED RESULT Firefox should always start up showing the firefox home screen SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Kernel Version: 5.18.6-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 Manufacturer: Notebook Product Name: P7xxTM1 System Version: Not Applicable ADDITIONAL INFORMATION Seems to only happen during autostart. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 454108] [5.24.90] [Regression] First character of password input to unlock session not registered
https://bugs.kde.org/show_bug.cgi?id=454108 --- Comment #11 from Richard Ullger --- I don't see any updates to Arch kde-unstable. I've manually applied the commit and it fixes the original problem and I'm not seeing your issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422230] Plasma crashed when I opened settings of "System Monitor Sensor" widget immediately after add it to desktop
https://bugs.kde.org/show_bug.cgi?id=422230 Richard Ullger changed: What|Removed |Added CC|rull...@protonmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454293] [5.24.90] [Regression] Power option missing from desktop right-click context menu
https://bugs.kde.org/show_bug.cgi?id=454293 Richard Ullger changed: What|Removed |Added Resolution|WAITINGFORINFO |INTENTIONAL Status|NEEDSINFO |RESOLVED --- Comment #2 from Richard Ullger --- Thanks, I've added it back in. Perhaps it should be left alone on an existing system and not mess around with peoples settings. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 454298] New: [5.24.90] [Regression] Strange text output on konsole startup
https://bugs.kde.org/show_bug.cgi?id=454298 Bug ID: 454298 Summary: [5.24.90] [Regression] Strange text output on konsole startup Product: konsole Version: 22.04.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: rull...@protonmail.com Target Milestone: --- Created attachment 149146 --> https://bugs.kde.org/attachment.cgi?id=149146&action=edit Konsole screenshot SUMMARY The konsole application outputs strange text on startup. Screenshot attached STEPS TO REPRODUCE 1. Upgrade to plasma 5.24.90 2. Start up the konsole application OBSERVED RESULT The text 'discover_other_daemon: 1' can be seen displayed before the bash prompt EXPECTED RESULT Bash prompt should display without the additional preceding text SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 Manufacturer: Notebook Product Name: P7xxTM1 System Version: Not Applicable -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454293] New: [5.24.90] [Regression] Power option missing from desktop right-click context menu
https://bugs.kde.org/show_bug.cgi?id=454293 Bug ID: 454293 Summary: [5.24.90] [Regression] Power option missing from desktop right-click context menu Product: plasmashell Version: 5.24.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: rull...@protonmail.com CC: notm...@gmail.com Target Milestone: 1.0 The right-click desktop context menu no longer contains the power option. STEPS TO REPRODUCE 1. Right-click on an empty area of the desktop OBSERVED RESULT The desktop context menu is displayed. The power option to Restart/Shutdown/Logoff is missing EXPECTED RESULT The desktop context menu is displayed and includes the power option to Restart/Shutdown/Logoff. This was the behaviour pre 5.24.90 SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 Manufacturer: Notebook Product Name: P7xxTM1 System Version: Not Applicable -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453700] dolphin in detailed view open files and folders also if I click elsewhere on the line not only on the filename
https://bugs.kde.org/show_bug.cgi?id=453700 Richard Ullger changed: What|Removed |Added CC||rull...@protonmail.com --- Comment #5 from Richard Ullger --- The change that is causing these issues is in my opinion a bad design decision. I can no longer copy or cut a file and paste it using the context menu unless the dolphin window contains empty space below the last file/directory. Where the window is filled with a list of files or directories, the context menu when clicked on a line that contains a file does not contain an option to paste the file. When clicked on a line that contains a directory the option to paste is there but the file is pasted into the directory on the clicked line instead of the directory being viewed. I can no longer drag and drop a file into an empty space in a dolphin window that is filled with a list of directories. The file will be dropped into the directory of the line where the mouse button is released instead of into the directory being viewed. I have misplaced files several times because of this until I realised what was happening. I can no longer click on an empty space after a file name to deselect a file. Doing so opens the file or enters the directory. More attention needs to be paid to click to the left of the file or directory name to deselect it. I can no longer click on the empty space after a file or directory name to select the left or right pane when in split view. Doing so opens the file or enters the directory on the line clicked. All these in my opinion being regressions from previous versions making dolphin annoying and more difficult to use. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 454108] New: [5.24.90] [Regression] First character of password input to unlock session not registered
https://bugs.kde.org/show_bug.cgi?id=454108 Bug ID: 454108 Summary: [5.24.90] [Regression] First character of password input to unlock session not registered Product: kscreenlocker Version: 5.24.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rull...@protonmail.com CC: bhus...@gmail.com Target Milestone: --- After the screen has blanked and the session locked, input of password to unlock the session without first bringing up the password input text box fails because the first character of the password is not registered. STEPS TO REPRODUCE 1. In a plasma session, allow the screen to blank and the session to lock. 2. Without waking the screen, start to enter your password to unlock the session and press OBSERVED RESULT The screen is awakened as you start to enter the password but screen unlock fails because the first character of the password did not register. EXPECTED RESULT The screen is awakened as you start to enter the password and the screen unlocks on input of . This was the behaviour pre the 5.24.90 release. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 Manufacturer: Notebook Product Name: P7xxTM1 System Version: Not Applicable ADDITIONAL INFORMATION The same result can be obtained by pressing L to lock the screen. On performing this action the lockscreen displays without the password input field being displayed. Entering the password immediately before the screen blanks causes the password input text box to be displayed but screen unlock fails because the first character of the password has not registered. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415364] Setting to disable when mouse is plugged in is missing when using Libinput driver
https://bugs.kde.org/show_bug.cgi?id=415364 --- Comment #11 from Richard Ullger --- You can reinstate the old behaviour by adding [autodisable] DisableWhenMousePluggedIn=true to ~/.config/touchpadrc At least, this still works for me and I get a notification that the touchpad has been disabled because a mouse was plugged in when I log into plasma. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 440903] Konsole not respecting initial window size set in profile even when the "remember window size" option is disabled
https://bugs.kde.org/show_bug.cgi?id=440903 Richard Ullger changed: What|Removed |Added CC|rull...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 449698] New: Highlight changed and unsaved lines markers not updated correctly on pressing ctrl-s
https://bugs.kde.org/show_bug.cgi?id=449698 Bug ID: 449698 Summary: Highlight changed and unsaved lines markers not updated correctly on pressing ctrl-s Product: kate Version: 21.12.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: rull...@gmail.com Target Milestone: --- SUMMARY After editing some lines, pressing ctrl-s to save the file does not update the 'Left side' markers to green for all edited lines STEPS TO REPRODUCE 1. Ensure Settings->Configure kate->Appearance->Borders->Highlight changed and unsaved lines is checked. 2. Create a dummy text file containing some lines of text in a directory where you do not have write permission, for example /etc using sudo. 3. Navigate to the directory in dolphin, right-click the file and select open with kate. 4. Make changes to some of the lines leaving the cursor on the last line edited. 5. Press ctrl-s to save the file entering your password when prompted. OBSERVED RESULT The red left side markers for the changed lines turn to green only for the lines on and below the line the cursor is on. EXPECTED RESULT The red left side markers for all changed lines should turn to green. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.5-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 ADDITIONAL INFORMATION The issue only presents itself after entering your password. The issue is not present if you have write access to the file and are not prompted to enter a password. Moving the cursor in any direction with the arrow keys causes the remaining red markers to turn green. Moving the mouse pointer to the left side that contains a line number causes the remaining red markers to turn green. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448403] New: SDDM login screen displays a white background
https://bugs.kde.org/show_bug.cgi?id=448403 Bug ID: 448403 Summary: SDDM login screen displays a white background Product: systemsettings Version: 5.23.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_sddm Assignee: k...@davidedmundson.co.uk Reporter: rull...@gmail.com CC: k...@david-redondo.de, plasma-b...@kde.org Target Milestone: --- Following upgrade to 5.23.90, the sddm login screen displays a white background instead of the selected wallpaper. STEPS TO REPRODUCE 1. Upgrade to 5.23.90 2. Reboot OBSERVED RESULT The SDDM login screen displays a white background with white date and time. The only things visible are the user and password fields EXPECTED RESULT The SDDM login screen background should display the selected wallpaper SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.0-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 ADDITIONAL INFORMATION The wallpaper is set to Next so that the wallpaper for each new plasma version is used. Plasma settings are applied in Startup and Shutdown -> Login Screen (SDDM). /usr/share/sddm/themes/breeze/theme.conf contains the line background=/usr/share/wallpapers/Next/contents/images/1920x1080.png but the wallpapers in /usr/share/wallpapers/Next/contents/images/ are all .jpg files. Changing the background line in the theme.conf file to a .jpg file fixes the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448389] New: Smart window placement missing - defaulting to centered
https://bugs.kde.org/show_bug.cgi?id=448389 Bug ID: 448389 Summary: Smart window placement missing - defaulting to centered Product: kwin Version: 5.23.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: rull...@gmail.com Target Milestone: --- Up to plasma 5.23.5, applications starting up unmaximised were placed on the desktop using smart placement. Following upgrade to 5.23.90, such applications are placed centred. On viewing Settings -> Window Management -> Window Behaviour -> Advanced -> Window Placement, it's value has been changed to 'Centred' and the smart placement option is no longer present. Downgrading to 5.23.5 does not restore the smart placement setting and smart placement option is still not present. STEPS TO REPRODUCE 1. Ensure window smart placement is set 2. Upgrade to 5.23.90 3. Reboot 4. Log in and start an unmaximised application OBSERVED RESULT Application starts up centred EXPECTED RESULT Application should start up using smart placement rules SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.0-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 ADDITIONAL INFORMATION Arch kde-unstable repo -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443262] Sync wallpaper to SDDM when all containments use the same image as their wallpaper
https://bugs.kde.org/show_bug.cgi?id=443262 --- Comment #2 from Richard Ullger --- Observation: The wallpaper in the login screen (breeze) thumbnail was updated. The same wallpaper could also be set for the sddm login screen. Alternatively, as a simple solution, you could let the user decide which wallpaper to use as a selection in the login screen settings. As a workaround I have disabled the theme.conf.user file. This causes sddm to display the correct wallpaper, which plasma updated in the theme.conf file. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443262] New: SDDM login screen wallpaper not updated when sync plasma settings
https://bugs.kde.org/show_bug.cgi?id=443262 Bug ID: 443262 Summary: SDDM login screen wallpaper not updated when sync plasma settings Product: systemsettings Version: 5.22.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_sddm Assignee: k...@davidedmundson.co.uk Reporter: rull...@gmail.com CC: k...@david-redondo.de, plasma-b...@kde.org Target Milestone: --- Created attachment 142124 --> https://bugs.kde.org/attachment.cgi?id=142124&action=edit sddm login screen settings screenshot SUMMARY The sddm login screen wallpaper does not get updated the the plasma theme wallpaper when you click on the 'Apply Plasma Settings...' button. STEPS TO REPRODUCE 1. Run Systemsettings 2. Change your wallpaper 3. Click on Startup and Shutdown 4. Click on 'Apply Plasma Settings...' OBSERVED RESULT The wallpaper on the sddm theme thumbnail is updated with the new wallpaper (see the attached screenshot) but the actual sddm login screen shows the old wallpaper EXPECTED RESULT The sddm login screen wallpaper should show the newly selected wallpaper SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.12.15-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31.3 GiB of RAM Graphics Processor: GeForce GTX 1080/PCIe/SSE2 ADDITIONAL INFORMATION The new wallpaper selection has been updated to the file /usr/share/sddm/themes/breeze/theme.conf but the file /usr/share/sddm/themes/breeze/theme.conf.user is overriding that selection. The file /usr/share/sddm/themes/breeze/theme.conf.user contains the lines... [General] background=Plasma 5.22 1920x1080.png type=image This is not a file that I have created or edited. Perhaps it is no longer used or it's update has been omitted. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442748] New: KpluginFactory cannot load the plugin kcm_fontinst.so
https://bugs.kde.org/show_bug.cgi?id=442748 Bug ID: 442748 Summary: KpluginFactory cannot load the plugin kcm_fontinst.so Product: systemsettings Version: 5.22.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_fontinst Assignee: plasma-b...@kde.org Reporter: rull...@gmail.com Target Milestone: --- Created attachment 141743 --> https://bugs.kde.org/attachment.cgi?id=141743&action=edit Font Management systemsettings screenshot SUMMARY KpluginFactory cannot load the plugin /usr/lib/qt/plugins/kcms/kcm_fontinst.so. The file is present on the system and is provided by the package kde-unstable/plasma-workspace STEPS TO REPRODUCE 1. Open systemsettings 2. Click on Appearance 3. Click on Font Management OBSERVED RESULT Error message. See attached screenshot EXPECTED RESULT Installed fonts should display SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.12.15-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31.3 GiB of RAM Graphics Processor: GeForce GTX 1080/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 439339] Konsole window doesn't honor Initial terminal size columns setting
https://bugs.kde.org/show_bug.cgi?id=439339 Richard Ullger changed: What|Removed |Added CC||rull...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 440903] Konsole not respecting window size set in profile even when the "remember window size" option is disabled
https://bugs.kde.org/show_bug.cgi?id=440903 Richard Ullger changed: What|Removed |Added CC||rull...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 430036] konsole no-toolbar setting missing or forgotten
https://bugs.kde.org/show_bug.cgi?id=430036 Richard Ullger changed: What|Removed |Added CC||rull...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435742] [Plasma Mobile] kwin_wayland crashes in KWin::ApplicationWayland::performStartup()
https://bugs.kde.org/show_bug.cgi?id=435742 Richard Ullger changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #10 from Richard Ullger --- No longer relevant -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435742] [Plasma Mobile] kwin_wayland crashes in KWin::ApplicationWayland::performStartup()
https://bugs.kde.org/show_bug.cgi?id=435742 --- Comment #9 from Richard Ullger --- Backtrace limit is already set to unlimited levels so I'm not sure how to generate the required info. Is the following of any use? 101 args = QStringList{QStringLiteral("--xwayland"), QStringLiteral(CMAKE_INSTALL_FULL_LIBEXECDIR "/startplasma-waylandsession")}; (gdb) s QStringList::~QStringList (this=0xf518, __in_chrg=) at /usr/include/qt/QtCore/qstringlist.h:111 111 class QStringList : public QList (gdb) n 103 runSync(QStringLiteral("kwin_wayland_wrapper"), args); (gdb) p args $5 = {> = {> = {}, {p = {static shared_null = {ref = {atomic = { _q_value = {> = { static _S_alignment = 4, _M_i = -1}, static is_always_lock_free = true}}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0xaab5cdc0}, d = 0xaab5cdc0}}, } (gdb) info stack #0 main (argc=, argv=0xf6c8) at /home/richard/kde/src/plasma/plasma-workspace/startkde/startplasma-wayland.cpp:103 (gdb) s QStringList::QStringList (this=0xf528) at /usr/include/qt/QtCore/qstringlist.h:115 115 inline QStringList() noexcept { } (gdb) s QList::QList (this=0xf528) at /usr/include/qt/QtCore/qlist.h:160 160 inline QList() noexcept : d(const_cast(&QListData::shared_null)) { } (gdb) s runSync (program=..., args=..., env=...) at /home/richard/kde/src/plasma/plasma-workspace/startkde/startplasma.cpp:77 77 { (gdb) l 72 names.sort(); 73 return names; 74 } 75 76 int runSync(const QString &program, const QStringList &args, const QStringList &env) 77 { 78 QProcess p; 79 if (!env.isEmpty()) 80 p.setEnvironment(QProcess::systemEnvironment() << env); 81 p.setProcessChannelMode(QProcess::ForwardedChannels); (gdb) s 78 QProcess p; (gdb) s 79 if (!env.isEmpty()) (gdb) s QList::isEmpty (this=0xf528) at /usr/include/qt/QtCore/qlist.h:201 201 inline bool isEmpty() const noexcept { return p.isEmpty(); } (gdb) s QListData::isEmpty (this=0xf528) at /usr/include/qt/QtCore/qlist.h:116 116 inline bool isEmpty() const noexcept { return d->end == d->begin; } (gdb) s 81 p.setProcessChannelMode(QProcess::ForwardedChannels); (gdb) s warning: Source file is more recent than executable. 121 Q_DECL_CONSTEXPR inline QFlags(Enum flags) noexcept : i(Int(flags)) {} (gdb) s [Detaching after fork from child process 3628] 84 p.waitForFinished(-1); (gdb) Launching kwin No backend specified through command line argument, trying auto resolution Compositor crashed, respawning Launching kwin No backend specified through command line argument, trying auto resolution QObject::connect(KWin::Platform, KWin::ColorManager): invalid nullptr parameter QObject::connect(KWin::Platform, KWin::ColorManager): invalid nullptr parameter QObject::connect(KWin::LogindIntegration, KWin::ColorManager): invalid nullptr parameter kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5079:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5081:48: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5083:48: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5087:47: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5089:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5097:48: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5101:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5103:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5107:45: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5110:46: this compose sequence is a duplicate of another; skipping line kf.globalaccel.kglobalacceld: Shortcut found twice in kglobalshortcutsrc. 134217760 kf.globalaccel.kglobalacceld: Shortcut found twice in kglobalshortcutsrc. 150994993 kf.globalaccel.kglobalacceld: Shortcut found twice in kglobalshortcutsrc. 16777362 kf.globalaccel.kglobalacceld: Shortcut found twice in kglobalshortcutsrc. 184549425 Compositor crashed, respawning Launch
[kwin] [Bug 435742] [Plasma Mobile] Crash in kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=435742 --- Comment #6 from Richard Ullger --- Btw, ExternalSizeMax=6G made no difference. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435742] [Plasma Mobile] Crash in kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=435742 --- Comment #5 from Richard Ullger --- Will you need debug symbols for the Qt packages or can you do without? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435742] [Plasma Mobile] Crash in kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=435742 Richard Ullger changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Richard Ullger --- Needed (gdb) thread apply all bt full coredumpctl gdb 3396 PID: 3396 (kwin_wayland) UID: 1000 (richard) GID: 1000 (richard) Signal: 11 (SEGV) Timestamp: Thu 2021-04-15 21:21:04 BST (1h 14min ago) Command Line: kwin_wayland --wayland_fd 4 --xwayland /home/richard/kde/usr/lib/libexec/startplasma-waylandsession Executable: /home/richard/kde/usr/bin/kwin_wayland Control Group: /user.slice/user-1000.slice/session-3.scope Unit: session-3.scope Slice: user-1000.slice Session: 3 Owner UID: 1000 (richard) Boot ID: 0cda462f126f472cb8d4ac870b350759 Machine ID: cbdca0011fc949b68c6fb34f1c74a5d0 Hostname: richards-pinetab Storage: /var/lib/systemd/coredump/core.kwin_wayland.1000.0cda462f126f472cb8d4ac870b350759.3396.161851806400.zst (present) Disk Size: 1.1M Message: Process 3396 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 3396: #0 0xbc1f5294 n/a (n/a + 0x0) #1 0xcbf013f8 n/a (n/a + 0x0) #2 0xcbeff7ac n/a (n/a + 0x0) #3 0x83732538 n/a (n/a + 0x0) #4 0xcbf00124 n/a (n/a + 0x0) GNU gdb (GDB) 10.1 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "aarch64-unknown-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /home/richard/kde/usr/bin/kwin_wayland... [New LWP 3396] [New LWP 3397] [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Core was generated by `kwin_wayland --wayland_fd 4 --xwayland /home/richard/kde/usr/lib/libexec/startp'. Program terminated with signal SIGSEGV, Segmentation fault. --Type for more, q to quit, c to continue without paging--c #0 0xbc1f5294 in ?? () [Current thread is 1 (Thread 0x7f629490 (LWP 3396))] (gdb) thread apply all bt full Thread 2 (Thread 0x7e5bafe0 (LWP 3397)): #0 0x837d7e64 in poll () at /usr/lib/libc.so.6 #1 0x873b2828 in () at /usr/lib/libglib-2.0.so.0 #2 0x873b29b4 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x842903d8 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x84221cf4 in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x83ff8f84 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x874df5ac in () at /usr/lib/libQt5DBus.so.5 #7 0x83ffa888 in () at /usr/lib/libQt5Core.so.5 #8 0x83cebf44 in start_thread () at /usr/lib/libpthread.so.0 #9 0x837e195c in thread_start () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f629490 (LWP 3396)): #0 0xbc1f5294 in () #1 0xcbf013f8 in KWin::ApplicationWayland::performStartup() (this=0xd061eb08) at /home/richard/kde/src/plasma/kwin/src/main_wayland.cpp:159 #2 0xcbeff7ac in main(int, char**) (argc=, argv=) at /home/richard/kde/src/plasma/kwin/src/main_wayland.cpp:800 userSignals = {__val = {2560, 281474177821776, 187650543042848, 6, 7, 18--Type for more, q to quit, c to continue without paging--c 7650543236616, 5, 281474177821776, 187650543042848, 281474177821840, 281472887104736, 187650543042752, 0, 281474177821840, 281472887104764, 187650543042752}} environment = {d = {d = 0xf23b45c0}} a = { = {}, static staticMetaObject = {d = {superdata = {direct = 0x8733e5b0 }, stringdata = 0xcbf5c1a8 , data = 0xcbf5c400 , static_metacall = 0xcbf00210 , relatedMetaObjects = 0x0, extradata = 0x0}}, m_startXWayland = true, m_applicationsToStart = {> = {> = {}, {p = {static shared_null = {ref = {atomic = {_q_value = {> = {static _S_alignment = 4, _M_i = -1}, static is_always_lock_free = true}}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0xf2447800}, d
[kwin] [Bug 435742] [Plasma Mobile] Crash in kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=435742 --- Comment #2 from Richard Ullger --- Backtrace coredumpctl gdb 3831 PID: 3831 (kwin_wayland) UID: 1000 (richard) GID: 1000 (richard) Signal: 11 (SEGV) Timestamp: Wed 2021-04-14 22:22:43 BST (19min ago) Command Line: kwin_wayland --wayland_fd 4 --xwayland /home/richard/kde/usr/lib/libexec/startplasma-waylandsession Executable: /home/richard/kde/usr/bin/kwin_wayland Control Group: /user.slice/user-1000.slice/session-4.scope Unit: session-4.scope Slice: user-1000.slice Session: 4 Owner UID: 1000 (richard) Boot ID: 87e81a0551f54891bf2f3f88edcc2fc2 Machine ID: cbdca0011fc949b68c6fb34f1c74a5d0 Hostname: richards-pinetab Storage: /var/lib/systemd/coredump/core.kwin_wayland.1000.87e81a0551f54891bf2f3f88edcc2fc2.3831.161843536300.zst (present) Disk Size: 1.1M Message: Process 3831 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 3831: #0 0x95e35154 n/a (n/a + 0x0) #1 0xb46a13f8 n/a (n/a + 0x0) #2 0xb469f7ac n/a (n/a + 0x0) #3 0x9b934538 n/a (n/a + 0x0) #4 0xb46a0124 n/a (n/a + 0x0) GNU gdb (GDB) 10.1 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "aarch64-unknown-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /home/richard/kde/usr/bin/kwin_wayland... [New LWP 3831] [New LWP 3832] [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Core was generated by `kwin_wayland --wayland_fd 4 --xwayland /home/richard/kde/usr/lib/libexec/startp'. Program terminated with signal SIGSEGV, Segmentation fault. --Type for more, q to quit, c to continue without paging-- #0 0x95e35154 in ?? () [Current thread is 1 (Thread 0x9782b490 (LWP 3831))] (gdb) bt #0 0x95e35154 in () #1 0xb46a13f8 in KWin::ApplicationWayland::performStartup() (this=0xe7aef628) at /home/richard/kde/src/plasma/kwin/src/main_wayland.cpp:159 #2 0xb469f7ac in main(int, char**) (argc=, argv=) at /home/richard/kde/src/plasma/kwin/src/main_wayland.cpp:800 (gdb) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435742] [Plasma Mobile] Crash in kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=435742 --- Comment #1 from Richard Ullger --- Created attachment 137614 --> https://bugs.kde.org/attachment.cgi?id=137614&action=edit kde-env-master.sh file installed by kdesrc-build -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435742] New: [Plasma Mobile] Crash in kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=435742 Bug ID: 435742 Summary: [Plasma Mobile] Crash in kwin_wayland Product: kwin Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: rull...@gmail.com Target Milestone: --- Created attachment 137613 --> https://bugs.kde.org/attachment.cgi?id=137613&action=edit .xsession file copied from /home/richard/kde/src/kdesrc-build/sample-xsession.sh (modified) SUMMARY Attempting to test plasma mobile on a pinetab, built from git master using kdesrc-build. I can run a plasma wayland session installed from the archlinuxarm repos without problem. STEPS TO REPRODUCE 1. Build plasma and frameworks using kdesrc-build 2. Start a plasma mobile session OBSERVED RESULT Executing .xsession from console: No backend specified through command line argument, trying auto resolution Compositor crashed, respawning (Repeats 10 times) startplasmacompositor: Shutting down... startplasmacompositor: Done. Coredump in kwin_wayland EXPECTED RESULT Plasma mobile session should start SOFTWARE/OS VERSIONS Linux: Archlinux Arm linux-pine64 5.10.19-4 KDE Plasma Version: git master (kdesrc-build) KDE Frameworks Version: git master (kdesrc-build) Qt Version: 5.15.2 from archlinuxarm repos ADDITIONAL INFORMATION Specifically built as specified in https://community.kde.org/Get_Involved/development#Plasma plus any dependencies determined by kdesrc-build: plasma-workspace plasma-framework plasma-nm plasma-pa plasma-workspace-wallpapers kdeplasma-addons krunner milou kwin kscreen breeze plasma-browser-integration xdg-desktop-portal-kde Specifically built as specified in https://community.kde.org/Get_Involved/development#Plasma_Mobile plus any dependencies determined by kdesrc-build: plasma-nano plasma-phone-components plasma-settings Created /usr/share/wayland-sessions/kdesrc-build.desktop as specified in https://docs.kde.org/trunk5/en/kdesrc-build/kdesrc-build/environment.html [Desktop Entry] Type=XSession Exec=/home/richard/.xsession Name=Plasma Wayland (kdesrc-build) .xsession file copied from /home/richard/kde/src/kdesrc-build/sample-xsession.sh (modified - see attached file) .config/kde-env-master.sh installed by kdesrc-build -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421748] Panel icons missing on login
https://bugs.kde.org/show_bug.cgi?id=421748 Richard Ullger changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 428091] Virtual Keyboard is pinned to the top of the screen instead of the bottom
https://bugs.kde.org/show_bug.cgi?id=428091 Richard Ullger changed: What|Removed |Added CC||rull...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427972] Display of (Qt)Virtual Keyboard doesn't work properly under Wayland session.
https://bugs.kde.org/show_bug.cgi?id=427972 Richard Ullger changed: What|Removed |Added CC||rull...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415364] Setting to disable when mouse is plugged in is missing
https://bugs.kde.org/show_bug.cgi?id=415364 Richard Ullger changed: What|Removed |Added CC||rull...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422111] Battery applet not showing up in tray.
https://bugs.kde.org/show_bug.cgi?id=422111 Richard Ullger changed: What|Removed |Added CC|rull...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 383846] Inactive menu elements in GTK2 apps difficult to see using Breeze-Dark theme
https://bugs.kde.org/show_bug.cgi?id=383846 Richard Ullger changed: What|Removed |Added CC|rull...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422111] Battery applet not showing up in tray.
https://bugs.kde.org/show_bug.cgi?id=422111 Richard Ullger changed: What|Removed |Added CC||rull...@gmail.com --- Comment #27 from Richard Ullger --- I don't see this issue. Operating System: Arch Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.7.12-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5 CPU M 430 @ 2.27GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics Set Battery and Brightness (Automatic Load) in system tray config to Always shown, icon appears in system tray. When set to Shown when relevant, icon disappears. Disconnect AC, icon appears. Reconnect AC (still full charge), icon disappears. Reconnect AC (part discharge), icon remains until charged. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412865] Memory leak when spamming notifications
https://bugs.kde.org/show_bug.cgi?id=412865 Richard Ullger changed: What|Removed |Added CC||rull...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 423107] Systray elements are missing after update - broken config?
https://bugs.kde.org/show_bug.cgi?id=423107 Richard Ullger changed: What|Removed |Added CC|rull...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 423107] Systray elements are missing after update - broken config?
https://bugs.kde.org/show_bug.cgi?id=423107 Richard Ullger changed: What|Removed |Added CC|rull...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 416461] [5.18] KDE wallet not unlocked on login
https://bugs.kde.org/show_bug.cgi?id=416461 Richard Ullger changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #30 from Richard Ullger --- This is fixed in the current version, Operating System: Arch Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.7.12-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5 CPU M 430 @ 2.27GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics ...and prior versions. See Comments 26 & 27. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422230] Plasma crashed when I opened settings of "System Monitor Sensor" widget immediately after add it to desktop
https://bugs.kde.org/show_bug.cgi?id=422230 Richard Ullger changed: What|Removed |Added CC||rull...@gmail.com --- Comment #7 from Richard Ullger --- Did the fix make it into frameworks 5.72? If it did, it's still an issue. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 390549] Finance-Quote no longer working
https://bugs.kde.org/show_bug.cgi?id=390549 Richard Ullger changed: What|Removed |Added CC|rull...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423107] Systray elements are missing after update - broken config?
https://bugs.kde.org/show_bug.cgi?id=423107 --- Comment #20 from Richard Ullger --- Created attachment 129558 --> https://bugs.kde.org/attachment.cgi?id=129558&action=edit System tray screen recording I have a similar issue with the system tray being empty which only manifests itself in latte-dock. The screen recording shows the empty system tray and a new one added. 1. The system tray used is the default plasma widget. 2. When added to a vertical latte dock, the system tray functions correctly. 3. When latte-dock is started, by quitting and restarting latte or by logging out and logging in, the system tray is empty. 4. Even though the system tray appears empty, hovering the mouse pointer over the dock causes the tool tips to be displayed but in a horizontal aspect. 5. Removing ~/.config/plasma-org.kde.plasma.desktop-appletsrc causes a default plasma panel to be created on login with a correctly functioning system tray. Operating System: Arch Linux KDE Plasma Version: 5.19.1 KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 Kernel Version: 5.7.4-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5 CPU M 430 @ 2.27GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics latte-dock-git r4256.25f1b66d-1 (Sat 20 Jun 2020 21:02:57 BST) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 414267] Mail list colours are reversed between read and unread
https://bugs.kde.org/show_bug.cgi?id=414267 Richard Ullger changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #6 from Richard Ullger --- I gave up with kmail so not sure if this is still an issue. As there doesn't seem to be any other interest I'm closing this report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423107] Systray elements are missing after update - broken config?
https://bugs.kde.org/show_bug.cgi?id=423107 Richard Ullger changed: What|Removed |Added CC||rull...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421748] Panel icons missing on login
https://bugs.kde.org/show_bug.cgi?id=421748 --- Comment #1 from Richard Ullger --- Seems to affect all widgets on auto hide panels. Ok when set to 'windows can cover' and 'always visible'. -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 416461] [5.18] KDE wallet not unlocked on login
https://bugs.kde.org/show_bug.cgi?id=416461 --- Comment #27 from Richard Ullger --- Following upgrade I too have not encountered the issue so far. Operating System: Arch Linux KDE Plasma Version: 5.18.90 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0rc2 Kernel Version: 5.6.14-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5 CPU M 430 @ 2.27GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 421779] Powerdevil icon disappears at each login starting with 5.18.90
https://bugs.kde.org/show_bug.cgi?id=421779 Richard Ullger changed: What|Removed |Added CC||rull...@gmail.com --- Comment #1 from Richard Ullger --- I see a similar issue but with the basket note pads icon. I have it set to always display. Basket is included in autostart and set to dock to the system tray. On next login the icon is no longer visible in the system tray. Changing the system tray setting away from 'Always display' and back, the icon becomes visible again until the next login. This is a regression in plasma 5.18.90. Operating System: Arch Linux KDE Plasma Version: 5.18.90 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0rc2 Kernel Version: 5.6.14-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5 CPU M 430 @ 2.27GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421749] New: Plasma desktop crashes when choosing to configure the thermal monitor widget
https://bugs.kde.org/show_bug.cgi?id=421749 Bug ID: 421749 Summary: Plasma desktop crashes when choosing to configure the thermal monitor widget Product: plasmashell Version: 5.18.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: rull...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.90) Qt Version: 5.15.0 Frameworks Version: 5.70.0 Operating System: Linux 5.6.13-arch1-1 x86_64 Windowing system: X11 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Right clicked the thermal monitor widget in the panel and chose 'Configure Thermal Monitor...' - Unusual behavior I noticed: The outline of a window briefly appeared and the desktop redisplayed. - Custom settings of the application: Breeze theme, ambient blue colour scheme. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f41b4dcb193 in QMapNodeBase::nextNode() const () at /usr/lib/libQt5Core.so.5 #5 0x7f41b6e73db3 in Plasma::DataContainer::checkForUpdate() () at /usr/lib/libKF5Plasma.so.5 #6 0x7f41b4fa9940 in () at /usr/lib/libQt5Core.so.5 #7 0x7f41b4ede329 in QProcess::finished(int, QProcess::ExitStatus) () at /usr/lib/libQt5Core.so.5 #8 0x7f41b4ee3c76 in () at /usr/lib/libQt5Core.so.5 #9 0x7f41b4ee3dae in () at /usr/lib/libQt5Core.so.5 #10 0x7f41b4fa9940 in () at /usr/lib/libQt5Core.so.5 #11 0x7f41b4face70 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #12 0x7f41b4fad67d in QSocketNotifier::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #13 0x7f41b5a9d6f2 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #14 0x7f41b4f7269a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #15 0x7f41b4fcbe26 in () at /usr/lib/libQt5Core.so.5 #16 0x7f41b33e96be in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #17 0x7f41b33eb531 in () at /usr/lib/libglib-2.0.so.0 #18 0x7f41b33eb571 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #19 0x7f41b4fcb211 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #20 0x7f41b4f7101c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #21 0x7f41b4f794a4 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #22 0x55ab566cef5b in () #23 0x7f41b4941002 in __libc_start_main () at /usr/lib/libc.so.6 #24 0x55ab566cf17e in _start () [Inferior 1 (process 19415) detached] Possible duplicates by query: bug 421739, bug 421657, bug 421588, bug 421489, bug 421392. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421748] New: Panel icons missing on login
https://bugs.kde.org/show_bug.cgi?id=421748 Bug ID: 421748 Summary: Panel icons missing on login Product: plasmashell Version: 5.18.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: rull...@gmail.com Target Milestone: 1.0 Created attachment 128590 --> https://bugs.kde.org/attachment.cgi?id=128590&action=edit Panel missing icons showing icon tooltip SUMMARY After upgrading to plasma 5.18.90, the icons in a quick launch widget on a panel are missing after you log into a plasma session. Choosing a different icon set or moving the panel to an alternative screen edge causes the icons to be displayed until the next time you log in. STEPS TO REPRODUCE 1. Create an empty auto-hide panel 2. Add the quick launch widget 3. Add some application launchers to the widget 4. Log out of the session. 5. Log into a new plasma session OBSERVED RESULT An empty panel displays with a rapid flickering before auto hiding. The panel remains empty. Hovering the mouse pointer over the panel displays the icon's tooltip (see attached image). EXPECTED RESULT The panel should contain the icons that were added. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.18.90 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0rc2 Kernel Version: 5.6.13-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5 CPU M 430 @ 2.27GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 419437] New: Latte-dock crashes when edit panel
https://bugs.kde.org/show_bug.cgi?id=419437 Bug ID: 419437 Summary: Latte-dock crashes when edit panel Product: lattedock Version: git (master) Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: rull...@gmail.com Target Milestone: --- Created attachment 127124 --> https://bugs.kde.org/attachment.cgi?id=127124&action=edit Backtrace STEPS TO REPRODUCE 1. Right click on panel and select 'Edit Panel...'. OBSERVED RESULT The panel disappeared and the current maximised application resized to fill the screen. Latte dock automatically restarted and the panel reappeared. Crash is reproducible. EXPECTED RESULT Latte-dock settings panel should open. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.15.0beta2 Kernel Version: 5.5.13-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5 CPU M 430 @ 2.27GHz Memory: 7.5 GiB of RAM ADDITIONAL INFORMATION kde-unstable repo KDE applications 20.03.80 latte-dock 0.9.85 r3923.a8cd4659 -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 416461] [5.18] KDE wallet not unlocked on login
https://bugs.kde.org/show_bug.cgi?id=416461 --- Comment #15 from Richard Ullger --- I frequently use my phone for tethering or as a wifi hotspot. Sometimes I forget to activate the network on the phone before logging in on my laptop, so the laptop doesn't get a network connection. I've noticed that when I then enable the network on the phone, the laptop will obtain a network connection and the wallet will get unlocked without prompting for the password. When I log in on the laptop and the network is already available on the phone, the password to unlock the wallet will always be prompted. This is 100% reproducible. The following entries appear in journalctl when prompted for a password... kwalletd5[1313]: Application ' "kded5" ' using kwallet without parent window! . . . sddm[1119]: kwalletd5: Checking for pam module sddm[1119]: kwalletd5: Got pam-login param sddm[1119]: kwalletd5: Waiting for hash on 7- sddm[1119]: kwalletd5: waitingForEnvironment on: 3 sddm[1119]: kwalletd5: client connected sddm[1119]: kwalletd5: client disconnected -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 416461] [5.18] KDE wallet not unlocked on login
https://bugs.kde.org/show_bug.cgi?id=416461 --- Comment #12 from Richard Ullger --- (In reply to Nate Graham from comment #11) > Out of curiosity, are the people experiencing this using encrypted home > directories? I myself am not using an encrypted home directory. -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 416461] [5.17.90] KDE wallet not unlocked on login
https://bugs.kde.org/show_bug.cgi?id=416461 --- Comment #2 from Richard Ullger --- The kde wallet in plasma 5.18 is stored in ~/.local/share/kwalletd/. Renaming this folder will cause the directory to be recreated and a new wallet to be set up. Contrary to the Arch wiki page, you have the option to use a gpg key or blowfish encryption, with the gpg option being the default. The problem with using a gpg key is that you will be prompted to enter the gpg passphrase every time you log in. Recreating the wallet using blowfish encryption and you're back to entering your login password every time you log in. This regression occurred when I upgraded to 5.17.90 (5.18 beta) and persists in 5.18 and 5.18.1. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413838] Dolphin split view path becomes invisible when unfocused when using Krita Dark color scheme
https://bugs.kde.org/show_bug.cgi?id=413838 Richard Ullger changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413838] Dolphin split view path becomes invisible when unfocused when using Krita Dark color scheme
https://bugs.kde.org/show_bug.cgi?id=413838 --- Comment #6 from Richard Ullger --- Created attachment 125505 --> https://bugs.kde.org/attachment.cgi?id=125505&action=edit Krita colour scheme current state Agreed. Running from Arch testing repos and krita 4.2.3.2-2 the paths are now visible -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416791] Latte-dock panel on right side of screen constantly flashing and sometimes corrupt
https://bugs.kde.org/show_bug.cgi?id=416791 --- Comment #6 from Richard Ullger --- Fix confirmed. Thanks for the quick turnaround. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416791] Latte-dock panel on right side of screen constantly flashing and sometimes corrupt
https://bugs.kde.org/show_bug.cgi?id=416791 --- Comment #2 from Richard Ullger --- Created attachment 125443 --> https://bugs.kde.org/attachment.cgi?id=125443&action=edit latte layout file A. Attached B. 1. Closed latte 2. Ran latte-dock --cc from terminal. This command started latte-dock. Right hand panel still flashes. C. System Settings > Display and Monitor > Enable compositor on startup is enabled. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416791] New: Latte-dock panel on right side of screen constantly flashing and sometimes corrupt
https://bugs.kde.org/show_bug.cgi?id=416791 Bug ID: 416791 Summary: Latte-dock panel on right side of screen constantly flashing and sometimes corrupt Product: lattedock Version: 0.9.8 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: rull...@gmail.com Target Milestone: --- Created attachment 125441 --> https://bugs.kde.org/attachment.cgi?id=125441&action=edit Demo showing panel behaviour SUMMARY After upgrading to v0.9.8 the panel down the right edge of the screen constantly flashes. STEPS TO REPRODUCE 1. Set up a panel on the right edge of the screen 2. Upgrade latte-dock to 0.9.8 3. Restart latte-dock OBSERVED RESULT Panel down the right edge of the screen is constantly flashing and sometimes it's display is corrupt. See attached video. EXPECTED RESULT Panel should be static and not flash. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 Kernel Version: 5.4.15-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5 CPU M 430 @ 2.27GHz Memory: 7.5 GiB of RAM ADDITIONAL INFORMATION Downgrading to 0.9.7 fixes the issue. A dock I have on the left edge of the screen is unaffected. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 416761] New: Notification buttons are sometimes missing and button action incorrect.
https://bugs.kde.org/show_bug.cgi?id=416761 Bug ID: 416761 Summary: Notification buttons are sometimes missing and button action incorrect. Product: kdeconnect Version: 1.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: rull...@gmail.com Target Milestone: --- Created attachment 125411 --> https://bugs.kde.org/attachment.cgi?id=125411&action=edit Notification examples SUMMARY Kdeconnect notifications from the android feeder app (rss reader) can contain buttons to 'Open link in browser' and 'Mark as read'. The 'Mark as read' button is only present in the notification if the rss item the notification relates to contains a link causing the 'Open link in browser' button to be included. If the rss item does not contain a link, the notification does not contain a 'Mark as read' button. Also, the button actions are transposed. For example, when you click the 'Mark as read' button, the link is opened in the browser on the phone. STEPS TO REPRODUCE 1. Install the feeder app from fdroid. 2. Subscribe to an rss feed where some items contain a link, such as store.kde.org - Latest Products. 3. Pair phone and wait for notifications for items with and without a link. 4. Click on the 'Mark as read' button. OBSERVED RESULT Notifications for items containing a link will include both buttons. Those not containing a link will not include any buttons. When the 'Mark as read' button is clicked the link is opened in browser on the phone. EXPECTED RESULT Notifications for items not containing a link should contain a 'Mark as read' button. When the 'Mark as read' button is clicked, the item the notification relates to should be marked as read. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 Kernel Version: 5.4.14-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5 CPU M 430 @ 2.27GHz Memory: 7.5 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 411753] KDE Connect spams the desktop with a torrent of old notifications causing the system to become unresponsive.
https://bugs.kde.org/show_bug.cgi?id=411753 Richard Ullger changed: What|Removed |Added CC||rull...@gmail.com --- Comment #2 from Richard Ullger --- Confirmed in Arch Linux, kde-unstable repo If the phone disconnects and reconnects, all notifications are sent again. In my opinion kdeconnect should only send new notifications since the phone was paired. I can see a complete list of kdeconnect notifications in the system tray. Operating System: Arch Linux KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 Kernel Version: 5.4.14-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5 CPU M 430 @ 2.27GHz Memory: 7.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407757] Certain notifications all display in the centre of the screen on top of each other
https://bugs.kde.org/show_bug.cgi?id=407757 Richard Ullger changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED --- Comment #26 from Richard Ullger --- Retested in plasma v5.17.90 kde-unstable repo. Notifications no longer display centre screen with or without kdeconnect paired. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 415142] Three dot menu stays open
https://bugs.kde.org/show_bug.cgi?id=415142 Richard Ullger changed: What|Removed |Added CC||rull...@gmail.com --- Comment #2 from Richard Ullger --- Created attachment 125317 --> https://bugs.kde.org/attachment.cgi?id=125317&action=edit kdeconnect menu demo Confirmed in Arch Linux kde-unstable repo plasma v5.17.90 I can only remove the menu by selecting an option from it. Operating System: Arch Linux KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 Kernel Version: 5.4.13-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5 CPU M 430 @ 2.27GHz Memory: 7.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 414267] Mail list colours are reversed between read and unread
https://bugs.kde.org/show_bug.cgi?id=414267 Richard Ullger changed: What|Removed |Added Version|unspecified |5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416531] Tooltips flicker when moving mouse on gtk3 apps
https://bugs.kde.org/show_bug.cgi?id=416531 --- Comment #3 from Richard Ullger --- I confirm the D26809 code changes to morphingpopups.js fix the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416531] [Plasma 5.17.90] Tooltips flicker when moving mouse on gtk3 apps
https://bugs.kde.org/show_bug.cgi?id=416531 --- Comment #2 from Richard Ullger --- Disabling the morphing popups effect fixes the issue and the tooltips are stable. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416531] New: [Plasma 5.17.90] Tooltips flicker when moving mouse on gtk3 apps
https://bugs.kde.org/show_bug.cgi?id=416531 Bug ID: 416531 Summary: [Plasma 5.17.90] Tooltips flicker when moving mouse on gtk3 apps Product: kwin Version: 5.17.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: rull...@gmail.com Target Milestone: --- Created attachment 125279 --> https://bugs.kde.org/attachment.cgi?id=125279&action=edit Demo showing tooltip flicker SUMMARY Tooltips flicker when moving mouse on gtk3 apps STEPS TO REPRODUCE 1. Open a gtk3 application 2. Hover the mouse on a relevant part of the screen to generate a tooltip e.g. a toolbar button. 3. move the mouse. OBSERVED RESULT Tooltip flickers. See attached screen recording. EXPECTED RESULT Tooltip should not flicker SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 Kernel Version: 5.4.13-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5 CPU M 430 @ 2.27GHz Memory: 7.5 GiB of RAM ADDITIONAL INFORMATION Observed on gnucash and virtual machine manager. Doesn't happen on inkscape (gtk2) or firefox Arch kde-unstable repo -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 416461] New: [5.17.90] KDE wallet not unlocked on login
https://bugs.kde.org/show_bug.cgi?id=416461 Bug ID: 416461 Summary: [5.17.90] KDE wallet not unlocked on login Product: kwallet-pam Version: 5.17.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rull...@gmail.com Target Milestone: --- SUMMARY The KDE wallet used to be automatically unlocked using the login password but since upgrading to plasma 5.17.90 this is no longer the case and the wallet password has to be entered every time you log in. This prevents automatic login to the wireless network. STEPS TO REPRODUCE 1. Upgrade to 5.17.90 2. Log in OBSERVED RESULT Wallet manager requests entry of password for kded5. EXPECTED RESULT Wallet should be automatically unlocked using the login password which should not need to be entered separately. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 Kernel Version: 5.4.13-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5 CPU M 430 @ 2.27GHz Memory: 7.5 GiB of RAM ADDITIONAL INFORMATION Arch kde-unstable repo -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 414267] Mail list colours are reversed between read and unread
https://bugs.kde.org/show_bug.cgi?id=414267 --- Comment #4 from Richard Ullger --- Created attachment 123994 --> https://bugs.kde.org/attachment.cgi?id=123994&action=edit Kmail mail list colouring breeze dark Thanks for removing the previous attachments. New attachments added. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 414267] Mail list colours are reversed between read and unread
https://bugs.kde.org/show_bug.cgi?id=414267 --- Comment #5 from Richard Ullger --- Created attachment 123995 --> https://bugs.kde.org/attachment.cgi?id=123995&action=edit Kmail mail list colouring breeze -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 414267] Mail list colours are reversed between read and unread
https://bugs.kde.org/show_bug.cgi?id=414267 --- Comment #1 from Richard Ullger --- Created attachment 123991 --> https://bugs.kde.org/attachment.cgi?id=123991&action=edit Kmail mail list colouring in Breeze theme To clarify, the first two emails are read and the third is unread -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 414267] New: Mail list colours are reversed between read and unread
https://bugs.kde.org/show_bug.cgi?id=414267 Bug ID: 414267 Summary: Mail list colours are reversed between read and unread Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: rull...@gmail.com Target Milestone: --- Created attachment 123990 --> https://bugs.kde.org/attachment.cgi?id=123990&action=edit Kmail mail list colouring in breeze dark SUMMARY The colour of read emails is brighter than unread emails. This is a regression from v19.08.3 STEPS TO REPRODUCE 1. Start kmail 2. View the mail list for the inbox or a folder that contains both read and unread emails. OBSERVED RESULT Read emails are a brighter colour than unread emails. EXPECTED RESULT Unread emails should be a brighter colour than read emails. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.14.0 Kernel Version: 5.3.11-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5 CPU M 430 @ 2.27GHz Memory: 7.5 GiB of RAM kmail version: 5.12.80 beta1 (19.11.80) ADDITIONAL INFORMATION Version in kde-unstable Arch repo. The same issue can be seen with the default Breeze theme. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414231] System Settings crashes when clicked on a few modules
https://bugs.kde.org/show_bug.cgi?id=414231 Richard Ullger changed: What|Removed |Added CC||rull...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413838] Dolphin split view path becomes invisible when unfocused when using Krita Dark color scheme
https://bugs.kde.org/show_bug.cgi?id=413838 Richard Ullger changed: What|Removed |Added Version|unspecified |4.2.7.1 --- Comment #4 from Richard Ullger --- Krita version set to 4.2.7.1 but affects earlier versions too. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413838] Dolphin split view path becomes invisible when unfocused in dark theme
https://bugs.kde.org/show_bug.cgi?id=413838 --- Comment #2 from Richard Ullger --- Ok. The colour scheme is provided as part of the krita package. Can I reassign the bug to krita? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413838] New: Dolphin split view path becomes invisible when unfocused in dark theme
https://bugs.kde.org/show_bug.cgi?id=413838 Bug ID: 413838 Summary: Dolphin split view path becomes invisible when unfocused in dark theme Product: dolphin Version: 19.08.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: split view Assignee: dolphin-bugs-n...@kde.org Reporter: rull...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 123732 --> https://bugs.kde.org/attachment.cgi?id=123732&action=edit Dolphin split window SUMMARY Dolphin split view path becomes invisible when unfocused and the theme is set to Breeze dark. STEPS TO REPRODUCE 1. Open dolphin. 2. Click on the Split toolbar button. 3. The new split opens in the right hand side of the window and is given focus. OBSERVED RESULT The path above the left split becomes invisible. See attached screenshot. When focus is changed to the left split, the path above the left split becomes visible and the path above right split becomes invisible. EXPECTED RESULT The path above the unfocused split should remain visible. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.63.0 Qt Version: 5.14.0beta2-1 Kernel Version: 5.3.8-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5 CPU M 430 @ 2.27GHz Memory: 7.5 GiB of RAM ADDITIONAL INFORMATION Global theme: Breeze dark Colour scheme: Krita dark When set to the Breeze theme, there is no change to the path when the split focus is changed. -- You are receiving this mail because: You are watching all bug changes.