[Touch-packages] [Bug 1870729] [NEW] DHCP Server regularly killed code=killed, status=6/ABRT

2020-04-03 Thread Andrew Welham
Public bug reported:

On Ubuntu 20.04 The idc-dhcp- server version is
isc-dhcp-server:
  Installed: (none)
  Candidate: 4.4.1-2.1ubuntu3
  Version table:
 4.4.1-2.1ubuntu3 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages


The DHCP server is being regularly killed, when searching google the  bug looks 
very similar to an older bug regarding accessing a lease file, that was fixed 
year ago. As a temporary fix in systemd I have enabled a restart every time the 
main process fails. The error got worse when i start to run a pair of dhcp 
servers syncing state between each other


I regularly see the following in the syslog

Apr  4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
Apr  4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ??
Apr  4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ??
Apr  4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ??
Apr  4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ??
Apr  4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ??
Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.
Apr  4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart job, 
restart counter is at 3.
Apr  4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server.
Apr  4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server.
Apr  4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400 
audit(1585958700.678:46): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Apr  4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1
Apr  4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1
Apr  4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium.
Apr  4 00:05:00 gw sh[2049]: All rights reserved.
Apr  4 00:05:00 gw sh[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
Apr  4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems Consortium.
Apr  4 00:05:00 gw dhcpd[2049]: All rights reserved.
Apr  4 00:05:00 gw dhcpd[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
Apr  4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400 
audit(1585958700.678:47): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Apr  4 00:05:00 gw kernel: [ 3508.161563] audit: type=1400 
audit(1585958700.682:48): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2070/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Apr  4 00:05:00 gw dhcpd[2049]: Config file: /etc/dhcp/dhcpd.conf
Apr  4 00:05:00 gw sh[2049]: Config file: /etc/dhcp/dhcpd.conf
Apr  4 00:05:00 gw sh[2049]: Database file: /var/lib/dhcp/dhcpd.leases
Apr  4 00:05:00 gw sh[2049]: PID file: /run/dhcp-server/dhcpd.pid
Apr  4 00:05:00 gw dhcpd[2049]: Database file: /var/lib/dhcp/dhcpd.leases
Apr  4 00:05:00 gw dhcpd[2049]: PID file: /run/dhcp-server/dhcpd.pid
Apr  4 00:05:00 gw dhcpd[2049]: Wrote 0 deleted host decls to leases file.

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1870729

Title:
  DHCP Server regularly killed code=killed, status=6/ABRT

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.04 The idc-dhcp- server version is
  isc-dhcp-server:
Installed: (none)
Candidate: 4.4.1-2.1ubuntu3
Version table:
   4.4.1-2.1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  The DHCP server is being regularly killed, when searching google the  bug 
looks very similar to an older bug regarding accessing a lease file, that was 
fixed year ago. As a temporary fix in systemd I have enabled a restart every 
time the main process fails. The error got worse when i start to run a pair of 
dhcp servers syncing state between each other

  
  I regularly see the following in the syslog

  Apr  4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr  4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ??
  Apr  4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ??
  Apr  4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ??
  Apr  4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ??
  Apr  4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ??
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.
  Apr  4 00:05:00 gw systemd[1]: isc-dhcp-server.service: 

[Touch-packages] [Bug 1870726] [NEW] Ubuntu Login Screen Loop

2020-04-03 Thread Rajkumar S
Public bug reported:

* Ubuntu Focal Fossa 20.04 (dev)
* xorg:
  Installed: 1:7.7+19ubuntu14
  Candidate: 1:7.7+19ubuntu1

Expected : Show desktop after login
Happened : On login screen, when password is entered correctly, it gets into a 
loop and shows the login screen again. But, it takes me to desktop properly if 
Ubuntu on Wayland is selected.

Steps to reproduce : 
1) Install Ubuntu 20 on an Oracle VirtualBox
2) Start a live session
3) Click the install button (Entire disk, Apply updates automatic)
4) After reboot, try to login.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  4 10:28:22 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
InstallationDate: Installed on 2020-04-04 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
Lsusb:
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=d609fc71-9cba-4875-8bc1-795cb584a629 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+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 focal ubuntu wayland-session

** Attachment added: "The video showing what actually happens."
   
https://bugs.launchpad.net/bugs/1870726/+attachment/5345984/+files/AayrBV8M.mp4

-- 
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/1870726

Title:
  Ubuntu Login Screen Loop

Status in xorg package in Ubuntu:
  New

Bug description:
  * Ubuntu Focal Fossa 20.04 (dev)
  * xorg:
Installed: 1:7.7+19ubuntu14
Candidate: 1:7.7+19ubuntu1

  Expected : Show desktop after login
  Happened : On login screen, when password is entered correctly, it gets into 
a loop and shows the login screen again. But, it takes me to desktop properly 
if Ubuntu on Wayland is selected.

  Steps to reproduce : 
  1) Install Ubuntu 20 on an Oracle VirtualBox
  2) Start a live session
  3) Click the install button (Entire disk, Apply updates automatic)
  4) After reboot, try to login.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 10:28:22 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2020-04-04 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 

[Touch-packages] [Bug 1854621] Re: ubuntu 20.04 daily boots with no background, selecting other background has warped picture

2020-04-03 Thread Chris Guiver
I ran a QA-test on (2020-Apr-03 ubu 20.04 desktop amd64)
dell [optiplex] 745 (c2d-6600, 6gb, amd/ati radeon rv516/x1300/x1550)
because lshw reports same video card, no glitches there with wallpaper on boot, 
nor changing wallpaper.

--- possibly unrelated
I did have that box boot the first time to "Oh No, something went wrong" and 
want me to logout, to get itself stuck in a loop..  I scanned dmesg and no 
squashfs errs, thought about filing then rebooted to see if it occurred again 
and nope.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1854621

Title:
  ubuntu 20.04 daily boots with no background, selecting other
  background has warped picture

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 daily - verified (check disc for defects) prior to boot.
  dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

  On booting, the 20.04 daily has no background when desktop is loaded?
  (ie. top panel is there, dock on left side on black screen)

  When changing background (to any already installed), they are warped
  when selected and made the bacground as if corrupted (but small image
  where selection is made looks valid).


  This issue may relate to video card  [radeon]

  ubuntu@ubuntu:~$ sudo lshw -C video
*-display:0   
 description: VGA compatible controller
 product: RV516 [Radeon X1300/X1550 Series]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:01:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:16 memory:d000-dfff memory:fe9e-fe9e 
ioport:dc00(size=256) memory:c-d
*-display:1 UNCLAIMED
 description: Display controller
 product: RV516 [Radeon X1300/X1550 Series] (Secondary)
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0.1
 bus info: pci@:01:00.1
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress bus_master cap_list
 configuration: latency=0
 resources: memory:fe9f-fe9f

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.440
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CasperVersion: 1.432
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  1 11:58:33 2019
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191128)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1854621/+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 1870725] Re: artifacts appearing on gnome shell

2020-04-03 Thread Ryan Hirasaki
No problem!

When I change wallpapers the issue appears goes away but on reboot or
switching back the issue persists. it appears to not affect other
applications such as Firefox even when in full screen.

-- 
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/1870725

Title:
  artifacts appearing on gnome shell

Status in ubuntu-meta package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  problems appear on the desktop and lock screen (not in gdm)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 22:50:55 2020
  DistUpgraded: 2020-04-03 20:26:10,751 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:225d]
  InstallationDate: Installed on 2020-03-30 (4 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: LENOVO 20L5CTO1WW
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=9aa1adb4-3c73-4d9b-8968-83630fb790f2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-04 (0 days ago)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K17763 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5CTO1WW
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+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/ubuntu-meta/+bug/1870725/+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 1870725] Re: artifacts appearing on gnome shell

2020-04-03 Thread Chris Guiver
Thank you for taking the time to report this issue and helping to make
Ubuntu better.

If you change wallpapers, does the issue still occur?  Does it occur if
you have windows fullscreen (eg. if firefox is your open window and
maximized so it covers your wallpaper, do you see the artifacts?) or are
they visible only on your wallpaper?

-- 
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/1870725

Title:
  artifacts appearing on gnome shell

Status in ubuntu-meta package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  problems appear on the desktop and lock screen (not in gdm)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 22:50:55 2020
  DistUpgraded: 2020-04-03 20:26:10,751 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:225d]
  InstallationDate: Installed on 2020-03-30 (4 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: LENOVO 20L5CTO1WW
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=9aa1adb4-3c73-4d9b-8968-83630fb790f2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-04 (0 days ago)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K17763 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5CTO1WW
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+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/ubuntu-meta/+bug/1870725/+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 1745418] Re: Screen tearing with AMD APU on Ubuntu 18.04 and 17.10

2020-04-03 Thread Launchpad Bug Tracker
[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mutter (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1745418

Title:
  Screen tearing with AMD APU on Ubuntu 18.04 and 17.10

Status in mesa package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  Hi,
  I have two PCs with AMD hardware: a desktop with AMD A10-7800 and a laptop 
with AMD A10-7300, so both with AMD Kaveri APUs.
  The operating system is Ubuntu 17.10 x64 both on the desktop and on the 
laptop.
  The good news is that the driver built into Ubuntu works fine. I hope I can 
improve yet but I am satisfied.
  The only problem occurs with the Opera browser: when I display something 
graphic, for example a video on YouTube or by scrolling the photos, it presents 
a lot of tearing. With Firefox this problem is not there.
  I have already reported this problem to Opera and AMD, but I do not think 
they have taken into account, because even the latest versions of Opera have 
screen tearing.
  I hope you can solve and work with AMD driver team and Opera because I would 
like to use that browser, thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1745418/+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 1745418] Re: Screen tearing with AMD APU on Ubuntu 18.04 and 17.10

2020-04-03 Thread Launchpad Bug Tracker
[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1745418

Title:
  Screen tearing with AMD APU on Ubuntu 18.04 and 17.10

Status in mesa package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  Hi,
  I have two PCs with AMD hardware: a desktop with AMD A10-7800 and a laptop 
with AMD A10-7300, so both with AMD Kaveri APUs.
  The operating system is Ubuntu 17.10 x64 both on the desktop and on the 
laptop.
  The good news is that the driver built into Ubuntu works fine. I hope I can 
improve yet but I am satisfied.
  The only problem occurs with the Opera browser: when I display something 
graphic, for example a video on YouTube or by scrolling the photos, it presents 
a lot of tearing. With Firefox this problem is not there.
  I have already reported this problem to Opera and AMD, but I do not think 
they have taken into account, because even the latest versions of Opera have 
screen tearing.
  I hope you can solve and work with AMD driver team and Opera because I would 
like to use that browser, thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1745418/+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 1870725] [NEW] artifacts appearing on gnome shell

2020-04-03 Thread Ryan Hirasaki
Public bug reported:

problems appear on the desktop and lock screen (not in gdm)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  3 22:50:55 2020
DistUpgraded: 2020-04-03 20:26:10,751 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:225d]
InstallationDate: Installed on 2020-03-30 (4 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
MachineType: LENOVO 20L5CTO1WW
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=9aa1adb4-3c73-4d9b-8968-83630fb790f2 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-04 (0 days ago)
dmi.bios.date: 02/19/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N24ET56W (1.31 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0K17763 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480
dmi.product.name: 20L5CTO1WW
dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
dmi.product.version: ThinkPad T480
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug corruption focal ubuntu

** Attachment added: "Screenshot from 2020-04-03 21-08-18.png"
   
https://bugs.launchpad.net/bugs/1870725/+attachment/5345966/+files/Screenshot%20from%202020-04-03%2021-08-18.png

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1870725

Title:
  artifacts appearing on gnome shell

Status in ubuntu-meta package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  problems appear on the desktop and lock screen (not in gdm)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 22:50:55 2020
  DistUpgraded: 2020-04-03 20:26:10,751 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:225d]
  InstallationDate: Installed on 2020-03-30 (4 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: LENOVO 20L5CTO1WW
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=9aa1adb4-3c73-4d9b-8968-83630fb790f2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-04 (0 days ago)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5CTO1WW
  dmi.board.vendor: 

[Touch-packages] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]

2020-04-03 Thread Phuc Minh Cai
Hi Hai Heng Feng,

How are you? Hope you're fine.

I saw it's already release kernel v5.6

Should I try with this kernel?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1860754

Title:
  ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to
  submit batchbuffer: Input/output error]

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't 
recognize graphic driver.
  - run udo apt-get install xserver-xorg-video-intel
  0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 14:29:01 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd]
  InstallationDate: Installed on 2020-01-24 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. T100HAN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T100HAN.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T100HAN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: T
  dmi.product.name: T100HAN
  dmi.product.sku: ASUS-TabletSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  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/linux/+bug/1860754/+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 1869629] Re: please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns

2020-04-03 Thread Launchpad Bug Tracker
This bug was fixed in the package apparmor - 2.13.3-7ubuntu3

---
apparmor (2.13.3-7ubuntu3) focal; urgency=medium

  * Add upstream-abstractions-add-etc-mdns.allow-to-etc-apparmor.d-ab.patch
(LP: #1869629)

 -- John Johansen   Wed, 01 Apr 2020
01:05:30 -0700

** Changed in: apparmor (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1869629

Title:
  please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns

Status in snapd:
  Triaged
Status in apparmor package in Ubuntu:
  Fix Released
Status in chrony package in Ubuntu:
  Invalid

Bug description:
  In focal users of mdns get denials in apparmor confined applications.
  An exampel can be found in the original bug below.

  It seems it is a common pattern, see
  https://github.com/lathiat/nss-mdns#etcmdnsallow

  Therefore I'm asking to add
 /etc/mdns.allow r,
  to the file
 /etc/apparmor.d/abstractions/mdns"
  by default.

  --- original bug ---

  Many repetitions of

  audit: type=1400 audit(1585517168.705:63): apparmor="DENIED"
  operation="open" profile="/usr/sbin/chronyd" name="/etc/mdns.allow"
  pid=1983815 comm="chronyd" requested_mask="r" denied_mask="r"
  fsuid=123 ouid=0

  in log.  I use libnss-mdns for .local name resolution, so
  /etc/nsswitch.conf contains

  hosts:  files mdns [NOTFOUND=return] myhostname dns

  and /etc/mnds.allow contains the domains to resolve with mDNS (in may
  case, "local." and "local"; see /usr/share/doc/libnss-
  mdns/README.html.)

  Presumably cronyd calls a gethostbyX() somewhere, thus eventually
  trickling down through the name service switch and opening
  /etc/mdns.allow, which the AppArmor profile in the chrony package does
  not allow.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: chrony 3.5-6ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  Date: Sun Mar 29 15:02:39 2020
  InstallationDate: Installed on 2020-03-26 (3 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200326)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: chrony
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1869629/+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 1854621] Re: ubuntu 20.04 daily boots with no background, selecting other background has warped picture

2020-04-03 Thread Chris Guiver
Reboot of same box as #6; same ISO.

I have wallpaper visible this time, but tiny glitches visible at the top
in what could be top-panel or wallpaper.  As mostly dark it looks like
glitch is with top-panel, but if I make this firefox window full screen
the glitch is hidden thus part of wallpaper most likely

Screengrab uploaded of what I'm seeing this time.

To ensure screengrab showed issue, I viewed it in eye-of-gnome; I'm
getting glitches on the screen as I press  in eye-of-gnome to view
fullscreen; most (if not all) on screen glitches are occuring at top of
screen or top-panel, but that could be where easy to notice them..  It's
not just that program as I get same on screen glitches with firefox now.

** Attachment added: "Screenshot from 2020-04-04 02-02-32.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1854621/+attachment/5345959/+files/Screenshot%20from%202020-04-04%2002-02-32.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1854621

Title:
  ubuntu 20.04 daily boots with no background, selecting other
  background has warped picture

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 daily - verified (check disc for defects) prior to boot.
  dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

  On booting, the 20.04 daily has no background when desktop is loaded?
  (ie. top panel is there, dock on left side on black screen)

  When changing background (to any already installed), they are warped
  when selected and made the bacground as if corrupted (but small image
  where selection is made looks valid).


  This issue may relate to video card  [radeon]

  ubuntu@ubuntu:~$ sudo lshw -C video
*-display:0   
 description: VGA compatible controller
 product: RV516 [Radeon X1300/X1550 Series]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:01:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:16 memory:d000-dfff memory:fe9e-fe9e 
ioport:dc00(size=256) memory:c-d
*-display:1 UNCLAIMED
 description: Display controller
 product: RV516 [Radeon X1300/X1550 Series] (Secondary)
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0.1
 bus info: pci@:01:00.1
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress bus_master cap_list
 configuration: latency=0
 resources: memory:fe9f-fe9f

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.440
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CasperVersion: 1.432
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  1 11:58:33 2019
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191128)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1854621/+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 1854621] Re: ubuntu 20.04 daily boots with no background, selecting other background has warped picture

