[Touch-packages] [Bug 2061257] Re: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg

[Martin D. Weinberg]

I also tried removing the Mesa Vulkan driver and set `export
LIBVA_DRIVER_NAME=i965`.  That gets rid of the warning message but I
still get a hang with Vivaldi and nextcloud-desktop still does not work.

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

Title:
  After 24.04 upgrade, many graphical app failures under Wayland; no
  issues with Xorg

Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  Many applications seem to fail under a Wayland session that work correctly 
with an Xorg session. E.g.
  - The nextcloud client app fails to contact the server and functions in the 
app will not launch with Wayland while they work perfectly in Xorg
  - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support 
is incomplete
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed.  It 
works correctly under Xorg.
  - The Slack app works correct in Xorg not in Wayland.
  - The Firefox snap works fine in both.

  I assume that these are related?  Esp. that latter suggests to me that
  there is some library problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 19:58:00 2024
  DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2021-11-11 (885 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20ARA0S100
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.release: 2.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARA0S100
  dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2061257/+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 2061257] Re: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg

[Martin D. Weinberg]

Thanks. Sounds similar.  My nautilus and gnome-control center do work
strangely enough.   But the more clues the better.

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

Title:
  After 24.04 upgrade, many graphical app failures under Wayland; no
  issues with Xorg

Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  Many applications seem to fail under a Wayland session that work correctly 
with an Xorg session. E.g.
  - The nextcloud client app fails to contact the server and functions in the 
app will not launch with Wayland while they work perfectly in Xorg
  - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support 
is incomplete
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed.  It 
works correctly under Xorg.
  - The Slack app works correct in Xorg not in Wayland.
  - The Firefox snap works fine in both.

  I assume that these are related?  Esp. that latter suggests to me that
  there is some library problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 19:58:00 2024
  DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2021-11-11 (885 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20ARA0S100
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.release: 2.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARA0S100
  dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2061257/+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 2061257] Re: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg

[Martin D. Weinberg]

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

** Project changed: wayland => wayland (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/2061257

Title:
  After 24.04 upgrade, many graphical app failures under Wayland; no
  issues with Xorg

Status in wayland package in Ubuntu:
  New

Bug description:
  Many applications seem to fail under a Wayland session that work correctly 
with an Xorg session. E.g.
  - The nextcloud client app fails to contact the server and functions in the 
app will not launch with Wayland while they work perfectly in Xorg
  - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support 
is incomplete
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed.  It 
works correctly under Xorg.
  - The Slack app works correct in Xorg not in Wayland.
  - The Firefox snap works fine in both.

  I assume that these are related?  Esp. that latter suggests to me that
  there is some library problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 19:58:00 2024
  DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2021-11-11 (885 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20ARA0S100
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.release: 2.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARA0S100
  dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2061257/+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 2061257] Re: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg

[Martin D. Weinberg]

I tried the same upgrade and test on an old Sandy Bridge laptop.
Everything works as expected there.  So a Haswell issue perhaps?

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

Title:
  After 24.04 upgrade, many graphical app failures under Wayland; no
  issues with Xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  Many applications seem to fail under a Wayland session that work correctly 
with an Xorg session. E.g.
  - The nextcloud client app fails to contact the server and functions in the 
app will not launch with Wayland while they work perfectly in Xorg
  - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support 
is incomplete
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed.  It 
works correctly under Xorg.
  - The Slack app works correct in Xorg not in Wayland.
  - The Firefox snap works fine in both.

  I assume that these are related?  Esp. that latter suggests to me that
  there is some library problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 19:58:00 2024
  DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2021-11-11 (885 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20ARA0S100
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.release: 2.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARA0S100
  dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2061257/+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 2061257] Re: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg

[Martin D. Weinberg]

I tried the same test on an old Sandy Bridge laptop.  Everything works
as expected there.  So a Haswell issue?

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

Title:
  After 24.04 upgrade, many graphical app failures under Wayland; no
  issues with Xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  Many applications seem to fail under a Wayland session that work correctly 
with an Xorg session. E.g.
  - The nextcloud client app fails to contact the server and functions in the 
app will not launch with Wayland while they work perfectly in Xorg
  - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support 
is incomplete
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed.  It 
works correctly under Xorg.
  - The Slack app works correct in Xorg not in Wayland.
  - The Firefox snap works fine in both.

  I assume that these are related?  Esp. that latter suggests to me that
  there is some library problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 19:58:00 2024
  DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2021-11-11 (885 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20ARA0S100
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.release: 2.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARA0S100
  dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2061257/+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 2061257] Re: With 24.04: Many graphical app failures under Wayland; no issues with Xorg

[Martin D. Weinberg]

** Summary changed:

- Many app failures under Wayland; no  issues with Xorg
+ With 24.04: Many graphical app failures under Wayland; no  issues with Xorg

** Summary changed:

- With 24.04: Many graphical app failures under Wayland; no  issues with Xorg
+ After 24.04 upgrade, many graphical app failures under Wayland; no  issues 
with Xorg

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

Title:
  After 24.04 upgrade, many graphical app failures under Wayland; no
  issues with Xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  Many applications seem to fail under a Wayland session that work correctly 
with an Xorg session. E.g.
  - The nextcloud client app fails to contact the server and functions in the 
app will not launch with Wayland while they work perfectly in Xorg
  - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support 
is incomplete
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed.  It 
works correctly under Xorg.
  - The Slack app works correct in Xorg not in Wayland.
  - The Firefox snap works fine in both.

  I assume that these are related?  Esp. that latter suggests to me that
  there is some library problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 19:58:00 2024
  DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2021-11-11 (885 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20ARA0S100
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.release: 2.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARA0S100
  dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2061257/+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 2061257] [NEW] Many app failures under Wayland; no issues with Xorg

[Martin D. Weinberg]

Public bug reported:

Many applications seem to fail under a Wayland session that work correctly with 
an Xorg session. E.g.
- The nextcloud client app fails to contact the server and functions in the app 
will not launch with Wayland while they work perfectly in Xorg
- The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support 
is incomplete
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed.  It 
works correctly under Xorg.
- The Slack app works correct in Xorg not in Wayland.
- The Firefox snap works fine in both.

I assume that these are related?  Esp. that latter suggests to me that
there is some library problem?

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 13 19:58:00 2024
DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources()
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
InstallationDate: Installed on 2021-11-11 (885 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20ARA0S100
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
dmi.bios.date: 03/19/2014
dmi.bios.release: 2.24
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET74WW (2.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20ARA0S100
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.ec.firmware.release: 1.9
dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s:
dmi.product.family: ThinkPad T440s
dmi.product.name: 20ARA0S100
dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug noble 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/2061257

Title:
  Many app failures under Wayland; no  issues with Xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  Many applications seem to fail under a Wayland session that work correctly 
with an Xorg session. E.g.
  - The nextcloud client app fails to contact the server and functions in the 
app will not launch with Wayland while they work perfectly in Xorg
  - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support 
is incomplete
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed.  It 
works correctly under Xorg.
  - The Slack app works correct in Xorg not in Wayland.
  - The Firefox snap works fine in both.

  I assume that these are related?  Esp. that latter suggests to me that
  there is some library problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 19:58:00 2024
  DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 

[Touch-packages] [Bug 2061257] Re: Many app failures under Wayland; no issues with Xorg

[Martin D. Weinberg]

I should also mention: this was an upgrade from 23.10 to 24.04 and all
of the apps worked correctly in 23.10.

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

Title:
  Many app failures under Wayland; no  issues with Xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  Many applications seem to fail under a Wayland session that work correctly 
with an Xorg session. E.g.
  - The nextcloud client app fails to contact the server and functions in the 
app will not launch with Wayland while they work perfectly in Xorg
  - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support 
is incomplete
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed.  It 
works correctly under Xorg.
  - The Slack app works correct in Xorg not in Wayland.
  - The Firefox snap works fine in both.

  I assume that these are related?  Esp. that latter suggests to me that
  there is some library problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 19:58:00 2024
  DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2021-11-11 (885 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20ARA0S100
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.release: 2.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARA0S100
  dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2061257/+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 2053235] [NEW] Upgrade libwayland on ubuntu 22.04.3 LTS

[Maniraj D]

Public bug reported:

We look to use / upgrade to Weston 13.0 on Ubuntu 22.04.3 LTS. We see
the following Weston-13.0 dependencies are not met for the same.

libwayland*: required version >= 1.22.0

So we request to upgrade these packages on Ubuntu 22.04.3 LTS.

The release of Ubuntu we are using:
  - Ubuntu 22.04.3 LTS

Current version of the libwayland* packages:
  - libwayland-bin/now 1.20.0-1ubuntu0.1 arm64 [installed,local]
  - libwayland-client0/now 1.20.0-1ubuntu0.1 arm64 [installed,local]
  - libwayland-cursor0/now 1.20.0-1ubuntu0.1 arm64 [installed,local]
  - libwayland-dev/now 1.20.0-1ubuntu0.1 arm64 [installed,local]
  - libwayland-egl1/now 1.20.0-1ubuntu0.1 arm64 [installed,local]
  - libwayland-server0/now 1.20.0-1ubuntu0.1 arm64 [installed,local]

What we expect to happen:
  - We want the upgrade of libwayland* packages to 1.22.0 on Ubuntu 22.04.3 LTS.

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

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

Title:
  Upgrade libwayland on ubuntu 22.04.3 LTS

Status in wayland package in Ubuntu:
  New

Bug description:
  We look to use / upgrade to Weston 13.0 on Ubuntu 22.04.3 LTS. We see
  the following Weston-13.0 dependencies are not met for the same.

  libwayland*: required version >= 1.22.0

  So we request to upgrade these packages on Ubuntu 22.04.3 LTS.

  The release of Ubuntu we are using:
- Ubuntu 22.04.3 LTS

  Current version of the libwayland* packages:
- libwayland-bin/now 1.20.0-1ubuntu0.1 arm64 [installed,local]
- libwayland-client0/now 1.20.0-1ubuntu0.1 arm64 [installed,local]
- libwayland-cursor0/now 1.20.0-1ubuntu0.1 arm64 [installed,local]
- libwayland-dev/now 1.20.0-1ubuntu0.1 arm64 [installed,local]
- libwayland-egl1/now 1.20.0-1ubuntu0.1 arm64 [installed,local]
- libwayland-server0/now 1.20.0-1ubuntu0.1 arm64 [installed,local]

  What we expect to happen:
- We want the upgrade of libwayland* packages to 1.22.0 on Ubuntu 22.04.3 
LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2053235/+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 1878617] Re: Apple pages file type should be added to MIME types

[David D Lowe]

Fantastic! I can confirm that this is fixed on Ubuntu 23.10.

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

Title:
  Apple pages file type should be added to MIME types

Status in shared-mime-info:
  Fix Released
Status in mime-support package in Ubuntu:
  Invalid
Status in shared-mime-info package in Ubuntu:
  Fix Released

Bug description:
  LibreOffice can open .pages files (from Apple pages). However, the
  mime type for these files is incorrectly just application/zip:

  $ file --mime-type example.pages
  example.pages: application/zip

  Instead, it should be application/vnd.apple.pages .

  This would allow the user to associate LibreOffice Writer with these
  types of files, and use it to open this file. (LibreOffice Writer can
  open .pages files)

  Apple Keynote files should have this MIME type:
  application/vnd.apple.keynote

  Apple Numbers files should have this MIME type:
  application/vnd.apple.numbers

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mime-support 3.64ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 14:46:40 2020
  InstallationDate: Installed on 2018-11-11 (550 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: mime-support
  UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1878617/+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 1771041] Re: Remove gconf from Ubuntu

[David D Lowe]

ooo-thumbnailer is an abandoned project and is being removed from
Debian. Project link: https://launchpad.net/ooo-thumbnailer

** Changed in: ooo-thumbnailer (Ubuntu)
   Status: New => Invalid

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

Title:
  Remove gconf from Ubuntu

Status in desktopnova package in Ubuntu:
  New
Status in evolution-indicator package in Ubuntu:
  Fix Released
Status in gconf package in Ubuntu:
  New
Status in gconf-editor package in Ubuntu:
  New
Status in gkdebconf package in Ubuntu:
  New
Status in gnome-mastermind package in Ubuntu:
  New
Status in gnome-phone-manager package in Ubuntu:
  New
Status in gnome-xcf-thumbnailer package in Ubuntu:
  New
Status in gnomint package in Ubuntu:
  New
Status in gtkwave package in Ubuntu:
  Fix Released
Status in guake-indicator package in Ubuntu:
  New
Status in gyrus package in Ubuntu:
  Fix Released
Status in jack-mixer package in Ubuntu:
  Fix Released
Status in jana package in Ubuntu:
  New
Status in mssh package in Ubuntu:
  New
Status in ogmrip package in Ubuntu:
  New
Status in ooo-thumbnailer package in Ubuntu:
  Invalid
Status in planner package in Ubuntu:
  New
Status in ogmrip package in Debian:
  Fix Released

Bug description:
  gconf is being removed from Debian Testing. We should remove it from
  Ubuntu also.

  eclipse is troublesome. At a minimum, we can remove everything but
  eclipse and gconf.

  libgnome is sort of a blocker so do it first LP: #1771031
  And remove libqt-gconf LP: #1740538

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktopnova/+bug/1771041/+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 2013072] [NEW] Missing symlink /sbin/resolvconf -> /bin/resolvectl makes openfortivpn mess with /etc/resolv.conf

[D]

Public bug reported:

In jammy (22.04) and focal (20.04) the executable /usr/bin/resolvectl is
provided by the package "systemd". If you install the packages libnss-
resolve and openfortivpn and run "openfortivpn vpn.example.com -u user
-v" you get undesired behavior:

[...]
INFO:   Adding VPN nameservers...
DEBUG:  Attempting to modify /etc/resolv.conf directly.
DEBUG:  Adding "nameserver 10.10.10.10", to /etc/resolv.conf.
DEBUG:  Adding "search ~10.in-addr.arpa ~example.com", to /etc/resolv.conf.
[...]

resolvectl can emulate the behavior of resolvconf so if you create a
symbolic link "sudo ln -s /usr/bin/resolvectl /sbin/resolvconf" then
openfortivpn happily uses resolvconf instead of messing with
/etc/resolv.conf:

[...]
INFO:   Adding VPN nameservers...
DEBUG:  Attempting to run /sbin/resolvconf.
DEBUG:  resolvconf_call: /sbin/resolvconf -a "ppp0.openfortivpn"
[...]

So it would be great if the symlink could be included in the package
"systemd". Thank you.

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

Title:
  Missing symlink /sbin/resolvconf -> /bin/resolvectl makes openfortivpn
  mess with /etc/resolv.conf

Status in systemd package in Ubuntu:
  New

Bug description:
  In jammy (22.04) and focal (20.04) the executable /usr/bin/resolvectl
  is provided by the package "systemd". If you install the packages
  libnss-resolve and openfortivpn and run "openfortivpn vpn.example.com
  -u user -v" you get undesired behavior:

  [...]
  INFO:   Adding VPN nameservers...
  DEBUG:  Attempting to modify /etc/resolv.conf directly.
  DEBUG:  Adding "nameserver 10.10.10.10", to /etc/resolv.conf.
  DEBUG:  Adding "search ~10.in-addr.arpa ~example.com", to /etc/resolv.conf.
  [...]

  resolvectl can emulate the behavior of resolvconf so if you create a
  symbolic link "sudo ln -s /usr/bin/resolvectl /sbin/resolvconf" then
  openfortivpn happily uses resolvconf instead of messing with
  /etc/resolv.conf:

  [...]
  INFO:   Adding VPN nameservers...
  DEBUG:  Attempting to run /sbin/resolvconf.
  DEBUG:  resolvconf_call: /sbin/resolvconf -a "ppp0.openfortivpn"
  [...]

  So it would be great if the symlink could be included in the package
  "systemd". Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2013072/+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 1987631] Re: Screencast only records one second

[Matthew D. Mower]

It seems like this has stalled again and I don't understand why. Patches
were posted about 1 month ago and they got some testing feedback within
2 days of availability.

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

Title:
  Screencast only records one second

Status in GNOME Shell:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  New
Status in gstreamer1.0 package in Ubuntu:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  Fix Released
Status in gst-plugins-base1.0 source package in Jammy:
  New
Status in gstreamer1.0 source package in Jammy:
  New
Status in pipewire source package in Jammy:
  Confirmed

Bug description:
  [Impact]
  When recording a screencast with gnome on kinetic the resulting video will 
play for one second and then freeze. It looks like the same bug was discussed 
upstream at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585

  This issue is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed 
the Cheese preview stuck issue on jammy
* d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch
  d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch
  - Camera output freeze when using pipewiresrc (LP: #1985057)

  Here is a comment from 
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057/comments/51 .
  ===
  So that's a regression of one of the cherrypicked commits, details are in 
https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488

  the issue is fixed in Kinetic through a combination of the shell fix
  and a new pipewire.

  In 22.04 the shell issue is fixed in the recent 42.5 update but we will need 
to cherrypick 
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 in pipewire 
to be working.
  ===

  [Test Plan]
  1. Install Jammy on the hardware issue reported, and hardware didn't report 
the issue to avoid the regression
 hardware list:
 a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD
 b. 0c45:6747 Microdia Integrated_Webcam_HD
 c. 0c45:6a14 Microdia Integrated_Webcam_HD
 d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M
 e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera
 f. 0408:545a Quanta Computer, Inc. HP 5MP Camera
 g. 0408:5483 Quanta Computer, Inc. HP HD Camera
 h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4)
 i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a)
 j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD
  2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2)
  3. $ sudo reboot
  4. Check if gst-launch-1.0 work
 a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest 
gst-launch-1.0 command
 b. $ gst-launch-1.0 pipewiresrc path= !  ! decodebin ! 
videoconvert ! glimagesink
 c. Check if the result ok
  5. Check the screencast function by pressing 'prt sc'
 a. the screenshot of all screen/selected region should work good
 b. the screenrecord of all screen/selected region should work good
  6. Check that video recording in gnome-shell works
 - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, 
verify that there is a new entry in ~/Video
  7. Check that screen sharing is working
 - go to settings, screen sharing and enable the feature
 - try to connect using rdp/vnc from another client

  do those steps under wayland and unset X

  [Where problems could occur]
  The patches try to dequeue the shared buffer, instead of pool buffer to 
prevent the pool buffer being corrupted. it might cause some camera preview 
failed if shared buffer is corrupted.
  It is from upstream and there is no regression found, so the risk is low.

  [Other Info]
  Upstream commits for pipewire:
  
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92
  
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f
  
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525c1ac946a915599c6bee813e88e8cee12
  Upstream commits for gstreamer:
  
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/3b900e1fa4fd888012dc005fa26ae2532a89b7a7

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 2002098] [NEW] Seems like my GPU isn't supported

[Walid D]

Public bug reported:

(base) walid@len:~$ lspci | grep VGA
:00:02.0 VGA compatible controller: Intel Corporation Device 9a78 (rev 01)
(base) walid@len:~$ sudo lshw -C video
[sudo] password for walid: 
  *-display 
   description: VGA compatible controller
   product: Intel Corporation
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   logical name: /dev/fb0
   version: 01
   width: 64 bits
   clock: 33MHz
   capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
   configuration: depth=32 driver=i915 latency=0 mode=1920x1080 
resolution=1920,1080 visual=truecolor xres=1920 yres=1080
   resources: iomemory:600-5ff iomemory:400-3ff irq:158 
