| === chris14_ is now known as chris14 | ||
| === tomreyn_ is now known as tomreyn | ||
| Sakara | Hi folks. I've experience an incident on my Ubuntu desktop that I'm keen to hear folks opinion on. I use the discord application on my Ubuntu 20.04 LTS desktop system. When my system is locked anyone is able to use my mouse bind and they can still use the voice communications in the application that is opened in my session. | 08:15 |
|---|---|---|
| Sakara | Is this an Ubuntu security bug, discord bug, or neither? | 08:16 |
| Habbie | what's a mouse bind? | 08:20 |
| Sakara | I've bound push to talk in the discord application to a button on the side of my mouse. | 08:21 |
| Habbie | ah | 08:21 |
| Habbie | i have a semi related data point, on my (debian) desktop, the media keys on my keyboard (play/pause, next, etc.) also work on the lock screen | 08:21 |
| Sakara | This is basically the same class of issue. | 08:22 |
| Habbie | where did you configure the bind? | 08:22 |
| Sakara | The bind is inside the discord application. | 08:22 |
| Sakara | Inside the application settings you select which button unmutes the chosen sound input device to transmit to people int he call. | 08:22 |
| Sakara | For me I use a button my mouse to unmute microphone to talk to everyone in the call. | 08:23 |
| Sakara | I lock my workstation but anyone is able to use my mouse to talk inside my call while I'm away from the desk. | 08:23 |
| Sakara | Not ideal. | 08:23 |
| JanC | Habbie: I think some people want their music to keep on playing while the screen is locked, and then it makes sense if you can also stop or mute it or change the volume, I guess... | 11:03 |
| Habbie | likely | 11:04 |
| Habbie | it's not a complaint from my side | 11:04 |
| Habbie | but i see how Sakara is unhappy with a similar outcome | 11:04 |
| JanC | well, in other cases it's obviously more of a problem | 11:04 |
| JanC | I think applications can detect when the lock screen is enabled | 11:04 |
| JanC | probably should do that in case of discord as Sakara sees | 11:06 |
| amurray | this feels more like a bug in gnome-shell or whatever implements the lock screen - when locked, input events should not be getting sent to applications (although if say discord has directly opened the input device rather than say using Gdk/Gtk to get input events then all bets are off) | 11:08 |
| JanC | amurray: it's a bit complicated as e.g. you might still want the volume/media keys to work in some cases, so gnome-shell blocking everything might not be the best solution either... :-/ | 11:13 |
| amurray | I think gnome-shell handles media-keys so then it should then be able to handle volume up/down (or perhaps it's gnome-settings-daemon - I forget which) | 11:19 |
| JanC | but I agree that gnome should probably have some sort of way to block everything | 11:21 |
| JanC | and in the mean time, sensitive applications should probably detect when the lock screen is enabled... | 11:22 |
| JanC | so filing bugs against all of them makes sense probably :) | 11:23 |
| Sakara | I'll see what I can do about seeing how to discuss this issue with the discord folks. I feel they will palm it off to the folks looking after the framework. | 11:26 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!