2020-04-03 Thread Chris Guiver
Changing wallpapers and on occasion the wallpaper would show correctly,
change it again sometimes it could get two change twice in a row without
glitches, then back to jarry-blocky mess for part of image on next
change (and usually 3-5 after that).

See #4 for pic; though % of jarry-block image and location varies, up to
80% of screen jarry-blocky but not always top of screen; can be lower
portion, or top & bottom but not middle... it's not consistent though
more commonly not right at top

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1854621

Title:
  ubuntu 20.04 daily boots with no background, selecting other
  background has warped picture

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 daily - verified (check disc for defects) prior to boot.
  dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

  On booting, the 20.04 daily has no background when desktop is loaded?
  (ie. top panel is there, dock on left side on black screen)

  When changing background (to any already installed), they are warped
  when selected and made the bacground as if corrupted (but small image
  where selection is made looks valid).


  This issue may relate to video card  [radeon]

  ubuntu@ubuntu:~$ sudo lshw -C video
*-display:0   
 description: VGA compatible controller
 product: RV516 [Radeon X1300/X1550 Series]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:01:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:16 memory:d000-dfff memory:fe9e-fe9e 
ioport:dc00(size=256) memory:c-d
*-display:1 UNCLAIMED
 description: Display controller
 product: RV516 [Radeon X1300/X1550 Series] (Secondary)
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0.1
 bus info: pci@:01:00.1
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress bus_master cap_list
 configuration: latency=0
 resources: memory:fe9f-fe9f

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.440
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CasperVersion: 1.432
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  1 11:58:33 2019
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191128)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1854621/+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 1854621] Re: ubuntu 20.04 daily boots with no background, selecting other background has warped picture

2020-04-03 Thread Chris Guiver
Sorry

Booted latest daily (03-Apr-2020) 'live' qa-test and on 
dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

and whilst I like the 'smooth' bootup messages, it ends up booting to a
black screen without wallpaper (wallpapers was visible in background
during try/boot, and changing wallpapers/backgrounds has the same effect
as described so I won't add another screendump (see comment #4 for what
my current screen looks like)

I just noticed I have another box with the same `lshw` reported video
card so I'll endeavour to use the 'live' on that & other similar boxes
later today.

** Changed in: ubuntu-meta (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1854621

Title:
  ubuntu 20.04 daily boots with no background, selecting other
  background has warped picture

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 daily - verified (check disc for defects) prior to boot.
  dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

  On booting, the 20.04 daily has no background when desktop is loaded?
  (ie. top panel is there, dock on left side on black screen)

  When changing background (to any already installed), they are warped
  when selected and made the bacground as if corrupted (but small image
  where selection is made looks valid).


  This issue may relate to video card  [radeon]

  ubuntu@ubuntu:~$ sudo lshw -C video
*-display:0   
 description: VGA compatible controller
 product: RV516 [Radeon X1300/X1550 Series]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:01:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:16 memory:d000-dfff memory:fe9e-fe9e 
ioport:dc00(size=256) memory:c-d
*-display:1 UNCLAIMED
 description: Display controller
 product: RV516 [Radeon X1300/X1550 Series] (Secondary)
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0.1
 bus info: pci@:01:00.1
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress bus_master cap_list
 configuration: latency=0
 resources: memory:fe9f-fe9f

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.440
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CasperVersion: 1.432
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  1 11:58:33 2019
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191128)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1854621/+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 1870550] Re: PCI/internal sound card not detected

2020-04-03 Thread Hui Wang
https://people.canonical.com/~hwang4/testdsp/ please test this kernel.
if it doesn't help. please upload a dmesg with that kernel.

-- 
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/1870550

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The sound card is not detected on my machine

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 00:51:33 2020
  InstallationDate: Installed on 2020-02-25 (37 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FA
  dmi.board.vendor: HP
  dmi.board.version: 87.46
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd03/02/2020:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.46:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
  dmi.product.sku: 8UR41PA#ABG
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870550/+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 1870637] Re: 20.04beta: Cannot set 3840x2160

2020-04-03 Thread Ubuntu Foundations Team Bug Bot
** 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/1870637

Title:
  20.04beta: Cannot set 3840x2160

Status in xorg package in Ubuntu:
  New

Bug description:
  When i do get it to work, on reboot it'll be back to fullhd.
  this happens on nvidia 440, 435 and 390.

  On X.Org X server it does work.

  Graphics card: nVidia GT1030
  Amp: Onkyo TX-NR646

  On 19.10 there are no problems.
  A couple of weeks ago i tested a daily build and there were no troubles also, 
so this is new.

  My favourite setting: 3840x2160 200% 60hz.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..10.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:10:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 01:02:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:2476]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=99bd1cce-b30c-44fb-8ead-90317474c33f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 (MS-7B84)
  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.:bvr2.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  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.7-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+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/1870637/+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 1870638] Re: When taskbar is set to bottom icons cannot be re-arranged

2020-04-03 Thread Ubuntu Foundations Team Bug Bot
** 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/1870638

Title:
  When taskbar is set to bottom icons cannot be re-arranged

Status in xorg package in Ubuntu:
  New

Bug description:
  When taskbar is set to bottom icons cannot be re-arranged
  When taskbar is set to the left of the screen icons can be re-arranged

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 01:23:38 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:2476]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=99bd1cce-b30c-44fb-8ead-90317474c33f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 (MS-7B84)
  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.:bvr2.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+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/1870638/+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 1870638] [NEW] When taskbar is set to bottom icons cannot be re-arranged

2020-04-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When taskbar is set to bottom icons cannot be re-arranged
When taskbar is set to the left of the screen icons can be re-arranged

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  4 01:23:38 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] [19da:2476]
InstallationDate: Installed on 2020-04-03 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: Micro-Star International Co., Ltd. MS-7B84
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=99bd1cce-b30c-44fb-8ead-90317474c33f ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/03/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.D0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450M PRO-M2 (MS-7B84)
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.:bvr2.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B84
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+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 focal ubuntu
-- 
When taskbar is set to bottom icons cannot be re-arranged
https://bugs.launchpad.net/bugs/1870638
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 1870637] [NEW] 20.04beta: Cannot set 3840x2160

2020-04-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When i do get it to work, on reboot it'll be back to fullhd.
this happens on nvidia 440, 435 and 390.

On X.Org X server it does work.

Graphics card: nVidia GT1030
Amp: Onkyo TX-NR646

On 19.10 there are no problems.
A couple of weeks ago i tested a daily build and there were no troubles also, 
so this is new.

My favourite setting: 3840x2160 200% 60hz.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..10.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:10:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  4 01:02:09 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 435.21, 5.4.0-21-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] [19da:2476]
InstallationDate: Installed on 2020-04-03 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: Micro-Star International Co., Ltd. MS-7B84
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=99bd1cce-b30c-44fb-8ead-90317474c33f ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/03/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.D0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450M PRO-M2 (MS-7B84)
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.:bvr2.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B84
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
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.7-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+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 focal resolution ubuntu
-- 
20.04beta: Cannot set 3840x2160   
https://bugs.launchpad.net/bugs/1870637
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 1866611] Re: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6

2020-04-03 Thread Brian Murray
** Tags added: focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1866611

Title:
  OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  After upgrading openssl on my Focal-install this morning (upgrade
  openssl:amd64 1.1.1d-2ubuntu3 1.1.1d-2ubuntu6 per /var/log/dpkg.log),
  my OpenVPN tunnel refuses to connect to our corporate VPN (from
  /var/log/syslog):

  corp-laptop nm-openvpn[4688]: VERIFY ERROR: depth=0, error=CA signature 
digest algorithm too weak: C=DK, ST=None, L=Copenhagen, O=XX, OU=XX, CN=XX, 
emailAddress=XX
  corp-laptop nm-openvpn[4688]: OpenSSL: error:1416F086:SSL 
routines:tls_process_server_certificate:certificate verify failed

  I'm told we're running a SHA1-signed CA, which we're guessing has been
  deprecated somewhere between -2ubuntu3 and -2ubuntu6. The changelog
  for -2ubuntu4 mentions importing some upstream changes, but isn't more
  specific than that:
  https://changelogs.ubuntu.com/changelogs/pool/main/o/openssl/openssl_1.1
  .1d-2ubuntu4/changelog

  As a work-around, the internet suggests two work-arounds (neither of
  which has worked for me):

  1) Adding the following to /etc/defaults/openssl:

  OPTARGS="--tls-cipher DEFAULT:@SECLEVEL=0"

  2) Adding the following to /etc/ssl/openssl.conf:

  CipherString= :@SECLEVEL=1

  I also tried rolling back the package, but the old version doesn't
  seem to be available:

  $ sudo apt install openssl=1.1.1d-2ubuntu3
  ...
  E: Version '1.1.1d-2ubuntu3' for 'openssl' was not found

  
  I am no SSL-expert and would appreciate any pointers to get around this. (Our 
network-dept. does not have the bandwidth to roll over our CA on short notice, 
so I will need some other way to move ahead).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1866611/+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 1869484] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

2020-04-03 Thread Gunnar Hjalmarsson
On 2020-04-03 21:52, Michael wrote:
> Was a mistake, miss-clicked and wouldn't let me revert. sorry!

N.p., thanks for explaining.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1869484

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  i don't know what's happened

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 27 23:00:56 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2018-08-07 (598 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1869484/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-04-03 Thread Rick
20.04 beta still has this issue for 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/1845801

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  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.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  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.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  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/gdm3/+bug/1845801/+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 1870200] Re: FTBFS please drop python build-dep, or change it to python2

2020-04-03 Thread Sebastien Bacher
** Changed in: indicator-power (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: indicator-power (Ubuntu)
 Assignee: Sebastien Bacher (seb128) => Dimitri John Ledkov (xnox)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1870200

Title:
  FTBFS please drop python build-dep, or change it to python2

Status in indicator-power package in Ubuntu:
  Fix Released

Bug description:
  FTBFS please drop python build-dep, or change it to python2

  not uploading this package, as my previous upload has been reverted in
  the past.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1870200/+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 1870617] Re: Merge fontconfig 2.13.1-3 (main) from Debian unstable (main)

