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

2020-08-06 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1890772/+attachment/5399472/+files/Dependencies.txt

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

Title:
  Some external 4K monitor is not working properly

Status in OEM Priority Project:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1890772/+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 1890772] xdpyinfo.txt

2020-08-06 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1890772/+attachment/5399488/+files/xdpyinfo.txt

** Description changed:

  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778
  
  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.
  
  `xrandr --output DP-3 --set "max bpc" 8`
  
  Would like to open this bug to open discussion for enhancing user experience.
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
-  # This is the distribution channel descriptor for the OEM CDs
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
-Subsystem: Dell Device [1028:09fc]
-Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
+  Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
+    Subsystem: Dell Device [1028:09fc]
+    Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
- dmi.bios.date: 08/03/2020
- dmi.bios.vendor: Dell Inc.
- dmi.bios.version: 0.6.0
- dmi.board.vendor: Dell Inc.
- dmi.chassis.type: 10
- dmi.chassis.vendor: Dell Inc.
- dmi.modalias: 
dmi:bvnDellInc.:bvr0.6.0:bd08/03/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
- dmi.product.family: Vostro
- dmi.product.name: Vostro 5301
- dmi.product.sku: 09FC
- dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

Title:
  Some external 4K monitor is not working properly

Status in OEM Priority Project:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  

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

2020-08-06 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1890772/+attachment/5399480/+files/ProcCpuinfoMinimal.txt

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

Title:
  Some external 4K monitor is not working properly

Status in OEM Priority Project:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1890772/+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 1890772] XorgLogOld.txt

2020-08-06 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1890772/+attachment/5399486/+files/XorgLogOld.txt

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

Title:
  Some external 4K monitor is not working properly

Status in OEM Priority Project:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1890772/+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 1890772] ProcCpuinfo.txt

2020-08-06 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1890772/+attachment/5399479/+files/ProcCpuinfo.txt

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

Title:
  Some external 4K monitor is not working properly

Status in OEM Priority Project:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1890772/+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 1890772] Lsusb-v.txt

2020-08-06 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1890772/+attachment/5399478/+files/Lsusb-v.txt

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

Title:
  Some external 4K monitor is not working properly

Status in OEM Priority Project:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1890772/+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 1890772] DpkgLog.txt

2020-08-06 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1890772/+attachment/5399473/+files/DpkgLog.txt

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

Title:
  Some external 4K monitor is not working properly

Status in OEM Priority Project:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1890772/+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 1890772] ProcEnviron.txt

2020-08-06 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1890772/+attachment/5399481/+files/ProcEnviron.txt

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

Title:
  Some external 4K monitor is not working properly

Status in OEM Priority Project:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1890772/+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 1890772] Lspci-vt.txt

2020-08-06 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1890772/+attachment/5399475/+files/Lspci-vt.txt

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

Title:
  Some external 4K monitor is not working properly

Status in OEM Priority Project:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1890772/+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 1890772] Lsusb-t.txt

2020-08-06 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1890772/+attachment/5399477/+files/Lsusb-t.txt

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

Title:
  Some external 4K monitor is not working properly

Status in OEM Priority Project:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1890772/+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 1890772] Lspci.txt

2020-08-06 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1890772/+attachment/5399474/+files/Lspci.txt

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

Title:
  Some external 4K monitor is not working properly

Status in OEM Priority Project:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1890772/+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 1890772] Lsusb.txt

2020-08-06 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1890772/+attachment/5399476/+files/Lsusb.txt

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

Title:
  Some external 4K monitor is not working properly

Status in OEM Priority Project:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1890772/+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 1890411] Re: [bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

2020-08-06 Thread Daniel van Vugt
Not that I can think of...

I forgot to mention: i965_dri isn't used in later Ubuntu releases. It's
been replaced by a new driver called 'iris_dri'.

You will probably find that Ubuntu 20.04.1 works better:
https://releases.ubuntu.com/20.04/

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

Title:
  [bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  When ubuntu starts up, gdm3 does not start due to a crash in the the
  xserver:

  [  1271.342] (II) SELinux: Disabled on system
  [  1271.346] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context_profile
  [  1271.346] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
  [  1271.346] (II) AIGLX: enabled GLX_INTEL_swap_event
  [  1271.346] (II) AIGLX: enabled GLX_SGI_swap_control
  [  1271.346] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
  [  1271.346] (II) AIGLX: enabled GLX_ARB_fbconfig_float
  [  1271.346] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
  [  1271.346] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context_robustness
  [  1271.346] (II) AIGLX: Loaded and initialized i965
  [  1271.346] (II) GLX: Initialized DRI2 GL provider for screen 0
  [  1271.348] (II) modeset(0): Damage tracking initialized
  [  1271.348] (II) modeset(0): Setting screen physical size to 508 x 317
  [  1271.352] (EE) 
  [  1271.352] (EE) Backtrace:
  [  1271.352] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5649b579bacd]
  [  1271.352] (EE) 1: /usr/lib/xorg/Xorg (0x5649b55e3000+0x1bc869) 
[0x5649b579f869]
  [  1271.352] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f5c7d0a5000+0x128a0) [0x7f5c7d0b78a0]
  [  1271.352] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x8e8652) [0x7f5c784e2652]
  [  1271.352] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x8e877f) [0x7f5c784e277f]
  [  1271.352] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x122916) [0x7f5c77d1c916]
  [  1271.352] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x1189bc) [0x7f5c77d129bc]
  [  1271.352] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x109c1b) [0x7f5c77d03c1b]
  [  1271.352] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x279558) [0x7f5c77e73558]
  [  1271.352] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x2796e3) [0x7f5c77e736e3]
  [  1271.352] (EE) 10: /usr/lib/xorg/modules/libglamoregl.so 
(0x7f5c79937000+0x1a1ab) [0x7f5c799511ab]
  [  1271.352] (EE) 11: /usr/lib/xorg/Xorg (0x5649b55e3000+0x13ed03) 
[0x5649b5721d03]
  [  1271.352] (EE) 12: /usr/lib/xorg/Xorg (miPaintWindow+0x22f) 
[0x5649b577fd1f]
  [  1271.352] (EE) 13: /usr/lib/xorg/Xorg (miWindowExposures+0x112) 
[0x5649b577fa62]
  [  1271.352] (EE) 14: /usr/lib/xorg/Xorg (0x5649b55e3000+0xa9c41) 
[0x5649b568cc41]
  [  1271.352] (EE) 15: /usr/lib/xorg/Xorg (MapWindow+0x114) [0x5649b5665d04]
  [  1271.352] (EE) 16: /usr/lib/xorg/Xorg (0x5649b55e3000+0x56e79) 
[0x5649b5639e79]
  [  1271.352] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xe7) [0x7f5c7ccd5b97]
  [  1271.352] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x5649b5623b8a]
  [  1271.352] (EE) 
  [  1271.352] (EE) Segmentation fault at address 0x4
  [  1271.352] (EE) 
  Fatal server error:
  [  1271.352] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [  1271.352] (EE) 
  [  1271.352] (EE) 

  As i965_dri.so is part of the libgl-mesa-dri package I downgraded this
  specific package from version 20.0.8-0ubuntu1~18.04.1 back to
  19.2.8-0ubuntu0~18.04.3.

  This solves the problem. So I suspect that the problem is in this
  specific package.

  My machine is (uname):
  4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 
x86_64 GNU/Linux

  (lspci)
  00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller 
(rev 06)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 05)
  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d5)
  00:1c.2 PCI bridge: Intel Corporation 8 

[Touch-packages] [Bug 1890593] Re: Xorg freeze

2020-08-06 Thread Daniel van Vugt
This sounds kind of like bug 1872159 or bug 1871641.

Can you please try editing /etc/default/grub and remove 'splash' then:

  sudo update-grub

and reboot.


** Tags added: hybrid nvidia

** Summary changed:

- Xorg freeze
+ [nvidia] Boot freeze - can't get to login screen without unplugging HDMI first

** Package changed: xorg (Ubuntu) => plymouth (Ubuntu)

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

** Also affects: gdm3 (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/1890593

Title:
  [nvidia] Boot freeze - can't get to login screen without unplugging
  HDMI first

Status in gdm3 package in Ubuntu:
  New
Status in plymouth package in Ubuntu:
  Incomplete

Bug description:
  Just installed ubuntu  20.04 and I am stuck on ubuntu with a spining
  logo. If I go to other tty and unplug the HDMI screens I can get to
  the login screen, Otherwise I cant. I did checked the md5sum of the
  iso before installing and its was correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  6 14:29:04 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo ThinkPad T570 [17aa:2248]
 Subsystem: Lenovo GM108GLM [Quadro M520 Mobile] [17aa:2248]
  InstallationDate: Installed on 2020-08-05 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20HCS0660M
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=be1cbba6-c044-4d36-a6f4-fe872353a538 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1VET49W (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HCS0660M
  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:bvrN1VET49W(1.39):bd05/08/2019:svnLENOVO:pn20HCS0660M:pvrThinkPadP51s:rvnLENOVO:rn20HCS0660M:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad THINKPAD P51S
  dmi.product.name: 20HCS0660M
  dmi.product.sku: LENOVO_MT_20HC_BU_Think_FM_ThinkPad THINKPAD P51S
  dmi.product.version: ThinkPad P51s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1890593/+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 1890772] XorgLog.txt

2020-08-06 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1890772/+attachment/5399485/+files/XorgLog.txt

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

Title:
  Some external 4K monitor is not working properly

Status in OEM Priority Project:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1890772/+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 1890772] UdevDb.txt

2020-08-06 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1890772/+attachment/5399484/+files/UdevDb.txt

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

Title:
  Some external 4K monitor is not working properly

