[Touch-packages] [Bug 1899193] Re: local denial of service due to parsing bugs in arfile.cc
its laging and not adding my pakadges or exepting my passwords -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1899193 Title: local denial of service due to parsing bugs in arfile.cc Status in apt package in Ubuntu: Fix Released Status in aptdaemon package in Ubuntu: Fix Released Status in python-apt package in Ubuntu: Fix Released Bug description: # GitHub Security Lab (GHSL) Vulnerability Report: `GHSL-2020-168`, `GHSL-2020-169`, `GHSL-2020-170` The [GitHub Security Lab](https://securitylab.github.com) team has identified potential security vulnerabilities in aptd. We are committed to working with you to help resolve these issues. In this report you will find everything you need to effectively coordinate a resolution of these issues with the GHSL team. If at any point you have concerns or questions about this process, please do not hesitate to reach out to us at `security...@github.com` (please include `GHSL-2020-168`, `GHSL-2020-169`, or `GHSL-2020-170` as a reference). If you are _NOT_ the correct point of contact for this report, please let us know! ## Summary The aptd daemon is a system service for installing and updating packages. It is accessible via [dbus](https://www.freedesktop.org/wiki/Software/dbus/) and has a method named "InstallFile" which is used for installing local `.deb` packages. Although polkit is used to prevent an unprivileged user from using "InstallFile" to install a malicious `.deb` package, it does not prevent aptd from parsing the contents of the `.deb` file. The parsing logic is provided by two packages, [libapt-pkg- dev](https://packages.ubuntu.com/focal/libapt-pkg-dev) and [python- apt](https://packages.ubuntu.com/source/focal/python-apt), and is implemented in C. These two packages contain several bugs, which an unprivileged user can exploit to trigger a local denial of service attack. ## Product aptd ## Tested Version * libapt-pkg-dev: version 2.0.2ubuntu0.1 * python-apt: 2.0.0ubuntu0.20.04.1 * Tested on Ubuntu 20.04.1 LTS ## Details ### Issue 1: aptd crash due to integer overflow in arfile.cc (GHSL-2020-168) A crafted `.deb` package can trigger a negative integer overflow at [arfile.cc, line 116](https://git.launchpad.net/ubuntu/+source/apt/tree/apt- pkg/contrib/arfile.cc?h=applied/ubuntu/focal- updates&id=4c264e60b524855b211751e1632ba48526f6b44d#n116): ```c Memb->Size -= Len; ``` Due to the integer overflow, the value of `Memb->Size` is `0x`. This leads to an out-of-memory error at [arfile.cc, line 602](https://git.launchpad.net/ubuntu/+source/python- apt/tree/python/arfile.cc?h=applied/ubuntu/focal- updates&id=0f7cc93acdb51d943114f1cd79002288c4ca4d24#n602): ```c char* value = new char[member->Size]; ``` The out-of-memory error causes aptd to crash. Please note that the source locations above refer to two separate files, both named `arfile.cc`. The first is from the libapt-pkg-dev package and the second is from the python-apt package. To trigger the crash, first use the attached source file named "createdeb.c" to generate the malicious `.deb` file: ```bash gcc createdeb.c -o createdeb ./createdeb crash test.deb ``` Now use `dbus-send` to send the malicious `.deb` file to aptd: ```bash $ dbus-send --system --type="method_call" --print-reply --dest=org.debian.apt /org/debian/apt org.debian.apt.InstallFile string:`realpath test.deb` boolean:true method return time=1602245339.731762 sender=:1.287 -> destination=:1.288 serial=8 reply_serial=2 string "/org/debian/apt/transaction/90f29de930854568964af1918f6ca5eb" $ dbus-send --system --type="method_call" --print-reply --dest=org.debian.apt /org/debian/apt/transaction/90f29de930854568964af1918f6ca5eb org.debian.apt.transaction.Run ``` Note that you need to use the "transaction id" returned by the first `dbus-send` in the second `dbus-send` command. Impact This issue may lead to local denial of service. Resources I have attached `createdeb.c`, which can be used to generate the malicious `.deb` file. ### Issue 2: aptd infinite loop due to integer overflow in arfile.cc (GHSL-2020-169) This issue is very similar to issue 1, but is caused by a different bug. This bug occurs during the call to `StrToNum` at [arfile.cc, line 92](https://git.launchpad.net/ubuntu/+source/apt/tree/apt- pkg/contrib/arfile.cc?h=applied/ubuntu/focal- updates&id=4c264e60b524855b211751e1632ba48526f6b44d#n92): ```c StrToNum(Head.Size,Memb->Size,sizeof(Head.Size)) == false) ``` The bug is due to the use of `strtoul` in [StrToNum](https://git.launchpad.net/ubuntu/+source/apt/tree/apt- pkg/contrib/strutl.cc?h=applied/ubuntu/focal- updates&id=4c264e60b524855b211751e1632ba48526f6b44d#n1169): ``
[Touch-packages] [Bug 1719220] [NEW] package libcupsmime1:amd64 2.1.3-4ubuntu0.3 failed to install/upgrade: package libcupsmime1:amd64 is already installed and configured
Public bug reported: yes ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libcupsmime1:amd64 2.1.3-4ubuntu0.3 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-lowlatency 4.10.17 Uname: Linux 4.10.0-35-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 CrashReports: 600:0:117:292008:2017-09-24 15:29:25.739557266 -0400:2017-09-24 15:29:26.739557266 -0400:/var/crash/libcups2:amd64.0.crash 600:0:117:292002:2017-09-24 15:29:25.775565147 -0400:2017-09-24 15:29:26.775565147 -0400:/var/crash/cups-daemon.0.crash 600:0:117:292016:2017-09-24 15:29:25.754560470 -0400:2017-09-24 15:29:26.754560470 -0400:/var/crash/libcupsmime1:amd64.0.crash CupsErrorLog: Date: Sun Sep 24 15:29:26 2017 DuplicateSignature: package:libcupsmime1:amd64:2.1.3-4ubuntu0.3 Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... dpkg: error processing package libcups2:amd64 (--configure): package libcups2:amd64 is already installed and configured ErrorMessage: package libcupsmime1:amd64 is already installed and configured InstallationDate: Installed on 2017-09-08 (16 days ago) InstallationMedia: Ubuntu-Studio 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Dell Inc. Latitude E5430 non-vPro Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-lowlatency root=UUID=f16090e3-ea0a-41ca-950c-f83d7e982692 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-lowlatency root=UUID=f16090e3-ea0a-41ca-950c-f83d7e982692 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: cups Title: package libcupsmime1:amd64 2.1.3-4ubuntu0.3 failed to install/upgrade: package libcupsmime1:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0MYF02 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd09/24/2014:svnDellInc.:pnLatitudeE5430non-vPro:pvr01:rvnDellInc.:rn0MYF02:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5430 non-vPro dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package need-duplicate-check xenial -- 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/1719220 Title: package libcupsmime1:amd64 2.1.3-4ubuntu0.3 failed to install/upgrade: package libcupsmime1:amd64 is already installed and configured Status in cups package in Ubuntu: New Bug description: yes ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libcupsmime1:amd64 2.1.3-4ubuntu0.3 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-lowlatency 4.10.17 Uname: Linux 4.10.0-35-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 CrashReports: 600:0:117:292008:2017-09-24 15:29:25.739557266 -0400:2017-09-24 15:29:26.739557266 -0400:/var/crash/libcups2:amd64.0.crash 600:0:117:292002:2017-09-24 15:29:25.775565147 -0400:2017-09-24 15:29:26.775565147 -0400:/var/crash/cups-daemon.0.crash 600:0:117:292016:2017-09-24 15:29:25.754560470 -0400:2017-09-24 15:29:26.754560470 -0400:/var/crash/libcupsmime1:amd64.0.crash CupsErrorLog: Date: Sun Sep 24 15:29:26 2017 DuplicateSignature: package:libcupsmime1:amd64:2.1.3-4ubuntu0.3 Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... dpkg: error processing package libcups2:amd64 (--configure): package libcups2:amd64 is already installed and configured ErrorMessage: package libcupsmime1:amd64 is already installed and configured InstallationDate: Installed on 2017-09-08 (16 days ago) InstallationMedia: Ubuntu-Studio 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Dell Inc. Latitude E5430 non-vPro Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-lowlatency root=UUID=f16090e3-ea0a-41ca-950c-f83d7e982692 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-lowlatency root=UUID=f16090e3-ea0a-41ca-950c-f83d7e982692 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: cups Title: package libcupsmime1:amd64 2.1.3-4ubuntu0.3 failed to install/upgrade: package libcupsmime1:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2014 dmi.bios.vendor: Dell Inc.
[Touch-packages] [Bug 1872146] Re: Audio on Headphones stopped working
After I removed it works, but the problems comes back afetr a few hours. -- 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/1872146 Title: Audio on Headphones stopped working Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio via my headphones worked yesterday, Today no such luck. When I plug in my headphone, Plasma picks it up but no sound. Bluetooth headset still works. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Apr 10 23:03:09 2020 InstallationDate: Installed on 2020-04-05 (5 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200404) PackageArchitecture: all ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872146/+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 1872146] Re: Audio on Headphones stopped working
*** This bug is a duplicate of bug 1866194 *** https://bugs.launchpad.net/bugs/1866194 Still seems to be the same. I booted from a Manjaro USB Pendrive. The sounds works then on all devices. Back in Kubuntu 20.04 only normal speakers works and Bluetooth HEadsets. Any audio via my Headphone Jack does not. Any info I can get. -- 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/1872146 Title: Audio on Headphones stopped working Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio via my headphones worked yesterday, Today no such luck. When I plug in my headphone, Plasma picks it up but no sound. Bluetooth headset still works. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Apr 10 23:03:09 2020 InstallationDate: Installed on 2020-04-05 (5 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200404) PackageArchitecture: all ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872146/+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 1872146] Re: Audio on Headphones stopped working
*** This bug is a duplicate of bug 1866194 *** https://bugs.launchpad.net/bugs/1866194 HI I did sudo apt-get install --reinstall alsa-base pulseaudio sudo alsa force-reload Did a restart and it sems to be working now. -- 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/1872146 Title: Audio on Headphones stopped working Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio via my headphones worked yesterday, Today no such luck. When I plug in my headphone, Plasma picks it up but no sound. Bluetooth headset still works. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Apr 10 23:03:09 2020 InstallationDate: Installed on 2020-04-05 (5 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200404) PackageArchitecture: all ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872146/+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 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
HI My problem returned. When I use analog I run pavucontrol-qt and then I select the correvt input device. I don't know why but it seems like the default audio selector does not work [Shaun .T - Chat @ Spike](https://spikenow.com/r/a/?ref=spike-organic- signature&_ts=hc2k8) [hc2k8] On April 24, 2020 at 21:21 GMT, David Bridson wrote: I'm experiencing the same problem on a fresh install of Ubuntu Mate 20.04 on a Dell XPS 13 9350. Sound works correctly using the internal speakers. If you plug in analog headphones to the 3.5mm jack, there is no sound from the headphones or the internal speakers. All relevant options are unmuted in Sound Settings. The Speaker Test exhibits the same behaviour. Analog headphones worked correctly on this system under 18.04. -- You received this bug notification because you are subscribed to a duplicate bug report (1872146). https://bugs.launchpad.net/bugs/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in gnome-control-center: Unknown Status in PulseAudio: New Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: In Progress Status in gnome-control-center source package in Focal: Invalid Status in pulseaudio source package in Focal: In Progress Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+subscriptions -- 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/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in gnome-control-center: Unknown Status in PulseAudio: New Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: In Progress Status in gnome-control-center source package in Focal: Invalid Status in pulseaudio source package in Focal: In Progress Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried
[Touch-packages] [Bug 1768552] [NEW] apt-add-repository fails to add key for PPA with non-ASCII name
Public bug reported: If the terminal is not configured for a UTF-8 locale, the following command fails: # sudo add-apt-repository ppa:cz.nic-labs/bird The BIRD Internet Routing Daemon PPA (by upstream & .deb maintainer) More info: https://launchpad.net/~cz.nic-labs/+archive/ubuntu/bird Press [ENTER] to continue or ctrl-c to cancel adding it gpg: keyring `/tmp/tmpsbr85z99/secring.gpg' created gpg: keyring `/tmp/tmpsbr85z99/pubring.gpg' created gpg: requesting key F9C59A45 from hkp server keyserver.ubuntu.com gpg: /tmp/tmpsbr85z99/trustdb.gpg: trustdb created gpg: key F9C59A45: public key "Launchpad Datov� schr�nky" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) 'ascii' codec can't decode byte 0xc3 in position 86: ordinal not in range(128) I'd expect it to work, but fail to display the characters that aren't supported. While I have a workaround, which is to switch locale, the context is that I'm trying to instruct the users of my application on how to install the above PPA and that's a lot more complicated if I have to explain to them how to check the locale and install a UTF-8 version of their locale and switch to it. --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-08-28 (1343 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Package: software-properties-common 0.96.20.7 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Tags: xenial Uname: Linux 4.4.0-119-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-08-01 (638 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected xenial ** Tags added: apport-collected xenial ** Description changed: If the terminal is not configured for a UTF-8 locale, the following command fails: # sudo add-apt-repository ppa:cz.nic-labs/bird The BIRD Internet Routing Daemon PPA (by upstream & .deb maintainer) More info: https://launchpad.net/~cz.nic-labs/+archive/ubuntu/bird Press [ENTER] to continue or ctrl-c to cancel adding it gpg: keyring `/tmp/tmpsbr85z99/secring.gpg' created gpg: keyring `/tmp/tmpsbr85z99/pubring.gpg' created gpg: requesting key F9C59A45 from hkp server keyserver.ubuntu.com gpg: /tmp/tmpsbr85z99/trustdb.gpg: trustdb created gpg: key F9C59A45: public key "Launchpad Datov� schr�nky" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) 'ascii' codec can't decode byte 0xc3 in position 86: ordinal not in range(128) I'd expect it to work, but fail to display the characters that aren't supported. - While I have a workaround, which is to switch locale, the context is - that I'm trying to instruct the users of my application on how to - install the above PPA and that's a lot more complicated if I have to - explain to them how to check the locale and install a UTF-8 version of - their locale and switch to it. + While I have a workaround, which is to switch locale, the context is that I'm trying to instruct the users of my application on how to install the above PPA and that's a lot more complicated if I have to explain to them how to check the locale and install a UTF-8 version of their locale and switch to it. + --- + ApportVersion: 2.20.1-0ubuntu2.16 + Architecture: amd64 + CurrentDesktop: GNOME-Flashback:Unity + DistroRelease: Ubuntu 16.04 + InstallationDate: Installed on 2014-08-28 (1343 days ago) + InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) + Package: software-properties-common 0.96.20.7 + PackageArchitecture: all + ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 + Tags: xenial + Uname: Linux 4.4.0-119-generic x86_64 + UpgradeStatus: Upgraded to xenial on 2016-08-01 (638 days ago) + UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1768552 Title: apt-add-repository fails to add key for PPA with non-ASCII name Status in software-properties package in Ubuntu: New Bug description: If the terminal is not configured for a UTF-8 locale, the following command fails: # sudo add-apt-repository ppa:cz.nic-labs/bird The BIRD Internet Routing Daemon PPA (by upstream & .deb maintainer) More info: https://launchpad.net/~cz.nic-labs/+archive/ubuntu/bird Press [ENTER] to continue or ctrl-c to cancel adding it gpg: keyring `/tmp/tmpsbr85z99/secring.gpg' created gpg: keyring `/tmp/tmpsbr85z99/pubrin
[Touch-packages] [Bug 1768552] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1768552/+attachment/5132102/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1768552 Title: apt-add-repository fails to add key for PPA with non-ASCII name Status in software-properties package in Ubuntu: New Bug description: If the terminal is not configured for a UTF-8 locale, the following command fails: # sudo add-apt-repository ppa:cz.nic-labs/bird The BIRD Internet Routing Daemon PPA (by upstream & .deb maintainer) More info: https://launchpad.net/~cz.nic-labs/+archive/ubuntu/bird Press [ENTER] to continue or ctrl-c to cancel adding it gpg: keyring `/tmp/tmpsbr85z99/secring.gpg' created gpg: keyring `/tmp/tmpsbr85z99/pubring.gpg' created gpg: requesting key F9C59A45 from hkp server keyserver.ubuntu.com gpg: /tmp/tmpsbr85z99/trustdb.gpg: trustdb created gpg: key F9C59A45: public key "Launchpad Datov� schr�nky" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) 'ascii' codec can't decode byte 0xc3 in position 86: ordinal not in range(128) I'd expect it to work, but fail to display the characters that aren't supported. While I have a workaround, which is to switch locale, the context is that I'm trying to instruct the users of my application on how to install the above PPA and that's a lot more complicated if I have to explain to them how to check the locale and install a UTF-8 version of their locale and switch to it. --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-08-28 (1343 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Package: software-properties-common 0.96.20.7 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Tags: xenial Uname: Linux 4.4.0-119-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-08-01 (638 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1768552/+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 1768552] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1768552/+attachment/5132103/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1768552 Title: apt-add-repository fails to add key for PPA with non-ASCII name Status in software-properties package in Ubuntu: New Bug description: If the terminal is not configured for a UTF-8 locale, the following command fails: # sudo add-apt-repository ppa:cz.nic-labs/bird The BIRD Internet Routing Daemon PPA (by upstream & .deb maintainer) More info: https://launchpad.net/~cz.nic-labs/+archive/ubuntu/bird Press [ENTER] to continue or ctrl-c to cancel adding it gpg: keyring `/tmp/tmpsbr85z99/secring.gpg' created gpg: keyring `/tmp/tmpsbr85z99/pubring.gpg' created gpg: requesting key F9C59A45 from hkp server keyserver.ubuntu.com gpg: /tmp/tmpsbr85z99/trustdb.gpg: trustdb created gpg: key F9C59A45: public key "Launchpad Datov� schr�nky" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) 'ascii' codec can't decode byte 0xc3 in position 86: ordinal not in range(128) I'd expect it to work, but fail to display the characters that aren't supported. While I have a workaround, which is to switch locale, the context is that I'm trying to instruct the users of my application on how to install the above PPA and that's a lot more complicated if I have to explain to them how to check the locale and install a UTF-8 version of their locale and switch to it. --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-08-28 (1343 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Package: software-properties-common 0.96.20.7 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Tags: xenial Uname: Linux 4.4.0-119-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-08-01 (638 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1768552/+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 1768552] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1768552/+attachment/5132104/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1768552 Title: apt-add-repository fails to add key for PPA with non-ASCII name Status in software-properties package in Ubuntu: New Bug description: If the terminal is not configured for a UTF-8 locale, the following command fails: # sudo add-apt-repository ppa:cz.nic-labs/bird The BIRD Internet Routing Daemon PPA (by upstream & .deb maintainer) More info: https://launchpad.net/~cz.nic-labs/+archive/ubuntu/bird Press [ENTER] to continue or ctrl-c to cancel adding it gpg: keyring `/tmp/tmpsbr85z99/secring.gpg' created gpg: keyring `/tmp/tmpsbr85z99/pubring.gpg' created gpg: requesting key F9C59A45 from hkp server keyserver.ubuntu.com gpg: /tmp/tmpsbr85z99/trustdb.gpg: trustdb created gpg: key F9C59A45: public key "Launchpad Datov� schr�nky" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) 'ascii' codec can't decode byte 0xc3 in position 86: ordinal not in range(128) I'd expect it to work, but fail to display the characters that aren't supported. While I have a workaround, which is to switch locale, the context is that I'm trying to instruct the users of my application on how to install the above PPA and that's a lot more complicated if I have to explain to them how to check the locale and install a UTF-8 version of their locale and switch to it. --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-08-28 (1343 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Package: software-properties-common 0.96.20.7 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Tags: xenial Uname: Linux 4.4.0-119-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-08-01 (638 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1768552/+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 1742250] Re: Adding and deleting a veth leaks a systemd unit
As a workaround, running systemctl daemon-reload removes all the leaked units. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1742250 Title: Adding and deleting a veth leaks a systemd unit Status in systemd package in Ubuntu: New Bug description: When I add a veth device: sudo ip link add name test1 type veth I see these systemd units appear: systemctl list-units --all | grep test sys-devices-virtual-net-test1.device loadedactive plugged /sys/devices/virtual/net/test1 sys-subsystem-net-devices-test1.device loadedactive plugged /sys/subsystem/net/devices/test1 However, if I then delete the veth: sudo ip link del dev test1 Then only one of the units is removed: systemctl list-units --all | grep test sys-devices-virtual-net-test1.device loadedactive plugged /sys/devices/virtual/net/test1 This is a big problem when running, for example, a Kubernetes cluster since each pod creation/deletion leaks a systemd unit. When enough have been leaked, systemd becomes unresponsive and the system is broken until reboot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 Date: Tue Jan 9 18:57:34 2018 Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Google Google Compute Engine ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=c66b8cf4-2a6c-4fb3-9f39-59483a6a025c ro scsi_mod.use_blk_mq=Y console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Google dmi.bios.version: Google dmi.board.asset.tag: 1AF4A7E8-D62B-D331-0693-3511A041DD96 dmi.board.name: Google Compute Engine dmi.board.vendor: Google dmi.chassis.type: 1 dmi.chassis.vendor: Google dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: dmi.product.name: Google Compute Engine dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1742250/+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 1742250] [NEW] Adding and deleting a veth leaks a systemd unit
Public bug reported: When I add a veth device: sudo ip link add name test1 type veth I see these systemd units appear: systemctl list-units --all | grep test sys-devices-virtual-net-test1.device loadedactive plugged /sys/devices/virtual/net/test1 sys-subsystem-net-devices-test1.device loadedactive plugged /sys/subsystem/net/devices/test1 However, if I then delete the veth: sudo ip link del dev test1 Then only one of the units is removed: systemctl list-units --all | grep test sys-devices-virtual-net-test1.device loadedactive plugged /sys/devices/virtual/net/test1 This is a big problem when running, for example, a Kubernetes cluster since each pod creation/deletion leaks a systemd unit. When enough have been leaked, systemd becomes unresponsive and the system is broken until reboot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 Date: Tue Jan 9 18:57:34 2018 Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Google Google Compute Engine ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=c66b8cf4-2a6c-4fb3-9f39-59483a6a025c ro scsi_mod.use_blk_mq=Y console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Google dmi.bios.version: Google dmi.board.asset.tag: 1AF4A7E8-D62B-D331-0693-3511A041DD96 dmi.board.name: Google Compute Engine dmi.board.vendor: Google dmi.chassis.type: 1 dmi.chassis.vendor: Google dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: dmi.product.name: Google Compute Engine dmi.sys.vendor: Google ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful uec-images ** Description changed: When I add a veth device: - sudo ip link add name test1 type veth + sudo ip link add name test1 type veth I see these systemd units appear: - systemctl list-units --all | grep test - smc-kubeadm-node-0: Tue Jan 9 19:02:41 2018 + systemctl list-units --all | grep test - sys-devices-virtual-net-test1.device - loadedactive plugged /sys/devices/virtual/net/test1 + sys-devices-virtual-net-test1.device + loadedactive plugged /sys/devices/virtual/net/test1 - sys-subsystem-net-devices-test1.device - loadedactive plugged /sys/subsystem/net/devices/test1 + sys-subsystem-net-devices-test1.device + loadedactive plugged /sys/subsystem/net/devices/test1 However, if I then delete the veth: - sudo ip link del dev test1 + sudo ip link del dev test1 Then only one of the units is removed: - systemctl list-units --all | grep test - smc-kubeadm-node-0: Tue Jan 9 19:03:53 2018 + systemctl list-units --all | grep test - sys-devices-virtual-net-test1.device - loadedactive plugged /sys/devices/virtual/net/test1 + sys-devices-virtual-net-test1.device + loadedactive plugged /sys/devices/virtual/net/test1 This is a big problem when running, for example, a Kubernetes cluster since each pod creation/deletion leaks a systemd unit. When enough have been leaked, systemd becomes unresponsive and the system is broken until reboot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 Date: Tue Jan 9 18:57:34 2018 Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Google Google Compute Engine ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=c66b8cf4-2a6c-4fb3-9f39-59483a6a025c ro scsi_mod.use_blk_mq=Y console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Google dmi.bios.version: Google dmi.board.asset.tag: 1AF4A7E8-D62B-D331-0693-3511A041DD96 dmi.board.name: Google Compute Engine dmi.board.vendor: Google dmi.chassis.type: 1 dmi.chassis.vendor: Google dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: dmi.product.name: Google Compute Engine dmi.sys.vendor: Google -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1742250 Title: Adding and deleting a veth leaks a systemd unit Status in sys
[Touch-packages] [Bug 1742250] Re: Adding and deleting a veth leaks a systemd unit
I tried this on Ubuntu 16.04, started on GCE and it didn't seem to repro there. When I add a veth, systemd units are added but they all seem to be cleaned up when the veth is removed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1742250 Title: Adding and deleting a veth leaks a systemd unit Status in systemd package in Ubuntu: New Bug description: When I add a veth device: sudo ip link add name test1 type veth I see these systemd units appear: systemctl list-units --all | grep test sys-devices-virtual-net-test1.device loadedactive plugged /sys/devices/virtual/net/test1 sys-subsystem-net-devices-test1.device loadedactive plugged /sys/subsystem/net/devices/test1 However, if I then delete the veth: sudo ip link del dev test1 Then only one of the units is removed: systemctl list-units --all | grep test sys-devices-virtual-net-test1.device loadedactive plugged /sys/devices/virtual/net/test1 This is a big problem when running, for example, a Kubernetes cluster since each pod creation/deletion leaks a systemd unit. When enough have been leaked, systemd becomes unresponsive and the system is broken until reboot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 Date: Tue Jan 9 18:57:34 2018 Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Google Google Compute Engine ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=c66b8cf4-2a6c-4fb3-9f39-59483a6a025c ro scsi_mod.use_blk_mq=Y console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Google dmi.bios.version: Google dmi.board.asset.tag: 1AF4A7E8-D62B-D331-0693-3511A041DD96 dmi.board.name: Google Compute Engine dmi.board.vendor: Google dmi.chassis.type: 1 dmi.chassis.vendor: Google dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: dmi.product.name: Google Compute Engine dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1742250/+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 1899766] [NEW] Xorg freeze after selecting large cursor
Public bug reported: After selecting the largest cursor in accessibility settings, the whole system froze. I had to use Magic SysRq to reboot the system. After reboot, the login screen was OK but after logging in it would immediately freeze again. Workaround: from login screen, switch to a VT with Ctrl-F2, log in and run dconf reset /org/gnome/desktop/interface/cursor-size I was playing with the cursor size because I see different cursor sizes in different apps and it was annoying me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 11:25:23 2020 DistUpgraded: 2020-05-02 16:08:06,720 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d] Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d] InstallationDate: Installed on 2018-12-11 (672 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-02 (164 days ago) dmi.bios.date: 07/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.1:bd07/09/2020:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1899766 Title: Xorg freeze after selecting large cursor Status in xorg package in Ubuntu: New Bug description: After selecting the largest cursor in accessibility settings, the whole system froze. I had to use Magic SysRq to reboot the system. After reboot, the login screen was OK but after logging in it would immediately freeze again. Workaround: from login screen, switch to a VT with Ctrl-F2, log in and run dconf reset /org/gnome/desktop/interface/cursor-size I was playing with the cursor size because I see different cursor sizes in different apps and it was annoying me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (
[Touch-packages] [Bug 1896229] [NEW] systemd-networkd thinks it loses its lease every renewal
Public bug reported: With a server running 20.04 on AWS, I noticed connectivity glitches once per half hour. Eventually managed to correlate it with DHCP renewals. Each time systemd-networkd does a renewal, it logs that the lease was lost and goes through a cycle of removing and re-adding the IP and routes (Even though it's the same IP and routes). This causes disruption, especially to SNATted flows; if a packet arrives for an SNATted flow during hte windows where the IP is removed then (I think) the host sends a RST and the flow gets torn down. (In any case, such flows get lost during the glitch.) I'd expect a DHCP renewal to be completely transparent; the IP shouldn't flap, it should just be updated to have a longer lifetime. I managed to capture a PCAP of the DHCP renewals along with a debug log from systemd-networkd. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.11 ProcVersionSignature: User Name 5.3.0-1030.32-aws 5.3.18 Uname: Linux 5.3.0-1030-aws x86_64 ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 Date: Fri Sep 18 13:05:22 2020 Ec2AMI: ami-0d3d788094d3f0aa9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: t3.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Amazon EC2 t3.large ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-1030-aws root=PARTUUID=e96a8035-01 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2017 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-0fc0b0107c428fe19 dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnt3.large:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: dmi.product.name: t3.large dmi.sys.vendor: Amazon EC2 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1896229 Title: systemd-networkd thinks it loses its lease every renewal Status in systemd package in Ubuntu: New Bug description: With a server running 20.04 on AWS, I noticed connectivity glitches once per half hour. Eventually managed to correlate it with DHCP renewals. Each time systemd-networkd does a renewal, it logs that the lease was lost and goes through a cycle of removing and re-adding the IP and routes (Even though it's the same IP and routes). This causes disruption, especially to SNATted flows; if a packet arrives for an SNATted flow during hte windows where the IP is removed then (I think) the host sends a RST and the flow gets torn down. (In any case, such flows get lost during the glitch.) I'd expect a DHCP renewal to be completely transparent; the IP shouldn't flap, it should just be updated to have a longer lifetime. I managed to capture a PCAP of the DHCP renewals along with a debug log from systemd-networkd. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.11 ProcVersionSignature: User Name 5.3.0-1030.32-aws 5.3.18 Uname: Linux 5.3.0-1030-aws x86_64 ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 Date: Fri Sep 18 13:05:22 2020 Ec2AMI: ami-0d3d788094d3f0aa9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: t3.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Amazon EC2 t3.large ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-1030-aws root=PARTUUID=e96a8035-01 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2017 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-0fc0b0107c428fe19 dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnt3.large:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: dmi.product.name: t3.large dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896229/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1896229] Re: systemd-networkd thinks it loses its lease every renewal
Hmm, looks like this server is on 19.10, not 20.04 as I'd thought. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1896229 Title: systemd-networkd thinks it loses its lease every renewal Status in systemd package in Ubuntu: New Bug description: With a server running 20.04 on AWS, I noticed connectivity glitches once per half hour. Eventually managed to correlate it with DHCP renewals. Each time systemd-networkd does a renewal, it logs that the lease was lost and goes through a cycle of removing and re-adding the IP and routes (Even though it's the same IP and routes). This causes disruption, especially to SNATted flows; if a packet arrives for an SNATted flow during hte windows where the IP is removed then (I think) the host sends a RST and the flow gets torn down. (In any case, such flows get lost during the glitch.) I'd expect a DHCP renewal to be completely transparent; the IP shouldn't flap, it should just be updated to have a longer lifetime. I managed to capture a PCAP of the DHCP renewals along with a debug log from systemd-networkd. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.11 ProcVersionSignature: User Name 5.3.0-1030.32-aws 5.3.18 Uname: Linux 5.3.0-1030-aws x86_64 ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 Date: Fri Sep 18 13:05:22 2020 Ec2AMI: ami-0d3d788094d3f0aa9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: t3.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Amazon EC2 t3.large ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-1030-aws root=PARTUUID=e96a8035-01 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2017 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-0fc0b0107c428fe19 dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnt3.large:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: dmi.product.name: t3.large dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896229/+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 1896229] Re: systemd-networkd thinks it loses its lease every renewal
** Attachment added: "PCAP of DHCP traffic" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896229/+attachment/5412183/+files/dhcp.pcap -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1896229 Title: systemd-networkd thinks it loses its lease every renewal Status in systemd package in Ubuntu: New Bug description: With a server running 20.04 on AWS, I noticed connectivity glitches once per half hour. Eventually managed to correlate it with DHCP renewals. Each time systemd-networkd does a renewal, it logs that the lease was lost and goes through a cycle of removing and re-adding the IP and routes (Even though it's the same IP and routes). This causes disruption, especially to SNATted flows; if a packet arrives for an SNATted flow during hte windows where the IP is removed then (I think) the host sends a RST and the flow gets torn down. (In any case, such flows get lost during the glitch.) I'd expect a DHCP renewal to be completely transparent; the IP shouldn't flap, it should just be updated to have a longer lifetime. I managed to capture a PCAP of the DHCP renewals along with a debug log from systemd-networkd. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.11 ProcVersionSignature: User Name 5.3.0-1030.32-aws 5.3.18 Uname: Linux 5.3.0-1030-aws x86_64 ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 Date: Fri Sep 18 13:05:22 2020 Ec2AMI: ami-0d3d788094d3f0aa9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: t3.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Amazon EC2 t3.large ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-1030-aws root=PARTUUID=e96a8035-01 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2017 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-0fc0b0107c428fe19 dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnt3.large:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: dmi.product.name: t3.large dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896229/+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 1896229] Re: systemd-networkd thinks it loses its lease every renewal
Looks like the restart to enable debug triggered a DHCPDISCOVER, that's the easiest point to use to synchronise the PCAP and the log. Note logs of successful DHCP ACK messages followed by "Lease lost!". ** Attachment added: "systemd-networkd logs" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896229/+attachment/5412184/+files/systemd-networkd.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1896229 Title: systemd-networkd thinks it loses its lease every renewal Status in systemd package in Ubuntu: New Bug description: With a server running 20.04 on AWS, I noticed connectivity glitches once per half hour. Eventually managed to correlate it with DHCP renewals. Each time systemd-networkd does a renewal, it logs that the lease was lost and goes through a cycle of removing and re-adding the IP and routes (Even though it's the same IP and routes). This causes disruption, especially to SNATted flows; if a packet arrives for an SNATted flow during hte windows where the IP is removed then (I think) the host sends a RST and the flow gets torn down. (In any case, such flows get lost during the glitch.) I'd expect a DHCP renewal to be completely transparent; the IP shouldn't flap, it should just be updated to have a longer lifetime. I managed to capture a PCAP of the DHCP renewals along with a debug log from systemd-networkd. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.11 ProcVersionSignature: User Name 5.3.0-1030.32-aws 5.3.18 Uname: Linux 5.3.0-1030-aws x86_64 ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 Date: Fri Sep 18 13:05:22 2020 Ec2AMI: ami-0d3d788094d3f0aa9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: t3.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Amazon EC2 t3.large ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-1030-aws root=PARTUUID=e96a8035-01 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2017 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-0fc0b0107c428fe19 dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnt3.large:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: dmi.product.name: t3.large dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896229/+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 1896229] Re: systemd-networkd thinks it loses its lease every renewal
Doesn't seem to repro on 20.04 with systemd 245.4-4ubuntu3.2 ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1896229 Title: systemd-networkd thinks it loses its lease every renewal Status in systemd package in Ubuntu: Invalid Bug description: With a server running 20.04 on AWS, I noticed connectivity glitches once per half hour. Eventually managed to correlate it with DHCP renewals. Each time systemd-networkd does a renewal, it logs that the lease was lost and goes through a cycle of removing and re-adding the IP and routes (Even though it's the same IP and routes). This causes disruption, especially to SNATted flows; if a packet arrives for an SNATted flow during hte windows where the IP is removed then (I think) the host sends a RST and the flow gets torn down. (In any case, such flows get lost during the glitch.) I'd expect a DHCP renewal to be completely transparent; the IP shouldn't flap, it should just be updated to have a longer lifetime. I managed to capture a PCAP of the DHCP renewals along with a debug log from systemd-networkd. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.11 ProcVersionSignature: User Name 5.3.0-1030.32-aws 5.3.18 Uname: Linux 5.3.0-1030-aws x86_64 ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 Date: Fri Sep 18 13:05:22 2020 Ec2AMI: ami-0d3d788094d3f0aa9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: t3.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Amazon EC2 t3.large ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-1030-aws root=PARTUUID=e96a8035-01 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2017 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-0fc0b0107c428fe19 dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnt3.large:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: dmi.product.name: t3.large dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896229/+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 1662355] [NEW] Signon shows up as Safari
Public bug reported: Signon UI popped up and asked me to log into Google. After logging in, Google immediately sent me a message asking whether I logged in as Safari, with my public IP (so I have no reason to think it was anyone but me). Is signon-ui spoofing as safari? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: signon-ui 0.17+16.04.20160406-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 6 22:41:44 2017 InstallationDate: Installed on 2012-09-26 (1594 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) PackageArchitecture: all SourcePackage: signon-ui UpgradeStatus: Upgraded to yakkety on 2017-01-23 (13 days ago) ** Affects: signon-ui (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1662355 Title: Signon shows up as Safari Status in signon-ui package in Ubuntu: New Bug description: Signon UI popped up and asked me to log into Google. After logging in, Google immediately sent me a message asking whether I logged in as Safari, with my public IP (so I have no reason to think it was anyone but me). Is signon-ui spoofing as safari? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: signon-ui 0.17+16.04.20160406-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 6 22:41:44 2017 InstallationDate: Installed on 2012-09-26 (1594 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) PackageArchitecture: all SourcePackage: signon-ui UpgradeStatus: Upgraded to yakkety on 2017-01-23 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1662355/+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 1368864] Re: old motd is displayed on login
Although /run/motd.dynamic is being updated, it's being updated after being displayed, which is why you see the old one from the previous login. After commenting out the second line with no arguments: sessionoptional pam_motd.so # [1] /run/motd.dynamic was no longer being updated on login so I knew this was the line triggering the udpate. After moving the noupdate to this line I was seeing the freshly generated motd.dynamic on login. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1368864 Title: old motd is displayed on login Status in shadow package in Ubuntu: Triaged Bug description: On Trusty, during login, the motd displayed is from the cache file /run/motd.dynamic. After being displayed, the scripts from /etc /update-motd.d are run to refresh /run/motd.dynamic. This behavior of displaying the cache first is not very convenient and didn't happen on Precise. This is also does not match the documentation (man 5 update- motd) nor the users' expectations. Steps to reproduce: $ cat << "EOF" | sudo tee /etc/update-motd.d/60-test #!/bin/sh printf "motd from: $(date +%T)\n" EOF $ sudo chmod +x /etc/update-motd.d/60-test $ echo 'echo "real time: $(date +%T)";exit' | ssh -T localhost Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-35-generic x86_64) * Documentation: https://help.ubuntu.com/ motd from: 6:05:43 real time: 12:36:14 The above is just an example of how old/stale the output can be. More details: $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy libpam-modules libpam-modules: Installed: 1.1.8-1ubuntu2 Candidate: 1.1.8-1ubuntu2 Version table: *** 1.1.8-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libpam-modules 1.1.8-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 12 12:22:09 2014 InstallationDate: Installed on 2014-01-26 (228 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124) SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1368864/+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 1501061] [NEW] nvidia driver
Public bug reported: still tears the screen when the computer has been on for a couple of hours, the pc cooling is fine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 346.96 Sun Aug 23 21:32:53 PDT 2015 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04) ApportVersion: 2.14.1-0ubuntu3.15 Architecture: i386 Date: Tue Sep 29 21:46:54 2015 DistUpgraded: 2015-09-19 23:28:07,799 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-63-generic, i686: installed bbswitch, 0.7, 3.13.0-65-generic, i686: installed bbswitch, 0.7, 3.2.0-90-generic-pae, i686: installed nvidia-346, 346.96, 3.13.0-63-generic, i686: installed nvidia-346, 346.96, 3.13.0-65-generic, i686: installed GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8429] InstallationDate: Installed on 2015-09-19 (10 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1) MachineType: FOXCONN RS880M06-8KRS3HX ProcEnviron: LANGUAGE=en_GB PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic root=UUID=8d17b1db-12bf-41c7-b494-cdd864d3d816 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2015-09-19 (9 days ago) dmi.bios.date: 05/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.name: A88GMX dmi.board.vendor: FOXCONN dmi.board.version: FAB 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: FOXCONN dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/20/2010:svnFOXCONN:pnRS880M06-8KRS3HX:pvrFAB1.0:rvnFOXCONN:rnA88GMX:rvrFAB1.0:cvnFOXCONN:ct3:cvr: dmi.product.name: RS880M06-8KRS3HX dmi.product.version: FAB 1.0 dmi.sys.vendor: FOXCONN version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Sep 29 21:13:07 2015 xserver.configfile: /etc/X11/xorg.conf xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDaKai 2.4G RXKEYBOARD, id 8 inputDaKai 2.4G RXKEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1501061 Title: nvidia driver Status in xorg package in Ubuntu: New Bug description: still tears the screen when the computer has been on for a couple of hours, the pc cooling is fine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 346.96 Sun Aug 23 21:32:53 PDT 2015 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04) ApportVersion: 2.14.1-0ubuntu3.15 Architecture: i386 Date: Tue Sep 29 21:46:54 2015 DistUpgraded: 2015-09-19 23:28:07,799 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-63-generic, i686: installed bbswitch, 0.7, 3.13.0-65-generic, i686: installed bbswitch, 0.7, 3.2.0-90-generic-pae, i686: installed nvidia-346, 346.96, 3.13.0-63-generic, i686: installed nvidia-346, 346.96, 3.13.0-65-generic, i686: installed GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8429] InstallationDate: Installed on 2015-09-19 (10 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1) Machin
[Touch-packages] [Bug 1869814] Re: ubuntu-docs build failure - possible solution
So in general, syntax errors in translations just cause a warning, and
the original text is used. itstool only errors on syntax if you pass
--strict, and yelp.m4 doesn't even give you a way to pass --strict.
There's a chance this is itstool's fault. You do still have to do memory
management with libxml2's Python bindings, so stuff like double frees in
application code is possible. But since this crash happens during error
reporting for a language with many-byte UTF-8 chars, and since it
weirdly only happens with Python 3, I suspect it's this libxml2 bug:
https://bugzilla.gnome.org/show_bug.cgi?id=789714
** Bug watch added: bugzilla.gnome.org/ #789714
https://bugzilla.gnome.org/show_bug.cgi?id=789714
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible solution
Status in itstool package in Ubuntu:
Invalid
Status in libxml2 package in Ubuntu:
New
Status in ubuntu-docs package in Ubuntu:
Fix Committed
Bug description:
ubuntu-docs failed to build during the second Focal Fossa test
rebuild:
https://launchpad.net/ubuntu/+archive/test-
rebuild-20200327-focal/+build/18982738
It was itstool which failed to generate the localized zh_CN pages. If
dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
excluding the Chinese pages is apparently not an acceptable solution.
The itstool package in focal {build-,}depends on python3. I built
itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
built fine without modifications:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages
So the root cause seems to lie neither in ubuntu-docs nor itstool. I
would suspect that python3-libxml2 is buggy, but since itstool was
built against python2 in eoan, it's hard to tell if it's a regression.
Would building itstool against python2 be an acceptable workaround in
focal?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1378487] [NEW] x server keeps crashing
Public bug reported: While I am using Ubuntu the x-server keeps freezing on me. I still can hear sounds coming from open applications and when I click blindly around, I get responses; but from my perspective everything is frozen in place. I am able to work around this by pressing ctrl-alt-f2 whenever it happens, but it occurs so frequently that it inhibits any work or play that I try to do on the system. Hopefully there is a fix to this problem. Thank you. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Oct 7 10:51:39 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-36-generic, x86_64: installed bbswitch, 0.7, 3.13.0-37-generic, x86_64: installed nvidia-331-updates, 331.38, 3.13.0-36-generic, x86_64: installed nvidia-331-updates, 331.38, 3.13.0-37-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:12dd] Subsystem: ASUSTeK Computer Inc. Device [1043:12dd] InstallationDate: Installed on 2014-10-07 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK COMPUTER INC. Q550LF ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=b0420dd4-a9d7-466c-b887-6f201000282e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q550LF.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Q550LF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ550LF.214:bd05/07/2014:svnASUSTeKCOMPUTERINC.:pnQ550LF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ550LF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: Q550LF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Oct 7 09:14:17 2014 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1068 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1378487 Title: x server keeps crashing Status in “xorg” package in Ubuntu: New Bug description: While I am using Ubuntu the x-server keeps freezing on me. I still can hear sounds coming from open applications and when I click blindly around, I get responses; but from my perspective everything is frozen in place. I am able to work around this by pressing ctrl-alt-f2 whenever it happens, but it occurs so frequently that it inhibits any work or play that I try to do on the system. Hopefully there is a fix to this problem. Thank you. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
[Touch-packages] [Bug 1332904] Re: Network manager stopped scanning for wifi networks
I have the same symptom (wifi ends up disconnected after resume, cured by running a scan manually) but I'm seeing this after upgrading to 16.04. One oddity is that network-manager often shows that it thinks it is connected to an AP after resume but it's not the correct one. It seems to think it is connected to my neighbour's AP, for example. I wondered if the APs had swapped channels due to autodetection or something. -- 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/1332904 Title: Network manager stopped scanning for wifi networks Status in network-manager package in Ubuntu: Confirmed Bug description: After I resumed my laptop from suspend, it would not connect to wifi. For a while, it seemed confused about its connection state, then it displayed "disconnected", and showed that there were no wifi networks available (which is not true). To debug the problem, I ran "nmcli d wifi list", which showed no results. Then I ran "iwlist scan", which also showed no results. Then I tried "sudo iwlist scan" - which showed all the wifi networks, and actually caused the network manager to start working again. It connected to a network successfully, and so on. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: KDE Date: Sat Jun 21 22:12:35 2014 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-05 (443 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.34 metric 9 SourcePackage: network-manager UpgradeStatus: Upgraded to trusty on 2014-05-14 (39 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1332904/+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 1643163] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1643163/+attachment/4779936/+files/CRDA.txt -- 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/1643163 Title: Wifi doesn't work after resume, fixed by forcing scan Status in network-manager package in Ubuntu: New Bug description: Often after resuming from suspend, my laptop (Samsung series 9) is disconnected from the wifi and it doesn't seem to reconnect. Network manager seems confused; it displays that it is connected, but it shows the wrong access point (i.e. one of my neighbour's access points that I don't even have the password for). Running iwlist scan manually fixes the problem almost immediately and network-manager starts showing the correct state (connecting, then connected to the right AP). Very similar to bug 1332904 but apport recommended filing diags on a fresh bug report. Wifi card appears to be "Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)" according to lspci. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) IpRoute: default via 192.168.1.254 dev wlan0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.241 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 1.2.2-0ubuntu0.16.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Tags: xenial Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.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/1643163/+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 1643163] [NEW] Wifi doesn't work after resume, fixed by forcing scan
Public bug reported: Often after resuming from suspend, my laptop (Samsung series 9) is disconnected from the wifi and it doesn't seem to reconnect. Network manager seems confused; it displays that it is connected, but it shows the wrong access point (i.e. one of my neighbour's access points that I don't even have the password for). Running iwlist scan manually fixes the problem almost immediately and network-manager starts showing the correct state (connecting, then connected to the right AP). Very similar to bug 1332904 but apport recommended filing diags on a fresh bug report. Wifi card appears to be "Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)" according to lspci. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) IpRoute: default via 192.168.1.254 dev wlan0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.241 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 1.2.2-0ubuntu0.16.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Tags: xenial Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected xenial ** Package changed: wpasupplicant (Ubuntu) => network-manager (Ubuntu) ** Tags added: apport-collected xenial ** Description changed: Often after resuming from suspend, my laptop (Samsung series 9) is disconnected from the wifi and it doesn't seem to reconnect. Network manager seems confused; it displays that it is connected, but it shows the wrong access point (i.e. one of my neighbour's access points that I don't even have the password for). Running iwlist scan manually fixes the problem almost immediately and network-manager starts showing the correct state (connecting, then connected to the right AP). Very similar to bug 1332904 but apport recommended filing diags on a fresh bug report. - Wifi card appears to be "Network controller: Intel Corporation Centrino - Advanced-N 6235 (rev 24)" according to lspci. + Wifi card appears to be "Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)" according to lspci. + --- + ApportVersion: 2.20.1-0ubuntu2.1 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + IfupdownConfig: + auto lo + iface lo inet loopback + InstallationDate: Installed on 2012-09-26 (1515 days ago) + InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) + IpRoute: + default via 192.168.1.254 dev wlan0 proto static metric 600 + 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown + 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown + 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.241 metric 600 + NetworkManager.state: + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + WimaxEnabled=true + Package: network-manager 1.2.2-0ubuntu0.16.04.3 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 + Tags: xenial + Uname: Linux 4.4.0-45-generic x86_64 + UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) + UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo wireshark + _MarkForUpload: True + nmcli-nm: + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.2.2connected started full enabled enabled enabled enabled enabled -- 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/1643163 Title: Wifi doesn't work after resume, fixed by forcing scan Status in network-manager package in Ubuntu: New Bug description: Often after resuming from suspend, my laptop (Samsung series 9) is disconnected from the wifi and it doesn't seem to reconnect. Network manager seems confused; it displays that it is connected, but it shows the wrong access point (i.e. one of my neighbour's acc
[Touch-packages] [Bug 1643163] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1643163/+attachment/4779937/+files/Dependencies.txt -- 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/1643163 Title: Wifi doesn't work after resume, fixed by forcing scan Status in network-manager package in Ubuntu: New Bug description: Often after resuming from suspend, my laptop (Samsung series 9) is disconnected from the wifi and it doesn't seem to reconnect. Network manager seems confused; it displays that it is connected, but it shows the wrong access point (i.e. one of my neighbour's access points that I don't even have the password for). Running iwlist scan manually fixes the problem almost immediately and network-manager starts showing the correct state (connecting, then connected to the right AP). Very similar to bug 1332904 but apport recommended filing diags on a fresh bug report. Wifi card appears to be "Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)" according to lspci. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) IpRoute: default via 192.168.1.254 dev wlan0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.241 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 1.2.2-0ubuntu0.16.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Tags: xenial Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.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/1643163/+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 1643163] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.launchpad.net/bugs/1643163/+attachment/4779943/+files/NetDevice.lo.txt -- 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/1643163 Title: Wifi doesn't work after resume, fixed by forcing scan Status in network-manager package in Ubuntu: New Bug description: Often after resuming from suspend, my laptop (Samsung series 9) is disconnected from the wifi and it doesn't seem to reconnect. Network manager seems confused; it displays that it is connected, but it shows the wrong access point (i.e. one of my neighbour's access points that I don't even have the password for). Running iwlist scan manually fixes the problem almost immediately and network-manager starts showing the correct state (connecting, then connected to the right AP). Very similar to bug 1332904 but apport recommended filing diags on a fresh bug report. Wifi card appears to be "Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)" according to lspci. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) IpRoute: default via 192.168.1.254 dev wlan0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.241 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 1.2.2-0ubuntu0.16.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Tags: xenial Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.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/1643163/+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 1643163] NetDevice.wlan0.txt
apport information ** Attachment added: "NetDevice.wlan0.txt" https://bugs.launchpad.net/bugs/1643163/+attachment/4779944/+files/NetDevice.wlan0.txt -- 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/1643163 Title: Wifi doesn't work after resume, fixed by forcing scan Status in network-manager package in Ubuntu: New Bug description: Often after resuming from suspend, my laptop (Samsung series 9) is disconnected from the wifi and it doesn't seem to reconnect. Network manager seems confused; it displays that it is connected, but it shows the wrong access point (i.e. one of my neighbour's access points that I don't even have the password for). Running iwlist scan manually fixes the problem almost immediately and network-manager starts showing the correct state (connecting, then connected to the right AP). Very similar to bug 1332904 but apport recommended filing diags on a fresh bug report. Wifi card appears to be "Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)" according to lspci. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) IpRoute: default via 192.168.1.254 dev wlan0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.241 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 1.2.2-0ubuntu0.16.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Tags: xenial Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.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/1643163/+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 1643163] NetDevice.eth0.txt
apport information ** Attachment added: "NetDevice.eth0.txt" https://bugs.launchpad.net/bugs/1643163/+attachment/4779942/+files/NetDevice.eth0.txt -- 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/1643163 Title: Wifi doesn't work after resume, fixed by forcing scan Status in network-manager package in Ubuntu: New Bug description: Often after resuming from suspend, my laptop (Samsung series 9) is disconnected from the wifi and it doesn't seem to reconnect. Network manager seems confused; it displays that it is connected, but it shows the wrong access point (i.e. one of my neighbour's access points that I don't even have the password for). Running iwlist scan manually fixes the problem almost immediately and network-manager starts showing the correct state (connecting, then connected to the right AP). Very similar to bug 1332904 but apport recommended filing diags on a fresh bug report. Wifi card appears to be "Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)" according to lspci. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) IpRoute: default via 192.168.1.254 dev wlan0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.241 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 1.2.2-0ubuntu0.16.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Tags: xenial Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.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/1643163/+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 1643163] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1643163/+attachment/4779948/+files/RfKill.txt -- 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/1643163 Title: Wifi doesn't work after resume, fixed by forcing scan Status in network-manager package in Ubuntu: New Bug description: Often after resuming from suspend, my laptop (Samsung series 9) is disconnected from the wifi and it doesn't seem to reconnect. Network manager seems confused; it displays that it is connected, but it shows the wrong access point (i.e. one of my neighbour's access points that I don't even have the password for). Running iwlist scan manually fixes the problem almost immediately and network-manager starts showing the correct state (connecting, then connected to the right AP). Very similar to bug 1332904 but apport recommended filing diags on a fresh bug report. Wifi card appears to be "Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)" according to lspci. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) IpRoute: default via 192.168.1.254 dev wlan0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.241 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 1.2.2-0ubuntu0.16.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Tags: xenial Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.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/1643163/+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 1643163] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1643163/+attachment/4779946/+files/PciNetwork.txt -- 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/1643163 Title: Wifi doesn't work after resume, fixed by forcing scan Status in network-manager package in Ubuntu: New Bug description: Often after resuming from suspend, my laptop (Samsung series 9) is disconnected from the wifi and it doesn't seem to reconnect. Network manager seems confused; it displays that it is connected, but it shows the wrong access point (i.e. one of my neighbour's access points that I don't even have the password for). Running iwlist scan manually fixes the problem almost immediately and network-manager starts showing the correct state (connecting, then connected to the right AP). Very similar to bug 1332904 but apport recommended filing diags on a fresh bug report. Wifi card appears to be "Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)" according to lspci. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) IpRoute: default via 192.168.1.254 dev wlan0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.241 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 1.2.2-0ubuntu0.16.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Tags: xenial Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.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/1643163/+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 1643163] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1643163/+attachment/4779947/+files/ProcEnviron.txt -- 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/1643163 Title: Wifi doesn't work after resume, fixed by forcing scan Status in network-manager package in Ubuntu: New Bug description: Often after resuming from suspend, my laptop (Samsung series 9) is disconnected from the wifi and it doesn't seem to reconnect. Network manager seems confused; it displays that it is connected, but it shows the wrong access point (i.e. one of my neighbour's access points that I don't even have the password for). Running iwlist scan manually fixes the problem almost immediately and network-manager starts showing the correct state (connecting, then connected to the right AP). Very similar to bug 1332904 but apport recommended filing diags on a fresh bug report. Wifi card appears to be "Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)" according to lspci. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) IpRoute: default via 192.168.1.254 dev wlan0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.241 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 1.2.2-0ubuntu0.16.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Tags: xenial Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.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/1643163/+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 1643163] NetworkManager.conf.txt
apport information ** Attachment added: "NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1643163/+attachment/4779945/+files/NetworkManager.conf.txt -- 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/1643163 Title: Wifi doesn't work after resume, fixed by forcing scan Status in network-manager package in Ubuntu: New Bug description: Often after resuming from suspend, my laptop (Samsung series 9) is disconnected from the wifi and it doesn't seem to reconnect. Network manager seems confused; it displays that it is connected, but it shows the wrong access point (i.e. one of my neighbour's access points that I don't even have the password for). Running iwlist scan manually fixes the problem almost immediately and network-manager starts showing the correct state (connecting, then connected to the right AP). Very similar to bug 1332904 but apport recommended filing diags on a fresh bug report. Wifi card appears to be "Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)" according to lspci. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) IpRoute: default via 192.168.1.254 dev wlan0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.241 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 1.2.2-0ubuntu0.16.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Tags: xenial Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.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/1643163/+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 1643163] nmcli-con.txt
apport information ** Attachment added: "nmcli-con.txt" https://bugs.launchpad.net/bugs/1643163/+attachment/4779950/+files/nmcli-con.txt -- 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/1643163 Title: Wifi doesn't work after resume, fixed by forcing scan Status in network-manager package in Ubuntu: New Bug description: Often after resuming from suspend, my laptop (Samsung series 9) is disconnected from the wifi and it doesn't seem to reconnect. Network manager seems confused; it displays that it is connected, but it shows the wrong access point (i.e. one of my neighbour's access points that I don't even have the password for). Running iwlist scan manually fixes the problem almost immediately and network-manager starts showing the correct state (connecting, then connected to the right AP). Very similar to bug 1332904 but apport recommended filing diags on a fresh bug report. Wifi card appears to be "Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)" according to lspci. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) IpRoute: default via 192.168.1.254 dev wlan0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.241 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 1.2.2-0ubuntu0.16.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Tags: xenial Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.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/1643163/+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 1643163] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1643163/+attachment/4779949/+files/WifiSyslog.txt -- 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/1643163 Title: Wifi doesn't work after resume, fixed by forcing scan Status in network-manager package in Ubuntu: New Bug description: Often after resuming from suspend, my laptop (Samsung series 9) is disconnected from the wifi and it doesn't seem to reconnect. Network manager seems confused; it displays that it is connected, but it shows the wrong access point (i.e. one of my neighbour's access points that I don't even have the password for). Running iwlist scan manually fixes the problem almost immediately and network-manager starts showing the correct state (connecting, then connected to the right AP). Very similar to bug 1332904 but apport recommended filing diags on a fresh bug report. Wifi card appears to be "Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)" according to lspci. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) IpRoute: default via 192.168.1.254 dev wlan0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.241 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 1.2.2-0ubuntu0.16.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Tags: xenial Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.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/1643163/+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 1643163] NetDevice.docker0.txt
apport information ** Attachment added: "NetDevice.docker0.txt" https://bugs.launchpad.net/bugs/1643163/+attachment/4779941/+files/NetDevice.docker0.txt -- 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/1643163 Title: Wifi doesn't work after resume, fixed by forcing scan Status in network-manager package in Ubuntu: New Bug description: Often after resuming from suspend, my laptop (Samsung series 9) is disconnected from the wifi and it doesn't seem to reconnect. Network manager seems confused; it displays that it is connected, but it shows the wrong access point (i.e. one of my neighbour's access points that I don't even have the password for). Running iwlist scan manually fixes the problem almost immediately and network-manager starts showing the correct state (connecting, then connected to the right AP). Very similar to bug 1332904 but apport recommended filing diags on a fresh bug report. Wifi card appears to be "Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)" according to lspci. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) IpRoute: default via 192.168.1.254 dev wlan0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.241 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 1.2.2-0ubuntu0.16.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Tags: xenial Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.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/1643163/+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 1643163] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1643163/+attachment/4779940/+files/JournalErrors.txt -- 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/1643163 Title: Wifi doesn't work after resume, fixed by forcing scan Status in network-manager package in Ubuntu: New Bug description: Often after resuming from suspend, my laptop (Samsung series 9) is disconnected from the wifi and it doesn't seem to reconnect. Network manager seems confused; it displays that it is connected, but it shows the wrong access point (i.e. one of my neighbour's access points that I don't even have the password for). Running iwlist scan manually fixes the problem almost immediately and network-manager starts showing the correct state (connecting, then connected to the right AP). Very similar to bug 1332904 but apport recommended filing diags on a fresh bug report. Wifi card appears to be "Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)" according to lspci. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) IpRoute: default via 192.168.1.254 dev wlan0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.241 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 1.2.2-0ubuntu0.16.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Tags: xenial Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.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/1643163/+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 1643163] nmcli-dev.txt
apport information ** Attachment added: "nmcli-dev.txt" https://bugs.launchpad.net/bugs/1643163/+attachment/4779951/+files/nmcli-dev.txt -- 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/1643163 Title: Wifi doesn't work after resume, fixed by forcing scan Status in network-manager package in Ubuntu: New Bug description: Often after resuming from suspend, my laptop (Samsung series 9) is disconnected from the wifi and it doesn't seem to reconnect. Network manager seems confused; it displays that it is connected, but it shows the wrong access point (i.e. one of my neighbour's access points that I don't even have the password for). Running iwlist scan manually fixes the problem almost immediately and network-manager starts showing the correct state (connecting, then connected to the right AP). Very similar to bug 1332904 but apport recommended filing diags on a fresh bug report. Wifi card appears to be "Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)" according to lspci. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) IpRoute: default via 192.168.1.254 dev wlan0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.241 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 1.2.2-0ubuntu0.16.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Tags: xenial Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.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/1643163/+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 1643163] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1643163/+attachment/4779938/+files/IpAddr.txt -- 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/1643163 Title: Wifi doesn't work after resume, fixed by forcing scan Status in network-manager package in Ubuntu: New Bug description: Often after resuming from suspend, my laptop (Samsung series 9) is disconnected from the wifi and it doesn't seem to reconnect. Network manager seems confused; it displays that it is connected, but it shows the wrong access point (i.e. one of my neighbour's access points that I don't even have the password for). Running iwlist scan manually fixes the problem almost immediately and network-manager starts showing the correct state (connecting, then connected to the right AP). Very similar to bug 1332904 but apport recommended filing diags on a fresh bug report. Wifi card appears to be "Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)" according to lspci. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) IpRoute: default via 192.168.1.254 dev wlan0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.241 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 1.2.2-0ubuntu0.16.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Tags: xenial Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.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/1643163/+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 1643163] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1643163/+attachment/4779939/+files/IwConfig.txt -- 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/1643163 Title: Wifi doesn't work after resume, fixed by forcing scan Status in network-manager package in Ubuntu: New Bug description: Often after resuming from suspend, my laptop (Samsung series 9) is disconnected from the wifi and it doesn't seem to reconnect. Network manager seems confused; it displays that it is connected, but it shows the wrong access point (i.e. one of my neighbour's access points that I don't even have the password for). Running iwlist scan manually fixes the problem almost immediately and network-manager starts showing the correct state (connecting, then connected to the right AP). Very similar to bug 1332904 but apport recommended filing diags on a fresh bug report. Wifi card appears to be "Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)" according to lspci. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) IpRoute: default via 192.168.1.254 dev wlan0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.241 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 1.2.2-0ubuntu0.16.04.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Tags: xenial Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.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/1643163/+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
