[Touch-packages] [Bug 1826403] Re: Ethernet won't connect when cable is plugged in at boot
Dear Sebastian, Thanks for your response. I've raised the bug upstream here: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/166 I'll try to keep this bug stream and that one coordinated. ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/issues #166 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/166 -- 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/1826403 Title: Ethernet won't connect when cable is plugged in at boot Status in network-manager package in Ubuntu: Confirmed Bug description: When booting Ubuntu 19.04 with the Ethernet cable plugged in, after boot, network manager won't connect. Unplugging and plugging back in the cable with the system running doesn't work to establish a connection. The workaround is to boot with the cable unplugged, then to plug it in after boot. This problem emerged immediately following an upgrade from 18.10 to 19.04. On the first boot networking was fine, but from the first reboot a networking connection through the Ethernet cable couldn't be established if the cable was plugged in at boot. This issue is also described here: https://askubuntu.com/questions/1135412/updated-to-19-04-and-no- ethernet-now/1135726#1135726 and here: https://ubuntu- mate.community/t/19-04-ethernet-wired-connection-refuses-to-connect- when-plugged-in-before-boot/19333/6 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 21:50:27 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto enp4s0f1 auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-23 (153 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.11.1 dev enp4s0f1 proto dhcp metric 100 169.254.0.0/16 dev enp4s0f1 scope link metric 1000 192.168.11.0/24 dev enp4s0f1 proto kernel scope link src 192.168.11.13 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2019-04-25T20:03:28.380204 nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH enp4s0f1 ethernet connectedfull limited /org/freedesktop/NetworkManager/Devices/2 Automatic connection e906293b-df71-435b-8909-7d88ca006540 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp3s0wifi unavailable limited limited /org/freedesktop/NetworkManager/Devices/3 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1826403/+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 1826403] [NEW] Ethernet won't connect when cable is plugged in at boot
Public bug reported: When booting Ubuntu 19.04 with the Ethernet cable plugged in, after boot, network manager won't connect. Unplugging and plugging back in the cable with the system running doesn't work to establish a connection. The workaround is to boot with the cable unplugged, then to plug it in after boot. This problem emerged immediately following an upgrade from 18.10 to 19.04. On the first boot networking was fine, but from the first reboot a networking connection through the Ethernet cable couldn't be established if the cable was plugged in at boot. This issue is also described here: https://askubuntu.com/questions/1135412/updated-to-19-04-and-no- ethernet-now/1135726#1135726 and here: https://ubuntu- mate.community/t/19-04-ethernet-wired-connection-refuses-to-connect- when-plugged-in-before-boot/19333/6 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 21:50:27 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto enp4s0f1 auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-23 (153 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.11.1 dev enp4s0f1 proto dhcp metric 100 169.254.0.0/16 dev enp4s0f1 scope link metric 1000 192.168.11.0/24 dev enp4s0f1 proto kernel scope link src 192.168.11.13 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2019-04-25T20:03:28.380204 nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH enp4s0f1 ethernet connectedfull limited /org/freedesktop/NetworkManager/Devices/2 Automatic connection e906293b-df71-435b-8909-7d88ca006540 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp3s0wifi unavailable limited limited /org/freedesktop/NetworkManager/Devices/3 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled disabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1826403 Title: Ethernet won't connect when cable is plugged in at boot Status in network-manager package in Ubuntu: New Bug description: When booting Ubuntu 19.04 with the Ethernet cable plugged in, after boot, network manager won't connect. Unplugging and plugging back in the cable with the system running doesn't work to establish a connection. The workaround is to boot with the cable unplugged, then to plug it in after boot. This problem emerged immediately following an upgrade from 18.10 to 19.04. On the first boot networking was fine, but from the first reboot a networking connection through the Ethernet cable couldn't be established if the cable was plugged in at boot. This issue is also described here: https://askubuntu.com/questions/1135412/updated-to-19-04-and-no- ethernet-now/1135726#1135726 and here: https://ubuntu- mate.community/t/19-04-ethernet-wired-connection-refuses-to-connect- when-plugged-in-before-boot/19333/6 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 21:50:27 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto enp4s0f1 auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-23 (153 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.11.1 dev enp4s0f1 proto dhcp metric 100 169.254.0.0/16 dev enp4s0f1 scope link met
[Touch-packages] [Bug 1545344] Re: package resolvconf 1.77ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
A round of dpkg reconfigure after reboot resolved the problem. ** Description changed: Error occurred when upgrading from 14.10 using do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 15.10 Package: resolvconf 1.77ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic i686 NonfreeKernelModules: fglrx wl ApportVersion: 2.19.1-0ubuntu5 AptOrdering: - resolvconf: Configure - NULL: ConfigurePending + resolvconf: Configure + NULL: ConfigurePending Architecture: i386 Date: Sun Feb 14 07:44:50 2016 DpkgTerminalLog: - Setting up resolvconf (1.77ubuntu1) ... - Processing triggers for resolvconf (1.77ubuntu1) ... - resolvconf: Error: /run/resolvconf/interface either does not exist or is not a directory - dpkg: error processing package resolvconf (--configure): - subprocess installed post-installation script returned error exit status 1 + Setting up resolvconf (1.77ubuntu1) ... + Processing triggers for resolvconf (1.77ubuntu1) ... + resolvconf: Error: /run/resolvconf/interface either does not exist or is not a directory + dpkg: error processing package resolvconf (--configure): + subprocess installed post-installation script returned error exit status 1 DuplicateSignature: package:resolvconf:1.77ubuntu1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-07-27 (1296 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) PackageArchitecture: all RelatedPackageVersions: - dpkg 1.18.2ubuntu5.1 - apt 1.0.10.2ubuntu1 + dpkg 1.18.2ubuntu5.1 + apt 1.0.10.2ubuntu1 SourcePackage: resolvconf Title: package resolvconf 1.77ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2016-02-13 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1545344 Title: package resolvconf 1.77ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in resolvconf package in Ubuntu: New Bug description: Error occurred when upgrading from 14.10 using do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 15.10 Package: resolvconf 1.77ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic i686 NonfreeKernelModules: fglrx wl ApportVersion: 2.19.1-0ubuntu5 AptOrdering: resolvconf: Configure NULL: ConfigurePending Architecture: i386 Date: Sun Feb 14 07:44:50 2016 DpkgTerminalLog: Setting up resolvconf (1.77ubuntu1) ... Processing triggers for resolvconf (1.77ubuntu1) ... resolvconf: Error: /run/resolvconf/interface either does not exist or is not a directory dpkg: error processing package resolvconf (--configure): subprocess installed post-installation script returned error exit status 1 DuplicateSignature: package:resolvconf:1.77ubuntu1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-07-27 (1296 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: resolvconf Title: package resolvconf 1.77ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2016-02-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1545344/+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 1545344] [NEW] package resolvconf 1.77ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Error occurred when upgrading from 14.10 using do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 15.10 Package: resolvconf 1.77ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic i686 NonfreeKernelModules: fglrx wl ApportVersion: 2.19.1-0ubuntu5 AptOrdering: resolvconf: Configure NULL: ConfigurePending Architecture: i386 Date: Sun Feb 14 07:44:50 2016 DpkgTerminalLog: Setting up resolvconf (1.77ubuntu1) ... Processing triggers for resolvconf (1.77ubuntu1) ... resolvconf: Error: /run/resolvconf/interface either does not exist or is not a directory dpkg: error processing package resolvconf (--configure): subprocess installed post-installation script returned error exit status 1 DuplicateSignature: package:resolvconf:1.77ubuntu1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-07-27 (1296 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: resolvconf Title: package resolvconf 1.77ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2016-02-13 (0 days ago) ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1545344 Title: package resolvconf 1.77ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in resolvconf package in Ubuntu: New Bug description: Error occurred when upgrading from 14.10 using do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 15.10 Package: resolvconf 1.77ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic i686 NonfreeKernelModules: fglrx wl ApportVersion: 2.19.1-0ubuntu5 AptOrdering: resolvconf: Configure NULL: ConfigurePending Architecture: i386 Date: Sun Feb 14 07:44:50 2016 DpkgTerminalLog: Setting up resolvconf (1.77ubuntu1) ... Processing triggers for resolvconf (1.77ubuntu1) ... resolvconf: Error: /run/resolvconf/interface either does not exist or is not a directory dpkg: error processing package resolvconf (--configure): subprocess installed post-installation script returned error exit status 1 DuplicateSignature: package:resolvconf:1.77ubuntu1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-07-27 (1296 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: resolvconf Title: package resolvconf 1.77ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2016-02-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1545344/+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 1519595] [NEW] No analog input for headphone microphone in system settings
Public bug reported: Up until just a few weeks ago my headphone microphone was working fine in Ubuntu 14.04, but recently the only input selection available in the settings menu is the 'Internal microphone'. I've looked in alsamixer, but it only has one entry for 'mic' and another for 'mic boost'. Plugging in the mic input drops the internal mic input to no sound, but the headphone mic doesn't seem to be sending any sound through to the computer. The stereo out jack is working fine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27 Uname: Linux 3.13.0-68-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: theron 9023 F pulseaudio /dev/snd/controlC0: theron 9023 F pulseaudio /dev/snd/pcmC0D0c: theron 9023 F...m pulseaudio CurrentDesktop: X-Cinnamon Date: Wed Nov 25 12:02:41 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-13 (772 days ago) InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to trusty on 2014-05-02 (571 days ago) dmi.bios.date: 09/14/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1449 dmi.board.vendor: Hewlett-Packard dmi.board.version: 65.2E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.13:bd09/14/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr0589110100242B10010020100:rvnHewlett-Packard:rn1449:rvr65.2E:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 0589110100242B10010020100 dmi.sys.vendor: Hewlett-Packard ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1519595 Title: No analog input for headphone microphone in system settings Status in pulseaudio package in Ubuntu: New Bug description: Up until just a few weeks ago my headphone microphone was working fine in Ubuntu 14.04, but recently the only input selection available in the settings menu is the 'Internal microphone'. I've looked in alsamixer, but it only has one entry for 'mic' and another for 'mic boost'. Plugging in the mic input drops the internal mic input to no sound, but the headphone mic doesn't seem to be sending any sound through to the computer. The stereo out jack is working fine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27 Uname: Linux 3.13.0-68-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: theron 9023 F pulseaudio /dev/snd/controlC0: theron 9023 F pulseaudio /dev/snd/pcmC0D0c: theron 9023 F...m pulseaudio CurrentDesktop: X-Cinnamon Date: Wed Nov 25 12:02:41 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-13 (772 days ago) InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to trusty on 2014-05-02 (571 days ago) dmi.bios.date: 09/14/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1449 dmi.board.vendor: Hewlett-Packard dmi.board.version: 65.2E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.13:bd09/14/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr0589110100242B10010020100:rvnHewlett-Packard:rn1449:rvr65.2E:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 0589110100242B10010020100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1519595/+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