memory:600200-6002ff memory:40-400fff ioport:3000(size=64) 
memory:c-d memory:401000-4016ff memory:402000-40
(base) walid@len:~$ lspci -nn |egrep "VGA|Display"
:00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9a78] (rev 01)
(base) walid@len:~$ sudo apt-get install xserver-xorg-video-intel
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
xserver-xorg-video-intel is already the newest version 
(2:2.99.917+git20210115-1).
xserver-xorg-video-intel set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
Uname: Linux 5.15.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan  6 11:30:53 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:9a78] (rev 01) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3f89]
MachineType: LENOVO 82FG
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=f5b7aa1d-e67f-4b72-8621-88ab6b130991 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/26/2021
dmi.bios.release: 1.59
dmi.bios.vendor: LENOVO
dmi.bios.version: FHCN59WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32866 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad 5 15ITL05
dmi.ec.firmware.release: 1.59
dmi.modalias: 
dmi:bvnLENOVO:bvrFHCN59WW:bd08/26/2021:br1.59:efr1.59:svnLENOVO:pn82FG:pvrIdeaPad515ITL05:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrIdeaPad515ITL05:skuLENOVO_MT_82FG_BU_idea_FM_IdeaPad515ITL05:
dmi.product.family: IdeaPad 5 15ITL05
dmi.product.name: 82FG
dmi.product.sku: LENOVO_MT_82FG_BU_idea_FM_IdeaPad 5 15ITL05
dmi.product.version: IdeaPad 5 15ITL05
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy 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/2002098

Title:
  Seems like my GPU isn't supported

Status in xorg package in Ubuntu:
  New

Bug description:
  (base) walid@len:~$ lspci | grep VGA
  :00:02.0 VGA compatible controller: Intel Corporation Device 9a78 (rev 01)
  (base) walid@len:~$ sudo lshw -C video
  [sudo] password for walid: 
*-display 
 description: VGA compatible controller
 product: Intel Corporation
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 logical name: /dev/fb0
 version: 01
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm vga_controller bus_master cap_list rom 
fb
 configuration: depth=32 driver=i915 latency=0 mode=1920x1080 
resolution=1920,1080 visual=truecolor xres=1920 yres=1080
 resources: iomemory:600-5ff iomemory:400-3ff irq:158 
memory:600200-6002ff memory:40-400fff ioport:3000(size=64) 

[Touch-packages] [Bug 1987631] Re: Screencast only records one second

[Matthew D. Mower]

@binli - here are my testing results with patches:
- gstreamer1.0_1.20.3-0ubuntu2.debdiff
- gst-plugins-base1.0_1.20.1-2.debdiff
- pipewire_0.3.48-1ubuntu4.debdiff

Gnome Shell screen recorder: pass
gst-launch-1.0 video preview: pass
Gnome Shell screen recorder while gst-launch-1.0 video preview is visible: pass
Cheese video preview: pass*

Cheese has an asterisk* because I ran into other problems: 1)
intermittently, selecting a filter can freeze the preview until a
different filter is selected. 2) lp:1994928

Camera hardware tested (two different computers):
13d3:5405 IMC Networks Integrated Camera (Lenovo T14s Gen2 AMD Laptop)
046d:082d Logitech, Inc. HD Pro Webcam C920

-

Details of how I built the packages and which ones I installed. Note
that I only installed packages that are part of a default Ubuntu jammy
installation: http://releases.ubuntu.com/jammy/ubuntu-22.04.1-desktop-
amd64.manifest .

$ wget 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987631/+attachment/5638524/+files/gstreamer1.0_1.20.3-0ubuntu2.debdiff
$ wget 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987631/+attachment/5638525/+files/gst-plugins-base1.0_1.20.1-2.debdiff
$ wget 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1987631/+attachment/5638528/+files/pipewire_0.3.48-1ubuntu4.debdiff

$ pull-lp-source gstreamer1.0 1.20.3-0ubuntu1
$ pull-lp-source gst-plugins-base1.0 1.20.1-1
$ pull-lp-source pipewire 0.3.48-1ubuntu3

$ patch -p1 -d gstreamer1.0-1.20.3 < gstreamer1.0_1.20.3-0ubuntu2.debdiff
$ patch -p1 -d gst-plugins-base1.0-1.20.1 < gst-plugins-base1.0_1.20.1-2.debdiff
$ patch -p1 -d pipewire-0.3.48 < pipewire_0.3.48-1ubuntu4.debdiff

$ sudo apt-get build-dep gstreamer1.0 gst-plugins-base1.0 pipewire

$ cd gstreamer1.0
$ dpkg-buildpackage -rfakeroot -b
$ cdu ..
$ sudo dpkg -i gir1.2-gstreamer-1.0_1.20.3-0ubuntu2_amd64.deb 
gstreamer1.0-tools_1.20.3-0ubuntu2_amd64.deb 
libgstreamer1.0-0_1.20.3-0ubuntu2_amd64.deb 
libgstreamer1.0-dev_1.20.3-0ubuntu2_amd64.deb

$ cd gst-plugins-base1.0-1.20.1
$ dpkg-buildpackage -rfakeroot -b
$ cdu ..
$ sudo dpkg -i gir1.2-gst-plugins-base-1.0_1.20.1-2_amd64.deb 
gstreamer1.0-alsa_1.20.1-2_amd64.deb gstreamer1.0-gl_1.20.1-2_amd64.deb 
gstreamer1.0-plugins-base_1.20.1-2_amd64.deb 
gstreamer1.0-plugins-base-apps_1.20.1-2_amd64.deb 
gstreamer1.0-x_1.20.1-2_amd64.deb libgstreamer-gl1.0-0_1.20.1-2_amd64.deb 
libgstreamer-plugins-base1.0-0_1.20.1-2_amd64.deb

$ cd pipewire-0.3.48
$ dpkg-buildpackage -rfakeroot -b
$ cd ..
$ sudo dpkg -i gstreamer1.0-pipewire_0.3.48-1ubuntu4_amd64.deb 
libpipewire-0.3-0_0.3.48-1ubuntu4_amd64.deb 
libpipewire-0.3-common_0.3.48-1ubuntu4_all.deb 
libpipewire-0.3-modules_0.3.48-1ubuntu4_amd64.deb 
libspa-0.2-modules_0.3.48-1ubuntu4_amd64.deb pipewire_0.3.48-1ubuntu4_amd64.deb 
pipewire-bin_0.3.48-1ubuntu4_amd64.deb

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

Title:
  Screencast only records one second

Status in GNOME Shell:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  New
Status in gstreamer1.0 package in Ubuntu:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  Fix Released
Status in gst-plugins-base1.0 source package in Jammy:
  New
Status in gstreamer1.0 source package in Jammy:
  New
Status in pipewire source package in Jammy:
  Confirmed

Bug description:
  [Impact]
  When recording a screencast with gnome on kinetic the resulting video will 
play for one second and then freeze. It looks like the same bug was discussed 
upstream at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585

  This issue is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed 
the Cheese preview stuck issue on jammy
* d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch
  d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch
  - Camera output freeze when using pipewiresrc (LP: #1985057)

  Here is a comment from 
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057/comments/51 .
  ===
  So that's a regression of one of the cherrypicked commits, details are in 
https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488

  the issue is fixed in Kinetic through a combination of the shell fix
  and a new pipewire.

  In 22.04 the shell issue is fixed in the recent 42.5 update but we will need 
to cherrypick 
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 in pipewire 
to be working.
  ===

  [Test Plan]
  1. Install Jammy on the hardware issue reported, and hardware didn't report 
the issue to avoid the regression
 hardware list:
 a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD
 b. 0c45:6747

[Touch-packages] [Bug 1987631] Re: Screencast only records one second

[Matthew D. Mower]

@binli - I'm still on pipewire from jammy-updates:

$ apt-cache policy pipewire
pipewire:
  Installed: 0.3.48-1ubuntu2
  Candidate: 0.3.48-1ubuntu2
  Version table:
 *** 0.3.48-1ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 0.3.48-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

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

Title:
  Screencast only records one second

Status in GNOME Shell:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  New
Status in gstreamer1.0 package in Ubuntu:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  Fix Released
Status in gst-plugins-base1.0 source package in Jammy:
  New
Status in gstreamer1.0 source package in Jammy:
  New
Status in pipewire source package in Jammy:
  Confirmed

Bug description:
  [Impact]
  When recording a screencast with gnome on kinetic the resulting video will 
play for one second and then freeze. It looks like the same bug was discussed 
upstream at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585

  This issue is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed 
the Cheese preview stuck issue on jammy
* d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch
  d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch
  - Camera output freeze when using pipewiresrc (LP: #1985057)

  Here is a comment from 
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057/comments/51 .
  ===
  So that's a regression of one of the cherrypicked commits, details are in 
https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488

  the issue is fixed in Kinetic through a combination of the shell fix
  and a new pipewire.

  In 22.04 the shell issue is fixed in the recent 42.5 update but we will need 
to cherrypick 
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 in pipewire 
to be working.
  ===

  [Test Plan]
  1. Install Jammy on the hardware issue reported, and hardware didn't report 
the issue to avoid the regression
 hardware list:
 a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD
 b. 0c45:6747 Microdia Integrated_Webcam_HD
 c. 0c45:6a14 Microdia Integrated_Webcam_HD
 d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M
 e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera
 f. 0408:545a Quanta Computer, Inc. HP 5MP Camera
 g. 0408:5483 Quanta Computer, Inc. HP HD Camera
 h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4)
 i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a)
 j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD
  2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2)
  3. $ sudo reboot
  4. Check if gst-launch-1.0 work
 a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest 
gst-launch-1.0 command
 b. $ gst-launch-1.0 pipewiresrc path= !  ! decodebin ! 
videoconvert ! glimagesink
 c. Check if the result ok
  5. Check the screencast function by pressing 'prt sc'
 a. the screenshot of all screen/selected region should work good
 b. the screenrecord of all screen/selected region should work good
  6. Check that video recording in gnome-shell works
 - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, 
verify that there is a new entry in ~/Video
  7. Check that screen sharing is working
 - go to settings, screen sharing and enable the feature
 - try to connect using rdp/vnc from another client

  do those steps under wayland and unset X

  [Where problems could occur]
  The patches try to dequeue the shared buffer, instead of pool buffer to 
prevent the pool buffer being corrupted. it might cause some camera preview 
failed if shared buffer is corrupted.
  It is from upstream and there is no regression found, so the risk is low.

  [Other Info]
  Upstream commits for pipewire:
  
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92
  
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f
  
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525c1ac946a915599c6bee813e88e8cee12
  Upstream commits for gstreamer:
  
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/3b900e1fa4fd888012dc005fa26ae2532a89b7a7

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


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

[Touch-packages] [Bug 1987631] Re: Screencast only records one second

[Matthew D. Mower]

@binli - I never found a need to update pipewire; the gstreamer patches
(for gstreamer and gst-plugins-base) seem to be sufficient in my
testing.

I tested your gstreamer & gst-plugins-base packages and they work the same as 
the ones I built. I think you could drop "-0ubuntu1binli1" from the symbols 
update though:
- _gst_meta_tag_memory_reference@Base 1.20.3-0ubuntu1binli1
+ _gst_meta_tag_memory_reference@Base 1.20.3

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

Title:
  Screencast only records one second

Status in GNOME Shell:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  New
Status in gstreamer1.0 package in Ubuntu:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  Fix Released
Status in gst-plugins-base1.0 source package in Jammy:
  New
Status in gstreamer1.0 source package in Jammy:
  New
Status in pipewire source package in Jammy:
  Confirmed

Bug description:
  When recording a screencast with gnome on kinetic the resulting video
  will play for one second and then freeze. It looks like the same bug
  was discussed upstream at https://gitlab.gnome.org/GNOME/gnome-
  shell/-/issues/5585

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1989602] Re: Delay in updating charge status in Ubuntu 22.04 LTS

[John D]

This bug does not seem to be present in Ubuntu 22.10, on the same
hardware.

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

Title:
  Delay in updating charge status in Ubuntu 22.04 LTS

Status in upower package in Ubuntu:
  New

Bug description:
  I am using a Lenovo ThinkPad Yoga 370, running Ubuntu 22.04 LTS.
  When plugging in the charger, the current charge status in the top bar and 
Settings shows 'Not Charging' for a few minutes and then shows that the system 
is charging normally.

  When unplugging the charger the same happens; the charge status shows
  'Not Charging' for a few minutes, and then shows the correct charge
  status.

  Normally, the change in power status should be instantaneous.
  In short, there is a delay in the OS in showing the current charge status.

  Upon further research, it was found that the 'upower' service is to blame; it 
polls every two minutes(i.e., it refreshes the charge status every two 
minutes); causing a delay in charge status.
  This is further compounded by the fact that restarting upower service, or the 
system as a whole makes the system to show the correct charge status.

  However, I did not have this problem on another system, a HP Pavilion x360 
14m-dw0023dx, running the same OS, Ubuntu 22.04 LTS.
  There, the power status behaves normally with no delays whatsoever.

  Please look into this issue and fix this bug as soon as possible.
  One suggestion would be to increase the polling frequency of upower from 2 
mins. to something lesser, so that the charge status shows correctly.

  upower version:
  UPower client version 0.99.17
  UPower daemon version 0.99.17

  OS:
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  Kernel: Linux 5.15.0-47-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: upower 0.99.17-1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 14 20:41:16 2022
  InstallationDate: Installed on 2022-09-12 (1 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1989602/+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 1995236] Re: Xsessions has_option code error with fix

[Peter D.]

And now OPTIONS has to be exported, 
and probably should be protected against being empty in the new file. So it 
becomes ${OPTIONS:-} and ${1:-}

What else have I missed?

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

Title:
  Xsessions has_option code error with fix

Status in xorg package in Ubuntu:
  New

Bug description:
  Jammy Jellyfish 22.04.1 LTS and others. There have been numerous bug
  reports and failed fixes for this over several years and releases.

  There are a couple of problems in /etc/X11/Xsessions where it fails to
  handle options, causing bogus error messages and, doubtless, many
  errors.

  The first bug is that the entire options file, including comments, is
  read into a variable.

  Where the variable "OPTIONS" is assigned;

  Replacing "cat" with "grep" strips out comments and blank lines;

  $ diff Xsession Xsession.orig 
  65c65
  < grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
  ---
  > cat "$OPTIONFILE"

  The second problem is that checking for a non-existent directory
  inside a command substitution does not work.  It just appends garbage
  onto the output string.

  That is probably a bug in BASH, but I defer to your opinion there.

  The immediate work around is to create an empty directory so that the
  test does not fail.  Better still, force the creation of the directory
  and remove the test.

  
  eg. change this;

  OPTIONS="$(
if [ -r "$OPTIONFILE" ]; then
  cat "$OPTIONFILE"
fi
if [ -d /etc/X11/Xsession.options.d ]; then
  run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d 
'\n' cat
fi
  )"

  to this;

  OPTIONSDIR=/etc/X11/Xsession.options.d
  mkdir --parents ${OPTIONSDIR}
  OPTIONS="$(
if [ -r "$OPTIONFILE" ]; then
  grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
fi
run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d 
'\n' cat
  )"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Oct 31 16:33:14 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.38, 5.15.0-362206031516-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  InstallationDate: Installed on 2022-10-20 (11 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Micro-Star International Co., Ltd. MS-7B89
  ProcKernelCmdLine: ro root=PARTUUID=1c70e394-574c-46cc-a65e-a402f0e077d4 
fbcon=rotate:2 initrd=\initrd.img
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.C0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M MORTAR MAX (MS-7B89)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.C0:bd02/01/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B89
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel

[Touch-packages] [Bug 1995236] Re: Xsessions has_option code error with fix

[Peter D.]

Bother.  There is a third problem, a scope issue of some sort. 
The errors in ~/.xsession.error go away if "has_options" is moved from Xsession 
to its own file in Xsession.d

I don't see why sourceing it should make any difference, but it does.

$ cat /etc/X11/Xsession.d/00
has_option () {
  # Ensure that a later no-foo overrides an earlier foo
  if [ "$(echo "$OPTIONS" | grep -Eo "^(no-)?$1\>" | tail -n 1)" == "$1" ]; then
return 0
  else
return 1
  fi
}

Also I changed a "=" to "==", but that should be cosmetic.

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

Title:
  Xsessions has_option code error with fix

Status in xorg package in Ubuntu:
  New

Bug description:
  Jammy Jellyfish 22.04.1 LTS and others. There have been numerous bug
  reports and failed fixes for this over several years and releases.

  There are a couple of problems in /etc/X11/Xsessions where it fails to
  handle options, causing bogus error messages and, doubtless, many
  errors.

  The first bug is that the entire options file, including comments, is
  read into a variable.

  Where the variable "OPTIONS" is assigned;

  Replacing "cat" with "grep" strips out comments and blank lines;

  $ diff Xsession Xsession.orig 
  65c65
  < grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
  ---
  > cat "$OPTIONFILE"

  The second problem is that checking for a non-existent directory
  inside a command substitution does not work.  It just appends garbage
  onto the output string.

  That is probably a bug in BASH, but I defer to your opinion there.

  The immediate work around is to create an empty directory so that the
  test does not fail.  Better still, force the creation of the directory
  and remove the test.

  
  eg. change this;

  OPTIONS="$(
if [ -r "$OPTIONFILE" ]; then
      cat "$OPTIONFILE"
fi
if [ -d /etc/X11/Xsession.options.d ]; then
  run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d 
'\n' cat
fi
  )"

  to this;

  OPTIONSDIR=/etc/X11/Xsession.options.d
  mkdir --parents ${OPTIONSDIR}
  OPTIONS="$(
if [ -r "$OPTIONFILE" ]; then
  grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
fi
run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d 
'\n' cat
  )"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Oct 31 16:33:14 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.38, 5.15.0-362206031516-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  InstallationDate: Installed on 2022-10-20 (11 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Micro-Star International Co., Ltd. MS-7B89
  ProcKernelCmdLine: ro root=PARTUUID=1c70e394-574c-46cc-a65e-a402f0e077d4 
fbcon=rotate:2 initrd=\initrd.img
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.C0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M MORTAR MAX (MS-7B89)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.C0:bd02/01/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B89
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz 1:0.9.14.1+22.04.2

[Touch-packages] [Bug 1995236] [NEW] Xsessions has_option code error with fix

[Peter D.]

Public bug reported:

Jammy Jellyfish 22.04.1 LTS and others. There have been numerous bug
reports and failed fixes for this over several years and releases.

There are a couple of problems in /etc/X11/Xsessions where it fails to
handle options, causing bogus error messages and, doubtless, many
errors.

The first bug is that the entire options file, including comments, is
read into a variable.

Where the variable "OPTIONS" is assigned;

Replacing "cat" with "grep" strips out comments and blank lines;

$ diff Xsession Xsession.orig 
65c65
< grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
---
> cat "$OPTIONFILE"

The second problem is that checking for a non-existent directory inside
a command substitution does not work.  It just appends garbage onto the
output string.

That is probably a bug in BASH, but I defer to your opinion there.

The immediate work around is to create an empty directory so that the
test does not fail.  Better still, force the creation of the directory
and remove the test.


eg. change this;

OPTIONS="$(
  if [ -r "$OPTIONFILE" ]; then
cat "$OPTIONFILE"
  fi
  if [ -d /etc/X11/Xsession.options.d ]; then
run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d 
'\n' cat
  fi
)"

to this;

OPTIONSDIR=/etc/X11/Xsession.options.d
mkdir --parents ${OPTIONSDIR}
OPTIONS="$(
  if [ -r "$OPTIONFILE" ]; then
grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
  fi
  run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d 
'\n' cat
)"

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Oct 31 16:33:14 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox/6.1.38, 5.15.0-362206031516-generic, x86_64: installed
 virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
