[Klojum]

Any tip before proceed to upgrade from 20.04 to 22.04?

Rumor has it that Ubuntu 22.04 uses Python 3.10, which doesn't seem to play nice all the time with Kodi.

[Nosepull]

Any tip before proceed to upgrade from 20.04 to 22.04?

Rumor has it that Ubuntu 22.04 uses Python 3.10, which doesn't seem to play nice all the time with Kodi.

Yes, don't upgrade right now, Kodi keeps crashing!

[taorn]

Thanks a lot for the advice!

I wont upgrade and will be waiting for any further tip

[bernid]

Hi 
Thank you for this excellent guide, I have been using it for years. Recently I installed Ubuntu server 23.10 on a Fujitsu thin client S940 (Gemini Lake). I installed Kodi from the Ubuntu repository, not the PPA (since Kodi PPA doesn't work). I also installed Gnome Desktop minimal.
 

Code:

sudo apt install ubuntu-desktop-minimal

 I normally switch between Kodi standalone full screen and Ubuntu wayland Gui using the openbox login window.
But something isn't working right here.
Often, when using the login window after selecting the user and Kodi or Ubuntu, I get a black screen (no connection) and only unplugging the TV and plugging it in again gives the image. The new computer only has two DisplayPort ports. so I use a DP-HDMI cable adapter to connect to the TV (4k Oled LG).
What do you think about it? Maybe something is starting too fast and that's why there's a black screen?
Is it possible to reduce the resolution and refresh rate of the openbox login window lets say to 1920x1080? In full 4k resolution, the elements are very small and inconvenient. Maybe I should change something in /home/kodi/.config/openbox/autostart file?

[3dfx]

Do you have anything relating to set output/resolution?

For example:

openbox autostart script:
xrandr -d :0 --output HDMI2 --auto --mode 3840x2160 --rate 60 --set "Broadcast RGB" "Full" 

[bernid]

Do you have anything relating to set output/resolution?

For example:

openbox autostart script:
xrandr -d :0 --output HDMI2 --auto --mode 3840x2160 --rate 60 --set "Broadcast RGB" "Full" 

Hi, 
No, just like was recommended in the first post, so:

opepox autostart:
OUTPUT=`xrandr -display :0 -q | sed '/ connected/!d;s/ .*//;q'`

xrandr -display :0 --output $OUTPUT --set "Broadcast RGB" "Full"

when I changed to:

openpox autostart:
OUTPUT=`xrandr -display :0 -q | sed '/ connected/!d;s/ .*//;q'`

xrandr -display :0 --output $OUTPUT --mode 1920x1080 --rate 60 --set "Broadcast RGB" "Full"

there is no change and I have 3840x2160@60Hz (but after repluging DP-HDMI cable)

[3dfx]

Did you save the EDID infos an passed it through while booting?
Why you selecting FullHD resolution when you want 4k?

Could it be the DP-HDMI converter?

[bernid]

Thanks for trying to help.

Did you save the EDID infos an passed it through while booting?

Unfortunately I don't understand.

So I have two issues:
1. Set lower resolution for openbox login screen, (SOLVED see below EDIT)
2. Losing video connection when switching windows system (Kodi/Ubutu/Ubuntu on Xorg)

1. Native 4k resolution for login screen for user sitting at a distance of 4m from the TV is not practical and inconvenient. The elements  and text are too small. So reducing the resolution of login screen should provide better readability. See how it looks (photo taken from 1.5m):
Maybe this resolution can be set in different place than /home/kodi/.config/openbox/autostart ?





2. When I switch windows system e.g. from Ubuntu (wayland) to Kodi (by login out) I experience a temporary loss of connection to the TV. Only unplugging the DP-HDMI cable and plugging it in again restores the login screen.
I looked at dmesg and see errors:

dmesg:
[ 906.433584] rfkill: input handler enabled

[ 909.018698] rfkill: input handler disabled

[ 938.928845] rfkill: input handler enabled

[ 939.003426] evict_inodes inode 00000000c830a67a, i_count = 1, was skipped!

[ 939.753134] i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

[ 942.410612] rfkill: input handler disabled

Is there any way around this?

----------------------------------
EDIT: I've managed to solve point 1. (the first issue)
I needed to change scaling-factor in /usr/share/glib-2.0/schemas/org.gnome.desktop.interface.gschema.xml
See details: https://www.themtparty.com/fix-ubuntu-gn...n-scaling/