Michele Guerini Rocco

>"And this is true since July, not just recently." > >Thats pretty recent in regards to the OpenZFS release timetable, last release was from May. >It does still needs to...

Is this so hard to fix? All you have to do this is listening for the udev events of the disks (I presume) you need to mount the pool before...

I tested this and it works but is somewhat slower at picking up the signal than with Linux::FD. Also it sometimes happens the colors are not updated until I resize...

The title and the alt text could be stored in the png metadata. You can use ImageMagic: see [this](http://blog.client9.com/2007/08/19/editing-png-metadata-from-command-line.html).

I think it would be a good idea to zero pad the numbers: right know it's impossible to browse.

> But it seems this is very outdated, what is the new code change that's needed to be done and rebuild transmission? I've been maintaining this [patch](https://maxwell.ydns.eu/~rnhmjoj/transmission-seq.patch). It works fine...

ping @perexg

The exit code 99 seems to be coming from this line: https://github.com/alsa-project/alsa-utils/blob/ca82cf8ed63c10b5bd018624e29d07c765d3e5ff/alsactl/init/00main#L24 IIUC it means the device couldn't be identified, or the hardware-specific initialisation failed. Since I can later issue...

I don't think that's the issue: the settings are not being restored on boot, but they do if I manually run the same command later.

I'm not sure, given it has identified the display I'd say i2c is set up correctly. There is a number of similar issues in the upstream tracker, so it's probably...