#StackBounty: #ubuntu #python #gdm #polkit #gdm3 Python tkinter GUI is being pushed behind GDM3 polkit password window

Bounty: 50

It seems that my Python PAM RFID solution development has come to an end 🎉 and I finally finished developing kind of working GUI solution as well.

Issue

But, of course I ran into one final issue 😑 – my GUI is being forced behind all GDM run windows – password window, login and lock screen window. I’ve double checked – YES the GUI runs without errors and shows up when needed – BUT it doesn’t show on top of windows being run by GDM.

How it works

  1. Python PAM module listens for RFID card on NFC scanner
  2. Once card present – it auto-fills user credentials and starts authentication process via remote server
  3. Server responds with status codes
  4. Python PAM module shows tkinter window (PIN, Register, Error) according to received state
  5. User interacts with form and actions are being done on user behalf in background as well as reply status are being send to remote server.

Example of an error

Here is a screenshot how it looks on password window (:
enter image description here

I made password window little bit more opaque, so you could see that the GUI is there.

Whatever I do (ALT+TAB, TAB anything that could bring the window up) doesn’t work.

The same happens on login/lock screen – only those are not opaque and it seems that they are not working, however, when I enter password and log back in, I see my previously (on login/lock screen) triggered GUI like so:
enter image description here

My tries to fix it

  • I tried to add these attributes to my tkinter root:
    tk_root.attributes('-topmost', True)
    tk_root.call('wm', 'attributes', '.', '-topmost', '1')
    

    but obviously gdm3 is being forced on top of everything and this won’t simply do the trick.😑

Question

How can I fix this? What would be the best and safest way to force my tkinter or any other Python GUI script/app on top of gdm3 GUIs?

At this point I’m open to anything – it can be something other than tkinter that will work on top of the GDM3 windows. Out of the box solutions are welcomed as well.

Thank you in advance, 🙏🏻

richardev


Get this bounty!!!

#StackBounty: #xorg #gdm #touchscreen Touchscreen stops working

Bounty: 50

I am working with some Ubuntu systems to control some smart home things. I run Ubuntu on a industrial PC with an industrial touchscreen display. Everything was working fine. Since some time ago the touchscreen has stopped working after some time. I didn’t reboot the PC. I have the same problem on more than one Ubuntu system, so I think the problem is a software problem. I have looked in the logs and I always see this if the problem disappears:

Jul 27 15:02:28 byk-station /usr/lib/gdm3/gdm-x-session[1021]: source device 10: history size 6400 overflowing for touch 3088  
Jul 27 15:02:50 byk-station /usr/lib/gdm3/gdm-x-session[1021]: message repeated 1585 times: [source device 10: history size 6400 overflowing for touch 3088]

This message comes often then. With this message the touchscreen stops working. Normally there helps a reboot, but I need to find a solution for the problem. I couldn’t add the whole syslog input here because it is too long.


Get this bounty!!!

#StackBounty: #fedora #tty #wayland #gdm #sway annoying CTRL+F# instead of CTRL+ALT+F# Virtual Terminal Switching on Fedora 33 with swa…

Bounty: 100

I have the annoying problem that CTRL+F# is switching to a Virtual Terminal. This should normally be done with CTRL+ALT+F# but for some reason it is also triggered by CTRL+F#.
I actually have an almost fresh Fedora 33 installation on a Lenovo laptop with sway and wayland.

I tried removing all Console_* bindings with something like:

sudo dumpkeys | grep -vE 'Console_5[^0-9]'  | sudo loadkeys

but it does not have an effect in sway/wayland.

I also tried srvkeys:none

setxkbmap -layout us -variant dvorak-alt-intl -option srvkeys:none

but it has no effect either.

It doesn’t matter if I start sway from gdm or from the shell. (however using a gnome session all is fine – i.e. ctrl+F# does not switch to a virtual console)

The usual gsettings does not show anything suspicions:

$ gsettings list-recursively | grep switch-to-session | sort

ca.desrt.dconf-editor.Settings saved-pathbar-path '/org/gnome/mutter/wayland/keybindings/switch-to-session-5'
ca.desrt.dconf-editor.Settings saved-view '/org/gnome/mutter/wayland/keybindings/switch-to-session-5'
org.gnome.mutter.wayland.keybindings switch-to-session-10 ['<Primary><Alt>F10']
org.gnome.mutter.wayland.keybindings switch-to-session-11 ['<Primary><Alt>F11']
org.gnome.mutter.wayland.keybindings switch-to-session-12 ['<Primary><Alt>F12']
org.gnome.mutter.wayland.keybindings switch-to-session-1 ['<Primary><Alt>F1']
org.gnome.mutter.wayland.keybindings switch-to-session-2 ['<Primary><Alt>F2']
org.gnome.mutter.wayland.keybindings switch-to-session-3 ['<Primary><Alt>F3']
org.gnome.mutter.wayland.keybindings switch-to-session-4 ['<Primary><Alt>F4']
org.gnome.mutter.wayland.keybindings switch-to-session-5 ['<Primary><Alt>F5']
org.gnome.mutter.wayland.keybindings switch-to-session-6 ['<Primary><Alt>F6']
org.gnome.mutter.wayland.keybindings switch-to-session-7 ['<Primary><Alt>F7']
org.gnome.mutter.wayland.keybindings switch-to-session-8 ['<Primary><Alt>F8']
org.gnome.mutter.wayland.keybindings switch-to-session-9 ['<Primary><Alt>F9']

And removing all mutter bindings does not change anything in sway.

I have no further ideas where and what to look for.
I have also filed an issue at https://github.com/swaywm/sway/issues/5885


Get this bounty!!!

#StackBounty: #gnome #keyboard #xorg #gdm why am i getting ' event processing lagging behind' msg in Ubuntu 20.10

Bounty: 50

seeing my system logs, they are full of msgs like this:

/usr/libexec/gdm-x-session[2564]: (EE) event4  - SIGMACHIP USB Keyboard: client bug: event processing lagging behind by 25ms, your system is too slow
/usr/libexec/gdm-x-session[2564]: (EE) event4  - SIGMACHIP USB Keyboard: client bug: event processing lagging behind by 17ms, your system is too slow

i have a 12 core system which is essentially idle when i see this. it seems to happen since i upgraded to Ubuntu 20.10.

how can i find the root cause and how to eliminate this issue?

sys info:

model name  : AMD Ryzen 9 3900X 12-Core Processor
/sys/devices/system/cpu/cpufreq/policy10/scaling_driver:acpi-cpufreq
/sys/devices/system/cpu/cpufreq/policy0/scaling_governor:ondemand


grep . /sys/devices/system/cpu/cpuidle/*
/sys/devices/system/cpu/cpuidle/available_governors:ladder menu teo 
/sys/devices/system/cpu/cpuidle/current_driver:acpi_idle
/sys/devices/system/cpu/cpuidle/current_governor:menu
/sys/devices/system/cpu/cpuidle/current_governor_ro:menu


Get this bounty!!!

#StackBounty: #gnome #keyboard #xorg #gdm why am i getting ' event processing lagging behind' msg in Ubuntu 20.10

Bounty: 50

seeing my system logs, they are full of msgs like this:

/usr/libexec/gdm-x-session[2564]: (EE) event4  - SIGMACHIP USB Keyboard: client bug: event processing lagging behind by 25ms, your system is too slow
/usr/libexec/gdm-x-session[2564]: (EE) event4  - SIGMACHIP USB Keyboard: client bug: event processing lagging behind by 17ms, your system is too slow

i have a 12 core system which is essentially idle when i see this. it seems to happen since i upgraded to Ubuntu 20.10.

how can i find the root cause and how to eliminate this issue?

sys info:

model name  : AMD Ryzen 9 3900X 12-Core Processor
/sys/devices/system/cpu/cpufreq/policy10/scaling_driver:acpi-cpufreq
/sys/devices/system/cpu/cpufreq/policy0/scaling_governor:ondemand


grep . /sys/devices/system/cpu/cpuidle/*
/sys/devices/system/cpu/cpuidle/available_governors:ladder menu teo 
/sys/devices/system/cpu/cpuidle/current_driver:acpi_idle
/sys/devices/system/cpu/cpuidle/current_governor:menu
/sys/devices/system/cpu/cpuidle/current_governor_ro:menu


Get this bounty!!!

#StackBounty: #gnome #keyboard #xorg #gdm why am i getting ' event processing lagging behind' msg in Ubuntu 20.10

Bounty: 50

seeing my system logs, they are full of msgs like this:

/usr/libexec/gdm-x-session[2564]: (EE) event4  - SIGMACHIP USB Keyboard: client bug: event processing lagging behind by 25ms, your system is too slow
/usr/libexec/gdm-x-session[2564]: (EE) event4  - SIGMACHIP USB Keyboard: client bug: event processing lagging behind by 17ms, your system is too slow

i have a 12 core system which is essentially idle when i see this. it seems to happen since i upgraded to Ubuntu 20.10.

how can i find the root cause and how to eliminate this issue?

sys info:

model name  : AMD Ryzen 9 3900X 12-Core Processor
/sys/devices/system/cpu/cpufreq/policy10/scaling_driver:acpi-cpufreq
/sys/devices/system/cpu/cpufreq/policy0/scaling_governor:ondemand


grep . /sys/devices/system/cpu/cpuidle/*
/sys/devices/system/cpu/cpuidle/available_governors:ladder menu teo 
/sys/devices/system/cpu/cpuidle/current_driver:acpi_idle
/sys/devices/system/cpu/cpuidle/current_governor:menu
/sys/devices/system/cpu/cpuidle/current_governor_ro:menu


Get this bounty!!!

#StackBounty: #gnome #keyboard #xorg #gdm why am i getting ' event processing lagging behind' msg in Ubuntu 20.10

Bounty: 50

seeing my system logs, they are full of msgs like this:

/usr/libexec/gdm-x-session[2564]: (EE) event4  - SIGMACHIP USB Keyboard: client bug: event processing lagging behind by 25ms, your system is too slow
/usr/libexec/gdm-x-session[2564]: (EE) event4  - SIGMACHIP USB Keyboard: client bug: event processing lagging behind by 17ms, your system is too slow

i have a 12 core system which is essentially idle when i see this. it seems to happen since i upgraded to Ubuntu 20.10.

how can i find the root cause and how to eliminate this issue?

sys info:

model name  : AMD Ryzen 9 3900X 12-Core Processor
/sys/devices/system/cpu/cpufreq/policy10/scaling_driver:acpi-cpufreq
/sys/devices/system/cpu/cpufreq/policy0/scaling_governor:ondemand


grep . /sys/devices/system/cpu/cpuidle/*
/sys/devices/system/cpu/cpuidle/available_governors:ladder menu teo 
/sys/devices/system/cpu/cpuidle/current_driver:acpi_idle
/sys/devices/system/cpu/cpuidle/current_governor:menu
/sys/devices/system/cpu/cpuidle/current_governor_ro:menu


Get this bounty!!!

#StackBounty: #gnome #keyboard #xorg #gdm why am i getting ' event processing lagging behind' msg in Ubuntu 20.10

Bounty: 50

seeing my system logs, they are full of msgs like this:

/usr/libexec/gdm-x-session[2564]: (EE) event4  - SIGMACHIP USB Keyboard: client bug: event processing lagging behind by 25ms, your system is too slow
/usr/libexec/gdm-x-session[2564]: (EE) event4  - SIGMACHIP USB Keyboard: client bug: event processing lagging behind by 17ms, your system is too slow

i have a 12 core system which is essentially idle when i see this. it seems to happen since i upgraded to Ubuntu 20.10.

how can i find the root cause and how to eliminate this issue?

sys info:

model name  : AMD Ryzen 9 3900X 12-Core Processor
/sys/devices/system/cpu/cpufreq/policy10/scaling_driver:acpi-cpufreq
/sys/devices/system/cpu/cpufreq/policy0/scaling_governor:ondemand


grep . /sys/devices/system/cpu/cpuidle/*
/sys/devices/system/cpu/cpuidle/available_governors:ladder menu teo 
/sys/devices/system/cpu/cpuidle/current_driver:acpi_idle
/sys/devices/system/cpu/cpuidle/current_governor:menu
/sys/devices/system/cpu/cpuidle/current_governor_ro:menu


Get this bounty!!!