The analysis below is for 47~rc1, 47.1 fixes the issue by not doing the broken
code path on Linux systems.
I believe this is related to the mutter displayconfig:
We receive this property change:
signal time=1727173020.361584 sender=:1.34 -> destination=(null destination)
serial=11943 path=/org/gnome/Mutter/DisplayConfig;
interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
string "org.gnome.Mutter.DisplayConfig"
array [
dict entry(
string "Backlight"
variant struct {
uint32 7
array [
array [
dict entry(
string "connector"
variant string "eDP-1"
)
dict entry(
string "active"
variant boolean true
)
]
]
}
)
]
array [
]
This is missing value/min/max, hence the update_mutter_backlight() code does
not enter:
if (g_variant_lookup (monitor, "value", "i",
&backlight->brightness_val)) {
g_variant_lookup (monitor, "min", "i",
&backlight->brightness_min);
g_variant_lookup (monitor, "max", "i",
&backlight->brightness_max);
have_backlight = TRUE;
}
So we set those values to -1:
if (!have_backlight) {
backlight->brightness_val = -1;
backlight->brightness_min = -1;
backlight->brightness_max = -1;
}
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081294
Title:
gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/2081294/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
