[Touch-packages] [Bug 1934644] [NEW] gsettings-desktop-schemas 40 breaks workspace nagivation with gnome-shell 38

[Julian Andres Klode]

Public bug reported:

gsettings-desktop-schemas 40 is supposed to be used with gnome-shell 40,
not 38, and hence has moved the Page_up/Down (and )
shortcuts for moving between workspaces from vertical to horizontal
settings, breaking workspace navigation in gnome-shell 38.

This commit needs to be reverted until gnome-shell 40 lands:

https://salsa.debian.org/gnome-team/gsettings-desktop-
schemas/-/commit/a7b057cde57a6509a91fd80b492460a036a04ade

Once gnome-shell 40 lands, the revert should be reverted and Breaks:
gnome-shell (<< 40) should be added.

** Affects: gsettings-desktop-schemas (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  gsettings-desktop-schemas 40 breaks workspace nagivation with gnome-
  shell 38

Status in gsettings-desktop-schemas package in Ubuntu:
  New

Bug description:
  gsettings-desktop-schemas 40 is supposed to be used with gnome-shell
  40, not 38, and hence has moved the Page_up/Down (and )
  shortcuts for moving between workspaces from vertical to horizontal
  settings, breaking workspace navigation in gnome-shell 38.

  This commit needs to be reverted until gnome-shell 40 lands:

  https://salsa.debian.org/gnome-team/gsettings-desktop-
  schemas/-/commit/a7b057cde57a6509a91fd80b492460a036a04ade

  Once gnome-shell 40 lands, the revert should be reverted and Breaks:
  gnome-shell (<< 40) should be added.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1934644/+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 1934647] [NEW] Nvidia driver black screen at login.

[Anatoli Navahrodski]

Public bug reported:

If I choose nvidia driver, then the screen is black and I cannot log in. To log 
in, I need to delete all nvidia files.
After that, the xorg is selected and I can log in. But I cannot edit 
brightness. I can hardly see anything on the screen. The battery is draining 
very badly.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
Uname: Linux 5.11.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul  5 10:54:41 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus: nvidia, 460.80, 5.11.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb]
 NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] 
[103c:85fb]
InstallationDate: Installed on 2021-06-25 (9 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro recovery nomodeset 
dis_ucode_ldr
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2020
dmi.bios.release: 15.33
dmi.bios.vendor: Insyde
dmi.bios.version: F.33
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 85FB
dmi.board.vendor: HP
dmi.board.version: 42.42
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 42.42
dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx
dmi.product.sku: 2C7M8EA#ACB
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.104-1build1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: amd64 apport-bug hirsute ubuntu

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

Title:
  Nvidia driver black screen at login.

Status in xorg package in Ubuntu:
  New

Bug description:
  If I choose nvidia driver, then the screen is black and I cannot log in. To 
log in, I need to delete all nvidia files.
  After that, the xorg is selected and I can log in. But I cannot edit 
brightness. I can hardly see anything on the screen. The battery is draining 
very badly.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  5 10:54:41 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 460.80, 5.11.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] 
[103c:85fb]
  InstallationDate: Installed on 2021-06-25 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro rec

[Touch-packages] [Bug 1934647] Re: Nvidia driver black screen at login.

[Anatoli Navahrodski]

** Attachment added: "nvidia-bug-report.log.gz"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1934647/+attachment/5509102/+files/nvidia-bug-report.log.gz

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

Title:
  Nvidia driver black screen at login.

Status in xorg package in Ubuntu:
  New

Bug description:
  If I choose nvidia driver, then the screen is black and I cannot log in. To 
log in, I need to delete all nvidia files.
  After that, the xorg is selected and I can log in. But I cannot edit 
brightness. I can hardly see anything on the screen. The battery is draining 
very badly.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  5 10:54:41 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 460.80, 5.11.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] 
[103c:85fb]
  InstallationDate: Installed on 2021-06-25 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro recovery nomodeset 
dis_ucode_ldr
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2020
  dmi.bios.release: 15.33
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 85FB
  dmi.board.vendor: HP
  dmi.board.version: 42.42
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 42.42
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx
  dmi.product.sku: 2C7M8EA#ACB
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1934647/+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 1934505] Re: gdb 11 doesn't work on impish: internal-error: displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, thread_info*, CORE_ADDR&): Assertion `gdbarch_dat

[Matthias Klose]

** Bug watch added: Sourceware.org Bugzilla #28056
   https://sourceware.org/bugzilla/show_bug.cgi?id=28056

** Also affects: gdb via
   https://sourceware.org/bugzilla/show_bug.cgi?id=28056
   Importance: Unknown
   Status: Unknown

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

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

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

Title:
  gdb 11 doesn't work on impish: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Unknown
Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1934505/+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 1934648] [NEW] [Vostro 15-3568, Realtek ALC3246, Speaker, Internal] Underruns, dropouts or crackling sound

[Sayantan Das]

Public bug reported:

Right speaker crackles while left speaker is intact.

Tried many quirks including those posted here -> 
https://ubuntuforums.org/showthread.php?t=2464361
(That OP is me only).

I also tried to position quirk as mentioned in troubleshooting guide --
didn't work.

I am yet to try to use a live boot and see if problem is hardware or
not.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
Uname: Linux 5.4.0-77-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ucalyptus   2157 F pulseaudio
 /dev/snd/pcmC0D0c:   ucalyptus   2157 F...m pulseaudio
 /dev/snd/pcmC0D0p:   ucalyptus   2157 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul  5 13:53:04 2021
InstallationDate: Installed on 2020-03-16 (475 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulseAudioLog:
 Jul 05 13:50:11 ucalyptus dbus-daemon[941]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.34' (uid=121 pid=1409 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
 Jul 05 13:51:09 ucalyptus systemd[1400]: pulseaudio.service: Succeeded.
 Jul 05 13:51:19 ucalyptus systemd[1400]: pulseaudio.socket: Succeeded.
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [Vostro 15-3568, Realtek ALC3246, Speaker, Internal] Underruns, dropouts 
or crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/10/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 3.4.0
dmi.board.name: 05HRPP
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr3.4.0:bd05/10/2019:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: Vostro
dmi.product.name: Vostro 15-3568
dmi.product.sku: 0793
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal

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

Title:
  [Vostro 15-3568, Realtek ALC3246, Speaker, Internal] Underruns,
  dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Right speaker crackles while left speaker is intact.

  Tried many quirks including those posted here -> 
https://ubuntuforums.org/showthread.php?t=2464361
  (That OP is me only).

  I also tried to position quirk as mentioned in troubleshooting guide
  -- didn't work.

  I am yet to try to use a live boot and see if problem is hardware or
  not.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ucalyptus   2157 F pulseaudio
   /dev/snd/pcmC0D0c:   ucalyptus   2157 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ucalyptus   2157 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  5 13:53:04 2021
  InstallationDate: Installed on 2020-03-16 (475 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   Jul 05 13:50:11 ucalyptus dbus-daemon[941]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.34' (uid=121 pid=1409 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
   Jul 05 13:51:09 ucalyptus systemd[1400]: pulseaudio.service: Succeeded.
   Jul 05 13:51:19 ucalyptus systemd[1400]: pulseaudio.socket: Succeeded.
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Vostro 15-3568, Realtek ALC3246, Speaker, Internal] Underruns, 
dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/10/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.4.0
  dmi.board.name: 05HRPP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor:

[Touch-packages] [Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default

[Christian Ehrhardt ]

The new NM tests were fine (even against the old dnsmasq due to the or in the 
regex).
NM hit a few non related systemd test issues - I re-triggered those.
Finally I did now start the new NM tests against the blocked dnsmasq.

Overall that should hopefully resolve both and let them migrate.

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

Title:
  [2.82 regression] router announcements have 'forever' lifetime by
  default

Status in dnsmasq package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  New
Status in dnsmasq source package in Groovy:
  Fix Released
Status in network-manager source package in Groovy:
  Invalid
Status in dnsmasq source package in Hirsute:
  Fix Released
Status in network-manager source package in Hirsute:
  Invalid
Status in dnsmasq source package in Impish:
  Triaged
Status in network-manager source package in Impish:
  New
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  The default lifetime was changed to 1 day in 2.82 in the change
  corresponding to this changelog entry:

  Change default lease time for DHCPv6 to one day.

  Fine, but the same commit also did this:

Alter calculation of preferred and valid times in router
advertisements, so that these do not have a floor applied
of the lease time in the dhcp-range if this is not explicitly
specified and is merely the default.

  And that change is buggy and causes advertisements to have infinite
  lifetime, when you are using the default.

  See this thread

http://lists.thekelleys.org.uk/pipermail/dnsmasq-
  discuss/2020q3/014341.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+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 1932311] Re: migrate to llvm 12

[Timo Aaltonen]

** Changed in: mesa (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  migrate to llvm 12

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

Bug description:
  (split off from bug 1917763)

  [Impact]

  Mesa should migrate to llvm 12 for new AMDGPU features and HW support.
  Normally this would be done during the devel series, but this version
  was delayed too much to migrate before hirsute was out.

  [Fix]
  Build-depend on the new packages, including libclc which is now built from 
llvm sources.

  [Test case]

  Test AMD graphics and/or qemu desktop (llvmpipe) after installing
  migrated packages.

  [Regression potential]

  This has been in Impish for a month now without issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1932311/+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 1925434] Re: New bugfix release 21.0.3

[Timo Aaltonen]

** Changed in: mesa (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  New bugfix release 21.0.3

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Focal:
  Fix Committed
Status in mesa source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  This is the last point-release of the 21.0.x-series, we should put it
  in hirsute so latest bugfixes would get there, and in focal for
  20.04.3 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/1925434/+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 1918855] Re: Xorg xserver got signal 6 to abort

[Timo Aaltonen]

focal update is available too

** Tags added: verification-needed-focal

** Changed in: mesa (Ubuntu Focal)
   Status: New => Fix Committed

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

Title:
  Xorg xserver got signal 6 to abort

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Committed
Status in mesa source package in Hirsute:
  Fix Committed

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may 
crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if 
kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session 
is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory 
pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on 
focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+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 1934648] Re: [Vostro 15-3568, Realtek ALC3246, Speaker, Internal] Underruns, dropouts or crackling sound

