[Touch-packages] [Bug 2049988] Re: Latest kernel kills wifi.

[Patrick M]

I think Connman is the culprit?

** Package changed: network-manager (Ubuntu) => connman

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

Title:
  Latest kernel kills wifi.

Status in Connection Manager:
  New

Bug description:
  New kernel 6.0.5-14 boot up system does not recognize built in wifi
  adapter. When I drop to last kernel install wifi works fine.

  HP Pavillion With intel core I7 chip.

  Output of lshow --C network:

   *-network 
 description: Wireless interface
 product: MT7921 802.11ax PCI Express Wireless Network Adapter
 vendor: MEDIATEK Corp.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlp2s0
 version: 00
 serial: b4:8c:9d:28:0e:cb
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=mt7921e 
driverversion=6.2.0-39-generic firmware=01-20220209150915 
ip=192.168.1.81 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: iomemory:600-5ff iomemory:600-5ff iomemory:600-5ff irq:144 
memory:601210-60121f memory:601220-6012203fff 
memory:6012204000-6012204fff
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrick2379 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-15 (432 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: HP HP Pavilion Laptop 15-eg2xxx
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=2a43dcba-8f84-43f8-a1d6-ad38002f17c0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-39-generic N/A
   linux-backports-modules-6.2.0-39-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.24
  Tags:  jammy
  Uname: Linux 6.2.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2023
  dmi.bios.release: 15.14
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 89F7
  dmi.board.vendor: HP
  dmi.board.version: 14.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 14.27
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd11/08/2023:br15.14:efr14.27:svnHP:pnHPPavilionLaptop15-eg2xxx:pvr:rvnHP:rn89F7:rvr14.27:cvnHP:ct10:cvrChassisVersion:sku6W540UA#ABA:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-eg2xxx
  dmi.product.sku: 6W540UA#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/connman/+bug/2049988/+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 2049988] Re: Latest kernel kills wifi.

[Patrick M]

Any news on this?

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

Title:
  Latest kernel kills wifi.

Status in network-manager package in Ubuntu:
  New

Bug description:
  New kernel 6.0.5-14 boot up system does not recognize built in wifi
  adapter. When I drop to last kernel install wifi works fine.

  HP Pavillion With intel core I7 chip.

  Output of lshow --C network:

   *-network 
 description: Wireless interface
 product: MT7921 802.11ax PCI Express Wireless Network Adapter
 vendor: MEDIATEK Corp.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlp2s0
 version: 00
 serial: b4:8c:9d:28:0e:cb
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=mt7921e 
driverversion=6.2.0-39-generic firmware=01-20220209150915 
ip=192.168.1.81 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: iomemory:600-5ff iomemory:600-5ff iomemory:600-5ff irq:144 
memory:601210-60121f memory:601220-6012203fff 
memory:6012204000-6012204fff
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrick2379 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-15 (432 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: HP HP Pavilion Laptop 15-eg2xxx
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=2a43dcba-8f84-43f8-a1d6-ad38002f17c0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-39-generic N/A
   linux-backports-modules-6.2.0-39-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.24
  Tags:  jammy
  Uname: Linux 6.2.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2023
  dmi.bios.release: 15.14
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 89F7
  dmi.board.vendor: HP
  dmi.board.version: 14.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 14.27
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd11/08/2023:br15.14:efr14.27:svnHP:pnHPPavilionLaptop15-eg2xxx:pvr:rvnHP:rn89F7:rvr14.27:cvnHP:ct10:cvrChassisVersion:sku6W540UA#ABA:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-eg2xxx
  dmi.product.sku: 6W540UA#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2049988/+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 2054742] [NEW] mv on zfs causes out of memory, fixed in 9.2

[Patrick Domack]

Public bug reported:

coreutils from 6.0 to 9.2 causes out of memory errors when using zfs due
to recordsize is too large for coreutils to manage.

https://github.com/coreutils/coreutils/commit/6c343a55745a37a1d4d20f39a427170c37044a65

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

** Attachment added: "mv-strace.txt"
   
https://bugs.launchpad.net/bugs/2054742/+attachment/5748591/+files/mv-strace.txt

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

Title:
  mv on zfs causes out of memory, fixed in 9.2

Status in coreutils package in Ubuntu:
  New

Bug description:
  coreutils from 6.0 to 9.2 causes out of memory errors when using zfs
  due to recordsize is too large for coreutils to manage.

  
https://github.com/coreutils/coreutils/commit/6c343a55745a37a1d4d20f39a427170c37044a65

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2054742/+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 2053153] Re: initramfs-tools broken by libpam-tmpdir and /tmp mounted with noexec

[Patrick Schleizer]

Changed in initramfs-tools (Debian):
status: Unknown → Fix Released

This is wrong as you can see from the context of the ticket.

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

Title:
  initramfs-tools broken by libpam-tmpdir and /tmp mounted with noexec

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  I would like to forward the bug that was reported against Debian
  "certain update-initramfs actions broken on systems with' from
  'cryptsetup-initramfs: cryptkeyctl script fails to discover
  decrypt_keyctl even when present" [1] to upstream initramfs-tools,
  which I think is here.

  To reproduce this bug in Debian:

  1) sudo apt install libpam-tmpdir

  2) Mount /tmp with noexec.

  This breaks the cryptkeyctl hook.

  Could you fix initramfs-tools compatibility with libpam-tmpdir and
  /tmp mounted with noexec please?

  Is there some more appropriate temporary folder for update-initramfs
  to use?

  By comparison, dracut has no such issue.

  [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062756

  (Disclaimer: I am not affiliated with Debian and writing this on my
  own imitative.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2053153/+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 2049988] Re: Latest kernel kills wifi.

[Patrick M]

Any news on this bug? Latest patches did not affect it

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

Title:
  Latest kernel kills wifi.

Status in network-manager package in Ubuntu:
  New

Bug description:
  New kernel 6.0.5-14 boot up system does not recognize built in wifi
  adapter. When I drop to last kernel install wifi works fine.

  HP Pavillion With intel core I7 chip.

  Output of lshow --C network:

   *-network 
 description: Wireless interface
 product: MT7921 802.11ax PCI Express Wireless Network Adapter
 vendor: MEDIATEK Corp.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlp2s0
 version: 00
 serial: b4:8c:9d:28:0e:cb
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=mt7921e 
driverversion=6.2.0-39-generic firmware=01-20220209150915 
ip=192.168.1.81 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: iomemory:600-5ff iomemory:600-5ff iomemory:600-5ff irq:144 
memory:601210-60121f memory:601220-6012203fff 
memory:6012204000-6012204fff
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrick2379 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-15 (432 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: HP HP Pavilion Laptop 15-eg2xxx
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=2a43dcba-8f84-43f8-a1d6-ad38002f17c0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-39-generic N/A
   linux-backports-modules-6.2.0-39-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.24
  Tags:  jammy
  Uname: Linux 6.2.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2023
  dmi.bios.release: 15.14
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 89F7
  dmi.board.vendor: HP
  dmi.board.version: 14.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 14.27
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd11/08/2023:br15.14:efr14.27:svnHP:pnHPPavilionLaptop15-eg2xxx:pvr:rvnHP:rn89F7:rvr14.27:cvnHP:ct10:cvrChassisVersion:sku6W540UA#ABA:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-eg2xxx
  dmi.product.sku: 6W540UA#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2049988/+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 2053153] [NEW] initramfs-tools broken by libpam-tmpdir and /tmp mounted with noexec

[Patrick Schleizer]

Public bug reported:

I would like to forward the bug that was reported against Debian
"certain update-initramfs actions broken on systems with' from
'cryptsetup-initramfs: cryptkeyctl script fails to discover
decrypt_keyctl even when present" [1] to upstream initramfs-tools, which
I think is here.

To reproduce this bug in Debian:

1) sudo apt install libpam-tmpdir

2) Mount /tmp with noexec.

This breaks the cryptkeyctl hook.

Could you fix initramfs-tools compatibility with libpam-tmpdir and /tmp
mounted with noexec please?

Is there some more appropriate temporary folder for update-initramfs to
use?

By comparison, dracut has no such issue.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062756

(Disclaimer: I am not affiliated with Debian and writing this on my own
imitative.)

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

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

Title:
  initramfs-tools broken by libpam-tmpdir and /tmp mounted with noexec

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I would like to forward the bug that was reported against Debian
  "certain update-initramfs actions broken on systems with' from
  'cryptsetup-initramfs: cryptkeyctl script fails to discover
  decrypt_keyctl even when present" [1] to upstream initramfs-tools,
  which I think is here.

  To reproduce this bug in Debian:

  1) sudo apt install libpam-tmpdir

  2) Mount /tmp with noexec.

  This breaks the cryptkeyctl hook.

  Could you fix initramfs-tools compatibility with libpam-tmpdir and
  /tmp mounted with noexec please?

  Is there some more appropriate temporary folder for update-initramfs
  to use?

  By comparison, dracut has no such issue.

  [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062756

  (Disclaimer: I am not affiliated with Debian and writing this on my
  own imitative.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2053153/+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 2049988] Re: Latest kernel kills wifi.

[Patrick M]

Has anyone figured out a patch for this? there was an update today,
which I applied. Did not change anything with new kernel, but now old
version boots to airplane mode. I can get the wifi going on older kernel
still.

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

Title:
  Latest kernel kills wifi.

Status in network-manager package in Ubuntu:
  New

Bug description:
  New kernel 6.0.5-14 boot up system does not recognize built in wifi
  adapter. When I drop to last kernel install wifi works fine.

  HP Pavillion With intel core I7 chip.

  Output of lshow --C network:

   *-network 
 description: Wireless interface
 product: MT7921 802.11ax PCI Express Wireless Network Adapter
 vendor: MEDIATEK Corp.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlp2s0
 version: 00
 serial: b4:8c:9d:28:0e:cb
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=mt7921e 
driverversion=6.2.0-39-generic firmware=01-20220209150915 
ip=192.168.1.81 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: iomemory:600-5ff iomemory:600-5ff iomemory:600-5ff irq:144 
memory:601210-60121f memory:601220-6012203fff 
memory:6012204000-6012204fff
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrick2379 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-15 (432 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: HP HP Pavilion Laptop 15-eg2xxx
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=2a43dcba-8f84-43f8-a1d6-ad38002f17c0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-39-generic N/A
   linux-backports-modules-6.2.0-39-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.24
  Tags:  jammy
  Uname: Linux 6.2.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2023
  dmi.bios.release: 15.14
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 89F7
  dmi.board.vendor: HP
  dmi.board.version: 14.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 14.27
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd11/08/2023:br15.14:efr14.27:svnHP:pnHPPavilionLaptop15-eg2xxx:pvr:rvnHP:rn89F7:rvr14.27:cvnHP:ct10:cvrChassisVersion:sku6W540UA#ABA:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-eg2xxx
  dmi.product.sku: 6W540UA#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2049988/+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

Re: [Touch-packages] [Bug 2049988] Re: Latest kernel kills wifi.

[Patrick M]

Thank you for the reply. I had to apply the command twice. It gave me an 
error the first time. Report was sent ( I think)

On 1/21/24 03:16, Chris Guiver wrote:
> apport-collect 2049988

** Package changed: linux (Ubuntu) => network-manager (Ubuntu)

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

Title:
  Latest kernel kills wifi.

Status in network-manager package in Ubuntu:
  New

Bug description:
  New kernel 6.0.5-14 boot up system does not recognize built in wifi
  adapter. When I drop to last kernel install wifi works fine.

  HP Pavillion With intel core I7 chip.

  Output of lshow --C network:

   *-network 
 description: Wireless interface
 product: MT7921 802.11ax PCI Express Wireless Network Adapter
 vendor: MEDIATEK Corp.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlp2s0
 version: 00
 serial: b4:8c:9d:28:0e:cb
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=mt7921e 
driverversion=6.2.0-39-generic firmware=01-20220209150915 
ip=192.168.1.81 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: iomemory:600-5ff iomemory:600-5ff iomemory:600-5ff irq:144 
memory:601210-60121f memory:601220-6012203fff 
memory:6012204000-6012204fff
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrick2379 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-15 (432 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: HP HP Pavilion Laptop 15-eg2xxx
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=2a43dcba-8f84-43f8-a1d6-ad38002f17c0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-39-generic N/A
   linux-backports-modules-6.2.0-39-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.24
  Tags:  jammy
  Uname: Linux 6.2.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2023
  dmi.bios.release: 15.14
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 89F7
  dmi.board.vendor: HP
  dmi.board.version: 14.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 14.27
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd11/08/2023:br15.14:efr14.27:svnHP:pnHPPavilionLaptop15-eg2xxx:pvr:rvnHP:rn89F7:rvr14.27:cvnHP:ct10:cvrChassisVersion:sku6W540UA#ABA:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-eg2xxx
  dmi.product.sku: 6W540UA#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2049988/+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 1116421] Re: Ethernet mac address resets when cable unplugged

[Patrick Schleizer]

This bug needs to be forwarded to, reported upstream against Network
Manager (NM) otherwise chances that it will ever get fixed are even
lower if it is only reported here.

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

Title:
  Ethernet mac address resets when cable unplugged

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I'm not exactly sure if this is a network-manager bug, but if not perhaps you 
could point me in the right direction (or tell me how to find out what the 
right direction is)..
  A friend running 12.10 and myself running 12.04.1 both experienced the same 
problem.

  Using the following series of commands to change the ethernet MAC address 
works fine under some specific circumstances:
  ifconfig eth0 down
  ifconfig eth0 hw ether xx:xx:xx:xx:xx:xx
  ifconfig eth0 up

  If there is a wired connection defined in the network-manager gui
  (click the wireless signal-> Edit Connections...) and there is a
  Cloned Mac Address defined in there, the MAC address of eth0 WILL
  REVERT to it's original (hardware) MAC address upon connection of an
  ethernet cable. This is very strange and frustrating. In order for the
  above MAC address changes to take effect, there needs to be nothing
  filled in with the GUI.

  Second issue (I guess it is related) is that if everything is working
  correctly, the MAC address WILL REVERT to it's original (hardware) MAC
  address upon DISconncetion of the ethernet cable.

  Perhaps I am doing something horribly, horribly wrong here, but it's
  frustrating and hours of searching the forums have not given me any
  indication of the correct place/time to change MAC address. If
  network-manager does not want to respect the changes I have requested,
  then it should at least provide a functioning, documented alternative
  method in order to make the same change.

  What I would expect:
  Changing the MAC address of eth0 using the network-manager gui will actually 
change the MAC address everytime the interface is brought up.

  Current workaround:
  In /etc/rc.local, run the above commands for changing hardware address
  In /etc/network/if-post-down.d/ create a script that will sleep for 5 seconds 
and then run the above commands.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.4.0-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  Date: Tue Feb  5 08:15:48 2013
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  IpRoute:
   default via 192.168.1.254 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.65  metric 
2
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2013-02-03T13:48:28.620664
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   BattlecruiserOperational  61ddc2db-76fa-4c7e-9b11-fc68440e8a47   
802-11-wireless   1360080712   Tue 05 Feb 2013 08:11:52 AM PSTyes   
no /org/freedesktop/NetworkManager/Settings/1
   magiclab  f1b348f9-ff96-4729-b690-dcdb69c729e5   
802-11-wireless   1360014380   Mon 04 Feb 2013 01:46:20 PM PSTyes   
no /org/freedesktop/NetworkManager/Settings/7
   ubcsecure a141ff8b-b47f-47a4-81be-c01335b9aa0a   
802-11-wireless   1360034251   Mon 04 Feb 2013 07:17:31 PM PSTyes   
no /org/freedesktop/NetworkManager/Settings/6
   Wired connection 1e54ce990-cd66-461c-8343-60f4f099b7ec   
802-3-ethernet1360034239   Mon 04 Feb 2013 07:17:19 PM PSTyes   
no /org/freedesktop/NetworkManager/Settings/5
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.4.0connected   enabled   enabled 
enabled

[Touch-packages] [Bug 2012291] [NEW] package libgstreamer-plugins-bad1.0-0 1.22.0-3ubuntu2 failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/libgstbasecamerabinsrc-1.0.so.0.2200.0« zu übe

[Patrick Mohr]

Public bug reported:

dont know what this is but become message

ProblemType: Package
DistroRelease: Kali 2023.1
Package: libgstreamer-plugins-bad1.0-0 1.22.0-3ubuntu2
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Mar 20 17:17:48 2023
ErrorMessage: Versuch, 
»/usr/lib/x86_64-linux-gnu/libgstbasecamerabinsrc-1.0.so.0.2200.0« zu 
überschreiben, welches auch in Paket libgstreamer-plugins-good1.0-0:amd64 
1.22.0-4ubuntu1 ist
InstallationDate: Installed on 2023-03-20 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230320)
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.21+kali1
 apt  2.6.0
SourcePackage: gst-plugins-bad1.0
Title: package libgstreamer-plugins-bad1.0-0 1.22.0-3ubuntu2 failed to 
install/upgrade: Versuch, 
»/usr/lib/x86_64-linux-gnu/libgstbasecamerabinsrc-1.0.so.0.2200.0« zu 
überschreiben, welches auch in Paket libgstreamer-plugins-good1.0-0:amd64 
1.22.0-4ubuntu1 ist
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gst-plugins-bad1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package kali-rolling third-party-packages

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

Title:
  package libgstreamer-plugins-bad1.0-0 1.22.0-3ubuntu2 failed to
  install/upgrade: Versuch, »/usr/lib/x86_64-linux-
  gnu/libgstbasecamerabinsrc-1.0.so.0.2200.0« zu überschreiben, welches
  auch in Paket libgstreamer-plugins-good1.0-0:amd64 1.22.0-4ubuntu1 ist

Status in gst-plugins-bad1.0 package in Ubuntu:
  New

Bug description:
  dont know what this is but become message

  ProblemType: Package
  DistroRelease: Kali 2023.1
  Package: libgstreamer-plugins-bad1.0-0 1.22.0-3ubuntu2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Mar 20 17:17:48 2023
  ErrorMessage: Versuch, 
»/usr/lib/x86_64-linux-gnu/libgstbasecamerabinsrc-1.0.so.0.2200.0« zu 
überschreiben, welches auch in Paket libgstreamer-plugins-good1.0-0:amd64 
1.22.0-4ubuntu1 ist
  InstallationDate: Installed on 2023-03-20 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230320)
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21+kali1
   apt  2.6.0
  SourcePackage: gst-plugins-bad1.0
  Title: package libgstreamer-plugins-bad1.0-0 1.22.0-3ubuntu2 failed to 
install/upgrade: Versuch, 
»/usr/lib/x86_64-linux-gnu/libgstbasecamerabinsrc-1.0.so.0.2200.0« zu 
überschreiben, welches auch in Paket libgstreamer-plugins-good1.0-0:amd64 
1.22.0-4ubuntu1 ist
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2012291/+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 2004123] [NEW] Unable to display 4K 60hz Ubuntu 20.10 for Raspberry Pi

[Patrick Coulter]

Public bug reported:

Ubuntu 20.10 won't display 4K at 60hz on Raspberry Pi 4. Workaround of
editing the config.txt file does not seem to work. Hardware combination
is capable of 4K at 60hz as everything works perfectly fine with
Raspberry PI OS 64-bit.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-1004.10-raspi 5.19.7
Uname: Linux 5.19.0-1004-raspi aarch64
ApportVersion: 2.23.1-0ubuntu3
Architecture: arm64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 29 16:35:35 2023
DistUpgraded: Fresh install
DistroCodename: kinetic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 
ImageMediaBuild: 20221018.1
Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805/806 xHCI 
USB 3.0 Controller
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 
snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 
video=HDMI-A-1:3840x2160M@30 smsc95xx.macaddr=E4:5F:01:5E:92:10 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  zswap.enabled=1 
zswap.zpool=z3fold zswap.compressor=zstd dwc_otg.lpm_enable=0 console=tty1 
root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
 
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: apport-bug arm64 arm64-image kinetic performance raspi-image ubuntu 
wayland-session

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

Title:
  Unable to display 4K 60hz Ubuntu 20.10 for Raspberry Pi

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 20.10 won't display 4K at 60hz on Raspberry Pi 4. Workaround of
  editing the config.txt file does not seem to work. Hardware
  combination is capable of 4K at 60hz as everything works perfectly
  fine with Raspberry PI OS 64-bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-1004.10-raspi 5.19.7
  Uname: Linux 5.19.0-1004-raspi aarch64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 29 16:35:35 2023
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   
  ImageMediaBuild: 20221018.1
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805/806 
xHCI USB 3.0 Controller
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 
snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 
video=HDMI-A-1:3840x2160M@30 smsc95xx.macaddr=E4:5F:01:5E:92:10 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  zswap.enabled=1 
zswap.zpool=z3fold zswap.compressor=zstd dwc_otg.lpm_enable=0 console=tty1 
root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2004123/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : 

[Touch-packages] [Bug 1999285] [NEW] systemd-networkd constantly resets link on i350 when attempting to apply dhcp server provided MTU

[Patrick Geary]

Public bug reported:

This is identical to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1881207

It just happens to affect 22.04.1.

I can confirm that removing the `interface-mtu ` option from my dhcp
server cures the issue.


My netplan looks like:

network:
  ethernets:
enp33s0f0:
  dhcp4: true
  dhcp6: false
enp33s0f1:
  dhcp4: true
  dhcp6: false


This snippet is from my test when I changed the dhcpd to no longer serve MTU:


Dec 10 00:47:42 wiyuda-echo systemd[1]: Startup finished in 6min 14.070s 
(firmware) + 2.667s (loader) + 25.861s (kernel) + 3min 53.796s (userspace) = 
10min 36.395s.
Dec 10 00:47:42 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
Dec 10 00:47:42 wiyuda-echo systemd-networkd[4866]: enp33s0f0: Lost carrier
Dec 10 00:47:42 wiyuda-echo systemd-networkd[4866]: enp33s0f0: DHCP lease lost
Dec 10 00:47:42 wiyuda-echo systemd-networkd[4866]: enp33s0f0: DHCPv6 lease lost
Dec 10 00:47:43 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
Dec 10 00:47:46 wiyuda-echo kernel: igb :21:00.0 enp33s0f0: igb: enp33s0f0 
NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Dec 10 00:47:46 wiyuda-echo systemd-networkd[4866]: enp33s0f0: Gained carrier
Dec 10 00:47:46 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
Dec 10 00:47:51 wiyuda-echo systemd-networkd[4866]: enp33s0f0: DHCPv4 address 
172.16.214.138/16 via 172.16.0.3
Dec 10 00:47:51 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
Dec 10 00:47:51 wiyuda-echo systemd-networkd[4866]: enp33s0f0: Lost carrier
Dec 10 00:47:51 wiyuda-echo systemd-networkd[4866]: enp33s0f0: DHCP lease lost
Dec 10 00:47:51 wiyuda-echo kernel: igb :21:00.0 enp33s0f0: Reset adapter
Dec 10 00:47:52 wiyuda-echo systemd-networkd[4866]: enp33s0f0: DHCPv6 lease lost
Dec 10 00:47:52 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
Dec 10 00:47:52 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
Dec 10 00:47:55 wiyuda-echo kernel: igb :21:00.0 enp33s0f0: igb: enp33s0f0 
NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Dec 10 00:47:55 wiyuda-echo systemd-networkd[4866]: enp33s0f0: Gained carrier
Dec 10 00:47:55 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
Dec 10 00:47:59 wiyuda-echo systemd-networkd[4866]: enp33s0f0: DHCPv4 address 
172.16.214.138/16 via 172.16.0.3
Dec 10 00:47:59 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
Dec 10 00:47:59 wiyuda-echo systemd-networkd[4866]: enp33s0f0: Lost carrier
Dec 10 00:47:59 wiyuda-echo systemd-networkd[4866]: enp33s0f0: DHCP lease lost
Dec 10 00:47:59 wiyuda-echo systemd-networkd[4866]: enp33s0f0: DHCPv6 lease lost
Dec 10 00:47:59 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
Dec 10 00:47:59 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
Dec 10 00:48:02 wiyuda-echo systemd[1]: systemd-timedated.service: Deactivated 
successfully.
Dec 10 00:48:02 wiyuda-echo kernel: igb :21:00.0 enp33s0f0: igb: enp33s0f0 
NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Dec 10 00:48:02 wiyuda-echo systemd-networkd[4866]: enp33s0f0: Gained carrier
Dec 10 00:48:02 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
Dec 10 00:48:07 wiyuda-echo systemd-networkd[4866]: enp33s0f0: DHCPv4 address 
172.16.214.138/16 via 172.16.0.3
Dec 10 00:48:08 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
Dec 10 00:48:08 wiyuda-echo kernel: igb :21:00.0 enp33s0f0: Reset adapter
Dec 10 00:48:08 wiyuda-echo systemd-networkd[4866]: enp33s0f0: Lost carrier
Dec 10 00:48:08 wiyuda-echo systemd-networkd[4866]: enp33s0f0: DHCP lease lost
Dec 10 00:48:08 wiyuda-echo systemd-networkd[4866]: enp33s0f0: DHCPv6 lease lost

  <- This is when I changed the configuration and restarted the dhcpd.

