[Touch-packages] [Bug 1443095] Re: rsync updates of VMs fail due to known debian bug 741628
*** This bug is a duplicate of bug 1300367 *** https://bugs.launchpad.net/bugs/1300367 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1300367, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1300367 rsync 3.1.0 and 3.0.9 incompatibility -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1443095 Title: rsync updates of VMs fail due to known debian bug 741628 Status in rsync package in Ubuntu: New Bug description: scripts running backups hang rather than crashing, which makes recovery harder error messages look like rsync: [sender] write error: Broken pipe (32) inflate returned -3 (296 bytes) rsync error: error in rsync protocol data stream (code 12) at token.c(548) [receiver=3.0.9] rsync error: error in rsync protocol data stream (code 12) at io.c(837) [sender=3.1.0] There is a known fix upstream reported at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=741628 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rsync 3.1.0-2ubuntu0.1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 12 07:45:48 2015 SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1443095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not
** Bug watch added: Red Hat Bugzilla #1166199 https://bugzilla.redhat.com/show_bug.cgi?id=1166199 ** Also affects: network-manager (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1166199 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1432599 Title: Network-manager tries to manage virbr0, which it should not Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Fedora: Unknown Bug description: Since a recent upgrade in vivid, nm is trying to manage virbr0. This results in my main machine not getting a real IP address on eth0, and virtual machines not being able to use the network. This is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1166199 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 16 12:36:07 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-12-13 (92 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) IpRoute: default via 10.0.0.1 dev eth0 proto static metric 1024 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) http_proxy: http://localhost:8118/ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not
Taking a cue from https://bugzilla.redhat.com/show_bug.cgi?id=1166199 I worked around the issue by adding the following to my /etc/NetworkManager/NetworkManager.conf [keyfile] unmanaged-devices=interface-name:virbr0 Yet I imagine that the real solution is something more general. ** Changed in: network-manager (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1432599 Title: Network-manager tries to manage virbr0, which it should not Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Fedora: Unknown Bug description: Since a recent upgrade in vivid, nm is trying to manage virbr0. This results in my main machine not getting a real IP address on eth0, and virtual machines not being able to use the network. This is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1166199 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 16 12:36:07 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-12-13 (92 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) IpRoute: default via 10.0.0.1 dev eth0 proto static metric 1024 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) http_proxy: http://localhost:8118/ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1417568] Re: diff reports bogus differences on identical files
Would it be possible for you to provide two (non-sensitive) example files showing this behavior? ** Changed in: diffutils (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to diffutils in Ubuntu. https://bugs.launchpad.net/bugs/1417568 Title: diff reports bogus differences on identical files Status in diffutils package in Ubuntu: Incomplete Bug description: I run diff file1 file2 and I get a result where every single line of file1 is removed and then every single line of file2 is added. I look at them and they look identical. Then I copy and paste the two files at https://www.diffchecker.com/diff and it confirms that they are absolutely identical. I wanted to report this upstream, but I can't find a public a bugtracker. Is it possible that they use a f*g mailing list to discuss bugs?? Omg. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: diffutils 1:3.3-1 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 3 14:10:33 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.5 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.5 InstallationDate: Installed on 2013-10-11 (479 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: diffutils UpgradeStatus: Upgraded to trusty on 2014-05-24 (254 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/diffutils/+bug/1417568/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1397491] Re: /etc/init.d/cups restart or stop failure
** Package changed: ubuntu = cups (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1397491 Title: /etc/init.d/cups restart or stop failure Status in cups package in Ubuntu: New Bug description: I've observed on several occasions that i've been unable to get the cups daemon to respond to changes in configuration files and have been unable to log in as administrator via the web interface when i know that i should be able to; even though i did /etc/init.d/cups restart. Finally figured it out! I did /etc/init.d/cups stop and using ps noticed 4 or 5 cupsd processes running! After killing all these off (oddly enough, a new one was spawned in their place), i did /etc/init.d/cups start and all was well! Based on my web search (which lead me to try this) this problem has been around for several years... sigh. Thanks to whoever might bring sanity to this. # lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 # apt-cache policy cups cups: Installed: 1.7.2-0ubuntu1.2 Candidate: 1.7.2-0ubuntu1.2 Version table: *** 1.7.2-0ubuntu1.2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 Packages 100 /var/lib/dpkg/status 1.7.2-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1397491/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394777] Re: dbus daemon running at 100%
** Package changed: ubuntu = dbus (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1394777 Title: dbus daemon running at 100% Status in “dbus” package in Ubuntu: New Bug description: This is on krillin r166. dbus-daemon was running at 100% for a few hours today. I noticed that when I launch System Settings, it causes dbus-daemon to run at lose to 100% until it opens. I also noticed that when I launched Systen Settings, after it finally opened, dbus-daemon settled down. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1394777/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391779] Re: curl not build with metalink support
Before curl can be built with metalink support someone needs to package libmetalink for Ubuntu, preferable by way of Debian. See also the Debian bug about building curl with metalink support: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683969 libmetalink packaging bugs: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=499159, https://bugs.launchpad.net/ubuntu/+bug/296283 ** Changed in: curl (Ubuntu) Importance: Undecided = Wishlist ** Changed in: curl (Ubuntu) Status: New = Triaged ** Bug watch added: Debian Bug tracker #683969 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683969 ** Bug watch added: Debian Bug tracker #499159 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499159 ** Also affects: curl (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683969 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1391779 Title: curl not build with metalink support Status in “curl” package in Ubuntu: Triaged Status in “curl” package in Debian: Unknown Bug description: The manpage for curl talks about having support for the --metalink flag but trying to use it in Ubuntu 14.04 fails with the following warning: Warning: --metalink option is ignored because the binary is built without the Warning: Metalink support. Can we get curl built with metalink support please? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1391779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391779] Re: curl not build with metalink support
Then there is the issue of curl being in Main. Hence any future libmetalink package too would have to be accepted into Main before curl could depend on it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1391779 Title: curl not build with metalink support Status in “curl” package in Ubuntu: Triaged Status in “curl” package in Debian: New Bug description: The manpage for curl talks about having support for the --metalink flag but trying to use it in Ubuntu 14.04 fails with the following warning: Warning: --metalink option is ignored because the binary is built without the Warning: Metalink support. Can we get curl built with metalink support please? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1391779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