[Hui Wang]

Could you please try the bootargs of "snd_hda_intel.codec_mask=0x1"

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

Title:
  [Vostro 15-3568, Realtek ALC3246, Speaker, Internal] Underruns,
  dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Right speaker crackles while left speaker is intact.

  Tried many quirks including those posted here -> 
https://ubuntuforums.org/showthread.php?t=2464361
  (That OP is me only).

  I also tried to position quirk as mentioned in troubleshooting guide
  -- didn't work.

  I am yet to try to use a live boot and see if problem is hardware or
  not.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ucalyptus   2157 F pulseaudio
   /dev/snd/pcmC0D0c:   ucalyptus   2157 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ucalyptus   2157 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  5 13:53:04 2021
  InstallationDate: Installed on 2020-03-16 (475 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   Jul 05 13:50:11 ucalyptus dbus-daemon[941]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.34' (uid=121 pid=1409 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
   Jul 05 13:51:09 ucalyptus systemd[1400]: pulseaudio.service: Succeeded.
   Jul 05 13:51:19 ucalyptus systemd[1400]: pulseaudio.socket: Succeeded.
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Vostro 15-3568, Realtek ALC3246, Speaker, Internal] Underruns, 
dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/10/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.4.0
  dmi.board.name: 05HRPP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.4.0:bd05/10/2019:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 15-3568
  dmi.product.sku: 0793
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1934648/+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 1923880] Re: libdrm 2.4.105: Add support for Intel Jasper Lake, Alder Lake

[Timo Aaltonen]

tested the update on ADL with both focal and hirsute

** Tags removed: verification-needed verification-needed-focal 
verification-needed-hirsute
** Tags added: verification-done verification-done-focal 
verification-done-hirsute

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

Title:
  libdrm 2.4.105: Add support for Intel Jasper Lake, Alder Lake

Status in libdrm package in Ubuntu:
  Fix Released
Status in libdrm source package in Focal:
  Fix Committed
Status in libdrm source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  There is a new minor release available, which adds support for i915
  Jasper Lake (JSL) and Alder Lake S (ADL-S), among other things.

  With this added, JSL can boot hirsute with the native driver.

  [Test case]

  Boot on JSL/ADL hardware, check that the native drm/dri driver is used
  (mesa support is already included).

  [What could go wrong]

  The worst case would be that the native driver would not be used
  anymore with this version, but there's no chance for that.

  Two regressing commits were reverted for impish, and we'll include
  those too.

  --

  git shortlog since 2.4.104:

  6b4e956d299c6ff Bump version to 2.4.105
  1d13cc1032bf66f amdgpu: add function of INFO ioctl for querying video caps
  50c98335c7b4013 amdgpu: sync up amdgpu_drm.h with latest from kernel
  b362850689d1b00 xf86drmMode: set FB_MODIFIERS flag when modifiers are supplied
  a5a400c9581c3b9 tests/amdgpu: fix bo eviction test issue
  af871ec1a6f017b drm/tests/amdgpu: fix Metadata test failed issue
  6d821612d9a4bc4 xf86drmMode: introduce drmModeGetPropertyType
  f5abbc303361980 test/amdgpu: remove static varible in Syncobj test
  cd3681976c3bbef intel: Keep libdrm working without pread/pwrite ioctls
  52f05d3d896480e meson: use library() instead of shared_library().
  7d6a1759900ffde xf86drm: fix null pointer deref in drmGetBufInfo
  2e67fef5f6c5870 intel: Add support for JSL
  a9bb32cfe1ee87f xf86drm: cap number of reported devices by drmGetDevice(2)
  06844b6eaefb03c Revert "xf86drm: cap number of reported devices by 
drmGetDevice(2)"
  632f59fcbfc790a xf86drm: warn about GEM handle reference counting
  523b3658aa8efa7 xf86drmMode: add drmIsKMS
  1225171bd55f65d amdgpu_drm: sync up with the latest amdgpu_drm.h based on 
drm-next (https://cgit.freedesktop.org/drm/drm)
  3b6cfb20fb3b7dd intel: add INTEL_ADLS_IDS to the pciids list
  9086ff9dafa87f9 intel: sync i915_pciids.h with kernel
  869ef0e4b22b8ba amdgpu: update marketing names
  a43cac24db2876b Avoid some compiler errors for 
tests/util/pattern.c62b9a3eee9bdaaf
  8cb12a2528d795c xf86drm: cap number of reported devices by drmGetDevice(2)
  19f0a9cb878da5b tests/amdgpu/vcn: clean abundant codes
  2315bcddd643b4b tests/amdgpu: add vcn test support for dimgrey_cavefish
  10377d661a31c7a tests/amdgpu: add vcn test support for navy_flounder
  5f85a6d98baba1d tests/util: Add mxsfb-drm driver
  62b9a3eee9bdaaf meson: Also search for rst2man.py
  10dd3eb6d5ab6c1 Use dep_rt in amdgpu/meson.build

  diffstat:
   amdgpu/amdgpu-symbols.txt|1
   amdgpu/amdgpu.h  |   17 +++
   amdgpu/amdgpu_gpu_info.c |   15 ++
   amdgpu/meson.build   |4 -
   core-symbols.txt |1
   data/amdgpu.ids  |6 ++
   etnaviv/meson.build  |2
   exynos/meson.build   |2
   freedreno/meson.build|2
   include/drm/amdgpu_drm.h |   51 +++---
   intel/i915_pciids.h  |  177 
+++--
   intel/intel_bufmgr_gem.c |   96 -
   intel/intel_chipset.c|2
   intel/meson.build|2
   libkms/meson.build   |2
   meson.build  |6 +-
   nouveau/meson.build  |2
   omap/meson.build |2
   radeon/meson.build   |2
   tegra/meson.build|2
   tests/amdgpu/amdgpu_test.c   |6 --
   tests/amdgpu/basic_tests.c   |   13 +++--
   tests/amdgpu/bo_tests.c  |4 -
   tests/amdgpu/syncobj_tests.c |2
   tests/amdgpu/vcn_tests.c |6 +-
   tests/util/kms.c |1
   tests/util/pattern.c |5 --
   xf86drm.c|   11 
   xf86drm.h|   18 +++
   xf86drmMode.c|   14 +-
   xf86drmMode.h|   12 +
   31 files changed, 365 insertions(+), 121 deletions(-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1923880/+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 1934505] Re: gdb 11 doesn't work on impish: internal-error: displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, thread_info*, CORE_ADDR&): Assertion `gdbarch_dat

[Bug Watch Updater]

Launchpad has imported 1 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=28056.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2021-07-05T08:27:01+00:00 Matthias Klose wrote:

seen with the trunk 20210630, and the gdb-12 branch 20210705 on s390x-
linux-gnu:

$ gdb /bin/ls
GNU gdb (Ubuntu 11.0.90.20210705-0ubuntu1) 11.0.90.20210705-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "s390x-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /bin/ls...
(No debugging symbols found in /bin/ls)
(gdb) run
Starting program: /usr/bin/ls 
/home/ubuntu/tmp/gdb-11.0.90.20210705/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) n
Command aborted.
(gdb)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1934505/comments/1


** Changed in: gdb
   Status: Unknown => Confirmed

** Changed in: gdb
   Importance: Unknown => Medium

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

Title:
  gdb 11 doesn't work on impish: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  <https://www.gnu.org/software/gdb/bugs/>.
  Find the GDB manual and other documentation resources online at:
  <http://www.gnu.org/software/gdb/documentation/>.

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  <https://www.gnu.org/software/gdb/bugs/>.

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1934505/+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 1934505] Re: gdb 11 doesn't work on impish/s390x: internal-error: displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, thread_info*, CORE_ADDR&): Assertion `gdbar

[Iain Lane]

** Summary changed:

- gdb 11 doesn't work on impish: internal-error: displaced_step_prepare_status 
linux_displaced_step_prepare(gdbarch*, thread_info*, CORE_ADDR&): Assertion 
`gdbarch_data->num_disp_step_buffers > 0' failed.
+ gdb 11 doesn't work on impish/s390x: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.

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

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1934505/+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 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default

[Christian Ehrhardt ]

dnsmasq tested all fine with the new NM.
Only the odd systemd blocker holds us back now.

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

Title:
  [2.82 regression] router announcements have 'forever' lifetime by
  default

Status in dnsmasq package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  New
Status in dnsmasq source package in Groovy:
  Fix Released
Status in network-manager source package in Groovy:
  Invalid
Status in dnsmasq source package in Hirsute:
  Fix Released
Status in network-manager source package in Hirsute:
  Invalid
Status in dnsmasq source package in Impish:
  Triaged
Status in network-manager source package in Impish:
  New
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  The default lifetime was changed to 1 day in 2.82 in the change
  corresponding to this changelog entry:

  Change default lease time for DHCPv6 to one day.

  Fine, but the same commit also did this:

Alter calculation of preferred and valid times in router
advertisements, so that these do not have a floor applied
of the lease time in the dhcp-range if this is not explicitly
specified and is merely the default.

  And that change is buggy and causes advertisements to have infinite
  lifetime, when you are using the default.

  See this thread

http://lists.thekelleys.org.uk/pipermail/dnsmasq-
  discuss/2020q3/014341.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+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 1930910] Re: Fix micmute hotkeys on HP ProBooks

[Andy Chi]

Hi @ddstreet,
Thanks. May I know when will systemd in -proposed?

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

Title:
  Fix micmute hotkeys on HP ProBooks

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  Micmute hotkey on many HP ProBooks don't work.

  [Fix]
  Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT 
keyboard's scancode to micmute hotkey.

  [Test]
  With the one-liner fix, micmute hotkey works on all the ProBooks I tested.

  [Where problems could occur]
  The hwdb originally only matches a few ProBooks, the fix changes that to 
match all ProBook models. So if there's any ProBook that uses the scancode for 
another purpose, there will be a regression.
  However, the risk is rather slim because HP explicitly states that all 
ProBooks use the same scancode for mic mute hotkey.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1930910/+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 1925320] Re: Backport packages for 20.04.3 HWE stack

[Timo Aaltonen]

did you get it with 21.0.1? it was in proposed for several weeks

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

Title:
  Backport packages for 20.04.3 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-12 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in directx-headers source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in llvm-toolchain-12 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  directx-headers: a new package, nothing can go wrong

  libdrm: adds some new api, no changes to old stuff

  llvm-12: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+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 1925320] Re: Backport packages for 20.04.3 HWE stack

[Timo Aaltonen]

I can't reproduce it with a Pro W5700, which is a NAVI 10 just like RX
5600 XT.

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

Title:
  Backport packages for 20.04.3 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-12 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in directx-headers source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in llvm-toolchain-12 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  directx-headers: a new package, nothing can go wrong

  libdrm: adds some new api, no changes to old stuff

  llvm-12: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+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 1934221] Re: systemd-resolve segfault

[Denys Fedoryshchenko]

As far as i can see - no crashes anymore.

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

Title:
  systemd-resolve segfault

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-resolve keep crashing and it is very annoying as sometimes it
  severely interrupt normal dns resolving.

  Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6
  Typical error in dmesg: 
  systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 
7ffe2fd0b758 error 15

  apport hints me that problem is related to mdns

  #3  0x7f3e903c2f11 in sd_event_dispatch () from /lib/systemd
  /libsystemd-shared-245.so

  It might be (or not) related that some hosts with mdns in my network
  have ipv6 enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119
  Uname: Linux 5.4.0-75-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  1 08:22:51 2021
  InstallationDate: Installed on 2018-12-05 (938 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic 
root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX X399-E GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX399-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+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 1934552] Re: Graphical glitches on Radeon RX 6700 XT

[Timo Aaltonen]

already fixed in 21.0.3 which is in hirsute-proposed, mind giving it a
try?

** Also affects: mesa (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Graphical glitches on Radeon RX 6700 XT

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Hirsute:
  Incomplete

Bug description:
  Ubuntu 21.04, mesa 21.0.1-2 amd64

  Upstream MR:
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9568

  Graphical glitches can be seen occasionally on screen with the RX 6700
  XT graphics card.

  This is fixed upstream with the above merged MR, so please backport
  it...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934552/+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 1877762] Re: 1360x768 Vega graphics display staggered

[Timo Aaltonen]

so this is a kernel bug

impish will soon get 5.13, but you also have the option of installing
oem-5.13 from focal-proposed (apt install linux-oem-20.04c)

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

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

Title:
  1360x768 Vega graphics display staggered

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This was the go-to resolution pre-update. All of the other modes seem
  to work.

  Release 20.04 LTS (Focal Fossa) 64-bit
  Kernel Linux 5.4.0-29-generic x86_64
  MATE 1.24.0
  Processor: AMD Ryzen 3 2200G with Radeon Vega Graphics × 4 
  Graphics: AMD RAVEN (DRM 3.35.0, 5.4.0-29-generic, LLVM 9.0.1)
  lspci output: 38:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8)

  As you can see from the attached image, the display shifts to the
  right every few lines.

  Still working on installing the full amdgpu package (libffs 6
  required, 7 installed so I'm working on the bits).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1877762/+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 1930279] Re: [Ivy Bridge] flashing sliced triangles on screen

[Timo Aaltonen]

groovy is soon EOL, please upgrade to 21.04 and let us know if this is
fixed there

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

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

Title:
  [Ivy Bridge] flashing sliced triangles on screen

Status in linux package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  when i did upgrade my ubuntu from 20.04 to 20.10 i have small winking
  triangles on my screen, they sometimes will appear when i watching a
  youtube video they will appear on the video's seek bar or when i
  typing they will appear on selected texts,but the main and most
  annoying state of it happens when I am playing minecraft,my entire
  game screen has these little triangles

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 31 18:05:33 2021
  DistUpgraded: 2021-05-27 14:18:07,483 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [1043:844d]
  InstallationDate: Installed on 2020-01-10 (507 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic 
root=UUID=a5a5279f-cdf5-4129-94fa-8f17f7401833 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2021-05-27 (4 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1204
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX R2.0
  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.:bvr1204:bd03/19/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/linux/+bug/1930279/+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 1684755] Re: Missing dependency to libtxc-dxtn-s2tc:amd64

[Timo Aaltonen]

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

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

Title:
  Missing dependency to libtxc-dxtn-s2tc:amd64

Status in mesa package in Ubuntu:
  Invalid
Status in steam package in Ubuntu:
  Invalid

Bug description:
  Steam is missing a dependency to libtxc-dxtn-s2tc:amd64

  How to reproduce:
  - Install steam from the Ubuntu repositories
  - Use the mesa drivers
  - Download a game that requires GL_EXT_TEXTURE_COMPRESSION_S3TC (e.g. Dota 2)
  - Steam throws an error on game start

  Workaround:
  - Install libtxc-dxtn-s2tc:amd64

  https://github.com/ValveSoftware/Dota-2/issues/1213

  Release: Ubuntu 17.04
  Package: steam:i386 (1:1.0.0.54+repack-2ubuntu5)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1684755/+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 1835660] Re: initramfs unpacking failed

[Dimitri John Ledkov]

@superm1 yes I have, it is now pulled into v5.14
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2c484419efc09e7234c667aa72698cb79ba8d8ed

I will request it to be included in linux-stable series.

Note that in Impish we have now switched to zstd compression for the
initramfs, as it has even better bootspeed performance.

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

Title:
  initramfs unpacking failed

Status in OEM Priority Project:
  New
Status in grub2 package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in grub2 source package in Focal:
  Invalid
Status in initramfs-tools source package in Focal:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in grub2 source package in Groovy:
  Invalid
Status in initramfs-tools source package in Groovy:
  Invalid
Status in linux source package in Groovy:
  Fix Released
Status in grub2 source package in Hirsute:
  Invalid
Status in initramfs-tools source package in Hirsute:
  Invalid
Status in linux source package in Hirsute:
  Fix Released

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

  ---

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

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

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

  [Impact]

   * Decoding failure messages in dmsg with a single lz4 initrd

   * Multiple lz4 compressed initrds cannot be decompressed by kernel,
  when loaded by grub

   * Multiple lz4 compressed initrds cannot be decompressed by kernel,
  when there is padding between them

  [Test Case]

   * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4

   * Create an lz4 compressed initrd with a single test-file in it with
  some content. I.e. echo "second-initrd" > test-file, and then pack
  that with cpio hewc owned by root & lz4 -l.

   * Create a combined padded initrd of stock initrd, pad4, and the
  test-marker initrd created above.

   * Boot above with "break=top" kernel command line.

   * With broken kernels, there should be dmesg error message that
  decoding failed, and one will observe that /test-file does not exist
  in the shell.

   * With fixed kernel, /test-file in the initrd shell should exist, and
  should have the expected content "second-initrd".

   * The alignment and padding in the above test case depends on the
  size of the first initrd => if a given padded initrd does not
  reproduce the problem, try varying the size of the first initrd or
  that of the padding between 0..4.

  
  [Where problems could occur]

   * This changes compatible lz4 decompressor in the kernel, which can
  also be used by other kernel modules such as cryptography, squashfs,
  zram, f2fs, comprssed kernel image, pstore. For example, previously
  rejected files with "bogus" length and extra padding may now be
  accepted, whereas they were previously getting rejected by the
  decompressor.

   * Ideally kernel should switch to the stable lz4 format which has
  better specification of end of stream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions

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

[Touch-packages] [Bug 1682913] Re: [radeon] corrupt gfx with Faeria/Payday 2

[Timo Aaltonen]

works fine here now

** Changed in: mesa (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  [radeon] corrupt gfx with Faeria/Payday 2

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  I've just upgraded Ubuntu from 16.10 to 17.04. Afterwards, I noticed 
graphical issues in some games, that render partially black. E.g.:
  - menu of Payday 2: 
https://steamuserimages-a.akamaihd.net/ugc/156906385546364727/C1182DAE4DA1A6CB638A2D42FA33541629F2/
  - menu of Faeria: 
https://steamuserimages-a.akamaihd.net/ugc/156906385546272628/52E8E6F366A54299597774C22D78771EA0F074ED/

  I've traced the issue to a missing lib, libgles1, which for some
  reason has been removed from the 17.04 repos, as using Oibaf's PPA and
  manually installing the lib from it fixes the issues on these games.

  So, please build a version for Mesa 17.0.3 and put it in the repos,
  it's needed by some games.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1682913/+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 1931765] Re: VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston)

[Timo Aaltonen]

vainfo works just fine  ​with gnome-shell/wayland

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

** Changed in: libva (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston)

Status in libva package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid

Bug description:
  SUMMARY

  VAAPI is broken on KDE Plasma Wayland and Weston Session

  STEPS TO REPRODUCE
  1. Open a terminal
  2. Type in vainfo

  
  OBSERVED RESULT

  Error Message:
  heiko@Tuxedobook:~$ vainfo
  wl_drm@6: error 0: authenticate failed
  VA error: wayland: Wayland roundtrip error: Protocol error (errno 71)
  libva info: VA-API version 1.10.0
  libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, 
driver_name = (null)
  vaInitialize failed with error code 3 (invalid VADisplay),exit


  EXPECTED RESULT
  Should show VAAPI information without errors like on X11 session

  This bug was reproduced multiple times on two systems one with an
  intel igpu and one with a dedicated AMD GPU. Both systems are using
  the MESA drivers from this ppa:

  https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa

  This bug was discovered because KODI Mediacenter was crashing on
  startup on wayland while it is working flawless on X11/X.org.

  SOFTWARE/OS VERSIONS
  Linux/KDE Plasma: Kubuntu 21.04 
  (available in About System)
  KDE Plasma Version: 5.22.0 

  
  ADDITIONAL INFORMATION

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1931765/+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 1688200] Re: libgles2-mesa-dev breaks gstreamer-imx video acceleration (14.04 armhf)

[Timo Aaltonen]

that doesn't sound right, a -dev package can't break it, sounds like you
were missing some updates or getting a mixed set of them

anyway, it's been four years, probably not an issue anymore if it ever
was

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

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

Title:
  libgles2-mesa-dev breaks gstreamer-imx video acceleration (14.04
  armhf)

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Installing libgles2-mesa-dev 10.1.3-0ubuntu0.6 armhf together with
  libxcb-randr0 breaks accelerated video playback with gstreamer-imx on
  UDOObuntu 2.1.2 (based on Ubuntu 14.04 LTS - see
  http://www.udoo.org/downloads/).

  This could be broken installation scripts or missing Pre-Depends.

  For example, video playback works fine on udoobuntu-udoo-qdl-desktop_2.1.img:
  # VIDEO + SOUND OK - without libgles2-mesa-dev installed
  gst-launch-1.0 playbin 
uri=file:///home/udooer/big_buck_bunny_720p_h264.mp4
  gst123 big_buck_bunny_720p_h264.mp4

  Introduce breakage by installing libgles2-mesa-dev *without* having 
libxcb-randr0 installed:
  sudo apt-get -y --purge remove libxcb-randr0 && sudo apt-get -y install 
libgles2-mesa-dev
  gst-launch-1.0 playbin 
uri=file:///home/udooer/big_buck_bunny_720p_h264.mp4 # BLACK & PAUSED
  gst123 big_buck_bunny_720p_h264.mp4 # SOUND ONLY + BLACK WINDOW

  Note that just uninstalling libgles2-mesa-dev does *NOT* fix the
  issue, only uninstalling libxcb-randr0 and reinstalling it before or
  without libgles2-mesa-dev brings video playback back to live.

  Workaround1, complete libxcb-randr0 installation before installing 
libgles2-mesa-dev:
  sudo apt-get -y --purge remove libxcb-randr0 && sudo apt-get -y install 
libxcb-randr0 && sudo apt-get -y install libgles2-mesa-dev
  # VIDEO + SOUND OK for gst-launch-1.0 and gst123

  Workaround2, install all dependencies before libgles2-mesa-dev:
  sudo apt-get -y --purge remove libxcb-randr0 && sudo apt-get -y install 
libegl1-mesa-dev && sudo apt-get -y install libgles2-mesa-dev
  # VIDEO + SOUND OK for gst-launch-1.0 and gst123

  So it looks like the libgles2-mesa-dev installation process if run
  before libxcb-randr0 has finished installation (libc triggers run,
  etc), messes up some configuration bits of libxcb-randr0 which stick
  around even after libgles2-mesa-dev is uninstalled.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgles2-mesa-dev 10.1.3-0ubuntu0.6
  Uname: Linux 3.14.56-udooqdl-02044-gddaad11 armv7l
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: armhf
  Date: Thu May  4 09:51:33 2017
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1688200/+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 1905285] Re: socket-activated sshd breaks on concurrent connections

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/openssh/+git/openssh/+merge/405183

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

Title:
  socket-activated sshd breaks on concurrent connections

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  This is mostly the same issue as https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=934663.

  With the default configuration of openssh-server and systemd, sshd
  will complain and crash when multiple connections are made and
  terminated in a quick succession, e.g. with `ssh-keyscan`. It results
  in the following errors in /var/log/auth.log:

  ```
  Nov 22 20:53:34 {host} sshd[14567]: Unable to negotiate with {client} port 