2020-04-03 Thread Sebastien Bacher
** Changed in: fontconfig (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1870617

Title:
  Merge fontconfig 2.13.1-3 (main) from Debian unstable (main)

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Please merge fontconfig 2.13.1-3 (main) from Debian unstable (main)

  Sorry, I can't work on this merge myself.
  It fixes Debian bugs, and they can be related to Ubuntu too.

  Explanation of the Ubuntu delta:
* Really include the symbols file update
* debian/patches/04_ubuntu_monospace_lcd_filter_conf.patch:
  - updated the 53-monospace-lcd-filter.conf syntax to avoid warnings
which make autopkgtests fail
* Upload proposed patch from upstream bug #103652. If the fontconfig cache
  was built on a system that has nanosecond timestamps and then later
  transplanted to one that doesn't - for example by mksquashfs as part of a
  live CD build - we consider the cache invalid and rebuild it during the
  boot process. Depending on the fonts involved, this can take a significant
  amount of time and potentially cause knock-on timeouts. The approach in
  this patch is to ignore the nanosecond portion of the cache's value if we
  get 0 when stat()ing the referenced directory, meaning it is considered
  fresh if the rest of the timestamp matches. (LP: #1749546)
* Merge with Debian (LP: #1638959, LP: #1702544). Remaining changes:
  - debian/source_fontconfig.py, debian/fontconfig.install:
+ Install apport hook
  - Add 03_prefer_dejavu.patch:
+ Prefer DejaVu to Bitstream Vera
  - Add 04_ubuntu_monospace_lcd_filter_conf.patch:
+ Use legacy lcdfilter with smaller monospace fonts
  - Add 05_ubuntu_add_antialiasing_confs.patch:
+ Add config file for antialiasing
  - Add 05_lcdfilterlegacy.patch: Recognize const value "lcdfilterlegacy",
used in Ubuntu before upstream introduced "lcdlegacy"
  - Add 07_no_bitmaps.patch:
+ Install 70-no-bitmaps.conf
  - Drop debian/fontconfig.NEWS, debian/fontconfig-config.templates,
debian/fontconfig-config.config, and associatedpo files.
Modify debian/rules, debian/fontconfig-config.postinst,
debian/fontconfig-config.postrm, and debian/README.Debian.
+ Don't provide debconf prompts
  - Modify debian/rules, debian/fontconfig-config.install,
debian/fontconfig-config.links, debian/fontconfig-config.postrm,
and debian/fontconfig-udeb.install:
+ Delay doing the transition from /etc to /usr
* New upstream release
* Refresh patches
* Update Ubuntu patches to use mode="append" and target="pattern"
  (LP: #1192175)
* Drop patches applied in new release:
  - 01_fonts_nanum.patch
  - 03_locale_c.utf8.patch
  - 06_cross.patch
  - CVE-2016-5384.patch

  Changelog entries since current focal version 2.13.1-2ubuntu2:

  fontconfig (2.13.1-3) unstable; urgency=medium

[ Laurent Bigonville ]
* debian/rules: Stop looking for fonts in /usr/X11R6/lib/X11/fonts, nothing
  is installing fonts there for years and it's causing gnome-settings-daemon
  to check the location every few seconds (Closes: #568686)

[ Fabian Greffrath ]
* fontconfig-config: extend, clean-up and order fontconfig-config's
  font dependencies (Closes: #879503)

[ Emilio Pozuelo Monfort ]
* Split documentation into a -doc package to avoid multi-arch problems in
  the -dev one (Closes: #935760, #844607)
* Since we're going through NEW, rename libfontconfig1-dev to
  libfontconfig-dev and provide the former.
* Switch to debhelper-compat.

   -- Emilio Pozuelo Monfort   Wed, 18 Mar 2020
  00:56:46 +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1870617/+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 1870617] [NEW] Merge fontconfig 2.13.1-3 (main) from Debian unstable (main)

2020-04-03 Thread Amr Ibrahim
Public bug reported:

Please merge fontconfig 2.13.1-3 (main) from Debian unstable (main)

Sorry, I can't work on this merge myself.
It fixes Debian bugs, and they can be related to Ubuntu too.

Explanation of the Ubuntu delta:
  * Really include the symbols file update
  * debian/patches/04_ubuntu_monospace_lcd_filter_conf.patch:
- updated the 53-monospace-lcd-filter.conf syntax to avoid warnings
  which make autopkgtests fail
  * Upload proposed patch from upstream bug #103652. If the fontconfig cache
was built on a system that has nanosecond timestamps and then later
transplanted to one that doesn't - for example by mksquashfs as part of a
live CD build - we consider the cache invalid and rebuild it during the
boot process. Depending on the fonts involved, this can take a significant
amount of time and potentially cause knock-on timeouts. The approach in
this patch is to ignore the nanosecond portion of the cache's value if we
get 0 when stat()ing the referenced directory, meaning it is considered
fresh if the rest of the timestamp matches. (LP: #1749546)
  * Merge with Debian (LP: #1638959, LP: #1702544). Remaining changes:
- debian/source_fontconfig.py, debian/fontconfig.install:
  + Install apport hook
- Add 03_prefer_dejavu.patch:
  + Prefer DejaVu to Bitstream Vera
- Add 04_ubuntu_monospace_lcd_filter_conf.patch:
  + Use legacy lcdfilter with smaller monospace fonts
- Add 05_ubuntu_add_antialiasing_confs.patch:
  + Add config file for antialiasing
- Add 05_lcdfilterlegacy.patch: Recognize const value "lcdfilterlegacy",
  used in Ubuntu before upstream introduced "lcdlegacy"
- Add 07_no_bitmaps.patch:
  + Install 70-no-bitmaps.conf
- Drop debian/fontconfig.NEWS, debian/fontconfig-config.templates,
  debian/fontconfig-config.config, and associatedpo files.
  Modify debian/rules, debian/fontconfig-config.postinst,
  debian/fontconfig-config.postrm, and debian/README.Debian.
  + Don't provide debconf prompts
- Modify debian/rules, debian/fontconfig-config.install,
  debian/fontconfig-config.links, debian/fontconfig-config.postrm,
  and debian/fontconfig-udeb.install:
  + Delay doing the transition from /etc to /usr
  * New upstream release
  * Refresh patches
  * Update Ubuntu patches to use mode="append" and target="pattern"
(LP: #1192175)
  * Drop patches applied in new release:
- 01_fonts_nanum.patch
- 03_locale_c.utf8.patch
- 06_cross.patch
- CVE-2016-5384.patch

Changelog entries since current focal version 2.13.1-2ubuntu2:

fontconfig (2.13.1-3) unstable; urgency=medium

  [ Laurent Bigonville ]
  * debian/rules: Stop looking for fonts in /usr/X11R6/lib/X11/fonts, nothing
is installing fonts there for years and it's causing gnome-settings-daemon
to check the location every few seconds (Closes: #568686)

  [ Fabian Greffrath ]
  * fontconfig-config: extend, clean-up and order fontconfig-config's
font dependencies (Closes: #879503)

  [ Emilio Pozuelo Monfort ]
  * Split documentation into a -doc package to avoid multi-arch problems in
the -dev one (Closes: #935760, #844607)
  * Since we're going through NEW, rename libfontconfig1-dev to
libfontconfig-dev and provide the former.
  * Switch to debhelper-compat.

 -- Emilio Pozuelo Monfort   Wed, 18 Mar 2020 00:56:46
+0100

** Affects: fontconfig (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1870617

Title:
  Merge fontconfig 2.13.1-3 (main) from Debian unstable (main)

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Please merge fontconfig 2.13.1-3 (main) from Debian unstable (main)

  Sorry, I can't work on this merge myself.
  It fixes Debian bugs, and they can be related to Ubuntu too.

  Explanation of the Ubuntu delta:
* Really include the symbols file update
* debian/patches/04_ubuntu_monospace_lcd_filter_conf.patch:
  - updated the 53-monospace-lcd-filter.conf syntax to avoid warnings
which make autopkgtests fail
* Upload proposed patch from upstream bug #103652. If the fontconfig cache
  was built on a system that has nanosecond timestamps and then later
  transplanted to one that doesn't - for example by mksquashfs as part of a
  live CD build - we consider the cache invalid and rebuild it during the
  boot process. Depending on the fonts involved, this can take a significant
  amount of time and potentially cause knock-on timeouts. The approach in
  this patch is to ignore the nanosecond portion of the cache's value if we
  get 0 when stat()ing the referenced directory, meaning it is considered
  fresh if the rest of the timestamp matches. (LP: #1749546)
* Merge with Debian (LP: #1638959, LP: #1702544). Remaining 

[Touch-packages] [Bug 1870442] NetworkManager.conf.txt

2020-04-03 Thread Seija Kijin
apport information

** Attachment added: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1870442/+attachment/5345844/+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/1870442

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   

[Touch-packages] [Bug 1870442] RfKill.txt

2020-04-03 Thread Seija Kijin
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1870442/+attachment/5345847/+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/1870442

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL

[Touch-packages] [Bug 1870442] NetDevice.wlp2s0.txt

2020-04-03 Thread Seija Kijin
apport information

** Attachment added: "NetDevice.wlp2s0.txt"
   
https://bugs.launchpad.net/bugs/1870442/+attachment/5345843/+files/NetDevice.wlp2s0.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/1870442

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL  

[Touch-packages] [Bug 1870615] [NEW] Wi-Fi fails to connect to my network even when I enter the correct password, until I turn on Airplane Mode and then turn it off.

2020-04-03 Thread Seija Kijin
Public bug reported:

This happens often, but not always, when I boot Ubuntu on my Dell
Inspiron 5570.

Ubuntu 18.04.4

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2ubuntu1.2
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CasperVersion: 1.394.3
Date: Fri Apr  3 20:05:04 2020
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp2s0 scope link metric 1000 
 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE  TIMESTAMP  
 TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE 
 NETGEAR18   39a9b5bc-fd79-40c0-bf5d-7a1eb39843a7  wifi  1585944263 
 Fri Apr  3 20:04:23 2020  yes  0 no
/org/freedesktop/NetworkManager/Settings/2  yes wlp2s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/3  --
 Wired connection 1  abfe1401-bc06-3a2f-b8ad-f79ba4b50d75  ethernet  1585944168 
 Fri Apr  3 20:02:48 2020  yes  4294966297no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --   
   --
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   39a9b5bc-fd79-40c0-bf5d-7a1eb39843a7  
/org/freedesktop/NetworkManager/ActiveConnection/3 
 enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  --   
   ---- 

 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  --   
   ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

** Attachment added: "journalctl.log"
   
https://bugs.launchpad.net/bugs/1870615/+attachment/5345803/+files/journalctl.log

-- 
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/1870615

Title:
  Wi-Fi fails to connect to my network even when I enter the correct
  password, until I turn on Airplane Mode and then turn it off.

Status in network-manager package in Ubuntu:
  New

Bug description:
  This happens often, but not always, when I boot Ubuntu on my Dell
  Inspiron 5570.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.2
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-28-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  Date: Fri Apr  3 20:05:04 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   39a9b5bc-fd79-40c0-bf5d-7a1eb39843a7  wifi  
1585944263  Fri Apr  3 20:04:23 2020  

[Touch-packages] [Bug 1870442] CRDA.txt

2020-04-03 Thread Seija Kijin
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1870442/+attachment/5345837/+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/1870442

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  

[Touch-packages] [Bug 1870442] PciNetwork.txt

2020-04-03 Thread Seija Kijin
apport information

** Attachment added: "PciNetwork.txt"
   
https://bugs.launchpad.net/bugs/1870442/+attachment/5345845/+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/1870442

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL

[Touch-packages] [Bug 1870442] WifiSyslog.txt

2020-04-03 Thread Seija Kijin
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1870442/+attachment/5345848/+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/1870442

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL

[Touch-packages] [Bug 1870442] ProcCpuinfoMinimal.txt

2020-04-03 Thread Seija Kijin
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1870442/+attachment/5345846/+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/1870442

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   

[Touch-packages] [Bug 1870442] IwConfig.txt

2020-04-03 Thread Seija Kijin
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1870442/+attachment/5345840/+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/1870442

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL

[Touch-packages] [Bug 1870442] Re: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on.

2020-04-03 Thread Seija Kijin
** Attachment added: "journalctl.log"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870442/+attachment/5345816/+files/journalctl.log

** Tags added: apport-collected

** Description changed:

  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on my
  PC for a brief second before disabling airplane mode and reenabling Wi-
  Fi.
  
  Ubuntu 18.04.4
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.9
+ Architecture: amd64
+ CasperVersion: 1.394.3
+ DistroRelease: Ubuntu 18.04
+ IfupdownConfig:
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
+ IpRoute:
+  default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
+  169.254.0.0/16 dev wlp2s0 scope link metric 1000 
+  192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
+ LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
+ NetworkManager.state:
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=true
+  WWANEnabled=true
+ Package: network-manager 1.10.6-2ubuntu1.2
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=C.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
+ Tags:  bionic
+ Uname: Linux 5.3.0-28-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ nmcli-con:
+  NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
+  NETGEAR18   39a9b5bc-fd79-40c0-bf5d-7a1eb39843a7  wifi  
1585944468  Fri Apr  3 20:07:48 2020  yes  0

[Touch-packages] [Bug 1870442] NetDevice.enp1s0.txt

2020-04-03 Thread Seija Kijin
apport information

** Attachment added: "NetDevice.enp1s0.txt"
   
https://bugs.launchpad.net/bugs/1870442/+attachment/5345841/+files/NetDevice.enp1s0.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/1870442

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL  

[Touch-packages] [Bug 1870442] Dependencies.txt

2020-04-03 Thread Seija Kijin
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1870442/+attachment/5345838/+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/1870442

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL  

[Touch-packages] [Bug 1870442] NetDevice.lo.txt

2020-04-03 Thread Seija Kijin
apport information

** Attachment added: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/bugs/1870442/+attachment/5345842/+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/1870442

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL  

[Touch-packages] [Bug 1870442] IpAddr.txt

2020-04-03 Thread Seija Kijin
apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1870442/+attachment/5345839/+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/1870442

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL

[Touch-packages] [Bug 1869484] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

2020-04-03 Thread Michael
Was a mistake, miss-clicked and wouldn't let me revert. sorry!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1869484

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  i don't know what's happened

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 27 23:00:56 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2018-08-07 (598 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1869484/+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 1870410] Re: wireless does not work on boot on RPi 3s

2020-04-03 Thread Brian Murray
Well I'm seeing a different failure with the systemd from the PPA.

Apr  3 19:47:53 ubuntu systemd-networkd[1112]: wlan0: Link UP
Apr  3 19:47:53 ubuntu systemd-networkd[1112]: wlan0: Gained carrier
Apr  3 19:47:53 ubuntu systemd-networkd[1112]: wlan0: Connected WiFi access 
point: javelin7 (50:c7:bf:15:c0:93)
Apr  3 19:47:53 ubuntu systemd-networkd[1112]: wlan0: Re-configuring with 
/run/systemd/network/10-netplan-wlan0.network
Apr  3 19:47:53 ubuntu systemd-networkd[1112]: wlan0: IPv6 successfully enabled
Apr  3 19:47:53 ubuntu systemd-networkd[1112]: wlan0: IPv6 successfully enabled
Apr  3 19:47:53 ubuntu systemd-networkd[1112]: wlan0: DHCP4 CLIENT: Failed to 
set request flag for MTU: File exists
Apr  3 19:47:53 ubuntu systemd-networkd[1112]: wlan0: Failed

ubuntu@ubuntu:~$ apt-cache policy systemd
systemd:
  Installed: 245.4-2~ubuntu1~rbalint1

-- 
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/1870410

Title:
  wireless does not work on boot on RPi 3s

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  I've setup a wireless config in /etc/netplan/config.yaml and it does
  not activate on boot. I have to run 'sudo netplan apply' to get my
  wireless connected. This works fine on an RPi4 but not an RPi3B.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: User Name 5.4.0-1006.6-raspi2 5.4.24
  Uname: Linux 5.4.0-1006-raspi2 armv7l
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: armhf
  Date: Thu Apr  2 19:02:27 2020
  Lspci:
   
  Lsusb:
   Bus 001 Device 007: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) 
SMSC9512/9514 Fast Ethernet Adapter
   Bus 001 Device 006: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) 
SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
   |__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/5p, 480M
   |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, 
Driver=smsc95xx, 480M
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 
bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:FF:6B:0F 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870410/+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 1869484] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

2020-04-03 Thread Gunnar Hjalmarsson
@Michael: Why did you close the bug with "Fix Released" without
justification?

** Changed in: ibus (Ubuntu)
   Status: Fix Released => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1869484

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  i don't know what's happened

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 27 23:00:56 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2018-08-07 (598 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1869484/+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 1870560] Re: Client does not renew IP after RADIUS COA disconnect

2020-04-03 Thread asylum
Thanks Brian!

-- 
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/1870560

Title:
  Client does not renew IP after RADIUS COA disconnect

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have been testing RADIUS change of authorization on Ubiquiti
  wireless.  I have tested this on Ubuntu 19.04 as well as Ubuntu 19.10
  and the behavior is the same on both as well as when testing on Debian
  or Fedora.  FWIW this is working with a Windows 10 or Android client
  connected to the same wireless SSID on the same wireless AP, so this
  does not seem to be a configuration issue on the AP from what I can
  see.  Below are the logs from the Ubuntu client as well as the RADIUS
  server.  Please let me know if any further info is needed or if this
  behavior is expected.  Log info is below.  Thanks!

  
  ubuntu@ubuntu:/var/log$ journalctl | grep -Ei 'dhcp'
  Mar 26 21:28:30 ubuntu NetworkManager[1127]:   [1585258110.5810] 
dhcp-init: Using DHCP client 'dhclient'

  Client sends an Access-Request to RADIUS server:

  Thu Mar 26 17:29:13 2020
  Packet-Type = Access-Request
  User-Name = "dshields"
  NAS-Identifier = "7483c28d26de"
  Called-Station-Id = "74-83-C2-8D-26-DE:DF-Ubiquiti-Test"
  NAS-Port-Type = Wireless-802.11
  Service-Type = Framed-User
  Calling-Station-Id = "38-59-F9-81-5C-98"
  Connect-Info = "CONNECT 0Mbps 802.11b"
  Acct-Session-Id = "ABB4DA79B50051CB"
  WLAN-Pairwise-Cipher = 1027076
  WLAN-Group-Cipher = 1027076
  WLAN-AKM-Suite = 1027073
  Framed-MTU = 1400
  EAP-Message = 0x022900061500
  State = 0x4cc366d24aea73b029eb30b6d6318ffc
  Message-Authenticator = 0x48aef4abde67bc109ce1689d34b292cb
  NAS-IP-Address = 10.100.10.235

  Thu Mar 26 17:29:13 2020
  Packet-Type = Access-Request
  User-Name = "dshields"
  NAS-Identifier = "7483c28d26de"
  Called-Station-Id = "74-83-C2-8D-26-DE:DF-Ubiquiti-Test"
  NAS-Port-Type = Wireless-802.11
  Service-Type = Framed-User
  Calling-Station-Id = "38-59-F9-81-5C-98"
  Connect-Info = "CONNECT 0Mbps 802.11b"
  Acct-Session-Id = "ABB4DA79B50051CB"
  WLAN-Pairwise-Cipher = 1027076
  WLAN-Group-Cipher = 1027076
  WLAN-AKM-Suite = 1027073
  Framed-MTU = 1400
  EAP-Message = 
0x022a00841500160303004610424104bbae17c4fd4f2c594c2fe9737cc7919914adc728c0c3080fcf9e0f4cec1e1baced618159446d056286c8ca54ab8eb9142a2b1cfd5c88e110e6a28edf4ce943ed1403030001011603030028c00e45cebb1752d0b5c6323f47be852483a27af729b82ee96e3139d24dfa485e8ffed35de2438d54
  State = 0x4cc366d24be973b029eb30b6d6318ffc
  Message-Authenticator = 0x5d0f1396a39e5b0e1e1a0c6118e1ebea
  NAS-IP-Address = 10.100.10.235

  Authentication succeeds and VLAN 230 is returned to client with Access-Accept:

  Thu Mar 26 17:29:13 2020 : Auth: Login OK: [dshields] (from client 
OPSWAT-AP-AC-PRO port 0 via TLS tunnel)
  Thu Mar 26 17:29:13 2020 : Auth: Login OK: [dshields] (from client 
OPSWAT-AP-AC-PRO port 0 cli 38-59-F9-81-5C-98)

  Thu Mar 26 17:29:13 2020
  Packet-Type = Access-Accept
  User-Name = "dshields"
  MS-MPPE-Recv-Key = 
0x0e4b4cd48f891763a1f1792c71047066b1fd70914f7212cf011f1a367277cd02
  MS-MPPE-Send-Key = 
0xc81a04f1482a75cff7cac78876a95391ab9908d613dd2e2476def943bab5cf4c
  EAP-MSK = 
0x0e4b4cd48f891763a1f1792c71047066b1fd70914f7212cf011f1a367277cd02c81a04f1482a75cff7cac78876a95391ab9908d613dd2e2476def943bab5cf4c
  EAP-EMSK = 
0x55d0a72ab01bd0a5ec49a6e081fcecff37357ba89f8c25767d8033e529e45b116a9cec3044cef37c20297c60b8b3b345be1248859214586ad9e925545cf88c14
  EAP-Session-Id = 
0x15066089550d45a92a0c53f9280e765fbdcf813480da08fdbf5b33de44dd5dc9c15e7d1ea91e31c2135dd3b384f8d628548ab4beb299a79ee60836464d78cfcce5
  EAP-Message = 0x032b0004
  Message-Authenticator = 0x
  Calling-Station-Id = "38-59-F9-81-5C-98"
  Tunnel-Type:0 += VLAN
  Tunnel-Medium-Type:0 += IEEE-802
  Tunnel-Private-Group-Id:0 += "230"

  Laptop sends a DHCP request and gets an IP in VLAN 230:

  Mar 26 21:29:13 ubuntu NetworkManager[1127]:   [1585258153.1150] dhcp4 
(wlp2s0b1): activation: beginning transaction (timeout in 45 seconds)
  Mar 26 21:29:13 ubuntu NetworkManager[1127]:   [1585258153.1352] dhcp4 
(wlp2s0b1): dhclient started with pid 2626
  Mar 26 21:29:13 ubuntu dhclient[2626]: DHCPDISCOVER on wlp2s0b1 to 
255.255.255.255 port 67 interval 3 (xid=0x6bec8061)
  Mar 26 21:29:13 ubuntu dhclient[2626]: DHCPOFFER of 10.103.230.59 from 
10.103.230.1
  Mar 26 21:29:13 ubuntu dhclient[2626]: DHCPREQUEST for 10.103.230.59 on 
wlp2s0b1 to 255.255.255.255 port 

[Touch-packages] [Bug 1870607] Re: After installing Ubuntu 20.04 alongside 19.10, initramfs no longer is able to extract from either OSes when I boot them.

2020-04-03 Thread Seija Kijin
** Attachment added: "my initrd.img"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1870607/+attachment/5345796/+files/initrd.img

-- 
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/1870607

Title:
  After installing Ubuntu 20.04 alongside 19.10, initramfs no longer is
  able to extract from either OSes when I boot them.

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  After installing Ubuntu 20.04, initramfs no longer can extract from
  either 20.04 OR 19.10. However, the initramfs should work AT LEAST on
  20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: initramfs-tools-core 0.133ubuntu10
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  Date: Fri Apr  3 15:33:36 2020
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1870607/+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 1870607] [NEW] After installing Ubuntu 20.04 alongside 19.10, initramfs no longer is able to extract from either OSes when I boot them.

2020-04-03 Thread Seija Kijin
Public bug reported:

After installing Ubuntu 20.04, initramfs no longer can extract from
either 20.04 OR 19.10. However, the initramfs should work AT LEAST on
20.04.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: initramfs-tools-core 0.133ubuntu10
ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
Uname: Linux 5.3.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
Date: Fri Apr  3 15:33:36 2020
InstallationDate: Installed on 2020-04-03 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

-- 
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/1870607

Title:
  After installing Ubuntu 20.04 alongside 19.10, initramfs no longer is
  able to extract from either OSes when I boot them.

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  After installing Ubuntu 20.04, initramfs no longer can extract from
  either 20.04 OR 19.10. However, the initramfs should work AT LEAST on
  20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: initramfs-tools-core 0.133ubuntu10
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  Date: Fri Apr  3 15:33:36 2020
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1870607/+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 1869484] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

2020-04-03 Thread Michael
Had this happen to me as well. Ill try and reproduce but not sure that
will happen. For me i logged out of a session then logged back in and
clicked on "software update" and got the error.

** Changed in: ibus (Ubuntu)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1869484

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

Status in ibus package in Ubuntu:
  Fix Released

Bug description:
  i don't know what's happened

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 27 23:00:56 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2018-08-07 (598 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1869484/+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 1870601] [NEW] Software & Updates window stops responding after I click "prereleased updates"

2020-04-03 Thread Seija Kijin
Public bug reported:

Whenever I check the "Prerelease updates" checkbox in Software &
Updates, the app stops responding and Ubuntu asks me to force-quit, ever
single time.

software-properties-gtk:
  Installed: 0.98.7
  Candidate: 0.98.7
  Version table:
 *** 0.98.7 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages
100 /var/lib/dpkg/status

Description:Ubuntu Focal Fossa (development branch)
Release:20.04

This issue happened after I booted the PC for the first time and logged
in, and then opened Software & Updates after Ubuntu said updates were
available and downloaded.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: software-properties-gtk 0.98.7
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
Date: Fri Apr  3 14:52:37 2020
InstallationDate: Installed on 2020-04-03 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot from 2020-04-03 14-58-00.png"
   
https://bugs.launchpad.net/bugs/1870601/+attachment/5345783/+files/Screenshot%20from%202020-04-03%2014-58-00.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1870601

Title:
  Software & Updates window stops responding after I click "prereleased
  updates"

Status in software-properties package in Ubuntu:
  New

Bug description:
  Whenever I check the "Prerelease updates" checkbox in Software &
  Updates, the app stops responding and Ubuntu asks me to force-quit,
  ever single time.

  software-properties-gtk:
Installed: 0.98.7
Candidate: 0.98.7
Version table:
   *** 0.98.7 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  This issue happened after I booted the PC for the first time and
  logged in, and then opened Software & Updates after Ubuntu said
  updates were available and downloaded.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  Date: Fri Apr  3 14:52:37 2020
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1870601/+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 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

2020-04-03 Thread Reshad Dernjani
Is https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1869481
possibly connected to this too?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1859754

Title:
  [SRU] add ucm to make alsa/sof driver work under PA (variants of
  Lenovo X1 Carbon 7th, Dell cnl and cml machines)

Status in HWE Next:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Fix Released
Status in alsa-lib source package in Eoan:
  Fix Released

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1870442] Re: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on.

2020-04-03 Thread Seija Kijin
It was a one-only time issue (for now), and yes, let me add the
jounralctl log.

-- 
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/1870442

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   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/1870442/+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 1870594] [NEW] Software properties is stuck "Refreshing cache" in an infinite loop whenever I attempt to reload the cache while my PC is disconnected from the internet

2020-04-03 Thread Seija Kijin
Public bug reported:

When I attempted to change the Software & Updates settings by clicking
on the "prerelease" version, I realized I forgot to connect to the
internet.

I did, but not before clicking the "Reload" button on the desktop.

As a result, even after my PC connected to the internet, now the Cache
Refresh is stuck at 100% completion, instead of finishing, or closing
after giving me an error.

Description:Ubuntu Focal Fossa (development branch)
Release:20.04

software-properties-gtk:
  Installed: 0.98.7
  Candidate: 0.98.7
  Version table:
 *** 0.98.7 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: software-properties-gtk 0.98.7
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CasperVersion: 1.442
Date: Fri Apr  3 18:14:03 2020
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot from 2020-04-03 18-19-32.png"
   
https://bugs.launchpad.net/bugs/1870594/+attachment/5345763/+files/Screenshot%20from%202020-04-03%2018-19-32.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1870594

Title:
  Software properties is stuck "Refreshing cache" in an infinite loop
  whenever I attempt to reload the cache while my PC is disconnected
  from the internet

Status in software-properties package in Ubuntu:
  New

Bug description:
  When I attempted to change the Software & Updates settings by clicking
  on the "prerelease" version, I realized I forgot to connect to the
  internet.

  I did, but not before clicking the "Reload" button on the desktop.

  As a result, even after my PC connected to the internet, now the Cache
  Refresh is stuck at 100% completion, instead of finishing, or closing
  after giving me an error.

  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  software-properties-gtk:
Installed: 0.98.7
Candidate: 0.98.7
Version table:
   *** 0.98.7 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CasperVersion: 1.442
  Date: Fri Apr  3 18:14:03 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1870594/+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 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

2020-04-03 Thread Apport retracing service
** Tags added: focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1843982

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  Triaged
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1843982/+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 1854621] Re: ubuntu 20.04 daily boots with no background, selecting other background has warped picture

2020-04-03 Thread Brian Murray
We believe that this issue has been fixed with the Beta release of
Ubuntu 20.04. Could you please confirm that the background is no longer
black / missing? Thanks in advance!

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1854621

Title:
  ubuntu 20.04 daily boots with no background, selecting other
  background has warped picture

Status in ubuntu-meta package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 daily - verified (check disc for defects) prior to boot.
  dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

  On booting, the 20.04 daily has no background when desktop is loaded?
  (ie. top panel is there, dock on left side on black screen)

  When changing background (to any already installed), they are warped
  when selected and made the bacground as if corrupted (but small image
  where selection is made looks valid).


  This issue may relate to video card  [radeon]

  ubuntu@ubuntu:~$ sudo lshw -C video
*-display:0   
 description: VGA compatible controller
 product: RV516 [Radeon X1300/X1550 Series]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:01:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:16 memory:d000-dfff memory:fe9e-fe9e 
ioport:dc00(size=256) memory:c-d
*-display:1 UNCLAIMED
 description: Display controller
 product: RV516 [Radeon X1300/X1550 Series] (Secondary)
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0.1
 bus info: pci@:01:00.1
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress bus_master cap_list
 configuration: latency=0
 resources: memory:fe9f-fe9f

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.440
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CasperVersion: 1.432
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  1 11:58:33 2019
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191128)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1854621/+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 1870589] [NEW] test-seccomp fails test_restrict_suid_sgid on arm64 on Bionic

2020-04-03 Thread Dan Streetman
Public bug reported:

[impact]

test case failure

[test case]

check autopkgtest logs, e.g.
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/s/systemd/20200401_09_34f60@/log.gz

/* test_restrict_suid_sgid */
Failed to add suid/sgid rule for architecture arm64, skipping: Numerical 
argument out of domain
Assertion 'chmod(path, 0775 | S_ISUID) < 0 && errno == EPERM' failed at 
../src/test/test-seccomp.c:823, function test_restrict_suid_sgid(). Aborting.
suidsgidseccomp terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("suidsgidseccomp", pid, WAIT_LOG) == 
EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:889, function 
test_restrict_suid_sgid(). Aborting.
FAIL: test-seccomp (code: 134)
Aborted (core dumped)

[regression potential]

TBD

[scope]

this appears to fail only in Bionic, and this specific testcase was
backported in patch CVE-2019-384x-2.patch.  It does not appear that it
ever passed in Bionic on arm64.

[other info]

systemd bionic arm64 autopkgtests have failed forever, but we should fix
that.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: systemd (Ubuntu Bionic)
 Importance: Low
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu)
   Status: New => Fix Released

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Bionic)
   Importance: Undecided => Low

** Changed in: systemd (Ubuntu Bionic)
   Status: New => In Progress

-- 
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/1870589

Title:
  test-seccomp fails test_restrict_suid_sgid on arm64 on Bionic

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress

Bug description:
  [impact]

  test case failure

  [test case]

  check autopkgtest logs, e.g.
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/s/systemd/20200401_09_34f60@/log.gz

  /* test_restrict_suid_sgid */
  Failed to add suid/sgid rule for architecture arm64, skipping: Numerical 
argument out of domain
  Assertion 'chmod(path, 0775 | S_ISUID) < 0 && errno == EPERM' failed at 
../src/test/test-seccomp.c:823, function test_restrict_suid_sgid(). Aborting.
  suidsgidseccomp terminated by signal ABRT.
  Assertion 'wait_for_terminate_and_check("suidsgidseccomp", pid, WAIT_LOG) == 
EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:889, function 
test_restrict_suid_sgid(). Aborting.
  FAIL: test-seccomp (code: 134)
  Aborted (core dumped)

  [regression potential]

  TBD

  [scope]

  this appears to fail only in Bionic, and this specific testcase was
  backported in patch CVE-2019-384x-2.patch.  It does not appear that it
  ever passed in Bionic on arm64.

  [other info]

  systemd bionic arm64 autopkgtests have failed forever, but we should
  fix that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870589/+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 1859581] Re: land oem-getlogs in focal and enable apport-unpack to process apport.gz file

2020-04-03 Thread Brian Murray
** Also affects: apport (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: apport (Ubuntu)
   Status: New => In Progress

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: apport (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1859581

Title:
  land oem-getlogs in focal and enable apport-unpack to process
  apport.gz file

Status in Apport:
  New
Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  In Progress

Bug description:
  LP: #1841157 seems forgeting to include oem-getlogs in
  debian/apport.install.

  Also, add the attached patch so that apport-unpack can process
  apport.gz that oem-getlogs generate directly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1859581/+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 1835660] Re: initramfs unpacking failed

2020-04-03 Thread Ayyappan
Follow-up on my previous post - Unpacking failed, Decoding failed is
back on second boot. Please do not waste your time trying the above.
Sorry.

-- 
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/1835660

Title:
  initramfs unpacking failed

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+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 1870585] [NEW] Not cleaning /var/tmp by default

2020-04-03 Thread Bryan Quigley
Public bug reported:

1) 20.04
2) 245.2-1ubuntu2
3) I expect /var/tmp to be cleaned up in some way.
4) It's commented out per 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773313

