[plasmashell] [Bug 487912] plasma X11 session is not restored after logout/login
https://bugs.kde.org/show_bug.cgi?id=487912 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 336990] Chromium and Firefox does not remember their virtual desktops on session restore
https://bugs.kde.org/show_bug.cgi?id=336990 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358277] when run in XWayland, Chrome PWA apps use the icon from chrome browser in Icon-Only Task Manager, but remain correctly separate
https://bugs.kde.org/show_bug.cgi?id=358277 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 15329] Save and remember positions of all windows
https://bugs.kde.org/show_bug.cgi?id=15329 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 487566] Kcalc doesn't chain result into next calculation anymore
https://bugs.kde.org/show_bug.cgi?id=487566 Michal Pácal changed: What|Removed |Added CC||mic...@pacal.cz -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 484639] Fallback to Breeze ignored by KIconLoader because of wrong global initialization order
https://bugs.kde.org/show_bug.cgi?id=484639 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482142] drag in drop files in Google Chrome renders Chrome unusable
https://bugs.kde.org/show_bug.cgi?id=482142 Michal Sylwester changed: What|Removed |Added CC||msylwes...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434363] Implement all context menu options present in KSysGuard's Processes view
https://bugs.kde.org/show_bug.cgi?id=434363 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 479332] No keyboard navigation to and through process list
https://bugs.kde.org/show_bug.cgi?id=479332 Michal Kec (MiK) changed: What|Removed |Added Version|5.27.10 |6.0.4 CC||k...@kecnet.cz --- Comment #2 from Michal Kec (MiK) --- I can second this. There's no easy way to list & control processes in Plasma since KSysGuard widget removal in Plasma 6 (KDE Neon). I consider the new System Monitor a handy tool for its - well system monitoring - tasks. Neat charts, great customization. But for this task it is too slow and heavy. Main issues are keyboard navigation and the performance mentioned at bug #479321. I also miss the possibility to watch the system monitor charts and process list at the same time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 Michal Hlavac changed: What|Removed |Added CC||m...@hlavki.eu -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 479321] Poor responsiveness of System Monitor under heavy CPU and IO load
https://bugs.kde.org/show_bug.cgi?id=479321 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484323] High CPU load of kwin_x11 when locking the screen
https://bugs.kde.org/show_bug.cgi?id=484323 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484606] High CPU usage on kwin_x11/Xorg when screen is off
https://bugs.kde.org/show_bug.cgi?id=484606 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485076] The Pie Chart widget display style is too thin after an update, without an option to configure the thickness
https://bugs.kde.org/show_bug.cgi?id=485076 --- Comment #1 from Michal Pácal --- Created attachment 168196 --> https://bugs.kde.org/attachment.cgi?id=168196=edit Look of the same three widgets before the update Added second attachment showing status before the last update for comparison (showing this really is a regression). Note that originally the circles were about two to three times wider (estimate based on looking at them). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485076] New: The Pie Chart widget display style is too thin after an update, without an option to configure the thickness
https://bugs.kde.org/show_bug.cgi?id=485076 Bug ID: 485076 Summary: The Pie Chart widget display style is too thin after an update, without an option to configure the thickness Classification: Plasma Product: plasmashell Version: 6.0.3 Platform: Manjaro OS: Linux Status: REPORTED Keywords: regression, usability Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: mic...@pacal.cz CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 Created attachment 168177 --> https://bugs.kde.org/attachment.cgi?id=168177=edit Look of three widges on a panel after the update STEPS TO REPRODUCE 1. Add system monitor sensor applet/widget on a panel 2. Use "Pie Chart" Display Style 3. Update to Plasma 6.0.3 / KDE Gear 24.02 OBSERVED RESULT The thickness of the pie chart circle decreases substantially, making it harder to "read". EXPECTED RESULT The thickness stays the same across versions, or there is an option to configure the thickness of the circle. SOFTWARE/OS VERSIONS Linux: Manjaro (Testing Update 2024-04-04) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 ADDITIONAL INFORMATION Graphics Platform: X11 Display resolution: 2560x1440 (reproduced on other screen resolutions as well) Global scale: 125% (reproduced on 100% as well) Plasma panel height: 45 (reproduced on other heights as well) -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 440515] Icons on HiDPI screens are blurry
https://bugs.kde.org/show_bug.cgi?id=440515 Michal Hlavac changed: What|Removed |Added CC|m...@hlavki.eu | -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 462307] File icons are drawn at wrong position if desktop scaling is active
https://bugs.kde.org/show_bug.cgi?id=462307 Michal Hlavac changed: What|Removed |Added CC||m...@hlavki.eu -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 440515] Icons on HiDPI screens are blurry
https://bugs.kde.org/show_bug.cgi?id=440515 Michal Hlavac changed: What|Removed |Added CC||m...@hlavki.eu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461176] Applications don't prompt to save unsaved work when logging out on Wayland, causing data loss
https://bugs.kde.org/show_bug.cgi?id=461176 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 469049] link failure on ppc64 (big endian) valgrind 3.20
https://bugs.kde.org/show_bug.cgi?id=469049 Michal changed: What|Removed |Added CC||hramr...@gmail.com --- Comment #10 from Michal --- Created attachment 159912 --> https://bugs.kde.org/attachment.cgi?id=159912=edit additional patch It does not really help. memcheck also fails to link, and when that is resolved callgrind fails to link [ 145s] ../coregrind/link_tool_exe_linux 0x5800 gcc -O2 -Wall -U_FORTIFY_SOURCE -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -g -o callgrind-ppc64be-linux -flto=auto -m64 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wcast-align -Wcast-qual -Wwrite-strings -Wempty-body -Wformat -Wformat-signedness -Wformat-security -Wignored-qualifiers -Wmissing-parameter-type -Wlogical-op -Wenum-conversion -Wimplicit-fallthrough=2 -Wold-style-declaration -finline-functions -fno-stack-protector -fno-strict-aliasing -fno-builtin -I../cachegrind -static -nodefaultlibs -nostartfiles -u _start -m64 callgrind_ppc64be_linux-bb.o callgrind_ppc64be_linux-bbcc.o callgrind_ppc64be_linux-callstack.o callgrind_ppc64be_linux-clo.o callgrind_ppc64be_linux-context.o callgrind_ppc64be_linux-costs.o callgrind_ppc64be_linux-debug.o callgrind_ppc64be_linux-dump.o callgrind_ppc64be_linux-events.o callgrind_ppc64be_linux-fn.o callgrind_ppc64be_linux-jumps.o callgrind_ppc64be_linux-main.o callgrind_ppc64be_linux-sim.o callgrind_ppc64be_linux-threads.o ../coregrind/libcoregrind-ppc64be-linux.a ../VEX/libvex-ppc64be-linux.a -lgcc ../coregrind/libgcc-sup-ppc64be-linux.a [ 145s] /usr/lib64/gcc/powerpc64-suse-linux/13/../../../../powerpc64-suse-linux/bin/ld: /tmp/ccaULq5i.ltrans1.ltrans.o: in function `vgCallgrind_instrument': [ 145s] /home/abuild/rpmbuild/BUILD/valgrind-3.21.0/callgrind/../coregrind/m_machine.c:2393: undefined reference to `vgCallgrind_setup_bbcc' [ 145s] /usr/lib64/gcc/powerpc64-suse-linux/13/../../../../powerpc64-suse-linux/bin/ld: /tmp/ccaULq5i.ltrans1.ltrans.o:/home/abuild/rpmbuild/BUILD/valgrind-3.21.0/callgrind/../coregrind/m_machine.c:2393: undefined reference to `vgCallgrind_setup_bbcc' [ 145s] collect2: error: ld returned 1 exit status [ 145s] make[3]: *** [Makefile:1119: callgrind-ppc64be-linux] Error 1 [ 145s] make[3]: Leaving directory '/home/abuild/rpmbuild/BUILD/valgrind-3.21.0/callgrind' [ 145s] make[3]: *** Waiting for unfinished jobs [ 156s] make[3]: Entering directory '/home/abuild/rpmbuild/BUILD/valgrind-3.21.0/callgrind' [ 156s] ../coregrind/link_tool_exe_linux 0x5800 gcc -O2 -Wall -U_FORTIFY_SOURCE -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -g -o callgrind-ppc32-linux -flto=auto -m32 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wcast-align -Wcast-qual -Wwrite-strings -Wempty-body -Wformat -Wformat-signedness -Wformat-security -Wignored-qualifiers -Wmissing-parameter-type -Wlogical-op -Wenum-conversion -Wimplicit-fallthrough=2 -Wold-style-declaration -finline-functions -fno-stack-protector -fno-strict-aliasing -fno-builtin -I../cachegrind -static -nodefaultlibs -nostartfiles -u _start -m32 callgrind_ppc32_linux-bb.o callgrind_ppc32_linux-bbcc.o callgrind_ppc32_linux-callstack.o callgrind_ppc32_linux-clo.o callgrind_ppc32_linux-context.o callgrind_ppc32_linux-costs.o callgrind_ppc32_linux-debug.o callgrind_ppc32_linux-dump.o callgrind_ppc32_linux-events.o callgrind_ppc32_linux-fn.o callgrind_ppc32_linux-jumps.o callgrind_ppc32_linux-main.o callgrind_ppc32_linux-sim.o callgrind_ppc32_linux-threads.o ../coregrind/libcoregrind-ppc32-linux.a ../VEX/libvex-ppc32-linux.a -lgcc ../coregrind/libgcc-sup-ppc32-linux.a [ 156s] make[3]: Leaving directory '/home/abuild/rpmbuild/BUILD/valgrind-3.21.0/callgrind' [ 156s] make[2]: *** [Makefile:1637: all-recursive] Error 1 [ 156s] make[1]: *** [Makefile:914: all-recursive] Error 1 [ 156s] make: *** [Makefile:777: all] Error 2 [ 156s] error: Bad exit status from /var/tmp/rpm-tmp.jTkwVz (%build) -- You are receiving this mail because: You are watching all bug changes.
[plasma-pass] [Bug 470152] New: Incorrect latest version tag
https://bugs.kde.org/show_bug.cgi?id=470152 Bug ID: 470152 Summary: Incorrect latest version tag Classification: Plasma Product: plasma-pass Version: 1.2.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: dvra...@kde.org Reporter: m...@hlavki.eu Target Milestone: --- SUMMARY *** Latest version tag in git scm is v0.2.1 instead of v1.2.1 https://invent.kde.org/plasma/plasma-pass/-/tags *** -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 391462] Wrong search behaviour
https://bugs.kde.org/show_bug.cgi?id=391462 Michal Hlavac changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #21 from Michal Hlavac --- This does not work. Searching for artists e.g. "Björk" with the search prefix "Bjo" shows empty result. -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 468986] google contacts in kaddressbook, missing address, website, notes, etc.
https://bugs.kde.org/show_bug.cgi?id=468986 Michal Hlavac changed: What|Removed |Added CC||m...@hlavki.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468460] GDK applications start with 96 dpi in X11
https://bugs.kde.org/show_bug.cgi?id=468460 Michal Hlavac changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #13 from Michal Hlavac --- env: SHELL=/bin/bash SESSION_MANAGER=local/hlknb:@/tmp/.ICE-unix/2822,unix/hlknb:/tmp/.ICE-unix/2822 WINDOWID=32505869 QT_SCREEN_SCALE_FACTORS=eDP-1=1; COLORTERM=truecolor SDK_HOME=/usr/lib64/jvm/java XDG_CONFIG_DIRS=/data/home/hlavki/.config/kdedefaults:/etc/xdg:/usr/local/etc/xdg:/usr/etc/xdg LESS=-M -I -R XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session1 JDK_HOME=/usr/lib64/jvm/java GTK_IM_MODULE=cedilla MACHTYPE=x86_64-suse-linux G_BROKEN_FILENAMES=1 HOSTNAME=hlknb HISTSIZE=1000 binary_input=/data/home/hlavki/.sdkman/tmp/mvnd-1.0-m6-m39.bin LANGUAGE=en_US FROM_HEADER= MINICOM=-c on JAVA_ROOT=/usr/lib64/jvm/java JAVA_HOME=/usr/lib64/jvm/java VDPAU_DRIVER=va_gl AUDIODRIVER=pulseaudio JRE_HOME=/usr/lib64/jvm/java SSH_AUTH_SOCK=/tmp/ssh-XX4KYfF6/agent.2636 GRADLE_HOME=/data/home/hlavki/.sdkman/candidates/gradle/current CPU=x86_64 SHELL_SESSION_ID=a58314a482e24f61bc6f9ada60f6f978 JAVA_BINDIR=/usr/lib64/jvm/java/bin ANT_HOME=/data/home/hlavki/.sdkman/candidates/ant/current SDKMAN_CANDIDATES_DIR=/data/home/hlavki/.sdkman/candidates XMODIFIERS=@im=local DESKTOP_SESSION=/usr/share/xsessions/plasma5 SSH_AGENT_PID=2755 GTK_RC_FILES=/etc/gtk/gtkrc:/data/home/hlavki/.gtkrc:/data/home/hlavki/.config/gtkrc XCURSOR_SIZE=36 GPG_TTY=/dev/pts/1 GTK_MODULES=canberra-gtk-module XDG_SEAT=seat0 PWD=/data/home/hlavki QEMU_AUDIO_DRV=pa XDG_SESSION_DESKTOP=KDE LOGNAME=hlavki XDG_SESSION_TYPE=x11 MANPATH=/usr/local/man:/usr/share/man SYSTEMD_EXEC_PID=2822 XAUTHORITY=/run/user/1000/xauth_OMiiHt LS_OPTIONS=-N --color=tty -T 0 XKEYSYMDB=/usr/X11R6/lib/X11/XKeysymDB zip_output=/data/home/hlavki/.sdkman/tmp/mvnd-1.0-m6-m39.zip GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/data/home/hlavki/.gtkrc-2.0:/data/home/hlavki/.config/gtkrc-2.0 XNLSPATH=/usr/share/X11/nls HOME=/data/home/hlavki SSH_ASKPASS=/usr/libexec/ssh/ssh-askpass LANG=sk_SK.UTF-8 LS_COLORS=no=00:fi=00:di=01;34:ln=00;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=41;33;01:ex=00;32:*.cmd=00;32:*.exe=01;32:*.com=01;32:*.bat=01;32:*.btm=01;32:*.dll=01;32:*.tar=00;31:*.tgz=00;31:*.arc=00;31:*.arj=00;31:*.taz=00;31:*.lha=00;31:*.lz4=00;31:*.lzh=00;31:*.lzma=00;31:*.tlz=00;31:*.txz=00;31:*.tzo=00;31:*.t7z=00;31:*.zip=00;31:*.z=00;31:*.Z=00;31:*.dz=00;31:*.gz=00;31:*.lrz=00;31:*.lz=00;31:*.lzo=00;31:*.xz=00;31:*.zst=00;31:*.tzst=00;31:*.bz2=00;31:*.bz=00;31:*.tbz=00;31:*.tbz2=00;31:*.tz=00;31:*.deb=00;31:*.rpm=00;31:*.jar=00;31:*.war=00;31:*.ear=00;31:*.sar=00;31:*.rar=00;31:*.alz=00;31:*.ace=00;31:*.zoo=00;31:*.cpio=00;31:*.7z=00;31:*.rz=00;31:*.cab=00;31:*.wim=00;31:*.swm=00;31:*.dwm=00;31:*.esd=00;31:*.asf=01;35:*.avi=01;35:*.bmp=01;35:*.cgm=01;35:*.dl=01;35:*.emf=01;35:*.flc=01;35:*.fli=01;35:*.flv=01;35:*.gif=01;35:*.gl=01;35:*.jpeg=01;35:*.jpg=01;35:*.m2v=01;35:*.m4v=01;35:*.mjpeg=01;35:*.mjpg=01;35:*.mkv=01;35:*.mng=01;35:*.mov=01;35:*.mp4=01;35:*.mp4v=01;35:*.mpeg=01;35:*.mpg=01;35:*.nuv=01;35:*.ogm=01;35:*.pbm=01;35:*.pcx=01;35:*.pgm=01;35:*.png=01;35:*.ppm=01;35:*.qt=01;35:*.rm=01;35:*.rmvb=01;35:*.svg=01;35:*.svgz=01;35:*.tga=01;35:*.tif=01;35:*.tiff=01;35:*.vob=01;35:*.webm=01;35:*.webp=01;35:*.wmv=01;35:*.xbm=01;35:*.xcf=01;35:*.xpm=01;35:*.xwd=01;35:*.yuv=01;35:*.ogv=01;35:*.ogx=01;35:*.aiff=00;32:*.ape=00;32:*.aac=00;32:*.au=00;32:*.flac=00;32:*.m4a=00;32:*.mid=00;32:*.midi=00;32:*.mka=00;32:*.mp3=00;32:*.mpc=00;32:*.ogg=00;32:*.ra=00;32:*.voc=00;32:*.wav=00;32:*.wma=00;32:*.wv=00;32:*.oga=00;32:*.opus=00;32:*.spx=00;32:*.xspf=00;32: XDG_CURRENT_DESKTOP=KDE KONSOLE_DBUS_SERVICE=:1.44 PYTHONSTARTUP=/etc/pythonstart KONSOLE_DBUS_SESSION=/Sessions/2 PROFILEHOME= JBANG_HOME=/data/home/hlavki/.sdkman/candidates/jbang/current SDKMAN_VERSION=5.16.0 OSTYPE=linux XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0 QT_IM_SWITCHER=imsw-multi LESS_ADVANCED_PREPROCESSOR=no INVOCATION_ID=1a656a219d3a421088819d7e9ad42c73 NNTPSERVER=news KONSOLE_VERSION=221203 GROOVY_HOME=/data/home/hlavki/.sdkman/candidates/groovy/current MANAGERPID=2615 XSESSION_IS_UP=yes KDE_SESSION_UID=1000 LESSCLOSE=lessclose.sh %s %s XDG_SESSION_CLASS=user TERM=xterm-256color G_FILENAME_ENCODING=@locale,UTF-8,ISO-8859-15,CP1252 HOST=hlknb XAUTHLOCALHOSTNAME=hlknb LESSOPEN=lessopen.sh %s USER=hlavki COLORFGBG=15;0 KDE_SESSION_VERSION=5 PAM_KWALLET5_LOGIN=/run/user/1000/kwallet5.socket MORE=-sl MAVEN_HOME=/data/home/hlavki/.sdkman/candidates/maven/current SDKMAN_DIR=/data/home/hlavki/.sdkman CSHEDIT=emacs DISPLAY=:0 SHLVL=1 WINDOWMANAGER=/usr/bin/startplasma-x11 PAGER=less ANDROID_SDK_ROOT=/data/home/hlavki/Programs/Android/Sdk/ QT_IM_MODULE=xim XDG_VTNR=7 SDKMAN_CANDIDATES_API=https://api.sdkman.io/2 XDG_SESSION_ID=3 LC_CTYPE=en_US.UTF-8
[systemsettings] [Bug 468460] GDK applications start with 96 dpi in X11
https://bugs.kde.org/show_bug.cgi?id=468460 --- Comment #12 from Michal Hlavac --- Created attachment 158104 --> https://bugs.kde.org/attachment.cgi?id=158104=edit x11 screenshot firefox dolphin -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468460] GDK applications start with 96 dpi in X11
https://bugs.kde.org/show_bug.cgi?id=468460 --- Comment #10 from Michal Hlavac --- > How it will behave if I have multiple displays in Wayland with different DPI? I meant this question how it will behave when I change the global scale to e.g. 175%. Will it adjust DPI to the display dpi? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468460] GDK applications start with 96 dpi in X11
https://bugs.kde.org/show_bug.cgi?id=468460 --- Comment #9 from Michal Hlavac --- If you look on "x11 screenshot" attachment, you can see that Plasma runs with dpi 192, but Firefox uses 96. So somehow plasma knows what is real DPI of my display. So I would expect that when I run Firefox or another GTK application in plasma, it also uses dpi 192. Why plasma in X11 detects display DPI and in Wayland doesn't? In wayland it runs completely with dpi 96. How it will behave if I have multiple displays in Wayland with different DPI? I am just trying to understand how it works, because it behaves differently in almost every release after 5.27.x thank you for your hard work on plasma. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468460] GDK applications start with 96 dpi in X11
https://bugs.kde.org/show_bug.cgi?id=468460 --- Comment #7 from Michal Hlavac --- The only settings I did is new file /etc/sddm.conf.d/hidpi.conf: [Wayland] EnableHiDPI=true [X11] EnableHiDPI=true -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468460] GDK applications start with 96 dpi in X11
https://bugs.kde.org/show_bug.cgi?id=468460 Michal Hlavac changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #6 from Michal Hlavac --- '~/.Xsession': No such file or directory -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468460] GDK applications start with 96 dpi in X11
https://bugs.kde.org/show_bug.cgi?id=468460 --- Comment #5 from Michal Hlavac --- Created attachment 158082 --> https://bugs.kde.org/attachment.cgi?id=158082=edit kdeglobals -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468460] GDK applications start with 96 dpi in X11
https://bugs.kde.org/show_bug.cgi?id=468460 --- Comment #4 from Michal Hlavac --- Created attachment 158081 --> https://bugs.kde.org/attachment.cgi?id=158081=edit kcmfonts -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468460] GDK applications start with 96 dpi in X11
https://bugs.kde.org/show_bug.cgi?id=468460 --- Comment #2 from Michal Hlavac --- Ok, then I would expect that all applications run with dpi 96. Why plasma & all KDE applications run with DPI 192? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468460] New: GDK applications start with 96 dpi in X11
https://bugs.kde.org/show_bug.cgi?id=468460 Bug ID: 468460 Summary: GDK applications start with 96 dpi in X11 Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Startup process Assignee: plasma-b...@kde.org Reporter: m...@hlavki.eu CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 158065 --> https://bugs.kde.org/attachment.cgi?id=158065=edit x11 screenshot Using X11 and after upgrade framework to 5.105 GDK applications (Firefox, Chrome, etc) starts with DPI 96. As workaround I use GDK_SCALE=1 firefox Plasma: 5.27.4 Framework: 5.105 In wayland whole desktop environment starts with dpi 96. Force DPI font is OFF. hlavki@hlknb:~> dump_xsettings Gdk/UnscaledDPI 98304 Gdk/WindowScalingFactor 1 Gtk/ButtonImages 1 Gtk/CursorThemeName "breeze_cursors" Gtk/CursorThemeSize 36 Gtk/DecorationLayout "icon:minimize,maximize,close" Gtk/EnableAnimations 1 Gtk/FontName "Noto Sans, 8" Gtk/MenuImages 1 Gtk/PrimaryButtonWarpsSlider 0 Gtk/ToolbarStyle 3 Net/IconThemeName "Papirus" Net/ThemeName "Breeze" hlavki@hlknb:~> ps aux | grep -iE 'xsettings|kded' hlavki 22696 1.3 0.4 2202624 154352 ? Ssl 22:22 0:01 /usr/bin/kded5 hlavki 22794 0.0 0.0 7656 4480 ?S22:22 0:00 /usr/bin/xsettingsd hlavki 25977 0.0 0.0 6528 2304 pts/1S+ 22:24 0:00 grep --color=auto -iE xsettings|kded Global Scale: 100% Screenshot is in attachment. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466463] Different scaling on HiDpi display for applications in 5.27.1
https://bugs.kde.org/show_bug.cgi?id=466463 --- Comment #33 from Michal Hlavac --- Sorry, the cause of my problem was file ~/.Xresources with Xft.dpi: 192 When I removed it, it works as expected. thanks -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466463] Different scaling on HiDpi display for applications in 5.27.1
https://bugs.kde.org/show_bug.cgi?id=466463 --- Comment #31 from Michal Hlavac --- Force DPI is off. https://paste.opensuse.org/pastes/462da4efefda -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466463] Different scaling on HiDpi display for applications in 5.27.1
https://bugs.kde.org/show_bug.cgi?id=466463 --- Comment #29 from Michal Hlavac --- Hi Luca, I run primary on X11. But I tried Wayland and there it looks like all Plasma and also GTK applications runs with DPI 96. X11 output: hlavki@hlknb:~> dump_xsettings Gdk/UnscaledDPI 98304 Gdk/WindowScalingFactor 1 Gtk/ButtonImages 1 Gtk/CursorThemeName "breeze_cursors" Gtk/CursorThemeSize 36 Gtk/DecorationLayout "icon:minimize,maximize,close" Gtk/EnableAnimations 1 Gtk/FontName "Noto Sans, 8" Gtk/MenuImages 1 Gtk/PrimaryButtonWarpsSlider 0 Gtk/ToolbarStyle 3 Net/IconThemeName "Papirus" Net/ThemeName "Breeze" hlavki@hlknb:~> ps aux | grep -iE 'xsettings|kded' hlavki 22696 1.3 0.4 2202624 154352 ? Ssl 22:22 0:01 /usr/bin/kded5 hlavki 22794 0.0 0.0 7656 4480 ?S22:22 0:00 /usr/bin/xsettingsd hlavki 25977 0.0 0.0 6528 2304 pts/1S+ 22:24 0:00 grep --color=auto -iE xsettings|kded Global Scale: 100% Wayland output: Gdk/UnscaledDPI 98304 Gdk/WindowScalingFactor 1 Gtk/ButtonImages 1 Gtk/CursorThemeName "breeze_cursors" Gtk/CursorThemeSize 36 Gtk/DecorationLayout "icon:minimize,maximize,close" Gtk/EnableAnimations 1 Gtk/FontName "Noto Sans, 8" Gtk/MenuImages 1 Gtk/PrimaryButtonWarpsSlider 0 Gtk/ToolbarStyle 3 Net/IconThemeName "Papirus" Net/ThemeName "Breeze" hlavki 26573 0.8 0.4 2273276 149968 ? Ssl 22:25 0:00 /usr/bin/kded5 hlavki 26627 0.0 0.0 7668 4224 ?S22:25 0:00 /usr/bin/xsettingsd hlavki 28704 0.0 0.0 6528 2304 pts/2S+ 22:27 0:00 grep --color=auto -iE xsettings|kded Global Scale: 100% -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466463] Different scaling on HiDpi display for applications in 5.27.1
https://bugs.kde.org/show_bug.cgi?id=466463 --- Comment #27 from Michal Hlavac --- After upgrading to framework 5.105 all GTK application runs with dpi 96. Plasma: 5.27.4 Framework: 5.105 Qt: 5.15.8 Kernel: 6.2.9 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438191] Deprecate the concept of icons in the Plasma theme
https://bugs.kde.org/show_bug.cgi?id=438191 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457847] kwin becomes unresponsive, need to restart session
https://bugs.kde.org/show_bug.cgi?id=457847 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466463] Different scaling on HiDpi display for applications in 5.27.1
https://bugs.kde.org/show_bug.cgi?id=466463 --- Comment #4 from Michal Hlavac --- Thanks Luca, would be really great to have it in 5.27.2, anyway maybe a kind of workaround for GTK3+ & java applications is to run: GDK_SCALE=2 program or echo "GDK_SCALE=2" >> ~/.profile this basically saves my work life. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466463] Different scaling on HiDpi display for applications in 5.27.1
https://bugs.kde.org/show_bug.cgi?id=466463 Michal Hlavac changed: What|Removed |Added Summary|Different scaling for |Different scaling on HiDpi |applications in 5.27.1 |display for applications in ||5.27.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466463] New: Different scaling for applications in 5.27.1
https://bugs.kde.org/show_bug.cgi?id=466463 Bug ID: 466463 Summary: Different scaling for applications in 5.27.1 Classification: Plasma Product: kwin Version: 5.27.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: m...@hlavki.eu Target Milestone: --- Created attachment 156754 --> https://bugs.kde.org/attachment.cgi?id=156754=edit Different scale for some applications SUMMARY *** Using OpenSUSE Tumbleweed X11 with plasma 5.27.1 and fonts for QT applications has different dpi, e.g. menu has correct dpi, but kmail, or ksettings has wrong dpi. Also for GTK applications I must use GDK_SCALE=2 to scale correctly. In wayland scaling unified, but also wrong. It looks like it uses dpi 96, so everything is small. *** STEPS TO REPRODUCE 1. Login to plasma using 4K monitor. 2. Try some applications 3. OBSERVED RESULT see screenshot EXPECTED RESULT Unified scaling. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed (20230224) (available in About System) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8+kde160 ADDITIONAL INFORMATION Screenshot in attachment. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and turns black for 30 seconds on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #55 from Michal Ziabkowski --- For what it's worth, this seems to be fixed in Plasma 5.27. Even with my sleep workaround disabled, I get my wallpaper instantly, just like expected. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466127] New: Tiling configuration works erratically on cloned screens
https://bugs.kde.org/show_bug.cgi?id=466127 Bug ID: 466127 Summary: Tiling configuration works erratically on cloned screens Classification: Plasma Product: kwin Version: 5.27.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Custom Tiling Assignee: kwin-bugs-n...@kde.org Reporter: mz...@o2.pl CC: notm...@gmail.com Target Milestone: --- SUMMARY I have two screens - a monitor (the primary screen) and a TV (which clones the primary screen). When I change the splits in tiling settings dialog, they seem to be changed not for the primary screen, but the other one. The end result is that the config changes don't apply. What I mean by this is that when I drag a window holding Shift, the new splits I've just added aren't there. Looking looking at kwinrc, I have two tiling sections for each screen: [Tiling][112a321c-1187-5b40-909d-f3bcef9080fa] - which seems to be TV [Tiling][8e33597a-6e65-5852-ba3f-f97b7fd8a401] - which is the monitor (primary screen) When changing the settings, they get applied to the first section (the TV), although it's not the primary screen. If I copy the tile settings to the second section (the monitor) and restart kwin, the new splits appear as intended. Additionally, the config dialog doesn't seem to update. It only shows changes after I restart kwin. This might also be related to the issue of settings being applied to the wrong screen. STEPS TO REPRODUCE 1. Set up a primary screen and a cloned screen 2. Open the tiling config dialog 3. Add new splits OBSERVED RESULT Splits aren't added for the primary screen, but the cloned one EXPECTED RESULT The config dialog shows the current (primary) screen and changes are applied to it SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.13 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.10-gentoo (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 23.4 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1650/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 Michal Wazgird changed: What|Removed |Added CC||cyry...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425154] Setting an application to open application/octet-stream has unexpected behavior
https://bugs.kde.org/show_bug.cgi?id=425154 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 383168] Message Window Minimal Font Size doesn't work on HiDPi
https://bugs.kde.org/show_bug.cgi?id=383168 Michal Hlavac changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Michal Hlavac --- This bug was already solved. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 462112] Restore unsaved (newly opened - "Untilted") document doesn't work when Plasma session is restored
https://bugs.kde.org/show_bug.cgi?id=462112 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 455447] krusader with >=kio-5.95.0 is not able to open archives (rar, zip, 7z) any more
https://bugs.kde.org/show_bug.cgi?id=455447 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461162] Plasma theme highlight effect doesn't appear on hover in Present Windows effect
https://bugs.kde.org/show_bug.cgi?id=461162 --- Comment #15 from Michal Ziabkowski --- For what it's worth, changing my mouse back to libinput didn't change anything. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461162] Plasma theme highlight effect doesn't appear on hover in Present Windows effect
https://bugs.kde.org/show_bug.cgi?id=461162 --- Comment #14 from Michal Ziabkowski --- Created attachment 153467 --> https://bugs.kde.org/attachment.cgi?id=153467=edit Screencast of the Overview effect on a clean account -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461162] Plasma theme highlight effect doesn't appear on hover in Present Windows effect
https://bugs.kde.org/show_bug.cgi?id=461162 --- Comment #13 from Michal Ziabkowski --- Created attachment 153466 --> https://bugs.kde.org/attachment.cgi?id=153466=edit Screencast of Present Windows on a clean account -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461162] Plasma theme highlight effect doesn't appear on hover in Present Windows effect
https://bugs.kde.org/show_bug.cgi?id=461162 --- Comment #12 from Michal Ziabkowski --- Okay, so I tried creating a new user and starting afresh. I don't get the hover effect even on a totally stock Plasma 5.26 config. Attaching screencasts for this and the overview effect. One thing that is non-standard on my system that should not have any bearing on this is that I'm using evdev instead of libinput for my mouse, since the latter lacked some options I needed. Just thought I'd mention this just to be on the safe side. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461162] Plasma theme highlight effect doesn't appear on hover in Present Windows effect
https://bugs.kde.org/show_bug.cgi?id=461162 --- Comment #11 from Michal Ziabkowski --- (In reply to Nate Graham from comment #10) > Oh, I thought from your first comment that you had modified the file locally. > > I'm at a loss to explain why this one single feature is missing the typical > Plasma theme highlight effect on hover, but it works everywhere else. > > Do you see the highlight effect in the Overview effect? I did in fact edit the qml file, but reverted it immediately after noticing it didn't help. Anyway, the overview effect doesn't have the highlight either. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461162] No hover effect in Present Windows effect
https://bugs.kde.org/show_bug.cgi?id=461162 --- Comment #9 from Michal Ziabkowski --- (In reply to Nate Graham from comment #8) > That's odd. It sounds like the highlight effect exists and is being applied > to other things correctly, but not Present Windows. > > Can you clear the cache with `rm ~/.cache/*plasma*`, reboot, and try again? > > Also is it possible that your local overrides have interfered with this? Can > you revert to the distro package version too? Thanks! Clearing the cache and rebooting didn't fix it. What do you mean with local overrides? I'm using the Plasma 5.26 packages from the Gentoo official repo. All I did was unmask 5.26, since 5.25 is the current stable version in Gentoo. Should I downgrade to 5.25.5 then? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461162] No hover effect in Present Windows effect
https://bugs.kde.org/show_bug.cgi?id=461162 --- Comment #7 from Michal Ziabkowski --- (In reply to Nate Graham from comment #6) > Do you see a highlight effect on hover for list and grid items in Kickoff, > or for thumbnails in the Task Manager tooltips, or for list items in System > Tray popups? I don't use Kickoff, but the Application Menu. But I do see a hover effect on the pinned apps to the left of the list and on the list items. I also see it for the systray popup and when hovering over task icons. I have the task thumbnails disabled, so I have no tooltips. What I've tried: switching the Plasma theme, color scheme, window decorations. Nothing helped. Maybe this depends on a kwin effect or a config setting I have disabled? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461162] No hover effect in Present Windows effect
https://bugs.kde.org/show_bug.cgi?id=461162 --- Comment #5 from Michal Ziabkowski --- (In reply to Nate Graham from comment #4) > Thanks. What Plasma theme are you using? I'm using a third-party theme called IOTA-Plasma, but for the sake of testing I've just now switched to Breeze and it doesn't seem to make a difference. I'm still not getting the highlight effect. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461162] No hover effect in Present Windows effect
https://bugs.kde.org/show_bug.cgi?id=461162 --- Comment #3 from Michal Ziabkowski --- Created attachment 153377 --> https://bugs.kde.org/attachment.cgi?id=153377=edit Screencast showing the problem -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461162] No hover effect in Present Windows effect
https://bugs.kde.org/show_bug.cgi?id=461162 --- Comment #2 from Michal Ziabkowski --- (In reply to Nate Graham from comment #1) > It has a highlight effect that appears behind the window when hovered. Are > you not seeing that? Yeah, I'm not seeing this at all. Uploading a short screencast for reference. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461162] New: No hover effect in Present Windows effect
https://bugs.kde.org/show_bug.cgi?id=461162
Bug ID: 461162
Summary: No hover effect in Present Windows effect
Classification: Plasma
Product: kwin
Version: 5.26.2
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: effects-present-windows
Assignee: kwin-bugs-n...@kde.org
Reporter: mz...@o2.pl
Target Milestone: ---
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
***
After upgrading from Plasma 5.24 to 5.26, I've noticed that the newly rewritten
Present Windows effect has no visual feedback when hovering the cursor over a
thumbnail. In the old one the hovered item was enlarged and highlighted, which
felt much more organic.
I've tried editing windowview/qml/main.qml and adding this to the
windowThumbnail definition, to no avail:
HoverHandler{
onHoveredChanged: {
if(hovered){
windowThumbnail.scale = 1.2
}
else{
windowThumbnail.scale = 1
}
}
The new effect seems to otherwise work fine, except for this blemish. Are there
any plans to restore the old behavior in some form or is this a bug on my end?
STEPS TO REPRODUCE
1. Activate the Present Windows effect
2. Hover the mouse cursor over one of the window thumbnails
OBSERVED RESULT
There is no animation for the hovered thumbnail.
EXPECTED RESULT
The hovered thumbnail shows visual feedback.
SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux 2.9
KDE Plasma Version: 5.26.2
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.5
Kernel Version: 5.15.71-gentoo (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 23.4 GiB of RAM
Graphics Processor: NVIDIA GeForce GT 1030/PCIe/SSE2
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 364414] Google calendar resource incorrectly refresh events
https://bugs.kde.org/show_bug.cgi?id=364414 --- Comment #3 from Michal Hlavac --- Hi Justin, thanks, I think it works now. I already forgot this issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460159] With a dark color scheme, Telegram's Tray icon color switches back to black after the app has been running for some time
https://bugs.kde.org/show_bug.cgi?id=460159 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 460182] Telegram system tray icon looks dark
https://bugs.kde.org/show_bug.cgi?id=460182 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454004] On login, Widget resets to using Pie Chart display style after manually setting it to use Line Chart display style
https://bugs.kde.org/show_bug.cgi?id=454004 --- Comment #17 from Michal Hlavac --- It works after latest snapshot update 20220911. https://lists.opensuse.org/archives/list/fact...@lists.opensuse.org/message/XAWANZS6DH3UAQ2VENEGR2YCUYHY3OYA/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454004] On login, Widget resets to using Pie Chart display style after manually setting it to use Line Chart display style
https://bugs.kde.org/show_bug.cgi?id=454004 Michal Hlavac changed: What|Removed |Added CC||m...@hlavki.eu --- Comment #16 from Michal Hlavac --- hi, I am using openSUSE Tumbleweed with plasma 5.25.5 and this error is still present. thanks -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 390450] sftp connect don't read ~/.ssh/config correctly
https://bugs.kde.org/show_bug.cgi?id=390450 Michal Hlavac changed: What|Removed |Added Version|18.04.3 |22.08.0 CC||m...@hlavki.eu --- Comment #6 from Michal Hlavac --- Does not work for me. If I have ~/.ssh/config Host server1 HostName 192.168.1.10 User root IdentityFile ~/.ssh/id_rsa IdentitiesOnly yes when I wrote to dolphin: sftp://server1, it says: Failed to resolve hostname server1 (Name or service not known) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 408563] Provide option for day/night color theme switching
https://bugs.kde.org/show_bug.cgi?id=408563 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #51 from Michal Ziabkowski --- I've added a 5-second delay before plasma-plasmashell.service is run with this override: [Service] ExecStartPre=sleep 5 While not ideal, this seems to have worked around my missing wallpaper bug. This confirms my theory that plasmashell is starting too early, before screens are properly configured. I have no clue how one would properly resolve this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #50 from Michal Ziabkowski --- Yes, unfortunately Plasma 5.25 didn't fix anything for me. Still getting a black background for the first 30 or so seconds. It doesn't even have to be a full reboot. Logging out and in again also causes the issue to happen. Tried to make sure plasma-plasmashell and plasma-kwin_x11 start after plasma-kscreen by adding this systemd config override for each (what I alluded to in comment #44): [Unit] After=plasma-kscreen.service Wants=plasma-kscreen.service While it didn't break anything, it didn't fix the bug either. Looking at the timestamps, all three services seem to be starting concurrently still, so I guess the override didn't work. Can anyone familiar with the code weigh in on where the 30 second timeout before the containment fixes itself comes from? I see a TimeoutSec=40sec in plasma-plasmashell.service, but that can't be it, right? The shell does start and the panel is present, it's just the wallpaper that's missing, so it's not as though the entire service is timing out. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 452840] Pressing F3 to view an ods always crash and close Krusader. Same on all document files from libreoffice, like .ods, odf, odt...
https://bugs.kde.org/show_bug.cgi?id=452840 Michal Kuncl changed: What|Removed |Added CC||michal.ku...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 452840] Pressing F3 to view an ods always crash and close Krusader. Same on all document files from libreoffice, like .ods, odf, odt...
https://bugs.kde.org/show_bug.cgi?id=452840 --- Comment #1 from Michal Kuncl --- Created attachment 149816 --> https://bugs.kde.org/attachment.cgi?id=149816=edit New crash information added by DrKonqi krusader (2.7.2 "Peace of Mind") using Qt 5.15.4 - What I was doing when the application crashed: Tried to open a libreoffice ODT document renamed to zip via viewer -- Backtrace (Reduced): #4 0x7f027ee12572 in QObject::setProperty(char const*, QVariant const&) () from /usr/lib/libQt5Core.so.5 #5 0x7f020a51c519 in Kerfuffle::LoadJob::onFinished(bool) () from /usr/lib/libkerfuffle.so.22 #6 0x7f027ee09430 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #7 0x7f027f88da7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #8 0x7f027ede5b28 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #46 from Michal Ziabkowski --- I'm currently on Plasma 5.24.5. And I'm fairly positive that I've been getting the black background consistently ever since upgrading to the 5.24 series. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #44 from Michal Ziabkowski --- A little update: the situation seems to have changed in that now I reliably get a black background which fixes itself in about 30 seconds. Which begs the question - is there some kind of preset timeout somewhere in plasma-shell or kscreen code, after which the outputs are re-probed or the containment is updated? Unlike what I reported earlier, now the behavior is totally reproducible. My educated guess is that there is a race condition between plasma-shell and kscreen. The latter is probably reconfiguring my other screen to be 1080p AFTER Plasma is already running and the containment has been created. I haven't mentioned it, since it didn't seem relevant at the time, but I'm using systemdBoot=true. It's probably worth seeing if forcing plasma-kscreen.service to start before plasma-plasmashell.service (but after plasma-kwin_x11.service, I assume?) changes anything. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock
https://bugs.kde.org/show_bug.cgi?id=435113 Michal S changed: What|Removed |Added CC||michalmax1...@gmail.com --- Comment #73 from Michal S --- I also have similar issues, the speed is saved in the plasma's settings, but when my bluetooth mouse reconnects they are not applied, but when i change the settings and click apply then it works. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 452828] New: Fedora 35
https://bugs.kde.org/show_bug.cgi?id=452828 Bug ID: 452828 Summary: Fedora 35 Product: kcalc Version: 21.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ete...@alum.rit.edu Reporter: eka...@gmail.com Target Milestone: --- Created attachment 148283 --> https://bugs.kde.org/attachment.cgi?id=148283=edit Insufficient space for: "Dzielenie modulo". Maybe leave jus "Modulo". Insufficient space for: "Dzielenie modulo". Maybe leave jus "Modulo". I think it is understandable for Poles 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. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Polish translation of Kcalc -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 439285] Bad request, Google replied "Contacts API is being deprecated"
https://bugs.kde.org/show_bug.cgi?id=439285 Michal Hlavac changed: What|Removed |Added CC||m...@hlavki.eu -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 451851] Column headers are nearly invisible in dark colour scheme
https://bugs.kde.org/show_bug.cgi?id=451851 michal.nik...@heuthes.pl changed: What|Removed |Added CC||michal.nik...@heuthes.pl -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 451851] New: Column headers are nearly invisible in dark colour scheme
https://bugs.kde.org/show_bug.cgi?id=451851 Bug ID: 451851 Summary: Column headers are nearly invisible in dark colour scheme Product: krusader Version: 2.7.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: michal.nik...@heuthes.pl CC: krusader-bugs-n...@kde.org Target Milestone: --- Created attachment 147698 --> https://bugs.kde.org/attachment.cgi?id=147698=edit Picture with marked titles, but PrintScr makes Krusader inactive so title is visible. I use Krusader with dark blue scheme and I cannot change colour of title of columns (Name, Extension, Size, Change Date). It is visible when Krusader is not active, when I work in other window: grey font on dark blue background. But when I work in Krusader window it is dark grey font on dark blue and is nearly invisible. It changed after I upgraded from Fedora 34 to Fedora 35. I tried to change colours in Krusader settings, but I have not found setting for column titles. In attachment there is picture with marked titles, but PrintScr makes Krusader inactive so titles are visible. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 344374] Allways one same tab in all split views
https://bugs.kde.org/show_bug.cgi?id=344374 Michal Dvorak changed: What|Removed |Added CC||midvok...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416140] Sub-pixel font rendering shows "RGB" in the KCM, but is not actually applied
https://bugs.kde.org/show_bug.cgi?id=416140 Michal Dvorak changed: What|Removed |Added CC||midvok...@gmail.com --- Comment #45 from Michal Dvorak --- I also had a problem to set the RGB subpixel rendering in Debian 11 with KDE and I guess it's this bug when KDE Fonts Settings doesn't set the ```"rgba" property in fonts.conf file. I fixed it by generating the file by the utility **qt5ct** which creates the correct config file. I described it here: https://unix.stackexchange.com/questions/690088/how-to-enable-rgb-subpixel-font-anti-aliasing-in-kde-plasma -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #42 from Michal Ziabkowski --- It seems I've spoken too soon. The bug still appears, but seems much harder to trigger without multiple activities. I've gone through several reboots not being able to replicate it until it suddenly happened. So while multiple activities seem to exacerbate the issue, the only real constant is having multiple screens. Is there anything else I could to help debug this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #41 from Michal Ziabkowski --- After testing for a few days, I can say pretty conclusively that removing the second activity seems to have resolved the issue. So whatever it is, it seems to be triggered by the combination of multi-screen (different native resolutions might also be at play) AND multiple activities. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #40 from Michal Ziabkowski --- Created attachment 146126 --> https://bugs.kde.org/attachment.cgi?id=146126=edit kactivitymanagerdrc Also attaching my kactivitymanagerdrc (before removing the second activity) for reference. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #39 from Michal Ziabkowski --- Created attachment 146124 --> https://bugs.kde.org/attachment.cgi?id=146124=edit appletsrc after a few reboots I'm attaching my appletsrc after a few reboots with the other screen turned on, just in case. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #38 from Michal Ziabkowski --- I've found something that might also be related. My systemd journal (I'm using the systemd session) has a dozen or so instances of this just a few seconds after boot: plasmashell[584]: requesting unexisting screen 2 Moreover, I'm getting the same message with screen -1 every 15 minutes or so, which seems worrying. I'll try to remove one of my activities and see if it still happens with a single one. For the record, I have tried removing and recreating both activities and it didn't fix the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #37 from Michal Ziabkowski --- Cross-posting from bug 447388, as advised by Nate Graham: Okay, I've finally found some time for some more extensive testing. To remove some variables out of the equation, I purged my appletsrc, changed the wallpapers for both my activities (I have two with different wallpapers) and rebooted a few times. I can attach the config file, but I believe the changes between runs are more interesting: After the first reboot, the path to the wallpaper changes and a new containment is added: @@ -22,7 +22,7 @@ DialogWidth=800 [Containments][1][Wallpaper][org.kde.image][General] -Image=/usr/share/wallpapers/SafeLanding/ +Image=file:///usr/share/wallpapers/SafeLanding/contents/images/5120x2880.jpg SlidePaths=/home/mziab/.local/share/wallpapers,/usr/share/wallpapers [Containments][2] @@ -92,6 +92,20 @@ Image=/usr/share/wallpapers/OneStandsOut/ SlidePaths=/home/mziab/.local/share/wallpapers,/usr/share/wallpapers +[Containments][25] +ItemGeometries-1920x1080= +ItemGeometriesHorizontal= +activityId=c850a35c-21b5-4a3d-a501-e439889d7d98 +formfactor=0 +immutability=1 +lastScreen=2 +location=0 +plugin=org.kde.plasma.folder +wallpaperplugin=org.kde.image + +[Containments][25][Wallpaper][org.kde.image][General] +Image=file:///usr/share/wallpapers/Next/contents/images/1920x1080.png + [Containments][8] activityId= formfactor=2 On the next reboot, the wallpaper path changes again, for the other activity, it seems: @@ -89,7 +89,7 @@ DialogWidth=800 [Containments][24][Wallpaper][org.kde.image][General] -Image=/usr/share/wallpapers/OneStandsOut/ +Image=file:///usr/share/wallpapers/OneStandsOut/contents/images/1920x1080.jpg SlidePaths=/home/mziab/.local/share/wallpapers,/usr/share/wallpapers [Containments][25] Then it changes again on the next reboot: @@ -89,7 +89,7 @@ DialogWidth=800 [Containments][24][Wallpaper][org.kde.image][General] -Image=file:///usr/share/wallpapers/OneStandsOut/contents/images/1920x1080.jpg +Image=file:///usr/share/wallpapers/OneStandsOut/contents/images/2560x1600.jpg SlidePaths=/home/mziab/.local/share/wallpapers,/usr/share/wallpapers [Containments][25] As a reminder, this is an X11 install with two screens, a 1080p one and a 4k one. The latter is set to clone the first one (without scaling) for convenience. It's possible that there are TWO bugs at play here. The changing wallpaper paths might also warrant some scrutiny, but the bug happens with my own wallpapers with no multiple versions for different resolutions, so it's likely not the main culprit. I have conclusive evidence that disconnecting the TV works around the bug. After doing that I couldn't reproduce it, the proper wallpaper appeared instantly. With the TV plugged in, the wallpaper would change to the proper one after 40 or so seconds. Sorry if this is hard to read. I can post more info, just tell me what you need. Please note that this is still on Plasma 5.23, but I got the exact same bug on Plasma 5.23.90, so whatever causes it isn't yet fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447388] Wallpaper reset erratically after upgrade to Plasma 5.23
https://bugs.kde.org/show_bug.cgi?id=447388 --- Comment #7 from Michal Ziabkowski --- Okay, I've finally found some time for some more extensive testing. Sorry it took so long. To remove some variables out of the equation, I purged my appletsrc, changed the wallpapers for both my activities (I have two with different wallpapers) and rebooted a few times. I can attach the config file, but I believe the changes between runs are more interesting: After the first reboot, the path to the wallpaper changes and a new containment is added: @@ -22,7 +22,7 @@ DialogWidth=800 [Containments][1][Wallpaper][org.kde.image][General] -Image=/usr/share/wallpapers/SafeLanding/ +Image=file:///usr/share/wallpapers/SafeLanding/contents/images/5120x2880.jpg SlidePaths=/home/mziab/.local/share/wallpapers,/usr/share/wallpapers [Containments][2] @@ -92,6 +92,20 @@ Image=/usr/share/wallpapers/OneStandsOut/ SlidePaths=/home/mziab/.local/share/wallpapers,/usr/share/wallpapers +[Containments][25] +ItemGeometries-1920x1080= +ItemGeometriesHorizontal= +activityId=c850a35c-21b5-4a3d-a501-e439889d7d98 +formfactor=0 +immutability=1 +lastScreen=2 +location=0 +plugin=org.kde.plasma.folder +wallpaperplugin=org.kde.image + +[Containments][25][Wallpaper][org.kde.image][General] +Image=file:///usr/share/wallpapers/Next/contents/images/1920x1080.png + [Containments][8] activityId= formfactor=2 On the next reboot, the wallpaper path changes again, for the other activity, it seems: @@ -89,7 +89,7 @@ DialogWidth=800 [Containments][24][Wallpaper][org.kde.image][General] -Image=/usr/share/wallpapers/OneStandsOut/ +Image=file:///usr/share/wallpapers/OneStandsOut/contents/images/1920x1080.jpg SlidePaths=/home/mziab/.local/share/wallpapers,/usr/share/wallpapers [Containments][25] Then it changes again on the next reboot: @@ -89,7 +89,7 @@ DialogWidth=800 [Containments][24][Wallpaper][org.kde.image][General] -Image=file:///usr/share/wallpapers/OneStandsOut/contents/images/1920x1080.jpg +Image=file:///usr/share/wallpapers/OneStandsOut/contents/images/2560x1600.jpg SlidePaths=/home/mziab/.local/share/wallpapers,/usr/share/wallpapers [Containments][25] As a reminder, this is an X11 install with two screens, a 1080p one and a 4k one. The latter is set to clone the first one (without scaling) for convenience. It's possible that there are TWO bugs at play here. The changing wallpaper paths might also warrant some scrutiny, but the bug happens with my own wallpapers with no multiple versions for different resolutions, so it's likely not the main culprit. I have conclusive evidence that disconnecting the TV works around the bug. After doing that I couldn't reproduce it, the proper wallpaper appeared instantly. With the TV plugged in, the wallpaper would change to the proper one after 40 or so seconds. So if this is hard to read. I can post more info, just tell me what you need. Please note that this is still on Plasma 5.23, but as I mentioned in a previous comment, I got the exact same bug on Plasma 5.23.90, so whatever causes it isn't yet fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447388] Wallpaper reset erratically after upgrade to Plasma 5.23
https://bugs.kde.org/show_bug.cgi?id=447388 --- Comment #4 from Michal Ziabkowski --- Well, upgrading to Plasma 5.23.90 doesn't seem to have helped. After upgrading and rebooting I got the same black wallpaper again. Moreover, on some reboots this delay before the actual wallpaper is display doesn't seem to happen, but it's like 1 in 10 boots, maybe not even that. When I get the time I will try with a fresh Plasma profile to see what happens to the containments in appletsrc between boots. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447388] Wallpaper reset erratically after upgrade to Plasma 5.23
https://bugs.kde.org/show_bug.cgi?id=447388 --- Comment #2 from Michal Ziabkowski --- (In reply to Marco Martin from comment #1) > I think more than a wallpaper reset this is often plasma thinks there is no > containment for that screen and creates a new one, probably driving to many > stray ones in the appletrs. > > can you post your ~/.config/plasma-org.kde.plasma.desktop-appletsrc ? > > also can you test if this still happens on 5.24? You may be onto something here. I've seen containment ids being added seemingly at random when examining my appletsrc, but I thought that some legacy cruft in my old config was to blame, so I disregarded and forgot about it. As I mentioned before, the bug also happens with a fresh appletsrc, though. But I never checked what goes on with the ids in a fresh appletsrc, so that would be a reasonable next step, I guess. I've yet to test on Plasma 5.24, so I will get back to you on that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447388] New: Wallpaper reset erratically after upgrade to Plasma 5.23
https://bugs.kde.org/show_bug.cgi?id=447388 Bug ID: 447388 Summary: Wallpaper reset erratically after upgrade to Plasma 5.23 Product: plasmashell Version: 5.23.4 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: mz...@o2.pl CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Ever since upgrading to Plasma 5.23, one of three things will happen on a power cycle: a) I am greeted with a black background instead of the wallpaper b) the wallpaper is reset to the default one (/usr/share/wallpapers/Next/contents/images/1920x1080.png) c) more rarely the wallpaper is reset to one of the included I'd used previous (e.g. /usr/share/wallpapers/summer_1am/contents/images/2560x1600.jpg) The interesting thing is that the proper wallpaper will restore itself, if I wait about 20-30 seconds. I've tried deleting my plasma-org.kde.plasma.desktop-appletsrc and kactivitymanagerdrc, to no avail. My setup is a 1080p monitor connected via DVI and a 4k TV connected via HDMI. I have the latter set to 1080p and mirroring the primary 1080p screen. This seems similar to https://bugs.kde.org/show_bug.cgi?id=443832. However, I'm on nvidia-drivers. And that bug was filed against Plasma 5.22, whereas my issue only started with 5.23 and downgrading to 5.22 indeed makes the issue go away. One more pertinent piece of information: when I unplug the tv, the bug seems to go away. Hence why I've filed this against multi-screen support. STEPS TO REPRODUCE 1. Set custom wallpaper 2. Reboot OBSERVED RESULT The wallpaper is replaced by a blank background or the default wallpaper, then fixes itself after some seconds have passed EXPECTED RESULT The proper wallpaper is visible from the start SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Gentoo Linux 2.8 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.10-gentoo (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 23.5 GiB of RAM Graphics Processor: NVIDIA GeForce GT 1030/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 447378] New: Missing icons defaults to unreadable
https://bugs.kde.org/show_bug.cgi?id=447378 Bug ID: 447378 Summary: Missing icons defaults to unreadable Product: Breeze Version: 5.23.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: k...@kecnet.cz CC: kain...@gmail.com Target Milestone: --- Created attachment 144780 --> https://bugs.kde.org/attachment.cgi?id=144780=edit Bad icon substitution for missing Oxygen icons SUMMARY When set Oxygen iconset, the missing icons are substituted by Breeze icons. These icons are dark, even if Plasma theme set to Breeze dark should provide the light variants. The result is dark icon on dark system tray. STEPS TO REPRODUCE 1. Set Breeze dark Plasma theme 2. Set Oxygen iconset 3. Set DND mode OBSERVED RESULT DND icon (striked bell) on the systray is unreadable. EXPECTED RESULT White icons on dark panel should be provided from Breeze dark iconset. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-41-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 447219] Doplhin do not copy files through MNT Android
https://bugs.kde.org/show_bug.cgi?id=447219 --- Comment #1 from Michal Janousek --- Copy wors but when exist same folder Dollphin show error. It should show if I want to merge the folder, and keep or overwrite the files in it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447300] Task switcher icons don't respect chosen iconset
https://bugs.kde.org/show_bug.cgi?id=447300 --- Comment #1 from Michal Kec (MiK) --- Although I understand Nate's explanation in bug 433315 Comment 2, I do not understand such UX. Having different icons on task switcher vs. on task panel is super confusing. Now yet iconset-dependent. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447300] New: Task switcher icons don't respect chosen iconset
https://bugs.kde.org/show_bug.cgi?id=447300 Bug ID: 447300 Summary: Task switcher icons don't respect chosen iconset Product: plasmashell Version: 5.23.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: k...@kecnet.cz CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 144727 --> https://bugs.kde.org/attachment.cgi?id=144727=edit Comparison of task panel/switcher icons for Breeze and Oxygen SUMMARY The task switcher shows Breeze icons instead of default/Oxygen. STEPS TO REPRODUCE - Set Global Theme Breeze (any color variant) - Set Oxygen icons - Make sure your task switcher shows app icons (set i.e. "Big icons") - Make sure your task manager panel shows app icons - Start Krusader, start LibreOffice - Invoke task switcher by pressing Alt+Tab - See the icons... EXPECTED RESULT App icons on both task panel and task switcher should respect selected iconset. Basically they should be the same. OBSERVED RESULT See attached image... Whereas I can see the original icons (apps' built-in or Oxygen?) on the task panel, the task switcher shows different (Breeze?) icons. BTW: The same confusing icon is shown as the "window icon" in the windows' upper left corner. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-41-generic (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION I can see this confusing behavior for few weeks only since Plasma 5.23 (not sure if exactly since 5.23.3, but definitely in 5.23.4). To bring even more confusion here, this bug affects only some apps - namely Krusader and LibreOffice. KDE family apps (Dolphin, Konsole, even Kate) adjust their icons in respect with the iconset chosen. What is the difference? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 418996] Dark Telegram icon on dark Breeze theme
https://bugs.kde.org/show_bug.cgi?id=418996 --- Comment #17 from Michal Kec (MiK) --- Possibly related to bug 445518 ? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 445804] kiconthemes 5.88.0 inconsistent icon changes
https://bugs.kde.org/show_bug.cgi?id=445804 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 445489] Light theme icons randomly get installed in breeze-dark theme
https://bugs.kde.org/show_bug.cgi?id=445489 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 445518] KDE Plasma doesn't respect icon theme for some applications and application icons
https://bugs.kde.org/show_bug.cgi?id=445518 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 446477] Breeze icon being shown despite current icon theme not having Breeze in its fallback chain
https://bugs.kde.org/show_bug.cgi?id=446477 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
