[Desktop-packages] [Bug 1323594] Re: vpn auto-connect works, but doesn't connect automatically when network is available.
I have this bug in freshly installed Xubuntu 17.04. Ethernet doesn't connect automatically with VPN. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1323594 Title: vpn auto-connect works, but doesn't connect automatically when network is available. Status in network-manager package in Ubuntu: Fix Released Bug description: I'm having a bug in Ubuntu Trusty Tahr 14.04 LTS. The issue I'm having is that with a connection set to auto-connect to a PPTP-vpn, it does not auto-connect when (wireless)-network becomes available. Syslog returns this error: [1401130450.367538] [nm-vpn-connection.c:1374] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request. However it does connect when when connecting to the particular connection manually. e.g. I select the wireless network in the network-manager. This bug seems related to bugs: #280571 #1297849 #1247682 #1298047 The difference between my situation and the others is that vpn- autoconnect does work, it just doesn't work automatically. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1323594/+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 1310489] Re: xorg.conf overwritten by booting system
On Ubuntu 17.04 gpu-manager overwrites xorg.conf Does this bug still persist? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1310489 Title: xorg.conf overwritten by booting system Status in Linux Mint: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Trusty: Fix Released Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 == SRU Request == There is a regression in the gpu-manager that causes it to revert user changes right before the first reboot after enabling the fglrx driver or the nvidia driver on a system with hybrid graphics (Intel+AMD or Intel+NVIDIA). This causes the gpu-manager to remove the current xorg.conf and to switch to Mesa. [Impact] * This regression makes it almost impossible to use binary drivers on systems with hybrid graphics. [Test Case] * Make sure to be using a hybrid system with Intel+AMD or Intel+NVIDIA GPUs. * Make sure that the gpu-manager is not disabled (only necessary if you disabled it manually). * Remove all fglrx and nvidia drivers (keep the nvidia-common and the nvidia-prime packages): sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove fglrx sudo apt-get --purge remove fglrx-updates * Install ubuntu-drivers-common from trusty-proposed. * Restart the system. * Install the binary driver (either fglrx or nvidia, according to the available discrete GPU), reboot, and check that the binary driver is enabled (attach your /var/log/gpu-manager.log) - Expected: the (AMD or NVIDIA) discrete GPU is enabled. - Bad behavior: the system switches back to the intel driver and the discrete GPU is not used, despite the fact that the system was configured properly. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A - Hello, I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M. After installing fglrx I generated the xorg.conf in the terminal with 'sudo aticonfig --adapter=all --initial' and it looked pretty good. Up to this point I was able to switch between the cards with the commands 'sudo aticonfig --px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the intigrated card to save power. After rebooting I realized that I was no longer able to switch between the cards and found that the xorg.conf will be overwritten whenever I modified it and reboot the system. The new (by boot) generated xorg.conf contains not the relevant information for switing between the cards. I attached both configuration in one file (xorg.conf.comparison). I will also provide the atisysteminfo-report.txt so far I will find the place where to attach. Edit: I fixed the error --> "AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]" but it changed not the bug of overwriting the xorg.conf. Regards, Uwe ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Unity Date: Mon Apr 21 08:43:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1985] Subsystem: Hewlett-Packard Company Device [103c:1985] InstallationDate: Installed on 2014-04-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=fdcb1eaf-eda9-48ee-9d5b-b44e1fc06687 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1985 dmi.board.vendor: Hewlett-Packard dmi.board.version: 01.13 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis
[Desktop-packages] [Bug 1650927] Re: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc)
I can ping DNS server by IP. Host are not reachable if accessed by domain names. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1650927 Title: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc) Status in network-manager package in Ubuntu: Confirmed Bug description: Access to local ethernet is possible (e.g. ping 192.168.2.2), access to internet is not possible: ping: ports.ubuntu.com: Name or service not known ping: www.google.com: Name or service not known It does not matter if my PowerBook G4 is connected via WLAN or ethernet, the effect is the same. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.2-2ubuntu4 ProcVersionSignature: Ubuntu 4.9.0-11.12-powerpc-smp 4.9.0 Uname: Linux 4.9.0-11-powerpc-smp ppc ApportVersion: 2.20.4-0ubuntu1 Architecture: powerpc CasperVersion: 1.379 Date: Thu Nov 3 18:13:07 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.3.1 dev wlP1p17s0 proto static metric 600 169.254.0.0/16 dev wlP1p17s0 scope link metric 1000 192.168.3.0/24 dev wlP1p17s0 proto kernel scope link src 192.168.3.2 metric 600 LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha powerpc (20161218) NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm PATH=(custom, no user) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Carcosa 82f9a6ba-8a34-4aa8-8bba-6520f8b73c62 802-11-wireless 1478196808 Thu 03 Nov 2016 06:13:28 PM UTC yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlP1p17s0 activated /org/freedesktop/NetworkManager/ActiveConnection/4 Wired connection 1 1a0d2e10-42f2-3154-b4f6-dfbec067bff3 802-3-ethernet 1478196172 Thu 03 Nov 2016 06:02:52 PM UTC yes 4294966297 no/org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-dev: DEVICETYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlP1p17s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 Carcosa 82f9a6ba-8a34-4aa8-8bba-6520f8b73c62 /org/freedesktop/NetworkManager/ActiveConnection/4 enP2p36s15f0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- -- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1650927/+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 1650927] Re: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc)
In Xubuntu 17.04 amd64: $ systemd-resolve google.com google.com: resolve call failed: DNSSEC validation failed: signature-expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1650927 Title: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc) Status in network-manager package in Ubuntu: Confirmed Bug description: Access to local ethernet is possible (e.g. ping 192.168.2.2), access to internet is not possible: ping: ports.ubuntu.com: Name or service not known ping: www.google.com: Name or service not known It does not matter if my PowerBook G4 is connected via WLAN or ethernet, the effect is the same. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.2-2ubuntu4 ProcVersionSignature: Ubuntu 4.9.0-11.12-powerpc-smp 4.9.0 Uname: Linux 4.9.0-11-powerpc-smp ppc ApportVersion: 2.20.4-0ubuntu1 Architecture: powerpc CasperVersion: 1.379 Date: Thu Nov 3 18:13:07 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.3.1 dev wlP1p17s0 proto static metric 600 169.254.0.0/16 dev wlP1p17s0 scope link metric 1000 192.168.3.0/24 dev wlP1p17s0 proto kernel scope link src 192.168.3.2 metric 600 LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha powerpc (20161218) NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm PATH=(custom, no user) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Carcosa 82f9a6ba-8a34-4aa8-8bba-6520f8b73c62 802-11-wireless 1478196808 Thu 03 Nov 2016 06:13:28 PM UTC yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlP1p17s0 activated /org/freedesktop/NetworkManager/ActiveConnection/4 Wired connection 1 1a0d2e10-42f2-3154-b4f6-dfbec067bff3 802-3-ethernet 1478196172 Thu 03 Nov 2016 06:02:52 PM UTC yes 4294966297 no/org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-dev: DEVICETYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlP1p17s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 Carcosa 82f9a6ba-8a34-4aa8-8bba-6520f8b73c62 /org/freedesktop/NetworkManager/ActiveConnection/4 enP2p36s15f0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- -- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1650927/+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 1582986] Re: NetworkManager service does not start during bootup
This happens only sometimes on my system. In most of cases NetworkManager starts normally but dnscrypt-proxy fails. It happens on two installations. $ sudo journalctl | grep network июл 26 11:53:24 sunsetshimmer systemd[1]: network.target: Found ordering cycle on network.target/start июл 26 11:53:24 sunsetshimmer systemd[1]: network.target: Found dependency on NetworkManager.service/start июл 26 11:53:24 sunsetshimmer systemd[1]: network.target: Found dependency on dbus.service/start июл 26 11:53:24 sunsetshimmer systemd[1]: network.target: Found dependency on basic.target/start июл 26 11:53:24 sunsetshimmer systemd[1]: network.target: Found dependency on sockets.target/start июл 26 11:53:24 sunsetshimmer systemd[1]: network.target: Found dependency on dnscrypt-proxy.socket/start июл 26 11:53:24 sunsetshimmer systemd[1]: network.target: Found dependency on network.target/start июл 26 11:53:24 sunsetshimmer systemd[1]: network.target: Breaking ordering cycle by deleting job NetworkManager.service/start июл 26 11:53:24 sunsetshimmer systemd[1]: NetworkManager.service: Job NetworkManager.service/start deleted to break ordering cycle starting with network.target/start июл 26 11:53:26 sunsetshimmer systemd[1]: Started Trigger resolvconf update for networkd DNS. июл 26 11:53:26 sunsetshimmer systemd[1]: Starting Raise network interfaces... июл 26 11:53:26 sunsetshimmer systemd[1]: Started Raise network interfaces. июл 26 11:53:26 sunsetshimmer systemd[1]: Starting Anonymizing overlay network for TCP (multi-instance-master)... июл 26 11:53:26 sunsetshimmer systemd[1]: Starting Anonymizing overlay network for TCP... июл 26 11:53:26 sunsetshimmer systemd[1]: Starting load-balanced unspoofable packet switching network... июл 26 11:53:26 sunsetshimmer systemd[1]: Started Anonymizing overlay network for TCP (multi-instance-master). июл 26 11:53:27 sunsetshimmer systemd[1]: Started load-balanced unspoofable packet switching network. июл 26 11:53:27 sunsetshimmer systemd[1]: Started Anonymizing overlay network for TCP. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1582986 Title: NetworkManager service does not start during bootup Status in network-manager package in Ubuntu: Confirmed Bug description: Ubuntu 16.04 4.4.0-22 systemd 229-4 network-manager 1.1.93 network-manager-gnome 1.2.0 Multiple services and targets are deleted by systemd to "break ordering cycle" (cf. boot.log), but NetworkManager is the only one of them (network.target,rpcbind,sysinit.target,open-iscsi.service,remote- fs-pre.target,iscsid.service,zfs-fuse.service - cf. their respective logs) which is not started after bootup: sudo systemctl status NetworkManager.service ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: inactive (dead) May 18 05:00:10 samsung-ubuntu systemd[1]: NetworkManager.service: Job NetworkManager.service/verify-active deleted to break ordering cycle starting with network.target/start Attachments: --- - journalctl -l -b0 --system _COMM=systemd > boot.log - systemctl -l status rpcbind > rpcbind.log - systemctl -l status network.target > network.target.txt - systemctl -l status remote-fs-pre.target > remote-fs-pre.target.log - systemctl -l status sysinit.target > sysinit.target.log - systemctl -l status zfs-fuse.service > zfs-fuse.service.log - systemctl -l status open-iscsi.service > open-iscsi.service.log - systemctl -l status iscsid.service > iscsid.service.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+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