Status in OEM Priority Project:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1890772/+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 1890772] ProcModules.txt

2020-08-06 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1890772/+attachment/5399483/+files/ProcModules.txt

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

Title:
  Some external 4K monitor is not working properly

Status in OEM Priority Project:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1890772/+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 1890772] Xrandr.txt

2020-08-06 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1890772/+attachment/5399487/+files/Xrandr.txt

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

Title:
  Some external 4K monitor is not working properly

Status in OEM Priority Project:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1890772/+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 1890772] ProcInterrupts.txt

2020-08-06 Thread Kai-Chuan Hsieh
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1890772/+attachment/5399482/+files/ProcInterrupts.txt

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

Title:
  Some external 4K monitor is not working properly

Status in OEM Priority Project:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1890772/+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 1890772] [NEW] Some external 4K monitor is not working properly

2020-08-06 Thread Kai-Chuan Hsieh
Public bug reported:

The bug is originated from,
https://bugs.launchpad.net/somerville/+bug/1887915/
https://bugs.launchpad.net/somerville/+bug/1886778

It has some problem when user connect to external 4K monitor with refresh rate 
60.
The problem can be solved by lower the bpc, or lower the refresh rate.

`xrandr --output DP-3 --set "max bpc" 8`

Would like to open this bug to open discussion for enhancing user experience.
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
DistroCodename: focal
DistroRelease: Ubuntu 20.04
DistroVariant: ubuntu
DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:09fc]
   Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
InstallationDate: Installed on 2020-08-07 (0 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
MachineType: Dell Inc. Vostro 5301
Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
Tags: third-party-packages focal ubuntu
Uname: Linux 5.6.0-1021-oem x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 08/03/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.6.0
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr0.6.0:bd08/03/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Vostro
dmi.product.name: Vostro 5301
dmi.product.sku: 09FC
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: apport-collected focal third-party-packages 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/1890772

Title:
  Some external 4K monitor is not working properly

Status in xorg package in Ubuntu:
  New

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:09fc]
 Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: 

[Touch-packages] [Bug 1890772] Re: Some external 4K monitor is not working properly

2020-08-06 Thread Daniel van Vugt
There doesn't seem to be any external monitor connected to this machine,
or any 'DP-3' connector.

Please attach 'xrandr --verbose' info with a monitor connected showing
the problem, or please open a new bug from the affected machine.

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

** Changed in: oem-priority
   Status: New => Incomplete

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

Title:
  Some external 4K monitor is not working properly

Status in OEM Priority Project:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1890772/+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 1560094] Re: Starting bluez service is denied

2020-08-06 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Starting bluez service is denied

Status in bluez package in Ubuntu:
  Expired

Bug description:
  If snappy core is updated in the background (on Raspberry Pi 2), and
  then bluez installed, starting the service is failing.

  
  Denials:

  [   45.955490] audit: type=1400 audit(1458574955.667:11): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=834 comm="c0
  [   46.197608] audit: type=1326 audit(1458574955.907:12): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=831 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.275680] audit: type=1400 audit(1458574955.987:13): apparmor="DENIED" 
operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=829 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1
  [   46.276483] audit: type=1326 audit(1458574955.987:14): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=829 comm="bluetoothd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000
  [   46.412021] audit: type=1326 audit(1458574956.123:15): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=839 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.504308] audit: type=1400 audit(1458574956.215:16): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=842 comm="c0
  [   46.520137] audit: type=1400 audit(1458574956.231:17): apparmor="DENIED" 
operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=841 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1
  [   46.520800] audit: type=1326 audit(1458574956.231:18): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=841 comm="bluetoothd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000
  [   46.625293] audit: type=1326 audit(1458574956.335:19): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=844 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.721080] audit: type=1400 audit(1458574956.431:20): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=847 comm="c2

  If trying to start bluetootctl:

  [  582.205066] audit: type=1400 audit(1458575491.915:31): apparmor="DENIED" 
operation="connect" profile="bluez5_bluetoothctl_5.37-2-armhf" 
name="/run/dbus/system_bus_socket" pid=993 comm="bluetoothctl" re0
  [bluetooth]# 

  
  ubuntu@localhost:~$ snappy list
  NameDate   Version  Developer 
  bluez5  2016-02-04 5.37-2-armhf canonical 
  canonical-pi2   2016-02-02 3.0  canonical 
  canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical 
  ubuntu-core 2016-03-08 16.04.0-15.armhf canonical 
  ubuntu@localhost:~$ 

  ubuntu@localhost:~$ snappy info
  release: core/rolling
  architecture: armhf
  frameworks: bluez5.canonical
  apps:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1560094/+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 1871641] Re: Ubuntu never finishes booting: A start job is running for Hold until boot process finishes up (3min 7s / no limit) -- removing 'splash' kernel parm fixes it

2020-08-06 Thread Daniel van Vugt
Maybe related to bug 1872159, which supposedly happens when extra
monitors are connected. Although I doubt that's the only requirement to
make the bug happen.

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

Title:
  Ubuntu never finishes booting: A start job is running for Hold until
  boot process finishes up (3min 7s / no limit) -- removing 'splash'
  kernel parm fixes it

Status in plymouth package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Boot process freezes at the splash screen and nothing happens after
  that. The computer can be suspended and it is able to return from
  suspend. Boot is possible by pressing escape early in the process to
  bypass plymouth.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: plymouth 0.9.4git20200323-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-0ubuntu24
  Architecture: amd64
  Date: Wed Apr  8 14:30:13 2020
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  InstallationDate: Installed on 2020-04-08 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: LENOVO 7469A23
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=e12af5fd-b700-4292-8727-70345cb61c8e ro quiet splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=e12af5fd-b700-4292-8727-70345cb61c8e ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6DET72WW (3.22 )
  dmi.board.name: 7469A23
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6DET72WW(3.22):bd10/25/2012:svnLENOVO:pn7469A23:pvrThinkPadX200s:rvnLENOVO:rn7469A23:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X200s
  dmi.product.name: 7469A23
  dmi.product.version: ThinkPad X200s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1871641/+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 1890772] Re: Some external 4K monitor is not working properly

2020-08-06 Thread Shih-Yuan Lee
** Also affects: oem-priority
   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/1890772

Title:
  Some external 4K monitor is not working properly

Status in OEM Priority Project:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  The bug is originated from,
  https://bugs.launchpad.net/somerville/+bug/1887915/
  https://bugs.launchpad.net/somerville/+bug/1886778

  It has some problem when user connect to external 4K monitor with refresh 
rate 60.
  The problem can be solved by lower the bpc, or lower the refresh rate.

  `xrandr --output DP-3 --set "max bpc" 8`

  Would like to open this bug to open discussion for enhancing user experience.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:09fc]
     Subsystem: Dell GP107M [GeForce MX350] [1028:09fc]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: xorg 1:7.7+19ubuntu14 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Tags: third-party-packages focal ubuntu
  Uname: Linux 5.6.0-1021-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1890772/+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 1890541] [NEW] package apport 2.20.11-0ubuntu27 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2020-08-06 Thread Erdenesaikhan
Public bug reported:

1

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: apport 2.20.11-0ubuntu27
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
AptOrdering:
 gparted-common:amd64: Install
 gparted:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
