date:20211209

[Touch-packages] [Bug 1952083] Re: Add support for Beige Goby

2021-12-09 Thread Akbarkhon Variskhanov

@tjaalton, I always use the main official server (archive.ubuntu.com).
Anyway, there were no errors today and the update went smoothly.

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

Title:
  Add support for Beige Goby

Status in amd:
  New
Status in OEM Priority Project:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released

Bug description:
  Impact]

  New hardware support for AMD's Beige Goby needs a commit backported to
  mesa. This is only needed on focal, skipping hirsute (no kernel
  support there). Fixed in impish and up.

  [Test plan]

  Install updates, boot a BG machine and check that the desktop has full
  hardware acceleration.

  [Where problems could occur]

  Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what
  could go wrong.

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


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

[Touch-packages] [Bug 1927255] Re: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04)

2021-12-09 Thread Oliver Tacke

@Jacob Awesome research! Thanks!

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

Title:
  [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I got a Rodecaster Pro USB device that has been causing trouble before
  and already lead to quirk handling in the kernel for the sample rate,
  see
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/usb/format.c?h=v5.8#n412

  The Rodecaster is running fine on my laptop, but on my desktop, only
  audio input is working. The audio output is distorted. It's played
  kind of very slowly. Interestingly, if the source is a video file, the
  video plays slower, e.g. YouTube in a browser. I have never seen
  anything like that before.

  I have tried to figure out what the cause might be and I think I have
  reached the end of where I can get to on my own. I have documented
  most things at https://ubuntuforums.org/showthread.php?t=2461568

  Putting my last step it in a nutshell: I have booted both my computers
  with a plain Ubuntu 21.04 from a pen drive (it uses kernel version
  5.11.0-16-generic) to make sure it's not some different configuration
  that I have set up over the years on my systems (both Ubuntu 20.04
  with kernel 5.8.18). I attached the Rodecaster. It runs fine on my
  laptop, but not on my desktop (used the output test from).

  I then detected the card number with

  aplay -l

  I killed pulseaudio with

  pulseaudio -k

  I then played the same sample (encoded in 48000 Hz in PCM signed 32
  bit little endian format) using

  aplay -f S32_LE -c 2 -r 48000 -D hw:x ~/sample.wav

  where x is the appropriate card number and the rest of the arguments
  meet the Rodecaster's narrow specification. It's playing fine on the
  laptop, but distorted on the desktop. As far as I understand using
  aplay this way without a plugin should send the file directly to the
  device, so I assume there's something on the way from aplay to the
  Rodecaster that's interfering (kernel or even some piece of hardware)
  - and that definitely is where my expertise ends (rather a little
  before :-)).

  I'll gladly contribute any information that could be useful and I will
  willingly help to debug this problem if it may be related to the
  kernel. If there's anything I can do, please let me know.

  Cheers,
  Oliver

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.8.18-050818-generic x86_64
  NonfreeKernelModules: blackmagic_io nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Wed May  5 18:28:46 2021
  InstallationDate: Installed on 2020-05-15 (355 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Pro failed
  Symptom_Card: RODECaster Pro - RODECaster Pro
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B550-A PRO (MS-7C56)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C56
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

[Touch-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot

2021-12-09 Thread Fredrik Jacobsson

I would like to add that my computer resets the volume to 70% after I
resume from suspending.

DM: gdm
DE: gnome flashback

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

Title:
  In Jammy sound level reset after reboot

Status in alsa-utils package in Ubuntu:
  Confirmed

Bug description:
  After reboot sound level is reset ignoring the level set in previous
  session.

  I manually set the sound output level 
  at next boot the sound is set at a different level (about 70%)

  Expected: the sound level is persistent across power off/on

  What happens : sound level is set at a different level (about 70%)

  Note: this problem does not occur on different partitions of same PC
  running Ubuntu 20.04 or 21.10

  corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p3-jj-1130:~$ inxi -Fx
  System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 
compiler: gcc v: 11.2.0
 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 

 Mobo: Dell model: 0C1PF2 v: A00 serial:  UEFI: 
Dell v: 1.5.0 date: 12/17/2019
  Battery:   ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) 
volts: 11.3 min: 11.4
 model: SWD-ATL3.618 DELL WJPC403 status: Discharging
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 cache:
 L2: 6 MiB
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046
 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 
710 3: 706 4: 714 5: 966 6: 712
 7: 724 8: 821
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus-ID: 00:02.0
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus-ID: 1-6:3
 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell 
driver: loaded: i915
 note: n/a (using device driver) resolution: 1920x1080~60Hz
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
21.2.2 direct render: Yes
  Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel
 bus-ID: 00:1f.3
 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes
 Sound Server-2: PulseAudio v: 15.0 running: yes
 Sound Server-3: PipeWire v: 0.3.40 running: yes
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000
 bus-ID: 01:00.0
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci
 v: kernel bus-ID: 02:00.0
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9
  Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 
1-10:4
 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: 
enabled,running rfk-block: hardware: no
 software: yes address: D8:12:65:B8:21:BA
  Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%)
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB temp: 24.9 C
 ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 
