[Touch-packages] [Bug 1931104] Re: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-proposed

[Christian Ehrhardt ]

Without the recent PPC fixes s390x was broken as well, so I'm not saying "the 
ppc fixes broke s390x":
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-service-4577/impish/s390x/d/dogtag-pki/20210608_073451_f187d@/log.gz

Instead there seems to be a new crash affecting s390x that has to be
looked at to be able to rev up the nss version.

Tagging server-next and subscribing the team as this is no more a +1 task.
If we are lucky the always dilligent locutus (who often merges nss) might come 
by and give it a short as well when we have latter nss versions.

** Tags added: server-next

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

Title:
  Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-
  proposed

Status in nss package in Ubuntu:
  New

Bug description:
  The test of dogtag-pki is failing on the nss 3.63 that is in impish proposed.
  Example:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/d/dogtag-pki/20210516_212719_e6522@/log.gz

  Bad:
  Installing CA into /var/lib/pki/pki-tomcat.
  Installation failed: ('Connection aborted.', RemoteDisconnected('Remote end 
closed connection without response'))
  ERROR: ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote 
end closed connection without response'))
    File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in 
main
  scriptlet.spawn(deployer)
    File 
"/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py",
 line 995, in spawn
  cert = deployer.setup_cert(client, tag)
    File "/usr/lib/python3/dist-packages/pki/server/deployment/__init__.py", 
line 355, in setup_cert
  return client.setupCert(request)
    File "/usr/lib/python3/dist-packages/pki/system.py", line 389, in setupCert
  response = self.connection.post(
    File "/usr/lib/python3/dist-packages/pki/client.py", line 55, in wrapper
  return func(self, *args, **kwargs)
    File "/usr/lib/python3/dist-packages/pki/client.py", line 293, in post
  r = self.session.post(
    File "/usr/lib/python3/dist-packages/requests/sessions.py", line 590, in 
post
  return self.request('POST', url, data=data, json=json, **kwargs)
    File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in 
request
  resp = self.send(prep, **send_kwargs)
    File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in 
send
  r = adapter.send(request, **kwargs)
    File "/usr/lib/python3/dist-packages/requests/adapters.py", line 498, in 
send
  raise ConnectionError(err, request=request)
   CA spawn failed:

  Good:
  nstalling CA into /var/lib/pki/pki-tomcat.
  Notice: Trust flag u is set automatically if the private key is present.
  /usr/lib/python3/dist-packages/urllib3/connection.py:455: 
SubjectAltNameWarning: Certificate for i-dogtag has no `subjectAltName`, 
falling back to check for a `commonName` for now. This feature is being removed 
by major browsers and deprecated by RFC 2818. (See 
https://github.com/urllib3/urllib3/issues/497 for details.)
    warnings.warn(

  ==
  INSTALLATION SUMMARY
  ==
  ...

  The good test above was with:
  ii  libnss3:s390x2:3.61-1ubuntu2  s390xNetwork Security 
Service libraries
  ii  389-ds-base1.4.4.11-2  s390x389 Directory Server suite - 
server

  Worth to know, the good case test still fails later on with:
  IOException: SocketException cannot write on socket: Failed to write to 
socket: (-5938) Encountered end of file.
  ERROR: CalledProcessError: Command '['pki', '-d', 
'/etc/pki/pki-tomcat/alias', '-f', '/etc/pki/pki-tomcat/password.conf', '-U', 
'https://i-dogtag:8443', 'securitydomain-join', '--session', 
'4717921475119312283', '--type', 'TKS', '--hostname', 'i-dogtag', 
'--unsecure-port', '8080', '--secure-port', '8443', 'TKS i-dogtag 8443']' 
returned non-zero exit status 255.
    File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in 
main
  scriptlet.spawn(deployer)
    File 
"/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py",
 line 1038, in spawn
  subsystem.join_security_domain(
    File "/usr/lib/python3/dist-packages/pki/server/subsystem.py", line 1201, 
in join_security_domain
  subprocess.check_call(cmd)
    File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
  raise CalledProcessError(retcode, cmd)
  Installation failed: Command failed: pki -d /etc/pki/pki-tomcat/alias -f 
/etc/pki/pki-tomcat/password.conf -U https://i-dogtag:8443 securitydomain-join 
--session 4717921475119312283 --type TKS --hostname i-dogtag --unsecure-port 
8080 --secure-port 8443 T

[Touch-packages] [Bug 1931104] Re: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-proposed

[Christian Ehrhardt ]

Reproducible, ppc64 is fixed and s390x broken by the latest 3.66 + fixes from 
master.
Links:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-service-4577/impish/s390x/d/dogtag-pki/20210609_065306_2e698@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-service-4577/impish/s390x/d/dogtag-pki/20210609_121610_a71da@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-service-4577/impish/s390x/d/dogtag-pki/20210609_124415_d071b@/log.gz

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

Title:
  Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-
  proposed

Status in nss package in Ubuntu:
  New

Bug description:
  The test of dogtag-pki is failing on the nss 3.63 that is in impish proposed.
  Example:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/d/dogtag-pki/20210516_212719_e6522@/log.gz

  Bad:
  Installing CA into /var/lib/pki/pki-tomcat.
  Installation failed: ('Connection aborted.', RemoteDisconnected('Remote end 
closed connection without response'))
  ERROR: ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote 
end closed connection without response'))
    File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in 
main
  scriptlet.spawn(deployer)
    File 
"/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py",
 line 995, in spawn
  cert = deployer.setup_cert(client, tag)
    File "/usr/lib/python3/dist-packages/pki/server/deployment/__init__.py", 
line 355, in setup_cert
  return client.setupCert(request)
    File "/usr/lib/python3/dist-packages/pki/system.py", line 389, in setupCert
  response = self.connection.post(
    File "/usr/lib/python3/dist-packages/pki/client.py", line 55, in wrapper
  return func(self, *args, **kwargs)
    File "/usr/lib/python3/dist-packages/pki/client.py", line 293, in post
  r = self.session.post(
    File "/usr/lib/python3/dist-packages/requests/sessions.py", line 590, in 
post
  return self.request('POST', url, data=data, json=json, **kwargs)
    File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in 
request
  resp = self.send(prep, **send_kwargs)
    File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in 
send
  r = adapter.send(request, **kwargs)
    File "/usr/lib/python3/dist-packages/requests/adapters.py", line 498, in 
send
  raise ConnectionError(err, request=request)
   CA spawn failed:

  Good:
  nstalling CA into /var/lib/pki/pki-tomcat.
  Notice: Trust flag u is set automatically if the private key is present.
  /usr/lib/python3/dist-packages/urllib3/connection.py:455: 
SubjectAltNameWarning: Certificate for i-dogtag has no `subjectAltName`, 
falling back to check for a `commonName` for now. This feature is being removed 
by major browsers and deprecated by RFC 2818. (See 
https://github.com/urllib3/urllib3/issues/497 for details.)
    warnings.warn(

  ==
  INSTALLATION SUMMARY
  ==
  ...

  The good test above was with:
  ii  libnss3:s390x2:3.61-1ubuntu2  s390xNetwork Security 
Service libraries
  ii  389-ds-base1.4.4.11-2  s390x389 Directory Server suite - 
server

  Worth to know, the good case test still fails later on with:
  IOException: SocketException cannot write on socket: Failed to write to 
socket: (-5938) Encountered end of file.
  ERROR: CalledProcessError: Command '['pki', '-d', 
'/etc/pki/pki-tomcat/alias', '-f', '/etc/pki/pki-tomcat/password.conf', '-U', 
'https://i-dogtag:8443', 'securitydomain-join', '--session', 
'4717921475119312283', '--type', 'TKS', '--hostname', 'i-dogtag', 
'--unsecure-port', '8080', '--secure-port', '8443', 'TKS i-dogtag 8443']' 
returned non-zero exit status 255.
    File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in 
main
  scriptlet.spawn(deployer)
    File 
"/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py",
 line 1038, in spawn
  subsystem.join_security_domain(
    File "/usr/lib/python3/dist-packages/pki/server/subsystem.py", line 1201, 
in join_security_domain
  subprocess.check_call(cmd)
    File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
  raise CalledProcessError(retcode, cmd)
  Installation failed: Command failed: pki -d /etc/pki/pki-tomcat/alias -f 
/etc/pki/pki-tomcat/password.conf -U https://i-dogtag:8443 securitydomain-join 
--session 4717921475119312283 --type TKS --hostname i-dogtag --unsecure-port 
8080 --secure-port 8443 TKS i-dogtag 8443
  Please check pkispawn logs in /var/log/pki/pki-tks-spawn.20210607093926.log

[Touch-packages] [Bug 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)

[Frank Heimes]

Ok, the line that concerns me is:
"
enP53p0s0.171: link pending udev initialization...
"

It looks like systemd-networkd thinks that udev is not done with
enP53p0s0.171 --> "pending", but configuring it with ip works - so could
be networkd or also udevd.

So lets expand the journal output with the udev messages and share it again:
journalctl -b -u systemd-networkd -u systemd-udevd --no-pager

Please can you also share the output of:
apt-cache policy systemd udev netplan.io

Investigations pointed me to:
https://github.com/systemd/systemd/issues/15445#issuecomment-776856604
(changing the interface name at some point could be interesting, too...)

Anyway, I'll mark this bug as affecting systemd now.

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

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

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

Title:
  [Ubuntu 20.4.2]  vLan not getting static IP assigned (on s390x)

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Doing vLAN configuration one of the vLANs is not getting static IP assigned 
when the rest are workin without problems
   
  Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com 
   
  ---uname output---
  Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 
17:29:32 UTC 2021 s390x s390x s390x GNU/Linux
   
  Machine Type = z15 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1)Configure the netplan file as follow:
  root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml

  # This is the network config written by 'subiquity'

  network:

ethernets:

  encdb0:

addresses:

- 11.111.114.213/22

macaddress: 02:76:54:00:00:03

  encdc0:

addresses:

- 11.111.112.213/22

macaddress: 02:76:54:00:00:04

  enP50s3832 :

addresses:

- 11.111.112.214/22

  enP53p0s0:

addresses:

- 11.111.112.215/22

vlans:

  encdb0.160:

id: 160

link: encdb0

mtu: 9000

addresses:

- 192.168.160.53/24

  encdc0.150:

id: 150

link: encdc0

mtu: 9000

addresses:

- 192.168.150.53/24

  enP50s3832.170:

id: 170

link: enP50s3832

mtu: 9000

addresses:

- 192.168.170.53/24

  enP53p0s0.171:

id: 171

link: enP53p0s0

mtu: 9000

addresses:

- 192.168.171.53/24

version: 2

  2)run net plan apply:
  root@ilabg13:~# netplan --debug apply

  ** (generate:59965): DEBUG: 14:55:15.046: Processing input file
  /etc/netplan/00-installer-config.yaml..

  ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass

  ** (generate:59965): DEBUG: 14:55:15.046: Processing input file
  /etc/netplan/01-iscsi-config.yaml..

  ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass

  ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass
  them through a final round of validation

  ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting
  default backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting
  default backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.047: Generating output files..

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  ence0f is not 

[Touch-packages] [Bug 1926548] Re: The gatt protocol has out-of-bounds read that leads to information leakage

[Seth Arnold]

Wonderful, thanks Daniel!

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

Title:
  The gatt protocol has out-of-bounds read that leads to information
  leakage

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Hirsute:
  Fix Released
Status in bluez source package in Impish:
  Fix Released

Bug description:
  I installed the latest bluez 5.53-0ubuntu3 version using apt-get install. It 
seems that this vulnerability was silently fixed in the latest bluez5.8, and 
the cve number was not assigned.
  But this vulnerability now affects the latest ubuntu system
  This vulnerability allows an attacker to remotely obtain most of the contents 
of the heap without authentication.
  The vulnerability code is stored in cli_feat_read_cb, this function does not 
verify the offset parameter
  The vulnerability code is as follows

  gatt-database.c

  1054：static void cli_feat_read_cb(struct gatt_db_attribute *attrib,
unsigned int id, uint16_t offset,
uint8_t opcode, struct bt_att *att,
void *user_data){
  ...
  len = sizeof(state->cli_feat)-offset;
  value = len? &state->cli_feat[offset]: NULL;

  done:
  gatt_db_attribute_read_result(attrib, id, ecode, value, len);

  
  }
  len will become very large due to integer overflow, so that a message of mtu 
(0x90) size will be sent later
  The message content is the buffer pointed to by value, which can be most 
addresses on the heap

  poc is very simple, the core is this line of code

  memcpy(&buf[0],"\x0c\x0b\x00\x0d\x00",5);

  0xc stands for read
  \x0b\x00 represents the handle of the client feature, which can be obtained 
through the find info message, which seems to be 0b by default
  \x0d\x00 is offset0xd

  
  this vulnerability is serious
  I want to apply for a cve number, although this has been silently fixed in 
the latest version

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

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

[Touch-packages] [Bug 1931485] Re: DaVinci Resolve is not identifying my integrated Intel Graphics card

[Daniel van Vugt]

Thanks for the bug report. The attached files seem to show that your
Intel graphics drivers are working properly for Ubuntu. Whatever the
problem is you see in DaVinci Resolve appears to be specific to that
application.


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

** Changed in: ubuntu
   Status: New => Invalid

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

Title:
  DaVinci Resolve is not identifying my integrated Intel Graphics card

Status in Ubuntu:
  Invalid

Bug description:
  In Windows the GPU gets identified automatically but not in Ubuntu
  which is installed on the same system

  My Configuration:

  Laptop: DELL Inspiron 15 5580
  Processor: i5-8265U
  Integrated graphics: Intel UHD Graphics 620

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-55-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 10 00:23:48 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:089d]
  InstallationDate: Installed on 2021-06-06 (3 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Inspiron 5580
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic 
root=UUID=4891d34b-6067-4d2e-b45e-3393d909 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/28/2020
  dmi.bios.release: 2.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.9.0
  dmi.board.name: 0J0XK8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.9.0:bd12/28/2020:br2.9:svnDellInc.:pnInspiron5580:pvr:rvnDellInc.:rn0J0XK8:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5580
  dmi.product.sku: 089D
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1931488] Re: Kubuntu: No more file search results in Krunner or Kickoff after Hirsute Upgrade

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => plasma-workspace (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/1931488

Title:
  Kubuntu: No more file search results in Krunner or Kickoff after
  Hirsute Upgrade

Status in plasma-workspace package in Ubuntu:
  New

Bug description:
  I just upgraded from Kubuntu 20.10 to 21.04 and now I no longer get
  any file search results ("Desktop search") in Krunner or Kickoff
  ("Application Launcher"). For example type "testfile" in Krunner gives
  zero results although there this file in the home directory.

  However baloosearch in the terminal works fine. Desktop search / file
  search is also enabled in the settings for Krunner and in system
  settings.

  If I create a new user account the file search does work. I assume
  that some setting in the home directory must have been changed during
  the upgrade.

  Please let me know which logs or files I could upload that could be of
  use to debug this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Jun  9 20:10:40 2021
  DistUpgraded: 2021-06-06 22:12:52,319 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.18, 5.11.0-18-generic, x86_64: installed
   virtualbox, 6.1.18, 5.8.0-55-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Fujitsu Technology Solutions HD Graphics 630 [1734:121c]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c326 Logitech, Inc. Washable Keyboard K310
   Bus 001 Device 002: ID 046d:c404 Logitech, Inc. TrackMan Wheel
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU ESPRIMO Q556/2
  ProcEnviron:
   LANGUAGE=de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic 
root=UUID=8f3a8bfd-584a-4e11-a2f8-984c6e293255 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to hirsute on 2021-06-06 (2 days ago)
  dmi.bios.date: 02/12/2020
  dmi.bios.release: 1.26
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.26.0 for D3403-U1x
  dmi.board.name: D3403-U1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3403-U1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.26.0forD3403-U1x:bd02/12/2020:br1.26:svnFUJITSU:pnESPRIMOQ556/2:pvr:rvnFUJITSU:rnD3403-U1:rvrS26361-D3403-U1:cvnFUJITSU:ct3:cvr:
  dmi.product.family: ESPRIMO-FTS
  dmi.product.name: ESPRIMO Q556/2
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1931488/+subscriptions

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

[Touch-packages] [Bug 1931387] Re: Ubuntu UI screen image freezes randomly during usage after fresh 21.04 install, suspecting Wayland

[Daniel van Vugt]

Thanks for the bug report. Please run this command to send us additional
system info:

  apport-collect 1931387

Please also follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Tags added: hirsute nouveau

** Package changed: wayland (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 wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1931387

Title:
  Ubuntu UI screen image freezes randomly during usage after fresh 21.04
  install, suspecting Wayland

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Also submitted at: https://askubuntu.com/questions/1344736/ubuntu-ui-
  freezes-randomly-after-fresh-21-04-install-suspecting-wayland

  Let me know if there's any way to collect more useful information if
  there is ever a future crash, or a better place to report.

  I was running 20.10 previously with NVIDIA drivers,

  Then four days ago, I did a clean 21.04 install without installing the
  NVIDIA drivers, and since then the UI has frozen three times on my.

  I am unable to determine exactly what action triggered the freeze.

  The third time, I was just looking at a webpage, I wasn't even
  touching my mouse at that exact moment, and then it just froze.

  I am then unable to see anything move on the screen, including after
  Ctrl + Alt + Fn, the last image just stays fixed.

  The third time was also a bit different.

  A few seconds after freezing, it actually went down to a black
  terminal screen as during boot messages and then I was redirected to
  the login screen, as if I had been logged out.

  I was able to login, my programs were closed, so I was effectively
  logged out.

  Then two Apport windows showed up, and one of them contained several
  references to Xwayland. Under
  `/var/crash/_usr_bin_Xwayland.1000.crash` I see one of them:

  - `ProcCmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth 
/run/user/1000/.mutter-Xwaylandauth.48ZQ40 -listen 4 -listen 5 -displayfd 6 
-initfd 7
  - `StackTraceAddressSignature` contained mentions of Xwayland and 
nouveau_dri.so:

```
StacktraceAddressSignature: 
/usr/bin/Xwayland:6:/usr/lib/x86_64-linux-gnu/libc-2.33.so+864:/usr/bin/Xwayland+13cb40:/usr/bin/Xwayland+14866f:/usr/bin/Xwayland+13b1a7:/usr/lib/x86_64-linux-gnu/libc-2.33.so+864:/usr/lib/x86_64-linux-gnu/libc-2.33.so+749:/usr/lib/x86_64-linux-gnu/libc-2.33.so+123d6:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+25d7:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+2537:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+265f:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+2a77:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+31aa:/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so+93b943:/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so+93bc61:/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so+17cc01
```

  I also checked and I am using Wayland (the default since 21.04
  apparently): https://askubuntu.com/questions/904940/how-can-i-tell-
  if-i-am-running-wayland/1344287#1344287

  Hardware:

  - Lenovo ThinkPad P51
  - NVIDIA Quadro M1200 4GB GDDR5 GPU

  Just after the crash, dmesg contained the following possibly
  interesting lines:

  ```
  [ 9556.450894] nouveau :01:00.0: gr: TRAP ch 3 [00ff8cf000 Xwayland[3831]]
  [ 9556.450907] nouveau :01:00.0: gr: GPC0/TPC2/MP trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp 3c000d [OOR_REG]
  [ 9556.454264] nouveau :01:00.0: gr: TRAP ch 3 [00ff8cf000 Xwayland[3831]]
  [ 9556.454283] nouveau :01:00.0: gr: GPC0/TPC0/MP trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp 3e000d [OOR_REG]
  [ 9556.466339] nouveau :01:00.0: gr: TRAP ch 3 [00ff8cf000 Xwayland[3831]]
  [ 9556.466351] nouveau :01:00.0: gr: GPC0/TPC3/MP trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp 3e000d [OOR_REG]
  [ 9698.230726] nouveau :01:00.0: Xwayland[3831]: failed to idle channel 5 
[Xwayland[3831]]
  [ 9713.230743] nouveau :01:00.0: Xwayland[3831]: failed to idle channel 5 
[Xwayland[3831]]
  [ 9713.231918] nouveau :01:00.0: fifo: fault 00 [READ] at 
00056000 engine 07 [HOST0] client 06 [HUB/HOST] reason 02 [PTE] on 
channel 5 [00ff0d9000 Xwayland[3831]]
  [ 9713.231930] nouveau :01:00.0: fifo: channel 5: killed

[Touch-packages] [Bug 1931475] Re: Ubuntu only stable in safe graphics mode

[Daniel van Vugt]

Thanks for the bug report. Please reproduce the bug (unwanted reboot)
again, then boot in safe mode and run:

 journalctl -b-1 > prevboot1.txt
 journalctl -b-2 > prevboot2.txt

and attach the resulting text files here.

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

** Changed in: linux (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/1931475

Title:
  Ubuntu only stable in safe graphics mode

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Brand new machine,  Intel i5, Brand new install of 20.04 ubuntu using
  5.11.0-18 kernel. BIOS updated to recent firmware. (5/11/2021 date)

  Machine will only stay running in safe graphics mode.  When booting
  normal, GUI loads for about 5 seconds then reboots.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  9 14:04:22 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
  InstallationDate: Installed on 2021-06-09 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard SK-8115
   Bus 001 Device 002: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 7: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
   |__ Port 8: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
  MachineType: ASUS System Product Name
  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.11.0-18-generic 
root=UUID=5e92baa8-faf7-43e0-ab03-c43a1ec8a549 ro recovery nomodeset 
dis_ucode_ldr text
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2021
  dmi.bios.release: 16.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1605
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B460-PLUS
  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.:bvr1605:bd04/07/2021:br16.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB460-PLUS: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: ASUS
  mtime.conffile..etc.apport.crashdb.conf: 2021-06-09T13:25:26.012453
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

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

[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

[Daniel van Vugt]

This is not hardware-specific.

** Summary changed:

- [hirsute/impish] Realtek RTL8821AE 802.11ac PCIe [10ec:8821] Subsystem 
[17aa:a814]: Can't turn bluetooth on again after turning it off
+ [hirsute/impish] Can't turn bluetooth on again after turning it off

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

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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

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

[Touch-packages] [Bug 1930409] Re: Pulseaudio 14.2 says: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ...

[Daniel van Vugt]

When you run 'apport-cli' it should give you a link to click on. Did you
follow that?

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

Title:
  Pulseaudio 14.2 says: GetManagedObjects() failed:
  org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ...

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Not sure if the bluez error is related, perhaps not (this is a desktop
  without Wifi/Bluetooth).

  jun 01 12:46:30 Obelix dbus-daemon[1070]: [system] Failed to activate service 
'org.bluez': timed out (service_start_timeout=25000ms)
  jun 01 12:46:30 Obelix pulseaudio[1749]: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired,>

  Intel i3-9100, C246 chipset, 32GB ram.

  Ubuntu Budgie 21.04 installed via usb boot disk.

  It gives me a popup "error occured" every time I reboot..

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: pulseaudio 1:14.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asterix1749 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Tue Jun  1 12:48:36 2021
  InstallationDate: Installed on 2021-05-11 (21 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.release: 1.6
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.13 R1.6.0 for D3644-B1x
  dmi.board.name: D3644-B1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3644-B1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.13R1.6.0forD3644-B1x:bd05/15/2019:br1.6:svnFUJITSU:pn:pvr:rvnFUJITSU:rnD3644-B1:rvrS26361-D3644-B1:cvnFUJITSU:ct3:cvr:
  dmi.product.family: OEM-FTS
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1926548] Re: The gatt protocol has out-of-bounds read that leads to information leakage

[Daniel van Vugt]

(checks again) Yes, fixed in 5.56 looks right.

commit 3a40bef49305f8327635b81ac8be52a3ca063d5a
Author: Luiz Augusto von Dentz 
AuthorDate: Mon Jan 4 10:38:31 2021 -0800
Commit: Luiz Augusto von Dentz 
CommitDate: Tue Jan 5 10:41:27 2021 -0800

landed on master before the next tag, which was:

commit 482929f12b645f652d378fbe8d0a5b7c05d65c4f (tag: 5.56)
Author: Marcel Holtmann 
AuthorDate: Mon Feb 22 21:12:40 2021 +0100
Commit: Marcel Holtmann 
CommitDate: Mon Feb 22 21:12:40 2021 +0100

However, it doesn't look like it's present on master anymore because it
was rewritten 6 hours later:

commit 6a50b6aeda78a88eafb177718109c256eec077a6
Author: Luiz Augusto von Dentz 
AuthorDate: Tue Jan 5 16:45:37 2021 -0800
Commit: Luiz Augusto von Dentz 
CommitDate: Tue Jan 5 16:55:32 2021 -0800

I assume the rewrite is free of the original bug, and so still fixed in
5.56.

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

Title:
  The gatt protocol has out-of-bounds read that leads to information
  leakage

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Hirsute:
  Fix Released
Status in bluez source package in Impish:
  Fix Released

Bug description:
  I installed the latest bluez 5.53-0ubuntu3 version using apt-get install. It 
seems that this vulnerability was silently fixed in the latest bluez5.8, and 
the cve number was not assigned.
  But this vulnerability now affects the latest ubuntu system
  This vulnerability allows an attacker to remotely obtain most of the contents 
of the heap without authentication.
  The vulnerability code is stored in cli_feat_read_cb, this function does not 
verify the offset parameter
  The vulnerability code is as follows

  gatt-database.c

  1054：static void cli_feat_read_cb(struct gatt_db_attribute *attrib,
unsigned int id, uint16_t offset,
uint8_t opcode, struct bt_att *att,
void *user_data){
  ...
  len = sizeof(state->cli_feat)-offset;
  value = len? &state->cli_feat[offset]: NULL;

  done:
  gatt_db_attribute_read_result(attrib, id, ecode, value, len);

  
  }
  len will become very large due to integer overflow, so that a message of mtu 
(0x90) size will be sent later
  The message content is the buffer pointed to by value, which can be most 
addresses on the heap

  poc is very simple, the core is this line of code

  memcpy(&buf[0],"\x0c\x0b\x00\x0d\x00",5);

  0xc stands for read
  \x0b\x00 represents the handle of the client feature, which can be obtained 
through the find info message, which seems to be 0b by default
  \x0d\x00 is offset0xd

  
  this vulnerability is serious
  I want to apply for a cve number, although this has been silently fixed in 
the latest version

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

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

[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Realtek RTL8821AE 802.11ac PCIe [10ec:8821] Subsystem [17aa:a814]: Can't turn bluetooth on again after turning it off

[You-Sheng Yang]

** Summary changed:

- [hirsute/impish] Can't turn bluetooth on again after turning it off
+ [hirsute/impish] Realtek RTL8821AE 802.11ac PCIe [10ec:8821] Subsystem 
[17aa:a814]: Can't turn bluetooth on again after turning it off

** Description changed:

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn it
  on again. it neither turns on nor scans/connects to any device. This is
  happening since I updated my system to ubuntu 21.04 LTS
+ 
+   Bluetooth: hci0: HCI reset during shutdown failed
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
-  LANGUAGE=en_IN:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_IN
-  SHELL=/bin/bash
+  LANGUAGE=en_IN:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_IN
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
-  hci0:Type: Primary  Bus: USB
-   BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
-   DOWN 
-   RX bytes:744804 acl:76 sco:0 events:105989 errors:0
-   TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0
+  hci0:Type: Primary  Bus: USB
+   BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
+   DOWN
+   RX bytes:744804 acl:76 sco:0 events:105989 errors:0
+   TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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

Title:
  [hirsute/impish] Realtek RTL8821AE 802.11ac PCIe [10ec:8821] Subsystem
  [17aa:a814]: Can't turn bluetooth on again after turning it off

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.mod

[Touch-packages] [Bug 1926548] Re: The gatt protocol has out-of-bounds read that leads to information leakage

[Seth Arnold]

Daniel, are you sure about that fixed-in-5.56 bug tag? I can't spot the
referenced commit in the tarballs 5.55, 5.56, 5.57, 5.58 from:
http://www.bluez.org/

nor in the github sources:
https://github.com/bluez/bluez/blob/master/src/gatt-database.c#L1054

nor the kernel.org sources:
https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/src/gatt-database.c#n1054

Thanks

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

Title:
  The gatt protocol has out-of-bounds read that leads to information
  leakage

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Hirsute:
  Fix Released
Status in bluez source package in Impish:
  Fix Released

Bug description:
  I installed the latest bluez 5.53-0ubuntu3 version using apt-get install. It 
seems that this vulnerability was silently fixed in the latest bluez5.8, and 
the cve number was not assigned.
  But this vulnerability now affects the latest ubuntu system
  This vulnerability allows an attacker to remotely obtain most of the contents 
of the heap without authentication.
  The vulnerability code is stored in cli_feat_read_cb, this function does not 
verify the offset parameter
  The vulnerability code is as follows

  gatt-database.c

  1054：static void cli_feat_read_cb(struct gatt_db_attribute *attrib,
unsigned int id, uint16_t offset,
uint8_t opcode, struct bt_att *att,
void *user_data){
  ...
  len = sizeof(state->cli_feat)-offset;
  value = len? &state->cli_feat[offset]: NULL;

  done:
  gatt_db_attribute_read_result(attrib, id, ecode, value, len);

  
  }
  len will become very large due to integer overflow, so that a message of mtu 
(0x90) size will be sent later
  The message content is the buffer pointed to by value, which can be most 
addresses on the heap

  poc is very simple, the core is this line of code

  memcpy(&buf[0],"\x0c\x0b\x00\x0d\x00",5);

  0xc stands for read
  \x0b\x00 represents the handle of the client feature, which can be obtained 
through the find info message, which seems to be 0b by default
  \x0d\x00 is offset0xd

  
  this vulnerability is serious
  I want to apply for a cve number, although this has been silently fixed in 
the latest version

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

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

[Touch-packages] [Bug 1918955] Re: SRU network: fix LXC_NET_NONE cleanup

[Scott Moser]

Just fwi, this is in 4.0.6 which is up for SRU in LP: #1923232.

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

Title:
  SRU network: fix LXC_NET_NONE cleanup

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Focal:
  Confirmed
Status in lxc source package in Groovy:
  Confirmed
Status in lxc source package in Hirsute:
  Fix Released

Bug description:
  Hi.  I'm using 20.04, and I need a fix for
  https://github.com/lxc/lxc/pull/3589

  I think my only options to get that via packaging are
   a.) https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxc-git-master
   b.) build my own.

  I don't love either of those options.

  Can we please get a SRU update to 20.04 of an lxc with that fix?

  The fix is not in 4.0.5, so I marked this as affecting Groovy
  (currently 1:4.0.4-0ubuntu3) without testing.

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

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

[Touch-packages] [Bug 1923232] Re: SRU of LXC 4.0.6 to focal (upstream bugfix release)

[Scott Moser]

This would fix LP: #1918955.

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

Title:
  SRU of LXC 4.0.6 to focal (upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Focal:
  Fix Committed

Bug description:
  LXC released 4.0.6 as a bugfix release with the following changelog:

  - Improve handling for compatibility architectures for seccomp
  - Harden seccomp notifier implementation
  - Rework parsing of /proc//mountinfo to handle kernel regression
  - Improve network device restoration
  - Significantly cleanup and harden config file parsing
  - Support new capabilities CAP_PERFORM, CAP_BPF, and 
CAP_CHECKPOINT_RESTORE
  - Harden containers started without CAP_NET_ADMIN
* New upstream bugfix release (4.0.5):
  - Support allocating PTS devices from within the container
  - Harden more path/mount handling logics
  - Rework LSM logic to limit initializer use
* Cherry-pick upstream fixes:
  - 0002-commands-fix-check-for-seccomp-notify-support.patch
  - 0003-configure-skip-libseccomp-tests-if-it-is-disabled.patch
  - 0004-conf-fix-containers-retaining-CAP_NET_ADMIN.patch
  - 0005-cgroups-fix-cgroup-mounting.patch
  - 0006-lsm-remove-obsolute-comment-about-constructor.patch
  - 0007-lxc_attach-include-rexec-conditionally.patch
  - 0008-tree-wide-fix-some-header-inclusions.patch
  - 0009-initutils-fix-missing-includes.patch
  - 0010-configure-support-static-binaries.patch
  - 0011-autotools-enable-static-builds-for-tools.patch
  - 0012-autotools-enable-static-builds-for-commands.patch
  - 0013-tree-wide-fix-compilation-with-Wstrict-prototypes-Wo.patch
  - 0014-config-update-ax_pthread.m4.patch
  - 0015-configure-add-AC_SYS_LARGEFILE-checking.patch
  - 0016-autotools-update-build.patch
  - 0017-file_utils-introduce-read_file_at.patch
  - 0018-string_utils-add-must_make_path_relative.patch
  - 0019-cgroups-coding-style-fixes.patch
  - 0020-cgroups-rework-cg_unified_init.patch
  - 0021-cgroups-detect-and-record-cgroup2-freezer-support.patch
  - 0022-criu-handle-cgroup2-freezer.patch
  - 0023-mkdir-p-proc-sys-on-container-startup.patch
  - 0024-conf-fix-coding-style.patch
  - 0025-conf-coding-style-fixes.patch
  - 0026-conf-move-proc-and-sys-mountpoint-creation-int-lxc_m.patch
  - 0027-attach-invert-child-parent-handling.patch
  - 0028-attach-use-__do_free-cleanup-macro-for-cwd.patch
  - 0029-attach-tweak-logging.patch
  - 0030-attach-use-__do_close-for-labelfd.patch
  - 0031-attach-coding-style-fixes.patch
  - 0032-attach-use-free_disarm.patch
  - 0033-attach-s-attach_child_main-do_attach-g.patch
  - 0034-attach-mark-do_attach-as-__noreturn.patch
  - 0035-attach-make-do_attach-void.patch
  - 0036-attach-use-close_prot_errno_disarm.patch
  - 0037-attach-add-some-DEBUG-logging-to-stdfd-dpulication.patch
  - 0038-cgroups-fix-cgroup-mounting.patch
  - 0039-utils-fix-mount_at.patch
  - 0040-configure-fix-static-builds-with-clang-12-and-LTO.patch
  - 0041-cgroups-bpf-fixes.patch
  - 0042-croups-improve-__do_bpf_program_free.patch
  - 0043-cgroups-coding-style-fixes.patch
  - 0044-cgroups-don-t-initiliaze-NULL-log.patch
  - 0045-cgroups-ensure-all-memory-is-zeroed.patch
  - 0046-cgroups-use-zalloc.patch
  - 0047-cgroups-tweak-cgroup-initialization.patch
  - 0048-log-remove-pointless-inline.patch
  - 0049-log-add-lxc_log_get_fd.patch
  - 0050-seccomp-use-lxc_log_get_fd.patch
  - 0051-log-rework-lxc_log_get_level.patch
  - 0052-seccomp-use-lxc_log_get_level.patch
  - 0053-cgroups-use-bpf-log-when-logging-at-trace-level.patch
  - 0054-log-add-lxc_log_trace-helper.patch
  - 0055-cgroups-use-PTR_TO_U64.patch
  - 0056-cgroups-align-methods.patch
  - 0057-utils-use-SYSTRACE-when-logging-stdio-permission-fix.patch
  - 0058-attach-log-failues-to-dup2-with-SYSDEBUG.patch
  - 0059-attach-fix-logging-for-stdfd-replacement.patch
  - 0060-attach-fix-error-checking-for-dup2.patch
  - 0061-cgroups-initialize-variable.patch
  - 0062-commands_utils-don-t-leak-memory.patch
  - 0063-conf-use-lxc_log_trace.patch
  - 0064-confile_utils-use-lxc_log_trace.patch
  - 0065-rexec-check-lseek-return-value.patch

* Cherry-pick upstream bugfix:
  - cgroups: fix armhf builds

* Cherry-pick upstream bugfix:
  - cgfsng: fix cgroup attach cgroup creation

* New upstream bugfix release (4.0.4):
  - Support for new Linux clone flags (clone into cgroup)
  - Support for new Linux VFS system calls
  - Internal symbols are now properly hidden from external consumers
* New upstream bugfix release (4.0.3):
  - Improvement to cgroupv1/cgroupv2 hand

[Touch-packages] [Bug 1926548] Re: The gatt protocol has out-of-bounds read that leads to information leakage

[Bug Watch Updater]

** Changed in: bluez
   Status: Unknown => Fix Released

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

Title:
  The gatt protocol has out-of-bounds read that leads to information
  leakage

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Hirsute:
  Fix Released
Status in bluez source package in Impish:
  Fix Released

Bug description:
  I installed the latest bluez 5.53-0ubuntu3 version using apt-get install. It 
seems that this vulnerability was silently fixed in the latest bluez5.8, and 
the cve number was not assigned.
  But this vulnerability now affects the latest ubuntu system
  This vulnerability allows an attacker to remotely obtain most of the contents 
of the heap without authentication.
  The vulnerability code is stored in cli_feat_read_cb, this function does not 
verify the offset parameter
  The vulnerability code is as follows

  gatt-database.c

  1054：static void cli_feat_read_cb(struct gatt_db_attribute *attrib,
unsigned int id, uint16_t offset,
uint8_t opcode, struct bt_att *att,
void *user_data){
  ...
  len = sizeof(state->cli_feat)-offset;
  value = len? &state->cli_feat[offset]: NULL;

  done:
  gatt_db_attribute_read_result(attrib, id, ecode, value, len);

  
  }
  len will become very large due to integer overflow, so that a message of mtu 
(0x90) size will be sent later
  The message content is the buffer pointed to by value, which can be most 
addresses on the heap

  poc is very simple, the core is this line of code

  memcpy(&buf[0],"\x0c\x0b\x00\x0d\x00",5);

  0xc stands for read
  \x0b\x00 represents the handle of the client feature, which can be obtained 
through the find info message, which seems to be 0b by default
  \x0d\x00 is offset0xd

  
  this vulnerability is serious
  I want to apply for a cve number, although this has been silently fixed in 
the latest version

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

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

[Touch-packages] [Bug 1922186] Re: ibus very difficult to restart

[Gunnar Hjalmarsson]

Hey, how about getting a more constructive hobby than killing various
important processes on your system? ;)

More seriously: I'm not sure that "ibus restart" is intended to handle
such situations. But please feel free to comment on the issue I
submitted — the upstream maintainer hasn't attended to it yet. Or,
probably better, submit an own upstream issue since they are separate
things.

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

Title:
  ibus very difficult to restart

Status in ibus:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  After closing ibus by task bar -> icon -> rightclick -> `Close` it
  seems to be impossible to restart it.

  Here some ways that should work and how they fail:

  1) Menu -> ibus
  -
  - opens iBus settings 
  - starts ibus service

  Problems:
- No keyboard input is actually processed; I.e. cannot use keyboard then.
- Service is not daemonized; I.e. as soon as the iBus settings window is 
closed, the services quits.

  Suggestion:
- No keyboard input possible seems to be a bug -> should be fixed.
- Service should be daemonized at this point

  2) terminal -> `ibus start`
  ---
  Problems:
- This command does not exist. One has to know, that `ibus-daemon` is the 
one they are searching for.

  Suggestions:
- Implement this command to start the daemon from here

  3) terminal -> `ibus-daemon &` / `ibus-daemon -d`
  -
   - brings up ibus with usable keyboard (good)

  Problems: 
- As soon as terminal gets closed, ibus-daemon quits

  4) terminal -> `nohup ibus-daemon &`
  -
   - brings up ibus with usable keyboard (good)

  Problem: 
- As soon as terminal gets closed, ibus-daemon quits (very strange. 
something I wouldn't expect from a `nohup` call, by the way).

  System
  ===

  - I use ibus in conjunction with ibus-anthy

  
  lsb_release -rd
  --
  Description:  Ubuntu 20.10
  Release:  20.10

  
  apt-cache policy ibus
  --
  ibus:
Installed: 1.5.23-0ubuntu1
Candidate: 1.5.23-0ubuntu1
Version table:
   *** 1.5.23-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

  
  apt-cache policy ibus-anthy
  --
  ibus-anthy:
Installed: 1.5.11-1build1
Candidate: 1.5.11-1build1
Version table:
   *** 1.5.11-1build1 500
  500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ibus 1.5.23-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Thu Apr  1 15:33:00 2021
  RebootRequiredPkgs:
   linux-image-5.8.0-48-generic
   linux-base
   linux-image-5.8.0-49-generic
   linux-base
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1922186] Re: ibus very difficult to restart

[DarkTrick]

+ Added the PPA and installed, now ibus stays "on" after openning the dialog. 
👍️ 
- `ibus restart` still doesnt work: "Can't connect to IBus"

Would be nice to also have a cmd-line option working for this case.


FYI:
Btw: here's another reason for quitting/restarting ibus: if I call `killall 
python3` on my machine, ibus/anthy (?) seems to get into an inconsistent state, 
which prevents input on certain apps. I guess the reason for this is somehow 
connected to what I've described earlier.

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

Title:
  ibus very difficult to restart

Status in ibus:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  After closing ibus by task bar -> icon -> rightclick -> `Close` it
  seems to be impossible to restart it.

  Here some ways that should work and how they fail:

  1) Menu -> ibus
  -
  - opens iBus settings 
  - starts ibus service

  Problems:
- No keyboard input is actually processed; I.e. cannot use keyboard then.
- Service is not daemonized; I.e. as soon as the iBus settings window is 
closed, the services quits.

  Suggestion:
- No keyboard input possible seems to be a bug -> should be fixed.
- Service should be daemonized at this point

  2) terminal -> `ibus start`
  ---
  Problems:
- This command does not exist. One has to know, that `ibus-daemon` is the 
one they are searching for.

  Suggestions:
- Implement this command to start the daemon from here

  3) terminal -> `ibus-daemon &` / `ibus-daemon -d`
  -
   - brings up ibus with usable keyboard (good)

  Problems: 
- As soon as terminal gets closed, ibus-daemon quits

  4) terminal -> `nohup ibus-daemon &`
  -
   - brings up ibus with usable keyboard (good)

  Problem: 
- As soon as terminal gets closed, ibus-daemon quits (very strange. 
something I wouldn't expect from a `nohup` call, by the way).

  System
  ===

  - I use ibus in conjunction with ibus-anthy

  
  lsb_release -rd
  --
  Description:  Ubuntu 20.10
  Release:  20.10

  
  apt-cache policy ibus
  --
  ibus:
Installed: 1.5.23-0ubuntu1
Candidate: 1.5.23-0ubuntu1
Version table:
   *** 1.5.23-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

  
  apt-cache policy ibus-anthy
  --
  ibus-anthy:
Installed: 1.5.11-1build1
Candidate: 1.5.11-1build1
Version table:
   *** 1.5.11-1build1 500
  500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ibus 1.5.23-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Thu Apr  1 15:33:00 2021
  RebootRequiredPkgs:
   linux-image-5.8.0-48-generic
   linux-base
   linux-image-5.8.0-49-generic
   linux-base
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)

[Kelsey Skunberg]

Also seeing this failure on Hirsute & Groovy systemd armhf through ADT:

https://autopkgtest.ubuntu.com/results/autopkgtest-
hirsute/hirsute/armhf/s/systemd/20210609_190755_3e0ab@/log.gz

https://autopkgtest.ubuntu.com/results/autopkgtest-
groovy/groovy/armhf/s/systemd/20210609_190741_7c920@/log.gz

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

Title:
  boot-and-services tests fails in impish on armhf (248.3)

Status in dnsmasq package in Ubuntu:
  Incomplete
Status in gdm3 package in Ubuntu:
  Incomplete
Status in glibc package in Ubuntu:
  Incomplete
Status in isc-dhcp package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf
  before now slipping into a bad mode.

  Now it seems all tests failed in boot-and-services by hanging until killed by
  VirtSubproc.Timeout of autokgtest.

  The last [1] test log has a bit more, it shows a python stack overflow
  ```
 VirtSubproc.Timeout
 Fatal Python error: Cannot recover from stack overflow.
 Python runtime state: initialized

 Current thread 0x7f108e840740 (most recent call first):
   File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log
   File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug
   File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send
   File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command
  ```

  I have seen a bunch of packages including even gdm3 and glibc being blocked by
  that so I wanted to at least track down the issue until we can put it on
  someones task list to resolve.
  No one replied to my pings yet, but maybe that means someone is already
  debugging this and had enabled some debugging?

  By running the same in armhf container on arm64 VM on canonistack I've seen
  no issues. The test worked fine and had no hang/issues.

  root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services
  lxc
  1
  test_profile (__main__.AppArmorTest)
  AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352'
  test_help (__main__.CLITest)
  --help works and succeeds ... ok
  test_invalid_option (__main__.CLITest)
  Calling with invalid option fails ... ok
  test_version (__main__.CLITest)
  --version works and succeeds ... ok
  test_cpushares (__main__.CgroupsTest)
  service with CPUShares ... ok
  test_simple (__main__.CgroupsTest)
  simple service ... ok
  test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does 
not work in containers'
  test_log_for_service (__main__.JournalTest) ... ok
  test_no_options (__main__.JournalTest) ... ok
  test_boot (__main__.NspawnTest) ... skipped 'nspawn does not work in most 
containers'
  test_service (__main__.NspawnTest) ... skipped 'nspawn does not work in most 
containers'
  test_failing (__main__.SeccompTest) ... ok
  test_0_init (__main__.ServicesTest)
  Verify that init is systemd ... ok
  test_cron (__main__.ServicesTest) ... ok
  test_dbus (__main__.ServicesTest) ... ok
  test_gdm3 (__main__.ServicesTest) ... skipped 'gdm3 not found'
  test_logind (__main__.ServicesTest) ... ok
  test_network_manager (__main__.ServicesTest) ... ok
  test_no_failed (__main__.ServicesTest)
  No failed units ... ok
  test_rsyslog (__main__.ServicesTest) ... ok
  test_tmp_cleanup (__main__.ServicesTest) ... ok
  test_tmp_mount (__main__.ServicesTest) ... ok
  test_udev (__main__.ServicesTest) ... skipped 'udev does not work in 
containers'
  --
  Ran 23 tests in 5.589s
  OK (skipped=6)

  So I can not reproduce this on canonistack, but it blocks autopkgtests of
  various packages pretty reproducibly :-/

  [1]: https://autopkgtest.ubuntu.com/results/autopkgtest-
  impish/impish/armhf/s/systemd/20210604_081326_d4319@/log.gz

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

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

[Touch-packages] [Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  boot-and-services tests fails in impish on armhf (248.3)

Status in dnsmasq package in Ubuntu:
  Incomplete
Status in gdm3 package in Ubuntu:
  Incomplete
Status in glibc package in Ubuntu:
  Incomplete
Status in isc-dhcp package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf
  before now slipping into a bad mode.

  Now it seems all tests failed in boot-and-services by hanging until killed by
  VirtSubproc.Timeout of autokgtest.

  The last [1] test log has a bit more, it shows a python stack overflow
  ```
 VirtSubproc.Timeout
 Fatal Python error: Cannot recover from stack overflow.
 Python runtime state: initialized

 Current thread 0x7f108e840740 (most recent call first):
   File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log
   File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug
   File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send
   File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command
  ```

  I have seen a bunch of packages including even gdm3 and glibc being blocked by
  that so I wanted to at least track down the issue until we can put it on
  someones task list to resolve.
  No one replied to my pings yet, but maybe that means someone is already
  debugging this and had enabled some debugging?

  By running the same in armhf container on arm64 VM on canonistack I've seen
  no issues. The test worked fine and had no hang/issues.

  root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services
  lxc
  1
  test_profile (__main__.AppArmorTest)
  AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352'
  test_help (__main__.CLITest)
  --help works and succeeds ... ok
  test_invalid_option (__main__.CLITest)
  Calling with invalid option fails ... ok
  test_version (__main__.CLITest)
  --version works and succeeds ... ok
  test_cpushares (__main__.CgroupsTest)
  service with CPUShares ... ok
  test_simple (__main__.CgroupsTest)
  simple service ... ok
  test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does 
not work in containers'
  test_log_for_service (__main__.JournalTest) ... ok
  test_no_options (__main__.JournalTest) ... ok
  test_boot (__main__.NspawnTest) ... skipped 'nspawn does not work in most 
containers'
  test_service (__main__.NspawnTest) ... skipped 'nspawn does not work in most 
containers'
  test_failing (__main__.SeccompTest) ... ok
  test_0_init (__main__.ServicesTest)
  Verify that init is systemd ... ok
  test_cron (__main__.ServicesTest) ... ok
  test_dbus (__main__.ServicesTest) ... ok
  test_gdm3 (__main__.ServicesTest) ... skipped 'gdm3 not found'
  test_logind (__main__.ServicesTest) ... ok
  test_network_manager (__main__.ServicesTest) ... ok
  test_no_failed (__main__.ServicesTest)
  No failed units ... ok
  test_rsyslog (__main__.ServicesTest) ... ok
  test_tmp_cleanup (__main__.ServicesTest) ... ok
  test_tmp_mount (__main__.ServicesTest) ... ok
  test_udev (__main__.ServicesTest) ... skipped 'udev does not work in 
containers'
  --
  Ran 23 tests in 5.589s
  OK (skipped=6)

  So I can not reproduce this on canonistack, but it blocks autopkgtests of
  various packages pretty reproducibly :-/

  [1]: https://autopkgtest.ubuntu.com/results/autopkgtest-
  impish/impish/armhf/s/systemd/20210604_081326_d4319@/log.gz

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

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

[Touch-packages] [Bug 1931505] [NEW] systemd/247.3-3ubuntu3 ADT test failure with linux/5.11.0-20.21

[Kelsey Skunberg]

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

Public bug reported:

This is a scripted bug report about ADT failures while running systemd
tests for linux/5.11.0-20.21 on hirsute. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be determined.

Testing failed on:
armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/armhf/s/systemd/20210609_190755_3e0ab@/log.gz

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

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

** This bug has been marked a duplicate of bug 1931088
   boot-and-services tests fails in impish on armhf (248.3)

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

Title:
  systemd/247.3-3ubuntu3 ADT test failure with linux/5.11.0-20.21

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

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.11.0-20.21 on hirsute. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/armhf/s/systemd/20210609_190755_3e0ab@/log.gz

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

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

[Touch-packages] [Bug 1931488] Re: Kubuntu: No more file search results in Krunner or Kickoff after Hirsute Upgrade

[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/1931488

Title:
  Kubuntu: No more file search results in Krunner or Kickoff after
  Hirsute Upgrade

Status in xorg package in Ubuntu:
  New

Bug description:
  I just upgraded from Kubuntu 20.10 to 21.04 and now I no longer get
  any file search results ("Desktop search") in Krunner or Kickoff
  ("Application Launcher"). For example type "testfile" in Krunner gives
  zero results although there this file in the home directory.

  However baloosearch in the terminal works fine. Desktop search / file
  search is also enabled in the settings for Krunner and in system
  settings.

  If I create a new user account the file search does work. I assume
  that some setting in the home directory must have been changed during
  the upgrade.

  Please let me know which logs or files I could upload that could be of
  use to debug this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Jun  9 20:10:40 2021
  DistUpgraded: 2021-06-06 22:12:52,319 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.18, 5.11.0-18-generic, x86_64: installed
   virtualbox, 6.1.18, 5.8.0-55-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Fujitsu Technology Solutions HD Graphics 630 [1734:121c]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c326 Logitech, Inc. Washable Keyboard K310
   Bus 001 Device 002: ID 046d:c404 Logitech, Inc. TrackMan Wheel
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU ESPRIMO Q556/2
  ProcEnviron:
   LANGUAGE=de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic 
root=UUID=8f3a8bfd-584a-4e11-a2f8-984c6e293255 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to hirsute on 2021-06-06 (2 days ago)
  dmi.bios.date: 02/12/2020
  dmi.bios.release: 1.26
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.26.0 for D3403-U1x
  dmi.board.name: D3403-U1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3403-U1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.26.0forD3403-U1x:bd02/12/2020:br1.26:svnFUJITSU:pnESPRIMOQ556/2:pvr:rvnFUJITSU:rnD3403-U1:rvrS26361-D3403-U1:cvnFUJITSU:ct3:cvr:
  dmi.product.family: ESPRIMO-FTS
  dmi.product.name: ESPRIMO Q556/2
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

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

[Touch-packages] [Bug 1931488] [NEW] Kubuntu: No more file search results in Krunner or Kickoff after Hirsute Upgrade

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I just upgraded from Kubuntu 20.10 to 21.04 and now I no longer get any
file search results ("Desktop search") in Krunner or Kickoff
("Application Launcher"). For example type "testfile" in Krunner gives
zero results although there this file in the home directory.

However baloosearch in the terminal works fine. Desktop search / file
search is also enabled in the settings for Krunner and in system
settings.

If I create a new user account the file search does work. I assume that
some setting in the home directory must have been changed during the
upgrade.

Please let me know which logs or files I could upload that could be of
use to debug this problem.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Jun  9 20:10:40 2021
DistUpgraded: 2021-06-06 22:12:52,319 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.18, 5.11.0-18-generic, x86_64: installed
 virtualbox, 6.1.18, 5.8.0-55-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: Fujitsu Technology Solutions HD Graphics 630 [1734:121c]
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 046d:c326 Logitech, Inc. Washable Keyboard K310
 Bus 001 Device 002: ID 046d:c404 Logitech, Inc. TrackMan Wheel
 Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: FUJITSU ESPRIMO Q556/2
ProcEnviron:
 LANGUAGE=de
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic 
root=UUID=8f3a8bfd-584a-4e11-a2f8-984c6e293255 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to hirsute on 2021-06-06 (2 days ago)
dmi.bios.date: 02/12/2020
dmi.bios.release: 1.26
dmi.bios.vendor: FUJITSU // American Megatrends Inc.
dmi.bios.version: V5.0.0.12 R1.26.0 for D3403-U1x
dmi.board.name: D3403-U1
dmi.board.vendor: FUJITSU
dmi.board.version: S26361-D3403-U1
dmi.chassis.type: 3
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.26.0forD3403-U1x:bd02/12/2020:br1.26:svnFUJITSU:pnESPRIMOQ556/2:pvr:rvnFUJITSU:rnD3403-U1:rvrS26361-D3403-U1:cvnFUJITSU:ct3:cvr:
dmi.product.family: ESPRIMO-FTS
dmi.product.name: ESPRIMO Q556/2
dmi.sys.vendor: FUJITSU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.104-1build1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: amd64 apport-bug hirsute kubuntu third-party-packages ubuntu
-- 
Kubuntu: No more file search results in Krunner or Kickoff after Hirsute Upgrade
https://bugs.launchpad.net/bugs/1931488
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 1875796] Re: HP Envy 5530 printer/scanner does not work

[Andrew]

I have one printer.  It is a HP Envy 5530.  I'm experiencing multiple issues.  
Sometimes CUPS finds printers, sometimes it doesn't.  It auto-adds printers 
randomly.  It auto-deletes printers randomly.  One day the printer works, the 
next it does not.

Also seeing these errors in syslog:
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 427: Found interface conf=0, 
iface=0, altset=1, index=3
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 389: Active kernel driver on 
interface=0 ret=0
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 515: invalid claim_interface 
7/1/4: Device or resource busy
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 427: Found interface conf=0, 
iface=3, altset=0, index=9
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 389: Active kernel driver on 
interface=3 ret=0
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 515: invalid claim_interface 
ff/4/1: Device or resource busy
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 427: Found interface conf=0, 
iface=0, altset=0, index=11
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 389: Active kernel driver on 
interface=0 ret=0
Jun  9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 515: invalid claim_interface 
ff/cc/0: Device or resource busy
Jun  9 12:42:14 yellow hp[34756]: prnt/backend/hp.c 825: INFO: open device 
failed stat=21: hp:/usb/ENVY_5530_series?serial=CN57A5636Z05XT; will retry in 
30 seconds...


** Attachment added: "Screenshot of duplicate printers in CUPS Find New 
Printers."
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1875796/+attachment/5503675/+files/screenshot-127.0.0.1_631-2021.06.09-12_38_33%281%29.png

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

[Touch-packages] [Bug 1931485] [NEW] DaVinci Resolve is not identifying my integrated Intel Graphics card

[joydipto-nag]

Public bug reported:

In Windows the GPU gets identified automatically but not in Ubuntu which
is installed on the same system

My Configuration:

Laptop: DELL Inspiron 15 5580
Processor: i5-8265U
Integrated graphics: Intel UHD Graphics 620

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-55-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 10 00:23:48 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:089d]
InstallationDate: Installed on 2021-06-06 (3 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: Dell Inc. Inspiron 5580
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic 
root=UUID=4891d34b-6067-4d2e-b45e-3393d909 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/28/2020
dmi.bios.release: 2.9
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.9.0
dmi.board.name: 0J0XK8
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.9.0:bd12/28/2020:br2.9:svnDellInc.:pnInspiron5580:pvr:rvnDellInc.:rn0J0XK8:rvrA02:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5580
dmi.product.sku: 089D
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  DaVinci Resolve is not identifying my integrated Intel Graphics card

Status in xorg package in Ubuntu:
  New

Bug description:
  In Windows the GPU gets identified automatically but not in Ubuntu
  which is installed on the same system

  My Configuration:

  Laptop: DELL Inspiron 15 5580
  Processor: i5-8265U
  Integrated graphics: Intel UHD Graphics 620

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-55-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 10 00:23:48 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:089d]
  InstallationDate: Installed on 2021-06-06 (3 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Inspiron 5580
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic 
root=UUID=4891d34b-6067-4d2e-b45e-3393d909 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/28/2020
  dmi.bios.release: 2.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.9.0
  dmi.board.name: 0J0XK8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.9.0:bd12/28/2020:br2.9:svnDellInc.:pnInspiron5580:pvr:rvnDellInc.:rn0J0XK8:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5580
  dmi.product.sku: 089D
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  v

[Touch-packages] [Bug 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)

[Thomas]

I just commended out the line "mystatedir statedir ifindex interface" on
both files /etc/network/if-up.d/resolved and /etc/network/if-
down.d/resolved

works without issues.

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

Title:
  wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]:
  /etc/network/if-up.d/resolved: 12: mystatedir: not found)

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  Syslog error:

 nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir:
  not found

  I think it's because of this line:

if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then
mystatedir statedir ifindex interface <- this 
is interpreted as a 'mystatedir' command and fails

interface=$IFACE
if [ ! "$interface" ]; then

  
  Perhaps the intention was to 'export mystatedir statedir ...'

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

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

[Touch-packages] [Bug 1931475] [NEW] Ubuntu only stable in safe graphics mode

[welefort]

Public bug reported:

Brand new machine,  Intel i5, Brand new install of 20.04 ubuntu using
5.11.0-18 kernel. BIOS updated to recent firmware. (5/11/2021 date)

Machine will only stay running in safe graphics mode.  When booting
normal, GUI loads for about 5 seconds then reboots.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun  9 14:04:22 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
InstallationDate: Installed on 2021-06-09 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard SK-8115
 Bus 001 Device 002: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
 |__ Port 7: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
 |__ Port 8: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
MachineType: ASUS System Product Name
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.11.0-18-generic 
root=UUID=5e92baa8-faf7-43e0-ab03-c43a1ec8a549 ro recovery nomodeset 
dis_ucode_ldr text
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2021
dmi.bios.release: 16.5
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1605
dmi.board.asset.tag: Default string
dmi.board.name: PRIME B460-PLUS
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.:bvr1605:bd04/07/2021:br16.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB460-PLUS: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: ASUS
mtime.conffile..etc.apport.crashdb.conf: 2021-06-09T13:25:26.012453
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.104-1build1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: amd64 apport-bug hirsute ubuntu

** Attachment added: "Kern.log"
   https://bugs.launchpad.net/bugs/1931475/+attachment/5503616/+files/kern.log

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

Title:
  Ubuntu only stable in safe graphics mode

Status in xorg package in Ubuntu:
  New

Bug description:
  Brand new machine,  Intel i5, Brand new install of 20.04 ubuntu using
  5.11.0-18 kernel. BIOS updated to recent firmware. (5/11/2021 date)

  Machine will only stay running in safe graphics mode.  When booting
  normal, GUI loads for about 5 seconds then reboots.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  9 14:04:22 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
  InstallationDate: Installed on 2021-06-09 (0 days ag

[Touch-packages] [Bug 1931475] Re: Ubuntu only stable in safe graphics mode

[welefort]

** Attachment added: "Hardware Info"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1931475/+attachment/5503634/+files/hardinfo_report.html

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

Title:
  Ubuntu only stable in safe graphics mode

Status in xorg package in Ubuntu:
  New

Bug description:
  Brand new machine,  Intel i5, Brand new install of 20.04 ubuntu using
  5.11.0-18 kernel. BIOS updated to recent firmware. (5/11/2021 date)

  Machine will only stay running in safe graphics mode.  When booting
  normal, GUI loads for about 5 seconds then reboots.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  9 14:04:22 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
  InstallationDate: Installed on 2021-06-09 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard SK-8115
   Bus 001 Device 002: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 7: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
   |__ Port 8: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
  MachineType: ASUS System Product Name
  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.11.0-18-generic 
root=UUID=5e92baa8-faf7-43e0-ab03-c43a1ec8a549 ro recovery nomodeset 
dis_ucode_ldr text
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2021
  dmi.bios.release: 16.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1605
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B460-PLUS
  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.:bvr1605:bd04/07/2021:br16.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB460-PLUS: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: ASUS
  mtime.conffile..etc.apport.crashdb.conf: 2021-06-09T13:25:26.012453
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

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

[Touch-packages] [Bug 1931394] Re: With glib2 2.68 gdebi is an FTBFS (hangs)

[Christian Ehrhardt ]

** Branch linked: lp:~paelzer/gdebi/gdebi-fix-glib-2.68

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

Title:
  With glib2 2.68 gdebi is an FTBFS (hangs)

Status in gdebi package in Ubuntu:
  New
Status in gdebi package in Debian:
  New

Bug description:
  Ubuntu https://launchpad.net/ubuntu/+source/gdebi/0.9.5.7+nmu5 is an FTBFS
  
https://launchpadlibrarian.net/542966965/buildlog_ubuntu-impish-amd64.gdebi_0.9.5.7+nmu5_BUILDING.txt.gz

  The same https://launchpad.net/ubuntu/+source/gdebi/0.9.5.7+nmu4
  worked as it was builds against glib2.0 2.66 back in the day.

  Debian still works as they have 2.66 still
  
https://buildd.debian.org/status/fetch.php?pkg=gdebi&arch=all&ver=0.9.5.7%2Bnmu5&stamp=1621453414&raw=0


  At build time it is getting stuck until a timeout kills it:

  Log:
  ```
  running build_ext
  test_simple (tests.test_gdebi_gtk.GDebiGtkTestCase) ... WARNING:root:Error 
loading logo gtk-icon-theme-error-quark: Icon 'gnome-mime-application-x-deb' 
not present in theme Yaru (0)

  (setup.py:7825): Gtk-WARNING **: 05:55:50.408: Error loading theme icon 
'dialog-error' for stock: Icon 'dialog-error' not present in theme Yaru
  E: Build killed with signal TERM after 150 minutes of inactivity
  ```

  This is reproducible locally and the process tree looks like:

  F   UID     PID    PPID PRI  NI    VSZ   RSS WCHAN  STAT TTY        TIME 
COMMAND
  4     0   39842       0  20   0   9328  3000 do_wai Ss   pts/2      0:00 bash
  0     0   40835   39842  20   0  22136 13032 do_wai S+   pts/2      0:00  \_ 
/usr/bin/perl /usr/bin/debuild -i -us -uc -b
  0     0   40852   40835  20   0   7392   604 pipe_w S+   pts/2      0:00      
\_ tee ../gdebi_0.9.5.7+nmu5_amd64.build
  0     0   40853   40835  20   0  25328 16328 do_wai S+   pts/2      0:00      
\_ /usr/bin/perl /usr/bin/dpkg-buildpackage -us -uc -ui -i -b
  0     0   40891   40853  20   0   7764  1616 do_wai S+   pts/2      0:00      
    \_ /usr/bin/make -f debian/rules build
  0     0   40892   40891  20   0  24356 15260 do_wai S+   pts/2      0:00      
        \_ /usr/bin/perl /usr/bin/dh build --with python3 --buildsystem pybuild
  0     0   41533   40892  20   0   7764  1572 do_wai S+   pts/2      0:00      
            \_ /usr/bin/make -f debian/rules override_dh_auto_test
  0     0   41535   41533  20   0   2620  1320 do_wai S+   pts/2      0:00      
                \_ /bin/sh /usr/bin/xvfb-run -a python3.9 setup.py test
  4     0   41545   41535  20   0 1034648 37536 ep_pol Sl+ pts/2      0:00      
                    \_ Xvfb :99 -screen 0 1280x1024x24 -nolisten tcp -auth 
/tmp/xvfb-run.RlZdX8/Xauthority
  0     0   41560   41535  20   0 1331396 131060 poll_s Sl+ pts/2     0:01      
                    \_ python3.9 setup.py test

  
  From there the test is stuck.
  Some debugging revealed that it does no more come back from:
  GDebiGtkTestCase
   -> test_lintian
    -> GDebiGtk (init)
      -> gio_copy_in_place
        -> show_alert

  That alert only happens because we run as root, but even if that is avoided
  (e.g. by running as another user) then it blocks at the next message. E.g.
  when failing to download.

  But these blocking alerts are only secondary symptoms.

  I've found that all issues come back to a check that seems wrong.
  The test wants to copy a non-existing file into a temp path.
  At least the current version of Gio.File hates this and errors out
    g-io-error-quark: Operation not supported (15)

  Maybe Gio was more tolerant in the past, but checking a non existing
  file makes no sense anyway. We can guard that step a bit better than all 
works.

  A fix could look like:
  --- /home/ubuntu/gdebi-0.9.5.7+nmu5/GDebi/GDebiGtk.py 2021-06-09 
10:17:06.516869439 +
  +++ /root/gdebi-0.9.5.7+nmu5/GDebi/GDebiGtk.py 2021-06-09 10:09:35.113662314 
+
  @@ -119,7 +119,8 @@
                                    self.on_window_main_drag_data_received)
   
           # Check file with gio
  -        file = self.gio_copy_in_place(file)
  +        if file != "" and os.path.exists(file):
  +            file = self.gio_copy_in_place(file)
   
           #self.vte_terminal.set_font_from_string("monospace 10")
           self.cprogress = self.CacheProgressAdapter(self.progressbar_cache)

  I've proposed the same to the project [1], but I'm unsure about the speed this
  is picked up there.
  I've also filed this in Debian for them to be aware when the 2.68 switch 
happens.

  [1]: 
https://code.launchpad.net/~paelzer/gdebi/gdebi-fix-glib-2.68/+merge/403954
  [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989647

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

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

[Touch-packages] [Bug 1931104] Re: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-proposed

[Christian Ehrhardt ]

This feels like a circle with nss/2:3.66-1ubuntu1~impishppa2 in
https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4577/+packages now ppc64 works but s390x fails
with (on the surface) the same symptom as it started with in 3.63 :-/

I retriggered the tests to see if that is flaky or reproducible.

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

Title:
  Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-
  proposed

Status in nss package in Ubuntu:
  New

Bug description:
  The test of dogtag-pki is failing on the nss 3.63 that is in impish proposed.
  Example:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/d/dogtag-pki/20210516_212719_e6522@/log.gz

  Bad:
  Installing CA into /var/lib/pki/pki-tomcat.
  Installation failed: ('Connection aborted.', RemoteDisconnected('Remote end 
closed connection without response'))
  ERROR: ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote 
end closed connection without response'))
    File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in 
main
  scriptlet.spawn(deployer)
    File 
"/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py",
 line 995, in spawn
  cert = deployer.setup_cert(client, tag)
    File "/usr/lib/python3/dist-packages/pki/server/deployment/__init__.py", 
line 355, in setup_cert
  return client.setupCert(request)
    File "/usr/lib/python3/dist-packages/pki/system.py", line 389, in setupCert
  response = self.connection.post(
    File "/usr/lib/python3/dist-packages/pki/client.py", line 55, in wrapper
  return func(self, *args, **kwargs)
    File "/usr/lib/python3/dist-packages/pki/client.py", line 293, in post
  r = self.session.post(
    File "/usr/lib/python3/dist-packages/requests/sessions.py", line 590, in 
post
  return self.request('POST', url, data=data, json=json, **kwargs)
    File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in 
request
  resp = self.send(prep, **send_kwargs)
    File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in 
send
  r = adapter.send(request, **kwargs)
    File "/usr/lib/python3/dist-packages/requests/adapters.py", line 498, in 
send
  raise ConnectionError(err, request=request)
   CA spawn failed:

  Good:
  nstalling CA into /var/lib/pki/pki-tomcat.
  Notice: Trust flag u is set automatically if the private key is present.
  /usr/lib/python3/dist-packages/urllib3/connection.py:455: 
SubjectAltNameWarning: Certificate for i-dogtag has no `subjectAltName`, 
falling back to check for a `commonName` for now. This feature is being removed 
by major browsers and deprecated by RFC 2818. (See 
https://github.com/urllib3/urllib3/issues/497 for details.)
    warnings.warn(

  ==
  INSTALLATION SUMMARY
  ==
  ...

  The good test above was with:
  ii  libnss3:s390x2:3.61-1ubuntu2  s390xNetwork Security 
Service libraries
  ii  389-ds-base1.4.4.11-2  s390x389 Directory Server suite - 
server

  Worth to know, the good case test still fails later on with:
  IOException: SocketException cannot write on socket: Failed to write to 
socket: (-5938) Encountered end of file.
  ERROR: CalledProcessError: Command '['pki', '-d', 
'/etc/pki/pki-tomcat/alias', '-f', '/etc/pki/pki-tomcat/password.conf', '-U', 
'https://i-dogtag:8443', 'securitydomain-join', '--session', 
'4717921475119312283', '--type', 'TKS', '--hostname', 'i-dogtag', 
'--unsecure-port', '8080', '--secure-port', '8443', 'TKS i-dogtag 8443']' 
returned non-zero exit status 255.
    File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in 
main
  scriptlet.spawn(deployer)
    File 
"/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py",
 line 1038, in spawn
  subsystem.join_security_domain(
    File "/usr/lib/python3/dist-packages/pki/server/subsystem.py", line 1201, 
in join_security_domain
  subprocess.check_call(cmd)
    File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
  raise CalledProcessError(retcode, cmd)
  Installation failed: Command failed: pki -d /etc/pki/pki-tomcat/alias -f 
/etc/pki/pki-tomcat/password.conf -U https://i-dogtag:8443 securitydomain-join 
--session 4717921475119312283 --type TKS --hostname i-dogtag --unsecure-port 
8080 --secure-port 8443 TKS i-dogtag 8443
  Please check pkispawn logs in /var/log/pki/pki-tks-spawn.20210607093926.log

  Well one issue at a time ... the current install issue first.

  Since it worked with the nss in -release I was upgrading this to the new nss.
  ii  389-ds-base1.4.4.11-2  s390x389 Directo

[Touch-packages] [Bug 1931434] [NEW] Handling of ~/.XCompose broken in 21.04

[Jacco van Schaik]

Public bug reported:

When starting gvim on (X)Ubuntu 21.04 I get a long list of GTK3 error
messages. It starts with

include in Compose files not supported: include
"/usr/share/X11/locale/en_US.UTF-8/Compose"

and this is followed by a long list of messages like this:

Need to double-quote the value: "ಠ_ಠ" # LOOK OF DISAPPROVAL:
  : "ಠ_ಠ" # LOOK OF
DISAPPROVAL

... for every compose combo in the .XCompose file. I have attached the
offending .XCompose file.

This used to work in Ubuntu 20.10 but not anymore in 21.04.

I realize this is probably more a GTK3 error than a vim error, but this
is where I encountered it, and I could not find an obvious GTK3 package
to report this under.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: vim-gtk3 2:8.2.2434-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Wed Jun  9 13:41:16 2021
InstallationDate: Installed on 2017-02-04 (1586 days ago)
InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: vim
UpgradeStatus: Upgraded to hirsute on 2021-06-08 (0 days ago)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2017-06-24T17:37:24.020007

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


** Tags: amd64 apport-bug hirsute

** Attachment added: "The .XCompose file that causes the problem."
   https://bugs.launchpad.net/bugs/1931434/+attachment/5503523/+files/.XCompose

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

Title:
  Handling of ~/.XCompose broken in 21.04

Status in vim package in Ubuntu:
  New

Bug description:
  When starting gvim on (X)Ubuntu 21.04 I get a long list of GTK3 error
  messages. It starts with

  include in Compose files not supported: include
  "/usr/share/X11/locale/en_US.UTF-8/Compose"

  and this is followed by a long list of messages like this:

  Need to double-quote the value: "ಠ_ಠ" # LOOK OF DISAPPROVAL:
: "ಠ_ಠ" # LOOK OF
  DISAPPROVAL

  ... for every compose combo in the .XCompose file. I have attached the
  offending .XCompose file.

  This used to work in Ubuntu 20.10 but not anymore in 21.04.

  I realize this is probably more a GTK3 error than a vim error, but
  this is where I encountered it, and I could not find an obvious GTK3
  package to report this under.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: vim-gtk3 2:8.2.2434-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Wed Jun  9 13:41:16 2021
  InstallationDate: Installed on 2017-02-04 (1586 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: vim
  UpgradeStatus: Upgraded to hirsute on 2021-06-08 (0 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2017-06-24T17:37:24.020007

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

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

[Touch-packages] [Bug 1931394] Re: With glib2 2.68 gdebi is an FTBFS (hangs)

[Bug Watch Updater]

** Changed in: gdebi (Debian)
   Status: Unknown => New

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

Title:
  With glib2 2.68 gdebi is an FTBFS (hangs)

Status in gdebi package in Ubuntu:
  New
Status in gdebi package in Debian:
  New

Bug description:
  Ubuntu https://launchpad.net/ubuntu/+source/gdebi/0.9.5.7+nmu5 is an FTBFS
  
https://launchpadlibrarian.net/542966965/buildlog_ubuntu-impish-amd64.gdebi_0.9.5.7+nmu5_BUILDING.txt.gz

  The same https://launchpad.net/ubuntu/+source/gdebi/0.9.5.7+nmu4
  worked as it was builds against glib2.0 2.66 back in the day.

  Debian still works as they have 2.66 still
  
https://buildd.debian.org/status/fetch.php?pkg=gdebi&arch=all&ver=0.9.5.7%2Bnmu5&stamp=1621453414&raw=0


  At build time it is getting stuck until a timeout kills it:

  Log:
  ```
  running build_ext
  test_simple (tests.test_gdebi_gtk.GDebiGtkTestCase) ... WARNING:root:Error 
loading logo gtk-icon-theme-error-quark: Icon 'gnome-mime-application-x-deb' 
not present in theme Yaru (0)

  (setup.py:7825): Gtk-WARNING **: 05:55:50.408: Error loading theme icon 
'dialog-error' for stock: Icon 'dialog-error' not present in theme Yaru
  E: Build killed with signal TERM after 150 minutes of inactivity
  ```

  This is reproducible locally and the process tree looks like:

  F   UID     PID    PPID PRI  NI    VSZ   RSS WCHAN  STAT TTY        TIME 
COMMAND
  4     0   39842       0  20   0   9328  3000 do_wai Ss   pts/2      0:00 bash
  0     0   40835   39842  20   0  22136 13032 do_wai S+   pts/2      0:00  \_ 
/usr/bin/perl /usr/bin/debuild -i -us -uc -b
  0     0   40852   40835  20   0   7392   604 pipe_w S+   pts/2      0:00      
\_ tee ../gdebi_0.9.5.7+nmu5_amd64.build
  0     0   40853   40835  20   0  25328 16328 do_wai S+   pts/2      0:00      
\_ /usr/bin/perl /usr/bin/dpkg-buildpackage -us -uc -ui -i -b
  0     0   40891   40853  20   0   7764  1616 do_wai S+   pts/2      0:00      
    \_ /usr/bin/make -f debian/rules build
  0     0   40892   40891  20   0  24356 15260 do_wai S+   pts/2      0:00      
        \_ /usr/bin/perl /usr/bin/dh build --with python3 --buildsystem pybuild
  0     0   41533   40892  20   0   7764  1572 do_wai S+   pts/2      0:00      
            \_ /usr/bin/make -f debian/rules override_dh_auto_test
  0     0   41535   41533  20   0   2620  1320 do_wai S+   pts/2      0:00      
                \_ /bin/sh /usr/bin/xvfb-run -a python3.9 setup.py test
  4     0   41545   41535  20   0 1034648 37536 ep_pol Sl+ pts/2      0:00      
                    \_ Xvfb :99 -screen 0 1280x1024x24 -nolisten tcp -auth 
/tmp/xvfb-run.RlZdX8/Xauthority
  0     0   41560   41535  20   0 1331396 131060 poll_s Sl+ pts/2     0:01      
                    \_ python3.9 setup.py test

  
  From there the test is stuck.
  Some debugging revealed that it does no more come back from:
  GDebiGtkTestCase
   -> test_lintian
    -> GDebiGtk (init)
      -> gio_copy_in_place
        -> show_alert

  That alert only happens because we run as root, but even if that is avoided
  (e.g. by running as another user) then it blocks at the next message. E.g.
  when failing to download.

  But these blocking alerts are only secondary symptoms.

  I've found that all issues come back to a check that seems wrong.
  The test wants to copy a non-existing file into a temp path.
  At least the current version of Gio.File hates this and errors out
    g-io-error-quark: Operation not supported (15)

  Maybe Gio was more tolerant in the past, but checking a non existing
  file makes no sense anyway. We can guard that step a bit better than all 
works.

  A fix could look like:
  --- /home/ubuntu/gdebi-0.9.5.7+nmu5/GDebi/GDebiGtk.py 2021-06-09 
10:17:06.516869439 +
  +++ /root/gdebi-0.9.5.7+nmu5/GDebi/GDebiGtk.py 2021-06-09 10:09:35.113662314 
+
  @@ -119,7 +119,8 @@
                                    self.on_window_main_drag_data_received)
   
           # Check file with gio
  -        file = self.gio_copy_in_place(file)
  +        if file != "" and os.path.exists(file):
  +            file = self.gio_copy_in_place(file)
   
           #self.vte_terminal.set_font_from_string("monospace 10")
           self.cprogress = self.CacheProgressAdapter(self.progressbar_cache)

  I've proposed the same to the project [1], but I'm unsure about the speed this
  is picked up there.
  I've also filed this in Debian for them to be aware when the 2.68 switch 
happens.

  [1]: 
https://code.launchpad.net/~paelzer/gdebi/gdebi-fix-glib-2.68/+merge/403954
  [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989647

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

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

[Touch-packages] [Bug 1931394] [NEW] With glib2 2.68 gdebi is an FTBFS (hangs)

[Christian Ehrhardt ]

Public bug reported:

Ubuntu https://launchpad.net/ubuntu/+source/gdebi/0.9.5.7+nmu5 is an FTBFS
https://launchpadlibrarian.net/542966965/buildlog_ubuntu-impish-amd64.gdebi_0.9.5.7+nmu5_BUILDING.txt.gz

The same https://launchpad.net/ubuntu/+source/gdebi/0.9.5.7+nmu4 worked
as it was builds against glib2.0 2.66 back in the day.

Debian still works as they have 2.66 still
https://buildd.debian.org/status/fetch.php?pkg=gdebi&arch=all&ver=0.9.5.7%2Bnmu5&stamp=1621453414&raw=0


At build time it is getting stuck until a timeout kills it:

Log:
```
running build_ext
test_simple (tests.test_gdebi_gtk.GDebiGtkTestCase) ... WARNING:root:Error 
loading logo gtk-icon-theme-error-quark: Icon 'gnome-mime-application-x-deb' 
not present in theme Yaru (0)

(setup.py:7825): Gtk-WARNING **: 05:55:50.408: Error loading theme icon 
'dialog-error' for stock: Icon 'dialog-error' not present in theme Yaru
E: Build killed with signal TERM after 150 minutes of inactivity
```

This is reproducible locally and the process tree looks like:

F   UID     PID    PPID PRI  NI    VSZ   RSS WCHAN  STAT TTY        TIME COMMAND
4     0   39842       0  20   0   9328  3000 do_wai Ss   pts/2      0:00 bash
0     0   40835   39842  20   0  22136 13032 do_wai S+   pts/2      0:00  \_ 
/usr/bin/perl /usr/bin/debuild -i -us -uc -b
0     0   40852   40835  20   0   7392   604 pipe_w S+   pts/2      0:00      
\_ tee ../gdebi_0.9.5.7+nmu5_amd64.build
0     0   40853   40835  20   0  25328 16328 do_wai S+   pts/2      0:00      
\_ /usr/bin/perl /usr/bin/dpkg-buildpackage -us -uc -ui -i -b
0     0   40891   40853  20   0   7764  1616 do_wai S+   pts/2      0:00        
  \_ /usr/bin/make -f debian/rules build
0     0   40892   40891  20   0  24356 15260 do_wai S+   pts/2      0:00        
      \_ /usr/bin/perl /usr/bin/dh build --with python3 --buildsystem pybuild
0     0   41533   40892  20   0   7764  1572 do_wai S+   pts/2      0:00        
          \_ /usr/bin/make -f debian/rules override_dh_auto_test
0     0   41535   41533  20   0   2620  1320 do_wai S+   pts/2      0:00        
              \_ /bin/sh /usr/bin/xvfb-run -a python3.9 setup.py test
4     0   41545   41535  20   0 1034648 37536 ep_pol Sl+ pts/2      0:00        
                  \_ Xvfb :99 -screen 0 1280x1024x24 -nolisten tcp -auth 
/tmp/xvfb-run.RlZdX8/Xauthority
0     0   41560   41535  20   0 1331396 131060 poll_s Sl+ pts/2     0:01        
                  \_ python3.9 setup.py test


>From there the test is stuck.
Some debugging revealed that it does no more come back from:
GDebiGtkTestCase
 -> test_lintian
  -> GDebiGtk (init)
    -> gio_copy_in_place
      -> show_alert

That alert only happens because we run as root, but even if that is avoided
(e.g. by running as another user) then it blocks at the next message. E.g.
when failing to download.

But these blocking alerts are only secondary symptoms.

I've found that all issues come back to a check that seems wrong.
The test wants to copy a non-existing file into a temp path.
At least the current version of Gio.File hates this and errors out
  g-io-error-quark: Operation not supported (15)

Maybe Gio was more tolerant in the past, but checking a non existing
file makes no sense anyway. We can guard that step a bit better than all works.

A fix could look like:
--- /home/ubuntu/gdebi-0.9.5.7+nmu5/GDebi/GDebiGtk.py 2021-06-09 
10:17:06.516869439 +
+++ /root/gdebi-0.9.5.7+nmu5/GDebi/GDebiGtk.py 2021-06-09 10:09:35.113662314 
+
@@ -119,7 +119,8 @@
                                  self.on_window_main_drag_data_received)
 
         # Check file with gio
-        file = self.gio_copy_in_place(file)
+        if file != "" and os.path.exists(file):
+            file = self.gio_copy_in_place(file)
 
         #self.vte_terminal.set_font_from_string("monospace 10")
         self.cprogress = self.CacheProgressAdapter(self.progressbar_cache)

I've proposed the same to the project [1], but I'm unsure about the speed this
is picked up there.
I've also filed this in Debian for them to be aware when the 2.68 switch 
happens.

[1]: https://code.launchpad.net/~paelzer/gdebi/gdebi-fix-glib-2.68/+merge/403954
[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989647

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

** Affects: gdebi (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: update-excuse

** Summary changed:

- FTBFS
+ With glib2 2.68 gdebi is an FTBFS (hangs)

** Bug watch added: Debian Bug tracker #989647
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989647

** Also affects: gdebi (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989647
   Importance: Unknown
   Status: Unknown

** Tags added: update-excuse

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

Title:
  With glib2 2.68 gdebi is an FTBFS (hangs)

Status i

[Touch-packages] [Bug 1931387] [NEW] Ubuntu UI screen image freezes randomly during usage after fresh 21.04 install, suspecting Wayland

[Ciro Santilli 六四事件 法轮功]

Public bug reported:

Also submitted at: https://askubuntu.com/questions/1344736/ubuntu-ui-
freezes-randomly-after-fresh-21-04-install-suspecting-wayland

Let me know if there's any way to collect more useful information if
there is ever a future crash, or a better place to report.

I was running 20.10 previously with NVIDIA drivers,

Then four days ago, I did a clean 21.04 install without installing the
NVIDIA drivers, and since then the UI has frozen three times on my.

I am unable to determine exactly what action triggered the freeze.

The third time, I was just looking at a webpage, I wasn't even touching
my mouse at that exact moment, and then it just froze.

I am then unable to see anything move on the screen, including after
Ctrl + Alt + Fn, the last image just stays fixed.

The third time was also a bit different.

A few seconds after freezing, it actually went down to a black terminal
screen as during boot messages and then I was redirected to the login
screen, as if I had been logged out.

I was able to login, my programs were closed, so I was effectively
logged out.

Then two Apport windows showed up, and one of them contained several
references to Xwayland. Under `/var/crash/_usr_bin_Xwayland.1000.crash`
I see one of them:

- `ProcCmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth 
/run/user/1000/.mutter-Xwaylandauth.48ZQ40 -listen 4 -listen 5 -displayfd 6 
-initfd 7
- `StackTraceAddressSignature` contained mentions of Xwayland and 
nouveau_dri.so:

  ```
  StacktraceAddressSignature: 
/usr/bin/Xwayland:6:/usr/lib/x86_64-linux-gnu/libc-2.33.so+864:/usr/bin/Xwayland+13cb40:/usr/bin/Xwayland+14866f:/usr/bin/Xwayland+13b1a7:/usr/lib/x86_64-linux-gnu/libc-2.33.so+864:/usr/lib/x86_64-linux-gnu/libc-2.33.so+749:/usr/lib/x86_64-linux-gnu/libc-2.33.so+123d6:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+25d7:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+2537:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+265f:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+2a77:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+31aa:/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so+93b943:/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so+93bc61:/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so+17cc01
  ```

I also checked and I am using Wayland (the default since 21.04
apparently): https://askubuntu.com/questions/904940/how-can-i-tell-if-i
-am-running-wayland/1344287#1344287

Hardware:

- Lenovo ThinkPad P51
- NVIDIA Quadro M1200 4GB GDDR5 GPU

Just after the crash, dmesg contained the following possibly interesting
lines:

```
[ 9556.450894] nouveau :01:00.0: gr: TRAP ch 3 [00ff8cf000 Xwayland[3831]]
[ 9556.450907] nouveau :01:00.0: gr: GPC0/TPC2/MP trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp 3c000d [OOR_REG]
[ 9556.454264] nouveau :01:00.0: gr: TRAP ch 3 [00ff8cf000 Xwayland[3831]]
[ 9556.454283] nouveau :01:00.0: gr: GPC0/TPC0/MP trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp 3e000d [OOR_REG]
[ 9556.466339] nouveau :01:00.0: gr: TRAP ch 3 [00ff8cf000 Xwayland[3831]]
[ 9556.466351] nouveau :01:00.0: gr: GPC0/TPC3/MP trap: global 0004 
[MULTIPLE_WARP_ERRORS] warp 3e000d [OOR_REG]
[ 9698.230726] nouveau :01:00.0: Xwayland[3831]: failed to idle channel 5 
[Xwayland[3831]]
[ 9713.230743] nouveau :01:00.0: Xwayland[3831]: failed to idle channel 5 
[Xwayland[3831]]
[ 9713.231918] nouveau :01:00.0: fifo: fault 00 [READ] at 00056000 
engine 07 [HOST0] client 06 [HUB/HOST] reason 02 [PTE] on channel 5 [00ff0d9000 
Xwayland[3831]]
[ 9713.231930] nouveau :01:00.0: fifo: channel 5: killed
[ 9713.231932] nouveau :01:00.0: fifo: runlist 0: scheduled for recovery
[ 9713.231939] nouveau :01:00.0: fifo: engine 5: scheduled for recovery
[ 9713.231943] nouveau :01:00.0: Xwayland[3831]: channel 5 killed!
[ 9717.642691] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
[ 9717.642702] nouveau :01:00.0: fifo: runlist 0: scheduled for recovery
[ 9717.642709] nouveau :01:00.0: fifo: channel 3: killed
[ 9717.642714] nouveau :01:00.0: fifo: engine 0: scheduled for recovery
[ 9717.643113] nouveau :01:00.0: Xwayland[3831]: channel 3 killed!
[ 9719.351714] apport-gtk[119654]: segfault at 18 ip 7f337637d194 sp 
7ffd95094dc0 error 4 in libgtk-3.so.0.2404.21[7f3376274000+385000]
[ 9719.351721] Code: c4 08 5b 5d c3 90 f3 0f 1e fa 48 8b 7f 10 48 85 ff 74 0b 
e9 ce c6 ff ff 66 0f 1f 44 00 00 48 83 ec 08 48 89 d7 e8 0c 36 17 00 <48> 8b 40 
18 48 8b 78 10 e8 ef 03 09 00 48 83 c4 08 48 89 c7 e9 a3
[ 9744.187533] rfkill: input handler enabled
[ 9745.940823] rfkill: input handler disabled
[ 9775.737572] rfkill: input handler enabled
[ 9777.953055] rfkill: input handler disabled
```

Related:

- https://askubuntu.com/questions/1334177/ubuntu-21-04-wayland-gimp-
black-window GIMP works fine

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

-- 
You received this bug notification because you are a member of Ubun

[Touch-packages] [Bug 1370953] Re: layout switch is delayed

[Denis Oleksiuk]

This bug still in ubuntu 20.04 :

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

Title:
  layout switch is delayed

Status in console-setup package in Ubuntu:
  Confirmed
Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+subscriptions

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

[Touch-packages] [Bug 1930409] Re: Pulseaudio 14.2 says: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ...

[rud]

Thanks, i tried that, still nothing happens and nothing new appears in 
https://errors.ubuntu.com/user/ID 
But going through the info shown when I use ubuntu-bug, I can confirm this 
crash on 2 different systems and it is about: "xorg crashed with sigabrt in 
osabort()" 
- The mentioned Intel C246 chipset with Core i3-9100, no dedicated GPU.
- Lenovo S540 AMD Ryzen 4800U laptop (no dedicated GPU).

I don't notice the crash during or after install btw. I only see the popup 
after a reboot.
In both cases it only happens once after clean install, if I remove the crash 
file, no new crash file is created after reboots.

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

Title:
  Pulseaudio 14.2 says: GetManagedObjects() failed:
  org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ...

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Not sure if the bluez error is related, perhaps not (this is a desktop
  without Wifi/Bluetooth).

  jun 01 12:46:30 Obelix dbus-daemon[1070]: [system] Failed to activate service 
'org.bluez': timed out (service_start_timeout=25000ms)
  jun 01 12:46:30 Obelix pulseaudio[1749]: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired,>

  Intel i3-9100, C246 chipset, 32GB ram.

  Ubuntu Budgie 21.04 installed via usb boot disk.

  It gives me a popup "error occured" every time I reboot..

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: pulseaudio 1:14.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asterix1749 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Tue Jun  1 12:48:36 2021
  InstallationDate: Installed on 2021-05-11 (21 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.release: 1.6
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.13 R1.6.0 for D3644-B1x
  dmi.board.name: D3644-B1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3644-B1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.13R1.6.0forD3644-B1x:bd05/15/2019:br1.6:svnFUJITSU:pn:pvr:rvnFUJITSU:rnD3644-B1:rvrS26361-D3644-B1:cvnFUJITSU:ct3:cvr:
  dmi.product.family: OEM-FTS
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1929647] Re: debian helper tools for python never updates

[pleabargain]

still cannot select
cannot upgrade

** Attachment added: "cannotPeek 2021-06-09 10-43.gif"
   
https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1929647/+attachment/5503427/+files/cannotPeek%202021-06-09%2010-43.gif

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

Title:
  debian helper tools for python never updates

Status in python-debian package in Ubuntu:
  New

Bug description:
  software updater prompts new updates
  debian helper tools for python is always one of them but I cannot select the 
checkbox
  so

  debian helper tools for python never updates


  Here's the screen shot
  https://i.imgur.com/AjDd5yo.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1929647/+subscriptions

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

[Touch-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

[Timo Aaltonen]

21.04 comes with Mesa 21.0.1 which does not seem to have 820dec3f7c7

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

Title:
  linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0]
  retry page fault"

Status in amd:
  New
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New

Bug description:
  After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the
  upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent
  and severe GPU instability. When this happens, I see this error in
  dmesg:

  [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault 
(src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 
pid 1236)
  [20061.061103] amdgpu :03:00.0: amdgpu:   in page starting at address 
0x80401000 from client 27
  [20061.061135] amdgpu :03:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00101031
  [20061.061147] amdgpu :03:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [20061.061157] amdgpu :03:00.0: amdgpu:  MORE_FAULTS: 0x1
  [20061.061167] amdgpu :03:00.0: amdgpu:  WALKER_ERROR: 0x0
  [20061.061174] amdgpu :03:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [20061.061183] amdgpu :03:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [20061.061189] amdgpu :03:00.0: amdgpu:  RW: 0x0

  I'll attach a couple of full dmesgs that I collected.

  Many of the times when this happens, the screen and keyboard freeze
  irreversibly (I tried waiting for more than 30 minutes, but it doesn't
  help). I can still log in via ssh though. When there's no freeze, I
  can continue using the computer normally, but the laptop fans keep
  running are always running and the battery depletes fast. There's
  probably something on a permanent loop either in the kernel or in the
  GPU.

  This bug happens several times a day, rendering the machine so
  unstable as to be almost unusable. It is a severe regression and I'm
  aghast that it passed AMD's Quality Assurance.

  After downgrading back to linux-firmware 1.190.5, the machine is back
  to the previous, mostly-reliable state. Which is to say, this bug is
  gone, I'm just left with the other amdgpu suspend bug I've learned to
  live with since I bought this computer.

  Please revert the amdgpu firmware in this package as soon as possible.
  This is unbearable.

  Relevant information:
  Ubuntu version: 21.04
  Linux kernel: 5.11.0-17-generic x86_64
  CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx
  GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Picasso (rev c1)
  Laptop model: Lenovo Ideapad S145

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

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

[Touch-packages] [Bug 1925795] Re: SRU the current 0.20.4 stable update

[Chris Halse Rogers]

Hey Seb! This is a candidate for release into -updates, but I don't
think we can do that while it supersedes any package in Groovy.

I understand that the Desktop team has constrained resources. The SRU
team intends to propose a policy change to help, but for now could you
please do a Groovy upload too?

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

Title:
  SRU the current 0.20.4 stable update

Status in libsecret package in Ubuntu:
  Fix Released
Status in libsecret source package in Focal:
  Fix Committed

Bug description:
  * Impact

  That's the current GNOME stable update, including some bugfixes and 
translation updates
  https://gitlab.gnome.org/GNOME/libsecret/-/blob/master/NEWS

  There are non trivial changes to the meson build system included in
  the update but we still build using autotools so that's not impacting
  us

  
  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Libsecret is providing an API to access gnome-keyring secrets, try a few 
applications using it and make sure credentials are correctly available. To 
list a few possible candidate softwares
  - evince (try to open a a password protected pdf, it should store and 
remember the password)
  - evolution
  - epiphany-browser 
  - vinagre
  - balsa
  - deja-dup

  * Regression potential

  Nothing specific to try in those changes, just ensure the library
  still access the passwords as expected

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

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