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
…check your logs:
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 126.96.36.199 Extended Upstream Stable Kernel
Release...The purpose of providing a newer kernel in the 12.04.2 point
release is for hardware enablement.
This bug is already reported at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/883646.
You can mark yourself as affected by clicking on the yellow icon besides the text Does this bug affect you?, and then clicking on Yes, it affects me.
A workaround is suggested here, which suggests plugging a USB 2.0 device in the USB 3.0 port during startup.
An easier solution: add the following lines to /etc/network/interfaces
iface wlp1s0 inet dhcp
I have tested it on 16.04 LTS. May work on other versions.
How are Mythbuntu and MythTV related and what are their major differences?
Mythbuntu is the official operating system based on Ubuntu.
MythTV is software that acts like a PVR (personal video recording) system. It is not limited to Ubuntu but can be used on Fedora called MythDora.
What are the definitions of a frontend and backend in the case of ...
The way we do the repos is by MythTV major version number, and the command to add it would be
apt-add-repository ppa:mythbuntu/<MythTV Version number>
So for 0.26 it would be
Note that any point releases (such as 0.26.1) would still be the 0.26 version.
It is not in the Ubuntu manpage for touch but the exit status for touch are:
0 The touch utility executed successfully and all requested changes were made.
>0 An error occurred. The touch utility returned the number of files for
which the times could not be successfully modified.
So the 1 is the amount of times touch failed to execute. Most likely you ...
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
Can't say I have the same problem, however it seems similar:
On atom box running latest 12.04.1 ubuntu kernel.
When boot up I exit frontend. and then go to control-centre. Open it and select Infrared control and remotes; I select Android and then apply - it says nothing to do (this is OK).
I then leave control-centre in this state (it seems there is a bug ...
Remote's Play button is consumed by media-keys plugin for gnome-settings-daemon. To disable it and allow MythTV receiving the event, do:
$ gsettings set org.gnome.settings-daemon.plugins.media-keys active false
Also you will want to disable/uninstall xfce4-volumed to prevent it from trapping XF86AudioLowerVolume, XF86AudioRaiseVolume and XF86AudioMute.
Commands usually return a non-zero exit code when something has gone wrong.
As the mythsystemevent.cpp source shows, the MythTV backend dutifully returns the command's actual exit code if it's non-zero:
if (result != GENERIC_EXIT_OK)
LOG(VB_GENERAL, LOG_WARNING, LOC +
QString("Command '%1' returned %2")
So returned 1 tells you ...
I would say that Mythbuntu is the most straightforward way to get MythTV and a full desktop environment, as it already comes with the lightweight XFCE desktop environment.
Straight from the source:
Mythbuntu uses the XFCE desktop. All unnecessary standard Ubuntu applications such as LibreOffice, Evolution, and a full Gnome desktop are not installed in a ...
I can not talk about MythBuntu, because I have no experience with it, but, as far as the other three go, they are essentially the same core operating system with a different graphical user interface.
Ubuntu is using Unity as it's core graphical user interface experience, Lubuntu is using LXDE and Kubuntu is using KDE (The K Desktop environment).
If the mythtv user is created as a system user, it won't have a password set and might be configured so you cannot log in as it.
Typically, you can log in as another user using sudo. If your account was the one created as the administrator when you installed Mythtbuntu, you will already be set up to use sudo. You can then try:
sudo -i -u mythtv
Yes, I have done this when I moved from Mythbuntu 14.04 to Mythbuntu 16.04. I had the database backup (mythconverg-1317-20160708233351.sql.gz, automaticaly generated by the Mythbuntu 14.04 system) and the recordings on one drive, and then I installed Mythbuntu 16.04 on a different drive. I mounted the recordings in the same place in the filesystem as before. ...
While Upstarted is deprecated on 16.04, it is also installed and supported. The Q&A SysV, Upstart and systemd init script coexistence explains the relationship between Upstart and Systemd on 16.04.
That said, using both systemd and upstart together causes extra complexity to debug, as you've just run into. If MythTV provides a systemd unit file that can ...
Well 1st and unexpected is that Mythbuntu does not install CUPS by default, so the soultion was simple, install CUPS from Ubuntu software. smbd can now connect to CUPS, although no printers are used.
CUPS can be maintained by using http://localhost:631/ in a browser, not mention in info on Ubuntu software
I'm having the same problem. I fixed it by installing it manually for now, until the dependency is back in apt.
tar xvfz *.tar.gz
make PREFIX=/usr install
I also see two more bugs with the burn to dvd flow of mytharchive. See https://bugs....
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 ...
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 ...
Found the issue. This is what happens when you set the IP address for mythtv to 192.168.1.10 and the master server IP address to 127.0.0.1. Set them both to 192.168.1.10 and videos scan just fine. Problem resolved. Hope this helps someone!
I find that 150G for all of / is a quite good size. It allows for ample space for games, movies, music etc. while maintaining plenty of room for the OS.
My current install is:
It's worth noting that I have don installs (fully running) in 7G and most of my servers on EC2 have a 10G / and a 40G /home (though there are exceptions based on certain needs).
yeah your getting that error because your formatting an extended partition, and you need a primary partition with SATA. If you were setting up an IDE slave device this would work, but you need a partition table with SATA. Extended partitions don't work that way.
So, if you want to start over this should work out, its not too complicated but you definitely ...
The most common reasons for MythTV tuning issues are:
You didn't go though all the steps in mythtv-setup (specifically
steps 2, 3, and 4). These 3 steps define the tuner, data, and then
connect the tuner to the data. All 3 of these steps are required.
You set your tuner to use multiplexing (number of recordings > 1)
and it doesn't support multiplexing. This ...
I have 3 DVB cards and I was seeing zero byte recordings (no system freeze though). I fixed it by adding the
kernel parameter to the grub command line that boots the system. See this thread
for some discussion on it.