In sosreport was comparing the difference between /tmp (Ubuntu/Debian)
and /var/tmp (RH) and determined that as long as /var/tmp gets cleaned
on a regular basis we would prefer /var/tmp.

The  bug that appears to have prompted the disabling was fixed a long
time ago, can we have this 30d delete re-enabled by default?

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1870585

Title:
  Not cleaning /var/tmp by default

Status in systemd package in Ubuntu:
  New

Bug description:
  1) 20.04
  2) 245.2-1ubuntu2
  3) I expect /var/tmp to be cleaned up in some way.
  4) It's commented out per 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773313

  In sosreport was comparing the difference between /tmp (Ubuntu/Debian)
  and /var/tmp (RH) and determined that as long as /var/tmp gets cleaned
  on a regular basis we would prefer /var/tmp.

  The  bug that appears to have prompted the disabling was fixed a long
  time ago, can we have this 30d delete re-enabled by default?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870585/+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 1835660] Re: initramfs unpacking failed

2020-04-03 Thread Ayyappan
Edit initramfs.conf as su.

Rem out COMPRESS-lz4 line

Run update-initramfs -u - System will return with "COMPRESS parameter
not set".

Now edit initramfs.conf again. Remove the # on COMPRESS=lz4, run again
update-initramfs -u.

It will close without any error. Reboot.

I just did and no more failed message.


** Attachment added: "initramfs-unpacking-decoding-failed.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660/+attachment/5345715/+files/initramfs-unpacking-decoding-failed.png

-- 
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/1835660

Title:
  initramfs unpacking failed

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+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 1870560] Re: Client does not renew IP after RADIUS COA disconnect

2020-04-03 Thread Brian Murray
** Package changed: ubuntu => network-manager (Ubuntu)

-- 
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/1870560

Title:
  Client does not renew IP after RADIUS COA disconnect

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have been testing RADIUS change of authorization on Ubiquiti
  wireless.  I have tested this on Ubuntu 19.04 as well as Ubuntu 19.10
  and the behavior is the same on both as well as when testing on Debian
  or Fedora.  FWIW this is working with a Windows 10 or Android client
  connected to the same wireless SSID on the same wireless AP, so this
  does not seem to be a configuration issue on the AP from what I can
  see.  Below are the logs from the Ubuntu client as well as the RADIUS
  server.  Please let me know if any further info is needed or if this
  behavior is expected.  Log info is below.  Thanks!

  
  ubuntu@ubuntu:/var/log$ journalctl | grep -Ei 'dhcp'
  Mar 26 21:28:30 ubuntu NetworkManager[1127]:   [1585258110.5810] 
