[Desktop-packages] [Bug 1673165] [NEW] Ignores route depending on other route
Public bug reported: Used versions: * Ubuntu 16.10 * network-manager 1.2.6-0ubuntu1 * network-manager-openvpn 1.2.6-2ubuntu1 * openvpn 2.3.11-1ubuntu2 Just like iputils refuses to add routes where it doesn't has a route to the gateway on the device, openvpn seems pretty much to do the same. % sudo /usr/lib/NetworkManager/nm-openvpn-service --debug [...] nm-openvpn[16132]: [helper-16342] environment: script_type=up nm-openvpn[16132]: [helper-16342] environment: dev_type=tun nm-openvpn[16132]: [helper-16342] environment: dev=tun0 nm-openvpn[16132]: [helper-16342] environment: link_mtu=1542 nm-openvpn[16132]: [helper-16342] environment: tun_mtu=1500 nm-openvpn[16132]: [helper-16342] environment: script_context=init nm-openvpn[16132]: [helper-16342] environment: route_gateway_2=172.19.200.141 nm-openvpn[16132]: [helper-16342] environment: route_netmask_2=255.255.255.0 nm-openvpn[16132]: [helper-16342] environment: route_network_2=172.19.200.0 nm-openvpn[16132]: [helper-16342] environment: route_gateway_1=172.19.200.141 nm-openvpn[16132]: [helper-16342] environment: route_netmask_1=255.255.0.0 nm-openvpn[16132]: [helper-16342] environment: route_network_1=172.19.0.0 nm-openvpn[16132]: [helper-16342] environment: route_vpn_gateway=172.19.200.141 nm-openvpn[16132]: [helper-16342] environment: route_net_gateway=192.168.178.1 nm-openvpn[16132]: [helper-16342] environment: ifconfig_remote=172.19.200.141 nm-openvpn[16132]: [helper-16342] environment: ifconfig_local=172.19.200.142 nm-openvpn[16132]: [helper-16342] environment: common_name=server nm-openvpn[16132]: [helper-16342] environment: trusted_port=1194 nm-openvpn[16132]: [helper-16342] environment: trusted_ip=IP_REMOVED nm-openvpn[16132]: [helper-16342] environment: untrusted_port=1194 nm-openvpn[16132]: [helper-16342] environment: untrusted_ip=IP_REMOVED [...TLS certs etc] nm-openvpn[16132]: [helper-16342] environment: verb=10 nm-openvpn[16132]: [helper-16342] environment: daemon=0 nm-openvpn[16132]: [helper-16342] environment: daemon_log_redirect=0 nm-openvpn[16132]: [helper-16342] environment: daemon_start_time=1489594872 nm-openvpn[16132]: [helper-16342] environment: daemon_pid=16267 nm-openvpn[16132]: [helper-16342] environment: proto_1=udp nm-openvpn[16132]: [helper-16342] environment: local_port_1=0 nm-openvpn[16132]: [helper-16342] environment: remote_1=HOST_NAME_REMOVED nm-openvpn[16132]: [helper-16342] environment: remote_port_1=1194 [...] % ip r l | grep 172.19 172.19.200.0/24 via 172.19.200.141 dev tun0 proto static metric 50 172.19.200.141 dev tun0 proto kernel scope link src 172.19.200.142 metric 50 I don't see anything happening to the routes wrt errors: Wed Mar 15 17:21:15 2017 us=306238 PUSH: Received control message: 'PUSH_REPLY,route 172.19.0.0 255.255.0.0,route 172.19.200.0 255.255.255.0,ping 10,ping-restart 120,ifconfig 172.19.200.142 172.19.200.141' Wed Mar 15 17:21:15 2017 us=306271 OPTIONS IMPORT: timers and/or timeouts modified Wed Mar 15 17:21:15 2017 us=306287 OPTIONS IMPORT: --ifconfig/up options modified Wed Mar 15 17:21:15 2017 us=306290 OPTIONS IMPORT: route options modified Wed Mar 15 17:21:15 2017 us=306371 ROUTE_GATEWAY 192.168.178.1/255.255.255.0 IFACE=eth0 HWADDR=54:ee:75:51:75:eb Wed Mar 15 17:21:15 2017 us=324890 TUN/TAP device tun0 opened Wed Mar 15 17:21:15 2017 us=324925 TUN/TAP TX queue length set to 100 Wed Mar 15 17:21:15 2017 us=324964 /usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper --debug 6 16132 --bus-name org.freedesktop.NetworkManager.openvpn --tun -- tun0 1500 1542 172.19.200.142 172.19.200.141 init Wed Mar 15 17:21:15 2017 us=325278 PKCS#11: __pkcs11h_forkFixup entry pid=16342, activate_slotevent=1 Wed Mar 15 17:21:15 2017 us=325329 PKCS#11: __pkcs11h_forkFixup return nm-openvpn[16132]: [helper-16342] command line: "/usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper" "--debug" "6" "16132" "--bus-name" "org.freedesktop.NetworkManager.openvpn" "--tun" "--" "tun0" "1500" "1542" "172.19.200.142" "172.19.200.141" "init" nm-openvpn[16132]: [helper-16342] environment: script_type=up I'm figuring it's trying to add the route before the network route itself is there, which leads to expected results when testing: % sudo ip link add foobar0 type dummy % sudo ip r a 172.19.0.0/16 dev foobar0 via 172.19.200.141 RTNETLINK answers: Network is unreachable If you use openvpn directly though, it works just fine: % ip r l | grep 172.19 % % sudo openvpn client.conf [...] Wed Mar 15 17:42:13 2017 /sbin/ip addr add dev tun0 local 172.19.200.142 peer 172.19.200.141 Wed Mar 15 17:42:13 2017 /sbin/ip route add 172.19.0.0/16 via 172.19.200.141 Wed Mar 15 17:42:13 2017 /sbin/ip route add 172.19.200.0/24 via 172.19.200.141 [...] % ip r l | grep 172.19 172.19.0.0/16 via 172.19.200.141 dev tun0 172.19.200.0/24 via 172.19.200.141 dev tun0 172.19.200.141 dev tun0 proto kernel scope link src 172.19.200.142 So I'll be blaming
[Desktop-packages] [Bug 1447501] [NEW] deja-dup crashes on start when using S3
Public bug reported: Backtrace when starting deja-dup backup to S3 (either via GUI or using deja-dup --backup): Traceback (most recent call last): File /usr/bin/duplicity, line 1500, in module with_tempdir(main) File /usr/bin/duplicity, line 1494, in with_tempdir fn() File /usr/bin/duplicity, line 1327, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File /usr/lib/python2.7/dist-packages/duplicity/commandline.py, line 1047, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File /usr/lib/python2.7/dist-packages/duplicity/backend.py, line 221, in get_backend obj = get_backend_object(url_string) File /usr/lib/python2.7/dist-packages/duplicity/backend.py, line 207, in get_backend_object return factory(pu) File /usr/lib/python2.7/dist-packages/duplicity/backends/_boto_single.py, line 161, in __init__ self.resetConnection() File /usr/lib/python2.7/dist-packages/duplicity/backends/_boto_single.py, line 183, in resetConnection self.conn = get_connection(self.scheme, self.parsed_url, self.storage_uri) File /usr/lib/python2.7/dist-packages/duplicity/backends/_boto_single.py, line 97, in get_connection assert scheme == 's3' AssertionError ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: deja-dup 32.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 23 10:43:45 2015 InstallationDate: Installed on 2013-05-06 (716 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: deja-dup UpgradeStatus: Upgraded to vivid on 2014-10-23 (181 days ago) ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1447501 Title: deja-dup crashes on start when using S3 Status in deja-dup package in Ubuntu: New Bug description: Backtrace when starting deja-dup backup to S3 (either via GUI or using deja-dup --backup): Traceback (most recent call last): File /usr/bin/duplicity, line 1500, in module with_tempdir(main) File /usr/bin/duplicity, line 1494, in with_tempdir fn() File /usr/bin/duplicity, line 1327, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File /usr/lib/python2.7/dist-packages/duplicity/commandline.py, line 1047, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File /usr/lib/python2.7/dist-packages/duplicity/backend.py, line 221, in get_backend obj = get_backend_object(url_string) File /usr/lib/python2.7/dist-packages/duplicity/backend.py, line 207, in get_backend_object return factory(pu) File /usr/lib/python2.7/dist-packages/duplicity/backends/_boto_single.py, line 161, in __init__ self.resetConnection() File /usr/lib/python2.7/dist-packages/duplicity/backends/_boto_single.py, line 183, in resetConnection self.conn = get_connection(self.scheme, self.parsed_url, self.storage_uri) File /usr/lib/python2.7/dist-packages/duplicity/backends/_boto_single.py, line 97, in get_connection assert scheme == 's3' AssertionError ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: deja-dup 32.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 23 10:43:45 2015 InstallationDate: Installed on 2013-05-06 (716 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: deja-dup UpgradeStatus: Upgraded to vivid on 2014-10-23 (181 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1447501/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245516] [NEW] owncloud integration fails at HTTP basic auth
Public bug reported: When trying to add an owncloud server to the online accounts, the adding fails because the HTTP Basic auth does not get handled. The relevant error message is unexpected response from server. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: evolution-data-server-goa 3.8.5-1ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 15:31:51 2013 InstallationDate: Installed on 2013-05-06 (174 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: evolution-data-server UpgradeStatus: Upgraded to saucy on 2013-10-17 (10 days ago) ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome3-ppa saucy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1245516 Title: owncloud integration fails at HTTP basic auth Status in “evolution-data-server” package in Ubuntu: New Bug description: When trying to add an owncloud server to the online accounts, the adding fails because the HTTP Basic auth does not get handled. The relevant error message is unexpected response from server. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: evolution-data-server-goa 3.8.5-1ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 15:31:51 2013 InstallationDate: Installed on 2013-05-06 (174 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: evolution-data-server UpgradeStatus: Upgraded to saucy on 2013-10-17 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1245516/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1106908] Re: Sound Recorder can not record sound
This is a bug present in 13.04, 13.10, gnome stable as well as staging ppas. It's utterly silly and makes a whole program unusable, please stop playing the triage and blame game and start debugging this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-media in Ubuntu. https://bugs.launchpad.net/bugs/1106908 Title: Sound Recorder can not record sound Status in One Hundred Paper Cuts: Confirmed Status in “gnome-media” package in Ubuntu: Triaged Bug description: Opened Sound Recorder. Pushed button Record As --nothing happened Pushed button Record Sound --nothing happened ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-media 3.4.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4 Uname: Linux 3.8.0-2-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Sun Jan 27 08:40:12 2013 InstallationDate: Installed on 2013-01-04 (22 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130102) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-media UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1106908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1153488] Re: Treats bluetooth input device batteries as batteries
FWIW, not fixed in the staging ppa. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1153488 Title: Treats bluetooth input device batteries as batteries Status in “gnome-power-manager” package in Ubuntu: Invalid Status in “upower” package in Ubuntu: Fix Released Status in “gnome-power-manager” source package in Precise: Invalid Status in “upower” source package in Precise: Fix Committed Status in “gnome-power-manager” source package in Quantal: Invalid Status in “upower” source package in Quantal: Confirmed Status in “gnome-power-manager” source package in Raring: Invalid Status in “upower” source package in Raring: Fix Committed Status in “gnome-power-manager” source package in Saucy: Invalid Status in “upower” source package in Saucy: Fix Released Bug description: [Impact] * There are many Bluetooth devices with battery information inside. When they are treated as system battery, it will make the system poweroff/suspend/hibernate when some Bluetooth device has critical low battery. It is a very annoying behavior for the users. Originally, there is no such Bluetooth battery information until Ubuntu 12.04 brings linux-quantal-lts and linux-raring-lts, so those linux kernels also bring this issue. [Test Case] * Pair some Bluetooth devices, such as Apple Wireless Mouse or Apple Wireless Keyboard. * Click the power indicator and you can find Apple Wireless Mouse is listed as system battery, and there is no Apple Wireless Keyboard. If you open gnome-power-statistics, you can find the 'Supply' field of Apple Wireless Mouse is 'Yes' but it should not be. [Regression Potential] * There is no obvious regression as I know. [Other Info] * Most patches are from upstream, modified to fix the conflicts, and made by the same developer (i.e. fourdollars). * We need another patch from https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d0a934b764c67b4bf626f5b7cf725a6e3066afd2 to make Apple Wireless Keyboard showing. [Original Bug Description] This is a weird one... the system is an HP Pavilion 23 All In One and is powered by a large power supply brick. I currently have an Apple Magic Mouse connected via Bluetooth. As soon as the mouse is connected, the Battery indicator shows up and clicking on that shows that the system is reading my mouse as a battery! See the attached screen shot for what I see in the Power status. Looking at hcitool: ubuntu@201206-11396:~$ hcitool dev Devices: hci0 9C:B7:0D:80:71:DB To make matters even more weird, I actually observed the battery indicator go from full to Critically Low and the system suspended itself. Keep in mind, again, that this system has NO battery, it's reading my bluetooth mouse as a battery device. I disconnected the magic mouse and the battery indicator went to Empty Red outline and status showed Battery Disconnected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 NonfreeKernelModules: wl fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1726 F pulseaudio Card0.Amixer.info: Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb4 irq 16' Mixer name : 'Realtek ALC269VC' Components : 'HDA:10ec0269,103c2aee,00100202' Controls : 21 Simple ctrls : 10 Date: Mon Mar 11 03:54:36 2013 HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MachineType: Hewlett-Packard a654 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=e2a5f4ae-dfa2-40be-a6c5-3ddb85dcf68e ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-23-generic N/A linux-backports-modules-3.5.0-23-generic N/A linux-firmware1.79.1 SourcePackage: linux StagingDrivers: rts_pstor UpgradeStatus: No upgrade log present (probably fresh install)