GiB
  Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: 
/dev/nvme0n1p3
 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  Alert: No swap data was found.
  Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A
 Fan Speeds (RPM): cpu: 0
  Info:  Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) 
Init: systemd runlevel: 5 Compilers:
 gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07
  corrado@corrado-p3-jj-1130:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-11-30 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  Package: gnome-control-center 1:41.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Tags:  wayland-session jammy
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev

[Touch-packages] [Bug 1927255] Re: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04)

2021-12-09 Thread Jacob Pfeifer

Hey guys, I was the one who started the amd chipset rumor. We've been
talking about the issue over at
https://forum.level1techs.com/t/rodecaster-pro-bad-audio-out-solved-
ish/170601.

At first I thought it was an amd vs intel issue just due to the hardware
I had on hand that worked/didn't work. After someone popped in
mentioning their intel device having the issue and a pcie card they
bought also having the issue it seems like the issue is with all usb3.2
gen2x2 host controllers, or at least that's my best guess. I picked up a
different pcie usb card than the person had trouble with and that was
3.2 gen2x2 capable. I can reproduce the issue on both it, and my
motherboard usb ports. However, using a usb3.0 pcie card the issue goes
away.

One strange thing to me about all of this is that the rodecaster pro is
negotiating usb2 480mbps connections, so i'm not sure why a later usb
spec would mess with that. It's also worth noting that the issue seems
to be related to the usb host controller itself as using ports capable
of different speeds/going through usb hubs or directly connecting
doesn't change the behavior. I also don't have a usb 3.1 gen2 host
controller to test to see if the issue is truly only with usb 3.2 gen2x2
controllers.

Debugging any further than that is proving difficult though. I did a
diff on both my lsusb and pw-dump output and the only changes in the two
were paths/ids which are expected to change.

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

Title:
[USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04)

Status in alsa-driver package in Ubuntu:
Confirmed

Bug description:
I got a Rodecaster Pro USB device that has been causing trouble before
and already lead to quirk handling in the kernel for the sample rate,
see

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/usb/format.c?h=v5.8#n412

The Rodecaster is running fine on my laptop, but on my desktop, only
audio input is working. The audio output is distorted. It's played
kind of very slowly. Interestingly, if the source is a video file, the
video plays slower, e.g. YouTube in a browser. I have never seen
anything like that before.

I have tried to figure out what the cause might be and I think I have
reached the end of where I can get to on my own. I have documented
most things at https://ubuntuforums.org/showthread.php?t=2461568

Putting my last step it in a nutshell: I have booted both my computers
with a plain Ubuntu 21.04 from a pen drive (it uses kernel version
5.11.0-16-generic) to make sure it's not some different configuration
that I have set up over the years on my systems (both Ubuntu 20.04
with kernel 5.8.18). I attached the Rodecaster. It runs fine on my
laptop, but not on my desktop (used the output test from).

I then detected the card number with

aplay -l

I killed pulseaudio with

pulseaudio -k

I then played the same sample (encoded in 48000 Hz in PCM signed 32
bit little endian format) using

aplay -f S32_LE -c 2 -r 48000 -D hw:x ~/sample.wav

