Hot answers tagged mythbuntu
This is explained in the release notes for Precise: By default, the 12.04.2 point release will ship with a newer 3.5.0-23.35 Ubuntu kernel from Quantal, and a matching X.org stack. This is based on the 184.108.40.206 Extended Upstream Stable Kernel Release...The purpose of providing a newer kernel in the 12.04.2 point release is for hardware enablement. This only ...
If you are a home user and using samba purely for file sharing from a server or NAS you’re probably not interested in sharing printers through it. If so, you can prevent this error from occurring by adding the following lines to your /etc/samba/smb.conf: printing = bsd printcap name = /dev/null Restart samba: /etc/init.d/smbd restart …check your logs: ...
You can get it to work: Back up /usr/share/mythtv/metadata/Movie/tmdb.py Grab the updated version of tmdb3.py from: https://raw.github.com/MythTV/mythtv/983bb0e4353d361f6c54f0de0c0db683b8d3be1d/mythtv/programs/scripts/metadata/Movie/tmdb3.py Save it, overwriting /usr/share/mythtv/metadata/Movie/tmdb.py Delete ~/.mythtv/pytmdb3.cache to clear out old values ...
Device: 14f7:0500 Technisat SkyStar USB HD No, I would not try those instructions: LinuxTV.org >> How to Obtain, Build and Install V4L-DVB Device Drivers No need to over complicate things. Try what I used: (adapted from: LinuxTV.org > TerraTec Cinergy T Stick) NOTE: First unplug device, create/install driver, and then plug back in. You may need to ...
download the file dvb-usb-SkyStar_USB_HD_FW_v17_63.HEX.fw sudo cp your_download_dir/dvb-usb-SkyStar_USB_HD_FW_v17_63.HEX.fw /lib/firmware/dvb-usb-SkyStar_USB_HD_FW_v17_63.HEX.fw sudo chmod 755 /lib/firmware/dvb-usb-SkyStar_USB_HD_FW_v17_63.HEX.fw
To answer my own question: I was barking up the wrong tree. Mythbuntu's backup and restore correctly backs up and restores the password for the database with the database, but apparently not quite everywhere that it's needed (not in ~mythtv/.mythtv/config.xml). Manually editing the password in there to match the other config files (such as mysql.txt in the ...
A simple way to resolve this error is to edit line 40 (or thereabouts) in /usr/bin/mythbuntu-control-centre, removing the now obsolete(!) reference to AptMessageDialog. Note that you'll still want to keep the other 2 references in the import statement, so just insert a parenthesis at the end of line before, then delete the line containing AptMessageDialog) ...
I've been running a Zotac Zbox HD-NS21 for a couple of years as a dedicated mythbuntu frontend. Early on I noticed the HD ran pretty hot and it eventually failed. I jettisoned it and now run from a live usb stick. No issues. I'm currently running 12.04.3 64 bit with nividia 303.88, VDPAU normal. It's solid.
I had the same problem. The workaround is to do this manually - using the command: sudo usermod -a G mythtv <userid> (<userid> being your particular user login) Use the following command to confirm the change: id <userid> You will need to restart/reboot to then successfully run mythtv
I just installed mythtv and had the same issue. Steeldriver had the solution in a comment. Run gksu-properties and change the mode from su to sudo. This worked for me to fix the issue where it would not accept my password to stop/start the backend.
I had the same symptoms, lirc would not work when run as a service, but would work as a command. Note that in my case some of the keys worked, but only when lirc was not running (neither as a service nor a command). The problem was that evdev (an input driver for Xorg) was picking up the remote as a keyboard input device. Getting evdev to ignore the remote ...
Only top voted, non community-wiki answers of a minimum length are eligible