41460: no matching host key type found. Their offer: 
sk-ecdsa-sha2-nistp...@openssh.com [preauth]
  Nov 22 20:53:34 {host} sshd[14570]: fatal: chroot("/run/sshd"): No such file 
or directory [preauth]
  Nov 22 20:53:34 {host} sshd[14569]: fatal: chroot("/run/sshd"): No such file 
or directory [preauth]
  Nov 22 20:53:34 {host} sshd[14568]: fatal: chroot("/run/sshd"): No such file 
or directory [preauth]
  Nov 22 20:53:34 {host} sshd[14566]: fatal: chroot("/run/sshd"): No such file 
or directory [preauth]
  Nov 22 20:53:47 {host} sshd[14584]: Connection closed by {client} port 59312 
[preauth]
  Nov 22 20:53:47 {host} sshd[14586]: fatal: chroot("/run/sshd"): No such file 
or directory [preauth]
  Nov 22 20:53:48 {host} sshd[14585]: fatal: chroot("/run/sshd"): No such file 
or directory [preauth]
  ```

  as well as e.g. missing responses in ssh-keyscan:

  ```
  $ ssh-keyscan -vvv {host}
  debug2: fd 3 setting O_NONBLOCK
  debug3: conalloc: oname {host} kt 2
  debug2: fd 4 setting O_NONBLOCK
  debug3: conalloc: oname {host} kt 4
  debug2: fd 5 setting O_NONBLOCK
  debug3: conalloc: oname {host} kt 8
  debug2: fd 6 setting O_NONBLOCK
  debug3: conalloc: oname {host} kt 32
  debug2: fd 7 setting O_NONBLOCK
  debug3: conalloc: oname {host} kt 64
  debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.1 pat OpenSSH* compat 0x0400
  # {host}:22 SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.1
  debug3: send packet: type 20
  debug1: SSH2_MSG_KEXINIT sent
  debug3: receive packet: type 20
  debug1: SSH2_MSG_KEXINIT received
  debug2: local client KEXINIT proposal
  debug2: KEX algorithms: 
curve25519-sha256,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256
  debug2: host key algorithms: sk-ecdsa-sha2-nistp...@openssh.com
  debug2: ciphers ctos: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com
  debug2: ciphers stoc: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com
  debug2: MACs ctos: 
umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
  debug2: MACs stoc: 
umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
  debug2: compression ctos: none,z...@openssh.com
  debug2: compression stoc: none,z...@openssh.com
  debug2: languages ctos:
  debug2: languages stoc:
  debug2: first_kex_follows 0
  debug2: reserved 0
  debug2: peer server KEXINIT proposal
  debug2: KEX algorithms: 
curve25519-sha256,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1
  debug2: host key algorithms: 
rsa-sha2-512,rsa-sha2-256,ssh-rsa,ecdsa-sha2-nistp256,ssh-ed25519
  debug2: ciphers ctos: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com
  debug2: ciphers stoc: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com
  debug2: MACs ctos: 
umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
  debug2: MACs stoc: 
umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
  debug2: compression ctos: none,z...@openssh.com
  debug2: compression stoc: none,z...@openssh.com
  debug2: languages ctos:
  de

[Touch-packages] [Bug 1835459] Re: libgl1-mesa-glx errors

[Timo Aaltonen]

that's just chrome complaining that it can't use hw acceleration (which
is expected for a remote connection)

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

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

Title:
  libgl1-mesa-glx errors

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  I have a VPS with Ubuntu 18.04 (implementation of pure software,
  Digital Ocean) and I connect through Windows 10 with an X server,
  Xming and I run Google-Chrome Remote. It works well and opens the
  Chrome remote control on my Windows, although it is quite slow, but it
  works. However, it throws some GPU and OpenGL errors that I can not
  solve. I have reported and are quite frequent errors, as recommended,
  I reinstalled the mesa-utils and libgl1-glx-mesa packages, and errors
  persist. Attached capture of these.

  I have installed (bionic):
  libgl1
  libgl1-mesa-dri
  libgl1-mesa-glx
  libglapi-mesa
  libglib2.0-0
  libglib2.0-data
  libglvnd0
  liglx-mesa0
  libglx0

  dbus
  dbus-x11

  I have searched for help in the stackoverflow forums without any
  success.

  OpenGL Propierties:
  ~$ glxinfo | grep "OpenGL versión"

  libGL error: No matching fbConfigs or visuals found
  libGL error: failed to load driver: swrast
  X Error of failed request: GLXBadContext
Major opcode of failed request: 148 (GLX)
Minor opcode of failed request: 6 (X_GLXIsDirect)
Serial number of failed request: 46
Current serial number in output stream: 45

  And the characteristics of the graphics of my VPS:

  ~ $ lspci -vk

  00: 02.0 VGA compatible controller: Red Hat, Inc. QXL paravirtual graphic 
card (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Red Hat, Inc. QEMU Virtual Machine
   Physical Slot: 2
   Flags: fast devsel, IRQ 10
   Memory at f800 (32-bit, non-prefetchable) [size = 64M]
   Memory at fc00 (32-bit, non-prefetchable) [size = 16M]
   Memory at fd05 (32-bit, non-prefetchable) [size = 8K]
   I / O ports at c0a0 [size = 32]
   Expansion ROM at 000c [disabled] [size = 128K]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1835459/+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 1878670] Re: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2)

