[Mythbuntu-bugs] [Bug 1159992] [NEW] Mysql settings being reset after MythTV update
Public bug reported: After doing a mythtv update using the 0.26 fixes branch mysql's setting are changed to only allow local connections. I have to reset this after every mythtv update. My mythtv.cnf file before an update. [mysqld] bind-address=0.0.0.0 max_connections=100 My mythtv.cnf file after an update. [mysqld] bind-address=127.0.0.1 max_connections=100 Here's the output of ifconfig eth0 Link encap:Ethernet HWaddr 00:11:d8:2d:5a:6f inet addr:192.168.1.56 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::211:d8ff:fe2d:5a6f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:29204658 errors:0 dropped:0 overruns:0 frame:0 TX packets:52133340 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3464655072 (3.4 GB) TX bytes:1224178208 (1.2 GB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8843878 errors:0 dropped:0 overruns:0 frame:0 TX packets:8843878 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2094011053 (2.0 GB) TX bytes:2094011053 (2.0 GB) I'm currently running the following version 0.26.0+fixes.20130320.c0419cd-0ubuntu0mythbuntu2 Thanks ** Affects: mythbuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Mythbuntu Bug Team, which is subscribed to Mythbuntu. https://bugs.launchpad.net/bugs/1159992 Title: Mysql settings being reset after MythTV update Status in Mythbuntu, Ubuntu derivative focused upon MythTV: New Bug description: After doing a mythtv update using the 0.26 fixes branch mysql's setting are changed to only allow local connections. I have to reset this after every mythtv update. My mythtv.cnf file before an update. [mysqld] bind-address=0.0.0.0 max_connections=100 My mythtv.cnf file after an update. [mysqld] bind-address=127.0.0.1 max_connections=100 Here's the output of ifconfig eth0 Link encap:Ethernet HWaddr 00:11:d8:2d:5a:6f inet addr:192.168.1.56 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::211:d8ff:fe2d:5a6f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:29204658 errors:0 dropped:0 overruns:0 frame:0 TX packets:52133340 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3464655072 (3.4 GB) TX bytes:1224178208 (1.2 GB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8843878 errors:0 dropped:0 overruns:0 frame:0 TX packets:8843878 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2094011053 (2.0 GB) TX bytes:2094011053 (2.0 GB) I'm currently running the following version 0.26.0+fixes.20130320.c0419cd-0ubuntu0mythbuntu2 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1159992/+subscriptions ___ Mailing list: https://launchpad.net/~mythbuntu-bugs Post to : mythbuntu-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~mythbuntu-bugs More help : https://help.launchpad.net/ListHelp
[Mythbuntu-bugs] [Bug 1159992] Re: Mysql settings being reset after MythTV update
I extracted the mythtv-database deb file and this is all I could find
relating to the mythtv.cnf file.
#For database fillings
#and mysql binding checks
if [ -f "${MYSQLCONFIG}" ]; then
db_get mythtv/public_bind
if [ -n "$RET" ] && [ $RET = true ]; then
NEWIP=`ifconfig | grep "inet addr:" | grep --invert-match 127.0.0.1
| sed ' s/inet addr://g; s/^[ \t]*//;s/[ \t]*$//; q;' | awk '{print $1}'`
sed -i -e 's/^#bind/bind/' ${MYSQLCONFIG}
else
sed -i -e 's/^bind/#bind/' ${MYSQLCONFIG}
fi
fi
I don't really understand all this but if there's extra info you want
from my system related to this let me know. It still resets the
mythtv.cnf file on me.
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/1159992
Title:
Mysql settings being reset after MythTV update
Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
New
Bug description:
After doing a mythtv update using the 0.26 fixes branch mysql's
setting are changed to only allow local connections. I have to reset
this after every mythtv update.
Here's the output of ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:d8:2d:5a:6f
inet addr:192.168.1.56 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::211:d8ff:fe2d:5a6f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29204658 errors:0 dropped:0 overruns:0 frame:0
TX packets:52133340 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3464655072 (3.4 GB) TX bytes:1224178208 (1.2 GB)
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8843878 errors:0 dropped:0 overruns:0 frame:0
TX packets:8843878 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2094011053 (2.0 GB) TX bytes:2094011053 (2.0 GB)
I'm currently running the following version
0.26.0+fixes.20130320.c0419cd-0ubuntu0mythbuntu2
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1159992/+subscriptions
___
Mailing list: https://launchpad.net/~mythbuntu-bugs
Post to : mythbuntu-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mythbuntu-bugs
More help : https://help.launchpad.net/ListHelp
[Mythbuntu-bugs] [Bug 1159992] Re: Mysql settings being reset after MythTV update
Yes, it's still happening on some of my servers. I think the postinst script fails the if after the db_get mythtv/public_bind line. I found the following in the config script but I'm not sure what it's doing. I don't get asked a question on an upgrade. db_input high mythtv/public_bind || true db_go || true -- You received this bug notification because you are a member of Mythbuntu Bug Team, which is subscribed to Mythbuntu. https://bugs.launchpad.net/bugs/1159992 Title: Mysql settings being reset after MythTV update Status in Mythbuntu, Ubuntu derivative focused upon MythTV: New Bug description: After doing a mythtv update using the 0.26 fixes branch mysql's setting are changed to only allow local connections. I have to reset this after every mythtv update. Here's the output of ifconfig eth0 Link encap:Ethernet HWaddr 00:11:d8:2d:5a:6f inet addr:192.168.1.56 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::211:d8ff:fe2d:5a6f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:29204658 errors:0 dropped:0 overruns:0 frame:0 TX packets:52133340 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3464655072 (3.4 GB) TX bytes:1224178208 (1.2 GB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8843878 errors:0 dropped:0 overruns:0 frame:0 TX packets:8843878 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2094011053 (2.0 GB) TX bytes:2094011053 (2.0 GB) I'm currently running the following version 0.26.0+fixes.20130320.c0419cd-0ubuntu0mythbuntu2 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1159992/+subscriptions ___ Mailing list: https://launchpad.net/~mythbuntu-bugs Post to : mythbuntu-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~mythbuntu-bugs More help : https://help.launchpad.net/ListHelp
[Mythbuntu-bugs] [Bug 1159992] Re: Mysql settings being reset after MythTV update
After more digging I found that if I set the value parameter of the following section of /var/cache/debconf/config.dat to true I'm able to do an update without /etc/mysql/conf.d/mythtv.cnf getting changed. Name: mythtv/public_bind Template: mythtv/public_bind Value: true Owners: mythtv-database Flags: seen I'm not sure this is the proper solution but it seems to fix my problem. Checking the config.dat file after the update shows that value is still set to true. My guess is that on a couple servers I chose not to allow public mysql access at first but then decided to change that later. -- You received this bug notification because you are a member of Mythbuntu Bug Team, which is subscribed to Mythbuntu. https://bugs.launchpad.net/bugs/1159992 Title: Mysql settings being reset after MythTV update Status in Mythbuntu, Ubuntu derivative focused upon MythTV: New Bug description: After doing a mythtv update using the 0.26 fixes branch mysql's setting are changed to only allow local connections. I have to reset this after every mythtv update. Here's the output of ifconfig eth0 Link encap:Ethernet HWaddr 00:11:d8:2d:5a:6f inet addr:192.168.1.56 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::211:d8ff:fe2d:5a6f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:29204658 errors:0 dropped:0 overruns:0 frame:0 TX packets:52133340 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3464655072 (3.4 GB) TX bytes:1224178208 (1.2 GB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8843878 errors:0 dropped:0 overruns:0 frame:0 TX packets:8843878 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2094011053 (2.0 GB) TX bytes:2094011053 (2.0 GB) I'm currently running the following version 0.26.0+fixes.20130320.c0419cd-0ubuntu0mythbuntu2 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1159992/+subscriptions ___ Mailing list: https://launchpad.net/~mythbuntu-bugs Post to : mythbuntu-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~mythbuntu-bugs More help : https://help.launchpad.net/ListHelp
[Mythbuntu-bugs] [Bug 1159992] Re: Mysql settings being reset after MythTV update
It was set to false. I'm pretty sure because I chose that option when installing and changed it later on. Any idea why mythbuntu-control- center only changes the mythtv.cnf file? -- You received this bug notification because you are a member of Mythbuntu Bug Team, which is subscribed to Mythbuntu. https://bugs.launchpad.net/bugs/1159992 Title: Mysql settings being reset after MythTV update Status in Mythbuntu, Ubuntu derivative focused upon MythTV: New Bug description: After doing a mythtv update using the 0.26 fixes branch mysql's setting are changed to only allow local connections. I have to reset this after every mythtv update. Here's the output of ifconfig eth0 Link encap:Ethernet HWaddr 00:11:d8:2d:5a:6f inet addr:192.168.1.56 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::211:d8ff:fe2d:5a6f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:29204658 errors:0 dropped:0 overruns:0 frame:0 TX packets:52133340 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3464655072 (3.4 GB) TX bytes:1224178208 (1.2 GB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8843878 errors:0 dropped:0 overruns:0 frame:0 TX packets:8843878 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2094011053 (2.0 GB) TX bytes:2094011053 (2.0 GB) I'm currently running the following version 0.26.0+fixes.20130320.c0419cd-0ubuntu0mythbuntu2 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1159992/+subscriptions ___ Mailing list: https://launchpad.net/~mythbuntu-bugs Post to : mythbuntu-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~mythbuntu-bugs More help : https://help.launchpad.net/ListHelp
[Mythbuntu-bugs] [Bug 1181335] [NEW] Menu bar still showing after reboot
Public bug reported: The menu bar stays showing after some reboots but not all on my frontend boxes. I'm running Mythbuntu 12.10. It really seems to be hit or miss. It doesn't seem to matter if it's a reboot or a start from a powered off state. If I close mythfrontend and restart it from the menu the menu bar is hidden like it should be. I'm assuming it's a race condition but I don't really know where to start debugging. ** Affects: mythbuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Mythbuntu Bug Team, which is subscribed to Mythbuntu. https://bugs.launchpad.net/bugs/1181335 Title: Menu bar still showing after reboot Status in Mythbuntu, Ubuntu derivative focused upon MythTV: New Bug description: The menu bar stays showing after some reboots but not all on my frontend boxes. I'm running Mythbuntu 12.10. It really seems to be hit or miss. It doesn't seem to matter if it's a reboot or a start from a powered off state. If I close mythfrontend and restart it from the menu the menu bar is hidden like it should be. I'm assuming it's a race condition but I don't really know where to start debugging. To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1181335/+subscriptions ___ Mailing list: https://launchpad.net/~mythbuntu-bugs Post to : mythbuntu-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~mythbuntu-bugs More help : https://help.launchpad.net/ListHelp
[Mythbuntu-bugs] [Bug 1184643] [NEW] Upgrade to 13.04 installs pulseaudio
Public bug reported: Upgrading from 12.10 to 13.04 installs pulseaudio. This causes all kinds of audio issues for me. Removing pulseaudio fixes things. Here's what I've found in my dist-upgrade log files. My apt.log file contains the following. new important dependency: pulseaudio:i386 Installing pulseaudio as Recommends of xfce4-volumed xfce4-volumed was installed with a clean 12.04 install and kept at the same version after the 12.10 upgrade. I'm assuming removing xfce4-volumed before upgrading to 13.04 would fix the problem. Not sure how this is done in the upgrade process itself though. ** Affects: mythbuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Mythbuntu Bug Team, which is subscribed to Mythbuntu. https://bugs.launchpad.net/bugs/1184643 Title: Upgrade to 13.04 installs pulseaudio Status in Mythbuntu, Ubuntu derivative focused upon MythTV: New Bug description: Upgrading from 12.10 to 13.04 installs pulseaudio. This causes all kinds of audio issues for me. Removing pulseaudio fixes things. Here's what I've found in my dist-upgrade log files. My apt.log file contains the following. new important dependency: pulseaudio:i386 Installing pulseaudio as Recommends of xfce4-volumed xfce4-volumed was installed with a clean 12.04 install and kept at the same version after the 12.10 upgrade. I'm assuming removing xfce4-volumed before upgrading to 13.04 would fix the problem. Not sure how this is done in the upgrade process itself though. To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1184643/+subscriptions ___ Mailing list: https://launchpad.net/~mythbuntu-bugs Post to : mythbuntu-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~mythbuntu-bugs More help : https://help.launchpad.net/ListHelp
[Mythbuntu-bugs] [Bug 1184643] Re: Upgrade to 13.04 installs pulseaudio
Just looking for an update on this. Would the proper solution for this be to have a 13.04 upgrage remove xfce4-volumed and install xfce4-mixer instead? I think that would work fine for my installs. -- You received this bug notification because you are a member of Mythbuntu Bug Team, which is subscribed to Mythbuntu. https://bugs.launchpad.net/bugs/1184643 Title: Upgrade to 13.04 installs pulseaudio Status in Mythbuntu, Ubuntu derivative focused upon MythTV: New Status in “update-manager” package in Ubuntu: New Status in “xfce4-volumed” package in Ubuntu: New Bug description: Upgrading from 12.10 to 13.04 installs pulseaudio. This causes all kinds of audio issues for me. Removing pulseaudio fixes things. Here's what I've found in my dist-upgrade log files. My apt.log file contains the following. new important dependency: pulseaudio:i386 Installing pulseaudio as Recommends of xfce4-volumed xfce4-volumed was installed with a clean 12.04 install and kept at the same version after the 12.10 upgrade. I'm assuming removing xfce4-volumed before upgrading to 13.04 would fix the problem. Not sure how this is done in the upgrade process itself though. To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1184643/+subscriptions ___ Mailing list: https://launchpad.net/~mythbuntu-bugs Post to : mythbuntu-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~mythbuntu-bugs More help : https://help.launchpad.net/ListHelp
[Mythbuntu-bugs] [Bug 1184643] Re: Upgrade to 13.04 installs pulseaudio
Just upgraded another system and pulseaudio was installed again. This time I removed (purged) xfce4-volumed before I did sudo do-release- upgrade. Digging into the apt.log file in /var/log/dist-upgrade shows the following. Installing pulseaudio as Recommends of gnome-settings-daemon Installing gnome-settings-daemon as Depends of gnome-control-center Installing gnome-control-center as Recommends of gnome-bluetooth new important dependency: gnome-bluetooth:i386 Installing gnome-bluetooth as Recommends of network-manager-gnome network-manager-gnome seems to be installed on my 12.10 systems. -- You received this bug notification because you are a member of Mythbuntu Bug Team, which is subscribed to Mythbuntu. https://bugs.launchpad.net/bugs/1184643 Title: Upgrade to 13.04 installs pulseaudio Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Triaged Status in “update-manager” package in Ubuntu: New Status in “xfce4-volumed” package in Ubuntu: New Bug description: Upgrading from 12.10 to 13.04 installs pulseaudio. This causes all kinds of audio issues for me. Removing pulseaudio fixes things. Here's what I've found in my dist-upgrade log files. My apt.log file contains the following. new important dependency: pulseaudio:i386 Installing pulseaudio as Recommends of xfce4-volumed xfce4-volumed was installed with a clean 12.04 install and kept at the same version after the 12.10 upgrade. I'm assuming removing xfce4-volumed before upgrading to 13.04 would fix the problem. Not sure how this is done in the upgrade process itself though. To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1184643/+subscriptions ___ Mailing list: https://launchpad.net/~mythbuntu-bugs Post to : mythbuntu-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~mythbuntu-bugs More help : https://help.launchpad.net/ListHelp
[Mythbuntu-bugs] [Bug 1307548] Re: updating from 12.04 to 14.04 causes apache to not start
The above didn't completely work for me. Since I had originally set up mythweb to not be the only web service I had to reconfigure mythweb twice. The first time to say mythweb would be the only web service running and the second to say it wouldn't. I dug a little further and found that instead of reconfiguring mythweb I could do the following. sudo nano /etc/apache2/sites-available/mythweb.conf Change any reference of /var/www/mythweb to /var/www/html/mythweb sudo a2ensite 000-default.conf The a2ensite command didn't seem to get run when I reconfigured mythweb and selected No for mythweb being the only web service. For some reason it had to be toggled to Yes and then back to No. -- You received this bug notification because you are a member of Mythbuntu Bug Team, which is subscribed to Mythbuntu. https://bugs.launchpad.net/bugs/1307548 Title: updating from 12.04 to 14.04 causes apache to not start Status in Mythbuntu, Ubuntu derivative focused upon MythTV: New Status in “mythtv” package in Ubuntu: Confirmed Bug description: Upgrading from 12.04 to 14.04 causes apache to not start: * Starting web server apache2 * * The apache2 configtest failed. Output of config test was: AH00526: Syntax error on line 30 of /etc/apache2/sites-enabled/mythweb.conf: You may not use 'Options +All' or 'Options -All'. Action 'configtest' failed. The Apache error log may have more information. This is because 12.04 had apache2 2.2. 14.04 has 2.4. The supported syntax changed between apache releases. Fixed by: $ sudo rm /etc/apache2/sites-available/mythweb.conf $ sudo dpkg-reconfigure mythweb $ sudo /etc/init.d/apache2 start I think during dist-upgrade we might want to either remove mythweb.conf so it can regenerate (easier/safer), or fix this in postinst for upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1307548/+subscriptions ___ Mailing list: https://launchpad.net/~mythbuntu-bugs Post to : mythbuntu-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~mythbuntu-bugs More help : https://help.launchpad.net/ListHelp
[Mythbuntu-bugs] [Bug 1184643] Re: Upgrade to 13.04 installs pulseaudio
Just upgraded my systems to 14.04 and pulseaudio was installed again. Here's what was in apt.log. Installing pulseaudio as Recommends of unity-settings-daemon Installing unity-settings-daemon as Depends of unity-control-center Installing unity-control-center as Recommends of gnome-bluetooth -- You received this bug notification because you are a member of Mythbuntu Bug Team, which is subscribed to Mythbuntu. https://bugs.launchpad.net/bugs/1184643 Title: Upgrade to 13.04 installs pulseaudio Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Triaged Status in “update-manager” package in Ubuntu: New Status in “xfce4-volumed” package in Ubuntu: Invalid Bug description: Upgrading from 12.10 to 13.04 installs pulseaudio. This causes all kinds of audio issues for me. Removing pulseaudio fixes things. Here's what I've found in my dist-upgrade log files. My apt.log file contains the following. new important dependency: pulseaudio:i386 Installing pulseaudio as Recommends of xfce4-volumed xfce4-volumed was installed with a clean 12.04 install and kept at the same version after the 12.10 upgrade. I'm assuming removing xfce4-volumed before upgrading to 13.04 would fix the problem. Not sure how this is done in the upgrade process itself though. To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1184643/+subscriptions ___ Mailing list: https://launchpad.net/~mythbuntu-bugs Post to : mythbuntu-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~mythbuntu-bugs More help : https://help.launchpad.net/ListHelp
[Mythbuntu-bugs] [Bug 1282868] Re: XFCE bar is visable over Mythfrontend on a fresh 14.04 install
I started noticing this after upgrading to 13.04. 13.10 and 14.04 also have this issue for me. Not sure if that helps track down the bug. Exiting mythfrontend and starting from the menu fixes it for me until the next reboot. -- You received this bug notification because you are a member of Mythbuntu Bug Team, which is subscribed to mythtv in Ubuntu. https://bugs.launchpad.net/bugs/1282868 Title: XFCE bar is visable over Mythfrontend on a fresh 14.04 install Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in “mythtv” package in Ubuntu: Confirmed Status in “xfce4-panel” package in Ubuntu: Confirmed Bug description: The XFCE bar is visable over mythfrontend on a fresh install. Reproduce: Install from Mythbuntu 14.04 ISO. Install with frontend+master backend. After install, when mythfrontend starts the XFCE bar is visable at the top of the screen. Historically, this has been an issue with Compiz (fixable by enabling the compiz legacy window mode). To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1282868/+subscriptions ___ Mailing list: https://launchpad.net/~mythbuntu-bugs Post to : mythbuntu-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~mythbuntu-bugs More help : https://help.launchpad.net/ListHelp
