[XWaylandVideoBridge] [Bug 470431] New: Shared window gets shared as a small corner in a white window (Discord)
https://bugs.kde.org/show_bug.cgi?id=470431 Bug ID: 470431 Summary: Shared window gets shared as a small corner in a white window (Discord) Classification: Applications Product: XWaylandVideoBridge Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kdeb...@ino.to CC: aleix...@kde.org, k...@davidedmundson.co.uk Target Milestone: --- Created attachment 159332 --> https://bugs.kde.org/attachment.cgi?id=159332&action=edit Discord sharing selected window with xwayland video bridge in a conner of a white screen SUMMARY Records in a small corner of a white screen STEPS TO REPRODUCE 1. Start xwayland video bridge 2. start a discord call 3. share a application window 4. select xwayland video bridge 5. Pick a window to share 6. window gets shared inside a bigger white window OBSERVED RESULT The selected window gets shared as a small corner in a white window (Discord) EXPECTED RESULT The window is shared maximized with no visual glitches or white background. SOFTWARE/OS VERSIONS ``` inxi -b System: Host: Garuda-Linux Kernel: 6.3.4-273-tkg-bmq arch: x86_64 bits: 64 Desktop: KDE Plasma v: 5.27.5 Distro: Garuda Linux Machine: Type: Desktop Mobo: ASRock model: X470 Taichi serial: UEFI: American Megatrends v: P5.10 date: 10/20/2022 CPU: Info: 6-core AMD Ryzen 5 5600X [MT MCP] speed (MHz): avg: 4372 min/max: 2200/4650 Graphics: Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] driver: amdgpu v: kernel Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.1.1 compositor: kwin_wayland driver: N/A resolution: 1: 2048x864 2: 1536x864 3: 1536x864 API: OpenGL v: 4.6 Mesa 23.1.1 renderer: AMD Radeon RX 6700 XT (navi22 LLVM 15.0.7 DRM 3.52 6.3.4-273-tkg-bmq) Network: Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi Device-2: Intel I211 Gigabit Network driver: igb Drives: Local Storage: total: 2.96 TiB used: 4.08 TiB (138.2%) Info: Processes: 547 Uptime: 30m Memory: available: 31.26 GiB used: 17.73 GiB (56.7%) Shell: fish inxi: 3.3.27 ``` ADDITIONAL INFORMATION I posted on the GitLab as I thought this was not a kde project and thus was not being tracked here but noticed bugs. -- You are receiving this mail because: You are watching all bug changes.
[XWaylandVideoBridge] [Bug 470431] Shared window gets shared as a small corner in a white window (Discord)
https://bugs.kde.org/show_bug.cgi?id=470431 Andres changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Andres --- I figured out why this wasn't working it's because of the bismuth tilling script I have it tilling the xwaylandvideo bridge into a corner if I disable it it works. Now i need to find the window class of xwaylandvideobridge and I can add it to the do not tile list -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 469119] Bluetooth Controller not enabled on startup despite "On Login: Enable Bluetooth" Setting
https://bugs.kde.org/show_bug.cgi?id=469119 Andres changed: What|Removed |Added CC||kdeb...@ino.to -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 469119] Bluetooth Controller not enabled on startup despite "On Login: Enable Bluetooth" Setting
https://bugs.kde.org/show_bug.cgi?id=469119 --- Comment #1 from Andres --- The same issue on my system, however, the fix of setting "~/.config/bluedevilglobalrc contains a line with my adapters MAC with "_powered=" to true keeps getting reverted every time I open the Bluetooth settings in KDE. another 'fix' is after setting the powered option to true make the file read-only so that it doesn't get set to false again Operating System: Garuda Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.3.6-273-tkg-bmq (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488994] New: Kwin crashes when an application e.g game disables/block the compositor
https://bugs.kde.org/show_bug.cgi?id=488994 Bug ID: 488994 Summary: Kwin crashes when an application e.g game disables/block the compositor Classification: Plasma Product: kwin Version: git-stable-Plasma/6.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: andresd.dia...@gmail.com Target Milestone: --- SUMMARY Kwin crashes when opening games that try to disable the compositor, it causes the windows to flicker and continuously alt tab to desktop until it completely crashes and no windows can be moved or closed I have to restart the pc to fix this issue, disabling Allow applications to block compositing seems to help but it still happens on game start up. STEPS TO REPRODUCE 1. Login into plasma x11 2. Open a game that tries to disable composition e.g Minecraft or cs2 OBSERVED RESULT Windows flicker and continuously alt+ tab to the desktop and back to the game over and over, until the desktop "freezes", images still render, videos and games still move but no mouse or keyboard action trigger any type of response on opened windows. EXPECTED RESULT game runs without crashing kwin. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux 6.9.5 (available in About System) KDE Plasma Version: 6.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION Video showing the issue: https://drive.google.com/file/d/1E7E24199gFz_DTiLV7uV15Bye7TrUJgz/view?usp=drive_link Crashed process viewer: PID: 1075 (kwin_x11) UID: 1000 (andres) GID: 984 (users) Signal: 11 (SEGV) Timestamp: Sat 2024-06-22 11:07:00 CST (1min 39s 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 (andres) Boot ID: c3f7443b83844b2cbac88912a49b42ba Machine ID: fb4034a1b6a84da4989b26d8c66aa6ce Hostname: Arch Storage: /var/lib/systemd/coredump/core.kwin_x11.1000.c3f7443b83844b2cbac88912a49b42ba.1075.171907602000.zst (present) Size on Disk: 7.3M Message: Process 1075 (kwin_x11) of user 1000 dumped core. Stack trace of thread 1075: #0 0x7c146bca8e44 n/a (libc.so.6 + 0x94e44) #1 0x7c146bc50a30 raise (libc.so.6 + 0x3ca30) #2 0x7c146f4b8643 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x6643) #3 0x7c146bc50ae0 n/a (libc.so.6 + 0x3cae0) #4 0x64dc39a61b50 n/a (n/a + 0x0) #5 0x7c146c3a17e7 n/a (libQt6Core.so.6 + 0x1a17e7) #6 0x7c146c3a9975 _ZN6QTimer10timerEventEP11QTimerEvent (libQt6Core.so.6 + 0x1a9975) #7 0x7c146c38c0b9 _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x18c0b9) #8 0x7c146d2fc55c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfc55c) #9 0x7c146c344e38 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x144e38) #10 0x7c146c4c3c38 _ZN14QTimerInfoList14activateTimersEv (libQt6Core.so.6 + 0x2c3c38) #11 0x7c146c5a4599 n/a (libQt6Core.so.6 + 0x3a4599) #12 0x7c146b26da89 n/a (libglib-2.0.so.0 + 0x5ca89) #13 0x7c146b2cf9b7 n/a (libglib-2.0.so.0 + 0xbe9b7) #14 0x7c146b26cf95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95) #15 0x7c146c5a28dd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a28dd) #16 0x7c146c34f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e) #17 0x7c146c34945d _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x14945d) #18 0x64dc16925e2b n/a (/usr/bin/kwin_x11 (deleted) + 0x38e2b) #19 0x7c146bc39c88 n/a (libc.so.6 + 0x25c88) #20 0x7c146bc39d4c __libc_start_main (libc.so.6 + 0x25d4c) #21 0x64dc16929a25 n/a (/usr/bin/kwin_x11 (deleted) + 0x3ca25) Stack trace of thread 1089: #0 0x7c146bd1c39d __poll (libc.so.6 + 0x10839d) #1 0x7c146b2cf8fd n/a (libglib-2.0.so.0 + 0xbe8fd) #2 0x7c146b26cf95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95) #3 0x7c146c5a28dd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a28dd) #4 0x7c
[kwin] [Bug 488994] Kwin crashes when an application e.g game disables/block the compositor
https://bugs.kde.org/show_bug.cgi?id=488994 --- Comment #4 from Andres --- (In reply to Vlad Zahorodnii from comment #2) > I cannot reproduce the crash Is there any more information I could provide that would be helpful to you or others to reproduce this issue? I won't have access to my pc this week but I could get it to you next week. As mentioned by nebrassy this didn't used to happen in the previous version of kwin. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 478332] New: Enabling sending computer notifications to android phone breaks kde connection between the two
https://bugs.kde.org/show_bug.cgi?id=478332 Bug ID: 478332 Summary: Enabling sending computer notifications to android phone breaks kde connection between the two Classification: Applications Product: kdeconnect Version: 24.01.80 Platform: Android OS: Android 13.x Status: REPORTED Severity: crash Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: kdeb...@ino.to CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY Connection between computer and phone terminates when enabling computer notifications to be sent to phone. If I unpair the phone and repair it, it will momentarily connect before terminating after a bit. The only way to get my phone to correctly pair again is to clear the app data and cache. STEPS TO REPRODUCE 1. Pair Phone to computer 2. In KDE connect settings on the computer, enable the sending notifications plugin 3. Connection is immediately severed and will no longer connect 4. unpairing and repairing the device will connect you momentarily before the connection ends again. 5. Clear app data and cache on the Android device to allow pairing between the two devices again without the connection suddenly terminating OBSERVED RESULT Enabling sending computer notifications to Android phone breaks KDE connection between the two. EXPECTED RESULT Enabling sending computer notifications to Android phone does not breaks KDE connection between the two. SOFTWARE/OS VERSIONS Operating System: Garuda Linux KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.5-1-cachyos (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT Samsung Galaxy S23 SM-S911U One UI 6.0 Android 14 1.29.0 from the Google Play Store ADDITIONAL INFORMATION Android 14 is missing from the os selection -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470549] Error while communicating with the global shortcuts service
https://bugs.kde.org/show_bug.cgi?id=470549 Andres changed: What|Removed |Added CC||kdeb...@ino.to --- Comment #9 from Andres --- I am getting this issue after upgrading to plasma 6 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482479] New: Can not set move window to next screen to meta +
https://bugs.kde.org/show_bug.cgi?id=482479 Bug ID: 482479 Summary: Can not set move window to next screen to meta + Classification: Applications Product: systemsettings Version: 6.0.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keys Assignee: plasma-b...@kde.org Reporter: kdeb...@ino.to CC: k...@david-redondo.de Target Milestone: --- SUMMARY Can not set move window to next screen to meta + Default meta shift right works as excpected STEPS TO REPRODUCE 1. Open shortcut settings 2. find move window to next screen 3. set keybind to meta + 4. test new binding of meta + OBSERVED RESULT Nothing happens EXPECTED RESULT The window moves to the next screen Operating System: Garuda Linux KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-1-cachyos (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477939] Center-aligned panels cause left/right/top/bottom aligned panels sharing the same edge to not touch that edge
https://bugs.kde.org/show_bug.cgi?id=477939 Andres changed: What|Removed |Added CC||kdeb...@ino.to -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480862] Unable to assign numpad keys to shortcuts on Wayland
https://bugs.kde.org/show_bug.cgi?id=480862 Andres changed: What|Removed |Added Version|5.93.0 |6.0.3 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #6 from Andres --- Still not fixed on 6.0.3. Shouldn't the fix be in there? Operating System: Garuda Linux KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.2-3-cachyos (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482479] Can not set move window to next screen to meta + when zoom in is assigned meta +
https://bugs.kde.org/show_bug.cgi?id=482479 Andres changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED --- Comment #4 from Andres --- @Nicolas Fella I don't think this a dup of https://bugs.kde.org/show_bug.cgi?id=471370 as its not a problem on having to set the shortcut multiple times. In my case no amount of setting and unsettling of the move window to next screen hotkey allows me to use the meta and + keys together -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482479] Can not set move window to next screen to meta + when zoom in is assigned meta +
https://bugs.kde.org/show_bug.cgi?id=482479 --- Comment #5 from Andres --- (In reply to Andres from comment #4) > @Nicolas Fella I don't think this a dup of > https://bugs.kde.org/show_bug.cgi?id=471370 as its not a problem on having > to set the shortcut multiple times. > > In my case no amount of setting and unsettling of the move window to next > screen hotkey allows me to use the meta and + keys together `Meta` + `Shift` + `=` does work (after multiple reassigns) however which is what @fanzhuyifan reported what I am reporting is `Meta` + `+` (numpad plus) is a not working (On any shortcut actually I have tried several) this was working on 5.27.10 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482479] Can not set move window to next screen to meta + when zoom in is assigned meta +
https://bugs.kde.org/show_bug.cgi?id=482479 --- Comment #7 from Andres --- the shortcut works with non num pad keys. It seems my problem is a duplicate of https://bugs.kde.org/show_bug.cgi?id=480862? although should that be fixed on 6.0.2? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 473858] Dolphin crashes when right click or context menu key pressed over a file from Insync synced folder
https://bugs.kde.org/show_bug.cgi?id=473858 Andres changed: What|Removed |Added CC||andresmateo@gmail.com Platform|Arch Linux |Neon -- You are receiving this mail because: You are watching all bug changes.
[systemdgenie] [Bug 462616] systemdgenia blocks under spam mesages about systemPropertiesChanged: "org.freedesktop.systemd1.xxxx"
https://bugs.kde.org/show_bug.cgi?id=462616 Andres changed: What|Removed |Added CC||kdeb...@ino.to -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 453355] New: error when install themes
https://bugs.kde.org/show_bug.cgi?id=453355 Bug ID: 453355 Summary: error when install themes Product: frameworks-qqc2-desktop-style Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: andypa...@gmail.com CC: ahiems...@heimr.nl, k...@davidedmundson.co.uk, noaha...@gmail.com Target Milestone: --- Created attachment 148543 --> https://bugs.kde.org/attachment.cgi?id=148543&action=edit Error when installed theme SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Go to preferences 2. Global themes 3. try to install one OBSERVED RESULT Error on install themes EXPECTED RESULT You can chose the theme and use it SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.10 (available in About System) KDE Plasma Version: 5.24.4 ADDITIONAL INFORMATION This error happens on Kubuntu 22.04 and Kubuntu 21.10 La instalación de /tmp/BNubxq-Nordic.tar.xz ha fallado: No se ha podido instalar la dependencia: «kns://sddmtheme.knsrc/api.kde-look.org/1366843» -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 453163] New: root pass on discover sofware source error
https://bugs.kde.org/show_bug.cgi?id=453163 Bug ID: 453163 Summary: root pass on discover sofware source error Product: Discover Version: 5.24.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: andypa...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 148440 --> https://bugs.kde.org/attachment.cgi?id=148440&action=edit error after root pass entered SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Go to Discover 2. Go to Preferences 3. Click on Software Sources and put root pass OBSERVED RESULT Error always to try enter in software sources EXPECTED RESULT Open software sources and manage all preferences SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 KDE Plasma Version: 5.24.4 ADDITIONAL INFORMATION It only is happened on Kubuntu 22.04. If you use Kubuntu backport from Kubuntu 21.10 it runs perfectly -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 445017] New: Star Catalog or Density star problem
https://bugs.kde.org/show_bug.cgi?id=445017 Bug ID: 445017 Summary: Star Catalog or Density star problem Product: kstars Version: 3.5.5 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: yoandres...@hotmail.com Target Milestone: --- Created attachment 143244 --> https://bugs.kde.org/attachment.cgi?id=143244&action=edit Amount of star running Kstas in Windows vs Linux SUMMARY STEPS TO REPRODUCE 1. Donwload Tycho-2 star catalog 2. Go to Kstas Settings and in Catalg section slice the Star Density slider to maximun and apply. 3. Go back to the planetarium view and zoom in close to Crux, for example, and you won't see any additional stars. OBSERVED RESULT - Adding the Tycho-2 catalog does not add any stars to the ones that Kstars brings by default. EXPECTED RESULT - Many more stars should be seen in the planetarium view (as seen running Kstars on Linux OS). SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share
https://bugs.kde.org/show_bug.cgi?id=451050 --- Comment #43 from Andres --- recently tried repoducing https://bugs.kde.org/show_bug.cgi?id=474066 and it works fine on my system seems it was fixed at some point Operating System: Garuda Linux KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Kernel Version: 6.6.8-1-cachyos (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459468] Certain Xwayland apps do not respect third-party cursor theme on Wayland
https://bugs.kde.org/show_bug.cgi?id=459468 --- Comment #26 from Andres --- Like I said in the above reply, this is affecting me on NON-flatpaked apps such as Vivaldi and Lutris which is installed via my package manager (Pacman) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469238] When run from a global shortcut, `normcap` does not copy text to clipboard, but `normcap | tee /dev/null` does
https://bugs.kde.org/show_bug.cgi?id=469238 Andres changed: What|Removed |Added CC||kdeb...@ino.to -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 474066] New: Dolphin crash when adding Nvidia shield TV pro SMB server
https://bugs.kde.org/show_bug.cgi?id=474066
Bug ID: 474066
Summary: Dolphin crash when adding Nvidia shield TV pro SMB
server
Classification: Applications
Product: dolphin
Version: 23.08.0
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: kdeb...@ino.to
CC: kfm-de...@kde.org
Target Milestone: ---
Application: dolphin (23.08.0)
Qt Version: 5.15.10
Frameworks Version: 5.109.0
Operating System: Linux 6.4.11-1-cachyos x86_64
Windowing System: Wayland
Distribution: Garuda Linux
DrKonqi: 5.27.7 [KCrashBackend]
-- Information about the crash:
Everytime I try to mount my shields smb server dolphin crashes
Steps to reproduce
1. enable smb server on nvidia shield Settings -> Device Prefenceses -> Storage
-> Transfer files over network
2. browse to network tab in dolphin
3. enter SMB folder
4. manually add shield IP to the address bar after the smb://
5. enter credentials as shown on shields settings page
6. Dolphin crashes
The crash can be reproduced every time.
-- Backtrace:
Application: Dolphin (dolphin), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7 0x7f70acc8e8a3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8 0x7f70acc3e668 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9 0x7f70acc264b8 in __GI_abort () at abort.c:79
#10 0x7f70af260156 in KCoreDirListerCache::printDebug()
(this=this@entry=0x7f70af38a4a0
<_ZZN12_GLOBAL__N_121Q_QGS_kDirListerCache13innerFunctionEvE6holder.lto_priv.0>)
at /usr/src/debug/kio/kio-5.109.0/src/core/kcoredirlister.cpp:2095
#11 0x7f70af30a6a0 in KCoreDirListerCache::slotUpdateResult(KJob*)
(this=0x7f70af38a4a0
<_ZZN12_GLOBAL__N_121Q_QGS_kDirListerCache13innerFunctionEvE6holder.lto_priv.0>,
j=0x559c81b69ba0) at
/usr/src/debug/kio/kio-5.109.0/src/core/kcoredirlister.cpp:1734
#12 0x7f70ad6d1637 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffdcdc90030, r=, this=0x559c82b695a0, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#13 doActivate(QObject*, int, void**) (sender=0x559c81b69ba0,
signal_index=6, argv=0x7ffdcdc90030) at kernel/qobject.cpp:3925
#14 0x7f70aeafc0aa in KJob::result(KJob*, KJob::QPrivateSignal)
(this=this@entry=0x559c81b69ba0, _t1=, _t1@entry=0x559c81b69ba0,
_t2=...) at
/usr/src/debug/kcoreaddons/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#15 0x7f70aeb0207c in KJob::finishJob(bool) (this=0x559c81b69ba0,
emitResult=) at
/usr/src/debug/kcoreaddons/kcoreaddons-5.109.0/src/lib/jobs/kjob.cpp:98
#16 0x7f70ad6d1637 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffdcdc90100, r=, this=0x7f70a000eda0, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#17 doActivate(QObject*, int, void**) (sender=0x559c82c5ff20,
signal_index=7, argv=0x7ffdcdc90100) at kernel/qobject.cpp:3925
#18 0x7f70af2b297a in KIO::SlaveInterface::dispatch(int, QByteArray const&)
(this=0x559c82c5ff20, _cmd=104, rawdata=...) at
/usr/src/debug/kio/kio-5.109.0/src/core/slaveinterface.cpp:149
#19 0x7f70af2ad3ea in KIO::SlaveInterface::dispatch() (this=0x559c82c5ff20)
at /usr/src/debug/kio/kio-5.109.0/src/core/slaveinterface.cpp:78
#20 0x7f70af2afe42 in KIO::Slave::gotInput() (this=0x559c82c5ff20) at
/usr/src/debug/kio/kio-5.109.0/src/core/slave.cpp:354
#21 0x7f70ad6d1637 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffdcdc90340, r=, this=0x559c812bdb60, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#22 doActivate(QObject*, int, void**) (sender=0x559c8170ce30,
signal_index=3, argv=0x7ffdcdc90340) at kernel/qobject.cpp:3925
#23 0x7f70ad6c4174 in QObject::event(QEvent*) (this=0x559c8170ce30,
e=0x559c8128e4e0) at kernel/qobject.cpp:1347
#24 0x7f70ae37893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x559c8170ce30, e=0x559c8128e4e0) at
kernel/qapplication.cpp:3640
#25 0x7f70ad69c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x559c8170ce30, event=0x559c8128e4e0) at
kernel/qcoreapplication.cpp:1064
#26 0x7f70ad6a165b in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x559c809fe550) at
kernel/qcoreapplication.cpp:1821
#27 0x7f70ad6e76d8 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x559c80a3de60) at kernel/qeventdispatcher_glib.cpp:277
#28 0x7f70ab310a61 in g_main_dispatch (context=0x7f70aee0) at
../glib/glib/gmain.c:3460
#29 g_main_context_di
[XWaylandVideoBridge] [Bug 471244] New: No longer shows Screen picker
https://bugs.kde.org/show_bug.cgi?id=471244 Bug ID: 471244 Summary: No longer shows Screen picker Classification: Applications Product: XWaylandVideoBridge Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kdeb...@ino.to CC: aleix...@kde.org, k...@davidedmundson.co.uk Target Milestone: --- When selecting xwayland video bridge it just shares a white screen. Does not give the screen picker it used to give. STEPS TO REPRODUCE 1. install xwaylandbridge from here https://invent.kde.org/system/xwaylandvideobridge/-/jobs/1009337 2. run it 3. run discord or some other screen sharing app 4. share your screen 5. select xwaylandvideobridge 6. just shares a white screen without prompting the user what they want to share OBSERVED RESULT just shares a white screen without prompting the user what they want to share EXPECTED RESULT Prompts the user what screen or application they want to share and shares it SOFTWARE/OS VERSIONS Operating System: Garuda Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.3.8-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[XWaylandVideoBridge] [Bug 471244] No longer shows Screen picker
https://bugs.kde.org/show_bug.cgi?id=471244 Andres changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Andres --- *** This bug has been marked as a duplicate of bug 471140 *** -- You are receiving this mail because: You are watching all bug changes.
[XWaylandVideoBridge] [Bug 471140] Xwayland Video Bridge stopped working on Arch
https://bugs.kde.org/show_bug.cgi?id=471140 Andres changed: What|Removed |Added CC||kdeb...@ino.to --- Comment #7 from Andres --- *** Bug 471244 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[XWaylandVideoBridge] [Bug 471140] Xwayland Video Bridge stopped working on Arch
https://bugs.kde.org/show_bug.cgi?id=471140 --- Comment #8 from Andres --- how can I get the original working version? tried downloading from here https://invent.kde.org/davidedmundson/xwaylandvideobridge/-/jobs/853700/artifacts/browse and it still doesn't work -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459468] Certain Xwayland apps do not respect third-party cursor theme on Wayland
https://bugs.kde.org/show_bug.cgi?id=459468 Andres changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #18 from Andres --- Is this supossed to be fixed on 5.27.6? I am still encountering the issue Operating System: Garuda Linux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.3.8-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459468] Certain Xwayland apps do not respect third-party cursor theme on Wayland
https://bugs.kde.org/show_bug.cgi?id=459468 Andres changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #24 from Andres --- This still affects me with non flatpak applications such as Vivaldi and lutris -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 490584] New: kwallet GPG error was No secret key
https://bugs.kde.org/show_bug.cgi?id=490584 Bug ID: 490584 Summary: kwallet GPG error was No secret key Classification: Applications Product: kwalletmanager Version: 24.05.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: va...@kde.org Reporter: kdeb...@ino.to Target Milestone: --- Created attachment 171845 --> https://bugs.kde.org/attachment.cgi?id=171845&action=edit picture of the error SUMMARY kwallet GPG error was No secret key STEPS TO REPRODUCE 1. setup a wallet password as requested in the first time setup (at least on bazzite) 2. reboot pc 3. Check if asked for a password on next login.(sometimes it does and sometimes it doesn't when it) 4. if it does not ask for a password try to open an app that depends on the wallet 5. See error OBSERVED RESULT no password prompt on some logins followed by kwallet GPG error was No secret key EXPECTED RESULT password prompt shows on all logins and no kwallet GPG error was No secret key SOFTWARE/OS VERSIONS Operating System: Bazzite 40 KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.8-204.fsync.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 490584] kwallet GPG error was No secret key
https://bugs.kde.org/show_bug.cgi?id=490584 --- Comment #1 from Andres --- Created attachment 171846 --> https://bugs.kde.org/attachment.cgi?id=171846&action=edit Journal from the boot with the error -- You are receiving this mail because: You are watching all bug changes.
[kde-gtk-config] [Bug 382048] Not showing symlinked icon-themes
https://bugs.kde.org/show_bug.cgi?id=382048 Andres changed: What|Removed |Added CC||cont...@andresbott.com Version|5.10.3 |5.17.1 --- Comment #1 from Andres --- I found this is due to the check performed here: https://cgit.kde.org/kde-gtk-config.git/tree/src/iconthemesmodel.cpp#n50 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 422344] New: crash trying to preview a video
https://bugs.kde.org/show_bug.cgi?id=422344 Bug ID: 422344 Summary: crash trying to preview a video Product: kdenlive Version: 20.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: jaana...@hotmail.com Target Milestone: --- Created attachment 128984 --> https://bugs.kde.org/attachment.cgi?id=128984&action=edit crash report SUMMARY STEPS TO REPRODUCE 1. open kdenlivw 2. add videos 3. play video OBSERVED RESULT kdenlive crashes EXPECTED RESULT previw video SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 5.3.0-53-generic x86_64 KDE Plasma Version: KDE neon User Edition 5.18 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 494006] New: No longer opens on a Galaxy s23
https://bugs.kde.org/show_bug.cgi?id=494006 Bug ID: 494006 Summary: No longer opens on a Galaxy s23 Classification: Applications Product: kdeconnect Version: 24.08.1 Platform: Android OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: kdeb...@ino.to CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY Since latest update for the Galaxy s23 KDE connect crashes on launch. This persists even after uninstalling and reinstalling the app STEPS TO REPRODUCE 1. Update Galaxy s23 to the latest version 2. Launch KDE connect 3. See it immediately crashes OBSERVED RESULT Crashes on launch EXPECTED RESULT Doesn't crash on launch -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484323] High CPU load of kwin_x11 when locking or turning off the screen
https://bugs.kde.org/show_bug.cgi?id=484323 andres changed: What|Removed |Added CC||andres...@gmail.com --- Comment #57 from andres --- The issue is still here on my laptop with Fedora 41 and the latest packages, right now, this is: Operating System: Fedora Linux 41 (KDE Plasma) x86_64 KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.9.0 Qt Version: 6.8.1 Kernel Version: 6.12.6-200.fc41.x86_64 (64-bit) Graphics Platform: X11 Processors: AMD Ryzen 5 5500U with Radeon Graphics (12) @ 2.100GHz Memory: 16 GiB of RAM Graphics Processor: AMD ATI 03:00.0 Lucienne Manufacturer: DELL -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484323] High CPU load of kwin_x11 when locking or turning off the screen
https://bugs.kde.org/show_bug.cgi?id=484323 --- Comment #68 from andres --- Still happening with plasma 6.3 Updated my fedora 41 using sudo dnf upgrade --refresh --advisory=FEDORA-2025-c1fc288a4c OS: Fedora Linux 41 (KDE Plasma) x86_64 Host: Inspiron 15 3525 1.12.0 Kernel: 6.12.11-200.fc41.x86_64 Uptime: 5 mins Packages: 2727 (rpm), 17 (flatpak) Shell: bash 5.2.32 Resolution: 1920x1080, 1920x1080 DE: Plasma 6.3.0 WM: KWin Theme: Breeze [GTK2/3] Icons: breeze-dark [GTK2/3] Terminal: konsole CPU: AMD Ryzen 5 5500U with Radeon Graphics (12) @ 2.100GHz GPU: AMD ATI 03:00.0 Lucienne Memory: 6085MiB / 15324MiB -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449601] Allow re-arranging Virtual Desktops in new Overview effect
https://bugs.kde.org/show_bug.cgi?id=449601 --- Comment #2 from Andres Betts --- (In reply to Nate Graham from comment #1) > It's not so much a technical barrier but rather a UI barrier. > > In the Overview effect, virtual desktops are displayed as a flat > one-dimensional list due to space constraints. However this may not actually > not accurate; the true layout can be two-dimensional with any number of rows > and columns. I think before we can allow re-arranging virtual desktops, we > first need to display the true arrangement of Virtual Desktops in the > effect. Otherwise it's just too confusing. This would make sense. I might require other bug reports or some proposals. I am happy to help there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450226] New: Implement exit animation when bypassing exit confirmation screen
https://bugs.kde.org/show_bug.cgi?id=450226 Bug ID: 450226 Summary: Implement exit animation when bypassing exit confirmation screen Product: plasmashell Version: master Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: anditosan1...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Users need to be notified of the state of their system at all times. For this reason, I think when shutting down or rebooting Plasma, after selecting to bypass confirmation screens, also needs to inform the user of the state of the system. This can be done with a fade out animation and a message in the center that says "shutting down" or "rebooting". That way the user is not "janked" out of the desktop so quickly and they can follow the progression of their actions through informative prompts. Something like this: https://imgur.com/a/SaYfCuS -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 450346] New: Show Key Combos Inline
https://bugs.kde.org/show_bug.cgi?id=450346 Bug ID: 450346 Summary: Show Key Combos Inline Product: systemsettings Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_kwin_effects Assignee: kwin-bugs-n...@kde.org Reporter: anditosan1...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- I think it would be great if the key combinations for all the effects in the effects KCM were inline with the list item. That way, the user can just glance at this page and know what key combination they need to activate a specific effect. Right now, the key combination is accessible through clicking the edit button for a selected effect. If the effect is unselected, the user can't access the key combo. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 450353] New: Discover Automatic Update Needs to Follow Confirmation Screen Bypass
https://bugs.kde.org/show_bug.cgi?id=450353 Bug ID: 450353 Summary: Discover Automatic Update Needs to Follow Confirmation Screen Bypass Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: anditosan1...@gmail.com CC: aleix...@kde.org Target Milestone: --- It appears even though Plasma is set to skip the confirmation screen for shutdown, restart or log out, Discover does not follow suit when the user selects "Restart automatically after installing packages". When I was doing the updates, I selected this option and the system showed the confirmation screen anyway. However, the rest of the system is set to skip the confirmation screen. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 450353] Discover Restart Button Needs to Follow Confirmation Screen Bypass
https://bugs.kde.org/show_bug.cgi?id=450353 Andres Betts changed: What|Removed |Added Summary|Discover Automatic Update |Discover Restart Button |Needs to Follow |Needs to Follow |Confirmation Screen Bypass |Confirmation Screen Bypass -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 450353] Discover Restart Button Needs to Follow Confirmation Screen Bypass
https://bugs.kde.org/show_bug.cgi?id=450353 --- Comment #1 from Andres Betts --- CORRECTION: It is "not" automatic updates that don't follow the confirmation screen bypass, it is the actual "restart" button that appears after completing the updates inside Discover. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 450392] New: Various Edit Dialogs Need Bigger Min Window Size
https://bugs.kde.org/show_bug.cgi?id=450392 Bug ID: 450392 Summary: Various Edit Dialogs Need Bigger Min Window Size Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwin_effects Assignee: kwin-bugs-n...@kde.org Reporter: anditosan1...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- A few edit windows in the effects kcm have their window size too small for the user to make out the information they convey. These edit windows belong to the following effects: Invert Mouse Click Animation Looking Glass Magnifier Zoom Mouse Mark Thumbnail Aside Show Paint Desktop Grid (Note this edit window does not follow the vertical organization that other edit windows do) Overview All of these need a min window size that accommodates to all the elements in the edit window. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454720] New: Maximize Panel Should Cancel Floating Panel
https://bugs.kde.org/show_bug.cgi?id=454720 Bug ID: 454720 Summary: Maximize Panel Should Cancel Floating Panel Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: anditosan1...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 In the floating panel section under edit mode, the button for floating panel is clicked once for enabling floating panel and a second time to disable floating panel. When the user enters floating panel and clicks Maximize Panel, the panel does nothing. I think we need to think these buttons as opposites of each other. If floating panel undoes maximize panel, then maximize panel should undo floating panel. This would be more congruent with the options we present users with. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388206] Right Click Extract Should Extract on First Click
https://bugs.kde.org/show_bug.cgi?id=388206 --- Comment #2 from Andres Betts --- (In reply to Nate Graham from comment #1) > No extra clicks are necessary, just a little bit of mouse movement to > navigate to "Extract archive here." Right-click menus are already advanced > functionality for most users. Don't know that I agree. But your reasoning makes sense, except it is not as fast. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 392906] ToolBarApplicationHeader: Add padding between back button and left edge
https://bugs.kde.org/show_bug.cgi?id=392906 --- Comment #2 from Andres Betts --- (In reply to Nate Graham from comment #1) > I've seen this sometimes too. Not in Discover though; this is a pure > Kirigami ToolBarApplicationHeader. Got it. I hope they notice it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454272] Use Plasma Image Wallpaper plugin to choose a background for SDDM
https://bugs.kde.org/show_bug.cgi?id=454272 --- Comment #2 from Andres Betts --- (In reply to Fushan Wen from comment #1) > I am not sure if it makes sense. SDDM themes have their own backgrounds, and > where should the default background be placed among other backgrounds in a > GridView? I think what I am hinting at here is the behavior we see in mobile and other OSs where they set a global wallpaper and any location that presents the user with the same background stays the same. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450226] Implement exit/logout animation
https://bugs.kde.org/show_bug.cgi?id=450226 --- Comment #8 from Andres Betts --- (In reply to Nate Graham from comment #7) > This is a legitimate request, so it's a shame you didn't respond to my last > question and the ticket got automatically closed. Re-opening. > > We should indeed create some kind of "logging out..." effect so that the > user knows what's going on. The challenge is not covering up any windows or > dialogs that demand attention to ask the user something, such as the > ubiquitous "Save your changes" dialogs that document-based apps will show. > > Not sure if the best place for this to be implemented would be Plasmashell > (as with the logout screen) or KWin (as a systemwide effect). Starting with > Plasma for now. I am so sorry Nate, I don't get updates about my own bugs for some reason. It's been like this for a long long time. I think I should have mentioned that we are talking about the desktop behavior when the user has enabled bypass shutdown screens or bypass reboot screens. So it's not the general behavior. Under this behavior, the user is not prompted about shutting down, for example, when they click shut down. It happens immediately. This is pretty cool for people ready to leave the desktop but it is also a bit radical in its behavior. I can confirm that under this behavior the system does "NOT" ask users to save. It shuts down without interruptions. Maybe it sends a TERM signal. This is why I say that even though this behavior is enabled, it should still warn users that they are shutting down or rebooting. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 465741] New: unpredictable behavior of desktop layout and wallpaper (breeze dark) when switching between external and internal screens
https://bugs.kde.org/show_bug.cgi?id=465741 Bug ID: 465741 Summary: unpredictable behavior of desktop layout and wallpaper (breeze dark) when switching between external and internal screens Classification: Plasma Product: KScreen Version: 5.26.90 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: acimmaru...@gmail.com Target Milestone: --- Created attachment 156253 --> https://bugs.kde.org/attachment.cgi?id=156253&action=edit Breeze dark bottom panel in middle of the screen in external screen SUMMARY The bottom panel of the breeze dark theme gets placed either in the middle of the screen or dissappears entirely when switching to external or from external to internal screens (while disabling the other). The wallpaper placement is all wrong when I leave my external monitor plugged in and I reboot and log back into my system. STEPS TO REPRODUCE 1. Plug in external 4k monitor 2. Select external monitor ONLY 3. Wrong desktop layout (not always) OR 1. While using external monitor ONLY 2. Switch back to ONLY laptop screen (or unplug external monitor) 3. Bottom panel missing OBSERVED RESULT Bottom panel or bottom panel right hand side icons missing or misplaced completely EXPECTED RESULT Desktop layout should adapt to different screen SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.1.8 / X11 KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION The workaround that reliably fixes the problem is to "reload" the breeze dark theme in System Settings > Apperance -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 465741] unpredictable behavior of desktop layout and wallpaper (breeze dark) when switching between external and internal screens
https://bugs.kde.org/show_bug.cgi?id=465741 --- Comment #1 from Andres Cimmarusti --- (sorry had a typo in the original report, version of plasma is 5.26.90) This is the output of kscreen-doctor, when external monitor is enabled ONLY. $ kscreen-doctor -o Output: 65 eDP-1 disabled connected priority 0 Panel Modes: 70:3200x1800@60! 71:3200x1800@60 72:3200x1800@60 73:3200x1800@48 74:2880x1620@60 75:2880x1620@60 76:2560x1600@60 77:2560x1600@60 78:2560x1440@60 79:2560x1440@60 80:2560x1440@60 81:2560x1440@60 82:2048x1536@60 83:1920x1440@60 84:1856x1392@60 85:1792x1344@60 86:2048x1152@60 87:2048x1152@60 88:2048x1152@60 89:2048x1152@60 90:1920x1200@60 91:1920x1200@60 92:1920x1080@60 93:1920x1080@60 94:1920x1080@60 95:1920x1080@60 96:1600x1200@60 97:1680x1050@60 98:1680x1050@60 99:1400x1050@60 100:1600x900@60 101:1600x900@60 102:1600x900@60 103:1600x900@60 104:1280x1024@60 105:1400x900@60 106:1400x900@60 107:1280x960@60 108:1440x810@60 109:1440x810@60 110:1368x768@60 111:1368x768@60 112:1280x800@60 113:1280x800@60 114:1280x800@60 115:1280x800@60 116:1280x720@60 117:1280x720@60 118:1280x720@60 119:1280x720@60 120:1024x768@60 121:1024x768@60 122:960x720@60 123:928x696@60 124:896x672@60 125:1024x576@60 126:1024x576@60 127:1024x576@60 128:1024x576@60 129:960x600@60 130:960x600@60 131:960x540@60 132:960x540@60 133:960x540@60 134:960x540@60 135:800x600@60 136:800x600@60 137:800x600@56 138:840x525@60 139:840x525@60 140:864x486@60 141:864x486@60 142:700x525@60 143:800x450@60 144:800x450@60 145:640x512@60 146:700x450@60 147:700x450@60 148:640x480@60 149:640x480@60 150:720x405@60 151:720x405@59 152:684x384@60 153:684x384@60 154:640x400@60 155:640x400@60 156:640x360@60 157:640x360@60 158:640x360@60 159:640x360@59 160:512x384@60 161:512x288@60 162:512x288@60 163:480x270@60 164:480x270@60 165:400x300@60 166:400x300@56 167:432x243@60 168:432x243@60 169:320x240@60 170:360x202@60 171:360x202@59 172:320x180@60 173:320x180@59 Geometry: 0,0 3200x1800 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 66 DP-1 enabled connected priority 1 DisplayPort Modes: 90:1920x1200@60 97:1680x1050@60 104:1280x1024@60 114:1280x800@60 121:1024x768@60 136:800x600@60 149:640x480@60 2104:3840x2160@60*! 2105:3840x2160@60 2106:3840x2160@60 2107:3840x2160@30 2108:3840x2160@30 2109:3840x2160@30 2110:1920x1080@60 2111:1920x1080@50 2112:1920x1080@60 2113:1920x1080@60 2114:1920x1080@50 2115:1920x1080@60 2116:1600x900@60 2117:1440x900@60 2118:1280x720@60 2119:1280x720@50 2120:1280x720@60 2121:720x576@50 2122:720x480@60 2123:720x480@60 2124:640x480@60 2125:720x400@70 Geometry: 0,0 3840x2160 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 67 HDMI-1 disabled disconnected priority 0 HDMI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 68 HDMI-2 disabled disconnected priority 0 HDMI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 465741] unpredictable behavior of desktop layout and wallpaper (breeze dark) when switching between external and internal screens
https://bugs.kde.org/show_bug.cgi?id=465741 --- Comment #2 from Andres Cimmarusti --- Created attachment 156254 --> https://bugs.kde.org/attachment.cgi?id=156254&action=edit Breeze dark bottom panel missing when switching to laptop screen -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 465741] unpredictable behavior of desktop layout and wallpaper (breeze dark) when switching between external and internal screens
https://bugs.kde.org/show_bug.cgi?id=465741 --- Comment #3 from Andres Cimmarusti --- I guess I should also mention that I run any of these screens with 200% scaling (since support for different scaling for different screens in X11 is not easily set up in KDE plasma, nor any other open source desktop environment) And I'm also using the environment variable: PLASMA_USE_QT_SCALING=1 (for my user account only: ~/.bash_profile) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 465741] unpredictable behavior of desktop layout and wallpaper (breeze dark) when switching between external and internal screens
https://bugs.kde.org/show_bug.cgi?id=465741 --- Comment #5 from Andres Cimmarusti --- Finally had a chance to test this. The panel placement issue is not present when using wayland. There are other little glitches there, but less important -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 465741] unpredictable behavior of desktop layout and wallpaper (breeze dark) when switching between external and internal screens
https://bugs.kde.org/show_bug.cgi?id=465741 --- Comment #6 from Andres Cimmarusti --- (In reply to Nate Graham from comment #4) > Can you try Wayland? Does it happen there? Finally had a chance to test this. The panel placement issue is not present when using wayland. There are other little glitches there, but less important. And as a boon, in Wayland, different scaling per monitor is supported! -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 271934] kded4 memory leaks related to Power Management
https://bugs.kde.org/show_bug.cgi?id=271934 Andres Salcedo changed: What|Removed |Added Summary|kded4 process grows on |kded4 memory leaks related |memory usage (possible |to Power Management |leak) | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467185] New: Add Descriptions to Advanced Settings Where Possible
https://bugs.kde.org/show_bug.cgi?id=467185 Bug ID: 467185 Summary: Add Descriptions to Advanced Settings Where Possible Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_flatpak Assignee: plasma-b...@kde.org Reporter: anditosan1...@gmail.com CC: joshiesuha...@gmail.com Target Milestone: --- Even though the flatpak advanced options is an area meant for advanced users, I think it makes sense to have descriptions for the items that would seems relevant for regular users to use. Given the descriptions are not there, a user looking to fix issues with flatpaks might have less of a hint to know what to do or where to start. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466019] Allow saving tiling layouts
https://bugs.kde.org/show_bug.cgi?id=466019 Andres Betts changed: What|Removed |Added CC||anditosan1...@gmail.com --- Comment #2 from Andres Betts --- +1 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467186] New: Select Region Controls Too Transparent
https://bugs.kde.org/show_bug.cgi?id=467186 Bug ID: 467186 Summary: Select Region Controls Too Transparent Classification: Applications Product: Spectacle Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: anditosan1...@gmail.com CC: k...@david-redondo.de Target Milestone: --- New screenshot tools under select region seem a little too transparent. Against a dark background, they are harder to make out what the buttons do. I wanted to suggest using background blur for these controls. This should make them easier to parse at a glance. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 467628] New: No Wifi After Laptop Wakeup
https://bugs.kde.org/show_bug.cgi?id=467628 Bug ID: 467628 Summary: No Wifi After Laptop Wakeup Classification: Plasma Product: plasma-nm Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: anditosan1...@gmail.com Target Milestone: --- It seems for my laptop, after closing the lid and then opening back up causes an issue with the network applet in the taskbar. After wake up, the system does not reconnect. I don't have wifi. When I click the applet, I get a list of available networks but the one I use doesn't allow me to click the connect button. The button does not appear disabled. I tried clicking the connect button for other networks. While those worked, I entered the password but they did not connect to that different wifi signal. After I reboot the system, the system comes back as normal and the wifi is enabled and working as expected. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467629] New: Inconsistent Tooltip Appear Animation
https://bugs.kde.org/show_bug.cgi?id=467629 Bug ID: 467629 Summary: Inconsistent Tooltip Appear Animation Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: anditosan1...@gmail.com Target Milestone: --- I noticed this behavior today. It seems that the appear animation for tooltips is not the same for all the elements in the taskbar. Video attached shows how some appear from the left, others from the right, others from the top, etc. Not sure if the team is aware. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467629] Inconsistent Tooltip Appear Animation
https://bugs.kde.org/show_bug.cgi?id=467629 --- Comment #2 from Andres Betts --- Sorry about that. The video was too big. I thought it had been attached. Here is a link to it: https://collaborate.kde.org/s/g8HJGdyJ7nNaX7H -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467704] New: Mouse KCM Should Default to The Currently Active Mouse
https://bugs.kde.org/show_bug.cgi?id=467704 Bug ID: 467704 Summary: Mouse KCM Should Default to The Currently Active Mouse Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_mouse Assignee: plasma-b...@kde.org Reporter: anditosan1...@gmail.com Target Milestone: --- Created attachment 157523 --> https://bugs.kde.org/attachment.cgi?id=157523&action=edit mousekcm It seems that the mouse kcm doesn't default to the settings for the mouse currently being used. It confused me as I believed I was editing the settings for the right mouse. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467704] Mouse KCM Should Default to The Currently Active Mouse
https://bugs.kde.org/show_bug.cgi?id=467704 --- Comment #2 from Andres Betts --- I was on a desktop with 2 mice. Only one of them was active but the mouse drop down had the inactive mouse first. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467185] Add Descriptions to Advanced Settings Where Possible
https://bugs.kde.org/show_bug.cgi?id=467185 --- Comment #3 from Andres Betts --- Yes, if possible. They don't have to be too long but enough to give a good hint to users about their use. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467704] Mouse KCM Should Default to The Currently Active Mouse
https://bugs.kde.org/show_bug.cgi?id=467704 --- Comment #4 from Andres Betts --- I think it would mean the one with the most recent record of movement. They are both "active" in the sense that they are recorded in the system and the system can receive input from both. However, I am thinking that there could be a clever way the system knows which one you are currently manipulating the system with and should automatically change to that as the default option in the KCM. You have to think that this is not as intuitive as we have a dropdown menu for the mouse list which only shows 1 option at a time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467629] Inconsistent Tooltip Appear Animation
https://bugs.kde.org/show_bug.cgi?id=467629 --- Comment #4 from Andres Betts --- When I do that, the slide animation goes away, but I get a weird stutter on the appear effect for the tooltip. Video attached. The behavior is still inconsistent across the panel. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467629] Inconsistent Tooltip Appear Animation
https://bugs.kde.org/show_bug.cgi?id=467629 --- Comment #5 from Andres Betts --- https://collaborate.kde.org/s/myxxKwYFfBJqnjE -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470610] New: Not enough contrast between breeze and overview effect background
https://bugs.kde.org/show_bug.cgi?id=470610 Bug ID: 470610 Summary: Not enough contrast between breeze and overview effect background Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: anditosan1...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Overview effect background should use more contrast to make windows more visible. Notice the contrast ratio fail that we see in the attached images. Also, for people with blurry vision, it's harder to make out what you see on the screen when you have too much of one color. Solutions are to change the background to a tint of black or use more transparency. Images: https://ibb.co/2yyv1Qf https://ibb.co/WyGgYfr -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470610] Not enough contrast between breeze and overview effect background
https://bugs.kde.org/show_bug.cgi?id=470610 --- Comment #2 from Andres Betts --- I don't think your logic is applicable in this case. You're assuming that people only focus on the content inside a window to determine their contents and also assume that people with blurry vision would not use our system. The blurry test was only to illustrate at a lower resolution how little difference there is between the window background and overview background. The background has been the same for me for a while even across multiple installs, I am not really sure the overview background is changing for me unless Neon unstable has a bug. We also have to think of defaults in this case. I get these results with the default combination of wallpaper, breeze style and overview enabled. I only added links to images because bugzilla didn't seem to allow more than one image. I could be wrong. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469591] New: Tab + Enter not working consistently in Kickoff
https://bugs.kde.org/show_bug.cgi?id=469591 Bug ID: 469591 Summary: Tab + Enter not working consistently in Kickoff Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: anditosan1...@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 It appears that tab + Enter does not work in Kickoff in all areas. When tabbing through the interface I selected the session icons for sleep, restart, shut down and they would not activate when hitting ENTER. However, tab to select applications did work when hitting ENTER. Wayland, latest unstable build. Neon. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 469636] New: Xwayland Crash on Wayland Unstable (Neon)
https://bugs.kde.org/show_bug.cgi?id=469636 Bug ID: 469636 Summary: Xwayland Crash on Wayland Unstable (Neon) Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: anditosan1...@gmail.com Target Milestone: --- Not sure what causes it but this is the output: PID: 1241 (Xwayland) UID: 1000 (andyb) GID: 1000 (andyb) Signal: 6 (ABRT) Timestamp: Thu 2023-05-11 15:24:39 EDT (23s ago) Command Line: /usr/bin/Xwayland :1 -auth /run/user/1000/xauth_OVHIHs -listen 65 -listen 66 -displayfd 56 -rootless -wm 60 Executable: /usr/bin/Xwayland Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service Unit: user@1000.service User Unit: plasma-kwin_wayland.service Slice: user-1000.slice Owner UID: 1000 (andyb) Boot ID: d12e825cb7da4d2a9db60c6c1a00c9f0 Machine ID: c3a40342ab074f99b61f8431914d49e4 Hostname: andy-rogzephyrusg14ga402rjga402rj Storage: /var/lib/systemd/coredump/core.Xwayland.1000.d12e825cb7da4d2a9db60c6c1a00c9f0.1241.168383307900.zst (present) Disk Size: 2.7M Message: Process 1241 (Xwayland) of user 1000 dumped core. Found module linux-vdso.so.1 with build-id: 064f675240880ede3e41c47c0b792a6601be18d0 Found module libpciaccess.so.0 with build-id: 4c93da952f83c1d085d4bdead692db544c79b004 Found module libdrm_intel.so.1 with build-id: 19b1ca240326d9a2e4fa5d8a46dc567880af84f3 Found module libdrm_nouveau.so.2 with build-id: a7835058d1e7ca987ea3c3f79339a2e9a4581239 Found module libdrm_amdgpu.so.1 with build-id: 40ea9dc003e771f3a5961a6290184d2bf07ef1c0 Found module libelf.so.1 with build-id: 0eaf2d056fb292c3da2d99fa16c13d0ec798f121 Found module libdrm_radeon.so.1 with build-id: 4b636f4f611e48e4b593f1677256f25f3481a63f Found module libsensors.so.5 with build-id: 0d5803327d5e32a301844fb819fd3c762f8e69f6 Found module libzstd.so.1 with build-id: 5d9d0d946a3154a748e87e17af9d14764519237b Found module radeonsi_dri.so with build-id: 2bfe8d16607e4a288458009b0d007e10514c999f Found module libicudata.so.70 with build-id: b1c2496dd0543023c7a19c961bb7f3abc818f465 Found module liblzma.so.5 with build-id: b85da6c48eb60a646615392559483b93617ef265 Found module libicuuc.so.70 with build-id: bef3ff1d70aadd68aab07d858a759360c8b919ae Found module libxml2.so.2 with build-id: 1cf4a22fbe15a77baca28e9c824592b8b5d852ff Found module libtinfo.so.6 with build-id: 5bc463a93df92725301f9399eea90bb6fc987b34 Found module libedit.so.2 with build-id: 9fcc3490de1a1f4919b1f6e398c99c7fa25f6863 Found module libstdc++.so.6 with build-id: f57e02bfadacc0c923c82457d5e18e1830b5faea Found module libLLVM-15.so.1 with build-id: b23af1ea3dcc63f22e69adfd4d5857ef7174261c Found module libxcb-sync.so.1 with build-id: 657d8516621c4042b4b221ce1b3525f92467ef7e Found module libxcb-present.so.0 with build-id: a4f415af56b06f1f38d5a0339dd9828ff136b115 Found module libxcb-dri3.so.0 with build-id: b6aa69fda711358025ae4dd29fa597866d29b8c5 Found module libxcb-xfixes.so.0 with build-id: d6f264cc06fb6c92b5ced2c8f373cf5a5bda0e09 Found module libxcb-randr.so.0 with build-id: 7af27bf3e608d5c06645ad4086788afe8a8447e7 Found module libxcb-dri2.so.0 with build-id: dc5a2c2b0c9080fff87ea241e7298a7ac2f838e3 Found module libX11-xcb.so.1 with build-id: 916a9b062e61b0310210ae16428615ebbe01c87d Found module libglapi.so.0 with build-id: 2d75b274fbcd459e128cd4ed99ac7f00205c Found module libEGL_mesa.so.0 with build-id: 529ca855c7d81401f9975f16ddb9e684e20b0854 Found module libEGL.so.1 with build-id: 236d96c92ee2914a0e90e06e01b79dfcba0f7b41 Found module libgcc_s.so.1 with build-id: 09c4935b79388431a1248f6a98e00d7dc81b8513 Found module libxcb.so.1 with build-id: 1bef862a339557aa16c34c7a4b27f8f3aea90517 Found module libresolv.so.2 with build-id: 7fd7253c61aa6fce2b7e13851c15afa14a5ab160 Found module libkeyutils.so.1 with build-id: ff27227afa5eeddccab180dd29bd7fcff94aea7c Found module libbrotlicommon.so.1 with build-id: 43a72967cf84155914c8b3e915926733d1e57c11 Found module libX11.so.6 with build-id: b8d9314a7185312e4813abcac67d8b68ae2fd690 Found module libkrb5support.so.0 with build-id: 60c3bf331f85f4be0c25e70
[plasmashell] [Bug 469591] Tab + Enter not working consistently in Kickoff
https://bugs.kde.org/show_bug.cgi?id=469591 --- Comment #2 from Andres Betts --- Can we say that it should always be the space bar and "not" the enter key? Because then, right now, the enter key works to launch items in kickoff. I think you're saying that it should be the spacebar. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 469636] Xwayland Crash on Wayland Unstable (Neon)
https://bugs.kde.org/show_bug.cgi?id=469636 --- Comment #2 from Andres Betts --- It seems to me that this is "fixed". I reinstalled Neon dev unstable and the problem is gone. IDK. It could have been anecdotal. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478370] New: Incorrect cursor sizing representation under Wayland
https://bugs.kde.org/show_bug.cgi?id=478370 Bug ID: 478370 Summary: Incorrect cursor sizing representation under Wayland Classification: Applications Product: systemsettings Version: 5.90.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_cursortheme Assignee: plasma-b...@kde.org Reporter: anditosan1...@gmail.com Target Milestone: --- Created attachment 164080 --> https://bugs.kde.org/attachment.cgi?id=164080&action=edit CursorSizing SUMMARY *** The cursor KCM has incorrect or non-correlated cursor sizes in its toolbar size selector. Screenshot attached. The representation in the dropdown is not the same as the actual cursor (next to it in screenshot) and still suffers from sizing issues noted here: https://bugs.kde.org/show_bug.cgi?id=439439 This is still a bug in Plasma 6. *** STEPS TO REPRODUCE 1. Access cursor KCM 2. Select cursor size 3. Notice the difference between the 24px selected in the dropdown vs your actual cursor EXPECTED RESULT Sizing should be consistent -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478513] New: Wallpaper Add Toolbar Disappears
https://bugs.kde.org/show_bug.cgi?id=478513 Bug ID: 478513 Summary: Wallpaper Add Toolbar Disappears Classification: Applications Product: systemsettings Version: 5.90.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: kcm_wallpaper Assignee: plasma-b...@kde.org Reporter: anditosan1...@gmail.com CC: me...@kde.org, n...@kde.org Target Milestone: --- SUMMARY *** Under wayland and using the wallpaper KCM, when users go to the add button to add custom images to the list of wallpapers, for some reason the toolbar disappears if you add more than one image consecutively. I was able to reproduce the error a couple of times and it was solved by reopening system settings. The toolbar should not disappear. I asked about this from other contributors who did not experience the same issue even though they were also in the unstable build for Plasma 6. *** STEPS TO REPRODUCE 1. Access System Settings 2. Access wallpaper KCM 3. Choose to ADD custom images 4. Try until you notice the add button disappears (For me, this was after 2 images added consecutively) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477941] Plasma crashes in ShellCorona::createWaitingPanels() after connecting the external display
https://bugs.kde.org/show_bug.cgi?id=477941 Andres Betts changed: What|Removed |Added CC||anditosan1...@gmail.com --- Comment #3 from Andres Betts --- In talking to @nicofe I think I am experiencing something similar. https://pastebin.com/qhKypGXR -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478622] New: Provide an option to turn off stylus indicator on screen
https://bugs.kde.org/show_bug.cgi?id=478622 Bug ID: 478622 Summary: Provide an option to turn off stylus indicator on screen Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_tablet Assignee: plasma-b...@kde.org Reporter: anditosan1...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY *** I wanted to suggest having a feature in the tablet KCM to turn off the graphic that appears to indicate the stylus position on the screen. I think sometimes, this graphic can get in the way. I think sometimes users want to work through touch and there are very few people who don't touch the screen with a stylus before they interact with the screen. The graphic helps appears before users touch the screen and I don't see a lot of value there. However, I know it's good for a few people so that's why I wanted to suggest having this as an option and not the default. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 478253] Finished updates disappear, but still occupy space
https://bugs.kde.org/show_bug.cgi?id=478253 Andres Betts changed: What|Removed |Added Ever confirmed|0 |1 CC||anditosan1...@gmail.com Status|REPORTED|CONFIRMED --- Comment #1 from Andres Betts --- This also happens on my machine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478875] Cannot login by pressing enter/return
https://bugs.kde.org/show_bug.cgi?id=478875 Andres Betts changed: What|Removed |Added CC||anditosan1...@gmail.com --- Comment #1 from Andres Betts --- I checked for this and it's not happening in Fedora rawhide. FYI. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 479920] network-wired should have less monitor, more wire
https://bugs.kde.org/show_bug.cgi?id=479920 --- Comment #21 from Andres Betts --- Can you write out the list of icons needed in total and their names? Sorry for dropping this. I have been pretty busy. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 487595] Breeze icon theme uses copyrighted icons without acknowledgement or compliance with the owners' guidelines
https://bugs.kde.org/show_bug.cgi?id=487595 Andres Betts changed: What|Removed |Added CC||anditosan1...@gmail.com --- Comment #1 from Andres Betts --- I think something we have to remember is what type of graphic we are speaking of. Sometimes they are referring to their logo graphic which is not the same as their icon graphic. Some companies don't provide an icon graphic. In which case, you have to make something similar that would fit the bill. However, a few companies provide their own icon graphic for various sizes, in which case, we should simply copy/paste into the icon collection for our system. Sometimes these icons contain a TM graphic as well. For reference, I did just that on the 24px collection for icons belonging to other companies. Just copy paste, no modifications. The 22px collection had the same, but I can't ascertain if they came from a company source or from a modified icon source. Unsure. Still, the icons belonging to companies should probably not be re-licensed. I hope that's clear LOGO is not the same as ICON. Those are two different graphics. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 487595] Breeze icon theme uses copyrighted icons without acknowledgement or compliance with the owners' guidelines
https://bugs.kde.org/show_bug.cgi?id=487595 --- Comment #3 from Andres Betts --- Adam, I appreciate your analysis and you're welcome to contact a lawyer that could explain this to us here. It's no problem. From your comments, I think you're speaking of something different than what we have and do at KDE. I would like to see how our use case fits or doesn't fit your assumptions around the legal ramifications of the icon use. Send the legal expert our way and we can review. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487760] New: Exit edit mode only by using final calls to action like exit edit mode
https://bugs.kde.org/show_bug.cgi?id=487760 Bug ID: 487760 Summary: Exit edit mode only by using final calls to action like exit edit mode Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Edit Mode toolbar Assignee: plasma-b...@kde.org Reporter: anditosan1...@gmail.com Target Milestone: 1.0 SUMMARY In the current edit mode interaction, when the user closes the panel edit dialog, edit mode closes. When the user clicks the widget sidebar to close it, this closes edit mode. This leads to users who are not done in edit mode to have to constantly reopen edit mode to do more tasks. Given that the edit mode concentrates a few interactions into one main edit interaction, the user should not exit edit mode involuntarily. Instead, the user should click on the final call to action, such as "exit edit mode" and then close the interaction. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487760] Exit edit mode only by using final calls to action like exit edit mode
https://bugs.kde.org/show_bug.cgi?id=487760 --- Comment #1 from Andres Betts --- I forgot to mention that the escape key can also be the way to exit edit mode. It would be esc key until all dialogs are closed. When none are left, the user should exit edit mode. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487760] Exit edit mode only by using final calls to action like exit edit mode
https://bugs.kde.org/show_bug.cgi?id=487760 --- Comment #3 from Andres Betts --- I submitted it here because it's a ux bug. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 481632] Add a number next to the wi-fi icon to indicate wi-fi generation technology that is in use.
https://bugs.kde.org/show_bug.cgi?id=481632 Andres Betts changed: What|Removed |Added CC||anditosan1...@gmail.com --- Comment #3 from Andres Betts --- In the context of the desktop, a number symbol at the bottom right could indicate how many wifi networks are available. A sum of networks rather than a version number. It would feel redundant since we have a detail view just a click away. I don't think it's common practice for UIs to show version numbers prominently either. They are just updated and you have new functions but icons don't tend to display version numbers. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 486116] New: Discover does not respect screenshot delay
https://bugs.kde.org/show_bug.cgi?id=486116 Bug ID: 486116 Summary: Discover does not respect screenshot delay Classification: Applications Product: Discover Version: master Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: anditosan1...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY In today's unstable builds in Fedora, Spectacle appears not to be respecting screenshots delays and takes screenshots immediately on clicking the specific kind of screenshot. STEPS TO REPRODUCE 1. Access Discover 2. Change delay seconds 3. Attempt to take a screenshot with any choice -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471010] Battery Monitor shows wrong remaining time
https://bugs.kde.org/show_bug.cgi?id=471010 Andres Rivas changed: What|Removed |Added CC||andres@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475255] Selecting a power profile through the battery & Brightness applet doesn't work correctly; works using `powerprofilesctl`
https://bugs.kde.org/show_bug.cgi?id=475255 Andres Rivas changed: What|Removed |Added CC||andres@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475255] Selecting a power profile through the battery & Brightness applet doesn't work correctly; works using `powerprofilesctl`
https://bugs.kde.org/show_bug.cgi?id=475255 --- Comment #17 from Andres Rivas --- To add to this bug, I'm experiencing it on kubuntu 23.10, either installed and live cd, but not on kubuntu 22.04 nor 24.04 live cds: === BUG PRESENT === Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-28-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 7.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: LENOVO Product Name: 20X4S27300 System Version: ThinkPad L15 Gen 2 === BUG NOT PRESENT 1 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 6.5.0-18-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 7.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics === BUG NOT PRESENT 2 Operating System: Kubuntu 24.04 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.8.0-31-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 7.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: LENOVO Product Name: 20X4S27300 System Version: ThinkPad L15 Gen 2 === Diyou's workaround of restarting plasma seems to work, but its kind of inconvenient -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 479920] network-wired should have less monitor, more wire
https://bugs.kde.org/show_bug.cgi?id=479920 --- Comment #28 from Andres Betts --- Created attachment 168985 --> https://bugs.kde.org/attachment.cgi?id=168985&action=edit Network icon with red X -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 486116] Discover does not respect screenshot delay
https://bugs.kde.org/show_bug.cgi?id=486116 --- Comment #2 from Andres Betts --- My bad Noah, I meant to say "Spectacle" Not sure why I wrote Discover. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 484969] Weather and brightness/night light's icons are easily confused
https://bugs.kde.org/show_bug.cgi?id=484969 Andres Betts changed: What|Removed |Added CC||anditosan1...@gmail.com --- Comment #3 from Andres Betts --- Would it also be a good thing to create a dedicated icon set for weather? I think right now, our collection doesn't contain a lot of that and is reusing icons intended for other purposes. Material has these: https://icon-sets.iconify.design/?query=weather (Filter for Material) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 484969] Weather and brightness/night light's icons are easily confused
https://bugs.kde.org/show_bug.cgi?id=484969 --- Comment #8 from Andres Betts --- Maybe I can review them. What do these weather icons go by? Are they 22px? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 484969] Weather and brightness/night light's icons are easily confused
https://bugs.kde.org/show_bug.cgi?id=484969 --- Comment #33 from Andres Betts --- Would it be ok if we propose or discuss these icons via gitlab? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 479920] network-wired should have less monitor, more wire
https://bugs.kde.org/show_bug.cgi?id=479920 --- Comment #23 from Andres Betts --- Created attachment 168374 --> https://bugs.kde.org/attachment.cgi?id=168374&action=edit icons 16px -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 479920] network-wired should have less monitor, more wire
https://bugs.kde.org/show_bug.cgi?id=479920 --- Comment #24 from Andres Betts --- Created attachment 168375 --> https://bugs.kde.org/attachment.cgi?id=168375&action=edit Icons 32px -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 479920] network-wired should have less monitor, more wire
https://bugs.kde.org/show_bug.cgi?id=479920 --- Comment #26 from Andres Betts --- - In network-wired-unavailable, was it intentional to use a black X instead of a red X? Usually our X badges are red. Yes, because even in the current 22px it's not consistent. I can make it red if there is more red than black in the icon set. Let me know. - network-wired, network-wired-active, and network-wired-available look the same (or am I just not seeing any differences?) so the latter two could just be symlinks to network-wired, right? Yes because it seemed to me that there is no need to make one different visually than the other. Maybe there is a case for that, let me know. - Could you also include 22px versions? That's the size that these will be displayed at most commonly in the panel, so it's important to have that size. 22px versions are contained in this attachment: wired network variant icons -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 479920] network-wired should have less monitor, more wire
https://bugs.kde.org/show_bug.cgi?id=479920 --- Comment #11 from Andres Betts --- Ok, sounds good! I will work on this during the weekend. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 479920] network-wired should have less monitor, more wire
https://bugs.kde.org/show_bug.cgi?id=479920 --- Comment #12 from Andres Betts --- Created attachment 165317 --> https://bugs.kde.org/attachment.cgi?id=165317&action=edit wired-network Here is a new rendition. Let me know of any edits. -- You are receiving this mail because: You are watching all bug changes.