[Timo Aaltonen]

** Changed in: linux-oem-osp1 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: linux (Ubuntu)
   Status: Triaged => Invalid

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

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

Title:
  Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8
  GT2)

Status in OEM Priority Project:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid

Bug description:
  The system freezes frequently then logs out.
  If happens at apparently random times, and using no particular app.

  Extract of syslog is attached.

  Requested info is below:

  1) release
  Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30)

  2) package version
  gnome-session:
Installeret: (ingen)
Kandidat:3.28.1-0ubuntu3
Versionstabel:
   3.28.1-0ubuntu3 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
   3.28.1-0ubuntu2 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) Gnome shouldn't crash

  4) Gnome crashed

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1878670/+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 1931765] Re: VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston)

[Heiko Gimbel]

Yes it works with the MESA packages from the ubunturepos. The problem
occurs after adding the kisak mesa fresh ppa and upgrading to the latest
stable MESA release. It only happens when Wayland is used. I always use
this otherwise great ppa to keep my MESA drivers up to date. Sadly the
packages in the ubuntu are often to old if you use your system for
gaming.

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

Title:
  VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston)

Status in libva package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid

Bug description:
  SUMMARY

  VAAPI is broken on KDE Plasma Wayland and Weston Session

  STEPS TO REPRODUCE
  1. Open a terminal
  2. Type in vainfo

  
  OBSERVED RESULT

  Error Message:
  heiko@Tuxedobook:~$ vainfo
  wl_drm@6: error 0: authenticate failed
  VA error: wayland: Wayland roundtrip error: Protocol error (errno 71)
  libva info: VA-API version 1.10.0
  libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, 
driver_name = (null)
  vaInitialize failed with error code 3 (invalid VADisplay),exit


  EXPECTED RESULT
  Should show VAAPI information without errors like on X11 session

  This bug was reproduced multiple times on two systems one with an
  intel igpu and one with a dedicated AMD GPU. Both systems are using
  the MESA drivers from this ppa:

  https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa

  This bug was discovered because KODI Mediacenter was crashing on
  startup on wayland while it is working flawless on X11/X.org.

  SOFTWARE/OS VERSIONS
  Linux/KDE Plasma: Kubuntu 21.04 
  (available in About System)
  KDE Plasma Version: 5.22.0 

  
  ADDITIONAL INFORMATION

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1931765/+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 1867581] Re: Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

[Timo Aaltonen]

does it happen with current updates?

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

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

Title:
  Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  ubuntu-bug mesa does not work, i don't see a package named mesa

  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.

  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
direct render: Yes
  corrado@corrado-x5-ff-0309:~$

  I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
  so now I'm opening this problem
  if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  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
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2020-03-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Tags:  focal ubuntu single-occurrence reproducible
  Uname: Linux 5.4.0-14-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: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  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 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/mesa/+bug/1867581/+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 1865536] Re: OBS consumes all memory, fixed in upstream Mesa

[Timo Aaltonen]

fixed in 20.04 and up

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  OBS consumes all memory, fixed in upstream Mesa

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  There is an issue where due to a Mesa bug OBS consumes all memory
  eventually. See https://gitlab.freedesktop.org/mesa/mesa/issues/1426.
  Unfortunately, this issue is in all recent Ubuntu versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1865536/+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 1923845] Re: Please compress packages with zstd by default

[Dimitri John Ledkov]

See reprepro verification comments at
https://bugs.launchpad.net/ubuntu/+source/reprepro/+bug/1933363

** Tags removed: verification-needed verification-needed-focal 
verification-needed-groovy verification-needed-hirsute
** Tags added: verification-done verification-done-focal 
verification-done-groovy verification-done-hirsute

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

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  New
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Committed
Status in dpkg package in Ubuntu:
  New
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  New
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  New
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Committed
Status in reprepro source package in Groovy:
  Fix Committed
Status in reprepro source package in Hirsute:
  Fix Committed
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
  https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archive.ml

  acr - skip, does not _have to_ be fixed, just creates packages, 
see dist/deb_hand.mak
  alien   - skip, uses dpkg-deb to extract .deb
  ansible - not affected, just test data in dbdata.tar.xz
  anthy   - not affected, just changelog entry
  apt - seems fixed already
  ceph- not affected in Ubuntu's version
  circlator  

[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default

[Dimitri John Ledkov]

@ubuntu-sru-bot

regressions triggered by reprepro have been retried, and have been now
cleared.

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

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  New
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Committed
Status in dpkg package in Ubuntu:
  New
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  New
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  New
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Committed
Status in reprepro source package in Groovy:
  Fix Committed
Status in reprepro source package in Hirsute:
  Fix Committed
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
  https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archive.ml

  acr - skip, does not _have to_ be fixed, just creates packages, 
see dist/deb_hand.mak
  alien   - skip, uses dpkg-deb to extract .deb
  ansible - not affected, just test data in dbdata.tar.xz
  anthy   - not affected, just changelog entry
  apt - seems fixed already
  ceph- not affected in Ubuntu's version
  circlator   - not affected, just test data
  cowdancer   - not affected, just documentation
  eccodes - skip, just orig-data.tar.xz
  eckit   - skip, just ...orig-data.tar.xz
  firefox - skip, profdata.tar.xz
  firefo

[Touch-packages] [Bug 1863763] Re: gnome-shell/Wayland on vmware/vmwgfx misrenders with large windows

[Timo Aaltonen]

20.0.4 from ubuntu 20.04 was backported to 18.04 roughly a year ago

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

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

Title:
  gnome-shell/Wayland on vmware/vmwgfx misrenders with large windows

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  There is a bug in mesa version 19.2.x where x>2, manifesting itself as
  window contents in large windows on 4K display renders with an
  incorrect vertical offset, making the desktop largely unusable for
  some customers.

  The bug is fixed in latest 19.3 series and 20.0 rc series, but since
  Ubuntu 18.04.1 still uses 19.2 series, a manual backport is needed.

  Please cherry-pick mesa master commit
  451cf228d53ba8f51beb3dcf04370e126fb7ccb6 ("svga: Fix banded DMA
  upload") to fix the issue, alternatively switch to mesa 19.3 series.

  Thanks,

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
  Uname: Linux 5.5.0+ x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 18 05:53:02 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2020-02-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: VMware, Inc. VMware Virtual Platform
  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.5.0+ 
root=UUID=3fa8a33e-bea4-42a8-9e5b-6a0b922e77d9 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd10/30/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1863763/+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 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.30.0-1ubuntu4

---
network-manager (1.30.0-1ubuntu4) impish; urgency=medium

  * d/t/nm.py: adapt to changes dnsmasq behavior (LP: #1894619)

 -- Christian Ehrhardt   Fri, 02 Jul
2021 11:13:46 +0200

** Changed in: network-manager (Ubuntu Impish)
   Status: New => Fix Released

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

Title:
  [2.82 regression] router announcements have 'forever' lifetime by
  default

Status in dnsmasq package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Groovy:
  Fix Released
Status in network-manager source package in Groovy:
  Invalid
Status in dnsmasq source package in Hirsute:
  Fix Released
Status in network-manager source package in Hirsute:
  Invalid
Status in dnsmasq source package in Impish:
  Triaged
Status in network-manager source package in Impish:
  Fix Released
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  The default lifetime was changed to 1 day in 2.82 in the change
  corresponding to this changelog entry:

  Change default lease time for DHCPv6 to one day.

  Fine, but the same commit also did this:

Alter calculation of preferred and valid times in router
advertisements, so that these do not have a floor applied
of the lease time in the dhcp-range if this is not explicitly
specified and is merely the default.

  And that change is buggy and causes advertisements to have infinite
  lifetime, when you are using the default.

  See this thread

http://lists.thekelleys.org.uk/pipermail/dnsmasq-
  discuss/2020q3/014341.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+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 462419] Re: evince apparmor profile prevents movies from opening

[Rolando Garza]

Hello everyone.

I've read the whole thread and I am experiencing a related bug.

My specific scenario is that I'm creating a PDF (by exporting from Emacs
/ Org-Mode) that contains a link to a local video.  It may have been a
recent change in an AppArmor that has resulted in the videos not opening
anymore (or maybe a security patch?), but I'm not able to open either
mp4 or webm videos like I could with mpv.

I read the /etc/apparmor.d/abstractions/evince file, and added the
following to the /etc/apparmor.d/local/usr.bin.evince file:

# vim:syntax=apparmor
#
# abstraction used by evince binaries
#

  # supported archivers
  /usr/bin/mpv ixr,
  /usr/bin/totem ixr,
  /usr/bin/vlc ixr,

After performing:

rolandog@computer:~$ sudo apparmor_parser --reload
/etc/apparmor.d/usr.bin.evince

I get the following error:

profile /usr/bin/evince: has merged rule /usr/bin/totem with conflicting x 
modifiers
ERROR merging rules for profile /usr/bin/evince, failed to load

Playback with mpv (the player I had set as default) still doesn't work
(is blocked by AppArmor), and, after running the following command, I
get the messages shown in the attached file:

rolandog@computer:~$ grep audit /var/log/kern.log

After removing the totem line I get a similar error, but for vlc.  After
removing both the totem line and the vlc line, I don't get an error (and
I can launch mpv (the default I had set).

However, I'm torn because this worked for me, but there may be others
that may have similar use-cases to mine that would prefer other players.

** Attachment added: "Semi-anonymized matching audit kernel logs from rolandog"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/462419/+attachment/5509133/+files/rolandog-apparmor-kernel-audit.txt

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

Title:
  evince apparmor profile prevents movies from opening

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: evince

  Trying to open a movie with vlc or totem from within evince. I get the
  error: "Failed to execute child process vlc (Permission denied)". The
  same with totem.

  I have been looking at all the "apparmor prevents" bugs that have been
  reported of late. DVI printing, chromium, etc... the package
  maintainers' strategy has been to add an exceptions to the apparmor
  profile as the bugs come in. May I comment that this is a ludicrous
  situation? There are going to be numerous helper applications that
  people might want to use within a PDF file... why is apparmor blocking
  them all?

  [22:47][kirkwood][~] > lsb_release -rd
  Description:Ubuntu 9.10
  Release:9.10
  [22:48][kirkwood][~] > apt-cache policy evince
  evince:
Installed: 2.28.1-0ubuntu1
Candidate: 2.28.1-0ubuntu1
Version table:
   *** 2.28.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com karmic/main Packages
  100 /var/lib/dpkg/status

  Expected to happen: movie opens when clicked on
  What happens instead: help application (totem/vlc) prevented from running by 
apparmor
  Reproducible: 100%

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/462419/+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 462419] Re: evince apparmor profile prevents movies from opening