InstallationDate: Installed on 2022-10-20 (11 days ago)
InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: Micro-Star International Co., Ltd. MS-7B89
ProcKernelCmdLine: ro root=PARTUUID=1c70e394-574c-46cc-a65e-a402f0e077d4 
fbcon=rotate:2 initrd=\initrd.img
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/01/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 2.C0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450M MORTAR MAX (MS-7B89)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.C0:bd02/01/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B89
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy 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/1995236

Title:
  Xsessions has_option code error with fix

Status in xorg package in Ubuntu:
  New

Bug description:
  Jammy Jellyfish 22.04.1 LTS and others. There have been numerous bug
  reports and failed fixes f

[Touch-packages] [Bug 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

[Ian! D. Allen]

** Description changed:

  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.
+ 
+ $ touch foo
+ $ rsync --update --info=skip foo foo
+ foo is newer<=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
+ 
+ Obviously a file should not be listed as newer than itself.  Another
+ way:
  
  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00
  
  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.
+ The bug was fixed upstream in June 2020:  
https://github.com/WayneD/rsync/issues/98
  
  $ touch foo
  $ rsync --update --info=skip foo foo
  foo is newer<=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  
  Obviously a file should not be listed as newer than itself.  Another
  way:
  
  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00
  
  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync:
  Unknown
Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.
  The bug was fixed upstream in June 2020:  
https://github.com/WayneD/rsync/issues/98

  $ touch foo
  $ rsync --update --info=skip foo foo
  foo is newer<=== THIS IS NOT CORRECT - A file 

[Touch-packages] [Bug 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

[Ian! D. Allen]

I'm not familiar with your SRU process, debdiff, dput, the "General
Requirements" document, the "security policy document", or your upload
process, and I'm not into learning about all that and filling out your
special form and making your special upload when there is no guarantee
that Ubuntu will actually fix the problem.

If all the info you need for your SRU process isn't already in this bug
report (or in the bug report upstream linked above), I don't know what
else to say.  I certainly don't have the experience to answer "Where
problems could occur" in a Ubuntu package management context, other than
to say the obvious "people may have already written scripts that depend
on the buggy behaviour".

You're already running a fixed version of rsync in Kinetic, so at some
level someone at Ubuntu already approved of a much more modern rsync
(3.2.5 was released August 14 2022) -- please use it.

I've documented the bug; someone else found the upstream fix; your
Ubuntu internals of adopting the fix are more reading than I want to do.
I will download the current source and update my own rsync -- I know how
to do that and I know it will solve the problem for me.  I hope Ubuntu
solves the problem for everyone else.

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

[Ian! D. Allen]

I knew nothing about your SRU process until now; the man page for
`ubuntu-bug` makes no mention of it.  Who fills out the SRU Bug Template
and makes the fix actually happen?  Is there anything more I need to do
here?

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

[Ian! D. Allen]

The problem was marked as Confirmed by Paride back on March 17.
Then today it gets marked Invalid.
Then later today it gets marked Confirmed again.
I don't understand your process.

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

[Ian! D. Allen]

Your incorrect statement "seems the issue does not actually exist" is
wrong.  I told you exactly how to reproduce the problem on your latest
22.04.1 LTS release.  I gave you the link to the upstream bug that Wayne
fixed over two years ago.  This two-year-old bug does exist and it
exists in your most recent Ubuntu 22.04.1 LTS release.  Here's another
way to show the bug:

$ touch foo
$ rsync --update --info=skip foo foo
foo is newer

Obviously a file should not be listed as newer than itself.  This rsync
is broken.

The real bug appears to be that Ubuntu is shipping a broken two-year-old
year 3.2.3 version of rsync in its latest 22.04.1 LTS release and won't
update it to get rid of the bug.  I've added a comment to the github bug
number 98 warning people about the broken Ubuntu LTS.

All my scripts that depend on an accurate "is newer" indicator from
rsync are broken.

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync package in Ubuntu:
  Invalid

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

[Ian! D. Allen]

Your incorrect statement "seems the issue does not actually exist" is
wrong.  I told you exactly how to reproduce the problem on your latest
22.04.1 LTS release.  You were also given the link to the upstream bug
that Wayne fixed over two years ago.  This two-year-old bug does exist
and it exists in your most recent Ubuntu 22.04.1 LTS release.  Here's
another way to show the bug:

$ touch foo
$ rsync --update --info=skip foo foo
foo is newer

Obviously a file should not be listed as newer than itself.  This rsync
is broken.

The real bug appears to be that Ubuntu is shipping a broken two-year-old
year 3.2.3 version of rsync in its latest 22.04.1 LTS release and won't
update it to get rid of the bug.

All my scripts that depend on an accurate "is newer" indicator from
rsync are broken.

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync package in Ubuntu:
  Invalid

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

[Ian! D. Allen]

Hey Ubuntu - I see now that this bug was reported and fixed at source in
September 2020, over two years ago.  The real bug is: "Why didn't Ubuntu
apply the fix to the supported Ubuntu releases?"

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+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 1989545] Re: ubuntu-bug fails when run via remote SSH login

[Ian! D. Allen]

The laptop is logged in and running Wayland: /usr/bin/Xwayland :0
My desktop is running X11: /usr/lib/xorg/Xorg -nolisten tcp :0
When I SSH into the laptop from the desktop, my DISPLAY is set to 
"localhost:10".
When I start an xterm in the SSH session (running xterm on the laptop),
the xterm window opens correctly on the desktop X11, not on the laptop.
Inside that xterm, when I type "ubuntu-bug" (running ubuntu-bug on the laptop),
ubuntu-bug incorrectly opens a window on the laptop, not on the desktop.
Typing "/usr/share/apport/apport-gtk alskdjflkj" also incorrectly opens a window
on the laptop, not the desktop.
I don't have /usr/share/apport/apport-kde installed, but I could install it
and see what happens if that would be helpful.

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

Title:
  ubuntu-bug fails when run via remote SSH login

Status in apport package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 20.04 on my desktop.  I SSH into my laptop running
  22.04:

  desktop$ ssh laptop
  laptop$ sudo -sE
  laptop#

  If I now run most any X11 client applications (e.g. xload, xterm)
  using this laptop SSH command line, they correctly open windows on my
  desktop X11 display, not on my laptop, using the DISPLAY variable set
  to localhost:10.0.  But ubuntu-bug does not do this when I run it on
  the laptop:

  laptop# ubuntu-bug /etc/network/if-up.d/resolved

  At this point, the laptop display incorrectly has the apport X11 window
  open.  The apport window does not open on my desktop, like any other
  X11 application would.  It appears to ignore my DISPLAY variable.

  If I go over to the laptop and try to continue with the bug report,
  everything falls apart when it tries to start up a web browser.  I get
  all these error messages on my SSH terminal screen:

  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none 
bind,ro 0 0): not a directory
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": 
permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none 
bind,ro 0 0): cannot open directory "/var/lib": permission denied
  /home/username/Music was removed, reassigning MUSIC to homedir
  X11 connection rejected because of wrong authentication.
  X11 connection rejected because of wrong authentication.
  Error: cannot open display: localhost:10.0
  X11 connection rejected because of wrong authentication.
  X11 connection rejected because of wrong authentication.
  X11 connection rejected because of wrong authentication.
  X11 connection rejected because of wrong authentication.

  If ubuntu-bug cannot work over SSH with DISPLAY=localhost:10.0, it should
  detect this and not even try.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 14 02:33:18 2022
  InstallationDate: Installed on 2020-09-08 (735 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to jammy on 2022-04-04 (162 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1989545/+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 1989602] [NEW] Delay in updating charge status in Ubuntu 22.04 LTS

[John D]

Public bug reported:

I am using a Lenovo ThinkPad Yoga 370, running Ubuntu 22.04 LTS.
When plugging in the charger, the current charge status in the top bar and 
Settings shows 'Not Charging' for a few minutes and then shows that the system 
is charging normally.

When unplugging the charger the same happens; the charge status shows
'Not Charging' for a few minutes, and then shows the correct charge
status.

Normally, the change in power status should be instantaneous.
In short, there is a delay in the OS in showing the current charge status.

Upon further research, it was found that the 'upower' service is to blame; it 
polls every two minutes(i.e., it refreshes the charge status every two 
minutes); causing a delay in charge status.
This is further compounded by the fact that restarting upower service, or the 
system as a whole makes the system to show the correct charge status.

However, I did not have this problem on another system, a HP Pavilion x360 
14m-dw0023dx, running the same OS, Ubuntu 22.04 LTS.
There, the power status behaves normally with no delays whatsoever.

Please look into this issue and fix this bug as soon as possible.
One suggestion would be to increase the polling frequency of upower from 2 
mins. to something lesser, so that the charge status shows correctly.

upower version:
UPower client version 0.99.17
UPower daemon version 0.99.17

OS:
Description:Ubuntu 22.04.1 LTS
Release:22.04
Kernel: Linux 5.15.0-47-generic

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: upower 0.99.17-1
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 14 20:41:16 2022
InstallationDate: Installed on 2022-09-12 (1 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
SourcePackage: upower
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  Delay in updating charge status in Ubuntu 22.04 LTS

Status in upower package in Ubuntu:
  New

Bug description:
  I am using a Lenovo ThinkPad Yoga 370, running Ubuntu 22.04 LTS.
  When plugging in the charger, the current charge status in the top bar and 
Settings shows 'Not Charging' for a few minutes and then shows that the system 
is charging normally.

  When unplugging the charger the same happens; the charge status shows
  'Not Charging' for a few minutes, and then shows the correct charge
  status.

  Normally, the change in power status should be instantaneous.
  In short, there is a delay in the OS in showing the current charge status.

  Upon further research, it was found that the 'upower' service is to blame; it 
polls every two minutes(i.e., it refreshes the charge status every two 
minutes); causing a delay in charge status.
  This is further compounded by the fact that restarting upower service, or the 
system as a whole makes the system to show the correct charge status.

  However, I did not have this problem on another system, a HP Pavilion x360 
14m-dw0023dx, running the same OS, Ubuntu 22.04 LTS.
  There, the power status behaves normally with no delays whatsoever.

  Please look into this issue and fix this bug as soon as possible.
  One suggestion would be to increase the polling frequency of upower from 2 
mins. to something lesser, so that the charge status shows correctly.

  upower version:
  UPower client version 0.99.17
  UPower daemon version 0.99.17

  OS:
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  Kernel: Linux 5.15.0-47-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: upower 0.99.17-1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 14 20:41:16 2022
  InstallationDate: Installed on 2022-09-12 (1 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1989602/+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 1989545] [NEW] ubuntu-bug fails when run via remote SSH login

[Ian! D. Allen]

Public bug reported:

I'm running Ubuntu 20.04 on my desktop.  I SSH into my laptop running
22.04:

desktop$ ssh laptop
laptop$ sudo -sE
laptop#

If I now run most any X11 client applications (e.g. xload, xterm)
using this laptop SSH command line, they correctly open windows on my
desktop X11 display, not on my laptop, using the DISPLAY variable set
to localhost:10.0.  But ubuntu-bug does not do this when I run it on
the laptop:

laptop# ubuntu-bug /etc/network/if-up.d/resolved

At this point, the laptop display incorrectly has the apport X11 window
open.  The apport window does not open on my desktop, like any other
X11 application would.  It appears to ignore my DISPLAY variable.

If I go over to the laptop and try to continue with the bug report,
everything falls apart when it tries to start up a web browser.  I get
all these error messages on my SSH terminal screen:

update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none 
bind,ro 0 0): not a directory
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": 
permission denied
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none 
bind,ro 0 0): cannot open directory "/var/lib": permission denied
/home/username/Music was removed, reassigning MUSIC to homedir
X11 connection rejected because of wrong authentication.
X11 connection rejected because of wrong authentication.
Error: cannot open display: localhost:10.0
X11 connection rejected because of wrong authentication.
X11 connection rejected because of wrong authentication.
X11 connection rejected because of wrong authentication.
X11 connection rejected because of wrong authentication.

If ubuntu-bug cannot work over SSH with DISPLAY=localhost:10.0, it should
detect this and not even try.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apport 2.20.11-0ubuntu82.1
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
ApportLog:
 
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 14 02:33:18 2022
InstallationDate: Installed on 2020-09-08 (735 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to jammy on 2022-04-04 (162 days ago)

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


** Tags: amd64 apport-bug jammy third-party-packages wayland-session

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

Title:
  ubuntu-bug fails when run via remote SSH login

Status in apport package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 20.04 on my desktop.  I SSH into my laptop running
  22.04:

  desktop$ ssh laptop
  laptop$ sudo -sE
  laptop#

  If I now run most any X11 client applications (e.g. xload, xterm)
  using this laptop SSH command line, they correctly open windows on my
  desktop X11 display, not on my laptop, using the DISPLAY variable set
  to localhost:10.0.  But ubuntu-bug does not do this when I run it on
  the laptop:

  laptop# ubuntu-bug /etc/network/if-up.d/resolved

  At this point, the laptop display incorrectly has the apport X11 window
  open.  The apport window does not open on my desktop, like any other
  X11 application would.  It appears to ignore my DISPLAY variable.

  If I go over to the laptop and try to continue with the bug report,
  everything falls apart when it tries to start up a web browser.  I get
  all these error messages on my SSH terminal screen:

  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none 
bind,ro 0 0): not a directory
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": 
permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none 
bind,ro 0 0): cannot open directory "/var/lib": permission denied
  /home/username/Music was removed, reassigning MUSIC to homedir
  X11 connection rejected because of wrong authentication.
  X11 connection rejected because of wrong authentication.
  Error: cannot open display: localhost:10.0
  X11 connection rejected because 

[Touch-packages] [Bug 1988667] Re: Quito isn't displayed as choice for time zone

[d]

Thank you for following this up and your reply. I will report it and see
if it is updated upstream.

Thank you again!

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

Title:
  Quito isn't displayed as choice for time zone

Status in tzdata package in Ubuntu:
  Opinion

Bug description:
  On Ubuntu 22.04.1 (and 20.04.x) there is no option available for
  Quito.

  On GNOME
  

  Settings > Date & Time > (A map is displayed)

  Type Quito on the search field.

  There are no matches.

  
  On KDE
  ==

  System Settings > Regional Settings > Date & Time > Time Zone

  When searching for the time zone I enter:

  Quito

  There are no matches.

  
  The entries for Ecuador are Galapagos Islands and Guayaquil. Quito is the 
capital city of Ecuador, whereas Guayaquil is the second biggest. It makes no 
sense for the capital not to be displayed in the city list, but to have the 
second.

  It is akin to have Marseille as the main choice for France instead of
  Paris.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1988667/+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 1948752] Re: apparmor is logging too many messages

[D-nl-k]

Unfortunately that didn't made any change. My
/etc/apparmor.d/usr.bin.redshift now looks like follows.

