1. The "use your own config" option in the LinHES Video Setup doesn't seem to do anything. I have my xorg.conf in /data/home/mythtv/templates/xorg.user, but whenever I check or uncheck the box, it overwrites /etc/X11/xorg.conf with the default configuration file. I found this section in /usr/MythVantage/bin/xconfig.sh:

I don't see anywhere where that $XORG_CONF variable is defined. The script sources /etc/profile, but it's not in there either.

2. Is there an easy way to use a screensaver, like in R5.5? I installed xscreensaver from the extra-testing repository, but one of the files in the package is an entry in /etc/pam.d, which would seem to indicate that a password is required to turn the screensaver off, which obviously won't do. A way to enable and disable a screensaver from LinHES setup would be nice.

3. I installed the Java JRE from extra-testing in order to run Azureus WebUI, but one of the required packages is libstdc++5, which is not in the LinHES repositories. I had to enable the ArchLinux "extra" repository and install it from there.

4. How does the automatic updating work? I enabled to install all updates, but it doesn't seem to have done anything, even though running pacman -Su shows updates available.

Other than that, I haven't encountered many issues. I've had to enable the ArchLinux repositories to install a few other things, including:
agg, gstreamer0.10, gstreamer0.10-base, liboil, libstdc++5, screen, libelf
Most of those are related to my temporary Hulu fix, other than screen and libelf which I needed to run a headless Azureus.

Flyspray please.



Flyspray please.



Flyspray please.



It has yet to be implemented. (I bet you thought I was going to say Flyspray)

_________________
Mike
My Hardware Profile

BTW - We may be starting to sound like broken records on the "flyspray" front, but the level of pain with trying to manually track issues in the run up to R5.5, made the need to use a real automated trouble ticket system glaringly obvious to everyone involved.

Bottom line, if people don't create flyspray tasks for the issues they encounter, they're going to get forgotten. On the plus side, we're actively working on things reported there, and maintaining the task list (priority, known workarounds, correcting oversights in the tasks, related issues, ...)