[Touch-packages] [Bug 1882494] [NEW] [UBUNTU 20.04] zlib not working on all s390x systems configurations

[bugproxy]

Public bug reported:

Pull request (https://github.com/madler/zlib/pull/410) and tagged
https://github.com/iii-i/zlib/tree/dfltcc-20200511.

The new code contains the following improvements:
* Added support for switching between software and hardware compression.
* Added --dfltcc configure flag (the old way of building it still works).

Switching between software and hardware compression is not simply a
nice-to-have feature, but is actually required by Java - that's why we
are requesting an update.

** Affects: zlib (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-186085 severity-high 
targetmilestone-inin2004

** Tags added: architecture-s39064 bugnameltc-186085 severity-high
targetmilestone-inin2004

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

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

Title:
  [UBUNTU 20.04] zlib not working on all s390x systems configurations

Status in zlib package in Ubuntu:
  New

Bug description:
  Pull request (https://github.com/madler/zlib/pull/410) and tagged
  https://github.com/iii-i/zlib/tree/dfltcc-20200511.

  The new code contains the following improvements:
  * Added support for switching between software and hardware compression.
  * Added --dfltcc configure flag (the old way of building it still works).

  Switching between software and hardware compression is not simply a
  nice-to-have feature, but is actually required by Java - that's why we
  are requesting an update.

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

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

[Touch-packages] [Bug 1882494] [NEW] [UBUNTU 20.04] zlib not working on all s390x systems configurations

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Pull request (https://github.com/madler/zlib/pull/410) and tagged
https://github.com/iii-i/zlib/tree/dfltcc-20200511.

The new code contains the following improvements:
* Added support for switching between software and hardware compression.
* Added --dfltcc configure flag (the old way of building it still works).

Switching between software and hardware compression is not simply a
nice-to-have feature, but is actually required by Java - that's why we
are requesting an update.

** Affects: zlib (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-186085 severity-high 
targetmilestone-inin2004
-- 
[UBUNTU 20.04] zlib not working on all s390x systems configurations
https://bugs.launchpad.net/bugs/1882494
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to zlib in Ubuntu.

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

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

[Joakim Soendojo]

I do have this problem running Ubuntu 20.04.
Have been fiddling around with config, starting and stopping, apparmor and what 
not.
Currently running it in single node with services stopped on the backup.

Not very keen on downgrading but might have to go that path or migrate
to KEA.

A very big thanks for the downgrade fix Andrew.

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

Title:
  DHCP Cluster crashes after a few hours

Status in isc-dhcp package in Ubuntu:
  Confirmed

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

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

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


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

  
  nothing in kern.log

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


  /var/crash/_usr_sbin_dhcpd.0.crash shows

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872118/+subscriptions

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

[Touch-packages] [Bug 1882368] Re: Sound is louder after resume from suspend or logging in Ubuntu 20.04

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1882368

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

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

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

Title:
  Sound is louder after resume from suspend or logging in Ubuntu 20.04

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I'm running Ubuntu 20.04 and have noticed that after logging back on
  to a machine either after its been asleep/suspended or logged out due
  to inactivity the sound is much louder at the same volume. I haven't
  enabled amplification or any other sound feature.

  To duplicate, boot machine with volume at say 50% and listen to some
  music. Let it either log out or suspend/sleep and then log back in,
  start music/sound and it will be much louder.

  In fact this louder sound at the volume sounds correct, because the
  windows boot sounds the same at that level. When ubuntu boots the
  volume is much softer. The sound post logging in after a suspend or
  lock out is what it should be from the get go.

  Soundcard details
  00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
DeviceName: Onboard - Sound
Subsystem: Hewlett-Packard Company Cannon Lake PCH cAVS
Flags: bus master, fast devsel, latency 32, IRQ 143
Memory at a351 (64-bit, non-prefetchable) [size=16K]
Memory at a310 (64-bit, non-prefetchable) [size=1M]
Capabilities: [50] Power Management version 3
Capabilities: [80] Vendor Specific Information: Len=14 
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_sof_pci

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

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

[Touch-packages] [Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background

[Guy Baconniere]

The usage of motd-news as Advertising media for Canonical products is well 
documented.
Now we need to know if Canonical share the crafted User-Agent with sensible 
info in it with third party and use it for telemetry like Microsoft Windows 10.

Samples output of motd-news mirrored in both login prompt via motd and
syslog

- MicroK8s gets a native Windows installer and command-line integration.
  https://ubuntu.com/blog/microk8s-installers-windows-and-macos

- How HBO's Silicon Valley built "Not Hotdog" with mobile TensorFlow,
Keras & React Native on Ubuntu

- Overheard at KubeCon: "microk8s.status just blew my mind".
  https://microk8s.io/docs/commands#microk8s.status

https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068

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

Title:
  motd-news transmitting private hardware data without consent or
  knowledge in background

Status in base-files package in Ubuntu:
  Confirmed

Bug description:
  In package base-files there is a script /etc/update-motd.d/50-motd-
  news that harvests private hardware data from the machine and
  transmits it in the background every day.  There is no notice, no
  consent, no nothing.  This should be by default disabled until there
  is informed consent.

  This solution is simple:

  1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 
  2. Place a comment in the file disclosing the fact that the 50-motd-news 
script will harvest private hardware data and upload it to motd.ubuntu.com 
daily if the end-user enables it.

  Creating databases that maps ip address to specify hardware is a
  threat to both privacy and security.  If an adversary knows the
  specific hardware and the ip address for that hardware their ability
  to successfully attack it is greatly increased.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions

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

[Touch-packages] [Bug 1882376] Re: Can't connect to external audio TaoTronics TT-BA07

[Daniel van Vugt]

Looks like an aptX device, which Ubuntu doesn't support audio on yet.
But that should not prevent pairing...

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

Title:
  Can't connect to external audio TaoTronics TT-BA07

Status in bluez package in Ubuntu:
  New

Bug description:
  From my iphone and chromebook I can see the external speakers plugged
  to a TaoTronics TT-BA07 bluetooth device.

  But from Ubuntu 20.04, the device doesn't appear listed in the
  settings. There is listed a deviced named "1" that, when connecting
  to, appears to be a sound device, but from the sound settings "test"
  buttons I can't get any sound to play.

  Any hints as to how I could triage this issue and collect more
  details?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 17:22:16 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-06-24 (1442 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:705a Lite-On Technology Corp. Integrated Camera
   Bus 001 Device 006: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 056a:5040 Wacom Co., Ltd Pen and multitouch sensor
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FQCTO1WW
  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.4.0-33-generic 
root=UUID=972ac4f9-34e5-4cf0-a6ba-2fa4322fd70a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to focal on 2020-05-20 (17 days ago)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET40W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FQCTO1WW:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FQCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 1st
  dmi.product.name: 20FQCTO1WW
  dmi.product.sku: LENOVO_MT_20FQ_BU_Think_FM_ThinkPad X1 Yoga 1st
  dmi.product.version: ThinkPad X1 Yoga 1st
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:B3:18:78:A6:5D  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:43684 acl:117 sco:0 events:3823 errors:0
TX bytes:705943 acl:202 sco:0 commands:2991 errors:0

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

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

[Touch-packages] [Bug 1882354] Re: [Intel T4200] all application open in black

[Daniel van Vugt]

Can you please attach a screenshot or photo of the problem?

** Summary changed:

- graphics card
+ [Intel T4200] all application open in black

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

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

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

Title:
  [Intel T4200] all application open in black

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  all application open in black

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 18:13:44 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated 
Graphics Controller [144d:c540]
 Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated 
Graphics Controller [144d:c540]
  InstallationDate: Installed on 2020-06-05 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R468/R418
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=c84a78a6-96a8-49ab-9350-c471429971dd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/28/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 04NG.MP01.20090728.HCW
  dmi.board.name: R468/R418
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr04NG.MP01.20090728.HCW:bd07/28/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnR468/R418:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR468/R418:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: R468/R418
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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

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

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

[Touch-packages] [Bug 1880041] XorgLogOld.txt

[Daniel Klein]

apport information

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

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

Title:
  Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel
  versions 5.3.0-52 and later

Status in DRI:
  Unknown
Status in libdrm package in Ubuntu:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Confirmed

Bug description:
  When booting up Ubuntu 18.04 with a kernel version of 5.3.0-52 or
  later (including 5.3.0-53), everything seems to be working as usual.
  However, when I shutdown, the system will only soft shutdown, with the
  CPU still running at full power, forcing me to hold down the power
  button to fully power off affected systems. If I reboot, it will cause
  the system to hang and not respond. Either way, a hard reset or
  poweroff will be required, and this is not an option for systems being
  remotely accessed. It is not possible for me to collect kernel logs at
  this point, unless something wrong is happening in those kernel
  versions before the actual shutdown.

  It is possible that this may also occur on Ubuntu 20.04 with kernel
  versions 5.4.0-29 and later, but I have not yet tested this out. This
  problem is occurring on both my desktop and laptop computers which
  respectively are:

  * AsRock B450 Pro4 with AMD Ryzen 3 3200G APU
  * Lenovo ThinkPad A485 with AMD Ryzen 5 Pro 2500U mobile APU

  In the meantime, I am stuck on kernel version 5.3.0-51, as that is the
  last working 5.3.x kernel version offered in the standard Ubuntu
  repositories that doesn't have this problem, without me having to use
  PPAs. I don't know if this problem also occurs on systems with Intel
  CPUs, as I don't own any recently-made system (last 3 years from 2017)
  with such CPUs to test if this problem occurs on them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions

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

[Touch-packages] [Bug 1880041] XorgLog.txt

[Daniel Klein]

apport information

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

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

Title:
  Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel
  versions 5.3.0-52 and later

Status in DRI:
  Unknown
Status in libdrm package in Ubuntu:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Confirmed

Bug description:
  When booting up Ubuntu 18.04 with a kernel version of 5.3.0-52 or
  later (including 5.3.0-53), everything seems to be working as usual.
  However, when I shutdown, the system will only soft shutdown, with the
  CPU still running at full power, forcing me to hold down the power
  button to fully power off affected systems. If I reboot, it will cause
  the system to hang and not respond. Either way, a hard reset or
  poweroff will be required, and this is not an option for systems being
  remotely accessed. It is not possible for me to collect kernel logs at
  this point, unless something wrong is happening in those kernel
  versions before the actual shutdown.

  It is possible that this may also occur on Ubuntu 20.04 with kernel
  versions 5.4.0-29 and later, but I have not yet tested this out. This
  problem is occurring on both my desktop and laptop computers which
  respectively are:

  * AsRock B450 Pro4 with AMD Ryzen 3 3200G APU
  * Lenovo ThinkPad A485 with AMD Ryzen 5 Pro 2500U mobile APU

  In the meantime, I am stuck on kernel version 5.3.0-51, as that is the
  last working 5.3.x kernel version offered in the standard Ubuntu
  repositories that doesn't have this problem, without me having to use
  PPAs. I don't know if this problem also occurs on systems with Intel
  CPUs, as I don't own any recently-made system (last 3 years from 2017)
  with such CPUs to test if this problem occurs on them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions

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

[Touch-packages] [Bug 1880041] xdpyinfo.txt

[Daniel Klein]

apport information

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

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

Title:
  Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel
  versions 5.3.0-52 and later

Status in DRI:
  Unknown
Status in libdrm package in Ubuntu:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Confirmed

Bug description:
  When booting up Ubuntu 18.04 with a kernel version of 5.3.0-52 or
  later (including 5.3.0-53), everything seems to be working as usual.
  However, when I shutdown, the system will only soft shutdown, with the
  CPU still running at full power, forcing me to hold down the power
  button to fully power off affected systems. If I reboot, it will cause
  the system to hang and not respond. Either way, a hard reset or
  poweroff will be required, and this is not an option for systems being
  remotely accessed. It is not possible for me to collect kernel logs at
  this point, unless something wrong is happening in those kernel
  versions before the actual shutdown.

  It is possible that this may also occur on Ubuntu 20.04 with kernel
  versions 5.4.0-29 and later, but I have not yet tested this out. This
  problem is occurring on both my desktop and laptop computers which
  respectively are:

  * AsRock B450 Pro4 with AMD Ryzen 3 3200G APU
  * Lenovo ThinkPad A485 with AMD Ryzen 5 Pro 2500U mobile APU

  In the meantime, I am stuck on kernel version 5.3.0-51, as that is the
  last working 5.3.x kernel version offered in the standard Ubuntu
  repositories that doesn't have this problem, without me having to use
  PPAs. I don't know if this problem also occurs on systems with Intel
  CPUs, as I don't own any recently-made system (last 3 years from 2017)
  with such CPUs to test if this problem occurs on them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions

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

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

[Daniel Klein]

apport information

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

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

Title:
  Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel
  versions 5.3.0-52 and later

Status in DRI:
  Unknown
Status in libdrm package in Ubuntu:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Confirmed

Bug description:
  When booting up Ubuntu 18.04 with a kernel version of 5.3.0-52 or
  later (including 5.3.0-53), everything seems to be working as usual.
  However, when I shutdown, the system will only soft shutdown, with the
  CPU still running at full power, forcing me to hold down the power
  button to fully power off affected systems. If I reboot, it will cause
  the system to hang and not respond. Either way, a hard reset or
  poweroff will be required, and this is not an option for systems being
  remotely accessed. It is not possible for me to collect kernel logs at
  this point, unless something wrong is happening in those kernel
  versions before the actual shutdown.

  It is possible that this may also occur on Ubuntu 20.04 with kernel
  versions 5.4.0-29 and later, but I have not yet tested this out. This
  problem is occurring on both my desktop and laptop computers which
  respectively are:

  * AsRock B450 Pro4 with AMD Ryzen 3 3200G APU
  * Lenovo ThinkPad A485 with AMD Ryzen 5 Pro 2500U mobile APU

  In the meantime, I am stuck on kernel version 5.3.0-51, as that is the
  last working 5.3.x kernel version offered in the standard Ubuntu
  repositories that doesn't have this problem, without me having to use
  PPAs. I don't know if this problem also occurs on systems with Intel
  CPUs, as I don't own any recently-made system (last 3 years from 2017)
  with such CPUs to test if this problem occurs on them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions

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

[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Pandu Rakimanputra]

I also experience this issue with 2 different Brand of Bluetooth Headset:
ATH-CRK75BTH
Edifier W200BT

Problem also appears every time I switch bluetooh devices as INPUT
device and OUTPUT using HEADSET Unit (HSP/HFP). Input indicator bar
doesn't move and test OUTPUT doesn't produce any sound. When I tried
video conferencing with my friend, he couldn't hear my voice and of
course I can't hear him either.

This is fresh installation using Ubuntu 20.04 (no prior Ubuntu or other
Linux distro in this laptop). A2DP mode works normal. Currently I'm
using internal laptop microphone and A2DP combination for video
conferencing. Just now, I ran "sudo apt dist-upgrade, some packages were
updated. But still not work for HSP/HFP mode output and Bluetooth mic
input.

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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

[Touch-packages] [Bug 1880041] Xrandr.txt

[Daniel Klein]

apport information

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

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

Title:
  Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel
  versions 5.3.0-52 and later

Status in DRI:
  Unknown
Status in libdrm package in Ubuntu:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Confirmed

Bug description:
  When booting up Ubuntu 18.04 with a kernel version of 5.3.0-52 or
  later (including 5.3.0-53), everything seems to be working as usual.
  However, when I shutdown, the system will only soft shutdown, with the
  CPU still running at full power, forcing me to hold down the power
  button to fully power off affected systems. If I reboot, it will cause
  the system to hang and not respond. Either way, a hard reset or
  poweroff will be required, and this is not an option for systems being
  remotely accessed. It is not possible for me to collect kernel logs at
  this point, unless something wrong is happening in those kernel
  versions before the actual shutdown.

  It is possible that this may also occur on Ubuntu 20.04 with kernel
  versions 5.4.0-29 and later, but I have not yet tested this out. This
  problem is occurring on both my desktop and laptop computers which
  respectively are:

  * AsRock B450 Pro4 with AMD Ryzen 3 3200G APU
  * Lenovo ThinkPad A485 with AMD Ryzen 5 Pro 2500U mobile APU

  In the meantime, I am stuck on kernel version 5.3.0-51, as that is the
  last working 5.3.x kernel version offered in the standard Ubuntu
  repositories that doesn't have this problem, without me having to use
  PPAs. I don't know if this problem also occurs on systems with Intel
  CPUs, as I don't own any recently-made system (last 3 years from 2017)
  with such CPUs to test if this problem occurs on them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions

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

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

[Daniel Klein]

apport information

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

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

Title:
  Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel
  versions 5.3.0-52 and later

Status in DRI:
  Unknown
Status in libdrm package in Ubuntu:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Confirmed

Bug description:
  When booting up Ubuntu 18.04 with a kernel version of 5.3.0-52 or
  later (including 5.3.0-53), everything seems to be working as usual.
  However, when I shutdown, the system will only soft shutdown, with the
  CPU still running at full power, forcing me to hold down the power
  button to fully power off affected systems. If I reboot, it will cause
  the system to hang and not respond. Either way, a hard reset or
  poweroff will be required, and this is not an option for systems being
  remotely accessed. It is not possible for me to collect kernel logs at
  this point, unless something wrong is happening in those kernel
  versions before the actual shutdown.

  It is possible that this may also occur on Ubuntu 20.04 with kernel
  versions 5.4.0-29 and later, but I have not yet tested this out. This
  problem is occurring on both my desktop and laptop computers which
  respectively are:

  * AsRock B450 Pro4 with AMD Ryzen 3 3200G APU
  * Lenovo ThinkPad A485 with AMD Ryzen 5 Pro 2500U mobile APU

  In the meantime, I am stuck on kernel version 5.3.0-51, as that is the
  last working 5.3.x kernel version offered in the standard Ubuntu
  repositories that doesn't have this problem, without me having to use
  PPAs. I don't know if this problem also occurs on systems with Intel
  CPUs, as I don't own any recently-made system (last 3 years from 2017)
  with such CPUs to test if this problem occurs on them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions

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

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

[Daniel Klein]

apport information

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

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

Title:
  Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel
  versions 5.3.0-52 and later

Status in DRI:
  Unknown
Status in libdrm package in Ubuntu:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Confirmed

Bug description:
  When booting up Ubuntu 18.04 with a kernel version of 5.3.0-52 or
  later (including 5.3.0-53), everything seems to be working as usual.
  However, when I shutdown, the system will only soft shutdown, with the
  CPU still running at full power, forcing me to hold down the power
  button to fully power off affected systems. If I reboot, it will cause
  the system to hang and not respond. Either way, a hard reset or
  poweroff will be required, and this is not an option for systems being
  remotely accessed. It is not possible for me to collect kernel logs at
  this point, unless something wrong is happening in those kernel
  versions before the actual shutdown.

  It is possible that this may also occur on Ubuntu 20.04 with kernel
  versions 5.4.0-29 and later, but I have not yet tested this out. This
  problem is occurring on both my desktop and laptop computers which
  respectively are:

  * AsRock B450 Pro4 with AMD Ryzen 3 3200G APU
  * Lenovo ThinkPad A485 with AMD Ryzen 5 Pro 2500U mobile APU

  In the meantime, I am stuck on kernel version 5.3.0-51, as that is the
  last working 5.3.x kernel version offered in the standard Ubuntu
  repositories that doesn't have this problem, without me having to use
  PPAs. I don't know if this problem also occurs on systems with Intel
  CPUs, as I don't own any recently-made system (last 3 years from 2017)
  with such CPUs to test if this problem occurs on them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions

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

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

[Daniel Klein]

apport information

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

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

Title:
  Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel
  versions 5.3.0-52 and later

Status in DRI:
  Unknown
Status in libdrm package in Ubuntu:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Confirmed

Bug description:
  When booting up Ubuntu 18.04 with a kernel version of 5.3.0-52 or
  later (including 5.3.0-53), everything seems to be working as usual.
  However, when I shutdown, the system will only soft shutdown, with the
  CPU still running at full power, forcing me to hold down the power
  button to fully power off affected systems. If I reboot, it will cause
  the system to hang and not respond. Either way, a hard reset or
  poweroff will be required, and this is not an option for systems being
  remotely accessed. It is not possible for me to collect kernel logs at
  this point, unless something wrong is happening in those kernel
  versions before the actual shutdown.

  It is possible that this may also occur on Ubuntu 20.04 with kernel
  versions 5.4.0-29 and later, but I have not yet tested this out. This
  problem is occurring on both my desktop and laptop computers which
  respectively are:

  * AsRock B450 Pro4 with AMD Ryzen 3 3200G APU
  * Lenovo ThinkPad A485 with AMD Ryzen 5 Pro 2500U mobile APU

  In the meantime, I am stuck on kernel version 5.3.0-51, as that is the
  last working 5.3.x kernel version offered in the standard Ubuntu
  repositories that doesn't have this problem, without me having to use
  PPAs. I don't know if this problem also occurs on systems with Intel
  CPUs, as I don't own any recently-made system (last 3 years from 2017)
  with such CPUs to test if this problem occurs on them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions

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

[Touch-packages] [Bug 1880041] CurrentDmesg.txt

[Daniel Klein]

apport information

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

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

Title:
  Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel
  versions 5.3.0-52 and later

Status in DRI:
  Unknown
Status in libdrm package in Ubuntu:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Confirmed

Bug description:
  When booting up Ubuntu 18.04 with a kernel version of 5.3.0-52 or
  later (including 5.3.0-53), everything seems to be working as usual.
  However, when I shutdown, the system will only soft shutdown, with the
  CPU still running at full power, forcing me to hold down the power
  button to fully power off affected systems. If I reboot, it will cause
  the system to hang and not respond. Either way, a hard reset or
  poweroff will be required, and this is not an option for systems being
  remotely accessed. It is not possible for me to collect kernel logs at
  this point, unless something wrong is happening in those kernel
  versions before the actual shutdown.

  It is possible that this may also occur on Ubuntu 20.04 with kernel
  versions 5.4.0-29 and later, but I have not yet tested this out. This
  problem is occurring on both my desktop and laptop computers which
  respectively are:

  * AsRock B450 Pro4 with AMD Ryzen 3 3200G APU
  * Lenovo ThinkPad A485 with AMD Ryzen 5 Pro 2500U mobile APU

  In the meantime, I am stuck on kernel version 5.3.0-51, as that is the
  last working 5.3.x kernel version offered in the standard Ubuntu
  repositories that doesn't have this problem, without me having to use
  PPAs. I don't know if this problem also occurs on systems with Intel
  CPUs, as I don't own any recently-made system (last 3 years from 2017)
  with such CPUs to test if this problem occurs on them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions

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

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

[Daniel Klein]

apport information

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

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

Title:
  Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel
  versions 5.3.0-52 and later

Status in DRI:
  Unknown
Status in libdrm package in Ubuntu:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Confirmed

Bug description:
  When booting up Ubuntu 18.04 with a kernel version of 5.3.0-52 or
  later (including 5.3.0-53), everything seems to be working as usual.
  However, when I shutdown, the system will only soft shutdown, with the
  CPU still running at full power, forcing me to hold down the power
  button to fully power off affected systems. If I reboot, it will cause
  the system to hang and not respond. Either way, a hard reset or
  poweroff will be required, and this is not an option for systems being
  remotely accessed. It is not possible for me to collect kernel logs at
  this point, unless something wrong is happening in those kernel
  versions before the actual shutdown.

  It is possible that this may also occur on Ubuntu 20.04 with kernel
  versions 5.4.0-29 and later, but I have not yet tested this out. This
  problem is occurring on both my desktop and laptop computers which
  respectively are:

  * AsRock B450 Pro4 with AMD Ryzen 3 3200G APU
  * Lenovo ThinkPad A485 with AMD Ryzen 5 Pro 2500U mobile APU

  In the meantime, I am stuck on kernel version 5.3.0-51, as that is the
  last working 5.3.x kernel version offered in the standard Ubuntu
  repositories that doesn't have this problem, without me having to use
  PPAs. I don't know if this problem also occurs on systems with Intel
  CPUs, as I don't own any recently-made system (last 3 years from 2017)
  with such CPUs to test if this problem occurs on them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions

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

[Touch-packages] [Bug 1880041] DpkgLog.txt

[Daniel Klein]

apport information

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

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

Title:
  Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel
  versions 5.3.0-52 and later

Status in DRI:
  Unknown
Status in libdrm package in Ubuntu:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Confirmed

Bug description:
  When booting up Ubuntu 18.04 with a kernel version of 5.3.0-52 or
  later (including 5.3.0-53), everything seems to be working as usual.
  However, when I shutdown, the system will only soft shutdown, with the
  CPU still running at full power, forcing me to hold down the power
  button to fully power off affected systems. If I reboot, it will cause
  the system to hang and not respond. Either way, a hard reset or
  poweroff will be required, and this is not an option for systems being
  remotely accessed. It is not possible for me to collect kernel logs at
  this point, unless something wrong is happening in those kernel
  versions before the actual shutdown.

  It is possible that this may also occur on Ubuntu 20.04 with kernel
  versions 5.4.0-29 and later, but I have not yet tested this out. This
  problem is occurring on both my desktop and laptop computers which
  respectively are:

  * AsRock B450 Pro4 with AMD Ryzen 3 3200G APU
  * Lenovo ThinkPad A485 with AMD Ryzen 5 Pro 2500U mobile APU

  In the meantime, I am stuck on kernel version 5.3.0-51, as that is the
  last working 5.3.x kernel version offered in the standard Ubuntu
  repositories that doesn't have this problem, without me having to use
  PPAs. I don't know if this problem also occurs on systems with Intel
  CPUs, as I don't own any recently-made system (last 3 years from 2017)
  with such CPUs to test if this problem occurs on them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions

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

[Touch-packages] [Bug 1880041] Re: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later

[Daniel Klein]

ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] 
[1002:687f] (rev c3) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 
64] [1002:0b36]
InstallationDate: Installed on 2019-04-12 (422 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Micro-Star International Co., Ltd MS-7B86
Package: linux-meta-hwe
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-51-generic 
root=UUID=afdf9011-a57a-434a-bcb5-0587e1b57161 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
Tags:  bionic ubuntu
Uname: Linux 5.3.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/21/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.20
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450 GAMING PLUS (MS-7B86)
dmi.board.vendor: Micro-Star International Co., Ltd
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.20:bd09/21/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7B86:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB450GAMINGPLUS(MS-7B86):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B86
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A


** Tags added: apport-collected bionic ubuntu

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

Title:
  Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel
  versions 5.3.0-52 and later

Status in DRI:
  Unknown
Status in libdrm package in Ubuntu:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Confirmed

Bug description:
  When booting up Ubuntu 18.04 with a kernel version of 5.3.0-52 or
  later (including 5.3.0-53), everything seems to be working as usual.
  However, when I shutdown, the system will only soft shutdown, with the
  CPU still running at full power, forcing me to hold down the power
  button to fully power off affected systems. If I reboot, it will cause
  the system to hang and not respond. Either way, a hard reset or
  poweroff will be required, and this is not an option for systems being
  remotely accessed. It is not possible for me to collect kernel logs at
  this point, unless something wrong is happening in those kernel
  versions before the actual shutdown.

  It is possible that this may also occur on Ubuntu 20.04 with kernel
  versions 5.4.0-29 and later, but I have not yet tested this out. This
  problem is occurring on both my desktop and laptop computers which
  respectively are:

  * AsRock B450 Pro4 with AMD Ryzen 3 3200G APU
  * Lenovo ThinkPad A485 with AMD Ryzen 5 Pro 2500U mobile APU

  In the meantime, I am stuck on kernel version 5.3.0-51, as that is the
  last working 5.3.x kernel version offered in the standard Ubuntu
  repositories that doesn't have this problem, without me having to use
  PPAs. I don't know if this problem also occurs on systems with Intel
  CPUs, as I don't own any recently-made system (last 3 years from 2017)
  with such CPUs to test if this problem occurs on them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions

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

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

[Daniel Klein]

apport information

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

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

Title:
  Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel
  versions 5.3.0-52 and later

Status in DRI:
  Unknown
Status in libdrm package in Ubuntu:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Confirmed

Bug description:
  When booting up Ubuntu 18.04 with a kernel version of 5.3.0-52 or
  later (including 5.3.0-53), everything seems to be working as usual.
  However, when I shutdown, the system will only soft shutdown, with the
  CPU still running at full power, forcing me to hold down the power
  button to fully power off affected systems. If I reboot, it will cause
  the system to hang and not respond. Either way, a hard reset or
  poweroff will be required, and this is not an option for systems being
  remotely accessed. It is not possible for me to collect kernel logs at
  this point, unless something wrong is happening in those kernel
  versions before the actual shutdown.

  It is possible that this may also occur on Ubuntu 20.04 with kernel
  versions 5.4.0-29 and later, but I have not yet tested this out. This
  problem is occurring on both my desktop and laptop computers which
  respectively are:

  * AsRock B450 Pro4 with AMD Ryzen 3 3200G APU
  * Lenovo ThinkPad A485 with AMD Ryzen 5 Pro 2500U mobile APU

  In the meantime, I am stuck on kernel version 5.3.0-51, as that is the
  last working 5.3.x kernel version offered in the standard Ubuntu
  repositories that doesn't have this problem, without me having to use
  PPAs. I don't know if this problem also occurs on systems with Intel
  CPUs, as I don't own any recently-made system (last 3 years from 2017)
  with such CPUs to test if this problem occurs on them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions

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

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

[Daniel Klein]

apport information

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

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

Title:
  Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel
  versions 5.3.0-52 and later

Status in DRI:
  Unknown
Status in libdrm package in Ubuntu:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Confirmed

Bug description:
  When booting up Ubuntu 18.04 with a kernel version of 5.3.0-52 or
  later (including 5.3.0-53), everything seems to be working as usual.
  However, when I shutdown, the system will only soft shutdown, with the
  CPU still running at full power, forcing me to hold down the power
  button to fully power off affected systems. If I reboot, it will cause
  the system to hang and not respond. Either way, a hard reset or
  poweroff will be required, and this is not an option for systems being
  remotely accessed. It is not possible for me to collect kernel logs at
  this point, unless something wrong is happening in those kernel
  versions before the actual shutdown.

  It is possible that this may also occur on Ubuntu 20.04 with kernel
  versions 5.4.0-29 and later, but I have not yet tested this out. This
  problem is occurring on both my desktop and laptop computers which
  respectively are:

  * AsRock B450 Pro4 with AMD Ryzen 3 3200G APU
  * Lenovo ThinkPad A485 with AMD Ryzen 5 Pro 2500U mobile APU

  In the meantime, I am stuck on kernel version 5.3.0-51, as that is the
  last working 5.3.x kernel version offered in the standard Ubuntu
  repositories that doesn't have this problem, without me having to use
  PPAs. I don't know if this problem also occurs on systems with Intel
  CPUs, as I don't own any recently-made system (last 3 years from 2017)
  with such CPUs to test if this problem occurs on them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions

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

[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Pandu Rakimanputra]

I also experience this issue with 2 different Brand of Bluetooth Headset:
ATH-CRK75BTH
Edifier W200BT

Problem also appears every time I switch bluetooh devices as INPUT
device and OUTPUT using HEADSET Unit (HSP/HFP). Input indicator bar
doesn't move and test OUTPUT doesn't produce any sound. When I tried
video conferencing with my friend, he couldn't hear my voice and of
course I can't hear him either.

This is fresh installation using Ubuntu 20.04 (no prior Ubuntu or other
Linux distro in this laptop). A2DP mode works normal. Currently I'm
using internal laptop microphone and A2DP combination for video
conferencing. Just now, I ran "sudo apt dist-upgrade, some packages were
updated. But still not work for HSP/HFP mode output and Bluetooth mic
input.

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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

[Touch-packages] [Bug 1876320] Re: Port parameter sshd_config is 22 AND whatever you specify

[Christian Ehrhardt ]

FYI
- 1:8.2p1-4ubuntu1 migrated into groovy
- 1:8.3p1-1 got into Debian containing the fix, so this can be a sync again
- added SRU template here
- uploaded to Focal-unapproved

** Description changed:

+ [Impact]
+ 
+  * The "Port" option in sshd_config is accumulative, but due to a bug re-
+adds the default when an include is encountered. Therefore we have these 
+cases
+a) Port 722
+   Listens on 722 (correct)
+b) Port 722
+   Port 
+   Listens on 722 &  (correct)
+c) Port 722
+   include /path/to/otherconfig
+   Listens on 722 & 22 (applied defaults as if Port was unset)
+ 
+  * Of the above (c) is a bug, not documented that way and can lead to open 
+ports not expected and not wanted.
+ 
+ [Test Case]
+ 
+ * Test if defaults are applied even if option is specified
+ 
+ Rename sshd_config to something_else and replace sshd_config with two
+ lines to include the original config (now called something_else) and set
+ the Port to 7722:
+ 
+ systemctl stop ssh
+ mv /etc/ssh/sshd_config /etc/ssh/something_else
+ cat > /etc/ssh/sshd_config  /etc/ssh/sshd_config 

[Touch-packages] [Bug 1868988] Re: apt assert failure: malloc(): mismatching next->prev_size (unsorted)

[Launchpad Bug Tracker]

[Expired for apt (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  apt assert failure: malloc(): mismatching next->prev_size (unsorted)

Status in apt package in Ubuntu:
  Expired

Bug description:
  libwxbase3.0-0v5 libwxgtk3.0-gtk3-0v5

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.0
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AssertionMessage: malloc(): mismatching next->prev_size (unsorted)
  Date: Wed Mar 25 14:19:48 2020
  ExecutablePath: /usr/bin/apt
  InstallationDate: Installed on 2020-03-17 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  ProcCmdline: apt upgrade
  Signal: 6
  SourcePackage: apt
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5e92ba0285 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f5e92ba2aa0 "malloc(): mismatching 
next->prev_size (unsorted)") at malloc.c:5347
   _int_malloc (av=av@entry=0x7f5e92bd1b80 , bytes=bytes@entry=128) 
at malloc.c:3741
   __GI___libc_malloc (bytes=128) at malloc.c:3058
   operator new(unsigned long) () from /lib/x86_64-linux-gnu/libstdc++.so.6
  Title: apt assert failure: malloc(): mismatching next->prev_size (unsorted)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

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

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

[Touch-packages] [Bug 1882481] Re: A dialog box stays on desktop and does not go away

[Daniel van Vugt]

This sounds like bug 1824874. To help us check that please:

1. Provide a screenshot or photo of the problem; and

2. After the dialog has appeared run:

   journalctl -b0 > journal.txt

   or if you had to reboot then run:

   journalctl -b-1 > prevboot.txt

   and attach the resulting text file here.


** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  A dialog box stays on desktop and does not go away

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Upon rebooting, I get dialog box

  Authentication Required

  Authentication is required to start 'cups.service'.

  I can type in the password and click Authenticate, but then nothing
  happens. I can't see under the box. I can't move the box, can't cancel
  the dialog.

  But, I can click on where I know the underneath icon to be and that
  click is accepted and the program in question runs. It appears the
  display manager does not remove the image after it is done with the
  dialog.


  I have recently done a clean install of 20.04.

  
  There is a screenshot in this Stack Exchange post:
  
https://askubuntu.com/questions/1242999/dialog-box-does-not-accept-input-stays-on-top-and-hides-everything-under-it-ub

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  7 23:10:43 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu, 3.3-19, 5.4.0-31-generic, x86_64: installed
   amdgpu, 3.3-19, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 
[1462:8a92]
  InstallationDate: Installed on 2020-05-12 (26 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=ebb08f84-7501-4461-a5c4-c69c3c25d9b0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0804
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0804:bd11/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx: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
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882481/+subscriptions

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

[Touch-packages] [Bug 1882481] Re: A dialog box stays on desktop and does not go away

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  A dialog box stays on desktop and does not go away

Status in xorg package in Ubuntu:
  New

Bug description:
  Upon rebooting, I get dialog box

  Authentication Required

  Authentication is required to start 'cups.service'.

  I can type in the password and click Authenticate, but then nothing
  happens. I can't see under the box. I can't move the box, can't cancel
  the dialog.

  But, I can click on where I know the underneath icon to be and that
  click is accepted and the program in question runs. It appears the
  display manager does not remove the image after it is done with the
  dialog.


  I have recently done a clean install of 20.04.

  
  There is a screenshot in this Stack Exchange post:
  
https://askubuntu.com/questions/1242999/dialog-box-does-not-accept-input-stays-on-top-and-hides-everything-under-it-ub

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  7 23:10:43 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu, 3.3-19, 5.4.0-31-generic, x86_64: installed
   amdgpu, 3.3-19, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 
[1462:8a92]
  InstallationDate: Installed on 2020-05-12 (26 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=ebb08f84-7501-4461-a5c4-c69c3c25d9b0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0804
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0804:bd11/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx: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
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1882484] [NEW] Firewall rule in before.rules for dhcp is wrong

[Joshua Stark]

Public bug reported:

The file delivered - /usr/share/ufw/iptables/before.rules
which is then copied to - /etc/ufw/before.rules

Delivered by Package:

# allow dhcp client to work
-A ufw-before-input -p udp --sport 67 --dport 68 -j ACCEPT

The ports for
--sport and --dport are swapped

Should be:

-A ufw-before-input -p udp --sport 68 --dport 67 -j ACCEPT


Package version found in:
  0.36-0ubuntu0.1


Note: ISC DHCP uses RAW sockets, which bypasses iptables anyway and doesn't 
drop the packets with the incorrect configuration. This has had me stumped for 
the last hour.

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

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

Title:
  Firewall rule in before.rules for dhcp is wrong

Status in ufw package in Ubuntu:
  New

Bug description:
  The file delivered - /usr/share/ufw/iptables/before.rules
  which is then copied to - /etc/ufw/before.rules

  Delivered by Package:

  # allow dhcp client to work
  -A ufw-before-input -p udp --sport 67 --dport 68 -j ACCEPT

  The ports for
  --sport and --dport are swapped

  Should be:

  -A ufw-before-input -p udp --sport 68 --dport 67 -j ACCEPT

  
  Package version found in:
0.36-0ubuntu0.1

  
  Note: ISC DHCP uses RAW sockets, which bypasses iptables anyway and doesn't 
drop the packets with the incorrect configuration. This has had me stumped for 
the last hour.

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

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

[Touch-packages] [Bug 1882481] [NEW] A dialog box stays on desktop and does not go away

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Upon rebooting, I get dialog box

Authentication Required

Authentication is required to start 'cups.service'.

I can type in the password and click Authenticate, but then nothing
happens. I can't see under the box. I can't move the box, can't cancel
the dialog.

But, I can click on where I know the underneath icon to be and that
click is accepted and the program in question runs. It appears the
display manager does not remove the image after it is done with the
dialog.


I have recently done a clean install of 20.04.


There is a screenshot in this Stack Exchange post:
https://askubuntu.com/questions/1242999/dialog-box-does-not-accept-input-stays-on-top-and-hides-everything-under-it-ub

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun  7 23:10:43 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 amdgpu, 3.3-19, 5.4.0-31-generic, x86_64: installed
 amdgpu, 3.3-19, 5.4.0-33-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA 
controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 [1462:8a92]
InstallationDate: Installed on 2020-05-12 (26 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: System manufacturer System Product Name
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=ebb08f84-7501-4461-a5c4-c69c3c25d9b0 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0804
dmi.board.asset.tag: Default string
dmi.board.name: ROG ZENITH EXTREME
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0804:bd11/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx: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
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu
-- 
A dialog box stays on desktop and does not go away
https://bugs.launchpad.net/bugs/1882481
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1880640] Re: unable to create '/bin/systemd-hwdb.dpkg-new' (while processing './bin/systemd- hwdb'): Operation not permitted

[Gigalo_CA]

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

** This bug has been marked a duplicate of bug 1874887
   package udev 245.4-4ubuntu3 failed to install/upgrade: installed udev 
package post-installation script subprocess returned error exit status 1

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

Title:
  unable to create '/bin/systemd-hwdb.dpkg-new' (while processing
  './bin/systemd- hwdb'): Operation not permitted

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04
  Kernel 5.4.0-31-generic

  apt upgrade failed.  Cannot clear the error.

  Ran apt --fix-broken install as suggested and the following error fell
  through.

  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
    udev
  The following packages will be upgraded:
    udev
  1 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
  Need to get 0 B/1,362 kB of archives.
  After this operation, 1,024 B of additional disk space will be used.
  Do you want to continue? [Y/n]
  (Reading database ... 229440 files and directories currently installed.)
  Preparing to unpack .../udev_245.4-4ubuntu3.1_amd64.deb ...
  Unpacking udev (245.4-4ubuntu3.1) over (245.4-4ubuntu3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/udev_245.4-4ubuntu3.1_amd
  64.deb (--unpack):
   unable to create '/bin/systemd-hwdb.dpkg-new' (while processing 
'./bin/systemd-
  hwdb'): Operation not permitted
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/udev_245.4-4ubuntu3.1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Following running apt --fix-broken install whoopsie
  The following packages have unmet dependencies:
   udev : Depends: libudev1 (= 245.4-4ubuntu3) but 245.4-4ubuntu3.1 is to be 
installed

  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages
  (or specify a solution).

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

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

[Touch-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

[Daniel van Vugt]

The upstream bug mentions:

> When gdm is configured with AutomaticLogin, restarting accounts-
daemon.service causes consumers to crash

so it might be possible to verify that way.

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

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

Status in accountsservice:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Fix Committed
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  [ Description ]

  When accountsservice's daemon is restarted - particularly when there
  is a user configured for auto login - it can cause code using its
  library to crash. This is bad because gnome-shell is one of those
  users which crashes.

  [ QA ]

  Configure a user for automatic login in gnome-shell.

  Update to this SRU, and then *restart your system*. The crash is in
  the library part, and so you will still see it if programs loaded the
  buggy version. Restarting is the easiest way to make sure you're not
  on it.

  Restart accounts-daemon.service (sudo systemctl restart accounts-
  daemon.service) a few times, leaving several seconds between each
  attempt.

  See that it crashes if you don't have this SRU, and doesn't if you do
  have it.

  ---

  Test that fast user switching still works properly.

  ---

  Take a look at the error reports listed below and hopefully see them
  not occurring (barring the usual noise) with the SRU.

  [ Regression potential ]

  We think this is safe - it tells clients that the daemon is away when
  it quits, and is back when it comes back. They should get appropriate
  signals to indicate this. Nevertheless, these signals are sent when
  they weren't before now, so that could cause problems. Watch out for
  errors creeping up with this SRU.

  We wondered upstream whether some more protections might be needed.
  I'm thinking that those should be *additional* safety rails around
  this fix, but it could actually be that more is needed and this fix
  isn't complete.

  [ Original report ]

  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1843982/+subscriptions

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

[Touch-packages] [Bug 1864287] Re: pulseaudio still trying to reproduce audio to HDMI without the HDMI cable connected

[Daniel van Vugt]

The bug automatically closed because we received no response to comment
#1. Please follow the instructions in comment #1 and in comment #5.

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

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

Title:
  pulseaudio still trying to reproduce audio to HDMI without the HDMI
  cable connected

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Yesterday I was using the HDMI cable to duplicate the monitor in the
  tv and play sound with the tv by selecting HDMI exit sound in ubuntu
  settings.

  With the pc turned off I removed the HDMI from the tv but ubuntu
  doesn't automatically set the exit sound to the default till in the
  settings there is only that option and till I selected it, ubuntu was
  still trying to reproduce the audio via HDMI...

  Also rebooting the system the problem persists.

  Also by reloading pulseaudio the problem persists.

  The only solution was installing a third-party program to switch
  correctly to the default audio exit...

  lsb_release -rd:
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  apt-cache policy pulseaudio:
  pulseaudio:
Installato: 1:11.1-1ubuntu7.2
Candidato:  1:11.1-1ubuntu7.4
Tabella versione:
   1:11.1-1ubuntu7.4 500
  500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   *** 1:11.1-1ubuntu7.2 100
  100 /var/lib/dpkg/status
   1:11.1-1ubuntu7 500
  500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

[Touch-packages] [Bug 1560094] Re: Starting bluez service is denied

[Daniel van Vugt]

In progress?

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

** Changed in: bluez (Ubuntu)
 Assignee: Scott Sweeny (ssweeny) => (unassigned)

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

Title:
  Starting bluez service is denied

Status in bluez package in Ubuntu:
  Incomplete

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

  
  Denials:

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

  If trying to start bluetootctl:

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

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

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

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

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

[Touch-packages] [Bug 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()

[Daniel van Vugt]

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: gnome-shell (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: fixed-in-3.36.4

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

Title:
  gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from deep_count_more_files_callback()

Status in GNOME Shell:
  Unknown
Status in glib2.0 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  gnome-shell-hotplug-sniffer crashes when attaching some device that
  may have files with unknown content type

  [ Test case ]

  - Plug a media, but it's not yet known which kind of files cause this issue,
so we should just monitor the e.u.c crash:
https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9

  [ Regression potential ]

  - No valid application for opening a media is shown by gnome-shell

  ---

  This is for 3.34:

  https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec

  ---

  Happened during normal use of the desktop.

  ProblemType: CrashDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 29 19:51:58 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  InstallationDate: Installed on 2020-01-25 (35 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax
   PC (0x7f5f54fa6444) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1865300/+subscriptions

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

[Touch-packages] [Bug 1882473] Re: test bug

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => New

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

Title:
  test bug

Status in systemd:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  test upstream bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1882473/+subscriptions

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

[Touch-packages] [Bug 1882473] Re: test bug

[Dimitri John Ledkov]

yeah, there is now ability to add url to upstream github issue.

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

Title:
  test bug

Status in systemd:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  test upstream bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1882473/+subscriptions

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

[Touch-packages] [Bug 1882473] [NEW] test bug

[Dimitri John Ledkov]

Public bug reported:

test upstream bug

** Affects: systemd
 Importance: Unknown
 Status: New

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

** Bug watch added: github.com/systemd/systemd/issues #16090
   https://github.com/systemd/systemd/issues/16090

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/16090
   Importance: Unknown
   Status: Unknown

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

Title:
  test bug

Status in systemd:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  test upstream bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1882473/+subscriptions

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

[Touch-packages] [Bug 1882466] [NEW] mythtv frontend crash when calling glClear in iris driver

[Ken]

Public bug reported:

on startup, mythfrontend crashes repeatedly when calling glClear - the 
following traceback:
Core was generated by `/usr/bin/mythfrontend.real'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f9495ca0838 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
[Current thread is 1 (Thread 0x7f9551e59940 (LWP 4164))]
(gdb) bt
#0  0x7f9495ca0838 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#1  0x7f9495ca2ebf in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#2  0x7f9495e65de4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#3  0x7f9495c7ce5d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4  0x7f9495c7da95 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#5  0x7f94952bc774 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#6  0x7f955f79e713 in QOpenGLFunctions::glClear (this=0x555cb36e8160, 
mask=16384)
at /usr/include/x86_64-linux-gnu/qt5/QtGui/qopenglfunctions.h:628
#7  0x7f955f798090 in MythRenderOpenGL::ClearFramebuffer (
this=0x555cb36e8150) at opengl/mythrenderopengl.cpp:801
#8  0x7f955f78a3f2 in MythOpenGLPainter::Begin (this=0x555cb398dac0, 
Parent=0x555cb399d1d0) at opengl/mythpainteropengl.cpp:136

I can work around this problem with this:
export MESA_LOADER_DRIVER_OVERRIDE=i965
(then running mythfrontend works fine)

sorry for the lack of debug symbols in iris_dri.so
if there is a .deb around with a debug version i can generate the traceback 
again
not sure if the problem belongs to iris_dri.so or to mythfrontend but I put it 
here due to the workaround.


$ lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04

$ apt-cache policy libgl1-mesa-dri
libgl1-mesa-dri:
  Installed: 20.0.4-2ubuntu1
  Candidate: 20.0.4-2ubuntu1
  Version table:
 *** 20.0.4-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

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

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

Title:
  mythtv frontend crash when calling glClear in iris driver

Status in mesa package in Ubuntu:
  New

Bug description:
  on startup, mythfrontend crashes repeatedly when calling glClear - the 
following traceback:
  Core was generated by `/usr/bin/mythfrontend.real'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f9495ca0838 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  [Current thread is 1 (Thread 0x7f9551e59940 (LWP 4164))]
  (gdb) bt
  #0  0x7f9495ca0838 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #1  0x7f9495ca2ebf in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #2  0x7f9495e65de4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #3  0x7f9495c7ce5d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #4  0x7f9495c7da95 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #5  0x7f94952bc774 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #6  0x7f955f79e713 in QOpenGLFunctions::glClear (this=0x555cb36e8160, 
  mask=16384)
  at /usr/include/x86_64-linux-gnu/qt5/QtGui/qopenglfunctions.h:628
  #7  0x7f955f798090 in MythRenderOpenGL::ClearFramebuffer (
  this=0x555cb36e8150) at opengl/mythrenderopengl.cpp:801
  #8  0x7f955f78a3f2 in MythOpenGLPainter::Begin (this=0x555cb398dac0, 
  Parent=0x555cb399d1d0) at opengl/mythpainteropengl.cpp:136

  I can work around this problem with this:
  export MESA_LOADER_DRIVER_OVERRIDE=i965
  (then running mythfrontend works fine)

  sorry for the lack of debug symbols in iris_dri.so
  if there is a .deb around with a debug version i can generate the traceback 
again
  not sure if the problem belongs to iris_dri.so or to mythfrontend but I put 
it here due to the workaround.

  
  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  $ apt-cache policy libgl1-mesa-dri
  libgl1-mesa-dri:
Installed: 20.0.4-2ubuntu1
Candidate: 20.0.4-2ubuntu1
Version table:
   *** 20.0.4-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1882453] [NEW] GUI blanks after long period of use

[Chris]

Public bug reported:

GUI screen goes blank with a right click on the desktop or a click on
the power button. The entire systems seems to slow too, with CPU
utilization reaching 100% at a consistent interval. This has happened
twice already after a long period of idle or when conducting many
actions with several applications. Not sure if any of it is causation
given its only happened twice and I can't replicate the problem
consistently. If you need further information reach me at
clmora...@pm.me.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41
Uname: Linux 5.4.0-34-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:06:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun  7 15:00:40 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GM204 [GeForce GTX 970] [3842:2974]
InstallationDate: Installed on 2020-05-20 (17 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: MSI MS-7885
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic 
root=UUID=40367ef8-089b-4ef9-9b43-d538f9b52b3d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/20/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.80
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X99A SLI PLUS(MS-7885)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd03/20/2015:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7885
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/1882453

Title:
  GUI blanks after long period of use

Status in xorg package in Ubuntu:
  New

Bug description:
  GUI screen goes blank with a right click on the desktop or a click on
  the power button. The entire systems seems to slow too, with CPU
  utilization reaching 100% at a consistent interval. This has happened
  twice already after a long period of idle or when conducting many
  actions with several applications. Not sure if any of it is causation
  given its only happened twice and I can't replicate the problem
  consistently. If you need further information reach me at
  clmora...@pm.me.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41
  Uname: Linux 5.4.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:06:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: sk

[Touch-packages] [Bug 1880041] Re: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later

[Mister Hippo]

can also confirm that this affects my "AMD Ryzen 5 3400G" on 18.04 with
"linux-image-5.3.0-53-generic".

rolling back to "linux-image-5.3.0-51-generic" also solves it for me

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

Title:
  Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel
  versions 5.3.0-52 and later

Status in DRI:
  Unknown
Status in libdrm package in Ubuntu:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Confirmed

Bug description:
  When booting up Ubuntu 18.04 with a kernel version of 5.3.0-52 or
  later (including 5.3.0-53), everything seems to be working as usual.
  However, when I shutdown, the system will only soft shutdown, with the
  CPU still running at full power, forcing me to hold down the power
  button to fully power off affected systems. If I reboot, it will cause
  the system to hang and not respond. Either way, a hard reset or
  poweroff will be required, and this is not an option for systems being
  remotely accessed. It is not possible for me to collect kernel logs at
  this point, unless something wrong is happening in those kernel
  versions before the actual shutdown.

  It is possible that this may also occur on Ubuntu 20.04 with kernel
  versions 5.4.0-29 and later, but I have not yet tested this out. This
  problem is occurring on both my desktop and laptop computers which
  respectively are:

  * AsRock B450 Pro4 with AMD Ryzen 3 3200G APU
  * Lenovo ThinkPad A485 with AMD Ryzen 5 Pro 2500U mobile APU

  In the meantime, I am stuck on kernel version 5.3.0-51, as that is the
  last working 5.3.x kernel version offered in the standard Ubuntu
  repositories that doesn't have this problem, without me having to use
  PPAs. I don't know if this problem also occurs on systems with Intel
  CPUs, as I don't own any recently-made system (last 3 years from 2017)
  with such CPUs to test if this problem occurs on them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions

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

[Touch-packages] [Bug 1882445] [NEW] Applications read ICC profile always from primary monitor

[Usamm]

Public bug reported:

Ubuntu 20.04
NVidia properietary drivers
2 monitors, each with its own ICC profile loaded
Monitors are configured in "Join Displays" mode.

Image Viewer and Chrome always use the color profile of whatever monitor
is set as the Primary Display, regardless of which monitor they're on.
Refreshing the window or creating new tabs doesn't help.

Since one of my monitors is wide gamut and the other is standard gamut,
the issue is extremely glaring, leading to extremely oversaturated
colors on the wide gamut monitor if the standard gamut monitor is
primary, or extremely undersaturated colors on the standard gamut
monitor if the wide gamut one is set as primary.

Expected behaviour:
All color-managed applications apply the ICC profile of the monitor they're 
currently displayed on, as soon as they're dragged on it.
I tested that Chrome on Windows 10 uses this behaviour.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:06:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun  7 18:23:54 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GM204 [GeForce GTX 970] 
[1462:3160]
InstallationDate: Installed on 2020-06-07 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Gigabyte Technology Co., Ltd. B450 GAMING X
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=3a087e9b-0230-4c3c-93fa-663dcecc108d ro quiet
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/27/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F50
dmi.board.asset.tag: Default string
dmi.board.name: B450 GAMING X
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.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450GAMINGX:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450GAMINGX:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: B450 GAMING X
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/1882445

Title:
  Applications read ICC profile always from primary monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04
  NVidia properietary drivers
  2 monitors, each with its own ICC profile loaded
  Monitors are configured in "Join Displays" mode.

  Image Viewer and Chrome always use the color profile of whatever
  monitor is set as the Primary Display, regardless of which monitor
  they're on. Refreshing the window or creating new tabs doesn't help.

  Since one of my monitors is wide gamut and the other is standard
  gamut, the issue is extremely glaring, leading to extremely
  oversaturated colors on the wide gamut monitor if the standard gamut
  monitor is primary, or extremely undersaturated colors on the standard
  gamut monitor if the wide gamut one is set as primary.

  Expected behaviour:
  All color-managed applications apply the ICC profile of the monitor they're 
currently dis

[Touch-packages] [Bug 1882440] Re: BadLength (poly request too large or internal Xlib length error) when using xfreerdp

[Hans-Peter]

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1882440/+attachment/5381249/+files/CurrentDmesg.txt

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

Title:
  BadLength (poly request too large or internal Xlib length error) when
  using xfreerdp

Status in xorg package in Ubuntu:
  New

Bug description:
  when using xfreerdp with Windows 10 and using the a screen capture tool on 
the remote host (windows 10) xfreerdp consistently fails with BadLength X 
error. 
  I reported this also to xfreerdp, where it was designated as potential 
internal error in X/Xlib.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  7 18:27:46 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.6, 5.4.0-31-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev ef) (prog-if 00 [VGA 
controller])
 Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353]
  InstallationDate: Installed on 2020-05-14 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. MS-7B89
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=4022b63e-4e73-4175-99a6-641a1284aeb3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.70
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M MORTAR MAX (MS-7B89)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.70:bd04/21/2020:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B89
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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

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

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

[Touch-packages] [Bug 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]

[protofik]

Happens to me as well. Running Ubuntu 20.04 with package isc-dhcp-server
4.4.1-2.1ubuntu5 I am trying to setup failover pair between RaspberryPi4
and Hyper-V VM. Restarting service on both servers at the same time will
cause one of them to fail.

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

Title:
  isc-dhcp-server crashing constantly [Ubuntu 20.04]

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  isc-dhcp-server crashing constantly (sometimes within seconds or minutes, 
sometimes within hours) with the following error messages:
  Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service.
  Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ??
  Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ??
  Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ??
  Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ??
  Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ??
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872106/+subscriptions

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

[Touch-packages] [Bug 1882440] [NEW] BadLength (poly request too large or internal Xlib length error) when using xfreerdp

[Hans-Peter]

Public bug reported:

when using xfreerdp with Windows 10 and using the a screen capture tool on the 
remote host (windows 10) xfreerdp consistently fails with BadLength X error. 
I reported this also to xfreerdp, where it was designated as potential internal 
error in X/Xlib.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun  7 18:27:46 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.6, 5.4.0-31-generic, x86_64: installed
 virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev ef) (prog-if 00 [VGA 
controller])
   Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353]
InstallationDate: Installed on 2020-05-14 (23 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Micro-Star International Co., Ltd. MS-7B89
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=4022b63e-4e73-4175-99a6-641a1284aeb3 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/21/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.70
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450M MORTAR MAX (MS-7B89)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.70:bd04/21/2020:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B89
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/1882440

Title:
  BadLength (poly request too large or internal Xlib length error) when
  using xfreerdp

Status in xorg package in Ubuntu:
  New

Bug description:
  when using xfreerdp with Windows 10 and using the a screen capture tool on 
the remote host (windows 10) xfreerdp consistently fails with BadLength X 
error. 
  I reported this also to xfreerdp, where it was designated as potential 
internal error in X/Xlib.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  7 18:27:46 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.6, 5.4.0-31-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev ef) (prog-if 00 [VGA 
controller])
 Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353]
  InstallationDate: Installed on 2020-05-14 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Micro-Star International Co., Ltd. MS-7B89
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=4022b6

[Touch-packages] [Bug 1834566] Re: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298

[Krishna Sai Chintala]

Same with me, tried in 18.04 and 20.04 versions. No sound in internal
speakers and in 3.5mm audio jack but works with bluetooth headset and
type-c earphones.

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

Title:
  Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel
  - Realtek ALC298

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Unable to get system speakers working running 19.04.  At max volume,
  sound is barely perceptible through headphones.  Pavucontrol shows
  sounds is present, but no amount of adjustments makes a difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert 3355 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun 28 00:44:13 2019
  InstallationDate: Installed on 2019-06-05 (22 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [930MBE, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02AHK.029.190425.PS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP930MBE-K04US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9872A0S-C01-G001-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02AHK.029.190425.PS:bd04/25/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn930MBE:pvrP02AHK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930MBE-K04US:rvrSGL9872A0S-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:
  dmi.product.family: Notebook 9 Series
  dmi.product.name: 930MBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHK
  dmi.product.version: P02AHK
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834566/+subscriptions

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

[Touch-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu6

---
pulseaudio (1:13.99.1-1ubuntu6) groovy; urgency=medium

  * debian/patches/git_config_upgrade.patch:
 -stream-restore: Forget pre-14.0 stream routing, old configurations are
  incompatible and create routing issues where e.g the speaker despite
  having headset selected (lp: #1866194)
  * debian/rules:
- enable --enable-stream-restore-clear-old-devices
  * debian/rules:
- don't let tests fail build on riscv

 -- Sebastien Bacher   Wed, 03 Jun 2020 17:28:51
+0200

** Changed in: pulseaudio (Ubuntu Groovy)
   Status: In Progress => Fix Released

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

Title:
  External audio device shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker, or none at
  all.

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

  1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
  2. Make sure it's the one selected as "Output device"
  3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  5. Try to switch back to the BT device and click Test
  -> same result as in step 3

  Tested with 2 different BT devices (one headset and one speaker) as
  well as a USB audio interface (Zoom H2N microphone).

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1866194/+subscriptions

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

[Touch-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu6

---
pulseaudio (1:13.99.1-1ubuntu6) groovy; urgency=medium

  * debian/patches/git_config_upgrade.patch:
 -stream-restore: Forget pre-14.0 stream routing, old configurations are
  incompatible and create routing issues where e.g the speaker despite
  having headset selected (lp: #1866194)
  * debian/rules:
- enable --enable-stream-restore-clear-old-devices
  * debian/rules:
- don't let tests fail build on riscv

 -- Sebastien Bacher   Wed, 03 Jun 2020 17:28:51
+0200

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

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
   State: RUNNING
   Name: alsa_input.pci-_00_1f.3.analog-stereo
   Description: Built-in Audio Analog Stereo
   Driver: module-alsa-card.c
   Sample Specification: s16le 2ch 44100Hz
   Channel Map: front-left,front-right
   Owner Module: 7
   Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

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

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

[Touch-packages] [Bug 1877102] Re: snap policy module can be unloaded, circumventing audio recording restrictions for snaps

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu6

---
pulseaudio (1:13.99.1-1ubuntu6) groovy; urgency=medium

  * debian/patches/git_config_upgrade.patch:
 -stream-restore: Forget pre-14.0 stream routing, old configurations are
  incompatible and create routing issues where e.g the speaker despite
  having headset selected (lp: #1866194)
  * debian/rules:
- enable --enable-stream-restore-clear-old-devices
  * debian/rules:
- don't let tests fail build on riscv

 -- Sebastien Bacher   Wed, 03 Jun 2020 17:28:51
+0200

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

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

Title:
  snap policy module can be unloaded, circumventing audio recording
  restrictions for snaps

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  This collates information about a security vulnerability discussed in
  email.  It has been assigned CVE-2020-11931.

  Ubuntu's PulseAudio package is shipped with a custom "module-snap-
  policy" module intended to restrict snap confined clients from
  recording audio unless they have the "audio-record" plug connected.
  However, it does not restrict access to the "PA_COMMAND_UNLOAD_MODULE"
  command.

  This allows a snap that has only plugged "audio-playback" to request
  that PulseAudio unload the security policy module, which in turn makes
  it possible to record audio.

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

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

[Touch-packages] [Bug 1808710] Re: !xcb_xlib_threads_sequence_lost error with GTK2 applications

[Tycho Kirchner]

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

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

Title:
  !xcb_xlib_threads_sequence_lost error with GTK2 applications

Status in gtk+2.0 package in Ubuntu:
  Confirmed
Status in libx11 package in Ubuntu:
  New

Bug description:
  GTK2 applications randomly crash or freeze with error like:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  : ../../src/xcb_io.c:263: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.

  where  is the name of the executable, e.g. audacious,
  soffice.bin, etc.

  RELATED BUGS
  LibreOffice: 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1801161
  PCManFM: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984
  Audacious: https://redmine.audacious-media-player.org/issues/798
  FreeCAD: https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1754084
  ClawsMail: 
https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4203

  OTHER APPLICATIONS
  SpaceFM, Pidgin, GPicView and GIMP appear to have similar problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+subscriptions

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

[Touch-packages] [Bug 1782984] Re: PCManFM freezes with Assertion `!xcb_xlib_threads_sequence_lost' failed when clicking on a file or folder in 18.04

[Tycho Kirchner]

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

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

Title:
  PCManFM freezes with Assertion `!xcb_xlib_threads_sequence_lost'
  failed when clicking on a file or folder in 18.04

Status in libx11 package in Ubuntu:
  New
Status in pcmanfm package in Ubuntu:
  Triaged

Bug description:
  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  
  Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) 
seem to have the same problems. This is probably at least rooted in a GTK2 bug:
  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710

  To further assert this, note that there is a SpaceFM file manager that
  is available in GTK2 and GTK3. The GTK2 version displays the behavior.
  The GTK3 version does not. Same with LibreOffice.

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

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

[Touch-packages] [Bug 1808710] Re: !xcb_xlib_threads_sequence_lost error with GTK2 applications

[Tycho Kirchner]

Apparently it's a bug in libx11, which persisted for a long time but
became much more likely with an update in libxcb.
Please see the still open merge request/patch at

https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34

Further reading:
This bug report (as it turned out now, it's probably *not*
a bug in gtk though):
https://gitlab.gnome.org/GNOME/gtk/-/issues/2767


** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #2767
   https://gitlab.gnome.org/GNOME/gtk/-/issues/2767

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

Title:
  !xcb_xlib_threads_sequence_lost error with GTK2 applications

Status in gtk+2.0 package in Ubuntu:
  Confirmed

Bug description:
  GTK2 applications randomly crash or freeze with error like:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  : ../../src/xcb_io.c:263: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.

  where  is the name of the executable, e.g. audacious,
  soffice.bin, etc.

  RELATED BUGS
  LibreOffice: 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1801161
  PCManFM: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984
  Audacious: https://redmine.audacious-media-player.org/issues/798
  FreeCAD: https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1754084
  ClawsMail: 
https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4203

  OTHER APPLICATIONS
  SpaceFM, Pidgin, GPicView and GIMP appear to have similar problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+subscriptions

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

[Touch-packages] [Bug 1882423] [NEW] [XPS L401X, Realtek ALC665, Black Headphone Out, Left] fails after a while

[moolchad versha]

Public bug reported:

sound stops after a while.plun in another start again for some time

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  moolchand   1232 F pulseaudio
 /dev/snd/controlC0:  moolchand   1232 F pulseaudio
 /dev/snd/pcmC0D1p:   moolchand   1232 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Sun Jun  7 14:09:59 2020
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel MID
Symptom_Jack: Black Headphone Out, Left
Symptom_PulseAudioLog: Jun 07 14:02:25 moolchand dbus-daemon[797]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.28' (uid=1000 pid=1232 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
Symptom_Type: Sound works for a while, then breaks
Title: [XPS L401X, Realtek ALC665, Black Headphone Out, Left] fails after a 
while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/22/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 069C9F
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd12/22/2010:svnDellInc.:pnXPSL401X:pvrNotSpecified:rvnDellInc.:rn069C9F:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: XPS L401X
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal

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

Title:
  [XPS L401X, Realtek ALC665, Black Headphone Out, Left] fails after a
  while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  sound stops after a while.plun in another start again for some time

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  moolchand   1232 F pulseaudio
   /dev/snd/controlC0:  moolchand   1232 F pulseaudio
   /dev/snd/pcmC0D1p:   moolchand   1232 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Jun  7 14:09:59 2020
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Black Headphone Out, Left
  Symptom_PulseAudioLog: Jun 07 14:02:25 moolchand dbus-daemon[797]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.28' (uid=1000 pid=1232 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
  Symptom_Type: Sound works for a while, then breaks
  Title: [XPS L401X, Realtek ALC665, Black Headphone Out, Left] fails after a 
while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 069C9F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd12/22/2010:svnDellInc.:pnXPSL401X:pvrNotSpecified:rvnDellInc.:rn069C9F:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS L401X
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1882423/+subscriptions

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

[Touch-packages] [Bug 1875796] Re: HP Envy 5530 printer/scanner does not work

[Roland S.]

Try workaround:

sudo apt purge ippusbxd

Source: Kellerkind_2009, https://forum.ubuntuusers.de/post/9151988/

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

Title:
  HP Envy 5530 printer/scanner does not work

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 20.04 LTS
  see troubleshoot.txt please

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 29 08:15:00 2020
  InstallationDate: Installed on 2020-04-28 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat:
   device for ENVY_5530_series_CN4A5310HJ067B_: 
implicitclass://ENVY_5530_series_CN4A5310HJ067B_/
   device for HP-ENVY-5530-series: 
hp:/usb/ENVY_5530_series?serial=CN4A5310HJ067B
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c52e Logitech, Inc. MK260 Wireless Combo Receiver
   Bus 001 Device 003: ID 03f0:c311 HP, Inc ENVY 5530 series
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-ENVY-5530-series.ppd', 
'/etc/cups/ppd/ENVY_5530_series_CN4A5310HJ067B_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP-ENVY-5530-series.ppd: Permission denied
   grep: /etc/cups/ppd/ENVY_5530_series_CN4A5310HJ067B_.ppd: Permission denied
  ProcEnviron:
   LANGUAGE=nl_BE:nl
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=77c5fdfc-4b0d-48ce-93d9-8aba51f17f9b ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-A/M.2
  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.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2: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/cups/+bug/1875796/+subscriptions

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