CrashReports: 600:0:125:342985:2020-08-06 14:51:38.472868204 +0800:2020-08-06 
14:51:39.472868204 +0800:/var/crash/apport.0.crash
Date: Thu Aug  6 14:51:38 2020
DuplicateSignature:
 package:apport:2.20.11-0ubuntu27
 Unpacking gparted (1.0.0-0.1build1) ...
 dpkg: error processing package apport (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2020-08-06 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: apport
Title: package apport 2.20.11-0ubuntu27 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package apport 2.20.11-0ubuntu27 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  1

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  AptOrdering:
   gparted-common:amd64: Install
   gparted:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports: 600:0:125:342985:2020-08-06 14:51:38.472868204 +0800:2020-08-06 
14:51:39.472868204 +0800:/var/crash/apport.0.crash
  Date: Thu Aug  6 14:51:38 2020
  DuplicateSignature:
   package:apport:2.20.11-0ubuntu27
   Unpacking gparted (1.0.0-0.1build1) ...
   dpkg: error processing package apport (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2020-08-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: apport
  Title: package apport 2.20.11-0ubuntu27 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1890541/+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 1872118] Re: DHCP Cluster crashes after a few hours

2020-08-06 Thread Andrew Welham
Not sure if this helps i coped the coredump file to a test system install gdb
and got the following
# gdb /usr/sbin/dhcpd ./CoreDump
GNU gdb (Ubuntu 9.1-0ubuntu1) 9.1
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/dhcpd...
(No debugging symbols found in /usr/sbin/dhcpd)
[New LWP 63464]
[New LWP 63463]
[New LWP 63448]
[New LWP 63465]

warning: Unexpected size of section `.reg-xstate/63464' in core file.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dh'.
Program terminated with signal SIGABRT, Aborted.

warning: Unexpected size of section `.reg-xstate/63464' in core file.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
[Current thread is 1 (Thread 0x7f0ed5c48700 (LWP 63464))]

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

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
 

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

2020-08-06 Thread Andrew Welham
Yes i restarted isc-dhcp-server with systemctl restart isc-dhcp-server (
even tried a reboot once)


# dpkg -l | grep ppa1
ii  isc-dhcp-server  4.4.1-2.1ubuntu6~ppa1  
amd64ISC DHCP server for automatic IP address assignment
ii  libdns-export11091:9.11.16+dfsg-3~ppa1  
amd64Exported DNS Shared Library
ii  libirs-export161 1:9.11.16+dfsg-3~ppa1  
amd64Exported IRS Shared Library
ii  libisc-export1105:amd64  1:9.11.16+dfsg-3~ppa1  
amd64Exported ISC Shared Library
ii  libisccfg-export163  1:9.11.16+dfsg-3~ppa1  
amd64Exported ISC CFG Shared Library

# systemctl status isc-dhcp-server
● isc-dhcp-server.service - ISC DHCP IPv4 server
 Loaded: loaded (/lib/systemd/system/isc-dhcp-server.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Thu 2020-08-06 07:26:09 BST; 2min 39s ago
   Docs: man:dhcpd(8)
   Main PID: 42301 (dhcpd)
  Tasks: 4 (limit: 9569)
 Memory: 7.6M
 CGroup: /system.slice/isc-dhcp-server.service
 └─42301 dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf

Aug 06 07:28:47 gw2-focal dhcpd[42301]: Remove host declaration test or remove 
192.168.0.90
Aug 06 07:28:47 gw2-focal dhcpd[42301]: from the dynamic address pool for 
192.168.0.0/24
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.0.90 
(192.168.0.2) from MACREMOVED via ens3: ignored (not authoritative).
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.6.161 
(192.168.6.3) from MACREMOVED (test) via ens13: ignored (not authoritative).
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.6.161 
(192.168.6.3) from MACREMOVED (test) via ens12: ignored (not authoritative).
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.6.161 
(192.168.6.3) from MACREMOVED (test) via ens11: ignored (not authoritative).
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.6.161 
(192.168.6.3) from MACREMOVED (test) via ens10: ignored (not authoritative).
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.6.161 
(192.168.6.3) from MACREMOVED (test) via ens9: ignored (not authoritative).
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.6.161 
(192.168.6.3) from MACREMOVED (test) via ens8: ignored (not authoritative).
Aug 06 07:28:47 gw2-focal dhcpd[42301]: DHCPREQUEST for 192.168.6.161 
(192.168.6.3) from MACREMOVED (test) via ens3: ignored (not authoritative).

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

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-08-06 Thread gruberm
I'm watching this error since about 10 months hoping that this would be fixed 
before the 20.04 release.
Now we're almost 4 months past the release date and it's still there.
Given that the fix is quite easy, I'm wondering why this is still an unresolved 
issue.

-- 
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:
  Invalid
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.

  ---

  However, we currently believe that the decoding error reported in
  dmesg is actually harmless and has no impact on usability on the
  system.

  Switching from lz4 to gzip compression, simply papers over the
  warning, without any benefits, and slows down boot.

  Kernel should be fixed to correctly parse lz4 compressed initrds, or
  at least lower the warning, to not be user visible as an error.

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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

2020-08-06 Thread yossisynett
Thanks for the tip, also got this working with the liquorix kernel but
didn't have to update the firmware - used the current version in ubuntu
20.04

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871794/+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 1890541] Re: package apport 2.20.11-0ubuntu27 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2020-08-06 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package apport 2.20.11-0ubuntu27 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  1

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  AptOrdering:
   gparted-common:amd64: Install
   gparted:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports: 600:0:125:342985:2020-08-06 14:51:38.472868204 +0800:2020-08-06 
14:51:39.472868204 +0800:/var/crash/apport.0.crash
  Date: Thu Aug  6 14:51:38 2020
  DuplicateSignature:
   package:apport:2.20.11-0ubuntu27
   Unpacking gparted (1.0.0-0.1build1) ...
   dpkg: error processing package apport (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2020-08-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: apport
  Title: package apport 2.20.11-0ubuntu27 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1890541/+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 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop

2020-08-06 Thread Hui Wang
OK, got it, will upload for G.
thx.

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

Title:
  Make digital mic on the AMD Renoir machines work under gnome desktop

Status in alsa-lib package in Ubuntu:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in alsa-lib source package in Focal:
  New
Status in alsa-ucm-conf source package in Focal:
  New
Status in pulseaudio source package in Focal:
  New
Status in alsa-lib source package in Groovy:
  New
Status in alsa-ucm-conf source package in Groovy:
  New
Status in pulseaudio source package in Groovy:
  New

Bug description:
  [Impact]
  On the LENOVO AMD Renoir machines, there is a digital mic directly
  connected to the APU instead of the codec, so there are two separate
  sound cards in the system, one is for analogue codec driven by hda
  driver, the other is for the dmic driven by ASoC acp driver.

  The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't
  support this design yet, it could support all audio devices on the codec
  well, but it doesn't support that dmic well. In the gnome-control-center,
  the dmic becomes two input devices: analog input and multichannel input,
  and users can only record sound from analog input, the multichannel input
  can't function at all. Besides this issue, there is another issue, after
  users plug an external mic, the external mic can't replace the dmic
  automatically, this gives users a bad experience since this behaviour is
  different from the other audio designs.

  [Fix for pulseaudio]
  backport 3 patches:
  2 of them from upstream
  device-port: queue CARD CHANGE event before update default sink
  alsa: adjust ucm sink/source priority according to ports priority
  1 of them from a merge request:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305

  [Fix for alsa-ucm-conf]
  backport 14 patches:
  11 of them from upstream:
  ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch
  ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch
  sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch
  ucm.conf-add-support-for-the-kernel-module-name-tree.patch
  sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch
  sof-soundwire-initial-UCM2-version.patch
  sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch
  sof-soundwire-rewrite-for-syntax-3.patch
  HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch
  Fix-invalid-Regex-Type-in-various-Condition-blocks.patch
  hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch
  3 of them from a merge request:
  https://github.com/alsa-project/alsa-ucm-conf/pull/41

  [Fix for alsa-lib]
  backport 47 patches from upstream:
  Enabled-extended-namehints-in-alsa.conf.patch
  conf-add-snd_config_is_array-function.patch
  topology-use-snd_config_is_array-function.patch
  ucm-merge-the-array-items-from-the-condition-blocks.patch
  ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch
  ucm-execute-SectionDefaults-lately-when-the-first-ve.patch
  ucm-handle-set-_once-command.patch
  ucm-handle-set-_defaults-command.patch
  ucm-initialize-mgr-once_list.patch
  ucm-fix-SectionOnce-comment.patch
  ucm-fix-compilation-error-in-set_defaults_user.patch
  ucm-rename-SectionOnce-to-BootSequence.patch
  ucm-rename-_once-command-to-_boot-command.patch
  ucm-configuration-implement-in-place-Include.patch
  ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch
  ucm-config-substitute-File-string-to-allow-variables.patch
  ucm-configuration-allow-to-define-the-configuration-.patch
  ucm-configuration-add-DefineRegex.patch
  ucm-substitute-arguments-in-sequences.patch
  ucm-allow-syntax-version-3.patch
  ucm-config-change-the-in-place-include-evaluation-or.patch
  ucm-allow-to-specify-the-toplevel-directory-using-as.patch
  ucm-substitute-also-value-strings.patch
  ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch
  ucm-String-condition-implement-Empty.patch
  ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch
  ucm-substitute-OpenName.patch
  ucm-substitute-CardNumber.patch
  ucm-implement-the-toplevel-ucm-configuration-file-pa.patch
  ucm-substitute-device-modifier-names-too.patch
  ucm-substitute-device-strings-in-the-device-lists.patch
  ucm-substitute-component-sequence-string.patch
  ucm-substitute-verb-name-and-file-field.patch
  ucm-substitute-Comment-in-Transition-and-Device.patch
  ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch
  ucm-substitute-arguments-in-sequences-only-for-synta.patch
  ucm-shuffle-code-in-compound_merge.patch
  ucm-implement-CardIdByName-substitution.patch
  ucm-allow-to-ignore-errors-for-the-value-substitutio.patch
  ucm-allow-to-use-the-defined-variables-in-the-substi.patch
  ucm-implement-CardNumberByName-substitution.patch
  ucm-fix-the-possible-buffer-overflow-substitution.patch
  

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

2020-08-06 Thread Andrew Welham
Jorge, Here you go

andrew@gw2-focal:~$ ldd /usr/sbin/dhcpd | grep export
libirs-export.so.161 => /lib/x86_64-linux-gnu/libirs-export.so.161 
(0x00   
 007fa030e7b000)
libdns-export.so.1109 => /lib/x86_64-linux-gnu/libdns-export.so.1109 
(0x 
   7fa030c46000)
libisc-export.so.1105 => /lib/x86_64-linux-gnu/libisc-export.so.1105 
(0x 
   7fa030bcf000)
libisccfg-export.so.163 => 
/lib/x86_64-linux-gnu/libisccfg-export.so.163   
  
(0x7fa03098b000)
andrew@gw2-focal:~$ ldd /usr/sbin/dhcpd | grep export
libirs-export.so.161 => /lib/x86_64-linux-gnu/libirs-export.so.161 
(0x7fa9fbeaf000)
libdns-export.so.1109 => /lib/x86_64-linux-gnu/libdns-export.so.1109 
(0x7fa9fbc7a000)
libisc-export.so.1105 => /lib/x86_64-linux-gnu/libisc-export.so.1105 
(0x7fa9fbc03000)
libisccfg-export.so.163 => 
/lib/x86_64-linux-gnu/libisccfg-export.so.163 (0x7fa9fb9bf000)
andrew@gw2-focal:~$ dpkg -S /lib/x86_64-linux-gnu/libisc-export.so.1105
libisc-export1105:amd64: /lib/x86_64-linux-gnu/libisc-export.so.1105
andrew@gw2-focal:~$ apt-cache policy libisc-export1105  | grep -i ppa
  Installed: 1:9.11.16+dfsg-3~ppa1
  Candidate: 1:9.11.16+dfsg-3~ppa1
 *** 1:9.11.16+dfsg-3~ppa1 500
500 http://ppa.launchpad.net/niedbalski/fix-1872118/ubuntu focal/main 
amd64 Packages
andrew@gw2-focal:~$ ls -als  /lib/x86_64-linux-gnu/libirs-export.so.161

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

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 

[Touch-packages] [Bug 1872560] Re: integer overflow in whoopsie 0.2.69

2020-08-06 Thread Brian Murray
** Tags removed: rls-ff-incoming

** Changed in: whoopsie (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

** Changed in: whoopsie (Ubuntu Groovy)
   Status: Confirmed => Fix Committed

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

Title:
  integer overflow in whoopsie 0.2.69

Status in whoopsie package in Ubuntu:
  Fix Committed
Status in whoopsie source package in Xenial:
  Fix Released
Status in whoopsie source package in Bionic:
  Fix Released
Status in whoopsie source package in Eoan:
  Won't Fix
Status in whoopsie source package in Focal:
  Fix Released
Status in whoopsie source package in Groovy:
  Fix Committed

Bug description:
  Hi,

  I have found a security issue on whoopsie 0.2.69 and earlier.

  ## Vulnerability in whoopsie
  - whoopsie 0.2.69 and earlier have a heap-based buffer overflow 
vulnerability. 
  - An attacker can cause a denial of service (memory corruption and 
application crash) via a crafted .crash file.

  
  ## Basic
  When a program has been crashed, Linux system tries to create a '.crash' file 
on '/var/crash/' directory with python script located in 
'/usr/share/apport/apport'. 
  The file contains a series of system crash information including core dump, 
syslog, stack trace, memory map info, etc.
  After the creation of '.crash' file, whoopsie extracts the above information 
from the '.crash' file and encodes it into binary json (bson) format.
  Lastly, whoopsie forwards the data to a remotely connected Ubuntu Error 
Report system.

   
  ## Vulnerability
  Unfortunately, we have found a heap-based buffer overflow vulnerability 
during the encoding, when whoopsie attempts to bsonify with crafted crash file.
  The data in '.crash' file is stored in key-value form and the whoopsie 
separately measures the length of 'key' and 'value' to allocate memory region 
during the encoding. 
  A heap-based buffer overflow can occur when an integer overflow happens on a 
variable that contains length of 'key'. 
  FYI, a issue to that raised by 'value' is well covered by performing 
exception handling.

  
@[bson.c:663][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n663]

  const uint32_t len = strlen( name ) + 1;

  - Integer overflow occurs when length of ‘name’ exceeds INT32_MAX value. 
  - Here, ‘name’ indicates the ‘key’ data in ‘.crash’ file.

  
@[bson.c:627][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n627]

  b->data = bson_realloc( b->data, new_size );

  - Unexpected small memory region is allocated due to above integer
  overflow.

  
@[bson.c:680][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n680]

  bson_append( b, name, len );

  - Memory corruption happens when unexpected small memory region is
  allocated.

  
  ## Attack Scenario
  1) Create a fake.crash file
  - '.crash' file is composed of the following format: 'key : value'.
  - To cause the overflow attack, the size of 'key' should be in double amount 
of INT32_MAX.
  - The size of 'value' doesn’t matter, but not zero length.

  $ python -c "print('A' * 0x + ' : ' + 'B')" > /var/crash/fake.crash
  $ cat fake.crash
  AAA … AA : B

  
  2) Trigger the whoopsie to read the fake.crash file
  - Just create 'fake.upload' file by touch command.
  - Or launch apport-gtk gui or apport-bug cli application.

  3) Check out the result
  - After a while, the whoopsie has been killed by segmentation fault.

  Sincerely,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1872560/+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 1872118] Re: DHCP Cluster crashes after a few hours