/usr/bin/redshift {

  dbus send bus="system" 
path="/org/freedesktop/DBus"
interface="org.freedesktop.DBus"
member="{GetNameOwner,StartServiceByName,AddMatch}",

  dbus send bus="system" 
path="/org/freedesktop/GeoClue2/Manager"
interface="org.freedesktop.DBus.Properties" 
member="GetAll",

  dbus send bus="system" 
path="/org/freedesktop/GeoClue2/Manager"
interface="org.freedesktop.GeoClue2.Manager" 
member="GetClient",


  # Allow but log any other dbus activity
  audit dbus bus=system,

  owner @{HOME}/.config/redshift.conf r,
  owner /run/user/*/redshift-shared-* rw,
}

(The last three lines where already in that file)
still tons of messages like this one:

[Do Jun  9 23:15:47 2022] audit: type=1420 audit(1654809348.128:59832): 
subj_apparmor=unconfined
[Do Jun  9 23:15:47 2022] audit: type=1107 audit(1654809348.128:59833): pid=977 
uid=103 auid=4294967295 ses=4294967295 subj=? msg='apparmor="ALLOWED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/DBus" 
interface="org.freedesktop.DBus" member="StartServiceByName" mask="send" 
name="org.freedesktop.DBus" pid=158627 label="/usr/bin/redshift" 
peer_label="unconfined"
   exe="/usr/bin/dbus-daemon" sauid=103 hostname=? 
addr=? terminal=?'
[Do Jun  9 23:15:47 2022] audit: type=1420 audit(1654809348.128:59834): 
subj_apparmor=unconfined

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

Title:
  apparmor is logging too many messages

Status in Redshift:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  Unfortunately, this bug does not seem to be fixed yet.
  My syslog is flooded with ALLOWED messages regarding redshift.

  My system is a Kubuntu 21.04.
  AppArmor is V. 3.0.0-0ubuntu7.1

  Attached you'll find an excerpt from /var/log/syslog for the last 5
  minutes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/redshift/+bug/1948752/+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 1948752] Re: apparmor is logging too many messages

[D-nl-k]

Which would be?

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

Title:
  apparmor is logging too many messages

Status in Redshift:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  Unfortunately, this bug does not seem to be fixed yet.
  My syslog is flooded with ALLOWED messages regarding redshift.

  My system is a Kubuntu 21.04.
  AppArmor is V. 3.0.0-0ubuntu7.1

  Attached you'll find an excerpt from /var/log/syslog for the last 5
  minutes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/redshift/+bug/1948752/+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 1946621] Re: Crash in libegl-mesa0 (eglReleaseThread)

[Maniraj D]

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

Verified internally with Ubuntu 20.04.4 + libegl-mesa0 version
"21.2.6-0ubuntu0.1~20.04.2" and confirmed the crash issue is resolved.

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

Title:
  Crash in libegl-mesa0 (eglReleaseThread)

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  New
Status in mesa source package in Impish:
  New

Bug description:
  Crash in libegl-mesa0 (in eglReleaseThread API), please find the
  backtrace:

  #0  0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) 
at pthread_mutex_lock.c:67
  #1  0xf4a7d110 in mtx_lock (mtx=0x8) at 
../include/c11/threads_posix.h:223
  #2  eglReleaseThread () at ../src/egl/main/eglapi.c:1713
  #3  0xf6c115b8 in eglReleaseThread () at 
/lib/aarch64-linux-gnu/libEGL.so.1
  #4  0xf7fdac00 in  () at /lib/ld-linux-aarch64.so.1
  #5  0xf7b4284c in __run_exit_handlers
  (status=0, listp=0xf7c76680 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at 
exit.c:108
  #6  0xf7b429dc in __GI_exit (status=) at exit.c:139
  #7  0xf7b2d094 in __libc_start_main (main=
  0x3530 , argc=13, argv=0xf488, init=, fini=, rtld_fini=, stack_end=)
  at ../csu/libc-start.c:342
  #8  0x4014 in _start ()

  It crashes at:
  https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713.
  'disp' pointer is being NULL in this case.

  Actually nvidia's EGL backend is being loaded by glvnd in this case.
  But the eglReleaseThread() implementation of glvnd calls the
  eglReleaseThread() API of all the vendors, that's how it end-up
  calling the eglReleaseThread() API of Mesa backend. Refer:
  https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.3 LTS
  Release:20.04
  Codename:   focal

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 21.0.3-0ubuntu0.3~20.04.2
Candidate: 21.0.3-0ubuntu0.3~20.04.2
Version table:
   *** 21.0.3-0ubuntu0.3~20.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   20.0.4-2ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1946621/+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 1878617] Re: Apple pages file type should be added to MIME types

[David D Lowe]

A fix was released upstream in shared-mime-info 2.2 (2022-03-27). Sadly,
this didn't make it to Ubuntu 22.04 LTS.

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

Title:
  Apple pages file type should be added to MIME types

Status in shared-mime-info:
  Unknown
Status in mime-support package in Ubuntu:
  New
Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  LibreOffice can open .pages files (from Apple pages). However, the
  mime type for these files is incorrectly just application/zip:

  $ file --mime-type example.pages
  example.pages: application/zip

  Instead, it should be application/vnd.apple.pages .

  This would allow the user to associate LibreOffice Writer with these
  types of files, and use it to open this file. (LibreOffice Writer can
  open .pages files)

  Apple Keynote files should have this MIME type:
  application/vnd.apple.keynote

  Apple Numbers files should have this MIME type:
  application/vnd.apple.numbers

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mime-support 3.64ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 14:46:40 2020
  InstallationDate: Installed on 2018-11-11 (550 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: mime-support
  UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1878617/+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 1954843] Re: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument

[Matthew D. Mower]

This issue is no longer present in Ubuntu 22.04. Wile using Ubuntu 21.10, the 
following workarounds also remedied the issue:
- Run a mainline 5.15.x kernel from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
- Run the Jammy Jellyfish kernel from 
https://packages.ubuntu.com/jammy/linux-image-generic
In both cases, it's necessary to install libssl3 from Jammy Jellyfish as well 
(see https://askubuntu.com/a/1389586/117513).

Ultimately, since Ubuntu 21.10 is rapidly approaching EoL, it makes
sense to upgrade to Ubuntu 22.04.

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

Title:
  amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid
  argument

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 21.10 does not succeed at setting the display brightness after
  booting (either to the GNOME login screen or to a logged-in user's
  desktop). The brightness is at its highest level until I adjust it
  with keyboard shortcuts or a GUI tool.

  The systemd-backlight@backlight:amdgpu_bl0 service seems to fail
  during startup, but I can subsequently run it after startup and it
  succeeds (and restores brightness):

  mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0
  [sudo] password for mdmower: 
  × systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0
   Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static)
   Active: failed (Result: exit-code) since Tue 2021-12-14 13:26:05 PST; 
30s ago
 Docs: man:systemd-backlight@.service(8)
  Process: 962 ExecStart=/lib/systemd/systemd-backlight load 
backlight:amdgpu_bl0 (code=exited, status=1/FAILURE)
 Main PID: 962 (code=exited, status=1/FAILURE)
  CPU: 3ms

  Dec 14 13:26:05 T14S systemd[1]: Starting Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0...
  Dec 14 13:26:05 T14S systemd-backlight[962]: amdgpu_bl0: Failed to write 
system 'brightness' attribute: Invalid argument
  Dec 14 13:26:05 T14S systemd[1]: 
systemd-backlight@backlight:amdgpu_bl0.service: Main process exited, 
code=exited, status=1/FAILURE
  Dec 14 13:26:05 T14S systemd[1]: 
systemd-backlight@backlight:amdgpu_bl0.service: Failed with result 'exit-code'.
  Dec 14 13:26:05 T14S systemd[1]: Failed to start Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0.

  mdmower@T14S ~ $ sudo systemctl start systemd-
  backlight@backlight:amdgpu_bl0

  mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0
  ● systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0
   Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static)
   Active: active (exited) since Tue 2021-12-14 13:26:45 PST; 1s ago
 Docs: man:systemd-backlight@.service(8)
  Process: 5119 ExecStart=/lib/systemd/systemd-backlight load 
backlight:amdgpu_bl0 (code=exited, status=0/SUCCESS)
 Main PID: 5119 (code=exited, status=0/SUCCESS)
  CPU: 5ms

  Dec 14 13:26:45 T14S systemd[1]: Starting Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0...
  Dec 14 13:26:45 T14S systemd[1]: Finished Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 14 13:29:38 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Cezanne [17aa:5095]
  InstallationDate: Installed on 2021-12-12 (2 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XF004WUS
  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.13.0-22-generic 
root=UUID=859a72cc-a3fe-470f-b525-37b151408289 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.14
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1NET44W (1.14)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XF004WUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset I

[Touch-packages] [Bug 1970070] [NEW] package linux-firmware 1.187.29 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

[D Tanski]

Public bug reported:

4/23/2022:  did apt-get update followed by apt-get dist-upgrade and this
is what happened.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.29
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
ApportVersion: 2.20.11-0ubuntu27.23
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm2568 F pulseaudio
  zepcom10571 F pulseaudio
CasperMD5CheckResult: skip
Date: Sat Apr 23 21:07:40 2022
Dependencies:
 
ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 13d3:56a8 IMC Networks USB2.0 HD UVC WebCam
 Bus 001 Device 003: ID 8087:0026 Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513EQ_S513EQ
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_5lwshk@/vmlinuz-5.13.0-35-generic 
root=ZFS=rpool/ROOT/ubuntu_5lwshk ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15
SourcePackage: initramfs-tools
Title: package linux-firmware 1.187.29 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/08/2021
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: X513EQ.305
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X513EQ
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX513EQ.305:bd04/08/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513EQ_S513EQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513EQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: VivoBook
dmi.product.name: VivoBook_ASUSLaptop X513EQ_S513EQ
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-package focal need-duplicate-check

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

Title:
  package linux-firmware 1.187.29 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  4/23/2022:  did apt-get update followed by apt-get dist-upgrade and
  this is what happened.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.29
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2568 F pulseaudio
zepcom10571 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sat Apr 23 21:07:40 2022
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56a8 IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 003: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513EQ_S513EQ
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_5lwshk@/vmlinuz-5.13.0-35-generic 
root=ZFS=rpool/ROOT/ubuntu_5lwshk ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.187.29 

[Touch-packages] [Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session

[Angel D. Segarra]

Updated and now I can't reproduce. Looks like some update made it go
away.

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

Title:
  "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in
  Wayland session

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in xwayland package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 21.10 on Wayland session
  mutter 40.5-1ubuntu3~21.10.1

  My apologies if this does not belong in mutter but because it happens
  in multiple applications, it's my best guess.

  This is a weird bug because I don't know what causes it but it happens
  consistently after normal usage which for me means several times
  leaving the laptop idle and unlocking.

  If I leave gnome-terminal and/or evince open, eventually any UI action
  like switching from multiple tabs, opening context menu etc will
  output the following to journal

  gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653
  drawable is not a native X11 window

  evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is
  not a native X11 window

  I suspect this may happen with other gtk apps as well. This persists
  until each individual app is restarted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+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 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session

[Angel D. Segarra]

fwiw I've checked Ubuntu 21.10/22.04, Fedora 35/36 and Arch. This only
happens in Ubuntu.

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

Title:
  "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in
  Wayland session

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in xwayland package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 21.10 on Wayland session
  mutter 40.5-1ubuntu3~21.10.1

  My apologies if this does not belong in mutter but because it happens
  in multiple applications, it's my best guess.

  This is a weird bug because I don't know what causes it but it happens
  consistently after normal usage which for me means several times
  leaving the laptop idle and unlocking.

  If I leave gnome-terminal and/or evince open, eventually any UI action
  like switching from multiple tabs, opening context menu etc will
  output the following to journal

  gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653
  drawable is not a native X11 window

  evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is
  not a native X11 window

  I suspect this may happen with other gtk apps as well. This persists
  until each individual app is restarted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+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 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session

[Angel D. Segarra]

I am seeing this in 22.04 and an easy way for me to reproduce is on a
fresh login, open a terminal and watch the log, open Brave/Chrome, for
some reason the first time you open the browser it has a GTK title bar
which goes away on closing/reopening the app, now right clicking in the
terminal window or opening the hamburger menu and bringing up the menu
triggers this message in the logs.

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

Title:
  "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in
  Wayland session

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in xwayland package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 21.10 on Wayland session
  mutter 40.5-1ubuntu3~21.10.1

  My apologies if this does not belong in mutter but because it happens
  in multiple applications, it's my best guess.

  This is a weird bug because I don't know what causes it but it happens
  consistently after normal usage which for me means several times
  leaving the laptop idle and unlocking.

  If I leave gnome-terminal and/or evince open, eventually any UI action
  like switching from multiple tabs, opening context menu etc will
  output the following to journal

  gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653
  drawable is not a native X11 window

  evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is
  not a native X11 window

  I suspect this may happen with other gtk apps as well. This persists
  until each individual app is restarted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

[Ian! D. Allen]

I am not arguing about the behaviour, which is correct and apparently hasn't 
changed.
I'm complaining about the unannounced change in message from "is uptodate" to 
"is newer".

Three problems:

1. The message "is newer" is an unannounced change from all previous
versions of rsync that say "is uptodate".  My scripts that look for "is
newer" are all broken, because now every file is flagged as newer, even
when the file is not newer.

2. I expect that a name flagged as "is newer" will be transferred when I
remove the --update option, and that does not happen because the file is
*NOT* newer; the message is wrong and no transfer happens.

3. The message changes with and without the --update option.  If rsync
says "is uptodate" without the --update option, why does that change to
"is newer" when you add the option?  Either the file is newer *OR* it is
uptodate; it can't be both.  Adding the --update option should not
change "is uptodate" to "is newer".  It is not newer; don't say it is.

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync package in Ubuntu:
  Incomplete

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+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 1965076] [NEW] rsync --update incorrectly reports file "is newer" than itself

[Ian! D. Allen]

Public bug reported:

rsync 3.2.3 has a broken "--update" option.See the examples below.
The "--update" option incorrectly makes rsync say a file is newer than itself.
Remove the "--update" option, and rsync correctly says the file is "uptodate".
The right output should of course be "is uptodate" in all cases.
This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

$ touch foo
$ rsync -avv --update foo .
delta-transmission disabled for local transfer or --whole-file
foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
total: matches=0  hash_hits=0  false_alarms=0 data=0
sent 38 bytes  received 96 bytes  268.00 bytes/sec
total size is 0  speedup is 0.00

$ rsync -avv foo .
delta-transmission disabled for local transfer or --whole-file
foo is uptodate  <=== THIS IS CORRECT
total: matches=0  hash_hits=0  false_alarms=0 data=0
sent 41 bytes  received 106 bytes  294.00 bytes/sec
total size is 0  speedup is 0.00

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: rsync 3.2.3-4ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 15 22:47:44 2022
InstallationDate: Installed on 2022-03-16 (0 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: rsync
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug impish wayland-session

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync package in Ubuntu:
  New

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+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 1956915] Re: New bugfix release 21.2.6

[Maniraj D]

Hi Timo,

When we can expect that to be part of 'focal-updates' ?

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

Title:
  New bugfix release 21.2.6

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Committed
Status in mesa source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  This is the last point-release of the 21.2.x-series, we should put it
  in impish so latest bugfixes would get there, and in focal for 20.04.4
  image.

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915/+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 1940545] Re: Update Mesa to mesa-21.1.7 on Ubuntu 20.04

[Maniraj D]

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

Hi Timo,

>From https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915, I
understood that Mesa 21.2.6 is backported to ubuntu0.1~20.04.1 and that
is currently under 'focal-proposed', when we can expect that to be part
of 'focal-updates' ?

I tried upgrading it with "sudo add-apt-repository ppa:savoury1/display
&& sudo apt upgrade" for now as mentioned in
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915. But the
mesa package is not upgraded in my system.

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

Title:
  Update Mesa to mesa-21.1.7 on Ubuntu 20.04

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  With the recent MR
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to
  Mesa, we (NVIDIA) have added ability to GBM to dynamically load the
  backends. So we request to upgrade mesa libs to its latest version
  (mesa-21.1.7) on Ubuntu 20.04 to use the added feature for our
  development.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1940545/+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 1954843] Re: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument

[Matthew D. Mower]

I compiled several Ubuntu-5.13.0-x.x tags from 
https://kernel.ubuntu.com/git/ubuntu/ubuntu-impish.git/refs/ but the backlight 
issue seems to go far back in time. I tested:
- Ubuntu-5.13.0-25.26
- Ubuntu-5.13.0-21.21
- Ubuntu-5.13.0-20.20
- Ubuntu-5.13.0-19.19
- Ubuntu-5.13.0-16.16

In Ubuntu-5.13.0-16.16, there are some 400ish commits by Ubuntu on top
of upstream v5.13.13. I haven't been able to identify which could be
responsible, yet.

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

Title:
  amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid
  argument

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 21.10 does not succeed at setting the display brightness after
  booting (either to the GNOME login screen or to a logged-in user's
  desktop). The brightness is at its highest level until I adjust it
  with keyboard shortcuts or a GUI tool.

  The systemd-backlight@backlight:amdgpu_bl0 service seems to fail
  during startup, but I can subsequently run it after startup and it
  succeeds (and restores brightness):

  mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0
  [sudo] password for mdmower: 
  × systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0
   Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static)
   Active: failed (Result: exit-code) since Tue 2021-12-14 13:26:05 PST; 
30s ago
 Docs: man:systemd-backlight@.service(8)
  Process: 962 ExecStart=/lib/systemd/systemd-backlight load 
backlight:amdgpu_bl0 (code=exited, status=1/FAILURE)
 Main PID: 962 (code=exited, status=1/FAILURE)
  CPU: 3ms

  Dec 14 13:26:05 T14S systemd[1]: Starting Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0...
  Dec 14 13:26:05 T14S systemd-backlight[962]: amdgpu_bl0: Failed to write 
system 'brightness' attribute: Invalid argument
  Dec 14 13:26:05 T14S systemd[1]: 
systemd-backlight@backlight:amdgpu_bl0.service: Main process exited, 
code=exited, status=1/FAILURE
  Dec 14 13:26:05 T14S systemd[1]: 
systemd-backlight@backlight:amdgpu_bl0.service: Failed with result 'exit-code'.
  Dec 14 13:26:05 T14S systemd[1]: Failed to start Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0.

  mdmower@T14S ~ $ sudo systemctl start systemd-
  backlight@backlight:amdgpu_bl0

  mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0
  ● systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0
   Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static)
   Active: active (exited) since Tue 2021-12-14 13:26:45 PST; 1s ago
 Docs: man:systemd-backlight@.service(8)
  Process: 5119 ExecStart=/lib/systemd/systemd-backlight load 
backlight:amdgpu_bl0 (code=exited, status=0/SUCCESS)
 Main PID: 5119 (code=exited, status=0/SUCCESS)
  CPU: 5ms

  Dec 14 13:26:45 T14S systemd[1]: Starting Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0...
  Dec 14 13:26:45 T14S systemd[1]: Finished Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 14 13:29:38 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Cezanne [17aa:5095]
  InstallationDate: Installed on 2021-12-12 (2 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XF004WUS
  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.13.0-22-generic 
root=UUID=859a72cc-a3fe-470f-b525-37b151408289 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.14
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1NET44W (1.14)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XF004WUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  

[Touch-packages] [Bug 1954843] Re: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument

[Matthew D. Mower]

I just tested signed Ubuntu kernel 5.13.0-28-generic which is in
Proposed right now, but it does not fix the issue. Brightness
adjustments work, but service fails during startup and screen is at full
brightness every boot (at gdm and at GNOME 3 desktop).

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

Title:
  amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid
  argument

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 21.10 does not succeed at setting the display brightness after
  booting (either to the GNOME login screen or to a logged-in user's
  desktop). The brightness is at its highest level until I adjust it
  with keyboard shortcuts or a GUI tool.

  The systemd-backlight@backlight:amdgpu_bl0 service seems to fail
  during startup, but I can subsequently run it after startup and it
  succeeds (and restores brightness):

  mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0
  [sudo] password for mdmower: 
  × systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0
   Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static)
   Active: failed (Result: exit-code) since Tue 2021-12-14 13:26:05 PST; 
30s ago
 Docs: man:systemd-backlight@.service(8)
  Process: 962 ExecStart=/lib/systemd/systemd-backlight load 
backlight:amdgpu_bl0 (code=exited, status=1/FAILURE)
 Main PID: 962 (code=exited, status=1/FAILURE)
  CPU: 3ms

  Dec 14 13:26:05 T14S systemd[1]: Starting Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0...
  Dec 14 13:26:05 T14S systemd-backlight[962]: amdgpu_bl0: Failed to write 
system 'brightness' attribute: Invalid argument
  Dec 14 13:26:05 T14S systemd[1]: 
systemd-backlight@backlight:amdgpu_bl0.service: Main process exited, 
code=exited, status=1/FAILURE
  Dec 14 13:26:05 T14S systemd[1]: 
systemd-backlight@backlight:amdgpu_bl0.service: Failed with result 'exit-code'.
  Dec 14 13:26:05 T14S systemd[1]: Failed to start Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0.

  mdmower@T14S ~ $ sudo systemctl start systemd-
  backlight@backlight:amdgpu_bl0

  mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0
  ● systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0
   Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static)
   Active: active (exited) since Tue 2021-12-14 13:26:45 PST; 1s ago
 Docs: man:systemd-backlight@.service(8)
  Process: 5119 ExecStart=/lib/systemd/systemd-backlight load 
backlight:amdgpu_bl0 (code=exited, status=0/SUCCESS)
 Main PID: 5119 (code=exited, status=0/SUCCESS)
  CPU: 5ms

  Dec 14 13:26:45 T14S systemd[1]: Starting Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0...
  Dec 14 13:26:45 T14S systemd[1]: Finished Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 14 13:29:38 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Cezanne [17aa:5095]
  InstallationDate: Installed on 2021-12-12 (2 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XF004WUS
  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.13.0-22-generic 
root=UUID=859a72cc-a3fe-470f-b525-37b151408289 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.14
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1NET44W (1.14)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XF004WUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 

[Touch-packages] [Bug 1954843] Re: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument

[Matthew D. Mower]

I tested some mainline 5.13.x kernels from
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D and was able to
find a point release where this issue is resolved. Testing results:

Signed Ubuntu kernel 5.13.0-27-generic: brightness adjustments work, but
service fails during startup and screen is at full brightness every boot
(at gdm and at GNOME 3 desktop)

Unsigned mainline kernels:
- 5.13.19 - fixed, service starts successfully automatically
- 5.13.15 - fixed, service starts successfully automatically
- 5.13.12 - fixed, service starts successfully automatically
- 5.13.11 - fixed, service starts successfully automatically
- 5.13.9  - stuck at max brightness, adjustments don't work at all, service 
starts successfully but is ineffective
- 5.13.0  - stuck at max brightness, adjustments don't work at all (forgot to 
check whether service started)

The service I was looking at for status on bootup is: systemd-
backlight@backlight:amdgpu_bl0

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

Title:
  amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid
  argument

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 21.10 does not succeed at setting the display brightness after
  booting (either to the GNOME login screen or to a logged-in user's
  desktop). The brightness is at its highest level until I adjust it
  with keyboard shortcuts or a GUI tool.

  The systemd-backlight@backlight:amdgpu_bl0 service seems to fail
  during startup, but I can subsequently run it after startup and it
  succeeds (and restores brightness):

  mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0
  [sudo] password for mdmower: 
  × systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0
   Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static)
   Active: failed (Result: exit-code) since Tue 2021-12-14 13:26:05 PST; 
30s ago
 Docs: man:systemd-backlight@.service(8)
  Process: 962 ExecStart=/lib/systemd/systemd-backlight load 
backlight:amdgpu_bl0 (code=exited, status=1/FAILURE)
 Main PID: 962 (code=exited, status=1/FAILURE)
  CPU: 3ms

  Dec 14 13:26:05 T14S systemd[1]: Starting Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0...
  Dec 14 13:26:05 T14S systemd-backlight[962]: amdgpu_bl0: Failed to write 
system 'brightness' attribute: Invalid argument
  Dec 14 13:26:05 T14S systemd[1]: 
systemd-backlight@backlight:amdgpu_bl0.service: Main process exited, 
code=exited, status=1/FAILURE
  Dec 14 13:26:05 T14S systemd[1]: 
systemd-backlight@backlight:amdgpu_bl0.service: Failed with result 'exit-code'.
  Dec 14 13:26:05 T14S systemd[1]: Failed to start Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0.

  mdmower@T14S ~ $ sudo systemctl start systemd-
  backlight@backlight:amdgpu_bl0

  mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0
  ● systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0
   Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static)
   Active: active (exited) since Tue 2021-12-14 13:26:45 PST; 1s ago
 Docs: man:systemd-backlight@.service(8)
  Process: 5119 ExecStart=/lib/systemd/systemd-backlight load 
backlight:amdgpu_bl0 (code=exited, status=0/SUCCESS)
 Main PID: 5119 (code=exited, status=0/SUCCESS)
  CPU: 5ms

  Dec 14 13:26:45 T14S systemd[1]: Starting Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0...
  Dec 14 13:26:45 T14S systemd[1]: Finished Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 14 13:29:38 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Cezanne [17aa:5095]
  InstallationDate: Installed on 2021-12-12 (2 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XF004WUS
  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.13.0-22-generic 
root=UUID=859a72cc-a3fe-470f-b525-37b15140828

[Touch-packages] [Bug 1958005] [NEW] rsyslogd mishandles startswith_i against $programname

[Ian! D. Allen]

Public bug reported:

The rsyslog program mis-handles the "startswith_i" comparison when applied
to $programname.  Details follow:

Put this file in /etc/rsyslog.d/10-idallen.conf (it precedes all other
files):

if ( $programname startswith 'foo' ) then {
/var/log/idallen-cron.log
stop
}

Restart rsyslog:

# /etc/init.d/rsyslog restart

Run these four tests:

$ logger -t 'test' "This is: test"
$ logger -t 'foo' "This is: foo"
$ logger -t 'FOO' "This is: FOO"
$ logger -t '/junk' "This is /junk"

Expected and correct result:

The file /var/log/syslog contains three lines (correct):

Jan 14 23:08:09 ubuntu20 test: This is: test
Jan 14 23:08:09 ubuntu20 FOO: This is: FOO
Jan 14 23:08:09 ubuntu20 /junk: This is /junk

The file /var/log/idallen-cron.log contains just one line (correct):

Jan 14 23:08:09 ubuntu20 foo: This is: foo


Now make this change: In the 10-idallen.conf file change "startswith"
to "startswith_i".  Restart rsyslog.  Run the four tests.  Here are the
unexpected and incorrect results:

The file /var/log/syslog contains just one line (should be two):

Jan 14 23:08:09 ubuntu20 test: This is: test

The file /var/log/idallen-cron.log contains three lines (should be two):

Jan 14 23:08:09 ubuntu20 foo: This is: foo
Jan 14 23:08:09 ubuntu20 FOO: This is: FOO
Jan 14 23:08:09 ubuntu20 /junk: This is /junk <== SHOULD NOT BE HERE

The '/junk' line should *NOT* be matched using "startswith_i 'foo'".

The same bug happens using '[junk' as the tag.  Any number of blanks
may precede the / or the [ character and still cause the bug.

$ logger -t '   /anything' "This also triggers the bug."
$ logger -t '   [anything' "This also triggers the bug."

The bug did not appear when matching against $syslogtag:

# This does not show the bug:
if ( $syslogtag startswith_i 'foo' ) then {
/var/log/idallen-cron.log
stop
}

I tried to use "startswith" and "startswith_i" to match against the
"$msg" instead of against "$programname" or "$syslogtag" but could not
get any match at all no matter what I used as my logger message text:

# This never matches anything:
if ( $msg startswith 'foo' ) then {
/var/log/idallen-cron.log
stop
}

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: rsyslog 8.2001.0-1ubuntu1.1
ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jan 15 02:02:24 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-10-07 (464 days ago)
InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: rsyslog
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.logrotate.d.rsyslog: [modified]
mtime.conffile..etc.logrotate.d.rsyslog: 2020-12-27T12:21:35.307395

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


** Tags: amd64 apport-bug focal third-party-packages

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

Title:
  rsyslogd mishandles startswith_i against $programname

Status in rsyslog package in Ubuntu:
  New

Bug description:
  The rsyslog program mis-handles the "startswith_i" comparison when applied
  to $programname.  Details follow:

  Put this file in /etc/rsyslog.d/10-idallen.conf (it precedes all other
  files):

  if ( $programname startswith 'foo' ) then {
  /var/log/idallen-cron.log
  stop
  }

  Restart rsyslog:

  # /etc/init.d/rsyslog restart

  Run these four tests:

  $ logger -t 'test' "This is: test"
  $ logger -t 'foo' "This is: foo"
  $ logger -t 'FOO' "This is: FOO"
  $ logger -t '/junk' "This is /junk"

  Expected and correct result:

  The file /var/log/syslog contains three lines (correct):

  Jan 14 23:08:09 ubuntu20 test: This is: test
  Jan 14 23:08:09 ubuntu20 FOO: This is: FOO
  Jan 14 23:08:09 ubuntu20 /junk: This is /junk

  The file /var/log/idallen-cron.log contains just one line (correct):

  Jan 14 23:08:09 ubuntu20 foo: This is: foo

  
  Now make this change: In the 10-idallen.conf file change "startswith"
  to "startswith_i".  Restart rsyslog.  Run the four tests.  Here are the
  unexpected and incorrect results:

  The file /var/log/syslog contains just one line (should be two):

  Jan 14 23:08:09 ubuntu20 test: This is: test

  The file /var/log/idallen-cron.log contains three lines (should be
  two):

  Jan 14 23:08:09 ubuntu20 foo: This is: foo
  Jan 14 23:08:09 ubuntu20 FOO: This is: FOO
  Jan 14 23:08:09 ubuntu20 /junk: This is /junk <== SHOULD NOT BE HERE

  The '/junk' line should *NOT* be matched using "startswith_i 'foo'".

  The same bug happens using '[junk' as the 

[Touch-packages] [Bug 1954843] Re: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument

[Matthew D. Mower]

I enabled debug logging for systemd with kernel cmdline:
systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M printk.devkmsg=on

New log attached to bug report is the output of 'journalctl -b':
systemd-debug.log

Filtering on "backlight" and omitting systemd-logind, this portion looks
interesting to my novice eyes. Does it imply the device loads after
systemd-backlight attempts to load the brightness value?

Dec 18 11:03:31 T14S systemd-backlight[1131]: amdgpu_bl0: Maximum brightness is 
255
Dec 18 11:03:31 T14S systemd-backlight[1131]: sd-device-enumerator: Scan all 
dirs
Dec 18 11:03:31 T14S systemd-backlight[1131]: sd-device-enumerator: Scanning 
/sys/bus
Dec 18 11:03:31 T14S systemd-backlight[1131]: sd-device-enumerator: Scanning 
/sys/class
Dec 18 11:03:31 T14S systemd-backlight[1131]: Using saved brightness 78.
Dec 18 11:03:31 T14S systemd-backlight[1131]: amdgpu_bl0: Failed to write 
system 'brightness' attribute: Invalid argument
Dec 18 11:03:31 T14S systemd[1217]: 
sys-devices-pci:00-:00:08.1-:05:00.0-backlight-amdgpu_bl0.device: 
Changed dead -> plugged
Dec 18 11:03:31 T14S systemd[1217]: 
sys-devices-platform-thinkpad_acpi-leds-tpacpi::kbd_backlight.device: Changed 
dead -> plugged
Dec 18 11:03:37 T14S systemd[3633]: 
sys-devices-pci:00-:00:08.1-:05:00.0-backlight-amdgpu_bl0.device: 
Changed dead -> plugged
Dec 18 11:03:37 T14S systemd[3633]: 
sys-devices-platform-thinkpad_acpi-leds-tpacpi::kbd_backlight.device: Changed 
dead -> plugged

** Attachment added: "journalctl -b with debug-level systemd logging"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954843/+attachment/5548522/+files/systemd-debug.log

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

Title:
  amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid
  argument

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

Bug description:
  Ubuntu 21.10 does not succeed at setting the display brightness after
  booting (either to the GNOME login screen or to a logged-in user's
  desktop). The brightness is at its highest level until I adjust it
  with keyboard shortcuts or a GUI tool.

  The systemd-backlight@backlight:amdgpu_bl0 service seems to fail
  during startup, but I can subsequently run it after startup and it
  succeeds (and restores brightness):

  mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0
  [sudo] password for mdmower: 
  × systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0
   Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static)
   Active: failed (Result: exit-code) since Tue 2021-12-14 13:26:05 PST; 
30s ago
 Docs: man:systemd-backlight@.service(8)
  Process: 962 ExecStart=/lib/systemd/systemd-backlight load 
backlight:amdgpu_bl0 (code=exited, status=1/FAILURE)
 Main PID: 962 (code=exited, status=1/FAILURE)
  CPU: 3ms

  Dec 14 13:26:05 T14S systemd[1]: Starting Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0...
  Dec 14 13:26:05 T14S systemd-backlight[962]: amdgpu_bl0: Failed to write 
system 'brightness' attribute: Invalid argument
  Dec 14 13:26:05 T14S systemd[1]: 
systemd-backlight@backlight:amdgpu_bl0.service: Main process exited, 
code=exited, status=1/FAILURE
  Dec 14 13:26:05 T14S systemd[1]: 
systemd-backlight@backlight:amdgpu_bl0.service: Failed with result 'exit-code'.
  Dec 14 13:26:05 T14S systemd[1]: Failed to start Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0.

  mdmower@T14S ~ $ sudo systemctl start systemd-
  backlight@backlight:amdgpu_bl0

  mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0
  ● systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0
   Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static)
   Active: active (exited) since Tue 2021-12-14 13:26:45 PST; 1s ago
 Docs: man:systemd-backlight@.service(8)
  Process: 5119 ExecStart=/lib/systemd/systemd-backlight load 
backlight:amdgpu_bl0 (code=exited, status=0/SUCCESS)
 Main PID: 5119 (code=exited, status=0/SUCCESS)
  CPU: 5ms

  Dec 14 13:26:45 T14S systemd[1]: Starting Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0...
  Dec 14 13:26:45 T14S systemd[1]: Finished Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: 

[Touch-packages] [Bug 1952533] [NEW] [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while

[John D Sheehan]

Public bug reported:

Sometimes if I run `pulseaudio -k` a few times, sound returns.
Sometimes if I run `sudo alsa force-reload`, sound returns.
Sometimes if I shutdown and start the laptop, sound returns.

This first occurred a few months ago when I was running 20.04, and I
upgraded to 21.10 in the hope it would fix the issue. It did not - sound
continues to be intermittent.

I use the Brave browser, not firefox.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  sheehan3636 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 27 20:21:47 2021
InstallationDate: Installed on 2021-10-15 (43 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_IE:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IE.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulseAudioLog:
 Nov 27 19:00:54 xps systemd[1436]: pulseaudio.service: Deactivated 
successfully.
 Nov 27 19:01:05 xps systemd[1436]: pulseaudio.socket: Deactivated successfully.
Symptom_Type: Sound works for a while, then breaks
Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2021
dmi.bios.release: 1.16
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.16.0
dmi.board.name: 0F6P3V
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd07/09/2021:br1.16:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:sku07E6:
dmi.product.family: XPS
dmi.product.name: XPS 13 9370
dmi.product.sku: 07E6
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-27T18:59:43.285943

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


** Tags: amd64 apport-bug impish wayland-session

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

Title:
  [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sometimes if I run `pulseaudio -k` a few times, sound returns.
  Sometimes if I run `sudo alsa force-reload`, sound returns.
  Sometimes if I shutdown and start the laptop, sound returns.

  This first occurred a few months ago when I was running 20.04, and I
  upgraded to 21.10 in the hope it would fix the issue. It did not -
  sound continues to be intermittent.

  I use the Brave browser, not firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sheehan3636 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 27 20:21:47 2021
  InstallationDate: Installed on 2021-10-15 (43 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IE:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IE.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   Nov 27 19:00:54 xps systemd[1436]: pulseaudio.service: Deactivated 
successfully.
   Nov 27 19:01:05 xps systemd[1436]: pulseaudio.socket: Deactivated 
successfully.
  Symptom_Type: Sound works for a while, then breaks
  Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2021
  dmi.bios.release: 1.16
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.0
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd07/09/2021:br1.16:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:sku07E6:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-27T18:59:43.285943

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


-- 

[Touch-packages] [Bug 1941752]

[K-d-hudson]

Created attachment 143424
New crash information added by DrKonqi

gwenview (20.12.3) using Qt 5.15.2

- What I was doing when the application crashed:

This is a little bizarre. I encountered this while rapidly scrolling
through thumbnails in a directory. One particular image reliably crashes
QwenView, but it isn't the image itself because QwenView opens the image
just fine if I copy it to another directory. If I copy just a few of the
images to another directory, QwenView also works just fine. The
directory contents are available online to replicate this issue. I
downloaded and replicated again just to be sure.

The directory contents are available online inside this archive:
https://downloads.open-
tx.org/2.3/release/sdcard/opentx-t16/sdcard-480x272-2.3V0025.zip. The
directory is IMAGES. The image QwenView crashes on is IMAGES/P51.jpg.

To replicate, extract the archive, and start clicking through the
images. I double clicked on in Dolphin to start.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#5  0x7f191f393864 in __GI_abort () at abort.c:79
[...]
#12 0x7f191f00a92d in Exiv2::Xmpdatum::write(std::ostream&, Exiv2::ExifData 
const*) const () from /lib/x86_64-linux-gnu/libexiv2.so.27
#13 0x7f1921515250 in 
Gwenview::ImageMetaInfoModel::setExiv2Image(Exiv2::Image const*) () from 
/lib/x86_64-linux-gnu/libgwenviewlib.so.5
#14 0x7f19214dfa70 in 
Gwenview::Document::setExiv2Image(std::unique_ptr >) () from 
/lib/x86_64-linux-gnu/libgwenviewlib.so.5

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

Title:
  Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening
  images exported by darktable

Status in Gwenview:
  Unknown
Status in exiv2 package in Ubuntu:
  Confirmed
Status in gwenview package in Ubuntu:
  Confirmed

Bug description:
  Since the recent security update of exiv2, Gwenview crashes when
  trying to open image files that got exported by darktable.

  Steps to reproduce:

  * Make a test installation of Kubuntu 21.04 in VirtualBox
  * Install all updates
  * Install darktable
  * Copy one of the images in /usr/share/wallpapers (or any other image) to 
your home directory and open it with darktable
  * Within darktable, export a copy of the image (no need to do any actual 
modifications)
  * Try to open that copy with Gwenview. Gwenview will crash.

  I'm attaching a crash report hinting that this is related to exiv2.

  Temporary workaround:
  If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so 
it seems the crash is related to changes in 0.27.3-3ubuntu1.5.

  I don't know if the underlying cause is actually some bug in exiv2,
  Gwenview or darktable.

  Kind regards, Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libexiv2-27 0.27.3-3ubuntu1.5
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Aug 26 15:16:47 2021
  InstallationDate: Installed on 2021-08-26 (0 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: exiv2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

[Maniraj D]

Hi Timo,

A similar crash is observed in mesa-egl and it is resolved in Mesa
master branch. Please refer the bug:
https://bugs.launchpad.net/mesa/+bug/1946621

Can you help backporting the fix to "Focal" series.

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

Title:
  Crash in libegl-mesa0 due to out of bound array access

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released

Bug description:
  Crash in libegl-mesa0 due to out of bound array access. Crash is fixed
  on Mesa master branch with change:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d
  .This bug is to request to include this change in Mesa upgrades in
  bionic.

  Please let me know if this change needs to be back ported to other
  branch so that libegl-mesa0 upgrade in Bionic could pick this change.

  lsb_release -a
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 18.0.0~rc5-1ubuntu1
Candidate: 18.0.0~rc5-1ubuntu1
Version table:
   *** 18.0.0~rc5-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1776499/+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 1946621] Re: Crash in libegl-mesa0 (eglReleaseThread)

[Maniraj D]

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #5466
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/5466

** Also affects: mesa via
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/5466
   Importance: Unknown
   Status: Unknown

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

Title:
  Crash in libegl-mesa0 (eglReleaseThread)

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Crash in libegl-mesa0 (in eglReleaseThread API), please find the
  backtrace:

  #0  0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) 
at pthread_mutex_lock.c:67
  #1  0xf4a7d110 in mtx_lock (mtx=0x8) at 
../include/c11/threads_posix.h:223
  #2  eglReleaseThread () at ../src/egl/main/eglapi.c:1713
  #3  0xf6c115b8 in eglReleaseThread () at 
/lib/aarch64-linux-gnu/libEGL.so.1
  #4  0xf7fdac00 in  () at /lib/ld-linux-aarch64.so.1
  #5  0xf7b4284c in __run_exit_handlers
  (status=0, listp=0xf7c76680 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at 
exit.c:108
  #6  0xf7b429dc in __GI_exit (status=) at exit.c:139
  #7  0xf7b2d094 in __libc_start_main (main=
  0x3530 , argc=13, argv=0xf488, init=, fini=, rtld_fini=, stack_end=)
  at ../csu/libc-start.c:342
  #8  0x4014 in _start ()

  It crashes at:
  https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713.
  'disp' pointer is being NULL in this case.

  Actually nvidia's EGL backend is being loaded by glvnd in this case.
  But the eglReleaseThread() implementation of glvnd calls the
  eglReleaseThread() API of all the vendors, that's how it end-up
  calling the eglReleaseThread() API of Mesa backend. Refer:
  https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.3 LTS
  Release:20.04
  Codename:   focal

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 21.0.3-0ubuntu0.3~20.04.2
Candidate: 21.0.3-0ubuntu0.3~20.04.2
Version table:
   *** 21.0.3-0ubuntu0.3~20.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   20.0.4-2ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1946621/+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 1948752] [NEW] apparmor is logging too many messages

[D-nl-k]

Public bug reported:

Unfortunately, this bug does not seem to be fixed yet.
My syslog is flooded with ALLOWED messages regarding redshift.

My system is a Kubuntu 21.04.
AppArmor is V. 3.0.0-0ubuntu7.1

Attached you'll find an excerpt from /var/log/syslog for the last 5
minutes.

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

** Attachment added: "5 Minutes excerpt of /var/lkog/syslog"
   https://bugs.launchpad.net/bugs/1948752/+attachment/5536110/+files/syslog

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

Title:
  apparmor is logging too many messages

Status in apparmor package in Ubuntu:
  New

Bug description:
  Unfortunately, this bug does not seem to be fixed yet.
  My syslog is flooded with ALLOWED messages regarding redshift.

  My system is a Kubuntu 21.04.
  AppArmor is V. 3.0.0-0ubuntu7.1

  Attached you'll find an excerpt from /var/log/syslog for the last 5
  minutes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1948752/+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 1946621] Re: Crash in libegl-mesa0 (eglReleaseThread)

[Maniraj D]

PR: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13302 is
merged on Mesa master branch:
https://gitlab.freedesktop.org/maniraj87/mesa/-/commit/796c9ab3fd6b897ae3b3c069568182178c7661d4

Please include this change in Mesa upgrades in "Focal" series.

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

Title:
  Crash in libegl-mesa0 (eglReleaseThread)

Status in mesa package in Ubuntu:
  New

Bug description:
  Crash in libegl-mesa0 (in eglReleaseThread API), please find the
  backtrace:

  #0  0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) 
at pthread_mutex_lock.c:67
  #1  0xf4a7d110 in mtx_lock (mtx=0x8) at 
../include/c11/threads_posix.h:223
  #2  eglReleaseThread () at ../src/egl/main/eglapi.c:1713
  #3  0xf6c115b8 in eglReleaseThread () at 
/lib/aarch64-linux-gnu/libEGL.so.1
  #4  0xf7fdac00 in  () at /lib/ld-linux-aarch64.so.1
  #5  0xf7b4284c in __run_exit_handlers
  (status=0, listp=0xf7c76680 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at 
exit.c:108
  #6  0xf7b429dc in __GI_exit (status=) at exit.c:139
  #7  0xf7b2d094 in __libc_start_main (main=
  0x3530 , argc=13, argv=0xf488, init=, fini=, rtld_fini=, stack_end=)
  at ../csu/libc-start.c:342
  #8  0x4014 in _start ()

  It crashes at:
  https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713.
  'disp' pointer is being NULL in this case.

  Actually nvidia's EGL backend is being loaded by glvnd in this case.
  But the eglReleaseThread() implementation of glvnd calls the
  eglReleaseThread() API of all the vendors, that's how it end-up
  calling the eglReleaseThread() API of Mesa backend. Refer:
  https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.3 LTS
  Release:20.04
  Codename:   focal

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 21.0.3-0ubuntu0.3~20.04.2
Candidate: 21.0.3-0ubuntu0.3~20.04.2
Version table:
   *** 21.0.3-0ubuntu0.3~20.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   20.0.4-2ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1946621/+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 1946621] Re: Crash in libegl-mesa0 (eglReleaseThread)

[Maniraj D]

Root caused the issue with Mesa-EGL, created a PR for the same:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13302

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

Title:
  Crash in libegl-mesa0 (eglReleaseThread)

Status in mesa package in Ubuntu:
  New

Bug description:
  Crash in libegl-mesa0 (in eglReleaseThread API), please find the
  backtrace:

  #0  0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) 
at pthread_mutex_lock.c:67
  #1  0xf4a7d110 in mtx_lock (mtx=0x8) at 
../include/c11/threads_posix.h:223
  #2  eglReleaseThread () at ../src/egl/main/eglapi.c:1713
  #3  0xf6c115b8 in eglReleaseThread () at 
/lib/aarch64-linux-gnu/libEGL.so.1
  #4  0xf7fdac00 in  () at /lib/ld-linux-aarch64.so.1
  #5  0xf7b4284c in __run_exit_handlers
  (status=0, listp=0xf7c76680 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at 
exit.c:108
  #6  0xf7b429dc in __GI_exit (status=) at exit.c:139
  #7  0xf7b2d094 in __libc_start_main (main=
  0x3530 , argc=13, argv=0xf488, init=, fini=, rtld_fini=, stack_end=)
  at ../csu/libc-start.c:342
  #8  0x4014 in _start ()

  It crashes at:
  https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713.
  'disp' pointer is being NULL in this case.

  Actually nvidia's EGL backend is being loaded by glvnd in this case.
  But the eglReleaseThread() implementation of glvnd calls the
  eglReleaseThread() API of all the vendors, that's how it end-up
  calling the eglReleaseThread() API of Mesa backend. Refer:
  https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.3 LTS
  Release:20.04
  Codename:   focal

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 21.0.3-0ubuntu0.3~20.04.2
Candidate: 21.0.3-0ubuntu0.3~20.04.2
Version table:
   *** 21.0.3-0ubuntu0.3~20.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   20.0.4-2ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1946621/+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 1946621] Re: Crash in libegl-mesa0 (eglReleaseThread)

[Maniraj D]

The crash happens only when calling eglReleaseThread() from destructor
of the process. Please find the attached simple app which can be used to
repro the issue.

With valgrind, I see there is some invalid memory access during the
eglReleaseThread() call. Find the logs below:

==5059== Invalid read of size 8
==5059==at 0x70480EC: eglReleaseThread (eglapi.c:1706)
==5059==by 0x48825B7: eglReleaseThread (in 
/usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0)
==5059==by 0x1089FB: deinit (in /home/ubuntu/egl_sample/egl_sample)
==5059==by 0x400EBFF: _dl_fini (dl-fini.c:138)
==5059==by 0x48DC84B: __run_exit_handlers (exit.c:108)
==5059==by 0x48DC9DB: exit (exit.c:139)
==5059==by 0x48C7093: (below main) (libc-start.c:342)
==5059==  Address 0x4c6f8c8 is 8 bytes inside a block of size 48 free'd
==5059==at 0x484AF20: free (in 
/usr/lib/aarch64-linux-gnu/valgrind/vgpreload_memcheck-arm64-linux.so)
==5059==by 0x7051FE3: _eglDestroyThreadInfo (eglcurrent.c:134)
==5059==by 0x7051FE3: _eglFiniTSD (eglcurrent.c:76)
==5059==by 0x70539CF: _eglAtExit (eglglobals.c:112)
==5059==by 0x48DC84B: __run_exit_handlers (exit.c:108)
==5059==by 0x48DC9DB: exit (exit.c:139)
==5059==by 0x48C7093: (below main) (libc-start.c:342)  

So eglReleaseThread() in this case, tries to access the _EGLThreadInfo
memory already freed by _eglFiniTSD() ? But it is expected that a new
instance of _EGLThreadInfo has to be created when eglReleaseThread() is
called from the app in this case.

** Attachment added: "egl_sample.tar"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1946621/+attachment/5531907/+files/egl_sample.tar

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

Title:
  Crash in libegl-mesa0 (eglReleaseThread)

Status in mesa package in Ubuntu:
  New

Bug description:
  Crash in libegl-mesa0 (in eglReleaseThread API), please find the
  backtrace:

  #0  0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) 
at pthread_mutex_lock.c:67
  #1  0xf4a7d110 in mtx_lock (mtx=0x8) at 
../include/c11/threads_posix.h:223
  #2  eglReleaseThread () at ../src/egl/main/eglapi.c:1713
  #3  0xf6c115b8 in eglReleaseThread () at 
/lib/aarch64-linux-gnu/libEGL.so.1
  #4  0xf7fdac00 in  () at /lib/ld-linux-aarch64.so.1
  #5  0xf7b4284c in __run_exit_handlers
  (status=0, listp=0xf7c76680 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at 
exit.c:108
  #6  0xf7b429dc in __GI_exit (status=) at exit.c:139
  #7  0xf7b2d094 in __libc_start_main (main=
  0x3530 , argc=13, argv=0xf488, init=, fini=, rtld_fini=, stack_end=)
  at ../csu/libc-start.c:342
  #8  0x4014 in _start ()

  It crashes at:
  https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713.
  'disp' pointer is being NULL in this case.

  Actually nvidia's EGL backend is being loaded by glvnd in this case.
  But the eglReleaseThread() implementation of glvnd calls the
  eglReleaseThread() API of all the vendors, that's how it end-up
  calling the eglReleaseThread() API of Mesa backend. Refer:
  https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.3 LTS
  Release:20.04
  Codename:   focal

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 21.0.3-0ubuntu0.3~20.04.2
Candidate: 21.0.3-0ubuntu0.3~20.04.2
Version table:
   *** 21.0.3-0ubuntu0.3~20.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   20.0.4-2ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1946621/+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 1946621] [NEW] Crash in libegl-mesa0 (eglReleaseThread)

[Maniraj D]

Public bug reported:

Crash in libegl-mesa0 (in eglReleaseThread API), please find the
backtrace:

#0  0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) at 
pthread_mutex_lock.c:67
#1  0xf4a7d110 in mtx_lock (mtx=0x8) at 
../include/c11/threads_posix.h:223
#2  eglReleaseThread () at ../src/egl/main/eglapi.c:1713
#3  0xf6c115b8 in eglReleaseThread () at 
/lib/aarch64-linux-gnu/libEGL.so.1
#4  0xf7fdac00 in  () at /lib/ld-linux-aarch64.so.1
#5  0xf7b4284c in __run_exit_handlers
(status=0, listp=0xf7c76680 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at 
exit.c:108
#6  0xf7b429dc in __GI_exit (status=) at exit.c:139
#7  0xf7b2d094 in __libc_start_main (main=
0x3530 , argc=13, argv=0xf488, init=, 
fini=, rtld_fini=, stack_end=)
at ../csu/libc-start.c:342
#8  0x4014 in _start ()

It crashes at:
https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713.
'disp' pointer is being NULL in this case.

Actually nvidia's EGL backend is being loaded by glvnd in this case. But
the eglReleaseThread() implementation of glvnd calls the
eglReleaseThread() API of all the vendors, that's how it end-up calling
the eglReleaseThread() API of Mesa backend. Refer:
https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.3 LTS
Release:20.04
Codename:   focal

apt-cache policy libegl-mesa0
libegl-mesa0:
  Installed: 21.0.3-0ubuntu0.3~20.04.2
  Candidate: 21.0.3-0ubuntu0.3~20.04.2
  Version table:
 *** 21.0.3-0ubuntu0.3~20.04.2 500
500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 
Packages
100 /var/lib/dpkg/status
 20.0.4-2ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages

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

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

Title:
  Crash in libegl-mesa0 (eglReleaseThread)

Status in mesa package in Ubuntu:
  New

Bug description:
  Crash in libegl-mesa0 (in eglReleaseThread API), please find the
  backtrace:

  #0  0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) 
at pthread_mutex_lock.c:67
  #1  0xf4a7d110 in mtx_lock (mtx=0x8) at 
../include/c11/threads_posix.h:223
  #2  eglReleaseThread () at ../src/egl/main/eglapi.c:1713
  #3  0xf6c115b8 in eglReleaseThread () at 
/lib/aarch64-linux-gnu/libEGL.so.1
  #4  0xf7fdac00 in  () at /lib/ld-linux-aarch64.so.1
  #5  0xf7b4284c in __run_exit_handlers
  (status=0, listp=0xf7c76680 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at 
exit.c:108
  #6  0xf7b429dc in __GI_exit (status=) at exit.c:139
  #7  0xf7b2d094 in __libc_start_main (main=
  0x3530 , argc=13, argv=0xf488, init=, fini=, rtld_fini=, stack_end=)
  at ../csu/libc-start.c:342
  #8  0x4014 in _start ()

  It crashes at:
  https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713.
  'disp' pointer is being NULL in this case.

  Actually nvidia's EGL backend is being loaded by glvnd in this case.
  But the eglReleaseThread() implementation of glvnd calls the
  eglReleaseThread() API of all the vendors, that's how it end-up
  calling the eglReleaseThread() API of Mesa backend. Refer:
  https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.3 LTS
  Release:20.04
  Codename:   focal

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 21.0.3-0ubuntu0.3~20.04.2
Candidate: 21.0.3-0ubuntu0.3~20.04.2
Version table:
   *** 21.0.3-0ubuntu0.3~20.04.2 500
  500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   20.0.4-2ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages

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

[steve d]

Closing this bug as it works for me (Xubuntu 20.04) and we've not seen
any reports of this problem for many years.

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

Title:
  Audacity ruins bluetooth

Status in Audacity:
  Invalid
Status in audacity package in Ubuntu:
  Incomplete
Status in portaudio package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: audacity

  Apparently Audacity is not smart enough to know that it's running
  under a Gnome environment. Everything in terms of audio devices is
  managed quite well with pulseaudio, bluetooth-applet, and other Gnome
  desktop infrastructure. It tries to hard and breaks it. It tries to
  hack into my bluetooth in a vain attempt to find a headset or
  something like that and it ruins my bluetooth support in the desktop.
  I am no longer able to send files or use bluetooth in anyway.

  First thing it does when you launch it is that it does nothing. It'll
  just hang. You click on the icon in the menu and you won't get any
  feedback. Even if you run it from the command line it will give no
  feedback and display no errors. It just hangs.

  Then you kill it and restart it a couple times and it launches successfully. 
Sorta. Besides the globalmenu bug reported in another report it displays this 
error on my terminal:
  $ audacity 
  bt_audio_service_open: connect() failed: Connection refused (111)
  bt_audio_service_open: connect() failed: Connection refused (111)
  bt_audio_service_open: connect() failed: Connection refused (111)
  bt_audio_service_open: connect() failed: Connection refused (111)
  Cannot connect to server socket err = No such file or directory
  Cannot connect to server socket
  jack server is not running or cannot be started
  Expression 'stream->capture.pcm' failed in 
'src/hostapi/alsa/pa_linux_alsa.c', line: 3653

  
  Here is the errors reported by dmesg:

  [  807.086761] EXT4-fs (dm-0): re-mounted. Opts: commit=0
  [  812.790151] usb 6-1: USB disconnect, address 2
  [  812.790881] btusb_intr_complete: hci0 urb 88010e8e1600 failed to 
resubmit (19)
  [  812.790905] btusb_bulk_complete: hci0 urb 88010e8e1c00 failed to 
resubmit (19)
  [  812.791892] btusb_bulk_complete: hci0 urb 8801185a93c0 failed to 
resubmit (19)
  [  812.792064] btusb_send_frame: hci0 urb 8800c0872e40 submission failed
  [  813.322598] usb 6-1: new full speed USB device using uhci_hcd and address 3
  [  900.790130] usb 6-1: USB disconnect, address 3
  [  900.790753] btusb_intr_complete: hci0 urb 8800cba0d6c0 failed to 
resubmit (19)
  [  900.790784] btusb_bulk_complete: hci0 urb 8800c0805d80 failed to 
resubmit (19)
  [  900.791836] btusb_bulk_complete: hci0 urb 8800c0805180 failed to 
resubmit (19)
  [  900.792039] btusb_send_frame: hci0 urb 8800c08ddf00 submission failed
  [  900.807505] bluetooth-apple[2004]: segfault at a ip 7f65d520c9ee sp 
7fffba728880 error 4 in libdbusmenu-glib.so.1.0.17[7f65d5208000+1]
  [  901.320309] usb 6-1: new full speed USB device using uhci_hcd and address 4
  [ 1308.540165] usb 6-1: USB disconnect, address 4
  [ 1308.541015] btusb_intr_complete: hci0 urb 8800c0b18840 failed to 
resubmit (19)
  [ 1308.541045] btusb_bulk_complete: hci0 urb 8800c099eb40 failed to 
resubmit (19)
  [ 1308.542097] btusb_bulk_complete: hci0 urb 8800c0b180c0 failed to 
resubmit (19)
  [ 1308.542300] btusb_send_frame: hci0 urb 88010f313540 submission failed


  At that point my bluetooth support is broken and thus Audacity will
  successfully open. After hitting ctrl-f to work around the globalmenu
  bug (even though I am not using global menu) I can then edit files and
  such. Save them. Everything works.

  Of course I can no longer connect to the internet through my phone,
  send files, upload ringtones, use my bluetooth headset, etc. To work
  around you can remove the USB bluetooth adapter if you use a external
  one, plug it back in, and launch bluetooth-applet from the command
  line and it should be working again.

  It's not the end of the world, but Audacity should be configured to
  work properly in the default environment.

  I suggest eliminating Alsa and bluetooth support and have it not try
  to fight proper daemons handle it as they do a much better job. At
  least with PA and Bluetooth. I don't know how well Jack supports
  bluetooth audio devices, but Audacity really should not be allowed to
  do this sort of thing. I understand that it seems like a nice feature
  to be able to use a headset outside of Gnome, but it seems to be
  fundamentally incompatible with having a bluetooth adapter that is
  able to work with any other device.

  
  For people that may run into this problem in the future through Google or 
whatever here is two work arounds I suggest:

  1. Remove or 

[Touch-packages] [Bug 1944459] [NEW] systemd-udevd NamePolicy= warning issue

[Deny D.]

Public bug reported:

So I'm getting a warning on syslog:

"ubuntu systemd-udevd[911]: Network interface NamePolicy= disabled on
kernel command line, ignoring."

I've seen another similar report which seems to be fixed back in 2015:

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1411992

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.13
ProcVersionSignature: Ubuntu 5.4.0-1043.47-raspi 5.4.133
Uname: Linux 5.4.0-1043-raspi armv7l
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: armhf
CasperMD5CheckResult: skip
Date: Tue Sep 21 20:46:59 2021
ImageMediaBuild: 20210819.1
Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 3.0 
Host Controller
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
 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/4p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
 |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
 |__ Port 2: Dev 3, If 0, Class=Vendor Specific Class, Driver=usbfs, 
480M
 |__ Port 2: Dev 3, If 1, Class=Vendor Specific Class, Driver=, 480M
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=0 
bcm2708_fb.fbheight=0 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:66:9F:A2 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait fixrtc fsck.mode=auto 
fsck.repair=yes ipv6.disable=1 bcm2835_wdt.nowayout=1 bcm2835_wdt.heartbeat=10 
quiet splash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
 
mtime.conffile..etc.systemd.resolved.conf: 2021-09-21T18:08:30.647280

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


** Tags: apport-bug armhf armhf-image focal raspi-image uec-images

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

Title:
  systemd-udevd NamePolicy= warning issue

Status in systemd package in Ubuntu:
  New

Bug description:
  So I'm getting a warning on syslog:

  "ubuntu systemd-udevd[911]: Network interface NamePolicy= disabled on
  kernel command line, ignoring."

  I've seen another similar report which seems to be fixed back in 2015:

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1411992

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.13
  ProcVersionSignature: Ubuntu 5.4.0-1043.47-raspi 5.4.133
  Uname: Linux 5.4.0-1043-raspi armv7l
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: armhf
  CasperMD5CheckResult: skip
  Date: Tue Sep 21 20:46:59 2021
  ImageMediaBuild: 20210819.1
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
   Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
   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/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
   |__ Port 2: Dev 3, If 0, Class=Vendor Specific Class, Driver=usbfs, 
480M
   |__ Port 2: Dev 3, If 1, Class=Vendor Specific Class, Driver=, 480M
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=0 
bcm2708_fb.fbheight=0 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:66:9F:A2 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait fixrtc fsck.mode=auto 
fsck.repair=yes ipv6.disable=1 bcm2835_wdt.nowayout=1 bcm2835_wdt.heartbeat=10 
quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  mtime.conffile..etc.systemd.resolved.conf: 2021-09-21T18:08:30.647280

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


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

[Touch-packages] [Bug 1940545] Re: Update Mesa to mesa-21.1.7 on Ubuntu 20.04

[Maniraj D]

Will that be updated only on impish (21.10) ? Actually we need the
update on focal (20.04).

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

Title:
  Update Mesa to mesa-21.1.7 on Ubuntu 20.04

Status in mesa package in Ubuntu:
  New

Bug description:
  With the recent MR
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to
  Mesa, we (NVIDIA) have added ability to GBM to dynamically load the
  backends. So we request to upgrade mesa libs to its latest version
  (mesa-21.1.7) on Ubuntu 20.04 to use the added feature for our
  development.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1940545/+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 1940545] Re: Update Mesa to mesa-21.1.7 on Ubuntu 20.04

[Maniraj D]

** Description changed:

  With the recent MR
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to Mesa,
- we have added ability to GBM to dynamically load the backends. So we
- request to upgrade mesa libs to its latest version (mesa-21.1.7) on
- Ubuntu 20.04 to use the added feature for our development.
+ we (NVIDIA) have added ability to GBM to dynamically load the backends.
+ So we request to upgrade mesa libs to its latest version (mesa-21.1.7)
+ on Ubuntu 20.04 to use the added feature for our development.

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

Title:
  Update Mesa to mesa-21.1.7 on Ubuntu 20.04

Status in mesa package in Ubuntu:
  New

Bug description:
  With the recent MR
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to
  Mesa, we (NVIDIA) have added ability to GBM to dynamically load the
  backends. So we request to upgrade mesa libs to its latest version
  (mesa-21.1.7) on Ubuntu 20.04 to use the added feature for our
  development.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1940545/+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 1940545] [NEW] Update Mesa to mesa-21.1.7 on Ubuntu 20.04

[Maniraj D]

Public bug reported:

With the recent MR
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to Mesa,
we (NVIDIA) have added ability to GBM to dynamically load the backends.
So we request to upgrade mesa libs to its latest version (mesa-21.1.7)
on Ubuntu 20.04 to use the added feature for our development.

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

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

Title:
  Update Mesa to mesa-21.1.7 on Ubuntu 20.04

Status in mesa package in Ubuntu:
  New

Bug description:
  With the recent MR
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to
  Mesa, we (NVIDIA) have added ability to GBM to dynamically load the
  backends. So we request to upgrade mesa libs to its latest version
  (mesa-21.1.7) on Ubuntu 20.04 to use the added feature for our
  development.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1940545/+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 1925742] Re: Recent iCloud versions trigger an issue in IMAP x

[Ivan D]

Tested on: Ubuntu 21.04
Package: evolution-data-server 3.40.1-2 (from Impish-proposed)

There aren't packages for hursuit (21.04) but I just tried the impish
(21.10) package and works.

Thanks again

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

Title:
  Recent iCloud versions trigger an issue in IMAP x

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Focal:
  Fix Committed

Bug description:
  * Impact

  The Icloud service introduced changes that are confusing evolution-
  data-server which means evolution is now failing to connect to the
  email server

  * Test case

  Set up an iCloud account and try to use it for emails in evolution

  * Regression potential

  The change is in the imapx connection code, it could create problems
  with other type of servers so we should try to test on different
  providers.

  
  -


  The bug has been fixed yesterday by Evolution's developer:
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1468

  However, the package in Ubuntu (at least in Focal Fosa) still needs to
  be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1925742] Re: Recent iCloud versions trigger an issue in IMAP x

[Ivan D]

Tested on: Ubuntu 20.04.2 LTS
Package: evolution-data-server 3.36.5-0ubuntu1 amd64

Personal iCloud account, now is solved.

Thanks

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

Title:
  Recent iCloud versions trigger an issue in IMAP x

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Focal:
  Fix Committed

Bug description:
  * Impact

  The Icloud service introduced changes that are confusing evolution-
  data-server which means evolution is now failing to connect to the
  email server

  * Test case

  Set up an iCloud account and try to use it for emails in evolution

  * Regression potential

  The change is in the imapx connection code, it could create problems
  with other type of servers so we should try to test on different
  providers.

  
  -


  The bug has been fixed yesterday by Evolution's developer:
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1468

  However, the package in Ubuntu (at least in Focal Fosa) still needs to
  be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1915908] [NEW] package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit statu

[Chetas D L]

Public bug reported:

sh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: activating (auto-restart) (Result: exit-code) since Wed 2021-02-17 
15:42:28 IST; 11ms ago
   Docs: man:sshd(8)
 man:sshd_config(5)
Process: 24813 ExecStartPre=/usr/sbin/sshd -t (code=exited, 
status=255/EXCEPTION)
dpkg: error processing package openssh-server (--configure):
 installed openssh-server package post-installation script subprocess returned 
error exit status 1
Processing triggers for systemd (245.4-4ubuntu3.4) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for ufw (0.36-6) ...
Errors were encountered while processing:
 openssh-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: openssh-server 1:8.2p1-4ubuntu0.1
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
AptOrdering:
 openssh-server:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Feb 17 15:42:28 2021
ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2021-01-05 (42 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python3.8, Python 3.8.5, python-is-python3, 3.8.2-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
/etc/ssh/sshd_config line 1: garbage at end of line; "to".
SourcePackage: openssh
Title: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to focal on 2021-02-04 (12 days ago)

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


** Tags: amd64 apport-package focal

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

Title:
  package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  sh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
   Active: activating (auto-restart) (Result: exit-code) since Wed 
2021-02-17 15:42:28 IST; 11ms ago
 Docs: man:sshd(8)
   man:sshd_config(5)
  Process: 24813 ExecStartPre=/usr/sbin/sshd -t (code=exited, 
status=255/EXCEPTION)
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Processing triggers for systemd (245.4-4ubuntu3.4) ...
  Processing triggers for man-db (2.9.1-1) ...
  Processing triggers for ufw (0.36-6) ...
  Errors were encountered while processing:
   openssh-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: openssh-server 1:8.2p1-4ubuntu0.1
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  AptOrdering:
   openssh-server:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb 17 15:42:28 2021
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-01-05 (42 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.5, python-is-python3, 3.8.2-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 
255: /etc/ssh/sshd_config line 1: garbage at end of line; "to".
  SourcePackage: openssh
  Title: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2021-02-04 (12 days ago)

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

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

[Touch-packages] [Bug 1915198] Re: "Dummy output" instead of the audio device ALC268

[D]

Hello Daniel,

Packages named 'timidity' or 'pipewire' are not installed. File
packages.txt in attachment.

Regards, Dmitriy.

** Attachment added: "packages.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1915198/+attachment/5462367/+files/packages.txt

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

Title:
  "Dummy output" instead of the audio device ALC268

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hello Support,

  "Dummy output" in Sound settings. nothing works.

  $ aplay -l
   List of PLAYBACK Hardware Devices 

  $ alsa-info.sh link to http://alsa-
  project.org/db/?f=834b3fe04e2e1c74c7f2a84b6fb698e6e49db8fa.

  # dmidecode -t system
  # dmidecode 3.2
  Getting SMBIOS data from sysfs.
  SMBIOS 2.4 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
Manufacturer: TOSHIBA
Product Name: Satellite U300
Version: PSU30E-01M01DRU

  # lspci |grep Audio
  00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio 
Controller (rev 03)
  00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio 
Controller [8086:284b] (rev 03)
Subsystem: Toshiba Corporation 82801H (ICH8 Family) HD Audio Controller 
[1179:ff50]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  Physical device is ALC268.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.10
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  9 22:37:35 2021
  InstallationDate: Installed on 2021-02-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2009
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V5.10
  dmi.board.name: Satellite U300
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV5.10:bd01/15/2009:svnTOSHIBA:pnSatelliteU300:pvrPSU30E-01M01DRU:rvnTOSHIBA:rnSatelliteU300:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite U300
  dmi.product.version: PSU30E-01M01DRU
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1915198/+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 1914284] [NEW] package gzip 1.10-2ubuntu1 failed to install/upgrade: unable to make backup link of './bin/zless' before installing new version: Input/output error

[John D Brown, MD]

Public bug reported:

installing plocate before mlocate

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: gzip 1.10-2ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair
Architecture: amd64
Date: Tue Feb  2 19:00:41 2021
Df:
 
ErrorMessage: unable to make backup link of './bin/zless' before installing new 
version: Input/output error
PythonDetails: N/A
SourcePackage: gzip
Title: package gzip 1.10-2ubuntu1 failed to install/upgrade: unable to make 
backup link of './bin/zless' before installing new version: Input/output error
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package groovy

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

Title:
  package gzip 1.10-2ubuntu1 failed to install/upgrade: unable to make
  backup link of './bin/zless' before installing new version:
  Input/output error

Status in gzip package in Ubuntu:
  New

Bug description:
  installing plocate before mlocate

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: gzip 1.10-2ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair
  Architecture: amd64
  Date: Tue Feb  2 19:00:41 2021
  Df:
   
  ErrorMessage: unable to make backup link of './bin/zless' before installing 
new version: Input/output error
  PythonDetails: N/A
  SourcePackage: gzip
  Title: package gzip 1.10-2ubuntu1 failed to install/upgrade: unable to make 
backup link of './bin/zless' before installing new version: Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1914284/+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 1481779] Re: apt-get autoremove crashes my system

[Jahoner D]

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

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

Title:
  apt-get autoremove crashes my system

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04 Server Gnome - 3.19.0-25-generic #26-Ubuntu SMP Fri Jul 24 
21:17:31 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
  apt 1.0.9.7

  If I try to clean my system with "sudo apt-get autoremove":
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
acpi-support app-install-data-partner apturl apturl-common argyll 
argyll-ref baobab bluez-alsa bluez-cups brltty cheese dc deja-dup
deja-dup-backend-cloudfiles deja-dup-backend-gvfs deja-dup-backend-s3 
duplicity folks-common fonts-cantarell fonts-guru fonts-guru-extra
fonts-kacst fonts-kacst-one fonts-khmeros-core fonts-lao 
fonts-lklug-sinhala fonts-lohit-guru fonts-sil-abyssinica fonts-sil-padauk
fonts-thai-tlwg fonts-tibetan-machine fonts-tlwg-garuda fonts-tlwg-kinnari 
fonts-tlwg-laksaman fonts-tlwg-loma fonts-tlwg-mono fonts-tlwg-norasi
fonts-tlwg-purisa fonts-tlwg-sawasdee fonts-tlwg-typewriter 
fonts-tlwg-typist fonts-tlwg-typo fonts-tlwg-umpush fonts-tlwg-waree gdm 
geoclue-2.0
gir1.2-accountsservice-1.0 gir1.2-champlain-0.12 gir1.2-gck-1 gir1.2-gcr-3 
gir1.2-gdata-0.0 gir1.2-gdm-1.0 gir1.2-geocodeglib-1.0 gir1.2-gkbd-3.0
gir1.2-goa-1.0 gir1.2-gtkchamplain-0.12 gir1.2-gweather-3.0 
gir1.2-mutter-3.0 gir1.2-rb-3.0 gir1.2-rest-0.7 gir1.2-telepathyglib-0.12
gir1.2-telepathylogger-0.2 gir1.2-tracker-1.0 gir1.2-udisks-2.0 
gir1.2-upowerglib-1.0 gir1.2-xkl-1.0 gir1.2-zpj-0.0 gjs gnome-backgrounds
gnome-calculator gnome-color-manager gnome-contacts gnome-dictionary 
gnome-disk-utility gnome-documents gnome-font-viewer gnome-maps
gnome-online-accounts gnome-online-miners gnome-orca gnome-screenshot 
gnome-session-canberra gnome-shell gnome-shell-common gnome-shell-extensions
gnome-system-log gnome-tweak-tool gnome-video-effects gnome-weather 
gstreamer0.10-alsa gstreamer0.10-nice gstreamer1.0-nice gucharmap gvfs-fuse
hamster-applet hamster-indicator ibus-pinyin ibus-table inputattach 
intel-gpu-tools itstool kerneloops-daemon libavahi-gobject0 libavahi-ui-gtk3-0
libbrlapi0.6 libcaribou-gtk-module libcaribou-gtk3-module 
libchamplain-0.12-0 libchamplain-gtk-0.12-0 libdiscid0 libdotconf0 
libfarstream-0.1-0
libfarstream-0.2-2 libfolks-eds25 libfolks-telepathy25 libfolks25 
libgdict-1.0-6 libgdict-common libgdm1 libgexiv2-2 libgfbgraph-0.2-0
libgpod-common libgpod4 libgsf-1-114 libgsf-1-common libgupnp-igd-1.0-4 
liblouis-data liblouis2 libmeanwhile1 libminiupnpc10
libmission-control-plugins0 libnatpmp1 libnice10 libnotify-bin 
libnss-myhostname libopencc1 libproxy1-plugin-gsettings
libproxy1-plugin-networkmanager libpurple-bin libpurple0 libpyzy-1.0-0 
libraw10 librhythmbox-core8 librsync1 librygel-core-2.4-2
librygel-renderer-2.4-2 librygel-renderer-gst-2.4-2 librygel-server-2.4-2 
libsofia-sip-ua-glib3 libsofia-sip-ua0 libspeechd2
libtelepathy-farstream3 libtelepathy-logger3 libtracker-control-1.0-0 
libtracker-miner-1.0-0 libunity-control-center1 libxp6 libzapojit-0.0-0
libzephyr4 mscompress nautilus-share oneconf oneconf-common pcmciautils 
policykit-desktop-privileges printer-driver-brlaser printer-driver-c2esp
printer-driver-foo2zjs printer-driver-foo2zjs-common 
printer-driver-min12xxw printer-driver-pnm2ppa printer-driver-ptouch 
printer-driver-pxljr
printer-driver-sag-gdi printer-driver-splix pulseaudio-module-bluetooth 
python-appindicator python-boto python-cloudfiles python-cups
python-debtagshw python-lockfile python-notify python-oneconf 
python-piston-mini-client python-wnck python3-brlapi python3-louis python3-mako
python3-oauthlib python3-oneconf python3-piston-mini-client python3-pyatspi 
python3-speechd realmd rfkill rhythmbox rhythmbox-data
rhythmbox-mozilla rhythmbox-plugin-cdrecorder rhythmbox-plugin-magnatune 
rhythmbox-plugin-zeitgeist rhythmbox-plugins rygel rygel-playbin
rygel-preferences seahorse shotwell shotwell-common 
signon-keyring-extension signon-plugin-oauth2 simple-scan software-center
software-center-aptdaemon-plugins sound-juicer speech-dispatcher 
speech-dispatcher-audio-plugins syslinux syslinux-common syslinux-legacy
telepathy-gabble telepathy-haze telepathy-idle telepathy-logger 
telepathy-mission-control-5 telepathy-rakia telepathy-salut toshset tracker
tracker-extract tracker-gui tracker-miner-fs tracker-utils 
transmission-common transmission-gtk ttf-ancient-fonts-symbola 
ttf-indic-fonts-core
ubuntu-gnome-default-settings unity-asset-pool usb-creator-common 
usb-creator-gtk vino whoopsie x11-apps x11-session-utils xbrlapi
xdg-user-dirs-gtk xdiagnose xinit xorg 

[Touch-packages] [Bug 1908025] [NEW] export var=~root does not expand ~root to /root

[Ian! D. Allen]

Public bug reported:

Shouldn't these give the same results in dash, i.e. "/root"?
They give the same output in bash.

$ dash
$ var=~root
$ echo "$var"
/root
$ export var=~root
$ echo "$var"
~root

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: dash 0.5.10.2-6
ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
Uname: Linux 5.4.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Dec 14 00:14:44 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-10-07 (67 days ago)
InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: dash
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  export var=~root does not expand ~root to /root

Status in dash package in Ubuntu:
  New

Bug description:
  Shouldn't these give the same results in dash, i.e. "/root"?
  They give the same output in bash.

  $ dash
  $ var=~root
  $ echo "$var"
  /root
  $ export var=~root
  $ echo "$var"
  ~root

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: dash 0.5.10.2-6
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Dec 14 00:14:44 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-10-07 (67 days ago)
  InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: dash
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1908025/+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 1718927] Re: No HDMI sound after suspend/resume

[Jonas D.]

A workaround that worked for me was `pulseaudio -k`; having to do this
almost every time I need audio is a big PITA though.

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

Title:
  No HDMI sound after suspend/resume

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works
  perfectly, but when I suspend computer and resume it there is no sound
  via HDMI in TV. However sound via built in speakers works fine. The
  only thing I can do to restore sound is to reboot the machine. Similar
  problem was discussed in following thread
  https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I
  tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no
  solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1718927/+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 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"

[Alex A. D.]

@Kai Kasurinen 
>probably fixed on shared-mime-info 2.0:
>https://gitlab.freedesktop.org/xdg/shared-mime-info/-/commit/18bb7cfc6c43d710ecf60339b5dd9bd19c297cdf
Yeah, well. It's if they only used the same database.

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

Title:
  misidentifies .html file as Perl script when it contains JavaScript
  "use strict"

Status in shared-mime-info:
  Unknown
Status in kde-cli-tools package in Ubuntu:
  New
Status in shared-mime-info package in Ubuntu:
  Fix Committed
Status in shared-mime-info package in Debian:
  Confirmed

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+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 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"

[Alex A. D.]

If you wrap string in the proper tags you will get the same result, but
with different offset (28 chars):

tee "index.html" <
`printf "x"%.0s {1..228}`
use strict

eol # -> text/html

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

Title:
  misidentifies .html file as Perl script when it contains JavaScript
  "use strict"

Status in shared-mime-info:
  Unknown
Status in kde-cli-tools package in Ubuntu:
  New
Status in shared-mime-info package in Ubuntu:
  Fix Committed
Status in shared-mime-info package in Debian:
  Confirmed

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+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 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"

[Alex A. D.]

#ＩＮＴＲＯ
After digging up for a while I've found where the issue comes from for both 
`.html` and `.py` (bug #1857824) files.

#ＳＨＯＲＴ
The culprit responsible for misidentification resides in `.xml` database which 
specifies how to match mime-type against input data. It can be found here [2].

#ＬＯＮＧ
The `kmimetypefinder.cpp` pulls up [0] `QMimeDatabase db` apis by 
`db.mimeTypeForFile(...)` which in turns bootstrup `QMimeDatabasePrivate ...` 
XML database from .xml file.[1] 

If we look carefully at the content of the `"text/x-perl"` entry we
would see the following:

```


  ...
   
  ...

```

Did you notice the offset attribute `"0:256"`? Now if we run the
following two cases we will see that files whose content contains
keywords `use strict` in the range of 1..256 will be identified as
`text/x-perl` script and as `text/html` if the `use trict` is located
outside of such range otherwise, checkout:

 tee "index.html"  index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+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 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"

[Alex A. D.]

With the same setup I have the `mimetype` to output `text/html` for
`index.html`. It seems it workds correctly.

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

Title:
  misidentifies .html file as Perl script when it contains JavaScript
  "use strict"

Status in shared-mime-info:
  Unknown
Status in kde-cli-tools package in Ubuntu:
  New
Status in shared-mime-info package in Ubuntu:
  Fix Committed
Status in shared-mime-info package in Debian:
  Confirmed

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+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 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"

[Alex A. D.]

** Also affects: kde-cli-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  misidentifies .html file as Perl script when it contains JavaScript
  "use strict"

Status in shared-mime-info:
  Unknown
Status in kde-cli-tools package in Ubuntu:
  New
Status in shared-mime-info package in Ubuntu:
  New
Status in shared-mime-info package in Debian:
  Unknown

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+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 1890716] Re: kmimetypefinder5 *.html reports wrong type

[Alex A. D.]

I've reported a new bug providing a complete and correct description:
https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1896682

This one can be safely closed.

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

Title:
  kmimetypefinder5 *.html reports wrong type

Status in shared-mime-info package in Ubuntu:
  Invalid

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+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 1890716] Re: kmimetypefinder5 *.html reports wrong type

[Alex A. D.]

New bug reopened with complete and correct explanation: 
https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1896682

** Changed in: shared-mime-info (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  kmimetypefinder5 *.html reports wrong type

Status in shared-mime-info package in Ubuntu:
  Invalid

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+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 1890716] Re: xdg-mime query filetype index.html reports wrong type

[Alex A. D.]

After running that commands I got the following output:

$ ...
Running kmimetypefinder5 "/home/alex/Desktop/index.html"
application/x-perl


It seems like that kmimetypefinder5 is major culprit here. I've found another 
unrelated bugreport here which was reported about a year ago: 
https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1857824

In that case the program reports wrong type for *.py files with correct 
content. Weird!
I think it's wortht to rename this bugreport.

** Summary changed:

- xdg-mime query filetype index.html reports wrong type
+ kmimetypefinder5 *.html reports wrong type

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

Title:
  kmimetypefinder5 *.html reports wrong type

Status in shared-mime-info package in Ubuntu:
  Incomplete

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+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 1890716] Re: xdg-mime query filetype index.html reports wrong type

[Alex A. D.]

I just have tried a fresh new user. The output is identical. See
attached screenshot.

** Attachment added: "xdg-mime query wrong result"
   
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+attachment/5413048/+files/Screenshot_20200921_232318.png

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

Title:
  xdg-mime query filetype index.html reports wrong type

Status in shared-mime-info package in Ubuntu:
  Incomplete

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+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 1890716] Re: xdg-mime query filetype index.html reports wrong type

[Alex A. D.]

why did you tag the report*

Bump.

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

Title:
  xdg-mime query filetype index.html reports wrong type

Status in shared-mime-info package in Ubuntu:
  Invalid

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+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 1890716] Re: xdg-mime query filetype index.html reports wrong type

[Alex A. D.]

Hi Sebastien. Thaks your for your reply.

I suggest you to do the following to see that even if file is starting
with proper tags it is recognized as `application/x-perl`:

$ tee "index.html" <
use strict
eol

$ xdg-mime query filetype index.html # -> application/x-perl - wrong
type

Why did you tagged report as invalid? 
I just got a file with minified JS code which has `use strict` burrowed deep 
somewhere inside correct html file but it's still recognized as perl script.

I can't use some tools to open the file in browser by using xdg-open and
forced to use browser-specific launcher.

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

Title:
  xdg-mime query filetype index.html reports wrong type

Status in shared-mime-info package in Ubuntu:
  Invalid

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

[Brett D]

Same issue here with Aukey EP-N5 bluetooth earbuds on 20.04.1.  This is
a top-selling set of earbuds on Amazon so I thought they'd work.

The microphone doesn't appear at all in the list of input devices under
system Sound Settings.

Attempting to change the profile within Blueman to HSP/HFP results in
"Failed to change profile to headset_head_unit".

Maddening.

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1576559/+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 1885310] [NEW] Unable to add local printer. cups hanging

[Peter D Knight]

Public bug reported:

Initially added epson c60 stylus but it installed with filter error.
Deleted printer from cups , added new printer.
Added the epson printer , selected the .ppd file that worked in 1904 and 
clicked add printer.
Cups just sits and thinks.
Same happens if I use the applications/System/printers menu.
Thanks
Peter

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups-daemon 2.3.1-9ubuntu1.1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Jun 26 18:16:57 2020
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2020-06-01 (25 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: System manufacturer System Product Name
Papersize: a4
PpdFiles: EPSON-Stylus-C60: Epson Stylus C60 - CUPS+Gutenprint v5.3.1
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcEnviron:
 LANG=en_ZA.UTF-8
 LANGUAGE=en_ZA:en
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=b750d723-abc0-43bf-bfd0-945d09637362 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/16/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0402
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5G41T-M LX3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0402:bd05/16/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug focal

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

Title:
  Unable to add local printer. cups hanging

Status in cups package in Ubuntu:
  New

Bug description:
  Initially added epson c60 stylus but it installed with filter error.
  Deleted printer from cups , added new printer.
  Added the epson printer , selected the .ppd file that worked in 1904 and 
clicked add printer.
  Cups just sits and thinks.
  Same happens if I use the applications/System/printers menu.
  Thanks
  Peter

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups-daemon 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jun 26 18:16:57 2020
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2020-06-01 (25 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: EPSON-Stylus-C60: Epson Stylus C60 - CUPS+Gutenprint v5.3.1
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcEnviron:
   LANG=en_ZA.UTF-8
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=b750d723-abc0-43bf-bfd0-945d09637362 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0402
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5G41T-M LX3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0402:bd05/16/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1878617] Re: Apple pages file type should be added to MIME types

[David D Lowe]

As requested, here is an example of an Apple Pages document, taken from
an online templates website.

** Attachment added: "New Job Resignation Letter.pages"
   
https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1878617/+attachment/5373328/+files/New%20Job%20Resignation%20Letter.pages

** Changed in: mime-support (Ubuntu)
   Status: Incomplete => New

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

Title:
  Apple pages file type should be added to MIME types

Status in mime-support package in Ubuntu:
  New

Bug description:
  LibreOffice can open .pages files (from Apple pages). However, the
  mime type for these files is incorrectly just application/zip:

  $ file --mime-type example.pages
  example.pages: application/zip

  Instead, it should be application/vnd.apple.pages .

  This would allow the user to associate LibreOffice Writer with these
  types of files, and use it to open this file. (LibreOffice Writer can
  open .pages files)

  Apple Keynote files should have this MIME type:
  application/vnd.apple.keynote

  Apple Numbers files should have this MIME type:
  application/vnd.apple.numbers

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mime-support 3.64ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 14:46:40 2020
  InstallationDate: Installed on 2018-11-11 (550 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: mime-support
  UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1878617/+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 1878617] Re: Apple pages file type should be added to MIME types

[David D Lowe]

I created a bug report in shared-mime-info's issues tracker here:
https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/136


** Bug watch added: gitlab.freedesktop.org/xdg/shared-mime-info/-/issues #136
   https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/136

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

Title:
  Apple pages file type should be added to MIME types

Status in mime-support package in Ubuntu:
  New

Bug description:
  LibreOffice can open .pages files (from Apple pages). However, the
  mime type for these files is incorrectly just application/zip:

  $ file --mime-type example.pages
  example.pages: application/zip

  Instead, it should be application/vnd.apple.pages .

  This would allow the user to associate LibreOffice Writer with these
  types of files, and use it to open this file. (LibreOffice Writer can
  open .pages files)

  Apple Keynote files should have this MIME type:
  application/vnd.apple.keynote

  Apple Numbers files should have this MIME type:
  application/vnd.apple.numbers

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mime-support 3.64ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 14:46:40 2020
  InstallationDate: Installed on 2018-11-11 (550 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: mime-support
  UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1878617/+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 1878617] [NEW] Apple pages file type should be added to MIME types

[David D Lowe]

Public bug reported:

LibreOffice can open .pages files (from Apple pages). However, the mime
type for these files is incorrectly just application/zip:

$ file --mime-type example.pages
example.pages: application/zip

Instead, it should be application/vnd.apple.pages .

This would allow the user to associate LibreOffice Writer with these
types of files, and use it to open this file. (LibreOffice Writer can
open .pages files)

Apple Keynote files should have this MIME type:
application/vnd.apple.keynote

Apple Numbers files should have this MIME type:
application/vnd.apple.numbers

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: mime-support 3.64ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu May 14 14:46:40 2020
InstallationDate: Installed on 2018-11-11 (550 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: mime-support
UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago)

** Affects: mime-support (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages

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

Title:
  Apple pages file type should be added to MIME types

Status in mime-support package in Ubuntu:
  New

Bug description:
  LibreOffice can open .pages files (from Apple pages). However, the
  mime type for these files is incorrectly just application/zip:

  $ file --mime-type example.pages
  example.pages: application/zip

  Instead, it should be application/vnd.apple.pages .

  This would allow the user to associate LibreOffice Writer with these
  types of files, and use it to open this file. (LibreOffice Writer can
  open .pages files)

  Apple Keynote files should have this MIME type:
  application/vnd.apple.keynote

  Apple Numbers files should have this MIME type:
  application/vnd.apple.numbers

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mime-support 3.64ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 14:46:40 2020
  InstallationDate: Installed on 2018-11-11 (550 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: mime-support
  UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1878617/+subscriptions

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

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

[Josh D]

This also happens on a Dell XPS 9570. My workaround after reboots, or
other events that disable the headphone audio, is to run this:

sudo alsactl restore

Then things are back to normal for a while.

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

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

Status in gnome-control-center:
  Unknown
Status in PulseAudio:
  New
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  In Progress
Status in gnome-control-center source package in Focal:
  Invalid
Status in pulseaudio source package in Focal:
  In Progress

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

  Steps to reproduce:

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

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+subscriptions

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

[Touch-packages] [Bug 1876632] [NEW] Corrupted fonts in display output when using multiple users

[Tom D.]

Public bug reported:

I recently installed ubuntu 20.04 on my computer, and I am running into
an issue when I do the following:

* Login with a user on desktop
* Select switch user, and login as second user
* Switch user again, and return to original user

At this point, text and icons in the menubar / sidebar are corrupted.
Text and icons in normal windows appear correctly. I have attached a
screenshot of what this looks like.

Screenshots: https://imgur.com/a/3ZFDLMc

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun May  3 18:12:45 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0]
InstallationDate: Installed on 2020-05-03 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/19/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F3
dmi.board.asset.tag: Default string
dmi.board.name: AX370-Gaming-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: se1
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: AX370-Gaming
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Corrupted fonts in display output when using multiple users

Status in xorg package in Ubuntu:
  New

Bug description:
  I recently installed ubuntu 20.04 on my computer, and I am running
  into an issue when I do the following:

  * Login with a user on desktop
  * Select switch user, and login as second user
  * Switch user again, and return to original user

  At this point, text and icons in the menubar / sidebar are corrupted.
  Text and icons in normal windows appear correctly. I have attached a
  screenshot of what this looks like.

  Screenshots: https://imgur.com/a/3ZFDLMc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  

[Touch-packages] [Bug 1871960] Re: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to install/upgrade: pre-dependency problem - not installing libpam-modules:amd64

[David D Lowe]

I also experienced this bug. I was running Ubuntu 18.04, and I upgraded
to Ubuntu 20.20 yesterday by running `update-manager -d` on the command-
line, which launched the GUI. During the upgrade itself, I was shown a
dialog displaying an error relating to pam.

I've attached apt-term.log (for me) to this comment. Here is the
relevant error, I think, I don't know how to find the core dump:

Preparing to unpack .../libpam0g_1.3.1-5ubuntu4_amd64.deb ...
Unpacking libpam0g:amd64 (1.3.1-5ubuntu4) over (1.1.8-3.6ubuntu2.18.04.1) ...
Setting up libpam0g:amd64 (1.3.1-5ubuntu4) ...
Fontconfig warning: "/etc/fonts/conf.avail/53-monospace-lcd-filter.conf", line 
10: Having multiple values in  isn't supported and may not work as 
expected
GLib-GObject-WARNING **: specified class size for type 'PangoCairoFcFont' is 
smaller than the parent type's 'PangoFcFont' class size at 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Glib/Object/Introspection.pm line 67.
GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion 
'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed at 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Glib/Object/Introspection.pm line 67.
GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed at 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Glib/Object/Introspection.pm line 67.
GLib-GObject-CRITICAL **: g_object_new_valist: assertion 'G_TYPE_IS_OBJECT 
(object_type)' failed at 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Glib/Object/Introspection.pm line 67.
dpkg: error processing package libpam0g:amd64 (--configure):
 installed libpam0g:amd64 package post-installation script subprocess was 
killed by signal (Segmentation fault), core dumped
Errors were encountered while processing:
 libpam0g:amd64
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 276143 files and directories currently installed.)
Preparing to unpack .../libpam-modules-bin_1.3.1-5ubuntu4_amd64.deb ...
Unpacking libpam-modules-bin (1.3.1-5ubuntu4) over (1.1.8-3.6ubuntu2.18.04.1) 
...
dpkg: dependency problems prevent configuration of libpam-modules-bin:
 libpam-modules-bin depends on libpam0g (>= 0.99.7.1); however:
  Package libpam0g:amd64 is not configured yet.

dpkg: error processing package libpam-modules-bin (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 libpam-modules-bin
dpkg: regarding .../libpam-modules_1.3.1-5ubuntu4_amd64.deb containing 
libpam-modules:amd64, pre-dependency problem:
 libpam-modules:amd64 pre-depends on libpam0g (>= 1.3.1)
  libpam0g:amd64 latest configured version is 1.1.8-3.6ubuntu2.18.04.1.

dpkg: error processing archive 
/var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4_amd64.deb (--unpack):
 pre-dependency problem - not installing libpam-modules:amd64
Errors were encountered while processing:
 /var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4_amd64.deb
dpkg: error processing package libpam-modules:amd64 (--configure):
 package libpam-modules:amd64 is already installed and configured
Errors were encountered while processing:
 libpam-modules:amd64


** Attachment added: "from flimm's machine"
   
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1871960/+attachment/5356669/+files/apt-term.log

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

Title:
  package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to
  install/upgrade: pre-dependency problem - not installing libpam-
  modules:amd64

Status in pam package in Ubuntu:
  Incomplete

Bug description:
  I was updating ubuntu to the 20.04 version. Not all packages were
  updated. I receive new errors every few seconds. what should I do?

  Thanks
  safi

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libpam-modules 1.1.8-3.6ubuntu2.18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  Date: Fri Apr 10 00:36:08 2020
  ErrorMessage: pre-dependency problem - not installing libpam-modules:amd64
  InstallationDate: Installed on 2019-12-28 (102 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.1ubuntu1
  SourcePackage:

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

[D]

apport information

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

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

Title:
  20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The installation scripts loads the correct drivers so the touch pad
  and pointer works during the install. However after the install
  neither work.

  I've worked around it by using a wireless USB from Vilros for mouse input 
while logging in. Then issuing (found on 
https://askubuntu.com/questions/1143663):
   sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol'

  So it's a bug for me but one I can work around and should be fixed before 
20.04 goes live.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1)
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-14-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] 
(rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b]
  InstallationDate: Installed on 2020-03-21 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  MachineType: LENOVO 20QRCTO1WW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: xorg 1:7.7+19ubuntu14
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Tags:  focal ubuntu reproducible has-workaround
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2NET35W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40104 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P73
  dmi.product.name: 20QRCTO1WW
  dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73
  dmi.product.version: ThinkPad P73
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

[D]

apport information

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

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

Title:
  20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The installation scripts loads the correct drivers so the touch pad
  and pointer works during the install. However after the install
  neither work.

  I've worked around it by using a wireless USB from Vilros for mouse input 
while logging in. Then issuing (found on 
https://askubuntu.com/questions/1143663):
   sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol'

  So it's a bug for me but one I can work around and should be fixed before 
20.04 goes live.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1)
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-14-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] 
(rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b]
  InstallationDate: Installed on 2020-03-21 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  MachineType: LENOVO 20QRCTO1WW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: xorg 1:7.7+19ubuntu14
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Tags:  focal ubuntu reproducible has-workaround
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2NET35W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40104 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P73
  dmi.product.name: 20QRCTO1WW
  dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73
  dmi.product.version: ThinkPad P73
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

[D]

apport information

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

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

Title:
  20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The installation scripts loads the correct drivers so the touch pad
  and pointer works during the install. However after the install
  neither work.

  I've worked around it by using a wireless USB from Vilros for mouse input 
while logging in. Then issuing (found on 
https://askubuntu.com/questions/1143663):
   sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol'

  So it's a bug for me but one I can work around and should be fixed before 
20.04 goes live.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1)
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-14-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] 
(rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b]
  InstallationDate: Installed on 2020-03-21 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  MachineType: LENOVO 20QRCTO1WW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: xorg 1:7.7+19ubuntu14
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Tags:  focal ubuntu reproducible has-workaround
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2NET35W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40104 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P73
  dmi.product.name: 20QRCTO1WW
  dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73
  dmi.product.version: ThinkPad P73
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

[D]

apport information

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

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

Title:
  20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The installation scripts loads the correct drivers so the touch pad
  and pointer works during the install. However after the install
  neither work.

  I've worked around it by using a wireless USB from Vilros for mouse input 
while logging in. Then issuing (found on 
https://askubuntu.com/questions/1143663):
   sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol'

  So it's a bug for me but one I can work around and should be fixed before 
20.04 goes live.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1)
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-14-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] 
(rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b]
  InstallationDate: Installed on 2020-03-21 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  MachineType: LENOVO 20QRCTO1WW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: xorg 1:7.7+19ubuntu14
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Tags:  focal ubuntu reproducible has-workaround
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2NET35W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40104 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P73
  dmi.product.name: 20QRCTO1WW
  dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73
  dmi.product.version: ThinkPad P73
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

[D]

apport information

** Attachment added: "MonitorsUser.xml.txt"
   
https://bugs.launchpad.net/bugs/1868474/+attachment/5341474/+files/MonitorsUser.xml.txt

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

Title:
  20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The installation scripts loads the correct drivers so the touch pad
  and pointer works during the install. However after the install
  neither work.

  I've worked around it by using a wireless USB from Vilros for mouse input 
while logging in. Then issuing (found on 
https://askubuntu.com/questions/1143663):
   sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol'

  So it's a bug for me but one I can work around and should be fixed before 
20.04 goes live.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1)
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-14-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] 
(rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b]
  InstallationDate: Installed on 2020-03-21 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  MachineType: LENOVO 20QRCTO1WW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: xorg 1:7.7+19ubuntu14
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Tags:  focal ubuntu reproducible has-workaround
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2NET35W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40104 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P73
  dmi.product.name: 20QRCTO1WW
  dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73
  dmi.product.version: ThinkPad P73
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

[D]

apport information

** Attachment added: "NvidiaBugReportLog.txt"
   
https://bugs.launchpad.net/bugs/1868474/+attachment/5341475/+files/NvidiaBugReportLog.txt

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

Title:
  20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The installation scripts loads the correct drivers so the touch pad
  and pointer works during the install. However after the install
  neither work.

  I've worked around it by using a wireless USB from Vilros for mouse input 
while logging in. Then issuing (found on 
https://askubuntu.com/questions/1143663):
   sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol'

  So it's a bug for me but one I can work around and should be fixed before 
20.04 goes live.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1)
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-14-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] 
(rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b]
  InstallationDate: Installed on 2020-03-21 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  MachineType: LENOVO 20QRCTO1WW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: xorg 1:7.7+19ubuntu14
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Tags:  focal ubuntu reproducible has-workaround
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2NET35W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40104 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P73
  dmi.product.name: 20QRCTO1WW
  dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73
  dmi.product.version: ThinkPad P73
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

[D]

apport information

** Attachment added: "nvidia-settings.txt"
   
https://bugs.launchpad.net/bugs/1868474/+attachment/5341484/+files/nvidia-settings.txt

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

Title:
  20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The installation scripts loads the correct drivers so the touch pad
  and pointer works during the install. However after the install
  neither work.

  I've worked around it by using a wireless USB from Vilros for mouse input 
while logging in. Then issuing (found on 
https://askubuntu.com/questions/1143663):
   sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol'

  So it's a bug for me but one I can work around and should be fixed before 
20.04 goes live.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1)
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-14-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] 
(rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b]
  InstallationDate: Installed on 2020-03-21 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  MachineType: LENOVO 20QRCTO1WW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: xorg 1:7.7+19ubuntu14
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Tags:  focal ubuntu reproducible has-workaround
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2NET35W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40104 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P73
  dmi.product.name: 20QRCTO1WW
  dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73
  dmi.product.version: ThinkPad P73
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

[D]

apport information

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

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

Title:
  20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The installation scripts loads the correct drivers so the touch pad
  and pointer works during the install. However after the install
  neither work.

  I've worked around it by using a wireless USB from Vilros for mouse input 
while logging in. Then issuing (found on 
https://askubuntu.com/questions/1143663):
   sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol'

  So it's a bug for me but one I can work around and should be fixed before 
20.04 goes live.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1)
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-14-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] 
(rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b]
  InstallationDate: Installed on 2020-03-21 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  MachineType: LENOVO 20QRCTO1WW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: xorg 1:7.7+19ubuntu14
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Tags:  focal ubuntu reproducible has-workaround
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2NET35W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40104 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P73
  dmi.product.name: 20QRCTO1WW
  dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73
  dmi.product.version: ThinkPad P73
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

[D]

apport information

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

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

Title:
  20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The installation scripts loads the correct drivers so the touch pad
  and pointer works during the install. However after the install
  neither work.

  I've worked around it by using a wireless USB from Vilros for mouse input 
while logging in. Then issuing (found on 
https://askubuntu.com/questions/1143663):
   sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol'

  So it's a bug for me but one I can work around and should be fixed before 
20.04 goes live.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1)
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-14-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] 
(rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b]
  InstallationDate: Installed on 2020-03-21 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  MachineType: LENOVO 20QRCTO1WW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: xorg 1:7.7+19ubuntu14
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Tags:  focal ubuntu reproducible has-workaround
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2NET35W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40104 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P73
  dmi.product.name: 20QRCTO1WW
  dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73
  dmi.product.version: ThinkPad P73
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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