Nope, just that rc4 is now a bit more stable than it was when first released 
1 Like
I actually have no idea what this means, but I think there must be a difference between r4.2-host-stable and r4.2-stable. @marmarek, what does host mean in these labels?
it’s about state of a package for dom0
2 Likes
Referencing here for visibility:
Update: this happens exactly once every dom0 reboot, after my dual-screen 4k setup goes into standbye mode. I heavily suspect this is related to the issues I had in 4.1 getting the same setup to work at all (see the issues with gnttab default size and so on). Once the screens wake for the first time it tries to redraw the windows open in the left (primary) screen, but not the right screen, which fails in some way or other, after which it stops trying to draw any windows from that VM until I reboot the VM. This doesn’t happen again after a second standbye/wake cycle, so I suspect this is (video) memory related somehow.
Thank you for the rc4 release. At install I did not have any issues. After starting I noticed that screen brightness cannot be changed (value changes but to no effect). It’s probably more kernel/linux related as I saw this issue on other distros for this model (w530) as well.
For me, System Tools → Power Manager → Handle Display Brightness Keys was not enabled.
Enabling the option made the brightness keys work again.
Not sure if this solution applies to your problem.
1 Like
Indeed, that was not enabled but it did not fix the issue. It is a model specific problem but. It would be easy to make a workaround. Using xrandr works so I just type the brightness I like.
1 Like