[Rolando Garza]

By the end of the previous comment I had experienced a weird bug.  But I
decided to post it here as a separate comment because this is still
relevant to this thread.

I resolved the issues by:

1. changing the default player
2. opening a PDF document that contains a link to a local video
3. clicking the link to the video (and failing to open)
4. closing evince and opening the same document again
5. clicking the link to the video again (and succeeding this time)

I had to reproduce those steps for both totem and for vlc, ... but now,
everything just works!

After that initial hurdle, changing default players results in opening
the correct default video player.

I'm not really sure what happened, but the issue just fixed itself.

There are still some odd messages in the kernel log (see attached file).

I don't know if this is reproducible elsewhere, or if this bug should be
marked as resolved or not, as I'm way past due to do a clean install of
the newest Ubuntu:

rolandog@computer:~$ lsb_release -rd
Description:Ubuntu 20.10
Release:20.10

rolandog@computer:~$ apt-cache policy evince
evince:
  Installed: 3.38.0-1
  Candidate: 3.38.0-1
  Version table:
 *** 3.38.0-1 500
500 http://nl.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
100 /var/lib/dpkg/status

I hope this helps out someone getting unexpected behavior.

** Attachment added: "rolandog-apparmor-kernel-audit-2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/462419/+attachment/5509157/+files/rolandog-apparmor-kernel-audit-2.txt

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

Title:
  evince apparmor profile prevents movies from opening

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: evince

  Trying to open a movie with vlc or totem from within evince. I get the
  error: "Failed to execute child process vlc (Permission denied)". The
  same with totem.

  I have been looking at all the "apparmor prevents" bugs that have been
  reported of late. DVI printing, chromium, etc... the package
  maintainers' strategy has been to add an exceptions to the apparmor
  profile as the bugs come in. May I comment that this is a ludicrous
  situation? There are going to be numerous helper applications that
  people might want to use within a PDF file... why is apparmor blocking
  them all?

  [22:47][kirkwood][~] > lsb_release -rd
  Description:Ubuntu 9.10
  Release:9.10
  [22:48][kirkwood][~] > apt-cache policy evince
  evince:
Installed: 2.28.1-0ubuntu1
Candidate: 2.28.1-0ubuntu1
Version table:
   *** 2.28.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com karmic/main Packages
  100 /var/lib/dpkg/status

  Expected to happen: movie opens when clicked on
  What happens instead: help application (totem/vlc) prevented from running by 
apparmor
  Reproducible: 100%

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/462419/+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 1925320] Re: Backport packages for 20.04.3 HWE stack

[Mateusz Stachowski]

I've got updates for mesa 21.0.1-2 July 1st and it was upgrade from
20.2.6 which worked without such problems. Then July 2nd there was
upgrade to 21.0.3-0.

I'm not sure if the problems started with 21.0.1.

Also there are programs that work without graphical glitches.
Suprisingly Firefox doesn't have problems but my main webbrowser Vivaldi
does. Also I was able to watch Amazon Prime using ElectronPlayer the
videos display without glitches however the menus of that program do
have glitches.

Also I've checked LiveCD image of Impish and there wasn't any problems
with that.

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

Title:
  Backport packages for 20.04.3 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-12 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in directx-headers source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in llvm-toolchain-12 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  directx-headers: a new package, nothing can go wrong

  libdrm: adds some new api, no changes to old stuff

  llvm-12: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+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 1867581] Re: Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

[corrado venturini]

installed too the last vmoon release...
same problem with last updates
mesa-va-drivers:
  Installed: 21.1.2-1
  Candidate: 21.1.2-1
  Version table:
 *** 21.1.2-1 500
500 http://archive.ubuntu.com/ubuntu impish/universe amd64 Packages
100 /var/lib/dpkg/status
mesa-vulkan-drivers:
  Installed: 21.1.2-1
  Candidate: 21.1.2-1
  Version table:
 *** 21.1.2-1 500
500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages
100 /var/lib/dpkg/status


** Attachment added: "The moon with unreadable characters"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867581/+attachment/5509169/+files/Screenshot%20from%202021-07-05%2020-17-57.png

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

Title:
  Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  ubuntu-bug mesa does not work, i don't see a package named mesa

  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.

  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
direct render: Yes
  corrado@corrado-x5-ff-0309:~$

  I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
  so now I'm opening this problem
  if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  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
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2020-03-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Tags:  focal ubuntu single-occurrence reproducible
  Uname: Linux 5.4.0-14-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: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  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 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/mesa/+bug/1867581/+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 1934688] [NEW] Tearing

[Niculescu Nicolae Mihai]

Public bug reported:

The tearing image is present all over this t61. especially at scroll.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-59-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Jul  5 20:50:34 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5]
   Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5]
InstallationDate: Installed on 2021-07-05 (0 days ago)
InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: LENOVO 7661V9Z
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic 
root=UUID=a3374028-cf0f-495f-9a41-121bf48bd983 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/18/2011
dmi.bios.release: 2.41
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETC9WW (2.29 )
dmi.board.name: 7661V9Z
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.ec.firmware.release: 1.6
dmi.modalias: 
dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:br2.41:efr1.6:svnLENOVO:pn7661V9Z:pvrThinkPadT61:rvnLENOVO:rn7661V9Z:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T61
dmi.product.name: 7661V9Z
dmi.product.version: ThinkPad T61
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Tearing

Status in xorg package in Ubuntu:
  New

Bug description:
  The tearing image is present all over this t61. especially at scroll.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Jul  5 20:50:34 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5]
 Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5]
  InstallationDate: Installed on 2021-07-05 (0 days ago)
  InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 7661V9Z
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic 
root=UUID=a3374028-cf0f-495f-9a41-121bf48bd983 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2011
  dmi.bios.release: 2.41
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETC9WW (2.29 )
  dmi.board.name: 7661V9Z
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:br2.41:efr1.6:svnLENOVO:pn7661V9Z:pvrThinkPadT61:rvnLENOVO:rn7661V9Z:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T61
  dmi.product.name: 7661V9Z
  dmi.product.version: Thi

[Touch-packages] [Bug 1918458] Re: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback
  problem, no sound from speakers, headphones ok

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Expect : sound from speaker
  Instead, obtain : no sound.

  
  Tried various configuration of /etc/modprobe.d/alsa-conf with :

  options snd-hda-intel model= and
  options snd-intel-dspcfg dsp_driver=3 or 1
  and systematic reboot.

  Either I get dummy output, or I get proper output detection, alsamixer
  and pavucontrol seems 100% ok, but no sound comes from the speakers.

  I'm under a dualboot with Windows 10, BIOS fast boot disabled.
  Ubuntu 20.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thibauts   1522 F pulseaudio
   /dev/snd/pcmC0D0p:   thibauts   1522 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 10 18:10:30 2021
  InstallationDate: Installed on 2021-03-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Cannon Point-LP High Definition Audio Controller - sof-hda-dsp
  Symptom_Jack: Grey Speaker, Internal
  Symptom_Type: Only some of outputs are working
  Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2019
  dmi.bios.release: 1.4
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Default string
  dmi.board.name: Guinness_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd05/24/2019:br1.4:efr1.6:svnAcer:pnSwiftSF515-51T:pvrV1.04:rvnWL:rnGuinness_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 5
  dmi.product.name: Swift SF515-51T
  dmi.product.sku: 
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-03-10T18:04:19.277254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1918458/+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 1808624] Re: package libmpg123-0:amd64 1.22.4-1 failed to install/upgrade: package libmpg123-0:amd64 is not ready for configuration cannot configure (current status 'half-install

[Sebastian Ramacher]

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

** This bug has been marked a duplicate of bug 1632268
   package libmpg123-0:i386 1.22.4-1 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration

** This bug is no longer a duplicate of bug 1632268
   package libmpg123-0:i386 1.22.4-1 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
** This bug has been marked a duplicate of bug 1572167
   package libavcodec-ffmpeg-extra56:amd64 7:2.7.6-0ubuntu0.15.10.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration

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

Title:
  package libmpg123-0:amd64 1.22.4-1 failed to install/upgrade: package
  libmpg123-0:amd64 is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in mpg123 package in Ubuntu:
  New

Bug description:
  Trying to fix grub but the operation fails

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libmpg123-0:amd64 1.22.4-1
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Sat Dec 15 15:39:44 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
  DpkgHistoryLog:
   Start-Date: 2018-12-15  15:39:25
   Commandline: apt-get install -y boot-repair
   Requested-By: nitish (1000)
   Install: python-gi:amd64 (3.20.0-0ubuntu1, automatic), pastebinit:amd64 
(1.5-1, automatic), gawk:amd64 (1:4.1.3+dfsg-0.1, automatic), boot-sav:amd64 
(4ppa65, automatic), boot-sav-extra:amd64 (4ppa65, automatic), 
glade2script:amd64 (3.2.3~ppa4, automatic), libsigsegv2:amd64 (2.10-4, 
automatic), boot-repair:amd64 (4ppa65)
  DuplicateSignature:
   package:libmpg123-0:amd64:1.22.4-1
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package libmpg123-0:amd64 (--configure):
package libmpg123-0:amd64 is not ready for configuration
  ErrorMessage: package libmpg123-0:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2018-03-29 (260 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: mpg123
  Title: package libmpg123-0:amd64 1.22.4-1 failed to install/upgrade: package 
libmpg123-0:amd64 is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/1808624/+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 1632268] Re: package libmpg123-0:i386 1.22.4-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Sebastian Ramacher]

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