dhcp-init: Using DHCP client 'dhclient'

  Client sends an Access-Request to RADIUS server:

  Thu Mar 26 17:29:13 2020
  Packet-Type = Access-Request
  User-Name = "dshields"
  NAS-Identifier = "7483c28d26de"
  Called-Station-Id = "74-83-C2-8D-26-DE:DF-Ubiquiti-Test"
  NAS-Port-Type = Wireless-802.11
  Service-Type = Framed-User
  Calling-Station-Id = "38-59-F9-81-5C-98"
  Connect-Info = "CONNECT 0Mbps 802.11b"
  Acct-Session-Id = "ABB4DA79B50051CB"
  WLAN-Pairwise-Cipher = 1027076
  WLAN-Group-Cipher = 1027076
  WLAN-AKM-Suite = 1027073
  Framed-MTU = 1400
  EAP-Message = 0x022900061500
  State = 0x4cc366d24aea73b029eb30b6d6318ffc
  Message-Authenticator = 0x48aef4abde67bc109ce1689d34b292cb
  NAS-IP-Address = 10.100.10.235

  Thu Mar 26 17:29:13 2020
  Packet-Type = Access-Request
  User-Name = "dshields"
  NAS-Identifier = "7483c28d26de"
  Called-Station-Id = "74-83-C2-8D-26-DE:DF-Ubiquiti-Test"
  NAS-Port-Type = Wireless-802.11
  Service-Type = Framed-User
  Calling-Station-Id = "38-59-F9-81-5C-98"
  Connect-Info = "CONNECT 0Mbps 802.11b"
  Acct-Session-Id = "ABB4DA79B50051CB"
  WLAN-Pairwise-Cipher = 1027076
  WLAN-Group-Cipher = 1027076
  WLAN-AKM-Suite = 1027073
  Framed-MTU = 1400
  EAP-Message = 
0x022a00841500160303004610424104bbae17c4fd4f2c594c2fe9737cc7919914adc728c0c3080fcf9e0f4cec1e1baced618159446d056286c8ca54ab8eb9142a2b1cfd5c88e110e6a28edf4ce943ed1403030001011603030028c00e45cebb1752d0b5c6323f47be852483a27af729b82ee96e3139d24dfa485e8ffed35de2438d54
  State = 0x4cc366d24be973b029eb30b6d6318ffc
  Message-Authenticator = 0x5d0f1396a39e5b0e1e1a0c6118e1ebea
  NAS-IP-Address = 10.100.10.235

  Authentication succeeds and VLAN 230 is returned to client with Access-Accept:

  Thu Mar 26 17:29:13 2020 : Auth: Login OK: [dshields] (from client 
OPSWAT-AP-AC-PRO port 0 via TLS tunnel)
  Thu Mar 26 17:29:13 2020 : Auth: Login OK: [dshields] (from client 
OPSWAT-AP-AC-PRO port 0 cli 38-59-F9-81-5C-98)

  Thu Mar 26 17:29:13 2020
  Packet-Type = Access-Accept
  User-Name = "dshields"
  MS-MPPE-Recv-Key = 
0x0e4b4cd48f891763a1f1792c71047066b1fd70914f7212cf011f1a367277cd02
  MS-MPPE-Send-Key = 
0xc81a04f1482a75cff7cac78876a95391ab9908d613dd2e2476def943bab5cf4c
  EAP-MSK = 
0x0e4b4cd48f891763a1f1792c71047066b1fd70914f7212cf011f1a367277cd02c81a04f1482a75cff7cac78876a95391ab9908d613dd2e2476def943bab5cf4c
  EAP-EMSK = 
0x55d0a72ab01bd0a5ec49a6e081fcecff37357ba89f8c25767d8033e529e45b116a9cec3044cef37c20297c60b8b3b345be1248859214586ad9e925545cf88c14
  EAP-Session-Id = 
0x15066089550d45a92a0c53f9280e765fbdcf813480da08fdbf5b33de44dd5dc9c15e7d1ea91e31c2135dd3b384f8d628548ab4beb299a79ee60836464d78cfcce5
  EAP-Message = 0x032b0004
  Message-Authenticator = 0x
  Calling-Station-Id = "38-59-F9-81-5C-98"
  Tunnel-Type:0 += VLAN
  Tunnel-Medium-Type:0 += IEEE-802
  Tunnel-Private-Group-Id:0 += "230"

  Laptop sends a DHCP request and gets an IP in VLAN 230:

  Mar 26 21:29:13 ubuntu NetworkManager[1127]:   [1585258153.1150] dhcp4 
(wlp2s0b1): activation: beginning transaction (timeout in 45 seconds)
  Mar 26 21:29:13 ubuntu NetworkManager[1127]:   [1585258153.1352] dhcp4 
(wlp2s0b1): dhclient started with pid 2626
  Mar 26 21:29:13 ubuntu dhclient[2626]: DHCPDISCOVER on wlp2s0b1 to 
255.255.255.255 port 67 interval 3 (xid=0x6bec8061)
  Mar 26 21:29:13 ubuntu dhclient[2626]: DHCPOFFER of 10.103.230.59 from 
10.103.230.1
  Mar 26 21:29:13 ubuntu dhclient[2626]: DHCPREQUEST for 

[Touch-packages] [Bug 1870560] [NEW] Client does not renew IP after RADIUS COA disconnect

2020-04-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have been testing RADIUS change of authorization on Ubiquiti wireless.
I have tested this on Ubuntu 19.04 as well as Ubuntu 19.10 and the
behavior is the same on both as well as when testing on Debian or
Fedora.  FWIW this is working with a Windows 10 or Android client
connected to the same wireless SSID on the same wireless AP, so this
does not seem to be a configuration issue on the AP from what I can see.
Below are the logs from the Ubuntu client as well as the RADIUS server.
Please let me know if any further info is needed or if this behavior is
expected.  Log info is below.  Thanks!


ubuntu@ubuntu:/var/log$ journalctl | grep -Ei 'dhcp'
Mar 26 21:28:30 ubuntu NetworkManager[1127]:   [1585258110.5810] 
dhcp-init: Using DHCP client 'dhclient'

Client sends an Access-Request to RADIUS server:

Thu Mar 26 17:29:13 2020
Packet-Type = Access-Request
User-Name = "dshields"
NAS-Identifier = "7483c28d26de"
Called-Station-Id = "74-83-C2-8D-26-DE:DF-Ubiquiti-Test"
NAS-Port-Type = Wireless-802.11
Service-Type = Framed-User
Calling-Station-Id = "38-59-F9-81-5C-98"
Connect-Info = "CONNECT 0Mbps 802.11b"
Acct-Session-Id = "ABB4DA79B50051CB"
WLAN-Pairwise-Cipher = 1027076
WLAN-Group-Cipher = 1027076
WLAN-AKM-Suite = 1027073
Framed-MTU = 1400
EAP-Message = 0x022900061500
State = 0x4cc366d24aea73b029eb30b6d6318ffc
Message-Authenticator = 0x48aef4abde67bc109ce1689d34b292cb
NAS-IP-Address = 10.100.10.235

Thu Mar 26 17:29:13 2020
Packet-Type = Access-Request
User-Name = "dshields"
NAS-Identifier = "7483c28d26de"
Called-Station-Id = "74-83-C2-8D-26-DE:DF-Ubiquiti-Test"
NAS-Port-Type = Wireless-802.11
Service-Type = Framed-User
Calling-Station-Id = "38-59-F9-81-5C-98"
Connect-Info = "CONNECT 0Mbps 802.11b"
Acct-Session-Id = "ABB4DA79B50051CB"
WLAN-Pairwise-Cipher = 1027076
WLAN-Group-Cipher = 1027076
WLAN-AKM-Suite = 1027073
Framed-MTU = 1400
EAP-Message = 
0x022a00841500160303004610424104bbae17c4fd4f2c594c2fe9737cc7919914adc728c0c3080fcf9e0f4cec1e1baced618159446d056286c8ca54ab8eb9142a2b1cfd5c88e110e6a28edf4ce943ed1403030001011603030028c00e45cebb1752d0b5c6323f47be852483a27af729b82ee96e3139d24dfa485e8ffed35de2438d54
State = 0x4cc366d24be973b029eb30b6d6318ffc
Message-Authenticator = 0x5d0f1396a39e5b0e1e1a0c6118e1ebea
NAS-IP-Address = 10.100.10.235

Authentication succeeds and VLAN 230 is returned to client with Access-Accept:

Thu Mar 26 17:29:13 2020 : Auth: Login OK: [dshields] (from client 
OPSWAT-AP-AC-PRO port 0 via TLS tunnel)
Thu Mar 26 17:29:13 2020 : Auth: Login OK: [dshields] (from client 
OPSWAT-AP-AC-PRO port 0 cli 38-59-F9-81-5C-98)

Thu Mar 26 17:29:13 2020
Packet-Type = Access-Accept
User-Name = "dshields"
MS-MPPE-Recv-Key = 
0x0e4b4cd48f891763a1f1792c71047066b1fd70914f7212cf011f1a367277cd02
MS-MPPE-Send-Key = 
0xc81a04f1482a75cff7cac78876a95391ab9908d613dd2e2476def943bab5cf4c
EAP-MSK = 
0x0e4b4cd48f891763a1f1792c71047066b1fd70914f7212cf011f1a367277cd02c81a04f1482a75cff7cac78876a95391ab9908d613dd2e2476def943bab5cf4c
EAP-EMSK = 
0x55d0a72ab01bd0a5ec49a6e081fcecff37357ba89f8c25767d8033e529e45b116a9cec3044cef37c20297c60b8b3b345be1248859214586ad9e925545cf88c14
EAP-Session-Id = 
0x15066089550d45a92a0c53f9280e765fbdcf813480da08fdbf5b33de44dd5dc9c15e7d1ea91e31c2135dd3b384f8d628548ab4beb299a79ee60836464d78cfcce5
EAP-Message = 0x032b0004
Message-Authenticator = 0x
Calling-Station-Id = "38-59-F9-81-5C-98"
Tunnel-Type:0 += VLAN
Tunnel-Medium-Type:0 += IEEE-802
Tunnel-Private-Group-Id:0 += "230"

Laptop sends a DHCP request and gets an IP in VLAN 230:

Mar 26 21:29:13 ubuntu NetworkManager[1127]:   [1585258153.1150] dhcp4 
(wlp2s0b1): activation: beginning transaction (timeout in 45 seconds)
Mar 26 21:29:13 ubuntu NetworkManager[1127]:   [1585258153.1352] dhcp4 
(wlp2s0b1): dhclient started with pid 2626
Mar 26 21:29:13 ubuntu dhclient[2626]: DHCPDISCOVER on wlp2s0b1 to 
255.255.255.255 port 67 interval 3 (xid=0x6bec8061)
Mar 26 21:29:13 ubuntu dhclient[2626]: DHCPOFFER of 10.103.230.59 from 
10.103.230.1
Mar 26 21:29:13 ubuntu dhclient[2626]: DHCPREQUEST for 10.103.230.59 on 
wlp2s0b1 to 255.255.255.255 port 67 (xid=0x6180ec6b)
Mar 26 21:29:13 ubuntu dhclient[2626]: DHCPACK of 10.103.230.59 from 
10.103.230.1 (xid=0x6bec8061)
Mar 26 21:29:13 ubuntu NetworkManager[1127]:   [1585258153.7935] dhcp4 
(wlp2s0b1):   address 10.103.230.59
Mar 26 21:29:13 ubuntu NetworkManager[1127]:   [1585258153.7936] dhcp4 
(wlp2s0b1):   plen 24 (255.255.255.0)
Mar 26 21:29:13 ubuntu NetworkManager[1127]:   [1585258153.7936] dhcp4 
(wlp2s0b1):   gateway 

[Touch-packages] [Bug 1870550] Re: PCI/internal sound card not detected

2020-04-03 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => alsa-driver (Ubuntu)

-- 
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/1870550

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The sound card is not detected on my machine

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 00:51:33 2020
  InstallationDate: Installed on 2020-02-25 (37 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FA
  dmi.board.vendor: HP
  dmi.board.version: 87.46
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd03/02/2020:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.46:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
  dmi.product.sku: 8UR41PA#ABG
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870550/+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 1870550] [NEW] PCI/internal sound card not detected

2020-04-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The sound card is not detected on my machine

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  4 00:51:33 2020
InstallationDate: Installed on 2020-02-25 (37 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/02/2020
dmi.bios.vendor: AMI
dmi.bios.version: F.13
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 86FA
dmi.board.vendor: HP
dmi.board.version: 87.46
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd03/02/2020:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.46:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Spectre
dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
dmi.product.sku: 8UR41PA#ABG
dmi.sys.vendor: HP

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic
-- 
PCI/internal sound card not detected
https://bugs.launchpad.net/bugs/1870550
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver 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 1869796] Re: vague error during upgrade

2020-04-03 Thread Balint Reczey
@paelzer I've left a comment in the Debian bug, too, and I agree that
the best fix would be in systemd, while I think for Focal a workaround
will be needed (maybe the one I proposed there, maybe one in libvirt).

** Changed in: systemd (Ubuntu)
   Status: New => Incomplete

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Wishlist

-- 
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/1869796

Title:
  vague error during upgrade

Status in debhelper package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in debhelper package in Debian:
  Incomplete