2020-08-06 Thread Andrew Welham
I think on of the links was wrong, just remade it. and going to test
again

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

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhcp/+bug/1872118/+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 1890619] [NEW] poppler fails to build on s390x with gcc10 due to symbols changes

2020-08-06 Thread Sebastien Bacher
Public bug reported:

The build log is there
https://launchpadlibrarian.net/491645678/buildlog_ubuntu-groovy-s390x.poppler_0.86.1-0ubuntu1_BUILDING.txt.gz

the errors are

 * Build-Depends-Package: libpoppler-glib-dev
- (regex)"^_Z.*@Base$" 0.86.1
+#MISSING: 0.86.1-0ubuntu1# (regex)"^_Z.*@Base$" 0.86.1

+
_ZN7Poppler19UnicodeParsedStringERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
0.86.1-0ubuntu1

** Affects: poppler (Ubuntu)
 Importance: High
 Assignee: Dimitri John Ledkov (xnox)
 Status: New


** Tags: ftbfs

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

** Changed in: poppler (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  poppler fails to build on s390x with gcc10 due to symbols changes

Status in poppler package in Ubuntu:
  New

Bug description:
  The build log is there
  
https://launchpadlibrarian.net/491645678/buildlog_ubuntu-groovy-s390x.poppler_0.86.1-0ubuntu1_BUILDING.txt.gz

  the errors are

   * Build-Depends-Package: libpoppler-glib-dev
  - (regex)"^_Z.*@Base$" 0.86.1
  +#MISSING: 0.86.1-0ubuntu1# (regex)"^_Z.*@Base$" 0.86.1

  +
  
_ZN7Poppler19UnicodeParsedStringERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
  0.86.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1890619/+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 1890619] Re: poppler fails to build on s390x with gcc10 due to symbols changes

2020-08-06 Thread Dimitri John Ledkov
tah.

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

Title:
  poppler fails to build on s390x with gcc10 due to symbols changes

Status in poppler package in Ubuntu:
  New

Bug description:
  The build log is there
  
https://launchpadlibrarian.net/491645678/buildlog_ubuntu-groovy-s390x.poppler_0.86.1-0ubuntu1_BUILDING.txt.gz

  the errors are

   * Build-Depends-Package: libpoppler-glib-dev
  - (regex)"^_Z.*@Base$" 0.86.1
  +#MISSING: 0.86.1-0ubuntu1# (regex)"^_Z.*@Base$" 0.86.1

  +
  
_ZN7Poppler19UnicodeParsedStringERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
  0.86.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1890619/+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 1871641] Re: Ubuntu never finishes booting: A start job is running for Hold until boot process finishes up (3min 7s / no limit) -- removing 'splash' kernel parm fixes it

2020-08-06 Thread Brian Murray
** Tags removed: rls-ff-incoming

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

Title:
  Ubuntu never finishes booting: A start job is running for Hold until
  boot process finishes up (3min 7s / no limit) -- removing 'splash'
  kernel parm fixes it

Status in plymouth package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Boot process freezes at the splash screen and nothing happens after
  that. The computer can be suspended and it is able to return from
  suspend. Boot is possible by pressing escape early in the process to
  bypass plymouth.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: plymouth 0.9.4git20200323-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-0ubuntu24
  Architecture: amd64
  Date: Wed Apr  8 14:30:13 2020
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  InstallationDate: Installed on 2020-04-08 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: LENOVO 7469A23
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=e12af5fd-b700-4292-8727-70345cb61c8e ro quiet splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=e12af5fd-b700-4292-8727-70345cb61c8e ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6DET72WW (3.22 )
  dmi.board.name: 7469A23
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6DET72WW(3.22):bd10/25/2012:svnLENOVO:pn7469A23:pvrThinkPadX200s:rvnLENOVO:rn7469A23:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X200s
  dmi.product.name: 7469A23
  dmi.product.version: ThinkPad X200s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1871641/+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 1890411] Re: Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

2020-08-06 Thread Daniel van Vugt
Thanks. That's the right crash report but unfortunately it doesn't offer
any new information :(


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

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => New

** Summary changed:

- Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
+ [bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

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

Title:
  [bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  When ubuntu starts up, gdm3 does not start due to a crash in the the
  xserver:

  [  1271.342] (II) SELinux: Disabled on system
  [  1271.346] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context_profile
  [  1271.346] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
  [  1271.346] (II) AIGLX: enabled GLX_INTEL_swap_event
  [  1271.346] (II) AIGLX: enabled GLX_SGI_swap_control
  [  1271.346] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
  [  1271.346] (II) AIGLX: enabled GLX_ARB_fbconfig_float
  [  1271.346] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
  [  1271.346] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context_robustness
  [  1271.346] (II) AIGLX: Loaded and initialized i965
  [  1271.346] (II) GLX: Initialized DRI2 GL provider for screen 0
  [  1271.348] (II) modeset(0): Damage tracking initialized
  [  1271.348] (II) modeset(0): Setting screen physical size to 508 x 317
  [  1271.352] (EE) 
  [  1271.352] (EE) Backtrace:
  [  1271.352] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5649b579bacd]
  [  1271.352] (EE) 1: /usr/lib/xorg/Xorg (0x5649b55e3000+0x1bc869) 
[0x5649b579f869]
  [  1271.352] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f5c7d0a5000+0x128a0) [0x7f5c7d0b78a0]
  [  1271.352] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x8e8652) [0x7f5c784e2652]
  [  1271.352] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x8e877f) [0x7f5c784e277f]
  [  1271.352] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x122916) [0x7f5c77d1c916]
  [  1271.352] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x1189bc) [0x7f5c77d129bc]
  [  1271.352] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x109c1b) [0x7f5c77d03c1b]
  [  1271.352] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x279558) [0x7f5c77e73558]
  [  1271.352] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x2796e3) [0x7f5c77e736e3]
  [  1271.352] (EE) 10: /usr/lib/xorg/modules/libglamoregl.so 
(0x7f5c79937000+0x1a1ab) [0x7f5c799511ab]
  [  1271.352] (EE) 11: /usr/lib/xorg/Xorg (0x5649b55e3000+0x13ed03) 