Dec 10 00:48:08 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
Dec 10 00:48:08 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
Dec 10 00:48:11 wiyuda-echo kernel: igb :21:00.0 enp33s0f0: igb: enp33s0f0 
NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Dec 10 00:48:11 wiyuda-echo systemd-networkd[4866]: enp33s0f0: Gained carrier
Dec 10 00:48:11 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
Dec 10 00:48:16 wiyuda-echo systemd-networkd[4866]: enp33s0f0: DHCPv4 address 
172.16.214.138/16 via 172.16.0.3
Dec 10 00:48:16 

[Touch-packages] [Bug 1969375] Re: systemd-cryptenroll does not support TPM2 devices

[Patrick Banholzer]

This seems to be a really easy fix in the rules file.

patch for version systemd_249.11-0ubuntu3:

# diff -Naur rules.old rules.new
--- rules.old   2022-03-08 14:53:55.0 +0100
+++ rules.new   2022-05-24 16:17:07.548254564 +0200
@@ -84,7 +84,7 @@
-Dfdisk=false \
-Dpwquality=false \
-Dp11kit=false \
-   -Dtpm2=false \
+   -Dtpm2=true \
-Doomd=true \
-Dsysext=true \
-Dnscd=true \

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

Title:
  systemd-cryptenroll does not support TPM2 devices

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd-cryptenroll can make use of tpm2 modules to bind against
  secure boot pcrs and enable auto unlocking of luks devices.

  Following the instructions here:
  https://wiki.archlinux.org/title/Trusted_Platform_Module#systemd-cryptenroll

  the following commands fail on ubuntu jammy (5.15.0-25-generic)

  root@testbox:~# systemd-cryptenroll --tpm2-device=list
  TPM2 not supported on this build.
  root@testbox:~# systemd-cryptenroll --tpm2-device=auto --tpm2-pcrs=7 /dev/sda3
   Please enter current passphrase for disk /dev/sda3: ***
  root@testbox:~# echo $?
  1

  It appears that this issue has been resolved in the debian build for
  systemd here:  https://salsa.debian.org/systemd-
  team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8

  Can we get the same modifications to the Jammy systemd build?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969375/+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 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup

[Patrick Walker]

Same problem with both 22.04 Server and Ubuntu Mate 22.04.
All the confined GUI snaps have this problem and thus can't run.
First, I encountered running MATE desktop via X2Go Server.
Then I tried to see if using xRDP would work. No still problem persists whether 
I use xRDP or X2Go
Left unable to remotely run any UI confined snaps using Ubuntu Server/Mate 
22.04 until fix or workaround instructions provided.

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

Title:
  Can't run snaps: .slice/session-1.scope is not a snap cgroup

Status in snapd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed
Status in snapd package in Debian:
  New

Bug description:
  I just upgraded from hirsute to impish using do-release-upgrade. On
  the upgraded system, I can't run either firefox or chromium (both of
  which worked fine under hirsute). Both fail with:

  /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where
  NNN is my uid

  With firefox, I was able to fix the problem with:

  snap remove --purge firefox
  apt purge firefox
  apt install firefox

  Now firefox works. But I tried the same thing substituting chromium-
  browser for firefox, and it didn't help: chromium fails with the same
  error message.

  I guess there must be something left over from the hirsute version of
  snapd that isn't getting noticed or cleared by the impish version?

  Someone suggested this might be related to bug 1850667, but that bug
  is marked fixed as of a couple months ago, and I just did this upgrade
  today. Also, it doesn't mention the error message I'm seeing.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: snapd 2.53+21.10ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Nov 18 18:12:45 2021
  InstallationDate: Installed on 2020-04-29 (568 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: snapd
  UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Patrick Aoude]

Fresh install of 22.04 and enterprise wifi at work is no longer working.
Steps in comment #22 did not work for me.

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1969688] [NEW] possible hardware incompatibility

[Patrick Day]

Public bug reported:

Update repeatedly fails to install some package.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-107.121-generic 5.4.174
Uname: Linux 5.4.0-107-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.23
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Apr 20 17:16:16 2022
DistUpgraded: 2020-10-07 14:17:40,302 DEBUG icon theme changed, re-reading
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: Gigabyte Technology Co., Ltd GT218 [GeForce 210] [1458:3525]
InstallationDate: Installed on 2015-03-16 (2592 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-107-generic 
root=UUID=f382b311-5a9b-4768-bb28-40f911cc2040 ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-10-07 (560 days ago)
dmi.bios.date: 03/24/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F1
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A58M-HD2
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd03/24/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A58M-HD2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Tue Aug 21 10:57:10 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputVideo BusKEYBOARD, id 7
 inputPower Button KEYBOARD, id 8
 inputComposite USB PS2 Converter USB to PS2 Adaptor  v1.09 KEYBOARD, 
id 9
 inputComposite USB PS2 Converter USB to PS2 Adaptor  v1.09 KEYBOARD, 
id 10
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.7
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  possible hardware incompatibility

Status in xorg package in Ubuntu:
  New

Bug description:
  Update repeatedly fails to install some package.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-107.121-generic 5.4.174
  Uname: Linux 5.4.0-107-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Apr 20 17:16:16 2022
  DistUpgraded: 2020-10-07 14:17:40,302 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: Gigabyte Technology Co., Ltd GT218 [GeForce 210] [1458:3525]
  InstallationDate: Installed on 2015-03-16 (2592 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-107-generic 
root=UUID=f382b311-5a9b-4768-bb28-40f911cc2040 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-10-07 (560 days ago)
  dmi.bios.date: 03/24/2014
  dmi.bios.vendor: 

[Touch-packages] [Bug 1954628] Re: [USB-Audio - ALC4080] Front panel: Headphone output not working

[Patrick Beckmann]

I have a "MAG X570S TOMAHAWK MAX WIFI (MS-7D54)", which seems to be nearly 
identical except of WiFi and a M.2 cooler. On Ubuntu 22.04 the same problem 
exists. The above mentioned "pacmd" call works with that as well and allows 
front panel headphone audio, while running a similar command,
  pacmd load-module module-alsa-sink device=hw:2,3
allows me to use the SPDIF. Thanks a lot for hint!

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

Title:
  [USB-Audio - ALC4080] Front panel: Headphone output not working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have a MSI MAG X570s Torpedo MAX motherboard, which has an onboard
  'Starship/Matisse HD Audio Controller' (-> ALC4080 USB based audio
  chip) controller that has a weird mapping via USB audio (see bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873 for a similar
  configuration).

  Sound via line-out works fine without any interventions.

  Headphone output however does not, while Ubuntu correctly detects the
  headphones as being plugged in when selected sound is still output via
  line-out, instead of via the front panel headphone jack-out.

  After some debugging I figured the headphones are connected to a seperate 
Alsa device on the same card as the line-out.
  Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working 
audio output that plays just via the headphone out.

  I guess a quirk needs to be written for the configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  gijs   2129 F pulseaudio
   /dev/snd/pcmC2D1p:   gijs   2129 F...m pulseaudio
   /dev/snd/controlC0:  gijs   2129 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 13 09:28:19 2021
  InstallationDate: Installed on 2020-12-06 (371 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful
  Symptom_Card: USB Audio - USB Audio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [USB-Audio - USB Audio, playback] Playback problem
  UpgradeStatus: Upgraded to impish on 2021-09-28 (75 days ago)
  dmi.bios.date: 07/09/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: A.00
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAG X570S TORPEDO MAX (MS-7D54)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.00:bd07/09/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D54:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX570STORPEDOMAX(MS-7D54):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7D54
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1954628/+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 1967690] [NEW] Denied association with wpasupplicant 2:2.10-2

[Patrick Beckmann]

Public bug reported:

When I upgraded my computer to Ubuntu 22.04 with "wpasupplicant" version
2:2.10-2, it would no longer connect to my WiFi, but instead tries
multiple times without success. The WiFi card is a "Intel Corporation
Centrino Advanced-N 6205 [Taylor Peak] (rev 34)", the WiFi access point
is a AVM FritzBox 7530 with the current firmware 07.29. The WiFi
security is set PSK/personal mode with "WPA 2 + WPA 3". Please see below
for Syslog messages. Downgrading to version 2:2.9.0-21build1 makes WiFi
connectivity work again.

This sound a lot like the following problem to me:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003907

It might not be a bug in package wpasupplicant itself, but it seems to
effectively prevent networking and should probably be circumvented.

Syslog excerpt with wpasupplicant 2.10:

Apr  3 19:32:49 intel2400 wpa_supplicant[11655]: wlan0: SME: Trying to 
authenticate with xx:xx:xx:xx:xx:xx (SSID='xx' freq=5180 MHz)
Apr  3 19:32:49 intel2400 kernel: [22688.198598] wlan0: authenticate with 
xx:xx:xx:xx:xx:xx
Apr  3 19:32:49 intel2400 NetworkManager[849]:   [1649007169.4799] device 
(wlan0): supplicant interface state: disconnected -> authenticating
Apr  3 19:32:49 intel2400 kernel: [22688.201456] wlan0: send auth to 
xx:xx:xx:xx:xx:xx (try 1/3)
Apr  3 19:32:49 intel2400 wpa_supplicant[11655]: wlan0: SME: Trying to 
authenticate with xx:xx:xx:xx:xx:xx (SSID='xx' freq=5180 MHz)
Apr  3 19:32:49 intel2400 kernel: [22688.403926] wlan0: authenticate with 
xx:xx:xx:xx:xx:xx
Apr  3 19:32:49 intel2400 kernel: [22688.403938] wlan0: send auth to 
xx:xx:xx:xx:xx:xx (try 1/3)
Apr  3 19:32:49 intel2400 wpa_supplicant[11655]: wlan0: PMKSA-CACHE-ADDED 
xx:xx:xx:xx:xx:xx 0
Apr  3 19:32:49 intel2400 wpa_supplicant[11655]: wlan0: Trying to associate 
with xx:xx:xx:xx:xx:xx (SSID='xx' freq=5180 MHz)
Apr  3 19:32:49 intel2400 NetworkManager[849]:   [1649007169.7386] device 
(wlan0): supplicant interface state: authenticating -> associating
Apr  3 19:32:49 intel2400 kernel: [22688.461401] wlan0: authenticated
Apr  3 19:32:49 intel2400 kernel: [22688.465084] wlan0: associate with 
xx:xx:xx:xx:xx:xx (try 1/3)
Apr  3 19:32:49 intel2400 kernel: [22688.467925] wlan0: RX AssocResp from 
xx:xx:xx:xx:xx:xx (capab=0x1511 status=40 aid=0)
Apr  3 19:32:49 intel2400 kernel: [22688.467956] wlan0: xx:xx:xx:xx:xx:xx 
denied association (code=40)
Apr  3 19:32:49 intel2400 wpa_supplicant[11655]: wlan0: CTRL-EVENT-ASSOC-REJECT 
bssid=xx:xx:xx:xx:xx:xx status_code=40
Apr  3 19:32:49 intel2400 wpa_supplicant[11655]: wlan0: SME: Deauth request to 
the driver failed
Apr  3 19:32:49 intel2400 wpa_supplicant[11655]: BSSID xx:xx:xx:xx:xx:xx ignore 
list count incremented to 2, ignoring for 10 seconds
Apr  3 19:32:49 intel2400 NetworkManager[849]:   [1649007169.7705] device 
(wlan0): supplicant interface state: associating -> disconnected
Apr  3 19:32:49 intel2400 NetworkManager[849]:   [1649007169.8706] device 
(wlan0): supplicant interface state: disconnected -> scanning
[after that it would repeat]

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

** Package changed: wpa (Ubuntu) => wpasupplicant (Ubuntu)

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

Title:
  Denied association with wpasupplicant 2:2.10-2

Status in wpasupplicant package in Ubuntu:
  New

Bug description:
  When I upgraded my computer to Ubuntu 22.04 with "wpasupplicant"
  version 2:2.10-2, it would no longer connect to my WiFi, but instead
  tries multiple times without success. The WiFi card is a "Intel
  Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)", the WiFi
  access point is a AVM FritzBox 7530 with the current firmware 07.29.
  The WiFi security is set PSK/personal mode with "WPA 2 + WPA 3".
  Please see below for Syslog messages. Downgrading to version
  2:2.9.0-21build1 makes WiFi connectivity work again.

  This sound a lot like the following problem to me:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003907

  It might not be a bug in package wpasupplicant itself, but it seems to
  effectively prevent networking and should probably be circumvented.

  Syslog excerpt with wpasupplicant 2.10:

  Apr  3 19:32:49 intel2400 wpa_supplicant[11655]: wlan0: SME: Trying to 
authenticate with xx:xx:xx:xx:xx:xx (SSID='xx' freq=5180 MHz)
  Apr  3 19:32:49 intel2400 kernel: [22688.198598] wlan0: authenticate with 
xx:xx:xx:xx:xx:xx
  Apr  3 19:32:49 intel2400 NetworkManager[849]:   [1649007169.4799] 
device (wlan0): supplicant interface state: disconnected -> authenticating
  Apr  3 19:32:49 intel2400 kernel: [22688.201456] wlan0: send auth to 
xx:xx:xx:xx:xx:xx (try 1/3)
  Apr  3 19:32:49 intel2400 wpa_supplicant[11655]: wlan0: SME: Trying to 
authenticate with xx:xx:xx:xx:xx:xx (SSID='xx' freq=5180 MHz)
  Apr  3 19:32:49 intel2400 kernel: 

[Touch-packages] [Bug 1877879] Re: segfault in iris_dri.so

[Patrick Fasano]

** This bug is no longer a duplicate of bug 1876219
   iris driver for old cpu

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

Title:
  segfault in iris_dri.so

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  As of Ubuntu 20.04, on intel graphics with intel driver (not
  modesetting), I got segfault whenever anything tries to use GL.

  This happens unless I export MESA_LOADER_DRIVER_OVERRIDE=i965. One
  says that it does not happen with modesetting driver.

  (gdb) run
  Starting program: /usr/bin/glxgears 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x717cf700 (LWP 97070)]
  [New Thread 0x7fffebfff700 (LWP 97071)]
  [New Thread 0x70fce700 (LWP 97072)]
  [New Thread 0x7fffeb7fe700 (LWP 97073)]

  Thread 1 "glxgears" received signal SIGSEGV, Segmentation fault.
  0x76a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  (gdb) where
  #0  0x76a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #1  0x76c42de4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #2  0x76a59e5d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #3  0x76a5aa95 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #4  0x76099774 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #5  0x711e in ?? ()
  #6  0x6c88 in ?? ()
  #7  0x77ace0b3 in __libc_start_main (main=0x6410, argc=1, 
argv=0x7fffe698, init=, fini=, 
rtld_fini=, stack_end=0x7fffe688) at ../csu/libc-start.c:308
  #8  0x6f0a in ?? ()
  (gdb) 

  I believe, this is a bug in mesa tracked here:
  https://gitlab.freedesktop.org/mesa/mesa/issues/1358

  packages versions:
  libgl1-mesa-dri:amd64 20.0.4-2ubuntu1 
amd64 
  xserver-xorg-video-intel  2:2.99.917+git20200226-1
amd64
  xserver-xorg-core 2:1.20.8-2ubuntu2   
amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1877879/+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 1854588] Re: gdebi-gtk calls pkexec inappropriately

[Patrick Fasano]

I recently noticed that this is no longer occurring on Ubuntu MATE
20.04.3. I am uncertain when it was fixed.

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

Title:
  gdebi-gtk calls pkexec inappropriately

Status in gdebi:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1. Have Ubuntu with gdebi-gtk installed
  2. Open Firefox
  3. Visit some site with deb-package download link or use direct link like 
https://github.com/jgm/pandoc/releases/download/2.9.2.1/pandoc-2.9.2.1-1-amd64.deb
  4. Proceed with file downloading
  5. In Firefox select Library → Downloads, click on downloaded deb-file

  Expected results:
  * gdebi-gtk is opened, the package installs normally after users clicks 
Install button

  Actual results:
  * gdebi-gtk is opened, the package is not installed because of vanishing of 
gdebi-gtk window just after clicking Install button


  

  Before anyone says this bug already exists... it doesn't (at least as
  far as I can see).  It's just that a lot of similar bugs do/did exist
  where people have also experienced the same symptoms (of gdebi-gtk
  vanishing upon clicking 'Install').

  So yes this is the same symptoms, but it must be a different cause as
  the circumstances are different and doesn't have the same resolution.

  The meat of it...

  Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or 
with Chrome if you installed that) go to any site that offers a .deb package 
and either...
  a) choose to open it directly from the browser (rather than saving it to 
'Downloads' folder)
  b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that 
file from within the browser itself.

  You should find that gdebi-gtk appears but vanishes the moment you
  click 'Install' without a prompt for a password, an explanation or the
  package actually getting installed.

  This bug has existed since the beginning of Ubuntu 18.04 however it's
  been largely confused with other similar bugs.  I've had it on half a
  dozen machines and confirmed it exists with IRC users on #ubuntu-mate
  of freenode.

  However with *this* bug (compared to others) gdebi-gtk works perfectly
  fine if you run it from the terminal or just double click the .deb
  package from your file manager.

  It's the kind of bug which if you're a hardened desktop Linux user,
  you'd just work around it...

  But if you're a novice and you can't get a simple thing like
  Teamviewer installed (which is a .deb, and a thing I might ask someone
  to do over the phone to try to help them) you likely get fed up and
  re-install Windows :S

  Any input on this would be brilliant as I can't seem to get any
  logs/output.

  ~lantizia

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdebi/+bug/1854588/+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 1951142] [NEW] Windows change position after screen flashes in Wayland

[Patrick Garraud]

Public bug reported:

When using the Wayland session, the screen will sometimes randomly flash
(usually after opening an application). After the screen flashes, the
open windows will often end up in different positions or in different
monitors. Video of the issue is attached.

Expected Behavior: For the LibreOffice window to stay on the right
monitor and to not change size or position.

Actual Behavior: The LibreOffice window opens to the right after I open
Lollypop.

This issue doesn't exclusively happen while LibreOffice or when opening
Lollypop, however, opening Lollypop is one of the most predictable ways
to trigger the bug. The majority of the time, the bug occurs in the
middle of regular use without me triggering anything.


I'm using a dual monitor set-up, with a 2560X1080 monitor at 1x scaling hooked 
up to a 4K Hi-DPI laptop screen at 2x scaling.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 16 11:22:32 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 630 [1028:08ac]
   Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac]