** This bug has been marked a duplicate of bug 1572167
   package libavcodec-ffmpeg-extra56:amd64 7:2.7.6-0ubuntu0.15.10.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration

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

Title:
  package libmpg123-0:i386 1.22.4-1 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in mpg123 package in Ubuntu:
  Confirmed

Bug description:
  not possible to deinstall that package by any means

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libmpg123-0:i386 1.22.4-1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Oct 11 10:45:19 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
  DuplicateSignature:
   package:libmpg123-0:i386:1.22.4-1
   Unpacking linux-libc-dev:amd64 (4.4.0-42.62) over (4.4.0-38.57) ...
   dpkg: error processing package libmpg123-0:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-07-12 (90 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: mpg123
  Title: package libmpg123-0:i386 1.22.4-1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Launchpad Bug Tracker]

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

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

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

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

Title:
  package libmpg123-0:i386 1.22.4-1 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in mpg123 package in Ubuntu:
  Confirmed

Bug description:
  not possible to deinstall that package by any means

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libmpg123-0:i386 1.22.4-1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Oct 11 10:45:19 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
  DuplicateSignature:
   package:libmpg123-0:i386:1.22.4-1
   Unpacking linux-libc-dev:amd64 (4.4.0-42.62) over (4.4.0-38.57) ...
   dpkg: error processing package libmpg123-0:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-07-12 (90 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: mpg123
  Title: package libmpg123-0:i386 1.22.4-1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/1632268/+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 297080] Re: mpg123 fails playing icecast streams

[Sebastian Ramacher]

** Changed in: mpg123 (Ubuntu)
   Status: New => Fix Released

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

Title:
  mpg123 fails playing icecast streams

Status in mpg123 package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: mpg123

  1) Ubuntu Release Information:
  Description: Ubuntu 8.10
  Release: 8.10

  2) Package Version:
  mpg123:
Installed: 1.4.3-3
Candidate: 1.4.3-3

  3) I expected to play a streaming icecast server through Asterisk
  which failed. I tested and narrowed the problem down to the version of
  mpg123 currently in stable.

  4) Using the command "mpg123 -s http://twit.am/listen > test.mp3" I
  got the following output:

  -BEGIN 
OUTPUT
  High Performance MPEG 1.0/2.0/2.5 Audio Player for Layers 1, 2 and 3
   version 1.4.3; written and copyright by Michael Hipp and others
   free software (LGPL/GPL) without any warranty but with best wishes

  Directory: http://twit.am/
  Playing MPEG stream 1 of 1: listen ...
  ICY-NAME: TWiT After Hours (Pre-recorded)
  ICY-URL: http://twit.am/listen
  MPEG 1.0 layer III, 64 kbit/s, 44100 Hz mono

  ICY-META: StreamTitle='1918-11-11_WINSTONCHURCHILL_00 - Winston Churchill';
  Note: Illegal Audio-MPEG-Header 0xcbb47d34 at offset 0x30ae.
  [parse.c:657] error: not attempting to resync...
  [mpg123.c:571] error: ...in decoding next frame: Lost track in the bytestream 
and did not attempt resync. (code 27)

  [0:01] Decoding of listen finished.
  -END 
OUTPUT

  This seems to be a known and fixed problem, see the news archive at
  http://www.mpg123.org/cgi-bin/news.cgi regarding both "resync is
  enabled again for ICY streams (the trouble in the past was due to a
  reader bug, not the streams)" and "workaround for frames that fail
  decoding (bad frame body, missing bit reservoir): fill up with
  silence"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/297080/+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 105586] Re: mpg123 does not support large files

[Sebastian Ramacher]

** Changed in: mpg123 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  mpg123 does not support large files

Status in mpg123 package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: mpg123-esd

  I was saving a MP3 stream to WAV file, and mpg123 (which is actually
  symlinked to mpg123-esd on my system) died when the output file hit
  2GB in size.  It appears that mpg123-esd needs to be recompiled with
  largefile support.  Largefile support should be enabled for all
  programs.

  
  system:bhalla370: mpg123 -w poodles.wav -@ 
http://10.0.0.251:9100/listen.m3u
  High Performance MPEG 1.0/2.0/2.5 Audio Player for Layers 1, 2 and 3
  version 0.60; written and copyright by Michael Hipp and others
  free software (LGPL/GPL) without any warranty but with best wishes

  Directory: http://10.0.0.251:9100/
  Playing MPEG stream 1 of 1: listen ...
  Note: Junk at the beginning (0x024a09a3)
  MPEG 1.0 layer III, 64 kbits/s, 44100 Hz joint-stereo
   zsh: file size limit exceeded (core dumped)  mpg123 -w poodles.wav -@ 
http://10.0.0.251:9100/listen.m3u

  system:bhalla384: ls -alt /opt/mp3/poodles.wav 
  -rw-r--r--1 bhalla   users2147483647 Apr 10 18:41 /opt/mp3/poodles.wav

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/105586/+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 1918458] Re: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok

[Hui Wang]

Does the speaker work normally in the windows? If yes, please run this
dumptool to get the codec setting.

Then in the linux, run 'sudo sh -c 'echo 1 >
/sys/module/snd_hda_codec/parameters/dump_coef', and run 'alsa-info
--no-upload' to get the alsa-info.txt.

Please upload both generated log files.

thx.

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

Title:
  [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback
  problem, no sound from speakers, headphones ok

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Expect : sound from speaker
  Instead, obtain : no sound.

  
  Tried various configuration of /etc/modprobe.d/alsa-conf with :

  options snd-hda-intel model= and
  options snd-intel-dspcfg dsp_driver=3 or 1
  and systematic reboot.

  Either I get dummy output, or I get proper output detection, alsamixer
  and pavucontrol seems 100% ok, but no sound comes from the speakers.

  I'm under a dualboot with Windows 10, BIOS fast boot disabled.
  Ubuntu 20.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thibauts   1522 F pulseaudio
   /dev/snd/pcmC0D0p:   thibauts   1522 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 10 18:10:30 2021
  InstallationDate: Installed on 2021-03-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Cannon Point-LP High Definition Audio Controller - sof-hda-dsp
  Symptom_Jack: Grey Speaker, Internal
  Symptom_Type: Only some of outputs are working
  Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2019
  dmi.bios.release: 1.4
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Default string
  dmi.board.name: Guinness_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd05/24/2019:br1.4:efr1.6:svnAcer:pnSwiftSF515-51T:pvrV1.04:rvnWL:rnGuinness_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 5
  dmi.product.name: Swift SF515-51T
  dmi.product.sku: 
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-03-10T18:04:19.277254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1918458/+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 1918458] Re: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok

[Hui Wang]

this is the dumptool in the windows.

** Attachment added: "RtHDDump_V236.zip"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1918458/+attachment/5509207/+files/RtHDDump_V236.zip

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

Title:
  [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback
  problem, no sound from speakers, headphones ok

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Expect : sound from speaker
  Instead, obtain : no sound.

  
  Tried various configuration of /etc/modprobe.d/alsa-conf with :

  options snd-hda-intel model= and
  options snd-intel-dspcfg dsp_driver=3 or 1
  and systematic reboot.

  Either I get dummy output, or I get proper output detection, alsamixer
  and pavucontrol seems 100% ok, but no sound comes from the speakers.

  I'm under a dualboot with Windows 10, BIOS fast boot disabled.
  Ubuntu 20.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thibauts   1522 F pulseaudio
   /dev/snd/pcmC0D0p:   thibauts   1522 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 10 18:10:30 2021
  InstallationDate: Installed on 2021-03-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Cannon Point-LP High Definition Audio Controller - sof-hda-dsp
  Symptom_Jack: Grey Speaker, Internal
  Symptom_Type: Only some of outputs are working
  Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2019
  dmi.bios.release: 1.4
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Default string
  dmi.board.name: Guinness_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd05/24/2019:br1.4:efr1.6:svnAcer:pnSwiftSF515-51T:pvrV1.04:rvnWL:rnGuinness_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 5
  dmi.product.name: Swift SF515-51T
  dmi.product.sku: 
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-03-10T18:04:19.277254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1918458/+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 1934688] Re: Tearing

[Daniel van Vugt]

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

** Tags added: tearing

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

Title:
  Tearing

Status in xfce4 package in Ubuntu:
  New

Bug description:
  The tearing image is present all over this t61. especially at scroll.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Jul  5 20:50:34 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5]
 Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5]
  InstallationDate: Installed on 2021-07-05 (0 days ago)
  InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 7661V9Z
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic 
root=UUID=a3374028-cf0f-495f-9a41-121bf48bd983 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2011
  dmi.bios.release: 2.41
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETC9WW (2.29 )
  dmi.board.name: 7661V9Z
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:br2.41:efr1.6:svnLENOVO:pn7661V9Z:pvrThinkPadT61:rvnLENOVO:rn7661V9Z:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T61
  dmi.product.name: 7661V9Z
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4/+bug/1934688/+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 1930279] Re: [Ivy Bridge] flashing sliced triangles on screen