[0x5649b5721d03]
  [  1271.352] (EE) 12: /usr/lib/xorg/Xorg (miPaintWindow+0x22f) 
[0x5649b577fd1f]
  [  1271.352] (EE) 13: /usr/lib/xorg/Xorg (miWindowExposures+0x112) 
[0x5649b577fa62]
  [  1271.352] (EE) 14: /usr/lib/xorg/Xorg (0x5649b55e3000+0xa9c41) 
[0x5649b568cc41]
  [  1271.352] (EE) 15: /usr/lib/xorg/Xorg (MapWindow+0x114) [0x5649b5665d04]
  [  1271.352] (EE) 16: /usr/lib/xorg/Xorg (0x5649b55e3000+0x56e79) 
[0x5649b5639e79]
  [  1271.352] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xe7) [0x7f5c7ccd5b97]
  [  1271.352] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x5649b5623b8a]
  [  1271.352] (EE) 
  [  1271.352] (EE) Segmentation fault at address 0x4
  [  1271.352] (EE) 
  Fatal server error:
  [  1271.352] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [  1271.352] (EE) 
  [  1271.352] (EE) 

  As i965_dri.so is part of the libgl-mesa-dri package I downgraded this
  specific package from version 20.0.8-0ubuntu1~18.04.1 back to
  19.2.8-0ubuntu0~18.04.3.

  This solves the problem. So I suspect that the problem is in this
  specific package.

  My machine is (uname):
  4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 
x86_64 GNU/Linux

  (lspci)
  00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller 
(rev 06)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 05)
  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: 

[Touch-packages] [Bug 1890411] Re: [bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

2020-08-06 Thread Ronald Hecht
I just added the crash report of gdm3: https://errors.ubuntu.com/oops
/1e6d888a-d7c5-11ea-ae81-fa163ee63de6

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

Title:
  [bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  When ubuntu starts up, gdm3 does not start due to a crash in the the
  xserver:

  [  1271.342] (II) SELinux: Disabled on system
  [  1271.346] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context_profile
  [  1271.346] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
  [  1271.346] (II) AIGLX: enabled GLX_INTEL_swap_event
  [  1271.346] (II) AIGLX: enabled GLX_SGI_swap_control
  [  1271.346] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
  [  1271.346] (II) AIGLX: enabled GLX_ARB_fbconfig_float
  [  1271.346] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
  [  1271.346] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context_robustness
  [  1271.346] (II) AIGLX: Loaded and initialized i965
  [  1271.346] (II) GLX: Initialized DRI2 GL provider for screen 0
  [  1271.348] (II) modeset(0): Damage tracking initialized
  [  1271.348] (II) modeset(0): Setting screen physical size to 508 x 317
  [  1271.352] (EE) 
  [  1271.352] (EE) Backtrace:
  [  1271.352] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5649b579bacd]
  [  1271.352] (EE) 1: /usr/lib/xorg/Xorg (0x5649b55e3000+0x1bc869) 
[0x5649b579f869]
  [  1271.352] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f5c7d0a5000+0x128a0) [0x7f5c7d0b78a0]
  [  1271.352] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x8e8652) [0x7f5c784e2652]
  [  1271.352] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x8e877f) [0x7f5c784e277f]
  [  1271.352] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x122916) [0x7f5c77d1c916]
  [  1271.352] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x1189bc) [0x7f5c77d129bc]
  [  1271.352] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x109c1b) [0x7f5c77d03c1b]
  [  1271.352] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x279558) [0x7f5c77e73558]
  [  1271.352] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x2796e3) [0x7f5c77e736e3]
  [  1271.352] (EE) 10: /usr/lib/xorg/modules/libglamoregl.so 
(0x7f5c79937000+0x1a1ab) [0x7f5c799511ab]
  [  1271.352] (EE) 11: /usr/lib/xorg/Xorg (0x5649b55e3000+0x13ed03) 
[0x5649b5721d03]
  [  1271.352] (EE) 12: /usr/lib/xorg/Xorg (miPaintWindow+0x22f) 
[0x5649b577fd1f]
  [  1271.352] (EE) 13: /usr/lib/xorg/Xorg (miWindowExposures+0x112) 
[0x5649b577fa62]
  [  1271.352] (EE) 14: /usr/lib/xorg/Xorg (0x5649b55e3000+0xa9c41) 
[0x5649b568cc41]
  [  1271.352] (EE) 15: /usr/lib/xorg/Xorg (MapWindow+0x114) [0x5649b5665d04]
  [  1271.352] (EE) 16: /usr/lib/xorg/Xorg (0x5649b55e3000+0x56e79) 
[0x5649b5639e79]
  [  1271.352] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xe7) [0x7f5c7ccd5b97]
  [  1271.352] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x5649b5623b8a]
  [  1271.352] (EE) 
  [  1271.352] (EE) Segmentation fault at address 0x4
  [  1271.352] (EE) 
  Fatal server error:
  [  1271.352] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [  1271.352] (EE) 
  [  1271.352] (EE) 

  As i965_dri.so is part of the libgl-mesa-dri package I downgraded this
  specific package from version 20.0.8-0ubuntu1~18.04.1 back to
  19.2.8-0ubuntu0~18.04.3.

  This solves the problem. So I suspect that the problem is in this
  specific package.

  My machine is (uname):
  4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 
x86_64 GNU/Linux

  (lspci)
  00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller 
(rev 06)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 05)
  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d5)
  00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #3 (rev d5)
  00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset 

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-08-06 Thread Pjotr12345
This is a simplified version of the means to work around this problem:

Step 1:
sudo sed -i 's/COMPRESS=lz4/COMPRESS=gzip/g' /etc/initramfs-tools/initramfs.conf

Step 2:
sudo update-initramfs -u

Step 3:
Reboot.

Now I wonder whether someone has already tried something other than gzip? 
Because initramfs.conf mentions no less than six options:
# COMPRESS: [ gzip | bzip2 | lz4 | lzma | lzop | xz ]

Apparently gzip is slower than lz4, which might slow the boot process by
several seconds. One of the other alternatives might be faster.

Of course I could test that myself, but I'm too lazy today, so I'm
hoping somebody else has done the footwork already

-- 
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:
  Invalid
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.

  ---

  However, we currently believe that the decoding error reported in
  dmesg is actually harmless and has no impact on usability on the
  system.

  Switching from lz4 to gzip compression, simply papers over the
  warning, without any benefits, and slows down boot.

  Kernel should be fixed to correctly parse lz4 compressed initrds, or
  at least lower the warning, to not be user visible as an error.

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 1890572] [NEW] USB backend never ends if the printer is not connected

2020-08-06 Thread Alejandro Claro
Public bug reported:

USB backend never ends if the printer is not connected. we have been
able to identify a infinity loop in print_device function in usb-
libusb.c file:

```
  fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
  while ((g.printer = find_device(print_cb, uri)) == NULL)
  {
_cupsLangPrintFilter(stderr, "INFO",
 _("Waiting for printer to become available."));
sleep(5);
  }
```

It's also easy to test by invoking the backend by hand:


```
# export DEVICE_URI='usb://Printer/Model?serial=?'
# /usr/lib/cups/backend/usb 0 root title 1 '' data.file

DEBUG: Loading USB quirks from "/usr/share/cups/usb".
DEBUG: Loaded 159 quirks.
DEBUG: Printing on printer with URI: usb://Brother/PJ-773?serial=?
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.

DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
...

```

Setting a job timeout policy or stopping the job by hand are not options
for us. We can have job that take up to an hour to complete.

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

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

Title:
  USB backend never ends if the printer is not connected

Status in cups package in Ubuntu:
  New

Bug description:
  USB backend never ends if the printer is not connected. we have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:

  ```
fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
while ((g.printer = find_device(print_cb, uri)) == NULL)
{
  _cupsLangPrintFilter(stderr, "INFO",
 _("Waiting for printer to become available."));
  sleep(5);
}
  ```

  It's also easy to test by invoking the backend by hand:

  
  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file

  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
  DEBUG: Printing on printer with URI: usb://Brother/PJ-773?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.

  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...

  ```

  Setting a job timeout policy or stopping the job by hand are not
  options for us. We can have job that take up to an hour to complete.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1890572/+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 1890572] Re: USB backend never ends if the printer is not connected

2020-08-06 Thread Alejandro Claro
** Description changed:

- USB backend never ends if the printer is not connected. we have been
+ USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:
  
  ```
-   fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
-   while ((g.printer = find_device(print_cb, uri)) == NULL)
-   {
- _cupsLangPrintFilter(stderr, "INFO",
-_("Waiting for printer to become available."));
- sleep(5);
-   }
+   fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
+   while ((g.printer = find_device(print_cb, uri)) == NULL)
+   {
+ _cupsLangPrintFilter(stderr, "INFO",
+ _("Waiting for printer to become available."));
+ sleep(5);
+   }
  ```
  
  It's also easy to test by invoking the backend by hand:
- 
  
  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file
  
  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
  DEBUG: Printing on printer with URI: usb://Brother/PJ-773?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...
  
  ```
  
- Setting a job timeout policy or stopping the job by hand are not options
- for us. We can have job that take up to an hour to complete.
+ Setting a work timeout policy or manually stopping work are not options
+ for us. We may have jobs that take up to an hour to complete.

** Description changed:

  USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:
  
  ```
    fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
    while ((g.printer = find_device(print_cb, uri)) == NULL)
    {
  _cupsLangPrintFilter(stderr, "INFO",
  _("Waiting for printer to become available."));
  sleep(5);
    }
  ```
  
  It's also easy to test by invoking the backend by hand:
  
  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file
  
  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