InstallationDate: Installed on 2020-11-18 (362 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Dell Inc. Precision 5530 2-in-1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2020
dmi.bios.release: 1.11
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.11.10
dmi.board.name: 02TH5P
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.10:bd07/09/2020:br1.11:svnDellInc.:pnPrecision55302-in-1:pvr:sku08AC:rvnDellInc.:rn02TH5P:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5530 2-in-1
dmi.product.sku: 08AC
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.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 ubuntu wayland-session

** Attachment added: "Video of the bug occuring"
   
https://bugs.launchpad.net/bugs/1951142/+attachment/5541229/+files/Wayland%20Bug.webm

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

Title:
  Windows change position after screen flashes in Wayland

Status in xorg package in Ubuntu:
  New

Bug description:
  When using the Wayland session, the screen will sometimes randomly
  flash (usually after opening an application). After the screen
  flashes, the open windows will often end up in different positions or
  in different monitors. Video of the issue is attached.

  Expected Behavior: For the LibreOffice window to stay on the right
  monitor and to not change size or position.

  Actual Behavior: The LibreOffice window opens to the right after I
  open Lollypop.

  This issue doesn't exclusively happen while LibreOffice or when
  opening Lollypop, however, opening Lollypop is one of the most
  predictable ways to trigger the bug. The majority of the time, the bug
  occurs in the middle of regular use without me triggering anything.

  
  I'm using a dual monitor set-up, with a 2560X1080 monitor at 1x scaling 
hooked up to a 4K Hi-DPI laptop screen at 2x scaling.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 16 11:22:32 2021
  DistUpgraded: Fresh install

[Touch-packages] [Bug 1891215] Re: systemd-resolved re-creates /run/systemd/resolve/*resolv.conf for every IPv6 RA received

[Patrick Naubert]

Confirmed fixed on lxd02 and client site, running Focal.  No reboot was
done.

Thank you.

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

Title:
  systemd-resolved re-creates /run/systemd/resolve/*resolv.conf for
  every IPv6 RA received

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Confirmed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed
Status in systemd source package in Hirsute:
  Fix Committed

Bug description:
  [impact]

  networking changes, like RA events, can cause systemd-resolved to re-
  write the resolv.conf file, even if the contents didn't change,
  resulting in unnecessary increased amount of inotify events

  [test case]

  see original description for ipv6ra-related reproducer, or simple
  reproducer here:

  configure networkd with some config for (e.g.) eth0, but not a config
  that would result in /etc/resolv.conf changing when the interface goes
  up/down - for example, use static config with no DNS search domains.
  Then bring eth0 up/down while observing the md5sum (file content) does
  not change but the mtime does change.

  root@lp1891215-h:~# ip l set down dev eth0
  root@lp1891215-h:~# md5sum /etc/resolv.conf
  db23e80078515192c312e5f321ff0340  /etc/resolv.conf
  root@lp1891215-h:~# stat -t -L /etc/resolv.conf
  /etc/resolv.conf 740 8 81a4 101 103 fc 188 1 0 0 1625238218 1625238216 
1625238216 0 4096
  root@lp1891215-h:~# ip l set up dev eth0
  root@lp1891215-h:~# md5sum /etc/resolv.conf
  db23e80078515192c312e5f321ff0340  /etc/resolv.conf
  root@lp1891215-h:~# stat -t -L /etc/resolv.conf
  /etc/resolv.conf 740 8 81a4 101 103 fc 188 1 0 0 1625238227 1625238226 
1625238226 0 4096

  [regression potential]

  regressions would result in incorrect or missing data in the
  resolv.conf file, possibly resulting in dns failures or errors

  [scope]

  this is needed for h and eralier

  this is (potentially) fixed upstream by
  f3e1f00d03445911ee73729219cea88c8a70c612 which in first included in
  v248, so this is needed in hirsute and earlier

  [original description]

  # Issue description:

  On 2 Linode VMs that are used as lxd hosts, we noticed that
  /run/systemd/resolve/*resolv.conf were re-created quite frequently (~
  once per second). We noticed because of the log noise from lxd's
  dnsmasq instance using inotify to watch the target of /etc/resolv.conf
  (which points to the stub-resolv.conf in our case). This was (wrongly)
  reported as a lxd bug (https://github.com/lxc/lxd/issues/7765) until
  it became apparent it was more likely to be a problem with
  systemd(-resolved)?.

  The log noise is the observable problem that would be nice to see
  addressed:

    root@lxd02:~# uptime
     17:55:48 up  9:52,  1 user,  load average: 0.18, 0.11, 0.05
    root@lxd02:~# journalctl -b0 | grep -cF dnsmasq
    158609

  Upon further investigation, it seems that systemd-resolved re-creates
  the resolv.conf and stub-resolv.conf files whenever an IPv6 RA is
  received.

  1) One can observe that by setting systemd-resolved's service in debug
  mode:

  $ sudo systemctl edit systemd-resolved

  and in the editor that is opened, add and save this content:

  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug

  then restart systemd-resolved and watch the logs scroll by with:

  $ journalctl -fu systemd-resolved

  3) In another terminal, watch the files be recreated with:

  watch -d -n 0.1 stat /run/systemd/resolve/stub-resolv.conf

  3) In yet another terminal, run a packet capture and watch "ICMP6,
  router advertisement" messages come by:

  sudo tcpdump -ni eth0 icmp6

  You will see that every time a RA packet comes in, resolved's journal
  will log this:

    Aug 11 17:33:55 lxd02 systemd-resolved[15368]: Sent message
  type=signal sender=n/a destination=n/a path=/org/freedesktop/resolve1
  interface=org.freedesktop.DBus.Properties member=PropertiesChanged
  cookie=244 reply_cookie=0 signature=sa{sv}as error-name=n/a error-
  message=n/a

  And the stat monitoring terminal will blink to highlight the new inode
  and timestamps of the freshly replaced stub-resolv.conf file.

  # Additional information:

  root@lxd02:~# lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  root@lxd02:~# apt-cache policy systemd
  systemd:
    Installed: 245.4-4ubuntu3.2
    Candidate: 245.4-4ubuntu3.2
    Version table:
   *** 245.4-4ubuntu3.2 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   245.4-4ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  root@lxd02:~# uname -a
  Linux lxd01 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

To manage 

[Touch-packages] [Bug 1891215] Re: systemd-resolved re-creates /run/systemd/resolve/*resolv.conf for every IPv6 RA received

[Patrick Naubert]

On the same machine as sdeziel found the problem:

root@lxd02:~# lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04

root@lxd02:~# apt-cache policy systemd
systemd:
  Installed: 245.4-4ubuntu3.7
  Candidate: 245.4-4ubuntu3.7
  Version table:
 *** 245.4-4ubuntu3.7 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
100 /var/lib/dpkg/status
 245.4-4ubuntu3 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

root@lxd02:~# uname -a
Linux lxd02 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 
x86_64 x86_64 GNU/Linux

root@lxd02:~# date
Tue 29 Jun 2021 01:16:13 PM UTC

root@lxd02:~# tail -f /var/log/syslog
Jun 29 13:16:20 lxd02 dnsmasq[1896]: using nameserver 127.0.0.53#53
Jun 29 13:16:20 lxd02 dnsmasq[1896]: reading /etc/resolv.conf
Jun 29 13:16:20 lxd02 dnsmasq[1896]: using local addresses only for domain lxd
Jun 29 13:16:20 lxd02 dnsmasq[1896]: using nameserver 127.0.0.53#53
^C
root@lxd02:~# uptime
 13:16:35 up 4 min,  1 user,  load average: 0.74, 1.46, 0.74

Problem is still occuring.

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

Title:
  systemd-resolved re-creates /run/systemd/resolve/*resolv.conf for
  every IPv6 RA received

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  # Issue description:

  On 2 Linode VMs that are used as lxd hosts, we noticed that
  /run/systemd/resolve/*resolv.conf were re-created quite frequently (~
  once per second). We noticed because of the log noise from lxd's
  dnsmasq instance using inotify to watch the target of /etc/resolv.conf
  (which points to the stub-resolv.conf in our case). This was (wrongly)
  reported as a lxd bug (https://github.com/lxc/lxd/issues/7765) until
  it became apparent it was more likely to be a problem with
  systemd(-resolved)?.

  The log noise is the observable problem that would be nice to see
  addressed:

root@lxd02:~# uptime
 17:55:48 up  9:52,  1 user,  load average: 0.18, 0.11, 0.05
root@lxd02:~# journalctl -b0 | grep -cF dnsmasq
158609

  Upon further investigation, it seems that systemd-resolved re-creates
  the resolv.conf and stub-resolv.conf files whenever an IPv6 RA is
  received.

  1) One can observe that by setting systemd-resolved's service in debug
  mode:

  $ sudo systemctl edit systemd-resolved

  and in the editor that is opened, add and save this content:

  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug

  then restart systemd-resolved and watch the logs scroll by with:

  $ journalctl -fu systemd-resolved

  3) In another terminal, watch the files be recreated with:

  watch -d -n 0.1 stat /run/systemd/resolve/stub-resolv.conf

  3) In yet another terminal, run a packet capture and watch "ICMP6,
  router advertisement" messages come by:

  sudo tcpdump -ni eth0 icmp6

  
  You will see that every time a RA packet comes in, resolved's journal will 
log this:

Aug 11 17:33:55 lxd02 systemd-resolved[15368]: Sent message
  type=signal sender=n/a destination=n/a path=/org/freedesktop/resolve1
  interface=org.freedesktop.DBus.Properties member=PropertiesChanged
  cookie=244 reply_cookie=0 signature=sa{sv}as error-name=n/a error-
  message=n/a

  And the stat monitoring terminal will blink to highlight the new inode
  and timestamps of the freshly replaced stub-resolv.conf file.

  
  # Additional information:

  root@lxd02:~# lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  root@lxd02:~# apt-cache policy systemd
  systemd:
Installed: 245.4-4ubuntu3.2
Candidate: 245.4-4ubuntu3.2
Version table:
   *** 245.4-4ubuntu3.2 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   245.4-4ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  root@lxd02:~# uname -a
  Linux lxd01 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891215/+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 703800] Re: init: restart command fails to restart main process when pre-stop stanza exists

[Patrick Hemmer]

> How is systemd relevant?

Because it replaced upstart, and support for discontinued software tends
to get much less attention. If the issue was known for years and wasn't
fixed while the software still had a future, it became extremely
unlikely to be fixed once it didn't have a future.

> Precise is still supported. Trusty will be supported until 2019.

It's now 2021, and Trusty is in it's extended security maintenance
phase, of which this issue certainly does not qualify for. So it seems
the assessment was accurate.

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

Title:
  init: restart command fails to restart main process when pre-stop
  stanza exists

Status in upstart :
  Triaged
Status in upstart package in Ubuntu:
  Triaged

Bug description:
  While testing the portmap daemon's recent changes in Ubuntu which
  cause statd to properly follow it on stop/start, I tried to restart
  portmap, only to find that it was not in fact restarted.

  This happens with any job that has a pre-stop. The reason is that in
  job_restart(), the code does this:

  
  job_change_goal (job, JOB_STOP);
  job_change_goal (job, JOB_START);

  job_change_goal will return as soon as the *first* state change has
  been completed. If there is no pre-stop, that is the change from
  JOB_RUNNING to JOB_KILLED, which does dutifully kill the main process.

  However, if there is a pre-stop, the pre-stop is run, but then
  job_change_state returns to job_change_goal, which then returns to
  job_restart, which then changes the goal back to start, which makes
  the new job_next_state() one that will bypass the change to
  JOB_KILLED.

  This was found on upstart v0.6.7-3 in Ubuntu, but also exists in the
  code in the current trunk.

  TEST CASE

  1. create job file /etc/init/test-restart-prestop.conf  with this content:
  # test-restart-prestop

  pre-stop exec /bin/true

  exec /bin/sleep 3600
  2. run "start test-restart-prestop" -- record pid of job
  3. immediately run "restart test-restart-prestop" -- if bug is present, pid 
remains the same when it should be a new pid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/703800/+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 1927993] Re: Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction

[Patrick Gillespie]

** Package changed: ubuntu => wayland (Ubuntu)

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

Title:
  Gnome Activities Overview Unresponsive to Mouse or Touchscreen
  Interaction

Status in wayland package in Ubuntu:
  New

Bug description:
  This also effects the Ubuntu Dock.

  Ubuntu 21.04 installed on a Micosoft Surface Go.

  When invoking the Activities Overview, the overview ceases to be
  responsive to mouse clicks or to touchscreen interaction. The only
  interaction to which it responds is the keyboard.

  Likewise, the Ubuntu Dock also ceases to respond to mouse gestures,
  clicks or to touchscreen interaction.

  Meanwhile, apps continue to respond to both Mouse and Touchscreen
  gestures.

  I haven't yet found a workaround. That said, I experimented yesterday
  with limiting myself to touchscreen interaction and the bug, for the
  period of time that used the system, didn't appear. It's possible that
  there's some kind of conflict between the mouse, touchscreen and
  Wayland usage?

  When used under a Xorg session, this Bug doesn't appear to affect the
  system.

  Notes: I chose Wayland as the affected passage but apparently Wayland
  "does not exist in Ubuntu".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1927993/+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 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)

[Christopher Patrick]

Thanks for the workaround. Can confirm it works, I was just wondering
how the key was allowed to expire, and if there is anything being done
to make sure it doesn't happen again to this or other keys.

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

Title:
  EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic
  Signing Key (2016) 

Status in ubuntu-keyring package in Ubuntu:
  Confirmed

Bug description:
  The public key used by the debugging symbols repository
  /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu-
  dbgsym-keyring expired.

  $ apt policy ubuntu-dbgsym-keyring
  ubuntu-dbgsym-keyring:
    Installed: 2020.02.11.2
    Candidate: 2020.02.11.2
    Version table:
   *** 2020.02.11.2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status
  $ gpg --no-default-keyring --keyring 
/usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys
  /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg
  -
  pub   rsa4096 2016-03-21 [SC] [expired: 2021-03-20]
    F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622
  uid   [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key 
(2016) 

  
  Error message on "apt update":

  E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not 
signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: GPG error: http://ddebs.ubuntu.com bionic Release: The following 
signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive 
Automatic Signing Key (2016) 
  E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following 
signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive 
Automatic Signing Key (2016) 
  E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not 
signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+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 1441460] Re: [xubuntu] Failing to sleep after inactivity - power manager error?

[Patrick Boake]

uname -a

Linux Aspire1 5.4.0-66-generic #74~18.04.2-Ubuntu SMP Fri Feb 5 11:21:26
UTC 2021 i686 i686 i686 GNU/Linux

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

Title:
  [xubuntu] Failing to sleep after inactivity - power manager error?

Status in powermgmt-base package in Ubuntu:
  Incomplete
Status in xfce4-power-manager package in Ubuntu:
  Invalid

Bug description:
  Newly installed XUbuntu 14.10 on 2 different machines but both
  experience the same problem.

  Problem:

  Failing to sleep after inactivity and a "xfce4 power manager error"

  When setting the machine in xfce4-power-manager to suspend after e.g.
  15 minutes the machine will fail to suspend.

  This is the message that meets me when I login after a failed suspend:

  Power Manager Error  
  GDBus.Error:org.freedesktop.DBus.Error.NoReply:
  Did not receive a reply. Possible causes include: the
  remote application did not send a reply, the message
  bus security policy blocked the reply, the reply
  timeout expired, or the network connection was 
  broken.

  http://s27.postimg.org/l24boyvqp/Screenshot_2015_04_05_15_20_38.png

  I can suspend from the logout dialog box.

  The following command suspends the system just fine:
  $ dbus-send --system --print-reply --dest="org.freedesktop.UPower" 
/org/freedesktop/UPower org.freedesktop.UPower.Suspend

  $ xfce4-power-manager --dump
  ---
  Xfce power manager version 1.4.1
  With policykit support
  With network manager support
  ---
  Can suspend: True
  Can hibernate: False
  Authorized to suspend: True
  Authorized to hibernate: False
  Authorized to shutdown: True
  Has battery: False
  Has brightness panel: True
  Has power button: True
  Has hibernate button: True
  Has sleep button: True
  Has LID: False

  So I guess It's some kind of  auth or policykit issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1441460/+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 1441460] Re: [xubuntu] Failing to sleep after inactivity - power manager error?

[Patrick Boake]

ls -al ~/.config/autostart/light-locker.desktop
ls: cannot access '/home/patrick/.config/autostart/light-locker.desktop': No 
such file or directory

** Also affects: powermgmt-base (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [xubuntu] Failing to sleep after inactivity - power manager error?

Status in powermgmt-base package in Ubuntu:
  Incomplete
Status in xfce4-power-manager package in Ubuntu:
  Invalid

Bug description:
  Newly installed XUbuntu 14.10 on 2 different machines but both
  experience the same problem.

  Problem:

  Failing to sleep after inactivity and a "xfce4 power manager error"

  When setting the machine in xfce4-power-manager to suspend after e.g.
  15 minutes the machine will fail to suspend.

  This is the message that meets me when I login after a failed suspend:

  Power Manager Error  
  GDBus.Error:org.freedesktop.DBus.Error.NoReply:
  Did not receive a reply. Possible causes include: the
  remote application did not send a reply, the message
  bus security policy blocked the reply, the reply
  timeout expired, or the network connection was 
  broken.

  http://s27.postimg.org/l24boyvqp/Screenshot_2015_04_05_15_20_38.png

  I can suspend from the logout dialog box.

  The following command suspends the system just fine:
  $ dbus-send --system --print-reply --dest="org.freedesktop.UPower" 
/org/freedesktop/UPower org.freedesktop.UPower.Suspend

  $ xfce4-power-manager --dump
  ---
  Xfce power manager version 1.4.1
  With policykit support
  With network manager support
  ---
  Can suspend: True
  Can hibernate: False
  Authorized to suspend: True
  Authorized to hibernate: False
  Authorized to shutdown: True
  Has battery: False
  Has brightness panel: True
  Has power button: True
  Has hibernate button: True
  Has sleep button: True
  Has LID: False

  So I guess It's some kind of  auth or policykit issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1441460/+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 1915455] [NEW] Problème affichage

[Patrick]

Public bug reported:

Le pc se fige pendant quelques secondes ensuite l'écran devient noir et
tout redevient normal.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
Uname: Linux 5.4.96-050496-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 11 22:14:11 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 82G965 Integrated Graphics Controller [8086:29a2] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 82G965 Integrated Graphics Controller 
[1043:81ea]
InstallationDate: Installed on 2021-02-06 (4 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.96-050496-generic 
root=UUID=7fc41ded-4d1e-43f9-924a-2e58d834e881 ro
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/22/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0510
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5B-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0510:bd05/22/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
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 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/1915455

Title:
  Problème affichage

Status in xorg package in Ubuntu:
  New

Bug description:
  Le pc se fige pendant quelques secondes ensuite l'écran devient noir
  et tout redevient normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.4.96-050496-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 11 22:14:11 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 82G965 Integrated Graphics Controller [8086:29a2] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 82G965 Integrated Graphics Controller 
[1043:81ea]
  InstallationDate: Installed on 2021-02-06 (4 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.96-050496-generic 
root=UUID=7fc41ded-4d1e-43f9-924a-2e58d834e881 ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0510
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0510:bd05/22/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  

[Touch-packages] [Bug 1877879] Re: segfault in iris_dri.so

[Patrick Fasano]

*** This bug is a duplicate of bug 1876219 ***
https://bugs.launchpad.net/bugs/1876219

I have a similar hardware configuration (Intel(R) Core(TM) i5-8265U and
Mesa Intel(R) UHD Graphics 620) and see this issue as well. I don't
believe it's the same bug as bug 1876219.

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

Title:
  segfault in iris_dri.so

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  As of Ubuntu 20.04, on intel graphics with intel driver (not
  modesetting), I got segfault whenever anything tries to use GL.

  This happens unless I export MESA_LOADER_DRIVER_OVERRIDE=i965. One
  says that it does not happen with modesetting driver.

  (gdb) run
  Starting program: /usr/bin/glxgears 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x717cf700 (LWP 97070)]
  [New Thread 0x7fffebfff700 (LWP 97071)]
  [New Thread 0x70fce700 (LWP 97072)]
  [New Thread 0x7fffeb7fe700 (LWP 97073)]

  Thread 1 "glxgears" received signal SIGSEGV, Segmentation fault.
  0x76a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  (gdb) where
  #0  0x76a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #1  0x76c42de4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #2  0x76a59e5d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #3  0x76a5aa95 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #4  0x76099774 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #5  0x711e in ?? ()
  #6  0x6c88 in ?? ()
  #7  0x77ace0b3 in __libc_start_main (main=0x6410, argc=1, 
argv=0x7fffe698, init=, fini=, 
rtld_fini=, stack_end=0x7fffe688) at ../csu/libc-start.c:308
  #8  0x6f0a in ?? ()
  (gdb) 

  I believe, this is a bug in mesa tracked here:
  https://gitlab.freedesktop.org/mesa/mesa/issues/1358

  packages versions:
  libgl1-mesa-dri:amd64 20.0.4-2ubuntu1 
amd64 
  xserver-xorg-video-intel  2:2.99.917+git20200226-1
amd64
  xserver-xorg-core 2:1.20.8-2ubuntu2   
amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1877879/+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

[Patrick Banholzer]

Problem remains, my environment:

 - Kernel: 5.4.0-65-generic
 - OS: Ubuntu 20.04.2 LTS
 - Machine: Dell Precision 5550
 - Headset: Jabra Evolve 75

Couple of users facing the same issue here.

-- 
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 bluez package in Ubuntu:
  Confirmed
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/bluez/+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 1915026] [NEW] Souris inactive et écran figé

[Patrick]

Public bug reported:

Bug constaté lorsque firefox est ouvert. Une partie de l'écran sautille,
la souris est mobile mais ne contrôle plus rien, plus aucun clic actif.
Le clavier reste opérationnel et me permet d'ouvrir une console pour
fermer firefox.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb  8 15:55:34 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 82G965 Integrated Graphics Controller [8086:29a2] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 82G965 Integrated Graphics Controller 
[1043:81ea]
InstallationDate: Installed on 2021-02-06 (1 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=7fc41ded-4d1e-43f9-924a-2e58d834e881 ro
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/22/2007
dmi.bios.release: 8.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0510
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5B-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0510:bd05/22/2007:br8.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
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 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/1915026

Title:
  Souris inactive et écran figé

Status in xorg package in Ubuntu:
  New

Bug description:
  Bug constaté lorsque firefox est ouvert. Une partie de l'écran
  sautille, la souris est mobile mais ne contrôle plus rien, plus aucun
  clic actif. Le clavier reste opérationnel et me permet d'ouvrir une
  console pour fermer firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb  8 15:55:34 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82G965 Integrated Graphics Controller [8086:29a2] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 82G965 Integrated Graphics Controller 
[1043:81ea]
  InstallationDate: Installed on 2021-02-06 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=7fc41ded-4d1e-43f9-924a-2e58d834e881 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2007
  dmi.bios.release: 8.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0510
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 

[Touch-packages] [Bug 1850966] Re: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan

[Patrick Böhm]

PPS: I've been running Linux on a USB-Stick.

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

Title:
  Stuck at "Refreshing software cache" after enabling repository not
  updated for Eoan

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Software and Updates
  2. Go to "other software" and enable, for example, a repository disabled 
during upgrade to Eoan which is not updated for Eoan yet
  3. Press close and then reload on the dialog that opens.
  4. Refreshing software cache dialog is stuck

  After closing the dialogs by right clicking on the windows and the
  open apps bar, re opening Software and updates only shows a white
  square you can't interact with.

  Ubuntu 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1850966/+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 1850966] Re: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan

[Patrick Böhm]

In case your tryin to reset your windows password with "chntpw" and
you're getting this message "chntpw: Unable to open/read a hive,
exiting..":

Take a look here (
https://superuser.com/questions/1010229/recovering-a-windows-10
-password-when-the-partition-is-read-only ) and search for the comment,
which starts with: "There is an easy fix for this problem." <--- My next
solution. May it be your next and final solution.

And again: Salut.

PS: After the final reboot to Linux I didn't needed to do the steps for
getting "chntpw". I was also connected to the Internet from start. But
for beeing sure I did this "refreshing (software) cache"-stuff again. I
ignored getting "Chntpw" and i was going ahead with my tutorial, where I
stopped.

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

Title:
  Stuck at "Refreshing software cache" after enabling repository not
  updated for Eoan

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Software and Updates
  2. Go to "other software" and enable, for example, a repository disabled 
during upgrade to Eoan which is not updated for Eoan yet
  3. Press close and then reload on the dialog that opens.
  4. Refreshing software cache dialog is stuck

  After closing the dialogs by right clicking on the windows and the
  open apps bar, re opening Software and updates only shows a white
  square you can't interact with.

  Ubuntu 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1850966/+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 1850966] Re: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan

[Patrick Böhm]

Hello guys:

First: I'm german, and I think my english is not the best.

I had the same problem. All i did was to get Internet connection.

Sounds simple and silly - but when i got the internet connection, my
"refreshing (software) cache" made it till the end (closed itself just
like in the tutorial, which i am watching)  without problems & without a
"send this problem"-window.

My litle life story: I've been frustrated when I was waiting about a
night to hope, it would been solved in idle. Now - a week later - i am
frustrated with a smile in the face too.

I wish, that this kind of my solution is your solution.

Salut.

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

Title:
  Stuck at "Refreshing software cache" after enabling repository not
  updated for Eoan

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Software and Updates
  2. Go to "other software" and enable, for example, a repository disabled 
during upgrade to Eoan which is not updated for Eoan yet
  3. Press close and then reload on the dialog that opens.
  4. Refreshing software cache dialog is stuck

  After closing the dialogs by right clicking on the windows and the
  open apps bar, re opening Software and updates only shows a white
  square you can't interact with.

  Ubuntu 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1850966/+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 1905228] [NEW] DIsplay Rotates to Portrait Mode when Certain Apps Open

[Patrick Garraud]

Public bug reported:

When using a 2 in 1 tablet with auto-rotation (Dell Precision 5530 2 in
1), the screen will frequently incorrectly rotate whenever some apps
open. This has been observed with Settings, Videos, Steam, Lollypop and
Firefox. Issue still occurs when the screen rotation is locked.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 22 22:59:56 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 630 [1028:08ac]
   Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac]
InstallationDate: Installed on 2020-11-18 (4 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 004: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
 Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 5530 2-in-1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.11.10
dmi.board.name: 02TH5P
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.10:bd07/09/2020:svnDellInc.:pnPrecision55302-in-1:pvr:rvnDellInc.:rn02TH5P:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5530 2-in-1
dmi.product.sku: 08AC
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.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu wayland-session

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

Title:
  DIsplay Rotates to Portrait Mode when Certain Apps Open

Status in xorg package in Ubuntu:
  New

Bug description:
  When using a 2 in 1 tablet with auto-rotation (Dell Precision 5530 2
  in 1), the screen will frequently incorrectly rotate whenever some
  apps open. This has been observed with Settings, Videos, Steam,
  Lollypop and Firefox. Issue still occurs when the screen rotation is
  locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 22:59:56 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:08ac]
 Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac]
  InstallationDate: Installed on 2020-11-18 (4 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5530 2-in-1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: 

[Touch-packages] [Bug 1905076] RebootRequiredPkgs.txt

[Patrick Michael May]

apport information

** Attachment added: "RebootRequiredPkgs.txt"
   
https://bugs.launchpad.net/bugs/1905076/+attachment/5436630/+files/RebootRequiredPkgs.txt

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

Title:
  module-alsa-sink's "control" argument causes segmentation fault

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Loading the pulseaudio module 'module-alsa-sink' with the "control"
  argument causes pulseaudio to segfault on my system.

  In /etc/pulse/default.pa find this line:

  #load-module module-alsa-sink

  and change it to this:

  load-module module-alsa-sink control=Master

  then restart pulseaudio by running these commands:

  pulseaudio -k
  pulseaudio --start

  Notice that it prints this into the terminal.
  E: [pulseaudio] main.c: Daemon startup failed.

  Try starting pulseaudio itself in the terminal, and you see what's happening:
  W: [pulseaudio] pid.c: Stale PID file, overwriting.
  Segmentation fault (core dumped)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-04-15 (219 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: pulseaudio 1:13.99.2-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  groovy
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1804
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1804:bd07/29/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

[Patrick Michael May]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1905076/+attachment/5436624/+files/CurrentDmesg.txt

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

Title:
  module-alsa-sink's "control" argument causes segmentation fault

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Loading the pulseaudio module 'module-alsa-sink' with the "control"
  argument causes pulseaudio to segfault on my system.

  In /etc/pulse/default.pa find this line:

  #load-module module-alsa-sink

  and change it to this:

  load-module module-alsa-sink control=Master

  then restart pulseaudio by running these commands:

  pulseaudio -k
  pulseaudio --start

  Notice that it prints this into the terminal.
  E: [pulseaudio] main.c: Daemon startup failed.

  Try starting pulseaudio itself in the terminal, and you see what's happening:
  W: [pulseaudio] pid.c: Stale PID file, overwriting.
  Segmentation fault (core dumped)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-04-15 (219 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: pulseaudio 1:13.99.2-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  groovy
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1804
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1804:bd07/29/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

[Patrick Michael May]

apport information

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

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

Title:
  module-alsa-sink's "control" argument causes segmentation fault

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Loading the pulseaudio module 'module-alsa-sink' with the "control"
  argument causes pulseaudio to segfault on my system.

  In /etc/pulse/default.pa find this line:

  #load-module module-alsa-sink

  and change it to this:

  load-module module-alsa-sink control=Master

  then restart pulseaudio by running these commands:

  pulseaudio -k
  pulseaudio --start

  Notice that it prints this into the terminal.
  E: [pulseaudio] main.c: Daemon startup failed.

  Try starting pulseaudio itself in the terminal, and you see what's happening:
  W: [pulseaudio] pid.c: Stale PID file, overwriting.
  Segmentation fault (core dumped)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-04-15 (219 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: pulseaudio 1:13.99.2-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  groovy
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1804
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1804:bd07/29/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

[Patrick Michael May]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1905076/+attachment/5436629/+files/PulseList.txt

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

Title:
  module-alsa-sink's "control" argument causes segmentation fault

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Loading the pulseaudio module 'module-alsa-sink' with the "control"
  argument causes pulseaudio to segfault on my system.

  In /etc/pulse/default.pa find this line:

  #load-module module-alsa-sink

  and change it to this:

  load-module module-alsa-sink control=Master

  then restart pulseaudio by running these commands:

  pulseaudio -k
  pulseaudio --start

  Notice that it prints this into the terminal.
  E: [pulseaudio] main.c: Daemon startup failed.

  Try starting pulseaudio itself in the terminal, and you see what's happening:
  W: [pulseaudio] pid.c: Stale PID file, overwriting.
  Segmentation fault (core dumped)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-04-15 (219 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: pulseaudio 1:13.99.2-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  groovy
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1804
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1804:bd07/29/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

[Patrick Michael May]

apport information

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

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

Title:
  module-alsa-sink's "control" argument causes segmentation fault

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Loading the pulseaudio module 'module-alsa-sink' with the "control"
  argument causes pulseaudio to segfault on my system.

  In /etc/pulse/default.pa find this line:

  #load-module module-alsa-sink

  and change it to this:

  load-module module-alsa-sink control=Master

  then restart pulseaudio by running these commands:

  pulseaudio -k
  pulseaudio --start

  Notice that it prints this into the terminal.
  E: [pulseaudio] main.c: Daemon startup failed.

  Try starting pulseaudio itself in the terminal, and you see what's happening:
  W: [pulseaudio] pid.c: Stale PID file, overwriting.
  Segmentation fault (core dumped)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-04-15 (219 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: pulseaudio 1:13.99.2-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  groovy
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1804
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1804:bd07/29/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

[Patrick Michael May]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1905076/+attachment/5436626/+files/PaInfo.txt

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

Title:
  module-alsa-sink's "control" argument causes segmentation fault

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Loading the pulseaudio module 'module-alsa-sink' with the "control"
  argument causes pulseaudio to segfault on my system.

  In /etc/pulse/default.pa find this line:

  #load-module module-alsa-sink

  and change it to this:

  load-module module-alsa-sink control=Master

  then restart pulseaudio by running these commands:

  pulseaudio -k
  pulseaudio --start

  Notice that it prints this into the terminal.
  E: [pulseaudio] main.c: Daemon startup failed.

  Try starting pulseaudio itself in the terminal, and you see what's happening:
  W: [pulseaudio] pid.c: Stale PID file, overwriting.
  Segmentation fault (core dumped)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-04-15 (219 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: pulseaudio 1:13.99.2-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  groovy
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1804
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1804:bd07/29/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

[Patrick Michael May]

apport information

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

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

Title:
  module-alsa-sink's "control" argument causes segmentation fault

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Loading the pulseaudio module 'module-alsa-sink' with the "control"
  argument causes pulseaudio to segfault on my system.

  In /etc/pulse/default.pa find this line:

  #load-module module-alsa-sink

  and change it to this:

  load-module module-alsa-sink control=Master

  then restart pulseaudio by running these commands:

  pulseaudio -k
  pulseaudio --start

  Notice that it prints this into the terminal.
  E: [pulseaudio] main.c: Daemon startup failed.

  Try starting pulseaudio itself in the terminal, and you see what's happening:
  W: [pulseaudio] pid.c: Stale PID file, overwriting.
  Segmentation fault (core dumped)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-04-15 (219 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: pulseaudio 1:13.99.2-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  groovy
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1804
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1804:bd07/29/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

[Patrick Michael May]

apport information

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1905076/+attachment/5436623/+files/AudioDevicesInUse.txt

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

Title:
  module-alsa-sink's "control" argument causes segmentation fault

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Loading the pulseaudio module 'module-alsa-sink' with the "control"
  argument causes pulseaudio to segfault on my system.

  In /etc/pulse/default.pa find this line:

  #load-module module-alsa-sink

  and change it to this:

  load-module module-alsa-sink control=Master

  then restart pulseaudio by running these commands:

  pulseaudio -k
  pulseaudio --start

  Notice that it prints this into the terminal.
  E: [pulseaudio] main.c: Daemon startup failed.

  Try starting pulseaudio itself in the terminal, and you see what's happening:
  W: [pulseaudio] pid.c: Stale PID file, overwriting.
  Segmentation fault (core dumped)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-04-15 (219 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: pulseaudio 1:13.99.2-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  groovy
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1804
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1804:bd07/29/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905076/+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 1905076] Re: module-alsa-sink's "control" argument causes segmentation fault

[Patrick Michael May]

apport information

** Tags added: apport-collected groovy

** Description changed:

  Loading the pulseaudio module 'module-alsa-sink' with the "control"
  argument causes pulseaudio to segfault on my system.
  
  In /etc/pulse/default.pa find this line:
  
  #load-module module-alsa-sink
  
  and change it to this:
  
  load-module module-alsa-sink control=Master
  
  then restart pulseaudio by running these commands:
  
  pulseaudio -k
  pulseaudio --start
  
  Notice that it prints this into the terminal.
  E: [pulseaudio] main.c: Daemon startup failed.
  
  Try starting pulseaudio itself in the terminal, and you see what's happening:
  W: [pulseaudio] pid.c: Stale PID file, overwriting.
  Segmentation fault (core dumped)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu50.1
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 20.10
+ InstallationDate: Installed on 2020-04-15 (219 days ago)
+ InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
+ Package: pulseaudio 1:13.99.2-1ubuntu2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
+ Tags:  groovy
+ Uname: Linux 5.4.0-54-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 07/29/2019
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 1804
+ dmi.board.asset.tag: Default string
+ dmi.board.name: PRIME B450-PLUS
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: Rev X.0x
+ dmi.chassis.asset.tag: Default string
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Default string
+ dmi.chassis.version: Default string
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1804:bd07/29/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: System Product Name
+ dmi.product.sku: SKU
+ dmi.product.version: System Version
+ dmi.sys.vendor: System manufacturer

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1905076/+attachment/5436622/+files/AlsaInfo.txt

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

Title:
  module-alsa-sink's "control" argument causes segmentation fault

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Loading the pulseaudio module 'module-alsa-sink' with the "control"
  argument causes pulseaudio to segfault on my system.

  In /etc/pulse/default.pa find this line:

  #load-module module-alsa-sink

  and change it to this:

  load-module module-alsa-sink control=Master

  then restart pulseaudio by running these commands:

  pulseaudio -k
  pulseaudio --start

  Notice that it prints this into the terminal.
  E: [pulseaudio] main.c: Daemon startup failed.

  Try starting pulseaudio itself in the terminal, and you see what's happening:
  W: [pulseaudio] pid.c: Stale PID file, overwriting.
  Segmentation fault (core dumped)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-04-15 (219 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: pulseaudio 1:13.99.2-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Tags:  groovy
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1804
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1804:bd07/29/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905076/+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 1905076] [NEW] module-alsa-sink's "control" argument causes segmentation fault

[Patrick Michael May]

Public bug reported:

Loading the pulseaudio module 'module-alsa-sink' with the "control"
argument causes pulseaudio to segfault on my system.

In /etc/pulse/default.pa find this line:

#load-module module-alsa-sink

and change it to this:

load-module module-alsa-sink control=Master

then restart pulseaudio by running these commands:

pulseaudio -k
pulseaudio --start

Notice that it prints this into the terminal.
E: [pulseaudio] main.c: Daemon startup failed.

Try starting pulseaudio itself in the terminal, and you see what's happening:
W: [pulseaudio] pid.c: Stale PID file, overwriting.
Segmentation fault (core dumped)

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

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

Title:
  module-alsa-sink's "control" argument causes segmentation fault

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Loading the pulseaudio module 'module-alsa-sink' with the "control"
  argument causes pulseaudio to segfault on my system.

  In /etc/pulse/default.pa find this line:

  #load-module module-alsa-sink

  and change it to this:

  load-module module-alsa-sink control=Master

  then restart pulseaudio by running these commands:

  pulseaudio -k
  pulseaudio --start

  Notice that it prints this into the terminal.
  E: [pulseaudio] main.c: Daemon startup failed.

  Try starting pulseaudio itself in the terminal, and you see what's happening:
  W: [pulseaudio] pid.c: Stale PID file, overwriting.
  Segmentation fault (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905076/+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 1904939] [NEW] Monitor Settings Don't Get Applied in Wayland

[Patrick Garraud]

Public bug reported:

When configuring a 1080p monitor and a 4k monitor in extended screen
mode while using Wayland, when trying to change the screen positions or
which screen is the primary screen in the Monitor Settings, the settings
reset to default when Apply is clicked. Choosing to "Revert the
Settings" during the 15-second timer causes it to apply the changed
settings, but this resets whenever a pop-up message appears or when
returning to the Monitor Settings.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 19 16:47:09 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 630 [1028:08ac]
   Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac]
InstallationDate: Installed on 2020-11-18 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Dell Inc. Precision 5530 2-in-1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.11.10
dmi.board.name: 02TH5P
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.10:bd07/09/2020:svnDellInc.:pnPrecision55302-in-1:pvr:rvnDellInc.:rn02TH5P:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5530 2-in-1
dmi.product.sku: 08AC
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.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu wayland-session

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

Title:
  Monitor Settings Don't Get Applied in Wayland

Status in xorg package in Ubuntu:
  New

Bug description:
  When configuring a 1080p monitor and a 4k monitor in extended screen
  mode while using Wayland, when trying to change the screen positions
  or which screen is the primary screen in the Monitor Settings, the
  settings reset to default when Apply is clicked. Choosing to "Revert
  the Settings" during the 15-second timer causes it to apply the
  changed settings, but this resets whenever a pop-up message appears or
  when returning to the Monitor Settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 19 16:47:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:08ac]
 Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac]
  InstallationDate: Installed on 2020-11-18 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Precision 5530 2-in-1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.10
  dmi.board.name: 02TH5P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Touch-packages] [Bug 1898753] Re: Non-existent home directory entry in /etc/passwd

[Patrick Goetz]

** Description changed:

  This bug applies to both Ubuntu 18.04 and Ubuntu 20.04, the two distros
  I've checked.
  
  This is likely a packaging error.  The syslog user appears in
  /etc/passwd as:
  
-   syslog:x:102:106::/home/syslog:/usr/sbin/nologin
+   syslog:x:102:106::/home/syslog:/usr/sbin/nologin
  
  Of course there is no directory /home/syslog.  This appears innocuous,
  but can cause problems for users that have, say autofs mounted home
- directories.  To cite one example, the python virtual envionment
- anaconda trolls through /etc/passw looking for environments in
+ directories.  To cite one example, the python virtual environment
+ anaconda trolls through /etc/passwd looking for environments in
  /home/USER.  This triggers autofs to try and mount /home/syslog, which
- doesn't existing, causing the automounter to hang under certain
+ doesn't exist, causing the automounter to hang under certain
  circumstances.  In, for example, Arch linux, this entry would appear as
  the considerably more sensible
  
-   syslog:x:102:106::/:/usr/sbin/nologin
+   syslog:x:102:106::/:/usr/sbin/nologin
  
  While an edge case in the current compute environment, this is also a
  very easy fix.  Don't reference non-existent directories. Many Ubuntu
  packages make this packaging error when creating local users with non-
  existent home directories; e.g. cups-pk-helper, which I'm filing a bug
  report for next.

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

Title:
  Non-existent home directory entry in /etc/passwd

Status in rsyslog package in Ubuntu:
  New

Bug description:
  This bug applies to both Ubuntu 18.04 and Ubuntu 20.04, the two
  distros I've checked.

  This is likely a packaging error.  The syslog user appears in
  /etc/passwd as:

    syslog:x:102:106::/home/syslog:/usr/sbin/nologin

  Of course there is no directory /home/syslog.  This appears innocuous,
  but can cause problems for users that have, say autofs mounted home
  directories.  To cite one example, the python virtual environment
  anaconda trolls through /etc/passwd looking for environments in
  /home/USER.  This triggers autofs to try and mount /home/syslog, which
  doesn't exist, causing the automounter to hang under certain
  circumstances.  In, for example, Arch linux, this entry would appear
  as the considerably more sensible

    syslog:x:102:106::/:/usr/sbin/nologin

  While an edge case in the current compute environment, this is also a
  very easy fix.  Don't reference non-existent directories. Many Ubuntu
  packages make this packaging error when creating local users with non-
  existent home directories; e.g. cups-pk-helper, which I'm filing a bug
  report for next.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1898753/+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 1898753] [NEW] Non-existent home directory entry in /etc/passwd

[Patrick Goetz]

Public bug reported:

This bug applies to both Ubuntu 18.04 and Ubuntu 20.04, the two distros
I've checked.

This is likely a packaging error.  The syslog user appears in
/etc/passwd as:

  syslog:x:102:106::/home/syslog:/usr/sbin/nologin

Of course there is no directory /home/syslog.  This appears innocuous,
but can cause problems for users that have, say autofs mounted home
directories.  To cite one example, the python virtual envionment
anaconda trolls through /etc/passw looking for environments in
/home/USER.  This triggers autofs to try and mount /home/syslog, which
doesn't existing, causing the automounter to hang under certain
circumstances.  In, for example, Arch linux, this entry would appear as
the considerably more sensible

  syslog:x:102:106::/:/usr/sbin/nologin

While an edge case in the current compute environment, this is also a
very easy fix.  Don't reference non-existent directories. Many Ubuntu
packages make this packaging error when creating local users with non-
existent home directories; e.g. cups-pk-helper, which I'm filing a bug
report for next.

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

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

Title:
  Non-existent home directory entry in /etc/passwd

Status in rsyslog package in Ubuntu:
  New

Bug description:
  This bug applies to both Ubuntu 18.04 and Ubuntu 20.04, the two
  distros I've checked.

  This is likely a packaging error.  The syslog user appears in
  /etc/passwd as:

syslog:x:102:106::/home/syslog:/usr/sbin/nologin

  Of course there is no directory /home/syslog.  This appears innocuous,
  but can cause problems for users that have, say autofs mounted home
  directories.  To cite one example, the python virtual envionment
  anaconda trolls through /etc/passw looking for environments in
  /home/USER.  This triggers autofs to try and mount /home/syslog, which
  doesn't existing, causing the automounter to hang under certain
  circumstances.  In, for example, Arch linux, this entry would appear
  as the considerably more sensible

syslog:x:102:106::/:/usr/sbin/nologin

  While an edge case in the current compute environment, this is also a
  very easy fix.  Don't reference non-existent directories. Many Ubuntu
  packages make this packaging error when creating local users with non-
  existent home directories; e.g. cups-pk-helper, which I'm filing a bug
  report for next.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1898753/+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 756317] Re: Captive portals may corrupt apt translation indices

[Patrick Wigmore]

Unfortunately, I cannot reproduce the bug by deliberately running apt
update while the captive portal is in effect.

I think I must have hit some obscure edge case that isn't covered by the
existing fix. Maybe something to do with switching networks during an
automatic update? Who knows. Clearly I haven't got enough information to
resolve this.

Unfortunately I did not retain a copy of the files I removed, so they
cannot be analysed, though I have saved a copy of the current captive
portal page if anyone wants me to upload it. (It might differ from the
one that triggered the bug for me though.)

Apologies for double comment.

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

Title:
  Captive portals may corrupt apt translation indices

Status in apt package in Ubuntu:
  Fix Released
Status in apt package in Debian:
  Fix Released

Bug description:
  I have an adsl modem which returns an html page if the adsl link is
  broken. This page ends as the content of the apt cache files stored in
  /var/lib/apt/lists, which breaks apt.

  The only way to make apt work again is to delete all the files stored
  in /var/lib/apt/lists.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/756317/+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 756317] Re: Captive portals may corrupt apt translation indices

[Patrick Wigmore]

I believe I have just experienced this bug in xenial with apt 1.2.32.
Files in /var/lib/apt/lists contained HTML from a captive portal, breaking apt 
until they were removed.

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

Title:
  Captive portals may corrupt apt translation indices

Status in apt package in Ubuntu:
  Fix Released
Status in apt package in Debian:
  Fix Released

Bug description:
  I have an adsl modem which returns an html page if the adsl link is
  broken. This page ends as the content of the apt cache files stored in
  /var/lib/apt/lists, which breaks apt.

  The only way to make apt work again is to delete all the files stored
  in /var/lib/apt/lists.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/756317/+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 1744372] Re: gparted does not start - Unit -.mount does not exist, proceeding anyway.

[patrick samples]

*** This bug is a duplicate of bug 1652282 ***
https://bugs.launchpad.net/bugs/1652282

^
apt install libgtk2.0-0

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

Title:
  gparted does not start - Unit -.mount does not exist, proceeding
  anyway.

Status in gparted package in Ubuntu:
  Confirmed
Status in wayland package in Ubuntu:
  Invalid

Bug description:
  1. fresh ubuntu 18.04 daily: lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2. install gparted with Software:
  gparted:
    Installiert:   0.30.0-3ubuntu1
    Installationskandidat: 0.30.0-3ubuntu1
    Versionstabelle:
   *** 0.30.0-3ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. launch with icon - enter password - nothing.
  4.launch in terminal:
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:8328): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.

  How to Fix: run xhost +local: before gparted! # this only bypass the
  wayland restriction; meaning a security violation (not a fix !!! )

  thomas@ubuntu-1804:~$ xhost +local:
  non-network local connections being added to access control list
  thomas@ubuntu-1804:~$ gparted
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  Gtk-Message: Failed to load module "canberra-gtk-module"
  ==
  libparted : 3.2
  ==
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gparted 0.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 19 19:45:14 2018
  InstallationDate: Installed on 2018-01-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gparted
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1744372/+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 1162475] Re: [hostnamed] Changing hostname doesn't update /etc/hosts

[Patrick O'Keeffe]

Hi apologies if this is the wrong thread. Just wanted to report I see
this issue on the Raspberry Pi build of Ubuntu MATE 16.04 running `mate-
control-center` 1.16.1-1~xenial4.0 and `systemd` 229-4ubuntu21.22.

I see resolution failures using `sudo` afterwards so even though it
still works, stdout gets polluted with error messages. I would call that
an ill effect.

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

Title:
  [hostnamed] Changing hostname doesn't update /etc/hosts

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Triaged
Status in unity-control-center source package in Xenial:
  Confirmed
Status in gnome-control-center package in Debian:
  Fix Released

Bug description:
  GUI
  ---
  1a. Run sudo gnome-control-center, or...
  1b. Save the gnome-control-center.pkla from 
https://bazaar.launchpad.net/~ubuntu-desktop/gnome-control-center/ubuntu/revision/556
 to /var/lib/polkit-1/localauthority/10-vendor.d/ and then run 
gnome-control-center as an admin user

  2. Enter the Details panel
  3. The "Device name" (hostname) text field should be editable; change the 
text to something else.
  4. The hostname is updated instantly which can be verified by looking in 
/etc/hostname. However /etc/hosts/ is not updated.

  Command line
  
  hostnamectl set-hostname

  The hostnamed documentation at 
http://www.freedesktop.org/wiki/Software/systemd/hostnamed says
  "To properly handle name lookups with changing local hostnames without having 
to edit /etc/hosts for them we recommend using hostnamed in combination with 
nss-myhostname: http://0pointer.de/lennart/projects/nss-myhostname/ "

  Without /etc/hosts being handled correctly, the hostnamed integration
  is only half-working.


  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu18
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Uname: Linux 3.8.0-15-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sun Mar 31 08:52:57 2013
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup26.0-0ubuntu1
   gnome-control-center-signon 0.1.5-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.03.26-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1162475/+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 1838856] [NEW] Cups printer installed but not recognized by application.

[Sean Patrick Sneed]

Public bug reported:

LibreOffice Writer fails with:

 "Could not start printer.  Please check your printer configuration."

and Notepad++ reports:

"Before you can perform printer-related tasks such as page setup or
printing a document, you need to install a printer.  Please install one
and retry."

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: cups 2.2.10-4ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
Uname: Linux 5.0.0-21-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug  3 10:27:58 2019
InstallationDate: Installed on 2019-07-30 (4 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lpstat: device for LBP6230-6240: socket://192.168.1.4
MachineType: Acer Aspire E5-522
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/LBP6230-6240.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/LBP6230-6240.ppd: Permission denied
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=72fc4deb-a416-4cf8-9607-32e97aa728e7 ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/15/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.08
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Nami_CZL
dmi.board.vendor: Acer
dmi.board.version: V1.08
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.08:bd09/15/2015:svnAcer:pnAspireE5-522:pvrV1.08:rvnAcer:rnNami_CZL:rvrV1.08:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: CZL
dmi.product.name: Aspire E5-522
dmi.product.sku: Aspire E5-522_0960_1.08
dmi.product.version: V1.08
dmi.sys.vendor: Acer

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


** Tags: amd64 apparmor apport-bug disco

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

Title:
  Cups printer installed but not recognized by application.

Status in cups package in Ubuntu:
  New

Bug description:
  LibreOffice Writer fails with:

   "Could not start printer.  Please check your printer configuration."

  and Notepad++ reports:

  "Before you can perform printer-related tasks such as page setup or
  printing a document, you need to install a printer.  Please install
  one and retry."

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: cups 2.2.10-4ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  3 10:27:58 2019
  InstallationDate: Installed on 2019-07-30 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat: device for LBP6230-6240: socket://192.168.1.4
  MachineType: Acer Aspire E5-522
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/LBP6230-6240.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/LBP6230-6240.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=72fc4deb-a416-4cf8-9607-32e97aa728e7 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Nami_CZL
  dmi.board.vendor: Acer
  dmi.board.version: V1.08
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.08:bd09/15/2015:svnAcer:pnAspireE5-522:pvrV1.08:rvnAcer:rnNami_CZL:rvrV1.08:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: CZL
  dmi.product.name: Aspire E5-522
  dmi.product.sku: Aspire E5-522_0960_1.08
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1838856/+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 1824753] Re: When I pass the Qt application to the secondary monitor the characters of the application increase

[Patrick]

My knowledge (of language and so on) is very basic, I am using a web 
translator. It is very difficult for me to advertise on the web 
? If someone can or wants to do it I will be very 
grateful.  I can provide as much information as required.
Thank you, greetings.

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

Title:
  When I pass the Qt application to the secondary monitor the characters
  of the application increase

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in vlc package in Ubuntu:
  Invalid

Bug description:
  Hi. I have recently installed Ubuntu 19.04 RC. Everything works fine except 
the Qt applications. I have two monitors and when I pass the Qt application to 
the secondary monitor the characters of the application increase. They happen 
to the traditionally installed Qt applications and to those installed with 
Flatpak and Snap. I leave you a video in which you can see the problem with the 
VLC application.
  https://youtu.be/tEZJONsinU4
  https://i.imgur.com/R7GubxF.png?fb
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-14 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1824753/+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 1824753] Re: When I pass the Qt application to the secondary monitor the characters of the application increase

[Patrick]

I don't know if it's the GNOME 3.30 to 3.32 update or the Qt update. I
know it happens with other distros because I tried Manjaro Gnome and it
also suffers this bug. I left a message in the forums with another video
https://forum.manjaro.org/t/gnome-two-monitors-and-qt-problems/83075

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

Title:
  When I pass the Qt application to the secondary monitor the characters
  of the application increase

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in vlc package in Ubuntu:
  Invalid

Bug description:
  Hi. I have recently installed Ubuntu 19.04 RC. Everything works fine except 
the Qt applications. I have two monitors and when I pass the Qt application to 
the secondary monitor the characters of the application increase. They happen 
to the traditionally installed Qt applications and to those installed with 
Flatpak and Snap. I leave you a video in which you can see the problem with the 
VLC application.
  https://youtu.be/tEZJONsinU4
  https://i.imgur.com/R7GubxF.png?fb
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-14 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1824753/+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 1824753] Re: When I pass the Qt application to the secondary monitor the characters of the application increase

[Patrick]

This bug is with all Qt applications. I used VLC to show it. And by the
way, it happens with other distros that use GNOME 3.32.

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

Title:
  When I pass the Qt application to the secondary monitor the characters
  of the application increase

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in vlc package in Ubuntu:
  Invalid

Bug description:
  Hi. I have recently installed Ubuntu 19.04 RC. Everything works fine except 
the Qt applications. I have two monitors and when I pass the Qt application to 
the secondary monitor the characters of the application increase. They happen 
to the traditionally installed Qt applications and to those installed with 
Flatpak and Snap. I leave you a video in which you can see the problem with the 
VLC application.
  https://youtu.be/tEZJONsinU4
  https://i.imgur.com/R7GubxF.png?fb
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-14 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1824753/+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 1824753] Re: When I pass the Qt application to the secondary monitor the characters of the application increase

[Patrick]

Now I do. Before I just updated mutter_3.32.0-1_amd64.deb.
I have updated all deb and the problem continues.

patrick@patrick-pc:~$   dpkg -l | grep mutter
ii  gir1.2-mutter-4:amd64  3.32.0-1 
amd64GObject introspection data for Mutter
ii  libmutter-4-0:amd643.32.0-1 
amd64window manager library from the Mutter window manager
iU  libmutter-4-dev:amd64  3.32.0-1 
amd64Development files for the Mutter window manager
ii  mutter 3.32.0-1 
amd64lightweight GTK+ window manager
ii  mutter-common  3.32.0-1 
all  shared files for the Mutter window manager
patrick@patrick-pc:~$

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

Title:
  When I pass the Qt application to the secondary monitor the characters
  of the application increase

Status in mutter package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete
Status in vlc package in Ubuntu:
  Incomplete

Bug description:
  Hi. I have recently installed Ubuntu 19.04 RC. Everything works fine except 
the Qt applications. I have two monitors and when I pass the Qt application to 
the secondary monitor the characters of the application increase. They happen 
to the traditionally installed Qt applications and to those installed with 
Flatpak and Snap. I leave you a video in which you can see the problem with the 
VLC application.
  https://youtu.be/tEZJONsinU4
  https://i.imgur.com/R7GubxF.png?fb
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-14 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1824753/+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 1824753] Re: When I pass the Qt application to the secondary monitor the characters of the application increase

[Patrick]

patrick@patrick-pc:~$ dpkg -l | grep mutter
ii  gir1.2-mutter-4:amd64  3.32.0+git20190410-1ubuntu1  
amd64GObject introspection data for Mutter
ii  libmutter-4-0:amd643.32.0+git20190410-1ubuntu1  
amd64window manager library from the Mutter window manager
ii  mutter 3.32.0-1 
amd64lightweight GTK+ window manager
ii  mutter-common  3.32.0+git20190410-1ubuntu1  
all  shared files for the Mutter window manager
patrick@patrick-pc:~$

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

Title:
  When I pass the Qt application to the secondary monitor the characters
  of the application increase

Status in mutter package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete
Status in vlc package in Ubuntu:
  Incomplete

Bug description:
  Hi. I have recently installed Ubuntu 19.04 RC. Everything works fine except 
the Qt applications. I have two monitors and when I pass the Qt application to 
the secondary monitor the characters of the application increase. They happen 
to the traditionally installed Qt applications and to those installed with 
Flatpak and Snap. I leave you a video in which you can see the problem with the 
VLC application.
  https://youtu.be/tEZJONsinU4
  https://i.imgur.com/R7GubxF.png?fb
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-14 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1824753/+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 1698693] Re: cups-pdf blocked by apparmor

[Patrick Hibbs]

Ooops. Ignore the previous post. Those were the wrong instructions.
These are the correct ones:


1. Install fresh copy of Ubuntu.

2. Install printer-driver-cups-pdf.

3. Change cups-pdf's output directory in /etc/cups/cups-pdf.conf to some
directory outside of the user's home directory, and that the user has
write access to that directory's parent.

4. Make sure the directory defined in step 3 does not exist.

5. Attempt to print using CUPS PDF.

6. Notice the DENIED error in dmesg, and the directory defined in step 3
still does not exist.

6. Notice that cups-pdf lacks an apparmor profile of it's own and is
stored alongside the cupsd profile in /etc/apparmor.d

7. Notice that unlike cupsd, cups-pdf's profile does not have an include
statement for local profile modifications in /etc/apparmor.d/local

8. Attempt to change the default profile for cups-pdf anyway, reload the
new default profile, and try to print again.

9. Find your pdf in the directory defined in step 3.

10. Wait until the cups package is updated again. (Accept the maintainer
version of /etc/apparmor.d/usr.sbin.cupsd when asked.)

11. Notice your changes to the default profile have been wiped out by
the update, and you can no longer print using CUPS PDF if the directory
defined in step 3 is moved or deleted.

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

Title:
  cups-pdf blocked by apparmor

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  cups-pdf cannot create the ~/PDF directory if it does not exist and
  fails with no indication to the user.

  It should however be pointed out that cups-pdf allows the system
  administrator to change it's output directory by changing the Out key
  in /etc/cups/cups-pdf.conf. As such apparmor will get in the way again
  if the admin changes the Out key to some other location outside of the
  ${HOME}/PDF directory. (It's default setting.)

  cups-pdf also does not have an #include for using local overrides in
  it's apparmor config. As such any fixes that the local admin makes
  will be overwritten by the next update to the cups package, breaking
  it again.

  
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  printer-driver-cups-pdf:
Installed: 2.6.1-21
Candidate: 2.6.1-21
Version table:
   *** 2.6.1-21 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  cups:
Installed: 2.1.3-4
Candidate: 2.1.3-4
Version table:
   *** 2.1.3-4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  What happened:
  cups-pdf when installed for the first time fails with the following apparmor 
denials:

  [ 6117.686934] audit: type=1400 audit(1497816878.998:1079): apparmor="DENIED" 
operation="file_inherit" profile="/usr/lib/cups/backend/cups-pdf" pid=6015 
comm="cups-pdf" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive" denied_mask="send receive" addr=none 
peer_addr=none peer="/usr/sbin/cupsd"
  [ 6117.686948] audit: type=1400 audit(1497816878.998:1080): apparmor="DENIED" 
operation="file_inherit" profile="/usr/sbin/cupsd" pid=6015 comm="cups-pdf" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none 
peer="/usr/lib/cups/backend/cups-pdf"
  [ 6117.688671] audit: type=1400 audit(1497816879.002:1081): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.688688] audit: type=1400 audit(1497816879.002:1082): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.689719] audit: type=1400 audit(1497816879.002:1083): apparmor="DENIED" 
operation="mkdir" profile="/usr/lib/cups/backend/cups-pdf" 
name="/home/CODENET.LOCAL/codebase/PDF/" pid=6015 comm="cups-pdf" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0

  
  What I expected to happen:
  cups-pdf creates the pdf file it was supposed to.

  
  As a workaround, I set cups-pdf to use the third-party settings from the cups 
profile, then it worked as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-24 (281 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  Lpstat:
   device for EPSONET-4550: 
ipp://call.codenet.local:631/printers/EPSON_ET-4550_Series
   device for PDF: cups-pdf:/
  MachineType: Gigabyte Technology Co., Ltd. 

[Touch-packages] [Bug 1698693] Re: cups-pdf blocked by apparmor

[Patrick Hibbs]

1. Install fresh copy of Ubuntu.

2. Make sure ~/PDF does not exist.

3. Install printer-driver-cups-pdf.

4. Attempt to print using CUPS PDF.

5. Notice the DENIED error in dmesg, and the lack of a ~/PDF directory.

6. Notice that cups-pdf lacks an apparmor profile of it's own and is
stored alongside the cupsd profile in /etc/apparmor.d

7. Notice that unlike cupsd, cups-pdf's profile does not have an include
statement for local profile modifications in /etc/apparmor.d/local

8. Attempt to change the default profile for cups-pdf anyway, reload the
new default profile, and try to print again.

9. Find your pdf in ~/PDF.

10. Wait until the cups package is updated again. (Accept the maintainer
version of /etc/apparmor.d/usr.sbin.cupsd when asked.)

11. Notice your changes to the default profile have been wiped out by
the update, and you can no longer print using CUPS PDF if ~/PDF is moved
/ or deleted.

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

Title:
  cups-pdf blocked by apparmor

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  cups-pdf cannot create the ~/PDF directory if it does not exist and
  fails with no indication to the user.

  It should however be pointed out that cups-pdf allows the system
  administrator to change it's output directory by changing the Out key
  in /etc/cups/cups-pdf.conf. As such apparmor will get in the way again
  if the admin changes the Out key to some other location outside of the
  ${HOME}/PDF directory. (It's default setting.)

  cups-pdf also does not have an #include for using local overrides in
  it's apparmor config. As such any fixes that the local admin makes
  will be overwritten by the next update to the cups package, breaking
  it again.

  
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  printer-driver-cups-pdf:
Installed: 2.6.1-21
Candidate: 2.6.1-21
Version table:
   *** 2.6.1-21 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  cups:
Installed: 2.1.3-4
Candidate: 2.1.3-4
Version table:
   *** 2.1.3-4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  What happened:
  cups-pdf when installed for the first time fails with the following apparmor 
denials:

  [ 6117.686934] audit: type=1400 audit(1497816878.998:1079): apparmor="DENIED" 
operation="file_inherit" profile="/usr/lib/cups/backend/cups-pdf" pid=6015 
comm="cups-pdf" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive" denied_mask="send receive" addr=none 
peer_addr=none peer="/usr/sbin/cupsd"
  [ 6117.686948] audit: type=1400 audit(1497816878.998:1080): apparmor="DENIED" 
operation="file_inherit" profile="/usr/sbin/cupsd" pid=6015 comm="cups-pdf" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none 
peer="/usr/lib/cups/backend/cups-pdf"
  [ 6117.688671] audit: type=1400 audit(1497816879.002:1081): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.688688] audit: type=1400 audit(1497816879.002:1082): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.689719] audit: type=1400 audit(1497816879.002:1083): apparmor="DENIED" 
operation="mkdir" profile="/usr/lib/cups/backend/cups-pdf" 
name="/home/CODENET.LOCAL/codebase/PDF/" pid=6015 comm="cups-pdf" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0

  
  What I expected to happen:
  cups-pdf creates the pdf file it was supposed to.

  
  As a workaround, I set cups-pdf to use the third-party settings from the cups 
profile, then it worked as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-24 (281 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  Lpstat:
   device for EPSONET-4550: 
ipp://call.codenet.local:631/printers/EPSON_ET-4550_Series
   device for PDF: cups-pdf:/
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 

[Touch-packages] [Bug 1698693] Re: cups-pdf blocked by apparmor

[Patrick Hibbs]

https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1675503 <- That has
nothing to do with this bug.

https://bugs.launchpad.net/ubuntu/+source/cups-pdf/+bug/1166786 <- Sort
of, that describes the issue and admits the issue's existance, but does
not actually fix it.

What I mean by that is the apparmor profile for cups-pdf does not allow
local modifications by default. Bug #1166786 says you need to make
modifications to workaround the issue, but even if you do, your changes
will be wiped out when the cups-daemon package gets updated.

I attached a patch for the cups-pdf apparmor profile to allow local
modifications, but it will get wiped out too unless it gets integrated
into the cups-daemon package.

Sidenote: Why is the apparmor profile for cups-pdf in cups-daemon? The
pdf backend is in a separate package: printer-driver-cups-pdf.

** Patch added: "Allows site-specific overrides for the cups-pdf profile."
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1698693/+attachment/5186550/+files/local_override_cups-pdf.patch

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

Title:
  cups-pdf blocked by apparmor

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  cups-pdf cannot create the ~/PDF directory if it does not exist and
  fails with no indication to the user.

  It should however be pointed out that cups-pdf allows the system
  administrator to change it's output directory by changing the Out key
  in /etc/cups/cups-pdf.conf. As such apparmor will get in the way again
  if the admin changes the Out key to some other location outside of the
  ${HOME}/PDF directory. (It's default setting.)

  cups-pdf also does not have an #include for using local overrides in
  it's apparmor config. As such any fixes that the local admin makes
  will be overwritten by the next update to the cups package, breaking
  it again.

  
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  printer-driver-cups-pdf:
Installed: 2.6.1-21
Candidate: 2.6.1-21
Version table:
   *** 2.6.1-21 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  cups:
Installed: 2.1.3-4
Candidate: 2.1.3-4
Version table:
   *** 2.1.3-4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  What happened:
  cups-pdf when installed for the first time fails with the following apparmor 
denials:

  [ 6117.686934] audit: type=1400 audit(1497816878.998:1079): apparmor="DENIED" 
operation="file_inherit" profile="/usr/lib/cups/backend/cups-pdf" pid=6015 
comm="cups-pdf" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive" denied_mask="send receive" addr=none 
peer_addr=none peer="/usr/sbin/cupsd"
  [ 6117.686948] audit: type=1400 audit(1497816878.998:1080): apparmor="DENIED" 
operation="file_inherit" profile="/usr/sbin/cupsd" pid=6015 comm="cups-pdf" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none 
peer="/usr/lib/cups/backend/cups-pdf"
  [ 6117.688671] audit: type=1400 audit(1497816879.002:1081): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.688688] audit: type=1400 audit(1497816879.002:1082): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.689719] audit: type=1400 audit(1497816879.002:1083): apparmor="DENIED" 
operation="mkdir" profile="/usr/lib/cups/backend/cups-pdf" 
name="/home/CODENET.LOCAL/codebase/PDF/" pid=6015 comm="cups-pdf" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0

  
  What I expected to happen:
  cups-pdf creates the pdf file it was supposed to.

  
  As a workaround, I set cups-pdf to use the third-party settings from the cups 
profile, then it worked as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-24 (281 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  Lpstat:
   device for EPSONET-4550: 
ipp://call.codenet.local:631/printers/EPSON_ET-4550_Series
   device for PDF: cups-pdf:/
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: 

[Touch-packages] [Bug 1698693] Re: cups-pdf blocked by apparmor

[Patrick Hibbs]

I'm using Bionic. (18.04.1 LTS) x64

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

Title:
  cups-pdf blocked by apparmor

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  cups-pdf cannot create the ~/PDF directory if it does not exist and
  fails with no indication to the user.

  It should however be pointed out that cups-pdf allows the system
  administrator to change it's output directory by changing the Out key
  in /etc/cups/cups-pdf.conf. As such apparmor will get in the way again
  if the admin changes the Out key to some other location outside of the
  ${HOME}/PDF directory. (It's default setting.)

  cups-pdf also does not have an #include for using local overrides in
  it's apparmor config. As such any fixes that the local admin makes
  will be overwritten by the next update to the cups package, breaking
  it again.

  
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  printer-driver-cups-pdf:
Installed: 2.6.1-21
Candidate: 2.6.1-21
Version table:
   *** 2.6.1-21 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  cups:
Installed: 2.1.3-4
Candidate: 2.1.3-4
Version table:
   *** 2.1.3-4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  What happened:
  cups-pdf when installed for the first time fails with the following apparmor 
denials:

  [ 6117.686934] audit: type=1400 audit(1497816878.998:1079): apparmor="DENIED" 
operation="file_inherit" profile="/usr/lib/cups/backend/cups-pdf" pid=6015 
comm="cups-pdf" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive" denied_mask="send receive" addr=none 
peer_addr=none peer="/usr/sbin/cupsd"
  [ 6117.686948] audit: type=1400 audit(1497816878.998:1080): apparmor="DENIED" 
operation="file_inherit" profile="/usr/sbin/cupsd" pid=6015 comm="cups-pdf" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none 
peer="/usr/lib/cups/backend/cups-pdf"
  [ 6117.688671] audit: type=1400 audit(1497816879.002:1081): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.688688] audit: type=1400 audit(1497816879.002:1082): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.689719] audit: type=1400 audit(1497816879.002:1083): apparmor="DENIED" 
operation="mkdir" profile="/usr/lib/cups/backend/cups-pdf" 
name="/home/CODENET.LOCAL/codebase/PDF/" pid=6015 comm="cups-pdf" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0

  
  What I expected to happen:
  cups-pdf creates the pdf file it was supposed to.

  
  As a workaround, I set cups-pdf to use the third-party settings from the cups 
profile, then it worked as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-24 (281 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  Lpstat:
   device for EPSONET-4550: 
ipp://call.codenet.local:631/printers/EPSON_ET-4550_Series
   device for PDF: cups-pdf:/
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic apparmor apparmor apparmor apparmor
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-20 (104 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F21
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Touch-packages] [Bug 1698693] Re: cups-pdf blocked by apparmor

[Patrick Hibbs]

Hmm... Access Denied, should I resubmit using a different login?

Also the lack of an include directive for /usr/lib/cups/backend/cups-pdf
in /etc/apparmor.d/usr.sbin.cupsd to allow using a different path for
pdf output is still an issue.

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

Title:
  cups-pdf blocked by apparmor

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  cups-pdf cannot create the ~/PDF directory if it does not exist and
  fails with no indication to the user.

  It should however be pointed out that cups-pdf allows the system
  administrator to change it's output directory by changing the Out key
  in /etc/cups/cups-pdf.conf. As such apparmor will get in the way again
  if the admin changes the Out key to some other location outside of the
  ${HOME}/PDF directory. (It's default setting.)

  cups-pdf also does not have an #include for using local overrides in
  it's apparmor config. As such any fixes that the local admin makes
  will be overwritten by the next update to the cups package, breaking
  it again.

  
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  printer-driver-cups-pdf:
Installed: 2.6.1-21
Candidate: 2.6.1-21
Version table:
   *** 2.6.1-21 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  cups:
Installed: 2.1.3-4
Candidate: 2.1.3-4
Version table:
   *** 2.1.3-4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  What happened:
  cups-pdf when installed for the first time fails with the following apparmor 
denials:

  [ 6117.686934] audit: type=1400 audit(1497816878.998:1079): apparmor="DENIED" 
operation="file_inherit" profile="/usr/lib/cups/backend/cups-pdf" pid=6015 
comm="cups-pdf" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive" denied_mask="send receive" addr=none 
peer_addr=none peer="/usr/sbin/cupsd"
  [ 6117.686948] audit: type=1400 audit(1497816878.998:1080): apparmor="DENIED" 
operation="file_inherit" profile="/usr/sbin/cupsd" pid=6015 comm="cups-pdf" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none 
peer="/usr/lib/cups/backend/cups-pdf"
  [ 6117.688671] audit: type=1400 audit(1497816879.002:1081): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.688688] audit: type=1400 audit(1497816879.002:1082): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.689719] audit: type=1400 audit(1497816879.002:1083): apparmor="DENIED" 
operation="mkdir" profile="/usr/lib/cups/backend/cups-pdf" 
name="/home/CODENET.LOCAL/codebase/PDF/" pid=6015 comm="cups-pdf" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0

  
  What I expected to happen:
  cups-pdf creates the pdf file it was supposed to.

  
  As a workaround, I set cups-pdf to use the third-party settings from the cups 
profile, then it worked as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-24 (281 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  Lpstat:
   device for EPSONET-4550: 
ipp://call.codenet.local:631/printers/EPSON_ET-4550_Series
   device for PDF: cups-pdf:/
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic apparmor apparmor apparmor apparmor
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-20 (104 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F21
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., 

[Touch-packages] [Bug 1698693] KernLog.txt

[Patrick Hibbs]

apport information

** Attachment added: "KernLog.txt"
   
https://bugs.launchpad.net/bugs/1698693/+attachment/5183606/+files/KernLog.txt

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

Title:
  cups-pdf blocked by apparmor

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  cups-pdf cannot create the ~/PDF directory if it does not exist and
  fails with no indication to the user.

  It should however be pointed out that cups-pdf allows the system
  administrator to change it's output directory by changing the Out key
  in /etc/cups/cups-pdf.conf. As such apparmor will get in the way again
  if the admin changes the Out key to some other location outside of the
  ${HOME}/PDF directory. (It's default setting.)

  cups-pdf also does not have an #include for using local overrides in
  it's apparmor config. As such any fixes that the local admin makes
  will be overwritten by the next update to the cups package, breaking
  it again.

  
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  printer-driver-cups-pdf:
Installed: 2.6.1-21
Candidate: 2.6.1-21
Version table:
   *** 2.6.1-21 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  cups:
Installed: 2.1.3-4
Candidate: 2.1.3-4
Version table:
   *** 2.1.3-4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  What happened:
  cups-pdf when installed for the first time fails with the following apparmor 
denials:

  [ 6117.686934] audit: type=1400 audit(1497816878.998:1079): apparmor="DENIED" 
operation="file_inherit" profile="/usr/lib/cups/backend/cups-pdf" pid=6015 
comm="cups-pdf" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive" denied_mask="send receive" addr=none 
peer_addr=none peer="/usr/sbin/cupsd"
  [ 6117.686948] audit: type=1400 audit(1497816878.998:1080): apparmor="DENIED" 
operation="file_inherit" profile="/usr/sbin/cupsd" pid=6015 comm="cups-pdf" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none 
peer="/usr/lib/cups/backend/cups-pdf"
  [ 6117.688671] audit: type=1400 audit(1497816879.002:1081): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.688688] audit: type=1400 audit(1497816879.002:1082): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.689719] audit: type=1400 audit(1497816879.002:1083): apparmor="DENIED" 
operation="mkdir" profile="/usr/lib/cups/backend/cups-pdf" 
name="/home/CODENET.LOCAL/codebase/PDF/" pid=6015 comm="cups-pdf" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0

  
  What I expected to happen:
  cups-pdf creates the pdf file it was supposed to.

  
  As a workaround, I set cups-pdf to use the third-party settings from the cups 
profile, then it worked as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-24 (281 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  Lpstat:
   device for EPSONET-4550: 
ipp://call.codenet.local:631/printers/EPSON_ET-4550_Series
   device for PDF: cups-pdf:/
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic apparmor apparmor apparmor apparmor
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-20 (104 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F21
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  

[Touch-packages] [Bug 1698693] ProcModules.txt

[Patrick Hibbs]

apport information

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

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

Title:
  cups-pdf blocked by apparmor

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  cups-pdf cannot create the ~/PDF directory if it does not exist and
  fails with no indication to the user.

  It should however be pointed out that cups-pdf allows the system
  administrator to change it's output directory by changing the Out key
  in /etc/cups/cups-pdf.conf. As such apparmor will get in the way again
  if the admin changes the Out key to some other location outside of the
  ${HOME}/PDF directory. (It's default setting.)

  cups-pdf also does not have an #include for using local overrides in
  it's apparmor config. As such any fixes that the local admin makes
  will be overwritten by the next update to the cups package, breaking
  it again.

  
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  printer-driver-cups-pdf:
Installed: 2.6.1-21
Candidate: 2.6.1-21
Version table:
   *** 2.6.1-21 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  cups:
Installed: 2.1.3-4
Candidate: 2.1.3-4
Version table:
   *** 2.1.3-4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  What happened:
  cups-pdf when installed for the first time fails with the following apparmor 
denials:

  [ 6117.686934] audit: type=1400 audit(1497816878.998:1079): apparmor="DENIED" 
operation="file_inherit" profile="/usr/lib/cups/backend/cups-pdf" pid=6015 
comm="cups-pdf" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive" denied_mask="send receive" addr=none 
peer_addr=none peer="/usr/sbin/cupsd"
  [ 6117.686948] audit: type=1400 audit(1497816878.998:1080): apparmor="DENIED" 
operation="file_inherit" profile="/usr/sbin/cupsd" pid=6015 comm="cups-pdf" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none 
peer="/usr/lib/cups/backend/cups-pdf"
  [ 6117.688671] audit: type=1400 audit(1497816879.002:1081): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.688688] audit: type=1400 audit(1497816879.002:1082): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.689719] audit: type=1400 audit(1497816879.002:1083): apparmor="DENIED" 
operation="mkdir" profile="/usr/lib/cups/backend/cups-pdf" 
name="/home/CODENET.LOCAL/codebase/PDF/" pid=6015 comm="cups-pdf" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0

  
  What I expected to happen:
  cups-pdf creates the pdf file it was supposed to.

  
  As a workaround, I set cups-pdf to use the third-party settings from the cups 
profile, then it worked as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-24 (281 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  Lpstat:
   device for EPSONET-4550: 
ipp://call.codenet.local:631/printers/EPSON_ET-4550_Series
   device for PDF: cups-pdf:/
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic apparmor apparmor apparmor apparmor
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-20 (104 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F21
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
 

[Touch-packages] [Bug 1698693] ProcCpuinfo.txt

[Patrick Hibbs]

apport information

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

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

Title:
  cups-pdf blocked by apparmor

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  cups-pdf cannot create the ~/PDF directory if it does not exist and
  fails with no indication to the user.

  It should however be pointed out that cups-pdf allows the system
  administrator to change it's output directory by changing the Out key
  in /etc/cups/cups-pdf.conf. As such apparmor will get in the way again
  if the admin changes the Out key to some other location outside of the
  ${HOME}/PDF directory. (It's default setting.)

  cups-pdf also does not have an #include for using local overrides in
  it's apparmor config. As such any fixes that the local admin makes
  will be overwritten by the next update to the cups package, breaking
  it again.

  
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  printer-driver-cups-pdf:
Installed: 2.6.1-21
Candidate: 2.6.1-21
Version table:
   *** 2.6.1-21 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  cups:
Installed: 2.1.3-4
Candidate: 2.1.3-4
Version table:
   *** 2.1.3-4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  What happened:
  cups-pdf when installed for the first time fails with the following apparmor 
denials:

  [ 6117.686934] audit: type=1400 audit(1497816878.998:1079): apparmor="DENIED" 
operation="file_inherit" profile="/usr/lib/cups/backend/cups-pdf" pid=6015 
comm="cups-pdf" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive" denied_mask="send receive" addr=none 
peer_addr=none peer="/usr/sbin/cupsd"
  [ 6117.686948] audit: type=1400 audit(1497816878.998:1080): apparmor="DENIED" 
operation="file_inherit" profile="/usr/sbin/cupsd" pid=6015 comm="cups-pdf" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none 
peer="/usr/lib/cups/backend/cups-pdf"
  [ 6117.688671] audit: type=1400 audit(1497816879.002:1081): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.688688] audit: type=1400 audit(1497816879.002:1082): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.689719] audit: type=1400 audit(1497816879.002:1083): apparmor="DENIED" 
operation="mkdir" profile="/usr/lib/cups/backend/cups-pdf" 
name="/home/CODENET.LOCAL/codebase/PDF/" pid=6015 comm="cups-pdf" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0

  
  What I expected to happen:
  cups-pdf creates the pdf file it was supposed to.

  
  As a workaround, I set cups-pdf to use the third-party settings from the cups 
profile, then it worked as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-24 (281 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  Lpstat:
   device for EPSONET-4550: 
ipp://call.codenet.local:631/printers/EPSON_ET-4550_Series
   device for PDF: cups-pdf:/
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic apparmor apparmor apparmor apparmor
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-20 (104 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F21
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
 

[Touch-packages] [Bug 1698693] ProcEnviron.txt

[Patrick Hibbs]

apport information

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

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

Title:
  cups-pdf blocked by apparmor

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  cups-pdf cannot create the ~/PDF directory if it does not exist and
  fails with no indication to the user.

  It should however be pointed out that cups-pdf allows the system
  administrator to change it's output directory by changing the Out key
  in /etc/cups/cups-pdf.conf. As such apparmor will get in the way again
  if the admin changes the Out key to some other location outside of the
  ${HOME}/PDF directory. (It's default setting.)

  cups-pdf also does not have an #include for using local overrides in
  it's apparmor config. As such any fixes that the local admin makes
  will be overwritten by the next update to the cups package, breaking
  it again.

  
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  printer-driver-cups-pdf:
Installed: 2.6.1-21
Candidate: 2.6.1-21
Version table:
   *** 2.6.1-21 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  cups:
Installed: 2.1.3-4
Candidate: 2.1.3-4
Version table:
   *** 2.1.3-4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  What happened:
  cups-pdf when installed for the first time fails with the following apparmor 
denials:

  [ 6117.686934] audit: type=1400 audit(1497816878.998:1079): apparmor="DENIED" 
operation="file_inherit" profile="/usr/lib/cups/backend/cups-pdf" pid=6015 
comm="cups-pdf" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive" denied_mask="send receive" addr=none 
peer_addr=none peer="/usr/sbin/cupsd"
  [ 6117.686948] audit: type=1400 audit(1497816878.998:1080): apparmor="DENIED" 
operation="file_inherit" profile="/usr/sbin/cupsd" pid=6015 comm="cups-pdf" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none 
peer="/usr/lib/cups/backend/cups-pdf"
  [ 6117.688671] audit: type=1400 audit(1497816879.002:1081): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.688688] audit: type=1400 audit(1497816879.002:1082): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.689719] audit: type=1400 audit(1497816879.002:1083): apparmor="DENIED" 
operation="mkdir" profile="/usr/lib/cups/backend/cups-pdf" 
name="/home/CODENET.LOCAL/codebase/PDF/" pid=6015 comm="cups-pdf" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0

  
  What I expected to happen:
  cups-pdf creates the pdf file it was supposed to.

  
  As a workaround, I set cups-pdf to use the third-party settings from the cups 
profile, then it worked as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-24 (281 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  Lpstat:
   device for EPSONET-4550: 
ipp://call.codenet.local:631/printers/EPSON_ET-4550_Series
   device for PDF: cups-pdf:/
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic apparmor apparmor apparmor apparmor
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-20 (104 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F21
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
 

[Touch-packages] [Bug 1698693] UdevDb.txt

[Patrick Hibbs]

apport information

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

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

Title:
  cups-pdf blocked by apparmor

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  cups-pdf cannot create the ~/PDF directory if it does not exist and
  fails with no indication to the user.

  It should however be pointed out that cups-pdf allows the system
  administrator to change it's output directory by changing the Out key
  in /etc/cups/cups-pdf.conf. As such apparmor will get in the way again
  if the admin changes the Out key to some other location outside of the
  ${HOME}/PDF directory. (It's default setting.)

  cups-pdf also does not have an #include for using local overrides in
  it's apparmor config. As such any fixes that the local admin makes
  will be overwritten by the next update to the cups package, breaking
  it again.

  
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  printer-driver-cups-pdf:
Installed: 2.6.1-21
Candidate: 2.6.1-21
Version table:
   *** 2.6.1-21 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  cups:
Installed: 2.1.3-4
Candidate: 2.1.3-4
Version table:
   *** 2.1.3-4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  What happened:
  cups-pdf when installed for the first time fails with the following apparmor 
denials:

  [ 6117.686934] audit: type=1400 audit(1497816878.998:1079): apparmor="DENIED" 
operation="file_inherit" profile="/usr/lib/cups/backend/cups-pdf" pid=6015 
comm="cups-pdf" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive" denied_mask="send receive" addr=none 
peer_addr=none peer="/usr/sbin/cupsd"
  [ 6117.686948] audit: type=1400 audit(1497816878.998:1080): apparmor="DENIED" 
operation="file_inherit" profile="/usr/sbin/cupsd" pid=6015 comm="cups-pdf" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none 
peer="/usr/lib/cups/backend/cups-pdf"
  [ 6117.688671] audit: type=1400 audit(1497816879.002:1081): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.688688] audit: type=1400 audit(1497816879.002:1082): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.689719] audit: type=1400 audit(1497816879.002:1083): apparmor="DENIED" 
operation="mkdir" profile="/usr/lib/cups/backend/cups-pdf" 
name="/home/CODENET.LOCAL/codebase/PDF/" pid=6015 comm="cups-pdf" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0

  
  What I expected to happen:
  cups-pdf creates the pdf file it was supposed to.

  
  As a workaround, I set cups-pdf to use the third-party settings from the cups 
profile, then it worked as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-24 (281 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  Lpstat:
   device for EPSONET-4550: 
ipp://call.codenet.local:631/printers/EPSON_ET-4550_Series
   device for PDF: cups-pdf:/
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic apparmor apparmor apparmor apparmor
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-20 (104 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F21
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  

[Touch-packages] [Bug 1698693] ProcInterrupts.txt

[Patrick Hibbs]

apport information

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

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

Title:
  cups-pdf blocked by apparmor

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  cups-pdf cannot create the ~/PDF directory if it does not exist and
  fails with no indication to the user.

  It should however be pointed out that cups-pdf allows the system
  administrator to change it's output directory by changing the Out key
  in /etc/cups/cups-pdf.conf. As such apparmor will get in the way again
  if the admin changes the Out key to some other location outside of the
  ${HOME}/PDF directory. (It's default setting.)

  cups-pdf also does not have an #include for using local overrides in
  it's apparmor config. As such any fixes that the local admin makes
  will be overwritten by the next update to the cups package, breaking
  it again.

  
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  printer-driver-cups-pdf:
Installed: 2.6.1-21
Candidate: 2.6.1-21
Version table:
   *** 2.6.1-21 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  cups:
Installed: 2.1.3-4
Candidate: 2.1.3-4
Version table:
   *** 2.1.3-4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  What happened:
  cups-pdf when installed for the first time fails with the following apparmor 
denials:

  [ 6117.686934] audit: type=1400 audit(1497816878.998:1079): apparmor="DENIED" 
operation="file_inherit" profile="/usr/lib/cups/backend/cups-pdf" pid=6015 
comm="cups-pdf" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive" denied_mask="send receive" addr=none 
peer_addr=none peer="/usr/sbin/cupsd"
  [ 6117.686948] audit: type=1400 audit(1497816878.998:1080): apparmor="DENIED" 
operation="file_inherit" profile="/usr/sbin/cupsd" pid=6015 comm="cups-pdf" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none 
peer="/usr/lib/cups/backend/cups-pdf"
  [ 6117.688671] audit: type=1400 audit(1497816879.002:1081): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.688688] audit: type=1400 audit(1497816879.002:1082): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.689719] audit: type=1400 audit(1497816879.002:1083): apparmor="DENIED" 
operation="mkdir" profile="/usr/lib/cups/backend/cups-pdf" 
name="/home/CODENET.LOCAL/codebase/PDF/" pid=6015 comm="cups-pdf" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0

  
  What I expected to happen:
  cups-pdf creates the pdf file it was supposed to.

  
  As a workaround, I set cups-pdf to use the third-party settings from the cups 
profile, then it worked as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-24 (281 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  Lpstat:
   device for EPSONET-4550: 
ipp://call.codenet.local:631/printers/EPSON_ET-4550_Series
   device for PDF: cups-pdf:/
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic apparmor apparmor apparmor apparmor
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-20 (104 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F21
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  

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

[Patrick Hibbs]

apport information

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

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

Title:
  cups-pdf blocked by apparmor

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  cups-pdf cannot create the ~/PDF directory if it does not exist and
  fails with no indication to the user.

  It should however be pointed out that cups-pdf allows the system
  administrator to change it's output directory by changing the Out key
  in /etc/cups/cups-pdf.conf. As such apparmor will get in the way again
  if the admin changes the Out key to some other location outside of the
  ${HOME}/PDF directory. (It's default setting.)

  cups-pdf also does not have an #include for using local overrides in
  it's apparmor config. As such any fixes that the local admin makes
  will be overwritten by the next update to the cups package, breaking
  it again.

  
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  printer-driver-cups-pdf:
Installed: 2.6.1-21
Candidate: 2.6.1-21
Version table:
   *** 2.6.1-21 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  cups:
Installed: 2.1.3-4
Candidate: 2.1.3-4
Version table:
   *** 2.1.3-4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  What happened:
  cups-pdf when installed for the first time fails with the following apparmor 
denials:

  [ 6117.686934] audit: type=1400 audit(1497816878.998:1079): apparmor="DENIED" 
operation="file_inherit" profile="/usr/lib/cups/backend/cups-pdf" pid=6015 
comm="cups-pdf" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive" denied_mask="send receive" addr=none 
peer_addr=none peer="/usr/sbin/cupsd"
  [ 6117.686948] audit: type=1400 audit(1497816878.998:1080): apparmor="DENIED" 
operation="file_inherit" profile="/usr/sbin/cupsd" pid=6015 comm="cups-pdf" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none 
peer="/usr/lib/cups/backend/cups-pdf"
  [ 6117.688671] audit: type=1400 audit(1497816879.002:1081): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.688688] audit: type=1400 audit(1497816879.002:1082): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.689719] audit: type=1400 audit(1497816879.002:1083): apparmor="DENIED" 
operation="mkdir" profile="/usr/lib/cups/backend/cups-pdf" 
name="/home/CODENET.LOCAL/codebase/PDF/" pid=6015 comm="cups-pdf" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0

  
  What I expected to happen:
  cups-pdf creates the pdf file it was supposed to.

  
  As a workaround, I set cups-pdf to use the third-party settings from the cups 
profile, then it worked as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-24 (281 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  Lpstat:
   device for EPSONET-4550: 
ipp://call.codenet.local:631/printers/EPSON_ET-4550_Series
   device for PDF: cups-pdf:/
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic apparmor apparmor apparmor apparmor
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-20 (104 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F21
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  

[Touch-packages] [Bug 1698693] PrintingPackages.txt

[Patrick Hibbs]

apport information

** Attachment added: "PrintingPackages.txt"
   
https://bugs.launchpad.net/bugs/1698693/+attachment/5183610/+files/PrintingPackages.txt

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

Title:
  cups-pdf blocked by apparmor

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  cups-pdf cannot create the ~/PDF directory if it does not exist and
  fails with no indication to the user.

  It should however be pointed out that cups-pdf allows the system
  administrator to change it's output directory by changing the Out key
  in /etc/cups/cups-pdf.conf. As such apparmor will get in the way again
  if the admin changes the Out key to some other location outside of the
  ${HOME}/PDF directory. (It's default setting.)

  cups-pdf also does not have an #include for using local overrides in
  it's apparmor config. As such any fixes that the local admin makes
  will be overwritten by the next update to the cups package, breaking
  it again.

  
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  printer-driver-cups-pdf:
Installed: 2.6.1-21
Candidate: 2.6.1-21
Version table:
   *** 2.6.1-21 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  cups:
Installed: 2.1.3-4
Candidate: 2.1.3-4
Version table:
   *** 2.1.3-4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  What happened:
  cups-pdf when installed for the first time fails with the following apparmor 
denials:

  [ 6117.686934] audit: type=1400 audit(1497816878.998:1079): apparmor="DENIED" 
operation="file_inherit" profile="/usr/lib/cups/backend/cups-pdf" pid=6015 
comm="cups-pdf" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive" denied_mask="send receive" addr=none 
peer_addr=none peer="/usr/sbin/cupsd"
  [ 6117.686948] audit: type=1400 audit(1497816878.998:1080): apparmor="DENIED" 
operation="file_inherit" profile="/usr/sbin/cupsd" pid=6015 comm="cups-pdf" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none 
peer="/usr/lib/cups/backend/cups-pdf"
  [ 6117.688671] audit: type=1400 audit(1497816879.002:1081): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.688688] audit: type=1400 audit(1497816879.002:1082): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.689719] audit: type=1400 audit(1497816879.002:1083): apparmor="DENIED" 
operation="mkdir" profile="/usr/lib/cups/backend/cups-pdf" 
name="/home/CODENET.LOCAL/codebase/PDF/" pid=6015 comm="cups-pdf" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0

  
  What I expected to happen:
  cups-pdf creates the pdf file it was supposed to.

  
  As a workaround, I set cups-pdf to use the third-party settings from the cups 
profile, then it worked as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-24 (281 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  Lpstat:
   device for EPSONET-4550: 
ipp://call.codenet.local:631/printers/EPSON_ET-4550_Series
   device for PDF: cups-pdf:/
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic apparmor apparmor apparmor apparmor
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-20 (104 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F21
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  

[Touch-packages] [Bug 1698693] Lsusb.txt

[Patrick Hibbs]

apport information

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

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

Title:
  cups-pdf blocked by apparmor

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  cups-pdf cannot create the ~/PDF directory if it does not exist and
  fails with no indication to the user.

  It should however be pointed out that cups-pdf allows the system
  administrator to change it's output directory by changing the Out key
  in /etc/cups/cups-pdf.conf. As such apparmor will get in the way again
  if the admin changes the Out key to some other location outside of the
  ${HOME}/PDF directory. (It's default setting.)

  cups-pdf also does not have an #include for using local overrides in
  it's apparmor config. As such any fixes that the local admin makes
  will be overwritten by the next update to the cups package, breaking
  it again.

  
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  printer-driver-cups-pdf:
Installed: 2.6.1-21
Candidate: 2.6.1-21
Version table:
   *** 2.6.1-21 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  cups:
Installed: 2.1.3-4
Candidate: 2.1.3-4
Version table:
   *** 2.1.3-4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  What happened:
  cups-pdf when installed for the first time fails with the following apparmor 
denials:

  [ 6117.686934] audit: type=1400 audit(1497816878.998:1079): apparmor="DENIED" 
operation="file_inherit" profile="/usr/lib/cups/backend/cups-pdf" pid=6015 
comm="cups-pdf" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive" denied_mask="send receive" addr=none 
peer_addr=none peer="/usr/sbin/cupsd"
  [ 6117.686948] audit: type=1400 audit(1497816878.998:1080): apparmor="DENIED" 
operation="file_inherit" profile="/usr/sbin/cupsd" pid=6015 comm="cups-pdf" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none 
peer="/usr/lib/cups/backend/cups-pdf"
  [ 6117.688671] audit: type=1400 audit(1497816879.002:1081): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.688688] audit: type=1400 audit(1497816879.002:1082): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.689719] audit: type=1400 audit(1497816879.002:1083): apparmor="DENIED" 
operation="mkdir" profile="/usr/lib/cups/backend/cups-pdf" 
name="/home/CODENET.LOCAL/codebase/PDF/" pid=6015 comm="cups-pdf" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0

  
  What I expected to happen:
  cups-pdf creates the pdf file it was supposed to.

  
  As a workaround, I set cups-pdf to use the third-party settings from the cups 
profile, then it worked as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-24 (281 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  Lpstat:
   device for EPSONET-4550: 
ipp://call.codenet.local:631/printers/EPSON_ET-4550_Series
   device for PDF: cups-pdf:/
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic apparmor apparmor apparmor apparmor
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-20 (104 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F21
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  

[Touch-packages] [Bug 1698693] Locale.txt

[Patrick Hibbs]

apport information

** Attachment added: "Locale.txt"
   https://bugs.launchpad.net/bugs/1698693/+attachment/5183607/+files/Locale.txt

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

Title:
  cups-pdf blocked by apparmor

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  cups-pdf cannot create the ~/PDF directory if it does not exist and
  fails with no indication to the user.

  It should however be pointed out that cups-pdf allows the system
  administrator to change it's output directory by changing the Out key
  in /etc/cups/cups-pdf.conf. As such apparmor will get in the way again
  if the admin changes the Out key to some other location outside of the
  ${HOME}/PDF directory. (It's default setting.)

  cups-pdf also does not have an #include for using local overrides in
  it's apparmor config. As such any fixes that the local admin makes
  will be overwritten by the next update to the cups package, breaking
  it again.

  
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  printer-driver-cups-pdf:
Installed: 2.6.1-21
Candidate: 2.6.1-21
Version table:
   *** 2.6.1-21 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  cups:
Installed: 2.1.3-4
Candidate: 2.1.3-4
Version table:
   *** 2.1.3-4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  What happened:
  cups-pdf when installed for the first time fails with the following apparmor 
denials:

  [ 6117.686934] audit: type=1400 audit(1497816878.998:1079): apparmor="DENIED" 
operation="file_inherit" profile="/usr/lib/cups/backend/cups-pdf" pid=6015 
comm="cups-pdf" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive" denied_mask="send receive" addr=none 
peer_addr=none peer="/usr/sbin/cupsd"
  [ 6117.686948] audit: type=1400 audit(1497816878.998:1080): apparmor="DENIED" 
operation="file_inherit" profile="/usr/sbin/cupsd" pid=6015 comm="cups-pdf" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none 
peer="/usr/lib/cups/backend/cups-pdf"
  [ 6117.688671] audit: type=1400 audit(1497816879.002:1081): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.688688] audit: type=1400 audit(1497816879.002:1082): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.689719] audit: type=1400 audit(1497816879.002:1083): apparmor="DENIED" 
operation="mkdir" profile="/usr/lib/cups/backend/cups-pdf" 
name="/home/CODENET.LOCAL/codebase/PDF/" pid=6015 comm="cups-pdf" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0

  
  What I expected to happen:
  cups-pdf creates the pdf file it was supposed to.

  
  As a workaround, I set cups-pdf to use the third-party settings from the cups 
profile, then it worked as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-24 (281 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  Lpstat:
   device for EPSONET-4550: 
ipp://call.codenet.local:631/printers/EPSON_ET-4550_Series
   device for PDF: cups-pdf:/
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic apparmor apparmor apparmor apparmor
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-20 (104 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F21
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  

[Touch-packages] [Bug 1698693] Lspci.txt

[Patrick Hibbs]

apport information

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

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

Title:
  cups-pdf blocked by apparmor

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  cups-pdf cannot create the ~/PDF directory if it does not exist and
  fails with no indication to the user.

  It should however be pointed out that cups-pdf allows the system
  administrator to change it's output directory by changing the Out key
  in /etc/cups/cups-pdf.conf. As such apparmor will get in the way again
  if the admin changes the Out key to some other location outside of the
  ${HOME}/PDF directory. (It's default setting.)

  cups-pdf also does not have an #include for using local overrides in
  it's apparmor config. As such any fixes that the local admin makes
  will be overwritten by the next update to the cups package, breaking
  it again.

  
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  printer-driver-cups-pdf:
Installed: 2.6.1-21
Candidate: 2.6.1-21
Version table:
   *** 2.6.1-21 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  cups:
Installed: 2.1.3-4
Candidate: 2.1.3-4
Version table:
   *** 2.1.3-4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  What happened:
  cups-pdf when installed for the first time fails with the following apparmor 
denials:

  [ 6117.686934] audit: type=1400 audit(1497816878.998:1079): apparmor="DENIED" 
operation="file_inherit" profile="/usr/lib/cups/backend/cups-pdf" pid=6015 
comm="cups-pdf" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive" denied_mask="send receive" addr=none 
peer_addr=none peer="/usr/sbin/cupsd"
  [ 6117.686948] audit: type=1400 audit(1497816878.998:1080): apparmor="DENIED" 
operation="file_inherit" profile="/usr/sbin/cupsd" pid=6015 comm="cups-pdf" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none 
peer="/usr/lib/cups/backend/cups-pdf"
  [ 6117.688671] audit: type=1400 audit(1497816879.002:1081): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.688688] audit: type=1400 audit(1497816879.002:1082): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.689719] audit: type=1400 audit(1497816879.002:1083): apparmor="DENIED" 
operation="mkdir" profile="/usr/lib/cups/backend/cups-pdf" 
name="/home/CODENET.LOCAL/codebase/PDF/" pid=6015 comm="cups-pdf" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0

  
  What I expected to happen:
  cups-pdf creates the pdf file it was supposed to.

  
  As a workaround, I set cups-pdf to use the third-party settings from the cups 
profile, then it worked as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-24 (281 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  Lpstat:
   device for EPSONET-4550: 
ipp://call.codenet.local:631/printers/EPSON_ET-4550_Series
   device for PDF: cups-pdf:/
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic apparmor apparmor apparmor apparmor
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-20 (104 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F21
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  

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

[Patrick Hibbs]

apport information

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

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

Title:
  cups-pdf blocked by apparmor

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  cups-pdf cannot create the ~/PDF directory if it does not exist and
  fails with no indication to the user.

  It should however be pointed out that cups-pdf allows the system
  administrator to change it's output directory by changing the Out key
  in /etc/cups/cups-pdf.conf. As such apparmor will get in the way again
  if the admin changes the Out key to some other location outside of the
  ${HOME}/PDF directory. (It's default setting.)

  cups-pdf also does not have an #include for using local overrides in
  it's apparmor config. As such any fixes that the local admin makes
  will be overwritten by the next update to the cups package, breaking
  it again.

  
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  printer-driver-cups-pdf:
Installed: 2.6.1-21
Candidate: 2.6.1-21
Version table:
   *** 2.6.1-21 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  cups:
Installed: 2.1.3-4
Candidate: 2.1.3-4
Version table:
   *** 2.1.3-4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  What happened:
  cups-pdf when installed for the first time fails with the following apparmor 
denials:

  [ 6117.686934] audit: type=1400 audit(1497816878.998:1079): apparmor="DENIED" 
operation="file_inherit" profile="/usr/lib/cups/backend/cups-pdf" pid=6015 
comm="cups-pdf" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive" denied_mask="send receive" addr=none 
peer_addr=none peer="/usr/sbin/cupsd"
  [ 6117.686948] audit: type=1400 audit(1497816878.998:1080): apparmor="DENIED" 
operation="file_inherit" profile="/usr/sbin/cupsd" pid=6015 comm="cups-pdf" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none 
peer="/usr/lib/cups/backend/cups-pdf"
  [ 6117.688671] audit: type=1400 audit(1497816879.002:1081): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.688688] audit: type=1400 audit(1497816879.002:1082): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.689719] audit: type=1400 audit(1497816879.002:1083): apparmor="DENIED" 
operation="mkdir" profile="/usr/lib/cups/backend/cups-pdf" 
name="/home/CODENET.LOCAL/codebase/PDF/" pid=6015 comm="cups-pdf" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0

  
  What I expected to happen:
  cups-pdf creates the pdf file it was supposed to.

  
  As a workaround, I set cups-pdf to use the third-party settings from the cups 
profile, then it worked as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-24 (281 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  Lpstat:
   device for EPSONET-4550: 
ipp://call.codenet.local:631/printers/EPSON_ET-4550_Series
   device for PDF: cups-pdf:/
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cups 2.2.7-1ubuntu2.1
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic apparmor apparmor apparmor apparmor
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-20 (104 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F21
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 

[Touch-packages] [Bug 1698693] Re: cups-pdf blocked by apparmor

[Patrick Hibbs]

apport information

** Tags added: apparmor apport-collected bionic

** Description changed:

  cups-pdf cannot create the ~/PDF directory if it does not exist and
  fails with no indication to the user.
  
  It should however be pointed out that cups-pdf allows the system
  administrator to change it's output directory by changing the Out key in
  /etc/cups/cups-pdf.conf. As such apparmor will get in the way again if
  the admin changes the Out key to some other location outside of the
  ${HOME}/PDF directory. (It's default setting.)
  
  cups-pdf also does not have an #include for using local overrides in
  it's apparmor config. As such any fixes that the local admin makes will
  be overwritten by the next update to the cups package, breaking it
  again.
  
  
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  
  printer-driver-cups-pdf:
Installed: 2.6.1-21
Candidate: 2.6.1-21
Version table:
   *** 2.6.1-21 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status
  
  cups:
Installed: 2.1.3-4
Candidate: 2.1.3-4
Version table:
   *** 2.1.3-4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  
  What happened:
  cups-pdf when installed for the first time fails with the following apparmor 
denials:
  
  [ 6117.686934] audit: type=1400 audit(1497816878.998:1079): apparmor="DENIED" 
operation="file_inherit" profile="/usr/lib/cups/backend/cups-pdf" pid=6015 
comm="cups-pdf" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive" denied_mask="send receive" addr=none 
peer_addr=none peer="/usr/sbin/cupsd"
  [ 6117.686948] audit: type=1400 audit(1497816878.998:1080): apparmor="DENIED" 
operation="file_inherit" profile="/usr/sbin/cupsd" pid=6015 comm="cups-pdf" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none 
peer="/usr/lib/cups/backend/cups-pdf"
  [ 6117.688671] audit: type=1400 audit(1497816879.002:1081): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.688688] audit: type=1400 audit(1497816879.002:1082): apparmor="DENIED" 
operation="open" profile="/usr/lib/cups/backend/cups-pdf" 
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 6117.689719] audit: type=1400 audit(1497816879.002:1083): apparmor="DENIED" 
operation="mkdir" profile="/usr/lib/cups/backend/cups-pdf" 
name="/home/CODENET.LOCAL/codebase/PDF/" pid=6015 comm="cups-pdf" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0
  
  
  What I expected to happen:
  cups-pdf creates the pdf file it was supposed to.
  
  
  As a workaround, I set cups-pdf to use the third-party settings from the cups 
profile, then it worked as expected.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.2
+ Architecture: amd64
+ CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2017-11-24 (281 days ago)
+ InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
+ Lpstat:
+  device for EPSONET-4550: 
ipp://call.codenet.local:631/printers/EPSON_ET-4550_Series
+  device for PDF: cups-pdf:/
+ MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: cups 2.2.7-1ubuntu2.1
+ PackageArchitecture: amd64
+ Papersize: letter
+ PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: 
Permission denied
+ ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal 
quiet splash
+ ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
+ Tags:  bionic apparmor apparmor apparmor apparmor
+ Uname: Linux 4.15.0-33-generic x86_64
+ UpgradeStatus: Upgraded to bionic on 2018-05-20 (104 days ago)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 02/08/2018
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: F21
+ dmi.board.asset.tag: Default string
+ dmi.board.name: A320M-S2H-CF
+ dmi.board.vendor: Gigabyte Technology Co., Ltd.
+ dmi.board.version: x.x
+ dmi.chassis.asset.tag: Default string
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Default string
+ dmi.chassis.version: Default string
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF21:bd02/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
+ dmi.product.family: 

[Touch-packages] [Bug 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon

[Patrick Wigmore]

I'm sorry, my previous comment seems to be untrue.

I have just found that aptitude will happily upgrade everything else the latest 
version, if I hold just these five packages at the versions listed:
libwayland-egl1-mesa:amd64 11.2.0-1ubuntu2
libegl1-mesa:amd64 11.2.0-1ubuntu2
libgl1-mesa-dri:i386 11.2.0-1ubuntu2
libgl1-mesa-dri:amd64 11.2.0-1ubuntu2
mesa-vdpau-drivers:amd64 11.2.0-1ubuntu2

So it is in fact possible to have just these five packages downgraded
while waiting for a fix.

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

Title:
  Recent libgl-mesa graphics update prevents drop down list menu
  appearing in apps like firefox three line/bar menu icon

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  PROBLEM

  Recent libgl-mesa 18.0.5-0ubuntu0~16.04.1 graphics update prevents
  drop down list menu appearing in apps like firefox three line/bar menu
  icon.

  After recently applying updates, left clicking on some application
  menus and icons no longer displays a drop-down menu list.

  For example in Firefox when I left-click on the **three line/bar**
  icon in the upper right-hand corner, the normal drop down list menu
  does not display.  Also the menu drop down doesn't display in
  keypassx.  Further xchat-gnome doesn't even display a window.

  Another anomaly is that my KDE bottom menu bar changed to a dark
  theme.

  
  BACKGROUND

  I'm using Kubuntu 16.04 on an Intel i7-7700k computer with Intel HD
  Graphics.  I have KDE **System Settings -> Compositor** enabled with:

 Scale method  :Accurate
 Rendering backend: OpenGL 3.1
 OpenGL interface:  GLX
 Tearing prevention ("vsync"):  Full screen repaints
 Keep window thumbnails:Only for Shown Windows

  
  INVESTIGATION

  After several hours of searching the Internet I found one other case
  of a similar problem.

 Firefox's Menu Bar won't open
 https://support.mozilla.org/en-US/questions/1194760

  The reported solution was to rollback the graphics drivers.

  
  Because the issues cropped up after applying updates on July 6, 2018,
  I tracked down the list of recent updates with:

 grep -A 2 'Start-Date: 2018-07-06' /var/log/apt/history.log | tail
  -1 >packages.txt

  After some editing to place packages on separate lines, and
  identifying the grahics libraries, I arrived at the following list:

  --

  libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)

  --

  To revert to the prior graphic drivers I tracked down the '.deb'
  packages for each of the above packages and downloaded the
  '17.2.8-0ubuntu0~16.04.1' version.

  For example:

  
https://launchpad.net/ubuntu/xenial/amd64/libxatracker2/17.2.8-0ubuntu0~16.04.1

  I also discovered that some of these depended on
  libllvm5.0_5.0-3~16.04.1 so I also downloaded the following files:

libllvm5.0_5.0-3~16.04.1_amd64.deb
libllvm5.0_5.0-3~16.04.1_i386.deb


  WORKAROUND (ROLLBACK TO PRIOR VERSION)

  Install older versions with:

  sudo dpkg -i \
libllvm5.0_5.0-3~16.04.1_amd64.deb \
libllvm5.0_5.0-3~16.04.1_i386.deb \
libegl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgbm1_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_i386.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgles2-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_i386.deb \
libwayland-egl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libxatracker2_17.2.8-0ubuntu0~16.04.1_amd64.deb \

[Touch-packages] [Bug 879825] Re: Severe logic errors in questionaire GUI

[Patrick Wigmore]

See also bug under Apport project
https://bugs.launchpad.net/apport/+bug/1163740

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

Title:
  Severe logic errors in questionaire GUI

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  The following misbehaviour are just examples I found during my first
  few clicks within this tool.

  Run "apport-bug" without any arguments.

  * A dialog appears asking "Which kind of problem do you want to report?"
  => Just clicking "ok" without selecting anything will crash the bug report 
application.
  => Selecting "Other Problem" brings up the "Display Problem" dialog, but 
"Display-Problem" is a completely different selection in the first dialog...

  * Clicking "Ok" without selection any option will also crash the bug report 
application at this point.
  * Clicking "Cancel" instead in this "Display Problem" dialog will completely 
freeze the bug report application, the windows will stay there but will not 
react to any interaction any more.

  I did not try anything further...

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: apport-kde 1.23-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportLog:
   
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 22 11:09:28 2011
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   LANG=de_DE@euro
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to oneiric on 2011-10-17 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/879825/+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 1462441] Re: apport hangs, wrong menu entries

[Patrick Wigmore]

*** This bug is a duplicate of bug 879825 ***
https://bugs.launchpad.net/bugs/879825

This looks like a duplicate of #879825

** This bug has been marked a duplicate of bug 879825
   Severe logic errors in questionaire GUI

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

Title:
  apport hangs, wrong menu entries

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Well, two problems. First:

  if you start ubuntu-bug without parameter, it shows a dialog
  containing:

  Other Problem
   (a lot of options)
  Display (X.org)

  first and last item are swapped. If you click other (the first), you
  will get a list of display problems. If you click Display (the last
  one), you will get "You need to specify a package or a PID. See --help
  for more information."

  Second problem:
  if you click cancel on the display page, apport hangs forever.
  Maybe duplicate of #660024

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: reportbug (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Jun  5 18:13:55 2015
  InstallationDate: Installed on 2013-10-25 (588 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: reportbug
  UpgradeStatus: Upgraded to vivid on 2015-05-19 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1462441/+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 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon

[Patrick Wigmore]

Thank you @gedakc for pointing out that old package versions are
available to download from Launchpad. I did not know that.

The intersection of the set of packages which @gedakc downgraded and the set of 
packages I downgraded is:
libegl1-mesa:amd64
libwayland-egl1-mesa:amd64
libgl1-mesa-dri:amd64
libgl1-mesa-dri:i386
mesa-vdpau-drivers:amd64

However, it is not possible to downgrade just the packages in this
intersection, due to unsatisfied dependencies.

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

Title:
  Recent libgl-mesa graphics update prevents drop down list menu
  appearing in apps like firefox three line/bar menu icon

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  PROBLEM

  Recent libgl-mesa 18.0.5-0ubuntu0~16.04.1 graphics update prevents
  drop down list menu appearing in apps like firefox three line/bar menu
  icon.

  After recently applying updates, left clicking on some application
  menus and icons no longer displays a drop-down menu list.

  For example in Firefox when I left-click on the **three line/bar**
  icon in the upper right-hand corner, the normal drop down list menu
  does not display.  Also the menu drop down doesn't display in
  keypassx.  Further xchat-gnome doesn't even display a window.

  Another anomaly is that my KDE bottom menu bar changed to a dark
  theme.

  
  BACKGROUND

  I'm using Kubuntu 16.04 on an Intel i7-7700k computer with Intel HD
  Graphics.  I have KDE **System Settings -> Compositor** enabled with:

 Scale method  :Accurate
 Rendering backend: OpenGL 3.1
 OpenGL interface:  GLX
 Tearing prevention ("vsync"):  Full screen repaints
 Keep window thumbnails:Only for Shown Windows

  
  INVESTIGATION

  After several hours of searching the Internet I found one other case
  of a similar problem.

 Firefox's Menu Bar won't open
 https://support.mozilla.org/en-US/questions/1194760

  The reported solution was to rollback the graphics drivers.

  
  Because the issues cropped up after applying updates on July 6, 2018,
  I tracked down the list of recent updates with:

 grep -A 2 'Start-Date: 2018-07-06' /var/log/apt/history.log | tail
  -1 >packages.txt

  After some editing to place packages on separate lines, and
  identifying the grahics libraries, I arrived at the following list:

  --

  libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)

  --

  To revert to the prior graphic drivers I tracked down the '.deb'
  packages for each of the above packages and downloaded the
  '17.2.8-0ubuntu0~16.04.1' version.

  For example:

  
https://launchpad.net/ubuntu/xenial/amd64/libxatracker2/17.2.8-0ubuntu0~16.04.1

  I also discovered that some of these depended on
  libllvm5.0_5.0-3~16.04.1 so I also downloaded the following files:

libllvm5.0_5.0-3~16.04.1_amd64.deb
libllvm5.0_5.0-3~16.04.1_i386.deb


  WORKAROUND (ROLLBACK TO PRIOR VERSION)

  Install older versions with:

  sudo dpkg -i \
libllvm5.0_5.0-3~16.04.1_amd64.deb \
libllvm5.0_5.0-3~16.04.1_i386.deb \
libegl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgbm1_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_i386.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgles2-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_i386.deb \
libwayland-egl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libxatracker2_17.2.8-0ubuntu0~16.04.1_amd64.deb \
mesa-vdpau-drivers_17.2.8-0ubuntu0~16.04.1_amd64.deb

  
  After 

[Touch-packages] [Bug 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon

[Patrick Wigmore]

Possible related or duplicate bug #1780846

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

Title:
  Recent libgl-mesa graphics update prevents drop down list menu
  appearing in apps like firefox three line/bar menu icon

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  PROBLEM

  Recent libgl-mesa 18.0.5-0ubuntu0~16.04.1 graphics update prevents
  drop down list menu appearing in apps like firefox three line/bar menu
  icon.

  After recently applying updates, left clicking on some application
  menus and icons no longer displays a drop-down menu list.

  For example in Firefox when I left-click on the **three line/bar**
  icon in the upper right-hand corner, the normal drop down list menu
  does not display.  Also the menu drop down doesn't display in
  keypassx.  Further xchat-gnome doesn't even display a window.

  Another anomaly is that my KDE bottom menu bar changed to a dark
  theme.

  
  BACKGROUND

  I'm using Kubuntu 16.04 on an Intel i7-7700k computer with Intel HD
  Graphics.  I have KDE **System Settings -> Compositor** enabled with:

 Scale method  :Accurate
 Rendering backend: OpenGL 3.1
 OpenGL interface:  GLX
 Tearing prevention ("vsync"):  Full screen repaints
 Keep window thumbnails:Only for Shown Windows

  
  INVESTIGATION

  After several hours of searching the Internet I found one other case
  of a similar problem.

 Firefox's Menu Bar won't open
 https://support.mozilla.org/en-US/questions/1194760

  The reported solution was to rollback the graphics drivers.

  
  Because the issues cropped up after applying updates on July 6, 2018,
  I tracked down the list of recent updates with:

 grep -A 2 'Start-Date: 2018-07-06' /var/log/apt/history.log | tail
  -1 >packages.txt

  After some editing to place packages on separate lines, and
  identifying the grahics libraries, I arrived at the following list:

  --

  libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)

  --

  To revert to the prior graphic drivers I tracked down the '.deb'
  packages for each of the above packages and downloaded the
  '17.2.8-0ubuntu0~16.04.1' version.

  For example:

  
https://launchpad.net/ubuntu/xenial/amd64/libxatracker2/17.2.8-0ubuntu0~16.04.1

  I also discovered that some of these depended on
  libllvm5.0_5.0-3~16.04.1 so I also downloaded the following files:

libllvm5.0_5.0-3~16.04.1_amd64.deb
libllvm5.0_5.0-3~16.04.1_i386.deb


  WORKAROUND (ROLLBACK TO PRIOR VERSION)

  Install older versions with:

  sudo dpkg -i \
libllvm5.0_5.0-3~16.04.1_amd64.deb \
libllvm5.0_5.0-3~16.04.1_i386.deb \
libegl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgbm1_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_i386.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgles2-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_i386.deb \
libwayland-egl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libxatracker2_17.2.8-0ubuntu0~16.04.1_amd64.deb \
mesa-vdpau-drivers_17.2.8-0ubuntu0~16.04.1_amd64.deb

  
  After rebooting, all the issues disappeared.

  For example I was once again able to left-click on the Firefox **three
  line/bar** menu and view the drop down list menu.  Also the KDE bottom
  menu bar retured to the normal "breeze" light grey colour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1780664/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages

[Touch-packages] [Bug 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly

[Patrick Wigmore]

Possible related or duplicate bug #1780664

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

Title:
  After update 2018-07-08 menus and buttons are behaving badly

Status in libdrm package in Ubuntu:
  Confirmed

Bug description:
  After an update to

     Description:   Ubuntu 16.04.4 LTS
     Release:   16.04

  Menus and buttons are behaving badly. This is a general issue, affecting most 
programs.
  Text in buttons is not always being displayed.
  When you mouse over an entry in a menu list the previous entry disappears
 e.g. the logout menu (power button icon at top right of panel)
  Menu items are getting red backgrounds where they were not before.

  Introduced by update done by update-manager on
     Last update Start-Date: 2018-07-08  21:25:10
  Modified packages:

   libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libapt-inst2.0:amd64 (1.2.26, 1.2.27)
   libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apt:amd64 (1.2.26, 1.2.27)
   libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libapt-pkg5.0:amd64 (1.2.26, 1.2.27)
   apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 
61.0+build3-0ubuntu0.16.04.2)
   libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apt-utils:amd64 (1.2.26, 1.2.27)
   libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2)
   apt-transport-https:amd64 (1.2.26, 1.2.27)
   libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1780846/+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 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon

[Patrick Wigmore]

This appears to be the same bug I am experiencing.

Graphical regression

Kubuntu xenial/16.04.4
Intel HD Graphics 530

Symptoms:
* Under KDE Plasma 5, the blur effect for most widgets with a transparent 
background is not rendered. Instead, an opaque background is rendered.

* The on-screen display provided by KMix when adjusting the volume using
keyboard hotkeys is not rendered. Instead, only its background blur
effect is rendered.

* In some applications, some pop-up menu widgets do not render (they are
invisible). For example, in Clementine, the drop down menu on the Stop
button does not appear visibly when summoned, the main menus do not
appear visibly when summoned, and the right-click menu does not appear
visibly when summoned. In Firefox, the all-in-one "hamburger" menu, as
well as other pop-ups from the main toolbar, do not appear visibly when
summoned. However, the main menus (accessed by pressing Alt, if hidden)
do appear. In the print dialogs in Okular, the drop-downs for "Page set"
and for printer-specific settings do not drop down. (Selection has to be
made by blindly scrolling through options using the arrow keys.)

As remarked by others, menu and volume OSD visibility is restored by
using XRender instead of OpenGL 3.1, but there is no background blur
effect and the background of Plasma widgets remains opaque.

For completeness, here are the results of my investigation into which
packages were causing the problem. This seems very similar to what has
already been said.

The symptoms appeared after upgrading some packages using the package
manager (aptitude).

The following subset of the package upgrades that took place appear to have 
caused the symptoms, since downgrading only these packages eliminates the 
symptoms:
package / old version / new version
libwayland-egl1-mesa:amd64 17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1
libdrm-common:all 2.4.83-1~16.04.1 2.4.91-2~16.04.1
libdrm-dev:amd64 2.4.83-1~16.04.1 2.4.91-2~16.04.1
libdrm2:amd64 2.4.83-1~16.04.1 2.4.91-2~16.04.1
libdrm2:i386 2.4.83-1~16.04.1 2.4.91-2~16.04.1
libdrm-intel1:amd64 2.4.83-1~16.04.1 2.4.91-2~16.04.1
libdrm-intel1:i386 2.4.83-1~16.04.1 2.4.91-2~16.04.1
libdrm-radeon1:amd64 2.4.83-1~16.04.1 2.4.91-2~16.04.1
libdrm-radeon1:i386 2.4.83-1~16.04.1 2.4.91-2~16.04.1
libdrm-nouveau2:amd64 2.4.83-1~16.04.1 2.4.91-2~16.04.1
libdrm-nouveau2:i386 2.4.83-1~16.04.1 2.4.91-2~16.04.1
libdrm-amdgpu1:amd64 2.4.83-1~16.04.1 2.4.91-2~16.04.1
libdrm-amdgpu1:i386 2.4.83-1~16.04.1 2.4.91-2~16.04.1
libegl1-mesa:amd64 17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1
libgl1-mesa-dri:i386 17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1
libgl1-mesa-dri:amd64 17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1
mesa-vdpau-drivers:amd64 17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1
libsensors4:i386 [not previously installed] 1:3.4.0-2

There were other package upgrades at the same time, but downgrading only these 
packages eliminated the symptoms. There are no symptoms with the following 
versions:
package / version downgraded to
libwayland-egl1-mesa:amd64 11.2.0-1ubuntu
libdrm-common:all 2.4.83-1
libdrm-dev:amd64 2.4.83-1
libdrm2:amd64 2.4.83-1
libdrm2:i386 2.4.83-1
libdrm-intel1:amd64 2.4.83-1
libdrm-intel1:i386 2.4.83-1
libdrm-radeon1:amd64 2.4.83-1
libdrm-radeon1:i386 2.4.83-1
libdrm-nouveau2:amd64 2.4.83-1
libdrm-nouveau2:i386 2.4.83-1
libdrm-amdgpu1:amd64 2.4.83-1
libdrm-amdgpu1:i386 2.4.83-1
libegl1-mesa:amd64 11.2.0-1ubuntu
libgl1-mesa-dri:i386 11.2.0-1ubuntu
libgl1-mesa-dri:amd64 11.2.0-1ubuntu
mesa-vdpau-drivers:amd64 11.2.0-1ubuntu
libsensors4:i386 [removed]

(N.B. I downloaded the 2.4.83-1 versions of the libdrm packages manually
from archive.ubuntu.com since the older version 2.4.67-1 in the xenial
repository created many dependency problems. These are therefore not
precisely the same package version as they were before the upgrade that
caused the symptoms.)

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

Title:
  Recent libgl-mesa graphics update prevents drop down list menu
  appearing in apps like firefox three line/bar menu icon

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  PROBLEM

  Recent libgl-mesa 18.0.5-0ubuntu0~16.04.1 graphics update prevents
  drop down list menu appearing in apps like firefox three line/bar menu
  icon.

  After recently applying updates, left clicking on some application
  menus and icons no longer displays a drop-down menu list.

  For example in Firefox when I left-click on the **three line/bar**
  icon in the upper right-hand corner, the normal drop down list menu
  does not display.  Also the menu drop down doesn't display in
  keypassx.  Further xchat-gnome doesn't even display a window.

  Another anomaly is that my KDE bottom menu bar changed to a dark
  theme.

  
  BACKGROUND

  I'm using Kubuntu 16.04 on an Intel i7-7700k computer with Intel HD
  

[Touch-packages] [Bug 558824] Re: menu items mixed up

[Patrick Wigmore]

*** This bug is a duplicate of bug 879825 ***
https://bugs.launchpad.net/bugs/879825

This seems to be the same bug as 879825. Marking as duplicate. (Please
correct if you do not think it is the same bug.)

** This bug has been marked a duplicate of bug 879825
   Severe logic errors in questionaire GUI

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

Title:
  menu items mixed up

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: apport-kde

  If I run ubuntu-bug, then select "other problem" then it offers me a
  list of sound problems to choose from. If I choose "Sound / Audio
  related problems" then it says "You need to specify a package or a
  PID". Also, if i choose cancel, it just hangs, and won't exit without
  being killed from command line (SIGTERM is enough though).

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: apport-kde 1.13.2-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic i686
  ApportLog:
   
  Architecture: i386
  Date: Fri Apr  9 00:24:12 2010
  InstallationMedia: Kubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100225)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/558824/+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 1060392] Re: apport-kde is weird after selecting problem type (audio)

[Patrick Wigmore]

*** This bug is a duplicate of bug 879825 ***
https://bugs.launchpad.net/bugs/879825

This looks like a duplicate of bug #879825. I will mark it as a
duplicate. Please correct if you think this is wrong.

** This bug has been marked a duplicate of bug 879825
   Severe logic errors in questionaire GUI

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

Title:
  apport-kde is weird after selecting problem type (audio)

Status in apport package in Ubuntu:
  New

Bug description:
  stefan@atlas-stfs:~$ lsb_release -rd
  Description:Ubuntu quantal (development branch)
  Release:12.10

  stefan@atlas-stfs:~$ apt-cache policy apport
  apport:
Installed: 2.6.1-0ubuntu1
Candidate: 2.6.1-0ubuntu1
Version table:
   *** 2.6.1-0ubuntu1 0
  500 http://is.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
  100 /var/lib/dpkg/status

  Description:
  After I start ubuntu-bug (or apport-bug) I select "Sound/audio related 
problem" from the list and press OK.

  Then I get a list that is totally unrelated to audio problems and
  instead have more to do with storage device problems (see screenshot).

  Now if I try to press Cancel in that menu, Apport freezes completely
  and I have to Ctrl+C it from the konsole window where I started it to
  get rid of the window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1060392/+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 637819] Re: apport-kde gives false options

[Patrick Wigmore]

*** This bug is a duplicate of bug 879825 ***
https://bugs.launchpad.net/bugs/879825

Appears to be same bug as #879825. Marking as duplicate.

** This bug has been marked a duplicate of bug 879825
   Severe logic errors in questionaire GUI

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

Title:
  apport-kde gives false options

Status in apport package in Ubuntu:
  New

Bug description:
  Binary package hint: apport-kde

  When using apport on kubuntu 10.04 with kde 4.5 installed though
  backports it gives totally false or wrong choices.

  eg. I you select a problem with display it gives options for sound and
  if you select sound it gives options for tty and ssh issues

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: apport-kde 1.13.3-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic x86_64
  NonfreeKernelModules: fglrx
  Architecture: amd64
  Date: Tue Sep 14 00:43:34 2010
  InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/637819/+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 879825] Re: Severe logic errors in questionaire GUI

[Patrick Wigmore]

Marked #951696 as duplicate of this bug due to identical symptoms. Still
present in apport-kde 2.20.1 on xenial.

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

Title:
  Severe logic errors in questionaire GUI

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  The following misbehaviour are just examples I found during my first
  few clicks within this tool.

  Run "apport-bug" without any arguments.

  * A dialog appears asking "Which kind of problem do you want to report?"
  => Just clicking "ok" without selecting anything will crash the bug report 
application.
  => Selecting "Other Problem" brings up the "Display Problem" dialog, but 
"Display-Problem" is a completely different selection in the first dialog...

  * Clicking "Ok" without selection any option will also crash the bug report 
application at this point.
  * Clicking "Cancel" instead in this "Display Problem" dialog will completely 
freeze the bug report application, the windows will stay there but will not 
react to any interaction any more.

  I did not try anything further...

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: apport-kde 1.23-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportLog:
   
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 22 11:09:28 2011
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   LANG=de_DE@euro
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to oneiric on 2011-10-17 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/879825/+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 951696] Re: "Other Problem" taken as "Display (X.org)" and then freezes

[Patrick Wigmore]

*** This bug is a duplicate of bug 879825 ***
https://bugs.launchpad.net/bugs/879825

** This bug has been marked a duplicate of bug 879825
   Severe logic errors in questionaire GUI

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

Title:
  "Other Problem" taken as "Display (X.org)" and then freezes

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  When I run ubuntu-bug without parameters and on the first choices I
  choose "Other problem" then the "Collecting Information" progress bar
  appears and It shows me a set of choises about display problems, as if
  I had choosen a display problem and then I can't close the windows and
  must kill the apport-kde app by terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: apport-kde 1.94.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  NonfreeKernelModules: fglrx
  ApportLog:
   
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  Date: Sat Mar 10 13:01:04 2012
  ExecutablePath: /usr/share/apport/apport-kde
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=es_CO:es
   TERM=xterm
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/951696/+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 951696] Re: "Other Problem" taken as "Display (X.org)" and then freezes

[Patrick Wigmore]

*** This bug is a duplicate of bug 879825 ***
https://bugs.launchpad.net/bugs/879825

This bug is still present in apport-kde 2.20.1 on xenial.

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

Title:
  "Other Problem" taken as "Display (X.org)" and then freezes

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  When I run ubuntu-bug without parameters and on the first choices I
  choose "Other problem" then the "Collecting Information" progress bar
  appears and It shows me a set of choises about display problems, as if
  I had choosen a display problem and then I can't close the windows and
  must kill the apport-kde app by terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: apport-kde 1.94.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  NonfreeKernelModules: fglrx
  ApportLog:
   
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  Date: Sat Mar 10 13:01:04 2012
  ExecutablePath: /usr/share/apport/apport-kde
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=es_CO:es
   TERM=xterm
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/951696/+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 1776686] [NEW] missing accountsservice.pc ?

[Patrick Welche]

Public bug reported:

Just tried to build gdm 3.28.2 from source on ubuntu 16.04.4.

Configure fails with:

configure: error: Package requirements (gobject-2.0 >= 2.36.0
gio-2.0 >= 2.36.0
gio-unix-2.0 >= 2.36.0
accountsservice >= 0.6.35
xcb
) were not met:

Package 'accountsservice', required by 'virtual:world', not found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

According to apt, the following are installed:

accountsservice/xenial-updates,now 0.6.40-2ubuntu11.3 amd64 
[installed,automatic]
  query and manipulate user account information

gir1.2-accountsservice-1.0/xenial-updates,now 0.6.40-2ubuntu11.3 amd64 
[installed]
  GObject introspection data for AccountService

libaccountsservice-dev/xenial-updates,now 0.6.40-2ubuntu11.3 amd64 [installed]
  query and manipulate user account information - header files

libaccountsservice0/xenial-updates,now 0.6.40-2ubuntu11.3 amd64 
[installed,automatic]
  query and manipulate user account information - shared libraries


Neither /usr/lib/pkgconfig nor /usr/share/pkgconfig contain accountsservice.pc 
=> I am assuming that it is missing.

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

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

Title:
  missing accountsservice.pc ?

Status in accountsservice package in Ubuntu:
  New

Bug description:
  Just tried to build gdm 3.28.2 from source on ubuntu 16.04.4.

  Configure fails with:

  configure: error: Package requirements (gobject-2.0 >= 2.36.0
  gio-2.0 >= 2.36.0
  gio-unix-2.0 >= 2.36.0
  accountsservice >= 0.6.35
  xcb
  ) were not met:

  Package 'accountsservice', required by 'virtual:world', not found

  Consider adjusting the PKG_CONFIG_PATH environment variable if you
  installed software in a non-standard prefix.

  According to apt, the following are installed:

  accountsservice/xenial-updates,now 0.6.40-2ubuntu11.3 amd64 
[installed,automatic]
query and manipulate user account information

  gir1.2-accountsservice-1.0/xenial-updates,now 0.6.40-2ubuntu11.3 amd64 
[installed]
GObject introspection data for AccountService

  libaccountsservice-dev/xenial-updates,now 0.6.40-2ubuntu11.3 amd64 [installed]
query and manipulate user account information - header files

  libaccountsservice0/xenial-updates,now 0.6.40-2ubuntu11.3 amd64 
[installed,automatic]
query and manipulate user account information - shared libraries

  
  Neither /usr/lib/pkgconfig nor /usr/share/pkgconfig contain 
accountsservice.pc => I am assuming that it is missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1776686/+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 1759300] Re: Gnome Shell: Touchpad right click (bottom right) area does not work

[Patrick Kilgore]

This is viewed as a confusing regression by a portion of the
userbase[0].  God knows it destroyed my workflow (and morning) when I
updated to 18.04 from 16.04.

For some of us 'old farts' who never use macs and always relied on the
"areas" behavior in both Linux and Windows it would be helpful to have
been told that the behavior changed and how to change it back, or simply
just asked, on installation, which option you want.

[0] https://askubuntu.com/questions/1028776/no-secondary-button-right-
click-on-touchpad/1028857#1028857

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

Title:
  Gnome Shell: Touchpad right click (bottom right) area does not work

Status in gsettings-desktop-schemas package in Ubuntu:
  Invalid

Bug description:
  The right (second) touchpad click does not work.
  It ceased to work about three months ago.
  ubuntu 18,04 aser ex2519

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1759300/+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 1603183] Re: Bottom right area of touchpad no longer treated as right click

[Patrick Kilgore]

@vanvugt I think this is still a big problem lots of 16.04 -> 18.04
upgraders will run into.

This one blew my mind after installing 18.04 today.  If this is going to
be the new default, we need to warn users, because those of us not using
Apple/ChromeOS hardware *expect* clickpads to work like they have for a
decade now so it feels like an Ubuntu regression / issue.

The easier solution may be to do a little bit of hardware detection
before Ubuntu configures this one for the users, and set the relevant
hardware accordingly (Apple/ChromeOs->"fingers";
Dell/Lenovo/Etc->"areas").

Currently (18.04), the easy fix for this is to set:

$ gsettings set org.gnome.desktop.peripherals.touchpad click-method
areas

My bug 1767383 is almost certainly a dupe of this one (sorry, I was
originally searching for it against the old driver), but I'll let
someone else decide that.

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

Title:
  Bottom right area of touchpad no longer treated as right click

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Triaged
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  Fix Released
Status in libinput package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Invalid
Status in unity8-desktop-session package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Using the touchpad I was not able to trigger any right click (with a
  single finger in the bottom right area), and I tought it was a problem
  of how unity8 handled the right clicks. Instead I just tried with a
  mouse and right click trigger different actions from left clicks.

  In the end the problem is that my touchpad right click is considered a
  left click by the system. This does not happen with an usb mouse.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603183/+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 1757538] Re: Some packages, e.g. systemd, fail to upgrade in Ubuntu app on Windows WSL (package systemd 234-2ubuntu12.3 failed to install/upgrade: subprocess installed post-insta

[Patrick M. Womack]

Reference https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748659

Most directly my work around:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748659/comments/13

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

Title:
  Some packages, e.g. systemd, fail to upgrade in Ubuntu app on Windows
  WSL (package systemd 234-2ubuntu12.3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This occurred after running do-release-upgrade on Ubuntu 16.04 on the
  Linux Subsystem Windows. After the upgrade has failed, there are now
  dependency problems with udev and libudev1, but I do not know whether
  these are connected.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 234-2ubuntu12.3
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Function not implemented
  Date: Wed Mar 21 21:51:43 2018
  Dmesg:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcInterrupts:
   
  ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro
  ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 
2: sort: cannot read: /proc/modules: No such file or directory
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.2.26
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: package systemd 234-2ubuntu12.3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-03-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1757538/+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 1701297] Re: NTP reload failure (unable to read library) on overlayfs

[Patrick M. Womack]

Hi all, sorry to necro a thread, but I'm having this issue on MAAS
2.3.1. Is anyone able to provide some insight into this issue?

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

Title:
  NTP reload failure (unable to read library) on overlayfs

Status in cloud-init:
  Won't Fix
Status in apparmor package in Ubuntu:
  Confirmed
Status in cloud-init package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  After update [1] of cloud-init in Ubuntu (which landed in xenial-
  updates on 2017-06-27), it is causing NTP reload failures.

  https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f-
  0ubuntu1~16.04.1

  In MAAS scenarios, this is causing the machine to fail to deploy.

  Related bugs:
   * bug 1645644: cloud-init ntp not using expected servers

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1701297/+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 1759769] [NEW] Failed to start AppArmor initialization.

[patrick]

Public bug reported:

ob for apparmor.service failed because the control process exited with error 
code.
See "systemctl  status apparmor.service" and "journalctl  -xe" for details.
invoke-rc.d: initscript apparmor, action "restart" failed.
● apparmor.service - AppArmor initialization
   Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Thu 2018-03-29 08:32:33 CEST; 9ms 
ago
 Docs: man:apparmor(7)
   http://wiki.apparmor.net/
  Process: 9534 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)
 Main PID: 9534 (code=exited, status=123)

mrt 29 08:32:33 osi-service apparmor[9534]: Skipping profile in 
/etc/apparmor.d/disable: usr.lib.libreoffice.program.senddoc
mrt 29 08:32:33 osi-service apparmor[9534]: Skipping profile in 
/etc/apparmor.d/disable: usr.lib.libreoffice.program.soffice.bin
mrt 29 08:32:33 osi-service apparmor[9534]: Skipping profile in 
/etc/apparmor.d/disable: usr.lib.libreoffice.program.xpdfimport
mrt 29 08:32:33 osi-service apparmor[9534]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in 
/etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor at line 14: 
Could not open '/usr/share/apparmor/hardware/audio.d'
mrt 29 08:32:33 osi-service apparmor[9534]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
mrt 29 08:32:33 osi-service apparmor[9534]:...fail!
mrt 29 08:32:33 osi-service systemd[1]: apparmor.service: Main process exited, 
code=exited, status=123/n/a
mrt 29 08:32:33 osi-service systemd[1]: Failed to start AppArmor initialization.
mrt 29 08:32:33 osi-service systemd[1]: apparmor.service: Unit entered failed 
state.
mrt 29 08:32:33 osi-service systemd[1]: apparmor.service: Failed with result 
'exit-code'.
dpkg: fout bij verwerken van pakket cqrlog (--remove):
 subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug
Fouten gevonden tijdens verwerken van:
 cqrlog
E: Sub-process /usr/bin/dpkg returned an error code (1)
patrick@osi-service:

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22
Uname: Linux 3.19.0-66-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Mar 29 08:30:03 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. G84 [GeForce 8600 GT] [1043:8259]
InstallationDate: Installed on 2016-04-09 (718 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7514
ProcEnviron:
 LANGUAGE=nl_BE:nl
 PATH=(custom, no user)
 LANG=nl_BE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-66-generic 
root=UUID=85bb4fa9-0aa0-4ead-999d-6694f541b35b ro splash quiet
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/02/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.3
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-7514
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.3:bd07/02/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7514:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7514:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
dmi.product.name: MS-7514
dmi.product.version: 1.0
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Thu Mar 29 07:05:26 2018
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2
xserver.video_driver: nouveau

** Affects: x

[Touch-packages] [Bug 1756031] Re: openssh-server doesn't accept aes256-cbc key

[Patrick Salecker]

Is our SSH ley length <1024 bit? Such short keys are refused by openssh
7.6.

When you open your key with Puttygen the length is shown in the
beginning of the "Key fingerprint" field. On Ubuntu you can check it
with "ssh-keygen -lf .ssh/authorized_keys".

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

Title:
  openssh-server doesn't accept aes256-cbc key

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  I am using putty connection with RSA key cached in pageant and want to
  login without password.

  Private key on windows:
  PuTTY-User-Key-File-2: ssh-rsa
  Encryption: aes256-cbc
  ...

  On ubuntu there is public key in .ssh/authorized_keys
  ssh-rsa B3Nz...JBjQ== palo@winpgnotas

  This key works well in ubuntu versions 14.04...17.10
  When I tried 18.04 beta, I am getting sshd error:
  mar 15 10:26:21 ubox sshd[5205]: error: userauth_pubkey: could not parse key: 
Invalid key length [preauth]
  and I have to provide password.

  I've found that aes256-cbc is not in the list of allowed ciphers by default, 
so I added
  Ciphers +aes256-cbc
  to /etc/ssh/sshd_config
  (and verified with nmap --script ssh2-enum-algos -sV -p 22 127.0.0.1)
  but the sshd error remains.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssh-server 1:7.6p1-4
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Thu Mar 15 10:03:14 2018
  InstallationDate: Installed on 2018-03-12 (2 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1756031/+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 1748659] Re: Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess retur

[Patrick M. Womack]

Ok, here it is. YMMV but this should theoretically fix systemd on 18.04
WSL.

** Attachment added: "Fix wsl 18.04 bash"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748659/+attachment/5073801/+files/fixwslsystemd.sh

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

Title:
  Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3
  failed to install/upgrade: installed systemd package post-installation
  script subprocess returned error exit status 1

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This was fresh Ubuntu 16.04 instance on Windows 10, running inside a
  Virtual Box on an iMac. I did an apt-get dist-upgrade before
  attempting to upgrade to 18.04.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Function not implemented
  Date: Sat Feb 10 18:59:28 2018
  Dmesg:
   
  ErrorMessage: installed systemd package post-installation script subprocess 
returned error exit status 1
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcInterrupts:
   
  ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro
  ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 
2: sort: cannot read: /proc/modules: No such file or directory
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.2.24
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: package systemd 235-3ubuntu3 failed to install/upgrade: installed 
systemd package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-02-10 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748659/+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 1748659] Re: Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess retur

[Patrick M. Womack]

Update for you all. I forced systemd down to the 16.04 version,
reconfigured it and it was happy. As for upgrading it to the 18.04
version, YOU MUST PURGE THE ENTIRE /usr/lib/tempfiles.d/ DIRECTORY. One
I did that, even thought the install will fail, I was able to get
systemd reconfigured. It now properly responds to dpkg --configure
commands and the system is no longer in a broken state.

As for how to resolve this upstream, I have a felling this has to do
with how WSL handles systemd (as, it doesn't, because WSL ignores
systemd for the most part.) most likely related to the fact that we're
not working with kernels, and systemd doesn't have anything to hook into
during the upgrade.

If you're having trouble with a system you forced to the 18.04 beta let
me know as I'm going to write a script here in a second to resolve the
issue for you.

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

Title:
  Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3
  failed to install/upgrade: installed systemd package post-installation
  script subprocess returned error exit status 1

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This was fresh Ubuntu 16.04 instance on Windows 10, running inside a
  Virtual Box on an iMac. I did an apt-get dist-upgrade before
  attempting to upgrade to 18.04.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Function not implemented
  Date: Sat Feb 10 18:59:28 2018
  Dmesg:
   
  ErrorMessage: installed systemd package post-installation script subprocess 
returned error exit status 1
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcInterrupts:
   
  ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro
  ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 
2: sort: cannot read: /proc/modules: No such file or directory
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.2.24
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: package systemd 235-3ubuntu3 failed to install/upgrade: installed 
systemd package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-02-10 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748659/+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 1748659] Re: Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess retur

[Patrick M. Womack]

I've gotten the release to upgrade to 18.04 on WSL, the issue I'm
running into however is that systemd will not reinstall. TBH WSL does
not require systemd to operate, but it defiantly makes the system angry
if it can't setup a way to manage startup. Just for anyone reading this
via google, if you want to push your WSL build to 18.04, DON'T. For
those of you who are ignoring my warning, you can push it to 18.04 BUT
YOU MUST HOLD SYSTEMD. If you try to run an upgrade and allow systemd to
be upgraded the upgrade will fail and you will be left with a completely
borked system. My thoughts at the moment is to try and grab a 16.04
systemd package and use that until we get a stable 18.04 one.

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

Title:
  Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3
  failed to install/upgrade: installed systemd package post-installation
  script subprocess returned error exit status 1

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This was fresh Ubuntu 16.04 instance on Windows 10, running inside a
  Virtual Box on an iMac. I did an apt-get dist-upgrade before
  attempting to upgrade to 18.04.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Function not implemented
  Date: Sat Feb 10 18:59:28 2018
  Dmesg:
   
  ErrorMessage: installed systemd package post-installation script subprocess 
returned error exit status 1
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcInterrupts:
   
  ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro
  ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 
2: sort: cannot read: /proc/modules: No such file or directory
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.2.24
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: package systemd 235-3ubuntu3 failed to install/upgrade: installed 
systemd package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-02-10 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748659/+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