[Daniel van Vugt]

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

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

Title:
  [Ivy Bridge] flashing sliced triangles on screen

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  when i did upgrade my ubuntu from 20.04 to 20.10 i have small winking
  triangles on my screen, they sometimes will appear when i watching a
  youtube video they will appear on the video's seek bar or when i
  typing they will appear on selected texts,but the main and most
  annoying state of it happens when I am playing minecraft,my entire
  game screen has these little triangles

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 31 18:05:33 2021
  DistUpgraded: 2021-05-27 14:18:07,483 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [1043:844d]
  InstallationDate: Installed on 2020-01-10 (507 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic 
root=UUID=a5a5279f-cdf5-4129-94fa-8f17f7401833 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2021-05-27 (4 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1204
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX R2.0
  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.:bvr1204:bd03/19/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/linux/+bug/1930279/+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 1931765] Re: VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston)

[Daniel van Vugt]

PPAs are not supported and you use them at your own risk. Please don't
log bugs about packages from a PPA because we can't help with them.

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

Title:
  VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston)

Status in libva package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid

Bug description:
  SUMMARY

  VAAPI is broken on KDE Plasma Wayland and Weston Session

  STEPS TO REPRODUCE
  1. Open a terminal
  2. Type in vainfo

  
  OBSERVED RESULT

  Error Message:
  heiko@Tuxedobook:~$ vainfo
  wl_drm@6: error 0: authenticate failed
  VA error: wayland: Wayland roundtrip error: Protocol error (errno 71)
  libva info: VA-API version 1.10.0
  libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, 
driver_name = (null)
  vaInitialize failed with error code 3 (invalid VADisplay),exit


  EXPECTED RESULT
  Should show VAAPI information without errors like on X11 session

  This bug was reproduced multiple times on two systems one with an
  intel igpu and one with a dedicated AMD GPU. Both systems are using
  the MESA drivers from this ppa:

  https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa

  This bug was discovered because KODI Mediacenter was crashing on
  startup on wayland while it is working flawless on X11/X.org.

  SOFTWARE/OS VERSIONS
  Linux/KDE Plasma: Kubuntu 21.04 
  (available in About System)
  KDE Plasma Version: 5.22.0 

  
  ADDITIONAL INFORMATION

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1931765/+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 1934647] Re: Nvidia driver black screen at login.

[Daniel van Vugt]

Thanks for the bug report. Please be careful to only report one problem
per bug. You can open multiple bugs.

Let's make this bug about the black screen issue only. To debug that
further we will need to see a system log from when the Nvidia driver was
installed and you did NOT have "recovery nomodeset" kernel parameters.

Please run:

  journalctl -b-1 > prevboot1.txt
  journalctl -b-2 > prevboot2.txt
  journalctl -b-3 > prevboot3.txt
  journalctl -b-4 > prevboot4.txt
  journalctl -b-5 > prevboot5.txt

and attach the resulting text files.


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

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

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

Title:
  Nvidia driver black screen at login.

Status in Ubuntu:
  Incomplete

Bug description:
  If I choose nvidia driver, then the screen is black and I cannot log in. To 
log in, I need to delete all nvidia files.
  After that, the xorg is selected and I can log in. But I cannot edit 
brightness. I can hardly see anything on the screen. The battery is draining 
very badly.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  5 10:54:41 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 460.80, 5.11.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] 
[103c:85fb]
  InstallationDate: Installed on 2021-06-25 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro recovery nomodeset 
dis_ucode_ldr
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2020
  dmi.bios.release: 15.33
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 85FB
  dmi.board.vendor: HP
  dmi.board.version: 42.42
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 42.42
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx
  dmi.product.sku: 2C7M8EA#ACB
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1934647/+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 1934607] Re: aptd ibelieve crashed

[Daniel van Vugt]

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

Title:
  aptd ibelieve crashed

Status in Ubuntu:
  Incomplete

Bug description:
  ???

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177
  Uname: Linux 4.4.0-148-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Jul  4 15:23:22 2021
  DistUpgraded: 2021-07-04 15:23:15,866 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 82Q963/Q965 Integrated Graphics Controller [8086:2992] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:4f43]
  InstallationDate: Installed on 2021-07-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-148-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2021-07-04 (0 days ago)
  dmi.bios.date: 11/02/2006
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: CO96510J.86A.5493.2006.1102.1728
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DQ965GF
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD41676-400
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrCO96510J.86A.5493.2006.1102.1728:bd11/02/2006:svnBriteComputers:pn:pvr:rvnIntelCorporation:rnDQ965GF:rvrAAD41676-400:cvn:ct2:cvr:
  dmi.sys.vendor: Brite Computers
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Jul  4 15:12:47 2021
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputSleep Button KEYBOARD, id 7
   input2.4G Wireless Mouse  MOUSE, id 8
   inputSONiX USB DEVICE KEYBOARD, id 9
   inputSONiX USB DEVICE KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12327 
   vendor HWP
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1934607/+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 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default

[Christian Ehrhardt ]

The DNSmasq change is in impish as well.
Since we (intentionally) referenced but not closed the bug by the upload I'll 
have to tag that manually.

** Changed in: dnsmasq (Ubuntu Impish)
   Status: Triaged => Fix Released

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

Title:
  [2.82 regression] router announcements have 'forever' lifetime by
  default

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Groovy:
  Fix Released
Status in network-manager source package in Groovy:
  Invalid
Status in dnsmasq source package in Hirsute:
  Fix Released
Status in network-manager source package in Hirsute:
  Invalid
Status in dnsmasq source package in Impish:
  Fix Released
Status in network-manager source package in Impish:
  Fix Released
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  The default lifetime was changed to 1 day in 2.82 in the change
  corresponding to this changelog entry:

  Change default lease time for DHCPv6 to one day.

  Fine, but the same commit also did this:

Alter calculation of preferred and valid times in router
advertisements, so that these do not have a floor applied
of the lease time in the dhcp-range if this is not explicitly
specified and is merely the default.

  And that change is buggy and causes advertisements to have infinite
  lifetime, when you are using the default.

  See this thread

http://lists.thekelleys.org.uk/pipermail/dnsmasq-
  discuss/2020q3/014341.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+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 1925320] Re: Backport packages for 20.04.3 HWE stack

[Timo Aaltonen]

best to file a separate bug anyway

that said, I'm not sure if this should block the updates, since I wasn't
able to reproduce it with a gpu of the same family

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

Title:
  Backport packages for 20.04.3 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-12 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in directx-headers source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in llvm-toolchain-12 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  directx-headers: a new package, nothing can go wrong

  libdrm: adds some new api, no changes to old stuff

  llvm-12: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+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 1867581] Re: Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

[Timo Aaltonen]

file a bug upstream then

https://gitlab.freedesktop.org/mesa/mesa/-/issues

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

Title:
  Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  ubuntu-bug mesa does not work, i don't see a package named mesa

  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.

  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
direct render: Yes
  corrado@corrado-x5-ff-0309:~$

  I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
  so now I'm opening this problem
  if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  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
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2020-03-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Tags:  focal ubuntu single-occurrence reproducible
  Uname: Linux 5.4.0-14-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: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  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 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/mesa/+bug/1867581/+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 1931765] Re: VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston)

[Heiko Gimbel]

At first i did not know that the problem was caused by the ppa. However
i think that the MESA drivers should always be upgraded to the latest
stable version. Ubuntu should handle the MESA packages like firefox.
Ubuntu is the only officialy supported linuxdistribution supported by
Steam for gaming and runs on outdated gpudrivers.

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

Title:
  VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston)

Status in libva package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid

Bug description:
  SUMMARY

  VAAPI is broken on KDE Plasma Wayland and Weston Session

  STEPS TO REPRODUCE
  1. Open a terminal
  2. Type in vainfo

  
  OBSERVED RESULT

  Error Message:
  heiko@Tuxedobook:~$ vainfo
  wl_drm@6: error 0: authenticate failed
  VA error: wayland: Wayland roundtrip error: Protocol error (errno 71)
  libva info: VA-API version 1.10.0
  libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, 
driver_name = (null)
  vaInitialize failed with error code 3 (invalid VADisplay),exit


  EXPECTED RESULT
  Should show VAAPI information without errors like on X11 session

  This bug was reproduced multiple times on two systems one with an
  intel igpu and one with a dedicated AMD GPU. Both systems are using
  the MESA drivers from this ppa:

  https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa

  This bug was discovered because KODI Mediacenter was crashing on
  startup on wayland while it is working flawless on X11/X.org.

  SOFTWARE/OS VERSIONS
  Linux/KDE Plasma: Kubuntu 21.04 
  (available in About System)
  KDE Plasma Version: 5.22.0 

  
  ADDITIONAL INFORMATION

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1931765/+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 1918855] Re: Xorg xserver got signal 6 to abort

[Kai-Heng Feng]

I enable -proposed and do a dist-upgrade, made sure
21.0.3-0ubuntu0.1~20.04.1 is installed, then reboot and run stress-ng:

$ stress-ng --stack 0 --timeout 300
stress-ng: info:  [1782] dispatching hogs: 16 stack
stress-ng: info:  [1782] successful run completed in 300.47s (5 mins, 0.47 secs)

The desktop session didn't crash so it's still alive.


** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

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

Title:
  Xorg xserver got signal 6 to abort

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Committed
Status in mesa source package in Hirsute:
  Fix Committed

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may 
crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if 
kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session 
is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory 
pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on 
focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

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