where x is the appropriate card number and the rest of the arguments
meet the Rodecaster's narrow specification. It's playing fine on the
laptop, but distorted on the desktop. As far as I understand using
aplay this way without a plugin should send the file directly to the
device, so I assume there's something on the way from aplay to the
Rodecaster that's interfering (kernel or even some piece of hardware)
- and that definitely is where my expertise ends (rather a little
before :-)).

I'll gladly contribute any information that could be useful and I will
willingly help to debug this problem if it may be related to the
kernel. If there's anything I can do, please let me know.

Cheers,
Oliver

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 5.8.18-050818-generic x86_64
NonfreeKernelModules: blackmagic_io nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read
kernel buffer failed: Operation not permitted
Date: Wed May 5 18:28:46 2021
InstallationDate: Installed on 2020-05-15 (355 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Pro failed
Symptom_Card: RODECaster Pro - RODECaster Pro
Symptom_Type: Digital clip or distortion, or "overdriven" sound
Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/30/2020
dmi.bios.release:

[Touch-packages] [Bug 1953521] Re: fixrtc produces extraneous (confusing) output

2021-12-09 Thread Mathew Hodson

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

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

Title:
  fixrtc produces extraneous (confusing) output

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  The premount script for fixrtc produces a couple of lines of
  extraneous (and slightly confusing) output. While this is irrelevant
  for most platforms, on the pi images (which use fixrtc owing to the
  lack of an RTC on the board), it means that "ext4" and "Thu Jan  1
  00:00:10 UTC 1970" are the first console output on every boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1953521/+subscriptions


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

[Touch-packages] [Bug 1954348] [NEW] sed 4.8-1 needs patch disabling non-portable tests

2021-12-09 Thread Dave Jones

Public bug reported:

The sed 4.8-1 package currently in proposed is failing to migrate due to
a failing test on armhf. The patch added in 4.7-1ubuntu1 is still
required to work around this, and the attached debdiff restores this.

The patch has been applied upstream to gnulib
(https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=175e0bc72808d564074c4adcc72aeadb74adfcc6)
but sed upstream has not yet bumped the version of gnulib that it
vendors in (or more precisely has not made a release since bumping its
version of gnulib; 4.8 predates that).

The patch itself simply disables the non-portable tests which is not
exactly ideal, but given it's what upstream's gone with we ought to
follow suit.

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

** Patch added: "sed-migration.debdiff"
   
https://bugs.launchpad.net/bugs/1954348/+attachment/5546537/+files/sed-migration.debdiff

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

Title:
  sed 4.8-1 needs patch disabling non-portable tests

Status in sed package in Ubuntu:
  New

Bug description:
  The sed 4.8-1 package currently in proposed is failing to migrate due
  to a failing test on armhf. The patch added in 4.7-1ubuntu1 is still
  required to work around this, and the attached debdiff restores this.

  The patch has been applied upstream to gnulib
  
(https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=175e0bc72808d564074c4adcc72aeadb74adfcc6)
  but sed upstream has not yet bumped the version of gnulib that it
  vendors in (or more precisely has not made a release since bumping its
  version of gnulib; 4.8 predates that).

  The patch itself simply disables the non-portable tests which is not
  exactly ideal, but given it's what upstream's gone with we ought to
  follow suit.

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


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

[Touch-packages] [Bug 1946860] Re: Merge heimdal from Debian unstable for 22.04

2021-12-09 Thread Launchpad Bug Tracker

This bug was fixed in the package heimdal - 7.7.0+dfsg-3ubuntu1

---
heimdal (7.7.0+dfsg-3ubuntu1) jammy; urgency=medium

  * Merge with Debian unstable (LP: #1946860). Remaining changes:
- Disable lto, to regain dep on roken, otherwise dependencies on amd64
  are different to i386 resulting in different files on amd64 and
  i386. LP #1934936
- Remove symbol rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226
  (LP #1945787)

 -- Andreas Hasenack   Wed, 08 Dec 2021 18:02:13
-0300

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

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

Title:
  Merge heimdal from Debian unstable for 22.04

Status in heimdal package in Ubuntu:
  Fix Released

Bug description:
  Upstream: tbd
  Debian:   7.7.0+dfsg-2
  Ubuntu:   7.7.0+dfsg-2ubuntu2

  ### New Debian Changes ###

  heimdal (7.7.0+dfsg-2) unstable; urgency=medium

    * Build using python3. Closes: #936695, #960032.

   -- Brian May   Tue, 12 May 2020 06:56:04 +1000

  heimdal (7.7.0+dfsg-1) unstable; urgency=medium

    * New upstream version.
    * Fix CVE-2019-14870: The DelegationNotAllowed Kerberos feature restriction
  was not being applied when processing protocol
  transition requests (S4U2Self), in the AD DC KDC. Closes: #946786.

   -- Brian May   Tue, 17 Dec 2019 20:23:41 +1100

  heimdal (7.5.0+dfsg-3) unstable; urgency=high

    * CVE-2018-16860: Samba AD DC S4U2Self/S4U2Proxy unkeyed checksum.
  Closes: #928966.
    * CVE-2019-12098: Always confirm PA-PKINIT-KX for anon PKINIT.
  Closes: #929064.
    * Update test certificates to pre 2038 expiry. Closes: #923930.

   -- Brian May   Tue, 21 May 2019 18:04:35 +1000

  heimdal (7.5.0+dfsg-2.1) unstable; urgency=medium

    * Non-maintainer upload
    * Add patch to create headers before building (Closes: 906623)

   -- Hilko Bengen   Sun, 28 Oct 2018 15:10:44 +0100

  heimdal (7.5.0+dfsg-2) unstable; urgency=medium

    * Replace 'MAXHOSTNAMELEN' with 'MaxHostNameLen' in kdc/kx509.c for The
  Hurd. Closes: #900079.

   -- Brian May   Sat, 02 Jun 2018 10:01:46 +1000

  heimdal (7.5.0+dfsg-1) unstable; urgency=high

    * New upstream version. (Closes: #850723)
  + CVE-2017-17439: Remote unauthenticated DoS in Heimdal-KDC 7.4
    (Closes: #878144, #868157)
  + Refresh patches.
    * Bump Standards-Version to 4.1.2 and compat level to 10.
  + Remove explicit reference to dh-autoreconf.
    * Use uscan to get orig source.
  + Refrain from mangling some bundled RFC texts;
    just exclude the mas they are not installed into any binary anyway.
  + Update d/copyright to DEP-5.
  + Can now use standard uscan/gbp/pristine-tar workflow.
    * Fix some lintian errors/warnings.
  + Strip trailing whitespace from changelog.
  + Fix some duplicate long descriptions.
  + Use optional priority everywhere.
  + Update/remove some overrides.
  + Enforce set -e in maintainer scripts.
  + Enable hardening.
    * Migrate to -dbgsym.
    * Add myself to uploaders.

   -- Dominik George   Fri, 15 Dec 2017 01:13:04
  +0100

  heimdal (7.4.0.dfsg.1-2) unstable; urgency=medium

    [ Jelmer Vernooĳ ]
    * Remove myself from uploaders.

    [ Brian May ]
    * Be explicit with heimdal.mkey filename in postinst. Closes: #868638.
    * Tests should respect DEB_BUILD_OPTIONS=nocheck.  Closes: #868842.

   -- Brian May   Sun, 23 Jul 2017 10:32:34 +1000

  heimdal (7.4.0.dfsg.1-1) unstable; urgency=high

    * New upstream version.
    * Update standards version to 4.0.0.
    * CVE-2017-11103: Fix Orpheus' Lyre KDC-REP service name validation.
  (Closes: #868208).

   -- Brian May   Sat, 15 Jul 2017 19:47:32 +1000

  heimdal (7.1.0+dfsg-13) unstable; urgency=medium

    * Add missing symbols base64_decode and base64_encode back into
  libroken. Closes: #848694.

   -- Brian May   Wed, 26 Apr 2017 19:38:20 +1000

  heimdal (7.1.0+dfsg-12) unstable; urgency=high

    * Fix transit path validation CVE-2017-6594.

   -- Brian May   Mon, 10 Apr 2017 17:21:35 +1000

  heimdal (7.1.0+dfsg-11) unstable; urgency=medium

    * Remove legacy provides/conflicts/replaces headers. Old daemons

  ### Old Ubuntu Delta ###

  heimdal (7.7.0+dfsg-2ubuntu2) impish; urgency=medium

    * Remove symbol rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226
  (LP: #1945787)

   -- Heinrich Schuchardt   Fri, 01
  Oct 2021 15:03:02 +0200

  heimdal (7.7.0+dfsg-2ubuntu1) impish; urgency=medium

    * Disable lto, to regain dep on roken, otherwise dependencies on amd64
  are different to i386 resulting in different files on amd64 and
  i386. LP: #1934936

   -- Dimitri John Ledkov   Tue, 20 Jul
  2021 10:32:53 +0100

  heimdal (7.7.0+dfsg-2build1) impish; urgency=medium

    * No-change rebuild due to OpenLDAP soname bump.

   -- Sergio

[Touch-packages] [Bug 1954320] Re: Add privacy screen modules to the initrd

2021-12-09 Thread Sebastien Bacher

I'm tagging the bug rls-jj-incoming for it to be reviewed as a target
for the cycle, we don't plan to update to 5.17 afaik but the feature is
requested by oem partners and we will likely end up cherry picking the
kernel changes to the version we include

** Tags added: rls-jj-incoming

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => High

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

Title:
  Add privacy screen modules to the initrd

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Starting with kernel 5.17 the kernel supports the builtin privacy
  screens built into the LCD panel of some new laptop models.

  This means that the drm drivers will now return -EPROBE_DEFER from
  their probe() method on models with a builtin privacy screen when the
  privacy screen provider driver has not been loaded yet.

  To avoid any regressions Ubuntu should modify its initrd generation
  tool to include privacy screen provider drivers in the initrd (at
  least on systems with a privacy screen), before 5.17 kernels start
  showing up in the Ubuntu repos.

  If this change is not made, then users using a graphical bootsplash
  (plymouth) will get an extra boot-delay of up to 8 seconds
  (DeviceTimeout in plymouthd.defaults) before plymouth will show and
  when using disk-encryption where the LUKS password is requested from
  the initrd, the system may fallback to text-mode after these 8
  seconds.

  I've written a patch with the necessary changes for dracut, which
  might be useful as an example for how to deal with this, see:
  https://github.com/dracutdevs/dracut/pull/1666

  ATM the only kms driver using privacy screens is the i915 driver and
  the only provider is the thinkpad_acpi driver. But both are likely to
  change (and change soon!), so the detection really should be made
  dynamic as has been done in the dracut patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1954320/+subscriptions


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

[Touch-packages] [Bug 1954320] Re: Add privacy screen modules to the initrd

2021-12-09 Thread Hans de Goede

** Package changed: linux (Ubuntu) => initramfs-tools (Ubuntu)

** Changed in: initramfs-tools (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Add privacy screen modules to the initrd

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Starting with kernel 5.17 the kernel supports the builtin privacy
  screens built into the LCD panel of some new laptop models.

  This means that the drm drivers will now return -EPROBE_DEFER from
  their probe() method on models with a builtin privacy screen when the
  privacy screen provider driver has not been loaded yet.

  To avoid any regressions Ubuntu should modify its initrd generation
  tool to include privacy screen provider drivers in the initrd (at
  least on systems with a privacy screen), before 5.17 kernels start
  showing up in the Ubuntu repos.

  If this change is not made, then users using a graphical bootsplash
  (plymouth) will get an extra boot-delay of up to 8 seconds
  (DeviceTimeout in plymouthd.defaults) before plymouth will show and
  when using disk-encryption where the LUKS password is requested from
  the initrd, the system may fallback to text-mode after these 8
  seconds.

  I've written a patch with the necessary changes for dracut, which
  might be useful as an example for how to deal with this, see:
  https://github.com/dracutdevs/dracut/pull/1666

  ATM the only kms driver using privacy screens is the i915 driver and
  the only provider is the thinkpad_acpi driver. But both are likely to
  change (and change soon!), so the detection really should be made
  dynamic as has been done in the dracut patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1954320/+subscriptions


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

[Touch-packages] [Bug 1954320] [NEW] Add privacy screen modules to the initrd

2021-12-09 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Starting with kernel 5.17 the kernel supports the builtin privacy
screens built into the LCD panel of some new laptop models.

This means that the drm drivers will now return -EPROBE_DEFER from their
probe() method on models with a builtin privacy screen when the privacy
screen provider driver has not been loaded yet.

To avoid any regressions Ubuntu should modify its initrd generation tool
to include privacy screen provider drivers in the initrd (at least on
systems with a privacy screen), before 5.17 kernels start showing up in
the Ubuntu repos.

If this change is not made, then users using a graphical bootsplash
(plymouth) will get an extra boot-delay of up to 8 seconds
(DeviceTimeout in plymouthd.defaults) before plymouth will show and when
using disk-encryption where the LUKS password is requested from the
initrd, the system may fallback to text-mode after these 8 seconds.

I've written a patch with the necessary changes for dracut, which might
be useful as an example for how to deal with this, see:
https://github.com/dracutdevs/dracut/pull/1666

ATM the only kms driver using privacy screens is the i915 driver and the
only provider is the thinkpad_acpi driver. But both are likely to change
(and change soon!), so the detection really should be made dynamic as
has been done in the dracut patch.

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

-- 
Add privacy screen modules to the initrd
https://bugs.launchpad.net/bugs/1954320
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to initramfs-tools in Ubuntu.

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

[Touch-packages] [Bug 1954311] Re: Daily cron job script unnecessarily executes `find` with `rm` instead of using its '-delete' action

2021-12-09 Thread Ubuntu Foundations Team Bug Bot

The attachment "apport.patch" seems to be a patch.  If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Daily cron job script unnecessarily executes `find` with `rm` instead
  of using its '-delete' action

Status in apport package in Ubuntu:
  New

Bug description:
  Executing `rm` as a separate process each time for every single file
  is unnecessary and inefficient. The option '-delete' should be used
  instead.

  Patch is included below.

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


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

[Touch-packages] [Bug 1823422] Re: heimdal ftbfs in disco

2021-12-09 Thread Andreas Hasenack

Disco is EOL, and the package builds fine in current devel release.
Closing the bug.

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

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

Title:
  heimdal ftbfs in disco

Status in Heimdal:
  New
Status in heimdal package in Ubuntu:
  Fix Released
Status in heimdal package in Debian:
  Fix Released

Bug description:
  https://launchpadlibrarian.net/417925401/buildlog_ubuntu-disco-
  amd64.heimdal_7.5.0+dfsg-2.1_BUILDING.txt.gz

  =
 Heimdal 7.5.0: lib/hx509/test-suite.log
  =

  # TOTAL: 16
  # PASS:  15
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0

  .. contents:: :depth: 2

  FAIL: test_chain
  

  cert -> root
  cert -> root
  cert -> root
  sub-cert -> root
  sub-cert -> sub-ca -> root
  sub-cert -> sub-ca
  sub-cert -> sub-ca -> root
  sub-cert -> sub-ca -> root
  sub-cert -> sub-ca -> root
  max depth 2 (ok)
  max depth 1 (fail)
  ocsp non-ca responder
  ocsp ca responder
  ocsp no-ca responder, missing cert
  ocsp no-ca responder, missing cert, in pool
  ocsp no-ca responder, keyHash
  ocsp revoked cert
  ocsp print reply resp1-ocsp-no-cert
  ocsp print reply resp1-ca
  ocsp print reply resp1-keyhash
  ocsp print reply resp2
  ocsp verify exists
  ocsp verify not exists
  ocsp verify revoked
  crl non-revoked cert
  FAIL test_chain (exit status: 1)

  
  Testsuite summary for Heimdal 7.5.0
  
  # TOTAL: 16
  # PASS:  15
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0
  
  See lib/hx509/test-suite.log
  Please report to https://github.com/heimdal/heimdal/issues

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


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

[Touch-packages] [Bug 1954311] [NEW] Daily cron job script unnecessarily executes `find` with `rm` instead of using its '-delete' action

2021-12-09 Thread Akbarkhon Variskhanov

Public bug reported:

Executing `rm` as a separate process each time for every single file is
unnecessary and inefficient. The option '-delete' should be used
instead.

Patch is included below.

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

** Patch added: "apport.patch"
   
https://bugs.launchpad.net/bugs/1954311/+attachment/5546501/+files/apport.patch

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

Title:
  Daily cron job script unnecessarily executes `find` with `rm` instead
  of using its '-delete' action

Status in apport package in Ubuntu:
  New

Bug description:
  Executing `rm` as a separate process each time for every single file
  is unnecessary and inefficient. The option '-delete' should be used
  instead.

  Patch is included below.

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


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

[Touch-packages] [Bug 1951667] Re: [SRU] pulseaudio: restore hdmi audio be active output after resume

2021-12-09 Thread Launchpad Bug Tracker

This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu3.13

---
pulseaudio (1:13.99.1-1ubuntu3.13) focal; urgency=medium

  * d/p/0001-card-restore-setting-preferred-ports-in-entry_from_c.patch
- cherry pick an upstream commit to fix the issue of hdmi can't be
  restored after s3 resume (LP: #1951667)

 -- Hui Wang   Sat, 20 Nov 2021 12:40:36 +0800

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

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

Title:
  [SRU] pulseaudio: restore hdmi audio be active output after resume

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in pulseaudio source package in Hirsute:
  Won't Fix
Status in pulseaudio source package in Impish:
  Fix Released
Status in pulseaudio source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  On the machines with legacy HDA audio driver, when users plug a hdmi/dp 
monitor, the active output device is still speaker, need users to manually 
select the hdmi, then the hdmi audio will be the users' preference, once it is 
plugged, it should become the active output automatically. But with the current 
PA, after reboot and suspend/resume, the hdmi can't change to be active output 
automatically anymore.

  [Fix]
  Backport an upstream fix, this will fix the issue of "preferred ports being 
cleaned by a mistake"

  [Test]
  On a machine with legacy HDA audio driver, install the patched pulseaudio, 
then run 'rm ~/.config/pulse/*; reboot', plug a hdmi monitor, select the hdmi 
audio to be active, with the hdmi monitor plugged and reboot, suspend and 
resume, check what is the active output, it is still the hdmi audio.

  [Where problems could occur]
  This patch is in the card-restore.c, if it could introduce regression, it 
will be on the default active input/output devices, for example, users select a 
input or output device to be active, after reboot, if those devices are 
available, they should be active, but they could be replaced by other devices 
if a regression is introduced. But this possibility is very low since we tested 
the patch on a couple of desktop and laptop machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1951667/+subscriptions


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

[Touch-packages] [Bug 1950484] Re: Adding an admin user a Gnome Control Center should set the right groups

2021-12-09 Thread Sebastien Bacher

** Changed in: accountsservice (Ubuntu)
   Status: New => Triaged

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

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Triaged

** Also affects: gnome-control-center (Ubuntu Jammy)
   Importance: High
   Status: Triaged

** Also affects: accountsservice (Ubuntu Jammy)
   Importance: High
   Status: Triaged

** No longer affects: accountsservice (Ubuntu)

** No longer affects: accountsservice (Ubuntu Jammy)

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

Title:
  Adding an admin user a Gnome Control Center should set the right
  groups

Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-control-center source package in Jammy:
  Triaged

Bug description:
  Currently when installing Ubuntu , the default admin belongs to
  several essential groups :

  adm cdrom sudo dip plugdev lpadmin lxd sambashare

  
  But when adding a user from GCC , the new admin user will only belong to : 

  
  sudo 

  
  This leads that the second admin cannot add printers and so on...

  This is observed on a clean 20.04.3 install

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


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

[Touch-packages] [Bug 1946621] Re: Crash in libegl-mesa0 (eglReleaseThread)

2021-12-09 Thread Sebastien Bacher

** Changed in: mesa (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: mesa (Ubuntu Impish)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Crash in libegl-mesa0 (eglReleaseThread)

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

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

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

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

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

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

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

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


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

79 matches

Mail list logo