It's a pleasant surprise to discover that you run a modern easy to use forum like this. Although I get frustrated with every flavor of every distro, something about Mate in particular always tells me you've got a good sense of taste.
I got the impression that as a new user I'm limited in the number of posts, so I'll list everything I haven't been able to figure out while using 18.04 LTS 32-bit. Let me know if I should split it up into several threads:
Regarding Kodi 17 "from Debian", from the Mate repos
Kodi (fullscreen) jumps from its own workspace to the active workspace whenever I adjust either screen backlight or audio volume using the dedicated keyboard keys for that. In other words, it seems to happen whenever the square indicator shows up and gives visual feedback for volume or brightness level.
Launch Kodi -> Change to another workspace -> Adjust backlight -> Kodi is now on screen.
With every window manager except "Marco (adaptive compositor)", i.e. on Marco (none), Macro (Compton GPU) and Compiz, Kodi will freeze video but continue audio playback when I adjust volume or screen backlight. This also happens in Debian 10 (buster) 32 bit when using their "Kodi from Debian". What might be the cause for this? Is there something that distinguishes Marco (adaptive compositor) which would reasonably exlpain it?
I'd like to understand what Mate does so that it uniquely among all the desktop environments and distros I've tried manages to run this version of Kodi without freezing upon backligt/volume adjustment. It would have been nice to be able to use Compiz, but I think I'll have to settle for understanding the problem.
Enabling Airplay in Kodi does not make the service visible on the network. Is there something about this "from Debian" build that I should be aware of? Airplay is a can of worms, but I can at least assure you that 1. airplay works on the network with other linux devices (OSMC on Rpi3), 2. the ports that Kodi forum members assert should be listened on for Airplay are not listened on, 3. the package that Kodi forum members mention --
shairplay-- doesn't exist in the Mate repos, 4. I compiled and installed
shairplayand confirmed that application worked and that zeroconf announcement worked, but Kodi still doesn't expose the service despite reasonably having access to the necessary library now, 5. avahi-daemon is running on the system, and other zeroconf services are announced from the system, 6. not a single mention of "air" anywhere in the kodi.log.
I would like to try making this version of Kodi work since other versions that I've tried have choppy playback in comparison, because of the very limited hardware.
Regarding smoothness of backlight adjustment in Mate
- Adjusting backlight is a little choppy, but completely fine (esp. compared to the horrible examples I've witnessed out there, like in Debian 10). However, adjusting it on Xubuntu Desktop is super smooth and feels great. Is it possible to get that experience on Mate somehow?
- Adjusting backlight noticeably writes to disk on every "tick", so if I were to hold down the button it would write to disk repeatedly for every level of backlight inbetween. I can hear the writes. Why is it doing this? I understand that you want to persist user preferences, but I mean why isn't the write deferred or throttled to not trigger during the actual interaction? Or maybe this doesn't matter and it's not what's making the experience less smooth.
Grateful for any explanations that can shed some light on these points.
Ubuntu Mate 18.04
Samsung NC10 netbook
- 2 GB RAM
- Intel Atom N270 @ 1.6 GHz x2
- Intel 945GME Graphics