[plasmashell] [Bug 460785] Option for an unread notifications counter on a panel
https://bugs.kde.org/show_bug.cgi?id=460785 Evgen changed: What|Removed |Added Attachment #153067|tooltip for "Notifications" |tooltip for "Notifications" description|applet informs about a |applet informs about a |number of unread|number of unread |notification|notifications -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460785] New: Option for an unread notifications counter on a panel
https://bugs.kde.org/show_bug.cgi?id=460785 Bug ID: 460785 Summary: Option for an unread notifications counter on a panel Classification: Plasma Product: plasmashell Version: git-stable-Plasma/5.26 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: alts...@gmail.com CC: k...@privat.broulik.de Target Milestone: 1.0 Created attachment 153067 --> https://bugs.kde.org/attachment.cgi?id=153067=edit tooltip for "Notifications" applet informs about a number of unread notification SUMMARY *** As we've figured out on https://bugs.kde.org/show_bug.cgi?id=460760 proper implementation of "unread notification badges for applications" is not that straightforward. Apps need to support Unity API ; distros or users should pre-install libunity ; "sandboxed" applications (Flatpak & Snap) need to communicate with libunity on system or pre-package it etc... So I'm asking for an option which could at least slightly improve user experience in this regard. Currently "Notifications" applet shows a number of unread notifications from history in an information tooltip which reveals on a mouse hover (screenshot attached). I'd like to see that number on a panel (over, inside, near or instead standard "bell" indicator, whatever design choice KDE VDG would approve). This way increased number could bring user's attention to some missed messages/events. I believe it could be more noticeable than a "shaking" animation (which eventually stops) or a static "bell" icon. Windows 10/11 has this feature so it's probably useful for someone. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460760] New: Notification badges for most applications using built-in notifications system
https://bugs.kde.org/show_bug.cgi?id=460760
Bug ID: 460760
Summary: Notification badges for most applications using
built-in notifications system
Classification: Plasma
Product: plasmashell
Version: git-stable-Plasma/5.26
Platform: Neon
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Task Manager and Icons-Only Task Manager
Assignee: plasma-b...@kde.org
Reporter: alts...@gmail.com
Target Milestone: 1.0
SUMMARY
***
Plasma 5.20 switched to "Icons-Only Task Manager" by default. It brought
overall better presentation but also exposed issue with Chat and Email
applications.
In a days of a "classic taskbar" (icon + text) programs used to blink or print
some text to bring user attention that there's a new chat or e-mail message
etc. Since "classic taskbar" is considered obsolete now, both OS/DE and
application devs drop such things.
Nowadays users should rely on notifications, tray indicators, shaking effects
and "unread badges". Unfortunately Linux Desktop Environments still doesn't
have a stable universal API for notification badges. For now there still exist
Unity API which KDE Plasma supports. But it's not something application
developers would target & distros pre-install. Among messaging apps which
supports libunity I know "Telegram Desktop" and "Ferdium". Most other apps
(e.g. "Viber", "Skype", "Thunderbird", "Google Chat" PWA etc) doesn't.
Situation is even worse with new packaging formats (Snap, Flatpak) which could
potentially "burn bridges" to Unity API, even for Electron apps.
Recently I've discovered that GNOME extension developers figured out how to get
notification counters/badges even without Unity API (references bellow).
Basically they get information about unread notifications from the message tray
and place number as a badge/indicator on "taskbar icon". When user opens
program window, notification is considered as "read" and "badge" disappears. It
works fairly well.
Looking at the Notification applet "unread messages", I presume that
Plasmashell knows/remembers which programs generated notifications, how many
etc. So theoretically this feature could be implemented in KDE Plasma as well.
Again, since we still don't even have a stable API, lots of legacy &
proprietary applications, I just don't see a better resolution for this problem
(which won't take years to implement and adopt).
Additional option to workaround this issue is a "notification counter"
instead/beside a "bell" icon but that's probably should be a separate issue.
---
Aforementioned GNOME extensions:
- RocketBar (https://github.com/linux-is-awesome/gnome_extension_rocketbar)
- Dash to Panel with unofficial modification
(https://github.com/home-sweet-gnome/dash-to-panel/issues/1695#issuecomment-1160077515)
- Notification Counter (https://github.com/vkrizan/NotificationCounter)
- new-mail-indicator (https://github.com/fthx/new-mail-indicator)
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. Receive a notification about new message at any messaging application that
doesn't support UnityAPI ("Thunderbird", "Google Chat", Viber, Skype, Electron
chat apps etc)
2. Check if application icon at "Icons-only Taskbar has an "unread
notification" badge
OBSERVED RESULT
Application icon doesn't inform about new messages
EXPECTED RESULT
Application icon has a badge with an unread messages counter
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon User Edition
KDE Plasma Version: 5.26.0
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
--
You are receiving this mail because:
You are watching all bug changes.
[ark] [Bug 436556] When Ark overwrites existing files, the dialog says "The files seem identical" even if different
https://bugs.kde.org/show_bug.cgi?id=436556 Evgen changed: What|Removed |Added CC||alts...@gmail.com --- Comment #2 from Evgen --- Can confirm this with Ark. Looks like it's not reproducible with Krusader (which have built-in archive manager). I tried to copy file on a second Krusader's panel and also tried to drag'n'drop it to Dolphin. In both cases dialog reported that files are different. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438990] Better detection of unresponsive applications
https://bugs.kde.org/show_bug.cgi?id=438990 --- Comment #2 from Evgen --- @(In reply to Alois Wohlschlager from comment #1) > While I agree that the current behavior is not ideal, I cannot reproduce the > bug entirely with your steps. Can you please provide your system information (Distro, video card, Plasma version, KWin version (KWin or KWinFT), Session type (X11, Wayland)? > * Screen content is not reused, the Kate window displays like it did the > last time before the SIGSTOP. In my case initially screen content of previous windows is not reused. It happens if I minimize/unminimize "frozen" application (e.g. Kate, GNOME Disks). Also screen content is reused even after de-saturation effect is applied. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438990] New: Better detection of unresponsive applications
https://bugs.kde.org/show_bug.cgi?id=438990 Bug ID: 438990 Summary: Better detection of unresponsive applications Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: alts...@gmail.com Target Milestone: --- Created attachment 139571 --> https://bugs.kde.org/attachment.cgi?id=139571=edit Demonstation how frozen application reuses screen content and how KWin reacts to frozen applications SUMMARY There is a usability problem with unresponsive/hanged/frozen applications. When application window stops responding, it may "take" part of the screen (user may see not application content before hang but content of the desktop or previous window). That's especially confusing for maximized windows. So we should try to close that window with a button on a window decoration or on the panel. Then it may apply effect "Desaturate Unresponsive Applications" for a frozen window and finally show a dialog that process is not responding. I see 2 problems here: 1. Dialog is only triggered with a "close" action 2. As frozen window reuses some screen content, for a user sometimes very hard to find that window on a screen. User must rely on a panel (Task Manager), Task Switcher, "Present Windows" etc. Situation gets worse with CSD and variable "KWIN_EFFECTS_FORCE_ANIMATIONS=0" which among others disables effect "Desaturate Unresponsive Applications". I tried to boot into GNOME 3.36 and liked how Mutter deals with this issue: - it detects that application is frozen without user's specific interaction with a close button/command and shows dialog with - It dims window and repeats showing that dialog if user selected to "Wait Longer". Also as Mutter attaches that modal dialog to a parent window, for a user it's really easy to identify frozen window. STEPS TO REPRODUCE 1. Launch Kate and maximize it's window 2. Launch Konsole and maximize it's window 3. On a Konsole find PID for a "Kate" process with ps -ely | grep kate (3rd collumn) 4. Simulate process hang with a command kill -SIGSTOP 5. Minimize Kate (left click on a Kate item on a Task Manager on the panel) so you will see Konsole window 6. Unminize Kate OBSERVED RESULT - KWin doesn't detect that application is unresponsive unless you press a "close" button - Unresponsive application reuses screen content so it's hard to identify your frozen window, especially with programs which use CSD (e.g "Gedit) EXPECTED RESULT User can easily identify and close unresponsive program SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.22 User Edition KDE Plasma Version: 5.22.1 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Video demonstration attached -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418370] Inivisible Anydesk tray icon sits at the top left corner.
https://bugs.kde.org/show_bug.cgi?id=418370 --- Comment #3 from Evgen --- Same thing happens with Cryptomator. Easily reproducible in a Wayland session. For some reason that misplaced invisible tray item is always at the top left corner. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 434125] High CPU usage with "size of contents" option when trying to analyze "/proc" folder
https://bugs.kde.org/show_bug.cgi?id=434125 Evgen changed: What|Removed |Added Summary|High CPU usage with "size |High CPU usage with "size |of contents" option for |of contents" option when |/proc folder|trying to analyze "/proc" ||folder -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 434125] New: High CPU usage with "size of contents" option for /proc folder
https://bugs.kde.org/show_bug.cgi?id=434125 Bug ID: 434125 Summary: High CPU usage with "size of contents" option for /proc folder Product: dolphin Version: 20.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: details mode Assignee: dolphin-bugs-n...@kde.org Reporter: alts...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I had high CPU usage while "Dolphin" window was opened. Later I figured out that problem was with "size of contents" option which I manually turned on. And specifically with symlink "z:" which point to "/" in "$HOME/.wine/dosdevices/" folder. That symlink Wine creates by default during configuration. STEPS TO REPRODUCE 1. Settings > Configure Dolphin > View Modes > Details. For "Folder size displays" select "Size of contents, up to 4 levels deep" 2. F4 to open terminal 3. Create symlink to "/proc" with command and "ln -s /proc test_size" OBSERVED RESULT Dolphin start eating up to 48% of CPU and at some point will show some strange value like "21,6 PiB" EXPECTED RESULT Probably Dolphin shouldn't inspect symlinks and /proc directory SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon User Edition KDE Plasma Version: 5.21 KDE Frameworks Version: 5.79 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427439] Anydesk error massages
https://bugs.kde.org/show_bug.cgi?id=427439 Evgen changed: What|Removed |Added CC||alts...@gmail.com --- Comment #3 from Evgen --- Workaround is to launch it with UBUNTU_MENUPROXY=0 e.g. UBUNTU_MENUPROXY=0 anydesk (you can easily edit launcher with KDE Menu Editor) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418370] Inivisible Anydesk tray icon sits at the top left corner.
https://bugs.kde.org/show_bug.cgi?id=418370 --- Comment #2 from Evgen --- My current workaround is to restart GUI after login with script nano ~/.config/autostart-scripts/restart_anydesk.sh #!/bin/bash if pgrep -f "anydesk --tray" > /dev/null; then pkill -x anydesk /usr/bin/anydesk --tray & fi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420917] Looped bash script (unfinished command) holds plasma_session startup
https://bugs.kde.org/show_bug.cgi?id=420917 --- Comment #2 from Evgen --- (In reply to David Edmundson from comment #1) > Fixing that would break other use cases as we have to source env variables > from that into our running environment. Sure. now I understand that this folder is primarily for env variables which must be set before starting anything else in session. By the way, some locations are not easily discoverable for an inexperienced user ... Hope with Plasma 6 structure would be reconsidered. > > The scripts doing what you're describing are probably best suited for the > .local/share/autostart-scripts these are run async and even if broken won't > lock startup. Thank you! Just a small correction: it's .config/autostart-scripts -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420917] Looped bash script (unfinished command) holds plasma_session startup
https://bugs.kde.org/show_bug.cgi?id=420917 Evgen changed: What|Removed |Added Summary|Looped bash script blocks |Looped bash script |plasma_session startup |(unfinished command) holds ||plasma_session startup -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420917] Looped bash script blocks plasma_session startup
https://bugs.kde.org/show_bug.cgi?id=420917 Evgen changed: What|Removed |Added Summary|Looped bash scripts block |Looped bash script blocks |plasma_session startup |plasma_session startup -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420917] New: Looped bash scripts block plasma_session startup
https://bugs.kde.org/show_bug.cgi?id=420917 Bug ID: 420917 Summary: Looped bash scripts block plasma_session startup Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_autostart Assignee: mon...@kde.org Reporter: alts...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Looped bash scripts blocks plasma_session startup SUMMARY I have few looped bash scripts for maintenance tasks (resume paused printers, mute sound after headphones disconnect). So I placed one of them to ~/.config/plasma-workspace/env/ During next login session didn't start leaving me with a mouse cursor on a black background. STEPS TO REPRODUCE 1. On ~/.config/plasma-workspace/env/ create file test.sh with content while true; do : done 2. Log out from session 3. Try to login OBSERVED RESULT Black background with a mouse cursor. I switched to different tty and htop showed that process /bin/sh /usr/lib/x86_64-linux-gnu/libexec/plasma-sourceenv.sh /home/$USER/.config/plasma-workspace/env/test.sh loads 100% percent of 1 CPU After I killed it plasma_session and other services started to load. Solution for my problem was to push that script into the background (adding "&" after "done") done & EXPECTED RESULT Looped script doesn't block plasma_session startup SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418385] New: Global Menu doesn't work properly with Mediainfo GUI
https://bugs.kde.org/show_bug.cgi?id=418385 Bug ID: 418385 Summary: Global Menu doesn't work properly with Mediainfo GUI Product: plasmashell Version: 5.18.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gmenu-dbusmenu-proxy Assignee: k...@privat.broulik.de Reporter: alts...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 126541 --> https://bugs.kde.org/attachment.cgi?id=126541=edit All "View" modes are visually "selected" SUMMARY With Global Menu enabled it's impossible to switch between "View" modes in Mediainfo GUI STEPS TO REPRODUCE 1. Install mediainfo-gui 2. Enable Global Menu (panel widget or decoration button) 3. Launch Mediainfo GUI 4. Try to change mode into "View" menu OBSERVED RESULT Visually all radio-buttons enabled and you can't really select one of them. EXPECTED RESULT Mode changes if you press appropriate radio-button SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION Mediainfo GUI uses wxWidgets + GTK3. I also tried it on XFCE (Xubuntu with xfce4-appmenu-plugin) and it works there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418370] New: Inivisible Anydesk tray icon sits at the top left corner.
https://bugs.kde.org/show_bug.cgi?id=418370 Bug ID: 418370 Summary: Inivisible Anydesk tray icon sits at the top left corner. Product: plasmashell Version: 5.18.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: alts...@gmail.com Target Milestone: 1.0 Created attachment 126531 --> https://bugs.kde.org/attachment.cgi?id=126531=edit Anydesk invisible tray icon at the top left corner SUMMARY Inivisible Anydesk tray icon sits at the top left corner. STEPS TO REPRODUCE 1. Install Anydesk 2. Restart 3. Try to click on top left corner 4. Log out / log in, eventually you'll get it OBSERVED RESULT Left click opens Anydesk window. Right click open Anydesk menu. Restarting plasmashell fixes it EXPECTED RESULT Anydesk tray item must be only in system tray SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION Issue isn't always reproducible, panel/tray location doesn't really matter. When Anydesk is installed, at loading (between SDDM and Plasma Shell) you can always notice black box at that corner. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416553] Bad UX with "audio playing" indicator on "Icons-only Task Manager"
https://bugs.kde.org/show_bug.cgi?id=416553 Evgen changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 415474] Crash while closing the "Energy Information" window
https://bugs.kde.org/show_bug.cgi?id=415474 Evgen changed: What|Removed |Added CC||alts...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416553] New: Bad UX with "audio playing" indicator on "Icons-only Task Manager"
https://bugs.kde.org/show_bug.cgi?id=416553 Bug ID: 416553 Summary: Bad UX with "audio playing" indicator on "Icons-only Task Manager" Product: plasmashell Version: 5.17.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: alts...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 125289 --> https://bugs.kde.org/attachment.cgi?id=125289=edit Demonstration of current "Audio playing" indicator on horizontal and vertical panels SUMMARY With vertical panel on the left side it's very to accidentally mute application sound STEPS TO REPRODUCE 1. Right click on panel > "Edit Panel" 2. with "Screen Edge" move panel to the left 3. Open something with sound 4. Try to switch between application windows on the panel OBSERVED RESULT I accidentally click on "audio playing" indicator and mute sound of the application EXPECTED RESULT "Audio playing" indicator doesn't stand in my way. Maybe make it smaller or relocate it to the bottom left (some users and even distros (like KaOS) put panel to the right edge so top right side location of the indicator will stand in their way), or give user option to relocate it. Another way is an option to make that indicator not clickable. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.66.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION On the attached screenshot there's 3 panel: - vertical with "Task Manager" - horizontal with "Task Manager" - horizontal with "Icons-only Task Manager" As you can see on both horizontal and vertical panels with "Icons-only Task Managers" that "Audio playing" indicator can be easily accidentally clicked. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408242] If you cut a clip with the effects turned off on the right side of the clip, the effects turn on
https://bugs.kde.org/show_bug.cgi?id=408242 Evgen changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #8 from Evgen --- Works for me. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408242] If you cut a clip with the effects turned off on the right side of the clip, the effects turn on
https://bugs.kde.org/show_bug.cgi?id=408242 Evgen changed: What|Removed |Added Attachment #124106|0 |1 is obsolete|| --- Comment #6 from Evgen --- Created attachment 124107 --> https://bugs.kde.org/attachment.cgi?id=124107=edit Here's demonstration of my issue -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408242] If you cut a clip with the effects turned off on the right side of the clip, the effects turn on
https://bugs.kde.org/show_bug.cgi?id=408242 --- Comment #5 from Evgen --- (In reply to emohr from comment #3) > Your step 3: "try to re-enable all effects at once" -> I have 2 effects on > the same clip -> How can I enable/disable all clips at ones? I didn't say about disabling all clips. This bug is about effects status on particular clip. Added screenshot with button I'm referring to. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408242] If you cut a clip with the effects turned off on the right side of the clip, the effects turn on
https://bugs.kde.org/show_bug.cgi?id=408242 --- Comment #4 from Evgen --- Created attachment 124106 --> https://bugs.kde.org/attachment.cgi?id=124106=edit all effects switcher -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408242] If you cut a clip with the effects turned off on the right side of the clip, the effects turn on
https://bugs.kde.org/show_bug.cgi?id=408242 Evgen changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED CC||alts...@gmail.com --- Comment #2 from Evgen --- I guess this problem is not fully resolved because after cut, "all effects switcher" on the right side has incorrect status (at least in Kdenlive 19.08.3) STEPS TO REPRODUCE 1. Disable all effects of a clip (eye icon) 2. Cut a clip 3. On the right side try to re-enable all effects at once OBSERVED RESULT Icon show the effects are enable (eye icon is not crossed) but all effects on the list are disabled. Clicking on "all effects" button changes nothing. You have to re-enable them on by one (or delete all of them and copy from the left side). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407226] GIMP 2.10 internal color picker doesn't work with "Color Picker" effect + OpenGL compositor backend
https://bugs.kde.org/show_bug.cgi?id=407226 --- Comment #11 from Evgen --- (In reply to Evgen from comment #8) > (In reply to Vlad Zagorodniy from comment #7) > > GIMP spews warnings like this > > > > (gimp:23528): GLib-CRITICAL **: 12:00:48.423: the GVariant format string > > '(u)' has a type of '(u)' but the given value has a type of '((u))' > > > > It looks very fishy because the return value has type of (u). In either > > case, it looks like a GIMP issue. Can you file corresponding bug report? > > https://gitlab.gnome.org/GNOME/gimp/issues/ > Sorry, I don't understand meaning of that warning. > Situation is that probably all X11 compositors except KWin support GIMP. > I can file bug report and they may say it's a KWin problem. This bug has already been reported (sadly, unnoticed) https://gitlab.gnome.org/GNOME/gimp/issues/1878 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407226] GIMP 2.10 internal color picker doesn't work with "Color Picker" effect + OpenGL compositor backend
https://bugs.kde.org/show_bug.cgi?id=407226 --- Comment #8 from Evgen --- (In reply to Vlad Zagorodniy from comment #7) > GIMP spews warnings like this > > (gimp:23528): GLib-CRITICAL **: 12:00:48.423: the GVariant format string > '(u)' has a type of '(u)' but the given value has a type of '((u))' > > It looks very fishy because the return value has type of (u). In either > case, it looks like a GIMP issue. Can you file corresponding bug report? > https://gitlab.gnome.org/GNOME/gimp/issues/ Sorry, I don't understand meaning of that warning. Situation is that probably all X11 compositors except KWin support GIMP. I can file bug report and they may say it's a KWin problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407226] GIMP 2.10 internal color picker doesn't work with "Color Picker" effect + OpenGL compositor backend
https://bugs.kde.org/show_bug.cgi?id=407226 --- Comment #5 from Evgen --- (In reply to Vlad Zagorodniy from comment #4) > A bit stupid question: what tool do you use for color picking? On toolbox on the left, under standard "tool" icons there's 2 colors (foreground/background). Click on one of them, then on the same line as "HTML notation" click on the 'eyedropper' icon. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407226] GIMP 2.10 internal color picker doesn't work with "Color Picker" effect + OpenGL compositor backend
https://bugs.kde.org/show_bug.cgi?id=407226 Evgen changed: What|Removed |Added Summary|Color picker of GIMP 2.10 |GIMP 2.10 internal color |doesn't work with "Color|picker doesn't work with |Picker" effect combined |"Color Picker" effect + |with OpenGL compositor |OpenGL compositor backend |backend | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407226] Color picker of GIMP 2.10 doesn't work with "Color Picker" effect combined with OpenGL compositor backend
https://bugs.kde.org/show_bug.cgi?id=407226 Evgen changed: What|Removed |Added Summary|Color picker of GIMP 2.10 |Color picker of GIMP 2.10 |doesn't work with OpenGL|doesn't work with "Color |compositor backend |Picker" effect combined ||with OpenGL compositor ||backend -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407226] Color picker of GIMP 2.10 doesn't work with OpenGL compositor backend
https://bugs.kde.org/show_bug.cgi?id=407226 --- Comment #3 from Evgen --- (In reply to Christoph Feck from comment #2) > Could be a duplicate of bug 172921. > I believe it's not the same bug. Those bugs tells that you can't pick a correct color because other window has been darkened. But here you can't pick any color (GIMP always returns black (#000) on most distributions or blue on Mageia (which has different theme by default). I should have added this to the first post. --- Meanwhile I tried to disable all effects and figured out that the problem is with (surpise-surprise :) ) "Color Picker" effect (hidden under 'Internal Desktop Effects'). After I disable it GIMP even with OpenGL backend gets correct color. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407226] Color picker of GIMP 2.10 doesn't work with OpenGL compositor backend
https://bugs.kde.org/show_bug.cgi?id=407226 Evgen changed: What|Removed |Added Flags|X11+| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407226] Color picker of GIMP 2.10 doesn't work with OpenGL compositor backend
https://bugs.kde.org/show_bug.cgi?id=407226 Evgen changed: What|Removed |Added Summary|Colour Picker of GIMP |Color picker of GIMP 2.10 |doesn't work with OpenGL|doesn't work with OpenGL |compositor backend |compositor backend -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407226] Colour Picker of GIMP doesn't work with OpenGL compositor backend
https://bugs.kde.org/show_bug.cgi?id=407226 Evgen changed: What|Removed |Added Flags||X11+, Usability+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407226] Colour Picker of GIMP doesn't work with OpenGL compositor backend
https://bugs.kde.org/show_bug.cgi?id=407226 --- Comment #1 from Evgen --- > OBSERVED RESULT > GIMP picks color under mouse > > EXPECTED RESULT > GIMP picks some color (black/blue) from Plasma theme Sorry, EXPECTED/OBSERVED must be vice versa. Unfortunately I'm unable to edit initial message. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407226] Colour Picker of GIMP doesn't work with OpenGL compositor backend
https://bugs.kde.org/show_bug.cgi?id=407226 Evgen changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407226] Colour Picker of GIMP doesn't work with OpenGL compositor backend
https://bugs.kde.org/show_bug.cgi?id=407226 Evgen changed: What|Removed |Added Keywords||reproducible, usability -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407226] New: Colour Picker of GIMP doesn't work with OpenGL compositor backend
https://bugs.kde.org/show_bug.cgi?id=407226 Bug ID: 407226 Summary: Colour Picker of GIMP doesn't work with OpenGL compositor backend Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: scene-opengl Assignee: kwin-bugs-n...@kde.org Reporter: alts...@gmail.com Target Milestone: --- SUMMARY When kwin_x11 uses OpenGL 2/3 compositor backends, GIMP 2.10 can't get right color with built-in color picker. STEPS TO REPRODUCE 1. Make sure you have compositing enabled with OpenGL backend 2. Install gimp 2.10.8+ (on Neon you can use ppa:otto-kesselgulasch/gimp) 3. Try to pick color OBSERVED RESULT GIMP picks color under mouse EXPECTED RESULT GIMP picks some color (black/blue) from Plasma theme SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon Unstable Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION GIMP 2.8.12 from repos is not affected. Flatpak version also works fine (didn't test Snap). After you switch backend to Xrender or "block compositing" from "Special Settings", color picker works properly. I tried it also on Kubuntu (Plasma 5.12.x) with this PPA. Debian 10 (Plasma 5.14.5) & Mageia 7 (Plasma 5.15.4) have GIMP 2.10 in the official repos and there problem is also reproducible. -- You are receiving this mail because: You are watching all bug changes.