Bug description:
  Seen from today's apt upgrade on focal:

  Setting up libvirt-daemon-driver-qemu (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-rbd (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-zfs (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-system (6.0.0-0ubuntu6) ...
  Job failed. See "journalctl -xe" for details.
  virtlockd.service is a disabled or a static unit, not starting it.
  virtlogd.service is a disabled or a static unit, not starting it.
  Setting up libvirt-daemon dnsmasq configuration.

  
  Sadly 'journactl -xe' was useless. (It only showed a thousand unrelated 
lines.) A raw journalctl took forever to run long enough to let me see it 
generated two million lines of output, and started about two years ago, that 
I'm not keen on trying to run that through less or similar. Advice accepted.

  systemctl status looks good enough though:

  $ systemctl status 'libvirt*'
  ● libvirtd.socket - Libvirt local socket
   Loaded: loaded (/lib/systemd/system/libvirtd.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local
  socket.

  ● libvirtd.service - Virtualization daemon
   Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
  TriggeredBy: ● libvirtd-admin.socket
   ● libvirtd.socket
   ● libvirtd-ro.socket
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 3646435 (libvirtd)
Tasks: 19 (limit: 32768)
   Memory: 26.9M
   CGroup: /system.slice/libvirtd.service
   ├─   3054 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   ├─   3055 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   └─3646435 /usr/sbin/libvirtd

  Mar 30 20:44:55 millbarge systemd[1]: Starting Virtualization daemon...
  Mar 30 20:44:55 millbarge systemd[1]: Started Virtualization daemon.
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read /etc/hosts - 7 addresses
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read 
/var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
  Mar 30 20:44:55 millbarge dnsmasq-dhcp[3054]: read 
/var/lib/libvirt/dnsmasq/default.hostsfile

  ● libvirtd-admin.socket - Libvirt admin socket
   Loaded: loaded (/lib/systemd/system/libvirtd-admin.socket; enabled; 
vendor preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-admin-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-admin.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt admin
  socket.

  ● libvirt-guests.service - Suspend/Resume Running libvirt Guests
   Loaded: loaded (/lib/systemd/system/libvirt-guests.service; enabled; 
vendor preset: enabled)
   Active: active (exited) since Wed 2020-03-25 00:41:47 UTC; 5 days ago
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 2808 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirt-guests.service

  Mar 25 00:41:47 millbarge systemd[1]: Starting Suspend/Resume Running libvirt 
Guests...
  Mar 25 00:41:47 millbarge systemd[1]: Finished Suspend/Resume Running libvirt 
Guests.

  ● libvirtd-ro.socket - Libvirt local read-only socket
   Loaded: loaded (/lib/systemd/system/libvirtd-ro.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● 

[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

2020-04-03 Thread Dan Streetman
Thanks!  Could you check the rfkill code, also?  I think instead of
patching the testcase, it would be better fix rfkill so the change is
effective as soon as it returns; that way users won't experience this
and have to add their own sleep after calling rfkill.

-- 
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/1733321

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  New
Status in network-manager source package in Focal:
  New

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock. Adding a sleep before calling nmcli fixes the issue.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  
  [Test Case]

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  
  [Regression Potential]

  No regression potential. The fix touches only the testcase shipped
  with the source package and it doesn't change the binary package. The
  sleep time added is very small, so no possibility of causing testcase
  timeout.

  
  [Other Info]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-04-03 Thread Rajat Pandita
Fresh install with proprietary driver’s installation check box ticked
worked fine till I rebooted again and then I could not get into the
desktop. All drivers installed fine but one reboot later things were
back to being unable to login. So I did a chroot and removed splash from
grub command line followed by update grub and I Am back in business

-- 
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/1845801

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  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.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  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.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  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:

[Touch-packages] [Bug 1870213] Re: "Switching to another layout" shortcut was not set by oem-config for end-user

2020-04-03 Thread Norbert
Exists in beta. Language pair does not really matter.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1870213

Title:
  "Switching to another layout" shortcut was not set by oem-config for
  end-user

Status in console-setup package in Ubuntu:
  New
Status in oem-config package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Launch Ubuntu MATE 20.04 LTS installer in OEM mode
  2. Confirm using English locale
  3. While setting OS for end user specify Russian language, confirm system 
configuration
  4. Login to the configured system

  Expected result:
  * the keyboard layout switcher shows two layouts - *en* and *ru*, reacts on 
+ hotkey 

  Actual result:
  * the keyboard layout switcher shows two layouts - *en* and *ru*, but does 
not react on + hotkey 

  Note: the contents of keyboard configuration files is the following:

  ```
  $ cat /etc/default/keyboard
  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="us,ru"
  XKBVARIANT=","
  XKBOPTIONS="grp_led:scroll"

  BACKSPACE="guess"

  ```
  so keyboard layout switcher is not defined here.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: keyboard-configuration 1.194ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Apr  2 00:43:16 2020
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1870213/+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 1870554] [NEW] ip-netns(8) unmounts /sys filesystem hierarchy within namespace

2020-04-03 Thread Lucio Andrés Illanes Albornoz
Public bug reported:

Filesystems ordinarily mounted beneath /sys, particularly /sys/fs/cgroup, are 
not mounted within network namespaces created by ip-netns(8), as 
lib/namespace.c:netns_switch() explicitly remounts /sys.
The patch enclosed removes the offending calls to umount2(2) and mount(2), 
leaving the /sys hierarchy intact within network namespaces.

$ lsb_release -rd
Description:Ubuntu 18.04.4 LTS
Release:18.04

$ apt-cache policy iproute2
iproute2:
  Installed: 4.15.0-2ubuntu1
  Candidate: 4.15.0-2ubuntu1
  Version table:
 *** 4.15.0-2ubuntu1 500
500 http://fr2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

Nota bene: this bug was reported in [1] (unresolved) and, on Arch Linux,
[2].

References:
[1] https://answers.launchpad.net/ubuntu/+source/iproute2/+question/659146
[2] https://bugs.archlinux.org/task/33328

** Affects: iproute2 (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "iproute2-4.3.0+no-remount-sysfs.patch"
   
https://bugs.launchpad.net/bugs/1870554/+attachment/5345647/+files/iproute2-4.3.0+no-remount-sysfs.patch

** Patch removed: "iproute2-4.3.0+no-remount-sysfs.patch"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1870554/+attachment/5345647/+files/iproute2-4.3.0+no-remount-sysfs.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1870554

Title:
  ip-netns(8) unmounts /sys filesystem hierarchy within namespace

Status in iproute2 package in Ubuntu:
  New

Bug description:
  Filesystems ordinarily mounted beneath /sys, particularly /sys/fs/cgroup, are 
not mounted within network namespaces created by ip-netns(8), as 
lib/namespace.c:netns_switch() explicitly remounts /sys.
  The patch enclosed removes the offending calls to umount2(2) and mount(2), 
leaving the /sys hierarchy intact within network namespaces.

  $ lsb_release -rd
  Description:Ubuntu 18.04.4 LTS
  Release:18.04

  $ apt-cache policy iproute2
  iproute2:
Installed: 4.15.0-2ubuntu1
Candidate: 4.15.0-2ubuntu1
Version table:
   *** 4.15.0-2ubuntu1 500
  500 http://fr2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Nota bene: this bug was reported in [1] (unresolved) and, on Arch
  Linux, [2].

  References:
  [1] https://answers.launchpad.net/ubuntu/+source/iproute2/+question/659146
  [2] https://bugs.archlinux.org/task/33328

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1870554/+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 1870554] Re: ip-netns(8) unmounts /sys filesystem hierarchy within namespace

2020-04-03 Thread Lucio Andrés Illanes Albornoz
** Patch added: "iproute2-4.3.0+no-remount-sysfs.patch"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1870554/+attachment/5345648/+files/iproute2-4.3.0+no-remount-sysfs.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1870554

Title:
  ip-netns(8) unmounts /sys filesystem hierarchy within namespace

Status in iproute2 package in Ubuntu:
  New

Bug description:
  Filesystems ordinarily mounted beneath /sys, particularly /sys/fs/cgroup, are 
not mounted within network namespaces created by ip-netns(8), as 
lib/namespace.c:netns_switch() explicitly remounts /sys.
  The patch enclosed removes the offending calls to umount2(2) and mount(2), 
leaving the /sys hierarchy intact within network namespaces.

  $ lsb_release -rd
  Description:Ubuntu 18.04.4 LTS
  Release:18.04

  $ apt-cache policy iproute2
  iproute2:
Installed: 4.15.0-2ubuntu1
Candidate: 4.15.0-2ubuntu1
Version table:
   *** 4.15.0-2ubuntu1 500
  500 http://fr2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Nota bene: this bug was reported in [1] (unresolved) and, on Arch
  Linux, [2].

  References:
  [1] https://answers.launchpad.net/ubuntu/+source/iproute2/+question/659146
  [2] https://bugs.archlinux.org/task/33328

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1870554/+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 1870408] Re: casper-md5check should leave a breadcrumb which apport, ubiquity, subiquity could use

2020-04-03 Thread Brian Murray
** Changed in: apport (Ubuntu)
   Status: New => Triaged

** Changed in: apport (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1870408

Title:
  casper-md5check should leave a breadcrumb which apport, ubiquity,
  subiquity could use

Status in subiquity:
  New
Status in apport package in Ubuntu:
  Triaged
Status in casper package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  New

Bug description:
  casper-md5check should leave a breadcrumb which apport & ubiquity can
  pick up. (subiquity too)

  There will be a file called:

  /run/casper-md5check.json

  If it does not exist, or is empty the check did not run enough to
  validate anything. Treat as skip.

  If it has content it will have:
  {
 "checksum_missmatch" : [
"./pics/red-upperleft.png",
"./pics/red-lowerleft.png"
 ],
 "result" : "fail"
  }

  optional checksum_missmatch key, which will have a list of strings
  that are files that failed md5sum.

  result key, which can have string values "pass" "fail" "skip".

  One can use python's json or yaml safe_load to parse the file into a
  dictionary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1870408/+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 1827857] Re: Stuck on applying package profile for servers running 18.04

2020-04-03 Thread Simon Poirier
** Changed in: landscape-client (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1827857

Title:
  Stuck on applying package profile for servers running 18.04

Status in landscape-client package in Ubuntu:
  Fix Committed
Status in python-apt package in Ubuntu:
  New

Bug description:
  When I apply a package profile to a server, the activity is stuck on
  'in progress'. It only happens for servers running on 18.04 LTS. It
  works for servers running on 14.04 LTS.

  I can verify that this is not a connection issue by:
  * Manually installing the packages contained in the package profile
  * Installing the package profile directly using apt-get.

  The landscape server is hosted on-premise using version 18.01.
  The 18.04 server is running:
* The latest version of landscape-client, 18.01-0ubuntu3.3.
* Ubuntu Server 18.04.02 LTS using 4.15.x kernel.
* Python version: 3.6.7

  Maybe relevant log files:

  package-changer.log 
  2019-05-06 11:59:55,977 WARNING  [MainThread] Package data not yet 
synchronized with server (...)

  package-reporter.log
  2019-05-06 12:00:07,581 ERROR[MainThread] None
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb2 in position 29: 
invalid start byte

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1827857/+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 1870553] [NEW] OopsText.txt does not contain stack trace

2020-04-03 Thread Mauricio Faria de Oliveira
Public bug reported:

Please refer to bug 1868388 attachment OopsText.txt.

The issue reported is a kernel cpu soft lockup.

The stack trace is essential to understand what was going on,
but it's _not included at_ all - actually, it's been cut off,
there's the beginning of the kernel messages, but ends there.

Unfortunately the output of dmesg (file CurrentDmesg.txt)
does not have the kernel error messages (maybe collected
at some other point in time?) - so the bug report has no
evidences of the stack trace to perform any debugging.

Is this behavior intentional/by design for some reason?

Can that be clarified/reviewed as there's at least one
(this) occurrence that didn't allow apport files to be
used for debugging?

Thanks!

** Affects: apport (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Changed in: apport (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1870553

Title:
  OopsText.txt does not contain stack trace

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Please refer to bug 1868388 attachment OopsText.txt.

  The issue reported is a kernel cpu soft lockup.

  The stack trace is essential to understand what was going on,
  but it's _not included at_ all - actually, it's been cut off,
  there's the beginning of the kernel messages, but ends there.

  Unfortunately the output of dmesg (file CurrentDmesg.txt)
  does not have the kernel error messages (maybe collected
  at some other point in time?) - so the bug report has no
  evidences of the stack trace to perform any debugging.

  Is this behavior intentional/by design for some reason?

  Can that be clarified/reviewed as there's at least one
  (this) occurrence that didn't allow apport files to be
  used for debugging?

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870553/+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 1858168] Re: Ubuntu 19.10 after updating the "Other Software" tab in "Software & Updates" the "cache refresh" hangs

2020-04-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1858168

Title:
  Ubuntu 19.10 after updating the "Other Software" tab in "Software &
  Updates" the "cache refresh" hangs

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Running the command from a terminal window The following messages are
  logged when the hang occurs:

  simon@Ubuntu-2600K:~$ sudo software-properties-gtk
  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 86, in on_pktask_finish
  results = self._pktask.generic_finish(result)
  gi.repository.GLib.Error: pk-client-error-quark: W: Skipping acquire of 
configured file 'main/binary-i386/Packages' as repository 
'http://packages.microsoft.com/repos/vscode stable InRelease' doesn't support 
architecture 'i386'
  E: The repository 
'http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu eoan 
Release' does not have a Release file.
  W: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  W: See apt-secure(8) manpage for repository creation and user configuration 
details.
   (319)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 89, in on_pktask_finish
  Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in 
__init__
  self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in 
__init__
  _window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
  TypeError: could not convert value for property `transient_for' from 
DialogCacheOutdated to GtkWindow

  I note similar issues reported for other functions however, these seem
  to have been resolved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1858168/+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 1870410] Re: wireless does not work on boot on RPi 3s

2020-04-03 Thread Balint Reczey
@ddstreet thanks, I'll pick those for the next upload (merging upcoming
245.4-2)

** Changed in: systemd (Ubuntu Focal)
   Status: New => In Progress

-- 
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/1870410

Title:
  wireless does not work on boot on RPi 3s

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  I've setup a wireless config in /etc/netplan/config.yaml and it does
  not activate on boot. I have to run 'sudo netplan apply' to get my
  wireless connected. This works fine on an RPi4 but not an RPi3B.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: User Name 5.4.0-1006.6-raspi2 5.4.24
  Uname: Linux 5.4.0-1006-raspi2 armv7l
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: armhf
  Date: Thu Apr  2 19:02:27 2020
  Lspci:
   
  Lsusb:
   Bus 001 Device 007: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) 
SMSC9512/9514 Fast Ethernet Adapter
   Bus 001 Device 006: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) 
SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
   |__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/5p, 480M
   |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, 
Driver=smsc95xx, 480M
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 
bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:FF:6B:0F 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870410/+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 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf

2020-04-03 Thread Laurent Bonnaud
** Tags added: 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/1826639

Title:
  wpasupplicant: unknown keys in no-mac-addr-change.conf

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  NetworkManager warns that no-mac-addr-change.conf contains unknown
  configuration directives:

  # journalctl | grep no-mac-addr-change
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] Read 
config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 
20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 
10-globally-managed-devices.conf, default-wifi-powersave-on.conf)
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'wifi.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'ethernet.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: wpasupplicant 2:2.6-21ubuntu3
  Uname: Linux 5.0.9-050009-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 27 13:15:27 2019
  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/1826639/+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 1870408] Re: casper-md5check should leave a breadcrumb which apport, ubiquity, subiquity could use

2020-04-03 Thread Dimitri John Ledkov
** Description changed:

  casper-md5check should leave a breadcrumb which apport & ubiquity can
  pick up. (subiquity too)
  
  There will be a file called:
  
- /run/casper-md5check.yaml
+ /run/casper-md5check.json
  
  If it does not exist, or is empty the check did not run enough to
  validate anything. Treat as skip.
  
  If it has content it will have:
- checksum_missmatch:
-   - ./pics/red-upperleft.png
- result: fail
+ {
+"checksum_missmatch" : [
+   "./pics/red-upperleft.png",
+   "./pics/red-lowerleft.png"
+],
+"result" : "fail"
+ }
  
  optional checksum_missmatch key, which will have a list of strings that
  are files that failed md5sum.
  
  result key, which can have string values "pass" "fail" "skip".
  
- One can use python's yaml safe_load to parse the file into a dictionary.
+ One can use python's json or yaml safe_load to parse the file into a
+ dictionary.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1870408

Title:
  casper-md5check should leave a breadcrumb which apport, ubiquity,
  subiquity could use

Status in subiquity:
  New
Status in apport package in Ubuntu:
  New
Status in casper package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  New

Bug description:
  casper-md5check should leave a breadcrumb which apport & ubiquity can
  pick up. (subiquity too)

  There will be a file called:

  /run/casper-md5check.json

  If it does not exist, or is empty the check did not run enough to
  validate anything. Treat as skip.

  If it has content it will have:
  {
 "checksum_missmatch" : [
"./pics/red-upperleft.png",
"./pics/red-lowerleft.png"
 ],
 "result" : "fail"
  }

  optional checksum_missmatch key, which will have a list of strings
  that are files that failed md5sum.

  result key, which can have string values "pass" "fail" "skip".

  One can use python's json or yaml safe_load to parse the file into a
  dictionary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1870408/+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 1870410] Re: wireless does not work on boot on RPi 3s

2020-04-03 Thread Dan Streetman
commits 08c588d18b1 and 1b43e246020

-- 
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/1870410

Title:
  wireless does not work on boot on RPi 3s

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Focal:
  New

Bug description:
  I've setup a wireless config in /etc/netplan/config.yaml and it does
  not activate on boot. I have to run 'sudo netplan apply' to get my
  wireless connected. This works fine on an RPi4 but not an RPi3B.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: User Name 5.4.0-1006.6-raspi2 5.4.24
  Uname: Linux 5.4.0-1006-raspi2 armv7l
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: armhf
  Date: Thu Apr  2 19:02:27 2020
  Lspci:
   
  Lsusb:
   Bus 001 Device 007: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) 
SMSC9512/9514 Fast Ethernet Adapter
   Bus 001 Device 006: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) 
SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
   |__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/5p, 480M
   |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, 
Driver=smsc95xx, 480M
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 
bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:FF:6B:0F 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870410/+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 1870408] Re: casper-md5check should leave a breadcrumb which apport, ubiquity, subiquity could use

2020-04-03 Thread Dimitri John Ledkov
Updated implementation.

** Description changed:

  casper-md5check should leave a breadcrumb which apport & ubiquity can
  pick up. (subiquity too)
  
  There will be a file called:
  
- /run/casper-md5check.failed
+ /run/casper-md5check.yaml
  
- or
- /run/casper-md5check.passed
- /run/casper-md5check.skipped
+ If it does not exist, or is empty the check did not run enough to
+ validate anything. Treat as skip.
+ 
+ If it has content it will have:
+ checksum_missmatch:
+   - ./pics/red-upperleft.png
+ result: fail
+ 
+ optional checksum_missmatch key, which will have a list of strings that
+ are files that failed md5sum.
+ 
+ result key, which can have string values "pass" "fail" "skip".
+ 
+ One can use python's yaml safe_load to parse the file into a dictionary.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1870408

Title:
  casper-md5check should leave a breadcrumb which apport, ubiquity,
  subiquity could use

Status in subiquity:
  New
Status in apport package in Ubuntu:
  New
Status in casper package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  New

Bug description:
  casper-md5check should leave a breadcrumb which apport & ubiquity can
  pick up. (subiquity too)

  There will be a file called:

  /run/casper-md5check.yaml

  If it does not exist, or is empty the check did not run enough to
  validate anything. Treat as skip.

  If it has content it will have:
  checksum_missmatch:
- ./pics/red-upperleft.png
  result: fail

  optional checksum_missmatch key, which will have a list of strings
  that are files that failed md5sum.

  result key, which can have string values "pass" "fail" "skip".

  One can use python's yaml safe_load to parse the file into a
  dictionary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1870408/+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 1863797] Re: gdk-pixbuf-thumbnailer fails to create thumbnails for CR2 100% of the time.

2020-04-03 Thread Sebastien Bacher
Upstream considers the issue to be invalid

** Changed in: gdk-pixbuf (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu.
https://bugs.launchpad.net/bugs/1863797

Title:
  gdk-pixbuf-thumbnailer fails to create thumbnails for CR2 100% of the
  time.

Status in gdk-pixbuf:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Invalid

Bug description:
  I have been adding "image/x-xpixmap;image/x-canon-cr2;image/x-adobe-
  dng" to the end of the line starting with "MimeType=" in the file
  "/usr/share/thumbnailers/gdk-pixbuf-thumbnailer.thumbnailer" since
  Ubuntu 18.10 for the thumbnailer to create the thumbnails primarily
  for the ".CR2" raw files from my Canon 77D and 80D cameras.

  Unfortunately I have to report that as of Ubuntu 19.10 this solution doesn’t 
work on my machine anymore.
  The thumbnailer tries to create the thumbnails but fails and instead creates 
1 pixel png images that it all puts in 
"~/.cache/thumbnails/fail/gnome-thumbnail-factory".

  Is there any solution? Should I test something?

  I've attached a CR2 photo of mine that anyone can use for testing.

  I've also created a bug report on gnome gitlab here:
  https://gitlab.gnome.org/GNOME/gdk-pixbuf/issues/144

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1863797/+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 1863797] Re: gdk-pixbuf-thumbnailer fails to create thumbnails for CR2 100% of the time.

2020-04-03 Thread Bug Watch Updater
** Changed in: gdk-pixbuf
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu.
https://bugs.launchpad.net/bugs/1863797

Title:
  gdk-pixbuf-thumbnailer fails to create thumbnails for CR2 100% of the
  time.

Status in gdk-pixbuf:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Confirmed

Bug description:
  I have been adding "image/x-xpixmap;image/x-canon-cr2;image/x-adobe-
  dng" to the end of the line starting with "MimeType=" in the file
  "/usr/share/thumbnailers/gdk-pixbuf-thumbnailer.thumbnailer" since
  Ubuntu 18.10 for the thumbnailer to create the thumbnails primarily
  for the ".CR2" raw files from my Canon 77D and 80D cameras.

  Unfortunately I have to report that as of Ubuntu 19.10 this solution doesn’t 
work on my machine anymore.
  The thumbnailer tries to create the thumbnails but fails and instead creates 
1 pixel png images that it all puts in 
"~/.cache/thumbnails/fail/gnome-thumbnail-factory".

  Is there any solution? Should I test something?

  I've attached a CR2 photo of mine that anyone can use for testing.

  I've also created a bug report on gnome gitlab here:
  https://gitlab.gnome.org/GNOME/gdk-pixbuf/issues/144

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1863797/+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 1870427] Re: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127

2020-04-03 Thread Laurent Bonnaud
Here it is on my system:

$ update-alternatives  --display pager
pager - auto mode
  link best version is /usr/bin/less
  link currently points to /usr/bin/less
  link pager is /usr/bin/pager
  slave pager.1.gz is /usr/share/man/man1/pager.1.gz
/bin/more - priority 50
  slave pager.1.gz: /usr/share/man/man1/more.1.gz
/usr/bin/less - priority 77
  slave pager.1.gz: /usr/share/man/man1/less.1.gz
/usr/bin/w3m - priority 25
  slave pager.1.gz: /usr/share/man/man1/w3m.1.gz

However this output is for my system in its current state, that has been
fixed by finishing the eoan -> focal upgrade.  The alternative was
probably transiently broken during the upgrade.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to less in Ubuntu.
https://bugs.launchpad.net/bugs/1870427

Title:
  package smartmontools 7.1-1build1 failed to install/upgrade: conffile
  difference visualizer subprocess returned error exit status 127

Status in dpkg package in Ubuntu:
  Incomplete
Status in less package in Ubuntu:
  New

Bug description:
  During an upgrade from eoan to focal I got the following error:

   package:smartmontools:7.1-1build1
   Installing new version of config file /etc/init.d/smartmontools ...

   Configuration file '/etc/smartd.conf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
  What would you like to do about it ?  Your options are:
   Y or I  : install the package maintainer's version
   N or O  : keep your currently-installed version
 D : show the differences between the versions
 Z : start a shell to examine the situation
The default action is to keep your current version.
   *** smartd.conf (Y/I/N/O/D/Z) [default=N] ? d
   sh: 1: pager: not found
   diff: standard output: Broken pipe
   dpkg: error processing package smartmontools (--configure):
conffile difference visualizer subprocess returned error exit status 127

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: smartmontools 7.1-1build1
  Uname: Linux 5.6.2-050602-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  Date: Thu Apr  2 19:58:06 2020
  ErrorMessage: conffile difference visualizer subprocess returned error exit 
status 127
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: /usr/bin/python3.8, Python 3.8.2, python-is-python3, 3.8.2-3
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  2.0.1
  SourcePackage: smartmontools
  Title: package smartmontools 7.1-1build1 failed to install/upgrade: conffile 
difference visualizer subprocess returned error exit status 127
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  mtime.conffile..etc.smartd.conf: 2019-06-28T19:35:09.428956

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1870427/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

2020-04-03 Thread rolfinator
Is this bug something that is actively worked on or is it ignored until
20.04 is released as stable (Regarding to
https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1840725/comments/37 in 20.04 the mic works)?

-- 
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/1840725

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1870074] Re: python-glanceclient ftbfs in focal

2020-04-03 Thread James Page
Boiling those down from the package build log:


glanceclient.tests.unit.test_ssl.TestHTTPSVerifyCert.test_v2_requests_valid_cert_no_key

OpenSSL.SSL.Error: [('SSL routines', 'SSL_CTX_use_certificate', 'ca md
too weak')]

glanceclient.tests.unit.test_ssl.TestHTTPSVerifyCert.test_v1_requests_cert_verification

OpenSSL.SSL.SysCallError: (104, 'ECONNRESET')

glanceclient.tests.unit.test_ssl.TestHTTPSVerifyCert.test_v2_requests_cert_verification_no_compression
glanceclient.tests.unit.test_ssl.TestHTTPSVerifyCert.test_v1_requests_cert_verification_no_compression

OpenSSL.SSL.SysCallError: (-1, 'Unexpected EOF')

glanceclient.tests.unit.test_ssl.TestHTTPSVerifyCert.test_v2_requests_cert_verification

OpenSSL.SSL.SysCallError: (-1, 'Unexpected EOF')

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1870074

Title:
  python-glanceclient ftbfs in focal

Status in openssl package in Ubuntu:
  New
Status in python-glanceclient package in Ubuntu:
  In Progress

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963677/+files/buildlog_ubuntu-focal-amd64.python-glanceclient_1%3A2.17.0-0ubuntu2_BUILDING.txt.gz

  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
665, in urlopen
  httplib_response = self._make_request(

File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
376, in _make_request
  self._validate_conn(conn)

File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
996, in _validate_conn
  conn.connect()

File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 352, 
in connect
  self.sock = ssl_wrap_socket(

File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 383, 
in ssl_wrap_socket
  return context.wrap_socket(sock)

File "/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py", 
line 491, in wrap_socket
  raise ssl.SSLError("bad handshake: %r" % e)

  ssl.SSLError: ("bad handshake: SysCallError(-1, 'Unexpected
  EOF')",)

  
  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, 
in send
  resp = conn.urlopen(

File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
719, in urlopen
  retries = retries.increment(

File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 436, 
in increment
  raise MaxRetryError(_pool, url, error or ResponseError(cause))

  urllib3.exceptions.MaxRetryError:
  HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
  with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
  handshake: SysCallError(-1, 'Unexpected EOF')")))

  
  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/<>/glanceclient/common/http.py", line 269, in 
_request
  resp = self.session.request(method,

File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533, 
in request
  resp = self.send(prep, **send_kwargs)

File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646, 
in send
  r = adapter.send(request, **kwargs)

File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514, 
in send
  raise SSLError(e, request=request)

  requests.exceptions.SSLError: HTTPSConnectionPool(host='0.0.0.0',
  port=45175): Max retries exceeded with url: /v2/images/image123
  (Caused by SSLError(SSLError("bad handshake: SysCallError(-1,
  'Unexpected EOF')")))

  
  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/<>/glanceclient/tests/unit/test_ssl.py", line 124, 
in test_v2_requests_cert_verification
  gc.images.get('image123')

File "/<>/glanceclient/v2/images.py", line 198, in get
  return self._get(image_id)

File "/<>/glanceclient/common/utils.py", line 598, in inner
  return RequestIdProxy(wrapped(*args, **kwargs))

File "/<>/glanceclient/v2/images.py", line 191, in _get
  resp, body = self.http_client.get(url, headers=header)

File "/<>/glanceclient/common/http.py", line 315, in get
  return self._request('GET', url, **kwargs)

File "/<>/glanceclient/common/http.py", line 282, in 
_request
  raise exc.CommunicationError(message=message)

  glanceclient.exc.CommunicationError: Error finding address for
  https://0.0.0.0:45175/v2/images/image123:
  HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
  with url: 

[Touch-packages] [Bug 1870074] Re: python-glanceclient ftbfs in focal

2020-04-03 Thread James Page
'ca md too weak' would indicate the signing alg is not good enough on
the ca.crt any longer:

Signature Algorithm: sha1WithRSAEncryption

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1870074

Title:
  python-glanceclient ftbfs in focal

Status in openssl package in Ubuntu:
  New
Status in python-glanceclient package in Ubuntu:
  In Progress

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963677/+files/buildlog_ubuntu-focal-amd64.python-glanceclient_1%3A2.17.0-0ubuntu2_BUILDING.txt.gz

  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
665, in urlopen
  httplib_response = self._make_request(

File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
376, in _make_request
  self._validate_conn(conn)

File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
996, in _validate_conn
  conn.connect()

File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 352, 
in connect
  self.sock = ssl_wrap_socket(

File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 383, 
in ssl_wrap_socket
  return context.wrap_socket(sock)

File "/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py", 
line 491, in wrap_socket
  raise ssl.SSLError("bad handshake: %r" % e)

  ssl.SSLError: ("bad handshake: SysCallError(-1, 'Unexpected
  EOF')",)

  
  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, 
in send
  resp = conn.urlopen(

File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
719, in urlopen
  retries = retries.increment(

File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 436, 
in increment
  raise MaxRetryError(_pool, url, error or ResponseError(cause))

  urllib3.exceptions.MaxRetryError:
  HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
  with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
  handshake: SysCallError(-1, 'Unexpected EOF')")))

  
  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/<>/glanceclient/common/http.py", line 269, in 
_request
  resp = self.session.request(method,

File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533, 
in request
  resp = self.send(prep, **send_kwargs)

File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646, 
in send
  r = adapter.send(request, **kwargs)

File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514, 
in send
  raise SSLError(e, request=request)

  requests.exceptions.SSLError: HTTPSConnectionPool(host='0.0.0.0',
  port=45175): Max retries exceeded with url: /v2/images/image123
  (Caused by SSLError(SSLError("bad handshake: SysCallError(-1,
  'Unexpected EOF')")))

  
  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/<>/glanceclient/tests/unit/test_ssl.py", line 124, 
in test_v2_requests_cert_verification
  gc.images.get('image123')

File "/<>/glanceclient/v2/images.py", line 198, in get
  return self._get(image_id)

File "/<>/glanceclient/common/utils.py", line 598, in inner
  return RequestIdProxy(wrapped(*args, **kwargs))

File "/<>/glanceclient/v2/images.py", line 191, in _get
  resp, body = self.http_client.get(url, headers=header)

File "/<>/glanceclient/common/http.py", line 315, in get
  return self._request('GET', url, **kwargs)

File "/<>/glanceclient/common/http.py", line 282, in 
_request
  raise exc.CommunicationError(message=message)

  glanceclient.exc.CommunicationError: Error finding address for
  https://0.0.0.0:45175/v2/images/image123:
  HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
  with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
  handshake: SysCallError(-1, 'Unexpected EOF')")))

  
  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in 
patched
  return func(*args, **keywargs)

File "/<>/glanceclient/tests/unit/test_ssl.py", line 128, 
in test_v2_requests_cert_verification
  self.fail('No certificate failure message is received')

File "/usr/lib/python3/dist-packages/unittest2/case.py", line 690, in 
fail
  raise 

[Touch-packages] [Bug 1870074] Re: python-glanceclient ftbfs in focal

2020-04-03 Thread James Page
glanceclient.tests.unit.test_ssl.TestHTTPSVerifyCert.test_v2_requests_valid_cert_no_key

glanceclient.exc.CommunicationError: SSL Error communicating with
https://0.0.0.0:58534/v2/images/image123: [('SSL routines',
'SSL_CTX_use_certificate', 'ca md too weak')]

** Also affects: openssl (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1870074

Title:
  python-glanceclient ftbfs in focal

Status in openssl package in Ubuntu:
  New
Status in python-glanceclient package in Ubuntu:
  In Progress

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963677/+files/buildlog_ubuntu-focal-amd64.python-glanceclient_1%3A2.17.0-0ubuntu2_BUILDING.txt.gz

  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
665, in urlopen
  httplib_response = self._make_request(

File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
376, in _make_request
  self._validate_conn(conn)

File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
996, in _validate_conn
  conn.connect()

File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 352, 
in connect
  self.sock = ssl_wrap_socket(

File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 383, 
in ssl_wrap_socket
  return context.wrap_socket(sock)

File "/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py", 
line 491, in wrap_socket
  raise ssl.SSLError("bad handshake: %r" % e)

  ssl.SSLError: ("bad handshake: SysCallError(-1, 'Unexpected
  EOF')",)

  
  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, 
in send
  resp = conn.urlopen(

File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
719, in urlopen
  retries = retries.increment(

File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 436, 
in increment
  raise MaxRetryError(_pool, url, error or ResponseError(cause))

  urllib3.exceptions.MaxRetryError:
  HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
  with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
  handshake: SysCallError(-1, 'Unexpected EOF')")))

  
  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/<>/glanceclient/common/http.py", line 269, in 
_request
  resp = self.session.request(method,

File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533, 
in request
  resp = self.send(prep, **send_kwargs)

File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646, 
in send
  r = adapter.send(request, **kwargs)

File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514, 
in send
  raise SSLError(e, request=request)

  requests.exceptions.SSLError: HTTPSConnectionPool(host='0.0.0.0',
  port=45175): Max retries exceeded with url: /v2/images/image123
  (Caused by SSLError(SSLError("bad handshake: SysCallError(-1,
  'Unexpected EOF')")))

  
  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/<>/glanceclient/tests/unit/test_ssl.py", line 124, 
in test_v2_requests_cert_verification
  gc.images.get('image123')

File "/<>/glanceclient/v2/images.py", line 198, in get
  return self._get(image_id)

File "/<>/glanceclient/common/utils.py", line 598, in inner
  return RequestIdProxy(wrapped(*args, **kwargs))

File "/<>/glanceclient/v2/images.py", line 191, in _get
  resp, body = self.http_client.get(url, headers=header)

File "/<>/glanceclient/common/http.py", line 315, in get
  return self._request('GET', url, **kwargs)

File "/<>/glanceclient/common/http.py", line 282, in 
_request
  raise exc.CommunicationError(message=message)

  glanceclient.exc.CommunicationError: Error finding address for
  https://0.0.0.0:45175/v2/images/image123:
  HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
  with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
  handshake: SysCallError(-1, 'Unexpected EOF')")))

  
  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in 
patched
  return func(*args, **keywargs)

File "/<>/glanceclient/tests/unit/test_ssl.py", line 128, 

[Touch-packages] [Bug 1552577] Re: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123]

2020-04-03 Thread Daniel van Vugt
No crash reports on any supported releases newer than xenial.

** Changed in: apport (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: gtk+3.0 (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1552577

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_style_provider_private_get_settings(provider=0x0)
  [gtkstyleproviderprivate.c:123]

Status in Apport:
  New
Status in GTK+:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/92c580cf48dae63a366ee45b28a16be710f70347

  ---

  Crash displayed after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport-gtk 2.20-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar  1 22:13:24 2016
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2016-02-21 (10 days ago)
  InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  SegvAnalysis:
   Segfault happened at: 0x7f3a0219cb89:mov(%rbx),%rdi
   PC (0x7f3a0219cb89) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1552577/+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 1870483] Re: package liblxc-common 1:4.0.0-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/man/ja/man1/lxc-user-nic.1.gz', which is also in package lxc-utils

2020-04-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: lxc (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1870483

Title:
  package liblxc-common 1:4.0.0-0ubuntu2 failed to install/upgrade:
  trying to overwrite '/usr/share/man/ja/man1/lxc-user-nic.1.gz', which
  is also in package lxc-utils 3.0.4-0ubuntu2

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: liblxc-common 1:4.0.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  Date: Fri Apr  3 08:00:56 2020
  ErrorMessage: trying to overwrite '/usr/share/man/ja/man1/lxc-user-nic.1.gz', 
which is also in package lxc-utils 3.0.4-0ubuntu2
  InstallationDate: Installed on 2018-04-14 (719 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=0af0a12d-3b1e-4708-89c4-73f666ddc618 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  SourcePackage: lxc
  Title: package liblxc-common 1:4.0.0-0ubuntu2 failed to install/upgrade: 
trying to overwrite '/usr/share/man/ja/man1/lxc-user-nic.1.gz', which is also 
in package lxc-utils 3.0.4-0ubuntu2
  UpgradeStatus: Upgraded to focal on 2020-03-08 (25 days ago)
  defaults.conf:
   lxc.net.0.type = veth
   lxc.net.0.link = lxcbr0
   lxc.net.0.flags = up
   lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1870483/+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 1870427] Re: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127

2020-04-03 Thread Christian Ehrhardt 
Hmm, the pager is called from dpkg to show the diff in your case.
This didn't change and dpkg doesn't do anything magic.

I can only assume that you might have the "pager" itself setup in an odd way.
Due to a bug or intentional - I don't know.

Could you report back the output of:

$ update-alternatives  --display pager

That most likely should look like:
root@f2:~# update-alternatives  --display pager
pager - auto mode
  link best version is /usr/bin/less
  link currently points to /usr/bin/less
  link pager is /usr/bin/pager
  slave pager.1.gz is /usr/share/man/man1/pager.1.gz
/bin/more - priority 50
  slave pager.1.gz: /usr/share/man/man1/more.1.gz
/usr/bin/less - priority 77
  slave pager.1.gz: /usr/share/man/man1/less.1.gz

If that is broken then I could see how the above error could happen.

Finally if that is not a local setup issue, then still it would be more
likely in dpkg and or less (as the common and default pager - both are
auto-installed and I see them updated in your log). I'll re-assign the
bug tasks accordingly.

** Package changed: smartmontools (Ubuntu) => dpkg (Ubuntu)

** Changed in: dpkg (Ubuntu)
   Status: New => Incomplete

** Also affects: less (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to less in Ubuntu.
https://bugs.launchpad.net/bugs/1870427

Title:
  package smartmontools 7.1-1build1 failed to install/upgrade: conffile
  difference visualizer subprocess returned error exit status 127

Status in dpkg package in Ubuntu:
  Incomplete
Status in less package in Ubuntu:
  New

Bug description:
  During an upgrade from eoan to focal I got the following error:

   package:smartmontools:7.1-1build1
   Installing new version of config file /etc/init.d/smartmontools ...

   Configuration file '/etc/smartd.conf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
  What would you like to do about it ?  Your options are:
   Y or I  : install the package maintainer's version
   N or O  : keep your currently-installed version
 D : show the differences between the versions
 Z : start a shell to examine the situation
The default action is to keep your current version.
   *** smartd.conf (Y/I/N/O/D/Z) [default=N] ? d
   sh: 1: pager: not found
   diff: standard output: Broken pipe
   dpkg: error processing package smartmontools (--configure):
conffile difference visualizer subprocess returned error exit status 127

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: smartmontools 7.1-1build1
  Uname: Linux 5.6.2-050602-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  Date: Thu Apr  2 19:58:06 2020
  ErrorMessage: conffile difference visualizer subprocess returned error exit 
status 127
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: /usr/bin/python3.8, Python 3.8.2, python-is-python3, 3.8.2-3
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  2.0.1
  SourcePackage: smartmontools
  Title: package smartmontools 7.1-1build1 failed to install/upgrade: conffile 
difference visualizer subprocess returned error exit status 127
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  mtime.conffile..etc.smartd.conf: 2019-06-28T19:35:09.428956

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1870427/+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 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

2020-04-03 Thread Seyeong Kim
Hello, I uploaded pkg to ppa
https://launchpad.net/~xtrusia/+archive/ubuntu/lp1733321

and checked ppc64el build and testing.

It worked fine without any issue.

Could you please adjust Kleber's debdiff as well?

Thanks a lot.

-- 
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/1733321

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  New
Status in network-manager source package in Focal:
  New

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock. Adding a sleep before calling nmcli fixes the issue.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  
  [Test Case]

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  
  [Regression Potential]

  No regression potential. The fix touches only the testcase shipped
  with the source package and it doesn't change the binary package. The
  sleep time added is very small, so no possibility of causing testcase
  timeout.

  
  [Other Info]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+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 1870489] [NEW] [UX390UAK, Realtek ALC295, Speaker, Internal] Sound is distorted

2020-04-03 Thread Javi
Public bug reported:

Fails with ubuntu 20 beta

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  javier 1440 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  3 09:15:05 2020
InstallationDate: Installed on 2020-04-03 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Audio Interno - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_Type: Digital clip or distortion, or "overdriven" sound
Title: [UX390UAK, Realtek ALC295, Speaker, Internal] Sound is distorted
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/25/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX390UAK.312
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX390UAK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX390UAK.312:bd04/25/2017:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX390UAK
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-03T08:59:03.114969

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1870489

Title:
  [UX390UAK, Realtek ALC295, Speaker, Internal] Sound is distorted

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Fails with ubuntu 20 beta

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  javier 1440 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 09:15:05 2020
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Audio Interno - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [UX390UAK, Realtek ALC295, Speaker, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX390UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX390UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX390UAK.312:bd04/25/2017:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX390UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-03T08:59:03.114969

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870489/+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 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf

2020-04-03 Thread Josh Freeno
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.5
Kernel Version: 5.4.0-21-generic
OS Type: 64-bit
Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz
Memory: 15.4 GiB of RAM

Apr 02 17:53:55 buntu NetworkManager[737]:   [1585868035.8797] 
NetworkManager (version 1.22.10) is starting... (for the first time)
Apr 02 17:53:55 buntu NetworkManager[737]:   [1585868035.8798] Read 
config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 
no-mac-addr-change.conf) (run: 10-globally-managed-devices.conf) (etc: 
default-wifi-po>
Apr 02 17:53:55 buntu NetworkManager[737]:   [1585868035.8798] config: 
unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi] 
of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
Apr 02 17:53:55 buntu NetworkManager[737]:   [1585868035.8798] config: 
unknown key 'ethernet.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'

-- 
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/1826639

Title:
  wpasupplicant: unknown keys in no-mac-addr-change.conf

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  NetworkManager warns that no-mac-addr-change.conf contains unknown
  configuration directives:

  # journalctl | grep no-mac-addr-change
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] Read 
config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 
20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 
10-globally-managed-devices.conf, default-wifi-powersave-on.conf)
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'wifi.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'ethernet.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: wpasupplicant 2:2.6-21ubuntu3
  Uname: Linux 5.0.9-050009-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 27 13:15:27 2019
  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/1826639/+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 1869629] Re: please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns

2020-04-03 Thread Christian Ehrhardt 
Lol - sorry for the noise after seeing another case like that I had to realize 
that focal-unapproved just is multiple pages now :-)
It is on the second page still waiting for the release team to accept after 
beta is out.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1869629

Title:
  please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns

Status in snapd:
  Triaged
Status in apparmor package in Ubuntu:
  Fix Committed
Status in chrony package in Ubuntu:
  Invalid

Bug description:
  In focal users of mdns get denials in apparmor confined applications.
  An exampel can be found in the original bug below.

  It seems it is a common pattern, see
  https://github.com/lathiat/nss-mdns#etcmdnsallow

  Therefore I'm asking to add
 /etc/mdns.allow r,
  to the file
 /etc/apparmor.d/abstractions/mdns"
  by default.

  --- original bug ---

  Many repetitions of

  audit: type=1400 audit(1585517168.705:63): apparmor="DENIED"
  operation="open" profile="/usr/sbin/chronyd" name="/etc/mdns.allow"
  pid=1983815 comm="chronyd" requested_mask="r" denied_mask="r"
  fsuid=123 ouid=0

  in log.  I use libnss-mdns for .local name resolution, so
  /etc/nsswitch.conf contains

  hosts:  files mdns [NOTFOUND=return] myhostname dns

  and /etc/mnds.allow contains the domains to resolve with mDNS (in may
  case, "local." and "local"; see /usr/share/doc/libnss-
  mdns/README.html.)

  Presumably cronyd calls a gethostbyX() somewhere, thus eventually
  trickling down through the name service switch and opening
  /etc/mdns.allow, which the AppArmor profile in the chrony package does
  not allow.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: chrony 3.5-6ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  Date: Sun Mar 29 15:02:39 2020
  InstallationDate: Installed on 2020-03-26 (3 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200326)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: chrony
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1869629/+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 1869629] Re: please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns

2020-04-03 Thread Christian Ehrhardt 
@Jamie/John - did you let this upload cancel from focal-unapproved?
It was, but is no more in -unapproved - but it also does not show up in 
-proposed.
I'm confused and was wondering if this was lost in work of the release-team or 
if you cancelled (and plan to re-upload) it intentionally?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1869629

Title:
  please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns

Status in snapd:
  Triaged
Status in apparmor package in Ubuntu:
  Fix Committed
Status in chrony package in Ubuntu:
  Invalid

Bug description:
  In focal users of mdns get denials in apparmor confined applications.
  An exampel can be found in the original bug below.

  It seems it is a common pattern, see
  https://github.com/lathiat/nss-mdns#etcmdnsallow

  Therefore I'm asking to add
 /etc/mdns.allow r,
  to the file
 /etc/apparmor.d/abstractions/mdns"
  by default.

  --- original bug ---

  Many repetitions of

  audit: type=1400 audit(1585517168.705:63): apparmor="DENIED"
  operation="open" profile="/usr/sbin/chronyd" name="/etc/mdns.allow"
  pid=1983815 comm="chronyd" requested_mask="r" denied_mask="r"
  fsuid=123 ouid=0

  in log.  I use libnss-mdns for .local name resolution, so
  /etc/nsswitch.conf contains

  hosts:  files mdns [NOTFOUND=return] myhostname dns

  and /etc/mnds.allow contains the domains to resolve with mDNS (in may
  case, "local." and "local"; see /usr/share/doc/libnss-
  mdns/README.html.)

  Presumably cronyd calls a gethostbyX() somewhere, thus eventually
  trickling down through the name service switch and opening
  /etc/mdns.allow, which the AppArmor profile in the chrony package does
  not allow.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: chrony 3.5-6ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  Date: Sun Mar 29 15:02:39 2020
  InstallationDate: Installed on 2020-03-26 (3 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200326)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: chrony
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1869629/+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 1870442] Re: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on.

2020-04-03 Thread Sebastien Bacher
Thank you for your bug report. Was it ony a one time issue? Can you add
your journalctl log from that session?

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

-- 
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/1870442

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   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/1870442/+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 1870483] [NEW] package liblxc-common 1:4.0.0-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/man/ja/man1/lxc-user-nic.1.gz', which is also in package lxc-util

2020-04-03 Thread Daniel Holbach
Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: liblxc-common 1:4.0.0-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
Date: Fri Apr  3 08:00:56 2020
ErrorMessage: trying to overwrite '/usr/share/man/ja/man1/lxc-user-nic.1.gz', 
which is also in package lxc-utils 3.0.4-0ubuntu2
InstallationDate: Installed on 2018-04-14 (719 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=0af0a12d-3b1e-4708-89c4-73f666ddc618 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
PythonDetails: N/A
SourcePackage: lxc
Title: package liblxc-common 1:4.0.0-0ubuntu2 failed to install/upgrade: trying 
to overwrite '/usr/share/man/ja/man1/lxc-user-nic.1.gz', which is also in 
package lxc-utils 3.0.4-0ubuntu2
UpgradeStatus: Upgraded to focal on 2020-03-08 (25 days ago)
defaults.conf:
 lxc.net.0.type = veth
 lxc.net.0.link = lxcbr0
 lxc.net.0.flags = up
 lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apparmor apport-package focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1870483

Title:
  package liblxc-common 1:4.0.0-0ubuntu2 failed to install/upgrade:
  trying to overwrite '/usr/share/man/ja/man1/lxc-user-nic.1.gz', which
  is also in package lxc-utils 3.0.4-0ubuntu2

Status in lxc package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: liblxc-common 1:4.0.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  Date: Fri Apr  3 08:00:56 2020
  ErrorMessage: trying to overwrite '/usr/share/man/ja/man1/lxc-user-nic.1.gz', 
which is also in package lxc-utils 3.0.4-0ubuntu2
  InstallationDate: Installed on 2018-04-14 (719 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=0af0a12d-3b1e-4708-89c4-73f666ddc618 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  SourcePackage: lxc
  Title: package liblxc-common 1:4.0.0-0ubuntu2 failed to install/upgrade: 
trying to overwrite '/usr/share/man/ja/man1/lxc-user-nic.1.gz', which is also 
in package lxc-utils 3.0.4-0ubuntu2
  UpgradeStatus: Upgraded to focal on 2020-03-08 (25 days ago)
  defaults.conf:
   lxc.net.0.type = veth
   lxc.net.0.link = lxcbr0
   lxc.net.0.flags = up
   lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1870483/+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