- DEBUG: Printing on printer with URI: usb://Brother/PJ-773?serial=?
+ DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...
  
  ```
  
  Setting a work timeout policy or manually stopping work are not options
  for us. We may have jobs that take up to an hour to complete.

** Description changed:

  USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:
  
  ```
    fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
    while ((g.printer = find_device(print_cb, uri)) == NULL)
    {
  _cupsLangPrintFilter(stderr, "INFO",
  _("Waiting for printer to become available."));
  sleep(5);
    }
  ```
  
  It's also easy to test by invoking the backend by hand:
  
  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file
  
  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
  DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
- 
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...
  
  ```
  
- Setting a work timeout policy or manually stopping work are not options
+ Setting a job timeout policy or manually stopping work are not options
  for us. We may have jobs that take up to an hour to complete.

** Description changed:

  USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:
  
  ```
    fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
    while 

[Touch-packages] [Bug 1888558] [NEW] VLC is using up to 2 GB of RAM just to play a regular 720px HD video

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

On my computer running Ubuntu 20.04 and XFCE desktop, The VLC GUI player
is using an increasing amount of memory as time progressed. The video is
a typical H.264 movie (MP4 file format). I have let the application sit
for a few days, and here is the usage of RAM as the days went by:

Date   Time(EDT) VSIZE   RSS
2020-07-19 20:19:162848984455148
2020-07-20 13:09:063307736926156
2020-07-22 13:18:054487464   2059848

The process itself was started on:
Sat Jul 18 21:41:24 2020

I was playing the video only for about ~5 minutes when the program
started, then let the program sit idle for a few days. Today I found
that it consumed 2GB RSS as shown above!

I am reporting this issue to see if something in my system is messing up
VLC memory usage. In an older laptop, trying to play the same file (with
VLC version 2.0.3) has its memory consumption starting at just under
190M.


Wirawan

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: vlc 3.0.9.2-1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Wed Jul 22 13:19:21 2020
SourcePackage: vlc
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug focal
-- 
VLC is using up to 2 GB of RAM just to play a regular 720px HD video
https://bugs.launchpad.net/bugs/1888558
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mesa 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 1888558] Re: VLC is using up to 2 GB of RAM just to play a regular 720px HD video

2020-08-06 Thread Sebastian Ramacher
As suspected, this seems to be an issue with a driver.

** Package changed: vlc (Ubuntu) => mesa (Ubuntu)

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

Title:
  VLC is using up to 2 GB of RAM just to play a regular 720px HD video

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  On my computer running Ubuntu 20.04 and XFCE desktop, The VLC GUI
  player is using an increasing amount of memory as time progressed. The
  video is a typical H.264 movie (MP4 file format). I have let the
  application sit for a few days, and here is the usage of RAM as the
  days went by:

  Date   Time(EDT) VSIZE   RSS
  2020-07-19 20:19:162848984455148
  2020-07-20 13:09:063307736926156
  2020-07-22 13:18:054487464   2059848

  The process itself was started on:
  Sat Jul 18 21:41:24 2020

  I was playing the video only for about ~5 minutes when the program
  started, then let the program sit idle for a few days. Today I found
  that it consumed 2GB RSS as shown above!

  I am reporting this issue to see if something in my system is messing
  up VLC memory usage. In an older laptop, trying to play the same file
  (with VLC version 2.0.3) has its memory consumption starting at just
  under 190M.

  
  Wirawan

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: vlc 3.0.9.2-1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed Jul 22 13:19:21 2020
  SourcePackage: vlc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1888558/+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 1890593] [NEW] Xorg freeze

2020-08-06 Thread Camelo
Public bug reported:

Just installed ubuntu  20.04 and I am stuck on ubuntu with a spining
logo. If I go to other tty and unplug the HDMI screens I can get to the
login screen, Otherwise I cant. I did checked the md5sum of the iso
before installing and its was correct.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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  440.100  Fri May 29 08:45:51 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug  6 14:29:04 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: This is the first time
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo ThinkPad T570 [17aa:2248]
   Subsystem: Lenovo GM108GLM [Quadro M520 Mobile] [17aa:2248]
InstallationDate: Installed on 2020-08-05 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 20HCS0660M
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=be1cbba6-c044-4d36-a6f4-fe872353a538 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/08/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1VET49W (1.39 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HCS0660M
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:bvrN1VET49W(1.39):bd05/08/2019:svnLENOVO:pn20HCS0660M:pvrThinkPadP51s:rvnLENOVO:rn20HCS0660M:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad THINKPAD P51S
dmi.product.name: 20HCS0660M
dmi.product.sku: LENOVO_MT_20HC_BU_Think_FM_ThinkPad THINKPAD P51S
dmi.product.version: ThinkPad P51s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal freeze ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Just installed ubuntu  20.04 and I am stuck on ubuntu with a spining
  logo. If I go to other tty and unplug the HDMI screens I can get to
  the login screen, Otherwise I cant. I did checked the md5sum of the
  iso before installing and its was correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  6 14:29:04 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection 

[Touch-packages] [Bug 1890597] [NEW] systemd-run --user fails to run

2020-08-06 Thread Tinco Andringa
Public bug reported:

Almost fresh install of 20.04, I run:

$ systemd-run --user --wait true

As is documented in the man page for systemd-run, and get the output:

Failed to create bus connection: No such file or directory

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: pass
Date: Thu Aug  6 12:36:53 2020
InstallationDate: Installed on 2020-08-01 (4 days ago)
InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 SHELL=/bin/bash
 LANG=C.UTF-8
 TERM=xterm-256color
 LC_CTYPE=C.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=2fa4d6db-e304-45ab-89aa-2a183f41fc4c ro
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/29/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.70
dmi.board.name: TRX40 Creator
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd05/29/2020:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnTRX40Creator:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug focal uec-images

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

Title:
  systemd-run --user fails to run

Status in systemd package in Ubuntu:
  New

Bug description:
  Almost fresh install of 20.04, I run:

  $ systemd-run --user --wait true

  As is documented in the man page for systemd-run, and get the output:

  Failed to create bus connection: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Aug  6 12:36:53 2020
  InstallationDate: Installed on 2020-08-01 (4 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   SHELL=/bin/bash
   LANG=C.UTF-8
   TERM=xterm-256color
   LC_CTYPE=C.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=2fa4d6db-e304-45ab-89aa-2a183f41fc4c ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: TRX40 Creator
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd05/29/2020:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnTRX40Creator:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890597/+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 1890411] Re: [bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

2020-08-06 Thread Ronald Hecht
Is there any other information I could provide?

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

Title:
  [bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  When ubuntu starts up, gdm3 does not start due to a crash in the the
  xserver:

  [  1271.342] (II) SELinux: Disabled on system
  [  1271.346] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context_profile
  [  1271.346] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
  [  1271.346] (II) AIGLX: enabled GLX_INTEL_swap_event
  [  1271.346] (II) AIGLX: enabled GLX_SGI_swap_control
  [  1271.346] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
  [  1271.346] (II) AIGLX: enabled GLX_ARB_fbconfig_float
  [  1271.346] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
  [  1271.346] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context_robustness
  [  1271.346] (II) AIGLX: Loaded and initialized i965
  [  1271.346] (II) GLX: Initialized DRI2 GL provider for screen 0
  [  1271.348] (II) modeset(0): Damage tracking initialized
  [  1271.348] (II) modeset(0): Setting screen physical size to 508 x 317
  [  1271.352] (EE) 
  [  1271.352] (EE) Backtrace:
  [  1271.352] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5649b579bacd]
  [  1271.352] (EE) 1: /usr/lib/xorg/Xorg (0x5649b55e3000+0x1bc869) 
[0x5649b579f869]
  [  1271.352] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f5c7d0a5000+0x128a0) [0x7f5c7d0b78a0]
  [  1271.352] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x8e8652) [0x7f5c784e2652]
  [  1271.352] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x8e877f) [0x7f5c784e277f]
  [  1271.352] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x122916) [0x7f5c77d1c916]
  [  1271.352] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x1189bc) [0x7f5c77d129bc]
  [  1271.352] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x109c1b) [0x7f5c77d03c1b]
  [  1271.352] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x279558) [0x7f5c77e73558]
  [  1271.352] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x2796e3) [0x7f5c77e736e3]
  [  1271.352] (EE) 10: /usr/lib/xorg/modules/libglamoregl.so 
(0x7f5c79937000+0x1a1ab) [0x7f5c799511ab]
  [  1271.352] (EE) 11: /usr/lib/xorg/Xorg (0x5649b55e3000+0x13ed03) 
[0x5649b5721d03]
  [  1271.352] (EE) 12: /usr/lib/xorg/Xorg (miPaintWindow+0x22f) 
[0x5649b577fd1f]
  [  1271.352] (EE) 13: /usr/lib/xorg/Xorg (miWindowExposures+0x112) 
[0x5649b577fa62]
  [  1271.352] (EE) 14: /usr/lib/xorg/Xorg (0x5649b55e3000+0xa9c41) 
[0x5649b568cc41]
  [  1271.352] (EE) 15: /usr/lib/xorg/Xorg (MapWindow+0x114) [0x5649b5665d04]
  [  1271.352] (EE) 16: /usr/lib/xorg/Xorg (0x5649b55e3000+0x56e79) 
[0x5649b5639e79]
  [  1271.352] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xe7) [0x7f5c7ccd5b97]
  [  1271.352] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x5649b5623b8a]
  [  1271.352] (EE) 
  [  1271.352] (EE) Segmentation fault at address 0x4
  [  1271.352] (EE) 
  Fatal server error:
  [  1271.352] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [  1271.352] (EE) 
  [  1271.352] (EE) 

  As i965_dri.so is part of the libgl-mesa-dri package I downgraded this
  specific package from version 20.0.8-0ubuntu1~18.04.1 back to
  19.2.8-0ubuntu0~18.04.3.

  This solves the problem. So I suspect that the problem is in this
  specific package.

  My machine is (uname):
  4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 
x86_64 GNU/Linux

  (lspci)
  00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller 
(rev 06)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 05)
  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d5)
  00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #3 (rev d5)
  00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #1 (rev 05)
  00:1f.0 ISA bridge: Intel 

[Touch-packages] [Bug 1889548] Re: ssh using gssapi will enforce FILE: credentials cache

2020-08-06 Thread Toby Blake
Hi Christian,

Thanks for your reply (and for the links).  I agree that a configurable
option coming from upstream would be the preferred option.  I'll submit
a bug upstream accordingly and note the ID here.

I note there's a patch referenced in the openssh mailing list link,
unfortunately the link is a 404 - I'll see if I can track it down via
other means.  On this topic, we've been using ssh on scientific linux
for a number of years now and that is patched to use the default ccache
name.  It would be interesting to see if it's the same or similar as the
404 patch above.

Depending on the outcome of my upstream bug report, I'll see if I can
port any patches we use to the current ubuntu/upstream code base.

As to your final question re: regression - I don't think so, looking at
the code, but we are only now in the process of converting desktop
machines to ubuntu.

Cheers
Toby

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

Title:
  ssh using gssapi will enforce FILE: credentials cache

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  ssh connections from a client with the following in ssh_config...

  GSSAPIAuthentication yes
  GSSAPIDelegateCredentials yes

  ... to an ubuntu 20.04 machine result in KRB5CCNAME being set to
  'FILE:/tmp/krb5cc_[uid]_[random]' despite the following in
  /etc/krb5.conf:

  [libdefaults]
   ...
   default_ccache_name = KEYRING:persistent:%{uid}

  This means that we cannot enforce a policy to use KEYRING ccaches
  across our systems.  Authentications which go via the pam stack (e.g.
  login to the machine at the console or over ssh using a password) can
  be configured to use a KEYRING ccache, via libpam-krb5 settings in
  /etc/krb5.conf.

  The FILE: setting seems to be hard-coded in the openssh code (auth-
  krb5.c).  It would be great if ssh(gssapi-with-mic) connections either
  (a) set KRB5CCNAME to the default_ccache_name value, if set in
  /etc/krb5.conf, or (b) didn't set KRB5CCNAME at all, so the system
  default is used.

  Many thanks
  Toby Blake
  School of Informatics
  University of Edinburgh

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1889548/+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 1870213] Re: "Switching to another layout" shortcut was not set by oem-config for end-user

2020-08-06 Thread Norbert
Groovy also affected.

** Tags added: groovy

-- 
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
Status in ubiquity 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 1890411] Re: Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

2020-08-06 Thread Ronald Hecht
I followed step 1 and 2. I don't know how to get the ID. According to
step 2 the link to the crash report is https://errors.ubuntu.com/oops
/3d15afdc-d7b7-11ea-b244-fa163e983629

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

Title:
  Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

Status in mesa package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  When ubuntu starts up, gdm3 does not start due to a crash in the the
  xserver:

  [  1271.342] (II) SELinux: Disabled on system
  [  1271.346] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context_profile
  [  1271.346] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
  [  1271.346] (II) AIGLX: enabled GLX_INTEL_swap_event
  [  1271.346] (II) AIGLX: enabled GLX_SGI_swap_control
  [  1271.346] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
  [  1271.346] (II) AIGLX: enabled GLX_ARB_fbconfig_float
  [  1271.346] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
  [  1271.346] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context_robustness
  [  1271.346] (II) AIGLX: Loaded and initialized i965
  [  1271.346] (II) GLX: Initialized DRI2 GL provider for screen 0
  [  1271.348] (II) modeset(0): Damage tracking initialized
  [  1271.348] (II) modeset(0): Setting screen physical size to 508 x 317
  [  1271.352] (EE) 
  [  1271.352] (EE) Backtrace:
  [  1271.352] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5649b579bacd]
  [  1271.352] (EE) 1: /usr/lib/xorg/Xorg (0x5649b55e3000+0x1bc869) 
[0x5649b579f869]
  [  1271.352] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f5c7d0a5000+0x128a0) [0x7f5c7d0b78a0]
  [  1271.352] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x8e8652) [0x7f5c784e2652]
  [  1271.352] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x8e877f) [0x7f5c784e277f]
  [  1271.352] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x122916) [0x7f5c77d1c916]
  [  1271.352] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x1189bc) [0x7f5c77d129bc]
  [  1271.352] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x109c1b) [0x7f5c77d03c1b]
  [  1271.352] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x279558) [0x7f5c77e73558]
  [  1271.352] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x2796e3) [0x7f5c77e736e3]
  [  1271.352] (EE) 10: /usr/lib/xorg/modules/libglamoregl.so 
(0x7f5c79937000+0x1a1ab) [0x7f5c799511ab]
  [  1271.352] (EE) 11: /usr/lib/xorg/Xorg (0x5649b55e3000+0x13ed03) 
[0x5649b5721d03]
  [  1271.352] (EE) 12: /usr/lib/xorg/Xorg (miPaintWindow+0x22f) 
[0x5649b577fd1f]
  [  1271.352] (EE) 13: /usr/lib/xorg/Xorg (miWindowExposures+0x112) 
[0x5649b577fa62]
  [  1271.352] (EE) 14: /usr/lib/xorg/Xorg (0x5649b55e3000+0xa9c41) 
[0x5649b568cc41]
  [  1271.352] (EE) 15: /usr/lib/xorg/Xorg (MapWindow+0x114) [0x5649b5665d04]
  [  1271.352] (EE) 16: /usr/lib/xorg/Xorg (0x5649b55e3000+0x56e79) 
[0x5649b5639e79]
  [  1271.352] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xe7) [0x7f5c7ccd5b97]
  [  1271.352] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x5649b5623b8a]
  [  1271.352] (EE) 
  [  1271.352] (EE) Segmentation fault at address 0x4
  [  1271.352] (EE) 
  Fatal server error:
  [  1271.352] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [  1271.352] (EE) 
  [  1271.352] (EE) 

  As i965_dri.so is part of the libgl-mesa-dri package I downgraded this
  specific package from version 20.0.8-0ubuntu1~18.04.1 back to
  19.2.8-0ubuntu0~18.04.3.

  This solves the problem. So I suspect that the problem is in this
  specific package.

  My machine is (uname):
  4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 
x86_64 GNU/Linux

  (lspci)
  00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller 
(rev 06)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 05)
  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d5)
  00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #3 (rev 

[Touch-packages] [Bug 1890411] Re: [bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

2020-08-06 Thread Daniel van Vugt
^^^
That is bug 1890563 but that's a different issue to this one.

Although it's likely both issues are fixed in Ubuntu 20.04 already.
Certainly bug 1890563 is.

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

Title:
  [bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  When ubuntu starts up, gdm3 does not start due to a crash in the the
  xserver:

  [  1271.342] (II) SELinux: Disabled on system
  [  1271.346] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context_profile
  [  1271.346] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
  [  1271.346] (II) AIGLX: enabled GLX_INTEL_swap_event
  [  1271.346] (II) AIGLX: enabled GLX_SGI_swap_control
  [  1271.346] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
  [  1271.346] (II) AIGLX: enabled GLX_ARB_fbconfig_float
  [  1271.346] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
  [  1271.346] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
  [  1271.346] (II) AIGLX: enabled GLX_ARB_create_context_robustness
  [  1271.346] (II) AIGLX: Loaded and initialized i965
  [  1271.346] (II) GLX: Initialized DRI2 GL provider for screen 0
  [  1271.348] (II) modeset(0): Damage tracking initialized
  [  1271.348] (II) modeset(0): Setting screen physical size to 508 x 317
  [  1271.352] (EE) 
  [  1271.352] (EE) Backtrace:
  [  1271.352] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5649b579bacd]
  [  1271.352] (EE) 1: /usr/lib/xorg/Xorg (0x5649b55e3000+0x1bc869) 
[0x5649b579f869]
  [  1271.352] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f5c7d0a5000+0x128a0) [0x7f5c7d0b78a0]
  [  1271.352] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x8e8652) [0x7f5c784e2652]
  [  1271.352] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x8e877f) [0x7f5c784e277f]
  [  1271.352] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x122916) [0x7f5c77d1c916]
  [  1271.352] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x1189bc) [0x7f5c77d129bc]
  [  1271.352] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x109c1b) [0x7f5c77d03c1b]
  [  1271.352] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x279558) [0x7f5c77e73558]
  [  1271.352] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x2796e3) [0x7f5c77e736e3]
  [  1271.352] (EE) 10: /usr/lib/xorg/modules/libglamoregl.so 
(0x7f5c79937000+0x1a1ab) [0x7f5c799511ab]
  [  1271.352] (EE) 11: /usr/lib/xorg/Xorg (0x5649b55e3000+0x13ed03) 
[0x5649b5721d03]
  [  1271.352] (EE) 12: /usr/lib/xorg/Xorg (miPaintWindow+0x22f) 
[0x5649b577fd1f]
  [  1271.352] (EE) 13: /usr/lib/xorg/Xorg (miWindowExposures+0x112) 
[0x5649b577fa62]
  [  1271.352] (EE) 14: /usr/lib/xorg/Xorg (0x5649b55e3000+0xa9c41) 
[0x5649b568cc41]
  [  1271.352] (EE) 15: /usr/lib/xorg/Xorg (MapWindow+0x114) [0x5649b5665d04]
  [  1271.352] (EE) 16: /usr/lib/xorg/Xorg (0x5649b55e3000+0x56e79) 
[0x5649b5639e79]
  [  1271.352] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xe7) [0x7f5c7ccd5b97]
  [  1271.352] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x5649b5623b8a]
  [  1271.352] (EE) 
  [  1271.352] (EE) Segmentation fault at address 0x4
  [  1271.352] (EE) 
  Fatal server error:
  [  1271.352] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [  1271.352] (EE) 
  [  1271.352] (EE) 

  As i965_dri.so is part of the libgl-mesa-dri package I downgraded this
  specific package from version 20.0.8-0ubuntu1~18.04.1 back to
  19.2.8-0ubuntu0~18.04.3.

  This solves the problem. So I suspect that the problem is in this
  specific package.

  My machine is (uname):
  4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 
x86_64 GNU/Linux

  (lspci)
  00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller 
(rev 06)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 05)
  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d5)
  00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #3 (rev d5)
  00:1d.0 USB 

[Touch-packages] [Bug 1883447] Re: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers

2020-08-06 Thread Steve Dodd
This bug also seems to generate "Assertion
'clock_gettime(map_clock_id(clock_id), ) == 0' failed at src/basic
/time-util.c:55, function now(). Aborting" in various places if you try
to boot an existing 20.04 container on bionic with systemd-nspawn.

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

Title:
  nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to
  focal in containers

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  
  Recent Linux kernels introduced a number of new syscalls ending in _time64 to 
fix Y2038 problem; it appears recent glibc, including the version in focal, 
test for the existence of these. systemd-nspawn in bionic (237-3ubuntu10.38) 
doesn't know about these so blocks them by default. It seems however glibc 
isn't expecting an EPERM, causing numerous programs to fail.

  In particular, running do-release-upgrade to focal in an nspawn
  container hosted on bionic will break as soon as the new libc has been
  unpacked.

  Solution (tested here) is to cherrypick upstream commit
  
https://github.com/systemd/systemd/commit/6ca677106992321326427c89a40e1c9673a499b2

  A newer libseccomp is also needed but this is already being worked on,
  see bug #1876055.

  It's a pretty trivial fix one the new libseccomp lands, and there is
  precedent for SRU-ing for a similar issue in bug #1840640.

  https://patchwork.kernel.org/patch/10756415/ is apparently the
  upstream kernel patch, which should give a clearer idea of which
  architectures are likely to be affected - I noticed it on armhf.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1883447/+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 1871641] Re: Ubuntu never finishes booting: A start job is running for Hold until boot process finishes up (3min 7s / no limit) -- removing 'splash' kernel parm fixes it

2020-08-06 Thread Balint Reczey
Is there a reliable way I can reproduce the problem? (I don't face it on my 
laptops.)
Is this happening on any Ubuntu-certified model? This could let our 
certification team to investigate the issue.

How can the systemd help? killing plymouth earlier?
 

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

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

Title:
  Ubuntu never finishes booting: A start job is running for Hold until
  boot process finishes up (3min 7s / no limit) -- removing 'splash'
  kernel parm fixes it

Status in plymouth package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Boot process freezes at the splash screen and nothing happens after
  that. The computer can be suspended and it is able to return from
  suspend. Boot is possible by pressing escape early in the process to
  bypass plymouth.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: plymouth 0.9.4git20200323-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-0ubuntu24
  Architecture: amd64
  Date: Wed Apr  8 14:30:13 2020
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  InstallationDate: Installed on 2020-04-08 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: LENOVO 7469A23
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=e12af5fd-b700-4292-8727-70345cb61c8e ro quiet splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=e12af5fd-b700-4292-8727-70345cb61c8e ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6DET72WW (3.22 )
  dmi.board.name: 7469A23
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6DET72WW(3.22):bd10/25/2012:svnLENOVO:pn7469A23:pvrThinkPadX200s:rvnLENOVO:rn7469A23:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X200s
  dmi.product.name: 7469A23
  dmi.product.version: ThinkPad X200s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1871641/+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 1890609] Re: improved resolved configuration

2020-08-06 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~xnox/ubuntu/+source/systemd/+git/systemd/+merge/388803

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

Title:
  improved resolved configuration

Status in systemd package in Ubuntu:
  New

Bug description:
  improved resolved configuration

  * isc-dhcp-client pushes DNS data to resolved via a hook it ships
  * ifupdown pushes DNS data to resolved via a hook it ships
  * resolvconf skips pulling DNS data that is pushed to resolved
  * systemd doesn't have enter hook anymore

  This way with or without resolvconf, resolved has all the information
  it needs and /etc/resolv.conf can be static, point at resolvconf
  managed file, or at resolved managed file as desired.

  isc-dhcp 4.4.1-2.1ubuntu7
  ifupdown 0.8.35ubuntu2
  resolvconf 1.82ubuntu1 
  systemd TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890609/+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 1890609] [NEW] improved resolved configuration

2020-08-06 Thread Dimitri John Ledkov
Public bug reported:

improved resolved configuration

* isc-dhcp-client pushes DNS data to resolved via a hook it ships
* ifupdown pushes DNS data to resolved via a hook it ships
* resolvconf skips pulling DNS data that is pushed to resolved
* systemd doesn't have enter hook anymore

This way with or without resolvconf, resolved has all the information it
needs and /etc/resolv.conf can be static, point at resolvconf managed
file, or at resolved managed file as desired.

isc-dhcp 4.4.1-2.1ubuntu7
ifupdown 0.8.35ubuntu2
resolvconf 1.82ubuntu1 
systemd TBD

** 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/1890609

Title:
  improved resolved configuration

Status in systemd package in Ubuntu:
  New

Bug description:
  improved resolved configuration

  * isc-dhcp-client pushes DNS data to resolved via a hook it ships
  * ifupdown pushes DNS data to resolved via a hook it ships
  * resolvconf skips pulling DNS data that is pushed to resolved
  * systemd doesn't have enter hook anymore

  This way with or without resolvconf, resolved has all the information
  it needs and /etc/resolv.conf can be static, point at resolvconf
  managed file, or at resolved managed file as desired.

  isc-dhcp 4.4.1-2.1ubuntu7
  ifupdown 0.8.35ubuntu2
  resolvconf 1.82ubuntu1 
  systemd TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890609/+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 1872118] Re: DHCP Cluster crashes after a few hours

2020-08-06 Thread Jorge Niedbalski
Hello Andrew,

I just reviewed the core file that you provided. Thread 1 is the thread that 
panics
on assertion because sock.pending_send is already set. This is the condition I 
prevented
in the PPA, so *shouldn't* be hitting the frame 3

In my test systems I don't hit this condition, dispatch_send isn't called if 
pending_send
is set.

(gdb) thread 1
[Switching to thread 1 (Thread 0x7f39a41f5700 (LWP 18780))]
#1  0x7f39a4dd1859 in __GI_abort () at abort.c:79
79  in abort.c
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x7f39a4dd1859 in __GI_abort () at abort.c:79
#2  0x7f39a4faf985 in isc_assertion_failed (file=, 
line=, type=, cond=) at 
../../../lib/isc/assertions.c:52
#3  0x7f39a4feb7e1 in dispatch_send (sock=0x7f39a4a03730) at 
../../../../lib/isc/unix/socket.c:3380
#4  process_fd (writeable=, readable=, fd=0, 
manager=0x7f39a49fa010) at ../../../../lib/isc/unix/socket.c:4054
#5  process_fds (writefds=, readfds=0x16, maxfd=-1533038191, 
manager=0x7f39a49fa010) at ../../../../lib/isc/unix/socket.c:4211
#6  watcher (uap=0x7f39a49fa010) at ../../../../lib/isc/unix/socket.c:4397
[...]
(gdb) frame 3
#3  0x7f39a4feb7e1 in dispatch_send (sock=0x7f39a4a03730) at 
../../../../lib/isc/unix/socket.c:3380
3380../../../../lib/isc/unix/socket.c: No such file or directory.
(gdb) info locals
iev = 0x0
ev = 
sender = 0x2
iev = 
ev = 
sender = 

(gdb) p sock
$1 = (isc__socket_t *) 0x7f39a4a03730
(gdb) p sock.pending_send
$2 = 1

Can you check your library links, etc?

ubuntu@dhcpd1:~$ ldd /usr/sbin/dhcpd | grep export
libirs-export.so.161 => /lib/x86_64-linux-gnu/libirs-export.so.161 
(0x7f5cb62e5000)
libdns-export.so.1109 => /lib/x86_64-linux-gnu/libdns-export.so.1109 
(0x7f5cb60b)
libisc-export.so.1105 => /lib/x86_64-linux-gnu/libisc-export.so.1105 
(0x7f5cb6039000)
libisccfg-export.so.163 => 
/lib/x86_64-linux-gnu/libisccfg-export.so.163 (0x7f5cb5df5000)
ubuntu@dhcpd1:~$ dpkg -S /lib/x86_64-linux-gnu/libisc-export.so.1105
libisc-export1105:amd64: /lib/x86_64-linux-gnu/libisc-export.so.1105
ubuntu@dhcpd1:~$ apt-cache policy libisc-export1105  | grep -i ppa
  Installed: 1:9.11.16+dfsg-3~ppa1
  Candidate: 1:9.11.16+dfsg-3~ppa1
 *** 1:9.11.16+dfsg-3~ppa1 500
500 http://ppa.launchpad.net/niedbalski/1872188-dbg/ubuntu focal/main 
amd64 Packages

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

Title:
  DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9-libs source package in Focal:
  New
Status in isc-dhcp source package in Focal:
  New
Status in bind9-libs source package in Groovy:
  New
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D 

<    1   2