[Touch-packages] [Bug 1872485] Re: virtualbox-guest-utils fails to install on 20.04
** Changed in: virtualbox (Debian) Status: New => Fix Released -- 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/1872485 Title: virtualbox-guest-utils fails to install on 20.04 Status in systemd package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in systemd package in Debian: Fix Released Status in virtualbox package in Debian: Fix Released Bug description: Attempting to install virtualbox-guest-utils 6.1.4-dfsg-2 on ubuntu:focal (20.04) produces a broken state. Debug of `apt-get install virtualbox-guest-utils` below. Steps to reproduce: 1. pull a fresh 20.04 image for testing (ex: lxc launch ubuntu-daily:20.04 test-container) 2. lxc exec test-container bash 3. apt update 4. apt full-upgrade 5. apt-get install virtualbox-guest-utils Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: glib-networking : Depends: gsettings-desktop-schemas but it is not going to be installed init : PreDepends: systemd-sysv but it is not going to be installed Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < none -> 6.1.4-dfsg-2 @un puN > Considering virtualbox-guest-utils:amd64 9998 as a solution to systemd-timesyncd:amd64 14 Removing systemd-timesyncd:amd64 rather than change virtualbox-guest-utils:amd64 Investigating (1) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mR > Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59 Added systemd-timesyncd:amd64 to the remove list Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H > Considering openntpd:amd64 0 as a solution to systemd:amd64 59 Added openntpd:amd64 to the remove list Fixing systemd:amd64 via keep of systemd-timesyncd:amd64 Fixing systemd:amd64 via keep of openntpd:amd64 Investigating (1) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < none -> 6.1.4-dfsg-2 @un puN > Considering virtualbox-guest-utils:amd64 9998 as a solution to systemd-timesyncd:amd64 14 Removing systemd-timesyncd:amd64 rather than change virtualbox-guest-utils:amd64 Investigating (2) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mR > Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59 Added systemd-timesyncd:amd64 to the remove list Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H > Considering openntpd:amd64 0 as a solution to systemd:amd64 59 Added openntpd:amd64 to the remove list Fixing systemd:amd64 via keep of systemd-timesyncd:amd64 Fixing systemd:amd64 via keep of openntpd:amd64 Investigating (2) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < none -> 6.1.4-dfsg-2 @un puN > Considering virtualbox-guest-utils:amd64 9998 as a solution to systemd-timesyncd:amd64 59 Removing systemd-timesyncd:amd64 rather than change virtualbox-guest-utils:amd64 Investigating (3) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mR > Considering systemd-timesyncd:amd64 9998 as a solution to systemd:amd64 59 Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H > Considering openntpd:amd64 59 as a solution to systemd:amd64 59 Or group remove for systemd:amd64 Investigating (3) libpam-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken libpam-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR > (= 245.4-2ubuntu1) Considering systemd:amd64 59 as a solution to libpam-systemd:amd64 23 Removing libpam-systemd:amd64 rather than change systemd:amd64 Investigating (3) libnss-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken libnss-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR > (= 245.4-2ubuntu1) Considering systemd:amd64 59 as a solution to libnss-systemd:amd64 14 Removing libnss-systemd:amd64 rather than change systemd:amd64 Investigating (3) plymouth:amd64 < 0.9.4git20200323-0ubuntu6 @ii mK Ib > Broken
[Touch-packages] [Bug 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid
Confirmed that the autopkgtests have passed with the new version in -proposed, for all series. Marking v-done so that this isn't listed as a candidate for removal from -proposed. ** Tags removed: verification-needed verification-needed-bionic verification-needed-eoan verification-needed-xenial ** Tags added: verification-done-bionic verification-done-eoan verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1859013 Title: openssh tests use "not valid yet" certificate from 2020, which is now valid Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Precise: New Status in openssh source package in Trusty: New Status in openssh source package in Xenial: Fix Committed Status in openssh source package in Bionic: Fix Committed Status in openssh source package in Disco: Won't Fix Status in openssh source package in Eoan: Fix Committed Status in openssh source package in Focal: Fix Released Bug description: [Impact] * regression testsuite uses 1st of January 2020 as the date in the future, however that is now in the past making autpkgtests fail. [Test Case] * Autopkgtest must pass [Regression Potential] * Testsuite assertion update only [Other Info] This is a staged update to be rolled up with any other openssh update in the future. fixed in debian https://tracker.debian.org/news/1092767/accepted- openssh-181p1-4-source-into-unstable/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1859013/+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 1867421] Re: Microsoft Classic IntelliMouse moves way too fast
Thanks, on Lubuntu 18.04.4 LTS, it's /lib/udev/hwdb.d/70-mouse.hwdb. I found the mouse far too slow after the update. Personally, I like to be able to quickly move the cursor from the left to right edge of my 1920 x 1080 screen in about an inch of physical movement. -- 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/1867421 Title: Microsoft Classic IntelliMouse moves way too fast Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] Microsoft Classic IntelliMouse moves way too fast to be usable. [test case] on a bionic system, connect affected mouse and attempt to move pointer, note it moves too fast. [regression potential] as this adds a hwdb entry for a mouse using vendor/product id and name matching, any regression would likely involve incorrectly setting dpi on a different mouse than intended. [scope] fixed by upstream commit 26d7cf3daf08b279bdd2e484936268e1e88648d4 which is included starting in v240, so this is already fixed in Eoan and later. This is needed only for Xenial and Bionic. [original description] Microsoft Classic IntelliMouse moves way too fast to be usable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.39 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 17:12:25 2020 InstallationDate: Installed on 2019-01-02 (436 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:0823 Microsoft Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 10M7CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=e226e89e-7b9d-4135-a662-4829015a56f0 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060531 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060531:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867421/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
+1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in PulseAudio: New Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1879054] Re: No sound after 20.04 update
Is the package timidity installed on your machine? If yes, please remove it. "sudo apt -r timidity;reboot" -- 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/1879054 Title: No sound after 20.04 update Status in pulseaudio package in Ubuntu: New Bug description: After update from 18.04 to 20.04 sound stopped working. KDE does not display Xonar sound card at all. $ aplay /usr/share/sounds/alsa/Front_Center.wav does not make any sound Alsamixer displays Xonar set at full volume but changing anything there does not seem to have any effect. Moving/deleting the pulse config ( ~/.config/pulse/ ) and restarting machine did not have any effect. Running: $ sudo alsa force-reload fixes the issue (until restart sound is back, and is displayed properly in KDE) (data arecord and cards display same data before and after restart) $ arecord -l Lista CAPTURE urządzeń karta 0: DX [Xonar DX], urządzenie 0: Multichannel [Multichannel] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0 karta 0: DX [Xonar DX], urządzenie 1: Digital [Digital] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0 $ cat /proc/asound/cards 0 [DX ]: AV200 - Xonar DX Asus Virtuoso 100 at 0xd000, irq 31 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xfe96 irq 67 $ lspci | grep -i audio 21:04.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio] 23:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] (build in motherboard soundcard is disabled in BIOS) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nait 5242 F pulseaudio /dev/snd/controlC1: nait 5242 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 16 14:54:07 2020 InstallationDate: Installed on 2018-11-11 (552 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-05-01 (14 days ago) dmi.bios.date: 09/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.J0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.J0:bd09/27/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879054/+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 1879114] [NEW] Sync dee 1.2.7+17.10.20170616-6 (main) from Debian unstable (main)
Public bug reported: Please sync dee 1.2.7+17.10.20170616-6 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * debian/control: Build-Depends on the versioned python binary * debian/patches/vapi-skip-properties.patch: - Disable properties that fail to build on newer versions of Vala and aren't required * Drop dependency on python and python3; package should not depend on python just because it provides python bindings. * debian/patches/build_no_werror.patch - Don't build with Werror, it makes the build fail on some glib deprecations (lp: #1843730) Both of the patch files were incorporated into Debian. They dropped Python 2 support, so the versioned build dependency is no longer relevant. They also dropped the hardcoded dependencies on python/python3 for gir1.2-dee-1.0. Changelog entries since current groovy version 1.2.7+17.10.20170616-4ubuntu6: dee (1.2.7+17.10.20170616-6) unstable; urgency=low * Bumped dh to 12. * Updated Standards-Version to 4.4.0 * Added patches from Ubuntu: + build_no_werror.patch: Don't build with Werror (Closes: #940163) + vapi-skip-properties.patch: Disable properties that fail to build on newer versions of Vala and aren't required. * Removed python2 support (Closes: #936379) * debian/rules: + Update for dh 12. * Updated examples. -- Kartik Mistry Mon, 30 Sep 2019 23:12:16 +0530 dee (1.2.7+17.10.20170616-5) unstable; urgency=low * Do not add unnecessary dependency on python. Thanks to Steve Langasek for patch. (Closes: #922632) * Added debian/gitlab-ci.yml for pipeline. -- Kartik Mistry Thu, 21 Feb 2019 10:35:44 +0530 ** Affects: dee (Ubuntu) Importance: Wishlist Status: New ** Changed in: dee (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dee in Ubuntu. https://bugs.launchpad.net/bugs/1879114 Title: Sync dee 1.2.7+17.10.20170616-6 (main) from Debian unstable (main) Status in dee package in Ubuntu: New Bug description: Please sync dee 1.2.7+17.10.20170616-6 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * debian/control: Build-Depends on the versioned python binary * debian/patches/vapi-skip-properties.patch: - Disable properties that fail to build on newer versions of Vala and aren't required * Drop dependency on python and python3; package should not depend on python just because it provides python bindings. * debian/patches/build_no_werror.patch - Don't build with Werror, it makes the build fail on some glib deprecations (lp: #1843730) Both of the patch files were incorporated into Debian. They dropped Python 2 support, so the versioned build dependency is no longer relevant. They also dropped the hardcoded dependencies on python/python3 for gir1.2-dee-1.0. Changelog entries since current groovy version 1.2.7+17.10.20170616-4ubuntu6: dee (1.2.7+17.10.20170616-6) unstable; urgency=low * Bumped dh to 12. * Updated Standards-Version to 4.4.0 * Added patches from Ubuntu: + build_no_werror.patch: Don't build with Werror (Closes: #940163) + vapi-skip-properties.patch: Disable properties that fail to build on newer versions of Vala and aren't required. * Removed python2 support (Closes: #936379) * debian/rules: + Update for dh 12. * Updated examples. -- Kartik Mistry Mon, 30 Sep 2019 23:12:16 +0530 dee (1.2.7+17.10.20170616-5) unstable; urgency=low * Do not add unnecessary dependency on python. Thanks to Steve Langasek for patch. (Closes: #922632) * Added debian/gitlab-ci.yml for pipeline. -- Kartik Mistry Thu, 21 Feb 2019 10:35:44 +0530 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dee/+bug/1879114/+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 1879113] [NEW] package python3-gi-cairo 3.26.1-2ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu
Public bug reported: Installing ra1nstorm virtual Mac ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3-gi-cairo 3.26.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun May 17 13:06:06 2020 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-05-16 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.3 SourcePackage: pygobject Title: package python3-gi-cairo 3.26.1-2ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pygobject (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1879113 Title: package python3-gi-cairo 3.26.1-2ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in pygobject package in Ubuntu: New Bug description: Installing ra1nstorm virtual Mac ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3-gi-cairo 3.26.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun May 17 13:06:06 2020 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-05-16 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.3 SourcePackage: pygobject Title: package python3-gi-cairo 3.26.1-2ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1879113/+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 1876147] Re: libtool-doc missing libtool.html
** Changed in: libtool (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtool in Ubuntu. https://bugs.launchpad.net/bugs/1876147 Title: libtool-doc missing libtool.html Status in libtool package in Ubuntu: New Status in libtool package in Debian: New Bug description: I am posting this as a bug to libtool but the package is libtool-doc When installing doc-base I I received this error/warning: Processing triggers for doc-base (0.10.9) ... Processing 2 added doc-base files... Error in `/usr/share/doc-base/libtool-doc', line 9: all `Format' sections are invalid. Note: `install-docs --verbose --check file_name' may give more details about the above error. Running: install-docs --verbose --check /usr/share/doc-base/libtool-doc I got: Warning in `/usr/share/doc-base/libtool-doc', line 9: file `/usr/share/doc/libtool-doc/libtool.html' does not exist. Error in `/usr/share/doc-base/libtool-doc', line 9: all `Format' sections are invalid. /usr/share/doc-base/libtool-doc: Fatal error found, the file won't be registered. A search for which package owns /usr/share/doc-base/libtool-doc apt-file search /usr/share/doc-base/libtool-doc libtool-doc: /usr/share/doc-base/libtool-doc Line 9 in /usr/share/doc-base/libtool-doc is; Index: /usr/share/doc/libtool-doc/libtool.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtool/+bug/1876147/+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 1879101] [NEW] Printing pdfs extremely slow
Public bug reported: HP Laserjet 3030 prints PDFs with photos extremely slowly (sometimes 10 min per page). Worked fine under Ubuntu 16.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat May 16 18:14:06 2020 InstallationDate: Installed on 2020-05-12 (4 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for hp_LaserJet_3030: hp:/usb/hp_LaserJet_3030?serial=00CNBM023795 device for hp_LaserJet_3030_fax: hpfax:/usb/hp_LaserJet_3030?serial=00CNBM023795 MachineType: MSI MS-7977 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/hp_LaserJet_3030.ppd', '/etc/cups/ppd/hp_LaserJet_3030_fax.ppd'] failed with exit code 2: grep: /etc/cups/ppd/hp_LaserJet_3030.ppd: Permission denied grep: /etc/cups/ppd/hp_LaserJet_3030_fax.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=a373b71f-c986-48fa-897f-bb1349f51f82 ro net.ifnames=0 biosdevname=0 quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.A0 dmi.board.asset.tag: Default string dmi.board.name: Z170A GAMING M5 (MS-7977) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.A0:bd07/22/2016:svnMSI:pnMS-7977:pvr1.0:rvnMSI:rnZ170AGAMINGM5(MS-7977):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7977 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug focal -- 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/1879101 Title: Printing pdfs extremely slow Status in cups package in Ubuntu: New Bug description: HP Laserjet 3030 prints PDFs with photos extremely slowly (sometimes 10 min per page). Worked fine under Ubuntu 16.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat May 16 18:14:06 2020 InstallationDate: Installed on 2020-05-12 (4 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for hp_LaserJet_3030: hp:/usb/hp_LaserJet_3030?serial=00CNBM023795 device for hp_LaserJet_3030_fax: hpfax:/usb/hp_LaserJet_3030?serial=00CNBM023795 MachineType: MSI MS-7977 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/hp_LaserJet_3030.ppd', '/etc/cups/ppd/hp_LaserJet_3030_fax.ppd'] failed with exit code 2: grep: /etc/cups/ppd/hp_LaserJet_3030.ppd: Permission denied grep: /etc/cups/ppd/hp_LaserJet_3030_fax.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=a373b71f-c986-48fa-897f-bb1349f51f82 ro net.ifnames=0 biosdevname=0 quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.A0 dmi.board.asset.tag: Default string dmi.board.name: Z170A GAMING M5 (MS-7977) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.A0:bd07/22/2016:svnMSI:pnMS-7977:pvr1.0:rvnMSI:rnZ170AGAMINGM5(MS-7977):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7977 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879101/+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 1878707] NetworkManager.conf.txt
apport information ** Attachment added: "NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372731/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] nmcli-dev.txt
apport information ** Attachment added: "nmcli-dev.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372738/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] NetDevice.wlp4s0.txt
apport information ** Attachment added: "NetDevice.wlp4s0.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372730/+files/NetDevice.wlp4s0.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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372735/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372733/+files/ProcCpuinfoMinimal.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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372734/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372732/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372736/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] nmcli-con.txt
apport information ** Attachment added: "nmcli-con.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372737/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] NetDevice.vpn0.txt
apport information ** Attachment added: "NetDevice.vpn0.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372729/+files/NetDevice.vpn0.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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] NetDevice.enp0s31f6.txt
apport information ** Attachment added: "NetDevice.enp0s31f6.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372727/+files/NetDevice.enp0s31f6.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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372725/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372728/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372724/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372726/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372723/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372712/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] modified.conffile..etc.NetworkManager.NetworkManager.conf.txt
apport information ** Attachment added: "modified.conffile..etc.NetworkManager.NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372713/+files/modified.conffile..etc.NetworkManager.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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] nmcli-dev.txt
apport information ** Attachment added: "nmcli-dev.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372715/+files/nmcli-dev.txt ** Description changed: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: KDE + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-05-13 (3 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + IpRoute: + default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 + default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 + 169.254.0.0/16 dev wlp4s0 scope link metric 1000 + 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 + 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 + Package: network-manager 1.22.10-1ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 + Tags: focal + Uname: Linux 5.4.0-29-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo + _MarkForUpload: True + modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] + mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 + nmcli-nm: + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.22.10 connected 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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug
[Touch-packages] [Bug 1878707] nmcli-con.txt
apport information ** Attachment added: "nmcli-con.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372714/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372711/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372709/+files/ProcCpuinfoMinimal.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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372702/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372704/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] NetDevice.enp0s31f6.txt
apport information ** Attachment added: "NetDevice.enp0s31f6.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372703/+files/NetDevice.enp0s31f6.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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372708/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372710/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] NetworkManager.conf.txt
apport information ** Attachment added: "NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372707/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372701/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] NetDevice.wlp4s0.txt
apport information ** Attachment added: "NetDevice.wlp4s0.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372706/+files/NetDevice.wlp4s0.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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] NetDevice.vpn0.txt
apport information ** Attachment added: "NetDevice.vpn0.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372705/+files/NetDevice.vpn0.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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372700/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] Re: Openconnect provided DNS servers are not read by NetworkManager
apport information ** Tags added: apport-collected ** Description changed: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: KDE + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-05-13 (3 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + IpRoute: + default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 + default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 + 169.254.0.0/16 dev wlp4s0 scope link metric 1000 + 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 + 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 + Package: network-manager 1.22.10-1ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 + Tags: focal + Uname: Linux 5.4.0-29-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo + _MarkForUpload: True + mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 + nmcli-nm: + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.22.10 connected started full enabled enabled enabled enabled enabled ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1878707/+attachment/5372699/+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/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: Incomplete Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage
[Touch-packages] [Bug 1817123] Re: tmpfiles.d files pointing to legacy directory /var/run
Fixed in version speech-dispatcher/0.9.1-4 Fixed in version spice-vdagent/0.19.0-1 ** Changed in: systemd (Ubuntu) Status: Confirmed => 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/1817123 Title: tmpfiles.d files pointing to legacy directory /var/run Status in systemd package in Ubuntu: Invalid Status in speech-dispatcher package in Debian: Fix Released Status in spice-vdagent package in Debian: Fix Released Bug description: Just updated cosmic and got: Setting up systemd (239-7ubuntu10.8) ... [/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher → /run/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:2] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache → /run/speech-dispatcher/.cache; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:3] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.speech-dispatcher → /run/speech-dispatcher/.speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:4] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache/speech-dispatcher → /run/speech-dispatcher/.cache/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:5] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/log → /run/speech-dispatcher/log; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/spice-vdagentd.conf:2] Line references path below legacy directory /var/run/, updating /var/run/spice-vdagentd → /run/spice-vdagentd; please update the tmpfiles.d/ drop-in file accordingly. andre@thinkpad:~$ lsb_release -rd Description:Ubuntu 18.10 Release:18.10 andre@thinkpad:~$ apt-cache policy systemd systemd: Installed: 239-7ubuntu10.8 Candidate: 239-7ubuntu10.8 Version table: *** 239-7ubuntu10.8 500 500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 Packages 100 /var/lib/dpkg/status 239-7ubuntu10 500 500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817123/+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 1879044] Re: gnome-shell restarts due to bluetooth disconnection
It also happens when the disconnection is made through the user interface (either blueman or settings -> bluetooth). -- 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/1879044 Title: gnome-shell restarts due to bluetooth disconnection Status in xorg package in Ubuntu: New Bug description: I am logged in an X session with gnome. Just after logging, I start a Sony Bluetooth headphones (WH-1000XM3). After they connect (and they work), I switch them off (using the switch in the headphones). < 3 seconds after disconnections, the gnome-session crashes (and restarts). If I do this in Wayland, since the server does not seem to support restarts, I am logged out of the session and the laptop returns to the login screen. Best, Manuel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 16 11:23:01 2020 DistUpgraded: 2020-05-09 00:31:28,496 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225c] InstallationDate: Installed on 2019-03-26 (416 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20KHCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to focal on 2020-05-08 (7 days ago) dmi.bios.date: 02/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET71W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879044/+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 1879089] [NEW] Single background colour and colour-gradient options are missing after upgrading from 18.04 to 20.04
Public bug reported: The options for selecting a single colour background, or, a colour gradient background, are missing in the settings, after upgrading from 18.04LTS to 20.04LTS. The upgrade was done according to this guide: https://www.linuxtechi.com/upgrade-ubuntu-18-04-lts-to-ubuntu-20-04-lts/ Also tried to make a clean install of 20.04LTS on a virtual machine, with the same result, those functions are missing. Kind regards Anton ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1879089 Title: Single background colour and colour-gradient options are missing after upgrading from 18.04 to 20.04 Status in ubuntu-settings package in Ubuntu: New Bug description: The options for selecting a single colour background, or, a colour gradient background, are missing in the settings, after upgrading from 18.04LTS to 20.04LTS. The upgrade was done according to this guide: https://www.linuxtechi.com/upgrade-ubuntu-18-04-lts-to-ubuntu-20-04-lts/ Also tried to make a clean install of 20.04LTS on a virtual machine, with the same result, those functions are missing. Kind regards Anton To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1879089/+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 1879090] [NEW] XDG_SEAT, XDG_VTNR, XDG_SESSION_ID not set
Public bug reported: I installed Ubuntu 20.04, it is running well. I switched display manager to lightdm. I noticed that it fails to set environment variables XDG_SEAT, XDG_VTNR, XDG_SESSION_ID. I also tested gdm3, it's the same. I also tried liveiso to no vail. apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu3.1 Candidate: 1.30.0-0ubuntu3.1 Version table: *** 1.30.0-0ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1879090 Title: XDG_SEAT, XDG_VTNR, XDG_SESSION_ID not set Status in lightdm package in Ubuntu: New Bug description: I installed Ubuntu 20.04, it is running well. I switched display manager to lightdm. I noticed that it fails to set environment variables XDG_SEAT, XDG_VTNR, XDG_SESSION_ID. I also tested gdm3, it's the same. I also tried liveiso to no vail. apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu3.1 Candidate: 1.30.0-0ubuntu3.1 Version table: *** 1.30.0-0ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1879090/+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 1879087] [NEW] dbus errors, frequent roaming and unstable connectivity
Public bug reported: When using this version of wpa_supplicant with my company WPA2-Enterprise wireless setup, I'm experiencing far too frequent roaming events (even when not moving around) accompanied by hiccups in connectivity. I also see these messages in the wpa_supplicant log: dbus: wpa_dbus_property_changed: no property RoamComplete in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property RoamTime in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3 Having done a little research, at least the dbus errors seem to be fixed by this commit upstream: https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756 So I built a version of wpa_supplicant including this particular patch and installed on my machine. Apart from solving the dbus errors completely, it seems to have had a positive impact on the frequent roaming and unstable connectivity as well (I've run for a day with no burst of roaming events at all, where they used to happen every few minutes most of the time.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: wpasupplicant 2:2.9-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat May 16 16:47:27 2020 InstallationDate: Installed on 2020-05-12 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1879087 Title: dbus errors, frequent roaming and unstable connectivity Status in wpa package in Ubuntu: New Bug description: When using this version of wpa_supplicant with my company WPA2-Enterprise wireless setup, I'm experiencing far too frequent roaming events (even when not moving around) accompanied by hiccups in connectivity. I also see these messages in the wpa_supplicant log: dbus: wpa_dbus_property_changed: no property RoamComplete in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property RoamTime in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3 Having done a little research, at least the dbus errors seem to be fixed by this commit upstream: https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756 So I built a version of wpa_supplicant including this particular patch and installed on my machine. Apart from solving the dbus errors completely, it seems to have had a positive impact on the frequent roaming and unstable connectivity as well (I've run for a day with no burst of roaming events at all, where they used to happen every few minutes most of the time.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: wpasupplicant 2:2.9-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat May 16 16:47:27 2020 InstallationDate: Installed on 2020-05-12 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1879087/+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 1325757] Re: USB Hub does not mount the USB devices
i can not see my USB in disks app or in [ fdisk -l ] result but i can see my flash USB in [ lsbsk ] result -- 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/1325757 Title: USB Hub does not mount the USB devices Status in systemd package in Ubuntu: Invalid Bug description: USB Hub doesn't mount the USB devices correctly. The Hub mounts some devices, does not mounts another and I can not insert another USB Hub inside it and agreegate USB ports. The system does not mount correctly and accurately the USB devices when using USB hubs. This is the bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.2 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 2 19:01:14 2014 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HotplugNewDevices: /dev/sde1 /dev/sde HotplugNewMounts: InstallationDate: Installed on 2014-05-30 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=cd35f223-f2ea-4470-b8d1-014a6008deb8 ro locale=pt_BR quiet splash vt.handoff=7 SourcePackage: systemd Symptom: storage Title: Removable storage device not detected as block device UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 19:01:39.045: The udisks-daemon is running (name-owner :1.68). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0502 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX/BR dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0502:bd12/01/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1325757/+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 1325757] Re: USB Hub does not mount the USB devices
it have not any problem in a windows device -- 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/1325757 Title: USB Hub does not mount the USB devices Status in systemd package in Ubuntu: Invalid Bug description: USB Hub doesn't mount the USB devices correctly. The Hub mounts some devices, does not mounts another and I can not insert another USB Hub inside it and agreegate USB ports. The system does not mount correctly and accurately the USB devices when using USB hubs. This is the bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.2 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 2 19:01:14 2014 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HotplugNewDevices: /dev/sde1 /dev/sde HotplugNewMounts: InstallationDate: Installed on 2014-05-30 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=cd35f223-f2ea-4470-b8d1-014a6008deb8 ro locale=pt_BR quiet splash vt.handoff=7 SourcePackage: systemd Symptom: storage Title: Removable storage device not detected as block device UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 19:01:39.045: The udisks-daemon is running (name-owner :1.68). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0502 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX/BR dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0502:bd12/01/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1325757/+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 1879085] [NEW] update-initramfs can't handle encrypted swap-files
Public bug reported: OS: Ubuntu 20.04 Mate I have an encrypted swap-file, which is working fine: # grep cryptswap /etc/fstab /dev/mapper/cryptswap none swap defaults 0 0 # grep cryptswap /etc/crypttab cryptswap /cryptswapfile /dev/urandom swap,cipher=aes-xts-plain64,size=256 But everytime I update the kernel and update-initramfs is executed, an error occurs: cryptsetup: ERROR: Couldn't resolve device /cryptswapfile cryptsetup: WARNING: Resume target cryptswap uses a key file And after the next reboot, the system can't load the cryptswap while booting and hangs for several minutes. Workaround: Boot into rescue mode and wait until the loading of the cryptswapfile timeouts. Go to a shell and comment the lines in the fstab and crypttab. Execute # swapoff -a && update-initramfs -u. Now uncomment the lines in fstab and crypttab again and reboot. Your system should boot fine and you should have an encrypted swapfile. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: focal ** Description changed: + OS: Ubuntu 20.04 Mate + I have an encrypted swap-file, which is working fine: - # grep cryptswap /etc/fstab + # grep cryptswap /etc/fstab /dev/mapper/cryptswap none swap defaults 0 0 - # grep cryptswap /etc/crypttab + # grep cryptswap /etc/crypttab cryptswap /cryptswapfile /dev/urandom swap,cipher=aes-xts-plain64,size=256 But everytime I update the kernel and update-initramfs is executed, an error occurs: cryptsetup: ERROR: Couldn't resolve device /cryptswapfile cryptsetup: WARNING: Resume target cryptswap uses a key file And after reboot, the system can't load the cryptswap while booting and hangs for several minutes. - - Workaround: Boot into rescue mode and wait until the loading of the cryptswapfile timeouts. Go to a shell and comment the lines in the fstab and crypttab. Execute # swapoff -a && update-initramfs -u. Now uncomment the lines in fstab and crypttab again and reboot. Your system should boot fine and you should have an encrypted swapfile. + Workaround: Boot into rescue mode and wait until the loading of the + cryptswapfile timeouts. Go to a shell and comment the lines in the fstab + and crypttab. Execute # swapoff -a && update-initramfs -u. Now uncomment + the lines in fstab and crypttab again and reboot. Your system should + boot fine and you should have an encrypted swapfile. ** Description changed: OS: Ubuntu 20.04 Mate I have an encrypted swap-file, which is working fine: # grep cryptswap /etc/fstab /dev/mapper/cryptswap none swap defaults 0 0 # grep cryptswap /etc/crypttab cryptswap /cryptswapfile /dev/urandom swap,cipher=aes-xts-plain64,size=256 But everytime I update the kernel and update-initramfs is executed, an error occurs: cryptsetup: ERROR: Couldn't resolve device /cryptswapfile cryptsetup: WARNING: Resume target cryptswap uses a key file - And after reboot, the system can't load the cryptswap while booting and - hangs for several minutes. + And after the next reboot, the system can't load the cryptswap while + booting and hangs for several minutes. Workaround: Boot into rescue mode and wait until the loading of the cryptswapfile timeouts. Go to a shell and comment the lines in the fstab and crypttab. Execute # swapoff -a && update-initramfs -u. Now uncomment the lines in fstab and crypttab again and reboot. Your system should boot fine and you should have an encrypted swapfile. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1879085 Title: update-initramfs can't handle encrypted swap-files Status in initramfs-tools package in Ubuntu: New Bug description: OS: Ubuntu 20.04 Mate I have an encrypted swap-file, which is working fine: # grep cryptswap /etc/fstab /dev/mapper/cryptswap none swap defaults 0 0 # grep cryptswap /etc/crypttab cryptswap /cryptswapfile /dev/urandom swap,cipher=aes-xts-plain64,size=256 But everytime I update the kernel and update-initramfs is executed, an error occurs: cryptsetup: ERROR: Couldn't resolve device /cryptswapfile cryptsetup: WARNING: Resume target cryptswap uses a key file And after the next reboot, the system can't load the cryptswap while booting and hangs for several minutes. Workaround: Boot into rescue mode and wait until the loading of the cryptswapfile timeouts. Go to a shell and comment the lines in the fstab and crypttab. Execute # swapoff -a && update-initramfs -u. Now uncomment the lines in fstab and crypttab again and reboot. Your system should boot fine and you should have an encrypted swapfile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879085/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1325757] Re: USB Hub does not mount the USB devices
yes The problem is not port and my system have not any problem while i connect them some another flash devices -- 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/1325757 Title: USB Hub does not mount the USB devices Status in systemd package in Ubuntu: Invalid Bug description: USB Hub doesn't mount the USB devices correctly. The Hub mounts some devices, does not mounts another and I can not insert another USB Hub inside it and agreegate USB ports. The system does not mount correctly and accurately the USB devices when using USB hubs. This is the bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.2 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 2 19:01:14 2014 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HotplugNewDevices: /dev/sde1 /dev/sde HotplugNewMounts: InstallationDate: Installed on 2014-05-30 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=cd35f223-f2ea-4470-b8d1-014a6008deb8 ro locale=pt_BR quiet splash vt.handoff=7 SourcePackage: systemd Symptom: storage Title: Removable storage device not detected as block device UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 19:01:39.045: The udisks-daemon is running (name-owner :1.68). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0502 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX/BR dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0502:bd12/01/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1325757/+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 1325757] Re: USB Hub does not mount the USB devices
i try to connect my USB device to computer but it did not work also i can not
see my USB in the {fdisk -l} result
but i have not any problem to connect some flash USB devices
i do not know how can i fix my problem
please help me
--
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/1325757
Title:
USB Hub does not mount the USB devices
Status in systemd package in Ubuntu:
Invalid
Bug description:
USB Hub doesn't mount the USB devices correctly. The Hub mounts some
devices, does not mounts another and I can not insert another USB Hub
inside it and agreegate USB ports. The system does not mount correctly
and accurately the USB devices when using USB hubs. This is the bug.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: udev 204-5ubuntu20.2
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Jun 2 19:01:14 2014
GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
HotplugNewDevices: /dev/sde1 /dev/sde
HotplugNewMounts:
InstallationDate: Installed on 2014-05-30 (3 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic
root=UUID=cd35f223-f2ea-4470-b8d1-014a6008deb8 ro locale=pt_BR quiet splash
vt.handoff=7
SourcePackage: systemd
Symptom: storage
Title: Removable storage device not detected as block device
UdisksMonitorLog:
Monitoring the udisks daemon. Press Ctrl+C to exit.
19:01:39.045: The udisks-daemon is running (name-owner :1.68).
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0502
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M5A78L-M LX/BR
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0502:bd12/01/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1325757/+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 1325757] Re: USB Hub does not mount the USB devices
** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Emad Bahrami (bashma) -- 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/1325757 Title: USB Hub does not mount the USB devices Status in systemd package in Ubuntu: Invalid Bug description: USB Hub doesn't mount the USB devices correctly. The Hub mounts some devices, does not mounts another and I can not insert another USB Hub inside it and agreegate USB ports. The system does not mount correctly and accurately the USB devices when using USB hubs. This is the bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.2 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 2 19:01:14 2014 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HotplugNewDevices: /dev/sde1 /dev/sde HotplugNewMounts: InstallationDate: Installed on 2014-05-30 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=cd35f223-f2ea-4470-b8d1-014a6008deb8 ro locale=pt_BR quiet splash vt.handoff=7 SourcePackage: systemd Symptom: storage Title: Removable storage device not detected as block device UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 19:01:39.045: The udisks-daemon is running (name-owner :1.68). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0502 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX/BR dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0502:bd12/01/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1325757/+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 1879080] [NEW] error message when installing pyodbc in a venv
Public bug reported:
I have a fresh install of Ubuntu 20.04. I have the following packages
installed:
python3-venv
python3-pip
python3-wheel
unixodbc-dev
If I run these commands:
python3 -m venv ./test_env
. ./test_env/bin/activate
pip3 install pyodbc
This is the output I get. The package does seem to install successfully,
in spite of the fact that this is an error, not a warning.
Collecting pyodbc
Downloading pyodbc-4.0.30.tar.gz (266 kB)
|| 266 kB 3.5 MB/s
Building wheels for collected packages: pyodbc
Building wheel for pyodbc (setup.py) ... error
ERROR: Command errored out with exit status 1:
command: /tmp/test_env/bin/python3 -u -c 'import sys, setuptools, tokenize;
sys.argv[0] = '"'"'/tmp/pip-install-5uh1fr89/pyodbc/setup.py'"'"';
__file__='"'"'/tmp/pip-install-5uh1fr89/pyodbc/setup.py'"'"';f=getattr(tokenize,
'"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"',
'"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))'
bdist_wheel -d /tmp/pip-wheel-snlh9z0l
cwd: /tmp/pip-install-5uh1fr89/pyodbc/
Complete output (6 lines):
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
error: invalid command 'bdist_wheel'
ERROR: Failed building wheel for pyodbc
Running setup.py clean for pyodbc
Failed to build pyodbc
Installing collected packages: pyodbc
Running setup.py install for pyodbc ... done
Successfully installed pyodbc-4.0.30
Note that I do not get this error if I install pyodbc outside the venv.
Also, if I install it outside the venv FIRST, then pip will cache the
wheel package and use it when installing in the venv, and I don't get
the above error in that case.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: python3 3.8.2-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat May 16 10:14:28 2020
InstallationDate: Installed on 2020-05-16 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: python3-defaults
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: python3-defaults (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1879080
Title:
error message when installing pyodbc in a venv
Status in python3-defaults package in Ubuntu:
New
Bug description:
I have a fresh install of Ubuntu 20.04. I have the following packages
installed:
python3-venv
python3-pip
python3-wheel
unixodbc-dev
If I run these commands:
python3 -m venv ./test_env
. ./test_env/bin/activate
pip3 install pyodbc
This is the output I get. The package does seem to install
successfully, in spite of the fact that this is an error, not a
warning.
Collecting pyodbc
Downloading pyodbc-4.0.30.tar.gz (266 kB)
|| 266 kB 3.5 MB/s
Building wheels for collected packages: pyodbc
Building wheel for pyodbc (setup.py) ... error
ERROR: Command errored out with exit status 1:
command: /tmp/test_env/bin/python3 -u -c 'import sys, setuptools,
tokenize; sys.argv[0] = '"'"'/tmp/pip-install-5uh1fr89/pyodbc/setup.py'"'"';
__file__='"'"'/tmp/pip-install-5uh1fr89/pyodbc/setup.py'"'"';f=getattr(tokenize,
'"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"',
'"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))'
bdist_wheel -d /tmp/pip-wheel-snlh9z0l
cwd: /tmp/pip-install-5uh1fr89/pyodbc/
Complete output (6 lines):
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
error: invalid command 'bdist_wheel'
ERROR: Failed building wheel for pyodbc
Running setup.py clean for pyodbc
Failed to build pyodbc
Installing collected packages: pyodbc
Running setup.py install for pyodbc ... done
Successfully installed pyodbc-4.0.30
Note that I do not get this error if I install pyodbc outside the
venv. Also, if I install it outside the venv FIRST, then pip will
cache the wheel package and use it when installing in the venv, and I
don't get the above error in that case.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: python3 3.8.2-0ubuntu2
ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: procps (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1874824 Title: pgrep reports error "cannot allocate" when run without stack limit Status in procps package in Ubuntu: Confirmed Bug description: If you have no stack limit (ulimit -S -s unlimited), any pgrep call will fail with an error: > pgrep vim pgrep: cannot allocate 4611686018427387903 bytes If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is very slow: > time pgrep vim 2196 real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444 The relevant upstream bug report could be: https://gitlab.com/procps-ng/procps/-/issues/152 Archlinux bug report: https://bugs.archlinux.org/task/66093 procps: Installed: 2:3.3.16-1ubuntu2 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+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 1872485] Re: virtualbox-guest-utils fails to install on 20.04
** Changed in: virtualbox (Ubuntu) Status: Confirmed => Fix Released -- 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/1872485 Title: virtualbox-guest-utils fails to install on 20.04 Status in systemd package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in systemd package in Debian: Fix Released Status in virtualbox package in Debian: New Bug description: Attempting to install virtualbox-guest-utils 6.1.4-dfsg-2 on ubuntu:focal (20.04) produces a broken state. Debug of `apt-get install virtualbox-guest-utils` below. Steps to reproduce: 1. pull a fresh 20.04 image for testing (ex: lxc launch ubuntu-daily:20.04 test-container) 2. lxc exec test-container bash 3. apt update 4. apt full-upgrade 5. apt-get install virtualbox-guest-utils Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: glib-networking : Depends: gsettings-desktop-schemas but it is not going to be installed init : PreDepends: systemd-sysv but it is not going to be installed Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < none -> 6.1.4-dfsg-2 @un puN > Considering virtualbox-guest-utils:amd64 9998 as a solution to systemd-timesyncd:amd64 14 Removing systemd-timesyncd:amd64 rather than change virtualbox-guest-utils:amd64 Investigating (1) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mR > Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59 Added systemd-timesyncd:amd64 to the remove list Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H > Considering openntpd:amd64 0 as a solution to systemd:amd64 59 Added openntpd:amd64 to the remove list Fixing systemd:amd64 via keep of systemd-timesyncd:amd64 Fixing systemd:amd64 via keep of openntpd:amd64 Investigating (1) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < none -> 6.1.4-dfsg-2 @un puN > Considering virtualbox-guest-utils:amd64 9998 as a solution to systemd-timesyncd:amd64 14 Removing systemd-timesyncd:amd64 rather than change virtualbox-guest-utils:amd64 Investigating (2) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mR > Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59 Added systemd-timesyncd:amd64 to the remove list Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H > Considering openntpd:amd64 0 as a solution to systemd:amd64 59 Added openntpd:amd64 to the remove list Fixing systemd:amd64 via keep of systemd-timesyncd:amd64 Fixing systemd:amd64 via keep of openntpd:amd64 Investigating (2) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < none -> 6.1.4-dfsg-2 @un puN > Considering virtualbox-guest-utils:amd64 9998 as a solution to systemd-timesyncd:amd64 59 Removing systemd-timesyncd:amd64 rather than change virtualbox-guest-utils:amd64 Investigating (3) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mR > Considering systemd-timesyncd:amd64 9998 as a solution to systemd:amd64 59 Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H > Considering openntpd:amd64 59 as a solution to systemd:amd64 59 Or group remove for systemd:amd64 Investigating (3) libpam-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken libpam-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR > (= 245.4-2ubuntu1) Considering systemd:amd64 59 as a solution to libpam-systemd:amd64 23 Removing libpam-systemd:amd64 rather than change systemd:amd64 Investigating (3) libnss-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib > Broken libnss-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR > (= 245.4-2ubuntu1) Considering systemd:amd64 59 as a solution to libnss-systemd:amd64 14 Removing libnss-systemd:amd64 rather than change systemd:amd64 Investigating (3) plymouth:amd64 < 0.9.4git20200323-0ubuntu6 @ii mK Ib > Broken
[Touch-packages] [Bug 1879076] [NEW] Xorg freeze
Public bug reported: When in both Firefox and Opera hardware acceleration is on and browser is running it will trigger freeze with X.OrgX driver on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_uvm 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 16 12:17:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 1600M] [10de:040d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G84GLM [Quadro FX 1600M] [1028:019b] InstallationDate: Installed on 2020-04-08 (38 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Precision M6300 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=57f985ce-6982-47e4-8428-74d41764c9ce ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0JM680 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd06/05/2013:svnDellInc.:pnPrecisionM6300:pvr:rvnDellInc.:rn0JM680:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M6300 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.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 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 possible-manual-nvidia-install 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/1879076 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: When in both Firefox and Opera hardware acceleration is on and browser is running it will trigger freeze with X.OrgX driver on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_uvm 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 16 12:17:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 1600M] [10de:040d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G84GLM [Quadro FX 1600M] [1028:019b] InstallationDate: Installed on 2020-04-08 (38 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Precision M6300 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=57f985ce-6982-47e4-8428-74d41764c9ce ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze
[Touch-packages] [Bug 1876152] Re: dstat warnings on install
*** This bug is a duplicate of bug 1870947 ***
https://bugs.launchpad.net/bugs/1870947
** Package changed: libtool (Ubuntu) => dstat (Ubuntu)
** Bug watch added: Debian Bug tracker #956188
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956188
** Also affects: dstat (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956188
Importance: Unknown
Status: Unknown
** This bug has been marked a duplicate of bug 1870947
SyntaxWarning with obviously buggy code
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libtool in Ubuntu.
https://bugs.launchpad.net/bugs/1876152
Title:
dstat warnings on install
Status in dstat package in Ubuntu:
New
Status in dstat package in Debian:
Unknown
Bug description:
Upon installing dstat I received this warning/error:
Setting up dstat (0.7.4-6) ...
/usr/share/dstat/dstat_mysql_keys.py:41: SyntaxWarning: 'str' object is not
callable; perhaps you missed a comma?
if op.debug > 1: print('%s: exception' (self.filename, e))
/usr/share/dstat/dstat_squid.py:48: SyntaxWarning: 'str' object is not
callable; perhaps you missed a comma?
if op.debug > 1: print('%s: exception' (self.filename, e))
basic dstat functions still operate
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dstat/+bug/1876152/+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 1879075] [NEW] Bluetooth sound card not detected.
Public bug reported: not connecting to my Bluetooth headphones. same problem on my desktop computor. all worked ok with 18.04 .sometimes it will connect but after a few seconds it will disconnect, if i remove the device, and then add it, i can get it to connect, but YouTube video stalls with no sound, if i disconnect the headphones, the video plays. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 1501 F pulseaudio /dev/snd/controlC0: chris 1501 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 16 17:06:19 2020 InstallationDate: Installed on 2020-05-04 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Grumpy_PK dmi.board.vendor: PK dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd09/26/2019:svnAcer:pnAspireA515-43:pvrV1.06:rvnPK:rnGrumpy_PK:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-43 dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: not connecting to my Bluetooth headphones. same problem on my desktop - computor. all worked ok with 18.04 sometimes it will connect but after a - few seconds it will disconnect, if i remove the device, and the add it, - i can get it to connect, but YouTube video stalls with no sound, if i - disconnect the headphones, the video plays. + computor. all worked ok with 18.04 .sometimes it will connect but after + a few seconds it will disconnect, if i remove the device, and then add + it, i can get it to connect, but YouTube video stalls with no sound, if + i disconnect the headphones, the video plays. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: chris 1501 F pulseaudio - /dev/snd/controlC0: chris 1501 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: chris 1501 F pulseaudio + /dev/snd/controlC0: chris 1501 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 16 17:06:19 2020 InstallationDate: Installed on 2020-05-04 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: - LANGUAGE=en_GB:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_GB.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_GB:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_GB.UTF-8 + SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Grumpy_PK dmi.board.vendor: PK dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd09/26/2019:svnAcer:pnAspireA515-43:pvrV1.06:rvnPK:rnGrumpy_PK:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-43 dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1879075 Title: Bluetooth sound card not detected. Status in alsa-driver package in Ubuntu: New Bug description: not connecting to my Bluetooth headphones. same problem on my desktop computor. all worked ok with 18.04 .sometimes it will connect but after a few seconds it will disconnect, if i remove the device, and then add it, i can get it to connect, but YouTube video stalls with no sound, if i disconnect the headphones, the video plays. ProblemType: Bug
[Touch-packages] [Bug 1876147] Re: libtool-doc missing libtool.html
** Bug watch added: Debian Bug tracker #951498 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951498 ** Also affects: libtool (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951498 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtool in Ubuntu. https://bugs.launchpad.net/bugs/1876147 Title: libtool-doc missing libtool.html Status in libtool package in Ubuntu: New Status in libtool package in Debian: Unknown Bug description: I am posting this as a bug to libtool but the package is libtool-doc When installing doc-base I I received this error/warning: Processing triggers for doc-base (0.10.9) ... Processing 2 added doc-base files... Error in `/usr/share/doc-base/libtool-doc', line 9: all `Format' sections are invalid. Note: `install-docs --verbose --check file_name' may give more details about the above error. Running: install-docs --verbose --check /usr/share/doc-base/libtool-doc I got: Warning in `/usr/share/doc-base/libtool-doc', line 9: file `/usr/share/doc/libtool-doc/libtool.html' does not exist. Error in `/usr/share/doc-base/libtool-doc', line 9: all `Format' sections are invalid. /usr/share/doc-base/libtool-doc: Fatal error found, the file won't be registered. A search for which package owns /usr/share/doc-base/libtool-doc apt-file search /usr/share/doc-base/libtool-doc libtool-doc: /usr/share/doc-base/libtool-doc Line 9 in /usr/share/doc-base/libtool-doc is; Index: /usr/share/doc/libtool-doc/libtool.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtool/+bug/1876147/+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 1876518] Re: Gtk.Clipboard set_text() not working
This has been reported upstream:
(https://gitlab.gnome.org/GNOME/pygobject/-/issues/405
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1876518
Title:
Gtk.Clipboard set_text() not working
Status in pygobject:
Unknown
Status in pygobject package in Ubuntu:
Incomplete
Bug description:
Writing to Gtk.Clipboard doesn't work (reading works).
Example code:
#!/usr/bin/python3
import gi
gi.require_version('Gtk', '3.0')
from gi.repository import Gtk, Gdk
clipboard = Gtk.Clipboard.get(Gdk.SELECTION_CLIPBOARD)
clipboard.set_text("Does a text of all texts contain itself?", -1)
clipboard.store()
Ubuntu 20.04 with Gtk 3.36.0-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/pygobject/+bug/1876518/+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 1879054] [NEW] No sound after 20.04 update
Public bug reported: After update from 18.04 to 20.04 sound stopped working. KDE does not display Xonar sound card at all. $ aplay /usr/share/sounds/alsa/Front_Center.wav does not make any sound Alsamixer displays Xonar set at full volume but changing anything there does not seem to have any effect. Moving/deleting the pulse config ( ~/.config/pulse/ ) and restarting machine did not have any effect. Running: $ sudo alsa force-reload fixes the issue (until restart sound is back, and is displayed properly in KDE) (data arecord and cards display same data before and after restart) $ arecord -l Lista CAPTURE urządzeń karta 0: DX [Xonar DX], urządzenie 0: Multichannel [Multichannel] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0 karta 0: DX [Xonar DX], urządzenie 1: Digital [Digital] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0 $ cat /proc/asound/cards 0 [DX ]: AV200 - Xonar DX Asus Virtuoso 100 at 0xd000, irq 31 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xfe96 irq 67 $ lspci | grep -i audio 21:04.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio] 23:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] (build in motherboard soundcard is disabled in BIOS) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nait 5242 F pulseaudio /dev/snd/controlC1: nait 5242 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 16 14:54:07 2020 InstallationDate: Installed on 2018-11-11 (552 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-05-01 (14 days ago) dmi.bios.date: 09/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.J0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.J0:bd09/27/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: After update from 18.04 to 20.04 sound stopped working. KDE does not display Xonar sound card at all. Alsamixer displays Xonar set at full volume but changing anything there does not seem to have any effect. Running: $ sudo alsa force-reload fixes the issue (until restart sound is back, and is displayed properly in KDE) - (data after restart) + (data arecord and cards display same data before and after restart) $ arecord -l Lista CAPTURE urządzeń karta 0: DX [Xonar DX], urządzenie 0: Multichannel [Multichannel] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0 karta 0: DX [Xonar DX], urządzenie 1: Digital [Digital] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0 $ cat /proc/asound/cards 0 [DX ]: AV200 - Xonar DX Asus Virtuoso 100 at 0xd000, irq 31 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xfe96 irq 67 (build in motherboard soundcard is disabled in BIOS) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nait 5242 F pulseaudio /dev/snd/controlC1: nait 5242 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 16 14:54:07 2020 InstallationDate: Installed on 2018-11-11 (552 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-05-01 (14 days ago) dmi.bios.date: 09/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.J0 dmi.board.asset.tag: To be filled by
[Touch-packages] [Bug 1879039] Re: Xorg crash
** Package changed: ubuntu => xorg (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/1879039 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: After Firefox crushes couldnt open any browser, no Firefox nor Chromium and I had to restart the OS. Ubuntu 19.10 is a guest OS on Parallels 15 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-53.47-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_vid prl_tg ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Sat May 16 12:17:36 2020 DistUpgraded: 2020-05-09 07:53:36,319 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: parallels-tools, 15.1.4.47270, 4.15.0-100-generic, x86_64: installed parallels-tools, 15.1.4.47270, 5.3.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Parallels, Inc. Accelerated Virtual Video Adapter [1ab8:4005] (prog-if 00 [VGA controller]) Subsystem: Parallels, Inc. Accelerated Virtual Video Adapter [1ab8:0400] InstallationDate: Installed on 2018-08-10 (644 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Parallels Software International Inc. Parallels Virtual Platform MonitorsUser.xml: Virtual1unknownunknownunknown144090059.988003001yes ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=b214da3c-eaae-4adf-bfcc-c64b050618e8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2020-05-09 (7 days ago) dmi.bios.date: 04/13/2020 dmi.bios.vendor: Parallels Software International Inc. dmi.bios.version: 15.1.4 (47270) dmi.board.name: Parallels Virtual Platform dmi.board.vendor: Parallels Software International Inc. dmi.board.version: None dmi.chassis.type: 9 dmi.chassis.vendor: Parallels Software International Inc. dmi.modalias: dmi:bvnParallelsSoftwareInternationalInc.:bvr15.1.4(47270):bd04/13/2020:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct9:cvr: dmi.product.family: Parallels VM dmi.product.name: Parallels Virtual Platform dmi.product.sku: Undefined dmi.product.version: None dmi.sys.vendor: Parallels Software International Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879039/+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 1879039] [NEW] Xorg crash
You have been subscribed to a public bug: After Firefox crushes couldnt open any browser, no Firefox nor Chromium and I had to restart the OS. Ubuntu 19.10 is a guest OS on Parallels 15 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-53.47-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_vid prl_tg ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Sat May 16 12:17:36 2020 DistUpgraded: 2020-05-09 07:53:36,319 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: parallels-tools, 15.1.4.47270, 4.15.0-100-generic, x86_64: installed parallels-tools, 15.1.4.47270, 5.3.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Parallels, Inc. Accelerated Virtual Video Adapter [1ab8:4005] (prog-if 00 [VGA controller]) Subsystem: Parallels, Inc. Accelerated Virtual Video Adapter [1ab8:0400] InstallationDate: Installed on 2018-08-10 (644 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Parallels Software International Inc. Parallels Virtual Platform MonitorsUser.xml: Virtual1unknownunknownunknown144090059.988003001yes ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=b214da3c-eaae-4adf-bfcc-c64b050618e8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2020-05-09 (7 days ago) dmi.bios.date: 04/13/2020 dmi.bios.vendor: Parallels Software International Inc. dmi.bios.version: 15.1.4 (47270) dmi.board.name: Parallels Virtual Platform dmi.board.vendor: Parallels Software International Inc. dmi.board.version: None dmi.chassis.type: 9 dmi.chassis.vendor: Parallels Software International Inc. dmi.modalias: dmi:bvnParallelsSoftwareInternationalInc.:bvr15.1.4(47270):bd04/13/2020:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct9:cvr: dmi.product.family: Parallels VM dmi.product.name: Parallels Virtual Platform dmi.product.sku: Undefined dmi.product.version: None dmi.sys.vendor: Parallels Software International Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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 crash eoan ubuntu -- Xorg crash https://bugs.launchpad.net/bugs/1879039 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- 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 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
Official site released the fix about bionic and xenial: https://github.com/json-c/json-c/commit/f2b7d0b5cbd0eccf4fb3c1851ec0864952be1057 But above has a problem in lh_table_insert(): if t->count > INT_MAX * LH_LOAD_FACTOR then error return Thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+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 1879044] Re: gnome-shell restarts due to bluetooth disconnection
It may of course be a bluetooth bug, but when I tried to submit it as an audio/sound-related problem, I could not characterize it correctly. -- 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/1879044 Title: gnome-shell restarts due to bluetooth disconnection Status in xorg package in Ubuntu: New Bug description: I am logged in an X session with gnome. Just after logging, I start a Sony Bluetooth headphones (WH-1000XM3). After they connect (and they work), I switch them off (using the switch in the headphones). < 3 seconds after disconnections, the gnome-session crashes (and restarts). If I do this in Wayland, since the server does not seem to support restarts, I am logged out of the session and the laptop returns to the login screen. Best, Manuel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 16 11:23:01 2020 DistUpgraded: 2020-05-09 00:31:28,496 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225c] InstallationDate: Installed on 2019-03-26 (416 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20KHCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to focal on 2020-05-08 (7 days ago) dmi.bios.date: 02/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET71W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879044/+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 1879044] [NEW] gnome-shell restarts due to bluetooth disconnection
Public bug reported: I am logged in an X session with gnome. Just after logging, I start a Sony Bluetooth headphones (WH-1000XM3). After they connect (and they work), I switch them off (using the switch in the headphones). < 3 seconds after disconnections, the gnome-session crashes (and restarts). If I do this in Wayland, since the server does not seem to support restarts, I am logged out of the session and the laptop returns to the login screen. Best, Manuel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 16 11:23:01 2020 DistUpgraded: 2020-05-09 00:31:28,496 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225c] InstallationDate: Installed on 2019-03-26 (416 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20KHCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to focal on 2020-05-08 (7 days ago) dmi.bios.date: 02/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET71W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 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 crash focal 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/1879044 Title: gnome-shell restarts due to bluetooth disconnection Status in xorg package in Ubuntu: New Bug description: I am logged in an X session with gnome. Just after logging, I start a Sony Bluetooth headphones (WH-1000XM3). After they connect (and they work), I switch them off (using the switch in the headphones). < 3 seconds after disconnections, the gnome-session crashes (and restarts). If I do this in Wayland, since the server does not seem to support restarts, I am logged out of the session and the laptop returns to the login screen. Best, Manuel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 16 11:23:01 2020 DistUpgraded: 2020-05-09 00:31:28,496 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225c] InstallationDate: Installed on 2019-03-26 (416 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic
[Touch-packages] [Bug 1879042] [NEW] Xorg high CPU usage and stuttering on ubuntu 20.04
Public bug reported: After upgrading Xubuntu from 19.10 to 20.04, some window operations (e.g. bringing one to foreground) can take an unusually long time (tenths of second, enough to compromise the general responsiveness of the system). Even switching from one terminal window to another causes a 80-90% CPU spike due to Xorg. (Tested with xfce4-terminal as well as rxvt.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat May 16 11:12:32 2020 DistUpgraded: 2020-05-09 17:20:01,127 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4290] [1002:9714] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. RS880 [Radeon HD 4290] [1043:8454] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=7ac7906b-f137-4adf-9de3-2ec128242354 ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-09 (6 days ago) dmi.bios.date: 04/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/13/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2017-10-10T22:39:42.917279 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 performance 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/1879042 Title: Xorg high CPU usage and stuttering on ubuntu 20.04 Status in xorg package in Ubuntu: New Bug description: After upgrading Xubuntu from 19.10 to 20.04, some window operations (e.g. bringing one to foreground) can take an unusually long time (tenths of second, enough to compromise the general responsiveness of the system). Even switching from one terminal window to another causes a 80-90% CPU spike due to Xorg. (Tested with xfce4-terminal as well as rxvt.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat May 16 11:12:32 2020 DistUpgraded: 2020-05-09 17:20:01,127 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4290] [1002:9714] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. RS880 [Radeon HD 4290] [1043:8454] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=7ac7906b-f137-4adf-9de3-2ec128242354 ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-09 (6 days ago) dmi.bios.date: 04/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag:
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
I have a Xenial server with upstart. I've made patches for CVE-2020-12762. See: https://gist.github.com/h-yamamo/61161ea78f3bb7761e508ca531c7 Thank you. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-12762 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+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
