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

[Daniel van Vugt]

Looks good. And it's now in git:

https://git.launchpad.net/~ubuntu-audio-dev/pulseaudio/log/?h=ubuntu-
focal

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

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

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

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

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

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

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

  

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

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

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

  Any help greatly appreciated.

  Regards,
  Roman

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

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

[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

[Kai-Heng Feng]

debdiff for Bionic.

** Patch added: "pulseaudio_11.1-1ubuntu7.8.debdiff"
   
https://bugs.launchpad.net/oem-priority/+bug/1869819/+attachment/5371296/+files/pulseaudio_11.1-1ubuntu7.8.debdiff

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

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

[Jared Young]

Actually I was able to make it work! I needed to remove

"options snd-hda-intel dmic_detect=0"

from /etc/modprobe.d/alsa-base.conf

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1877726] Re: [HDA-Intel - HD-Audio Generic, playback] USB sound with Rodecaster Pro not working

[nils]

It works out-of-the-box on a windows 10 machine (both as input and
output for MS teams, Skype, etc.) on which I have no admin access, so it
seems to work there without extra drivers.

https://www.sweetwater.com/sweetcare/articles/getting-started-with-the-rodecaster-pro/
claims that it is class compliant on a MAC at least: "Before you can use the 
Rodecaster Pro, you first need to download and install the Rodecaster Pro app, 
as well as the firmware. The Rodecaster Pro is considered class-compliant on 
Mac, which means it doesn’t need third-party audio drivers. PC users will need 
to download ASIO4All  for proper connectivity. Follow the 
steps below to get started."

On a Macbook Pro (15inch, 2011) with High Sierra 10.13.6 (won't run
Mojave) using Garageband it shows up as a RODECaster Pro Stereo, and
works (recording, playback) without a problem. I see two channels
(theoretically I should see 14 in a DAW I think?), but it works.

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

Title:
  [HDA-Intel - HD-Audio Generic, playback] USB sound with Rodecaster Pro
  not working

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Please see 
https://askubuntu.com/questions/1229085/ubuntu-with-rodecaster-pro-usb-soundcard/1236257#1236257
 for most background.
  tl;dr:
  - The Rodecaster Pro is a USB audio standard compliant device
  - lsusb sees it, but alsa cannot use it
  - trying the exact same setup with a Scarlett 2i2 USB device works (with some 
caveats, see the mentioned post)

  Somehow the Rodecaster is ignored by Alsa. I am more than happy to help debug.
  Alsa info is at 
http://alsa-project.org/db/?f=94fd609fa23912ab0a39b67676a026fd163f3f3b and also 
attached.

  nils@blackbox:~/tmp/soundtest$ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD 
Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: Generic_1 [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD 
Digital]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 2: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  nils@blackbox:~/tmp/soundtest$ arecord --list-devices
   List of CAPTURE Hardware Devices 
  card 0: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD 
Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: Generic_1 [HD-Audio Generic], device 2: ALC887-VD Alt Analog 
[ALC887-VD Alt Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 2: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio]
    Subdevices: 1/1
    Subdevice #0: subdevice #0

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  nils  90077 F pulseaudio
   /dev/snd/controlC0:  nils  90077 F pulseaudio
   /dev/snd/controlC1:  nils  90077 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sat May  9 11:45:20 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-23 (1354 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AudioUsers: pulse
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  nils  90077 F pulseaudio
   /dev/snd/controlC0:  nils  90077 F pulseaudio
   /dev/snd/controlC1:  nils  90077 F pulseaudio
  Symptom_Jack: SPDIF Out, Internal
  Symptom_Type: Sound works for some users but not for others
  Title: [HDA-Intel - HD-Audio Generic, playback] sound not working for all 
users
  UpgradeStatus: Upgraded to focal on 2020-05-09 (0 days ago)
  dmi.bios.date: 10/14/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5222
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5222:bd10/14/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  

[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

[Jared Young]

This does not work for me. My Hardware Devices were listed as follows

 List of CAPTURE Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0


Added to line to /etc/modprobe.d/alsa-base.conf and my internal microphone did 
not work.

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1878527] Re: "Dummy Output" as Audio Device in Ubuntu settings - Ubuntu 20.04.

[Daniel van Vugt]

Thanks for the bug report. It appears you have jackd installed, which is
not a normal part of Ubuntu and might steal the sound devices before
pulseaudio starts. Please uninstall jackd, restart, and tell us if the
problem persists.

Also if you have 'timidity' installed please remove that too.


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

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

Title:
  "Dummy Output" as Audio Device in Ubuntu settings  -  Ubuntu 20.04.

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hi All

 As soon as i boot to OS, my sound device is shown as "Dummy
  Output".

  i wait for 10 to 15 minutes and run below commands and then, it kills
  few processes and sound starts working. I have to do this step every
  time system is rebooted.

  # pulseaudio --kill; sleep 2s; sudo alsa force-reload ; pulseaudio
  --start

  
  Thanks.
  RD

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-7625.27~1576774585~18.04~c7868f8-generic 
5.3.13
  Uname: Linux 5.3.0-7625-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 09:39:15 2020
  InstallationDate: Installed on 2018-07-12 (671 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-04-28 (15 days ago)
  dmi.bios.date: 12/04/2018
  dmi.bios.vendor: System76
  dmi.bios.version: 1.07.11RSA4-1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp4
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnSystem76:bvr1.07.11RSA4-1:bd12/04/2018:svnSystem76:pnOryxPro:pvroryp4:rvnSystem76:rnOryxPro:rvroryp4:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: oryp4
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878527/+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 1878527] [NEW] "Dummy Output" as Audio Device in Ubuntu settings - Ubuntu 20.04.

[RD]

Public bug reported:

Hi All

   As soon as i boot to OS, my sound device is shown as "Dummy Output".

i wait for 10 to 15 minutes and run below commands and then, it kills
few processes and sound starts working. I have to do this step every
time system is rebooted.

# pulseaudio --kill; sleep 2s; sudo alsa force-reload ; pulseaudio
--start


Thanks.
RD

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.2
ProcVersionSignature: Ubuntu 5.3.0-7625.27~1576774585~18.04~c7868f8-generic 
5.3.13
Uname: Linux 5.3.0-7625-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu May 14 09:39:15 2020
InstallationDate: Installed on 2018-07-12 (671 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to focal on 2020-04-28 (15 days ago)
dmi.bios.date: 12/04/2018
dmi.bios.vendor: System76
dmi.bios.version: 1.07.11RSA4-1
dmi.board.asset.tag: Tag 12345
dmi.board.name: Oryx Pro
dmi.board.vendor: System76
dmi.board.version: oryp4
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnSystem76:bvr1.07.11RSA4-1:bd12/04/2018:svnSystem76:pnOryxPro:pvroryp4:rvnSystem76:rnOryxPro:rvroryp4:cvnSystem76:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: Oryx Pro
dmi.product.sku: Not Applicable
dmi.product.version: oryp4
dmi.sys.vendor: System76

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


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

** Attachment added: "Dummy Output"
   
https://bugs.launchpad.net/bugs/1878527/+attachment/5371251/+files/DeepinScreenshot_select-area_20200514094507.png

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

Title:
  "Dummy Output" as Audio Device in Ubuntu settings  -  Ubuntu 20.04.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hi All

 As soon as i boot to OS, my sound device is shown as "Dummy
  Output".

  i wait for 10 to 15 minutes and run below commands and then, it kills
  few processes and sound starts working. I have to do this step every
  time system is rebooted.

  # pulseaudio --kill; sleep 2s; sudo alsa force-reload ; pulseaudio
  --start

  
  Thanks.
  RD

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-7625.27~1576774585~18.04~c7868f8-generic 
5.3.13
  Uname: Linux 5.3.0-7625-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 09:39:15 2020
  InstallationDate: Installed on 2018-07-12 (671 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-04-28 (15 days ago)
  dmi.bios.date: 12/04/2018
  dmi.bios.vendor: System76
  dmi.bios.version: 1.07.11RSA4-1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp4
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnSystem76:bvr1.07.11RSA4-1:bd12/04/2018:svnSystem76:pnOryxPro:pvroryp4:rvnSystem76:rnOryxPro:rvroryp4:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: oryp4
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878527/+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 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

[Khaled El Mously]

** Changed in: linux (Ubuntu Focal)
   Status: Confirmed => Fix Committed

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-riscv package in Ubuntu:
  Invalid
Status in rtkit package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Committed
Status in linux-azure source package in Focal:
  New
Status in linux-gcp source package in Focal:
  New
Status in linux-kvm source package in Focal:
  New
Status in linux-oracle source package in Focal:
  New
Status in linux-riscv source package in Focal:
  New
Status in rtkit source package in Focal:
  Confirmed

Bug description:
  SRU Justification

  Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the
  lowlatency kernel since we expected most RT users to use that kernel.
  However we are getting RT regressions with the generic kernel. Digging
  deeper into this option, it seems to be pretty specialized and to
  require quite a bit of workload-specific configuration/tuning to be
  useful, so it doesn't really seem to make sense for a general-purpose
  kernel.

  Fix: Turn this option back off.

  Test Case: See comment #4.

  Regression Potential: This was turned on to support some docker
  functionality, so this functionality will no longer be available.
  We've had this option off for all releases prior to focal, so this
  seems acceptable.

  ---

  These errors started right after upgrading to 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 10:31:43 2020
  InstallationDate: Installed on 2019-06-18 (315 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago)

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

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

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

[Kai-Heng Feng]

** Patch added: "pulseaudio_13.99.1-1ubuntu3.3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+attachment/5371249/+files/pulseaudio_13.99.1-1ubuntu3.3.debdiff

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

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

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

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

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

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

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

  

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

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

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

  Any help greatly appreciated.

  Regards,
  Roman

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

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

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

[Kai-Heng Feng]

Daniel, please review this debdiff, thanks!

** Patch added: "pulseaudio_13.99.1-1ubuntu3.3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+attachment/5371250/+files/pulseaudio_13.99.1-1ubuntu3.3.debdiff

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

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

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

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

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

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

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

  

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

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

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

  Any help greatly appreciated.

  Regards,
  Roman

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

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

[Touch-packages] [Bug 1871543] Re: rtkit fails to start in focal "pthread_create failed: Resource temporarily unavailable"

[RussianNeuroMancer]

> Do you have other things than the kernel from outside the Ubuntu
Archive?

Not much, just two packages:

uboot bootloader: 
https://apt.armbian.com/pool/main/l/linux-u-boot-nanopct4-current/linux-u-boot-current-nanopct4_20.02.7_arm64.deb
board-specific configs and various tools, such as monitoring tool, installer, 
etc.: 
https://apt.armbian.com/pool/main/l/linux-focal-root-current-nanopct4/linux-focal-root-current-nanopct4_20.02.7_arm64.deb
 (take a peek inside to get idea).

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

Title:
  rtkit fails to start in focal "pthread_create failed: Resource
  temporarily unavailable"

Status in rtkit package in Ubuntu:
  Confirmed

Bug description:
  I was debugging something else and found rtkit broken on my system.

  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully called 
chroot.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully dropped 
privileges.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully limited 
resources.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Canary thread running.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Exiting canary thread.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoting known real-time 
threads.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoted 0 threads

  That state is reproducible through restarts.
  I haven't looked any further yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  8 07:59:58 2020
  InstallationDate: Installed on 2018-10-12 (543 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-03 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1871543/+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 1871543] Re: rtkit fails to start in focal "pthread_create failed: Resource temporarily unavailable"

[RussianNeuroMancer]

Out of curiosity I tried to reproduce this on other SBC - NanoPi-M1
which also running Armbian. Interestingly, it's not reproducible on this
board.

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

Title:
  rtkit fails to start in focal "pthread_create failed: Resource
  temporarily unavailable"

Status in rtkit package in Ubuntu:
  Confirmed

Bug description:
  I was debugging something else and found rtkit broken on my system.

  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully called 
chroot.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully dropped 
privileges.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully limited 
resources.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Canary thread running.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Exiting canary thread.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoting known real-time 
threads.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoted 0 threads

  That state is reproducible through restarts.
  I haven't looked any further yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  8 07:59:58 2020
  InstallationDate: Installed on 2018-10-12 (543 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-03 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1871543/+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 1878519] [NEW] Unable to use TLSv1.1 to connect to external servers

[Gordon Lack]

Public bug reported:

I'm on 20.04 LTS (Focal Fossa). (Kubuntu)

openssl (I'm on 1.1.1f-1ubuntu2) appears to now be set to use a minimum
of TLSv1.2

This is despite the fact that the Changelog 
(https://launchpad.net/ubuntu/+source/openssl/+changelog) says:
  Revert "Enable system default config to enforce TLS1.2 as a
  minimum" & "Increase default security level from 1 to 2".

As a result of this I can't get fetchmail to connect to an external IMPA
server I use, which only uses TLSv1.1

I *can* get:
  openssl s_client -state -cipher "DEFAULT:@SECLEVEL=1" -connect ... -starttls 
imap
to open a connexion, but I can find no way of getting that option into a 
configuration file such that it is used.

Consequently I cannot use a secure connexion to retrieve my emails.

All was fine in 19.10.

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

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

Title:
  Unable to use TLSv1.1 to connect to external servers

Status in openssl package in Ubuntu:
  New

Bug description:
  I'm on 20.04 LTS (Focal Fossa). (Kubuntu)

  openssl (I'm on 1.1.1f-1ubuntu2) appears to now be set to use a
  minimum of TLSv1.2

  This is despite the fact that the Changelog 
(https://launchpad.net/ubuntu/+source/openssl/+changelog) says:
Revert "Enable system default config to enforce TLS1.2 as a
minimum" & "Increase default security level from 1 to 2".

  As a result of this I can't get fetchmail to connect to an external
  IMPA server I use, which only uses TLSv1.1

  I *can* get:
openssl s_client -state -cipher "DEFAULT:@SECLEVEL=1" -connect ... 
-starttls imap
  to open a connexion, but I can find no way of getting that option into a 
configuration file such that it is used.

  Consequently I cannot use a secure connexion to retrieve my emails.

  All was fine in 19.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1878519/+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 1878469] Re: Ubuntu 20.04 causing green vertical stripes on my desktop

[Daniel van Vugt]

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

Title:
  Ubuntu 20.04 causing green vertical stripes on my desktop

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  As soon as I upgraded to Ubuntu 20.04, two green pixel stripes appeared on my 
desktop.
  They do not interfere with windows when opened, whether they are browsers, 
files or other items, and they do not seem to have an impact on the general 
behavior of the PC.

  Still, something tells me that they are not supposed to be there.

  I have a dual boot, Windows and Ubuntu, and two drivers:

  VGA compatbile controller: Intel UHD Graphics 630 (mobile)
  3D controller: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] 

  Any support would be welcome.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-31.35-lowlatency 5.4.34
  Uname: Linux 5.4.0-31-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 13 18:55:14 2020
  DistUpgraded: 2020-05-13 13:02:22,581 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c]
  InstallationDate: Installed on 2018-12-23 (506 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications 
   Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-lowlatency 
root=UUID=d49b534b-1745-4089-80d9-cb11f85d2570 ro acpi=force 
nvidia.NVreg_EnableBacklightHandler=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-05-13 (0 days ago)
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1878469/+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 1877528] Re: Applet does not terminate at end of X desktop session

[Bug Watch Updater]

** Changed in: system-config-printer (Debian)
   Status: Unknown => New

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

Title:
  Applet does not terminate at end of X desktop session

Status in System Config Printer:
  Fix Released
Status in lightdm package in Ubuntu:
  New
Status in sddm package in Ubuntu:
  New
Status in system-config-printer package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Invalid
Status in system-config-printer package in Debian:
  New

Bug description:
  This concerns system-config-printer 1.5.12-0ubuntu1 in Ubuntu focal.

  I log into the Xfce desktop, and then logout. The screen returns to
  the LightDM login screen.

  A few minutes later, "loginctl list-sessions" shows the following:

  SESSION  UID USERSEAT  TTY  
90 root   
   c2 1000 skunk   seat0  
   c3  116 lightdm seat0  

  3 sessions listed.

  Output from "loginctl session-status c2":

  c2 - skunk (1000)
 Since: Fri 2020-05-08 03:09:05 EDT; 9min ago
Leader: 2530
  Seat: seat0; vc7
   Display: :0
   Service: lightdm; type x11; class user
   Desktop: xubuntu
 State: closing
  Unit: session-c2.scope
└─2856 /usr/bin/python3 
/usr/share/system-config-printer/applet.py

  This process sticks around forever until I kill it, or its parent
  "systemd --user" process. Only then does the session disappear from
  list-sessions.

  When I run "session-status" while I'm logged in, I see a list of
  nearly 30 desktop-related processes. All of them except this one go
  away on logout. This one should too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/system-config-printer/+bug/1877528/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

[Han.xue-shan]

I fix it on ubuntu 19.10, maybe work on ubuntu 20.04

FIRST: do

arecord -l 
maybe gives:

 List of CAPTURE Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC3254 Analog [ALC3254 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

NOTE: Subdevices: 1/1, remember it!

SECOND:
add 
options snd-hda-intel index=X model=laptop-dmic 
to /etc/modprobe.d/alsa-base.conf

NOTE:
if Subdevices: 1/1, index=1
if Subdevices: 0/1, index=0

after update alsa-base.conf, reboot!

try it!

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1878421] Re: (If external monitor connected) Hang on boot while showing ubuntu boot screen with animation

[Daniel van Vugt]

This sounds like bug 1872159...

Please try editing /etc/default/grub and remove the word "splash". Then
run:

  sudo update-grub

and reboot. Now can you boot with the monitor connected?


** Summary changed:

- 20.4 - hybrid-graphics
+ (If external monitor connected) Hang on boot while showing ubuntu boot screen 
with animation

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

** Tags added: multimonitor

** Tags removed: multimonitor
** Tags added: mulimonitor

** Changed in: plymouth (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/1878421

Title:
  (If external monitor connected) Hang on boot while showing ubuntu boot
  screen with animation

Status in plymouth package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  i try to use external monitor on my dell G5 2019 (5590). works on
  ubuntu 18.4 (after reboot) using prime-select nvidia.

  did this on 20.4 (prime-select + reboot because logoff/login again
  still don't work) and it hang on boot while showing ubuntu bootscreen
  with animation (not stopped, but also response to esc-key to show
  terminal-output) on the monitor (need to switch off). booted again
  where monitor is configured to other input, boot works, i see it in
  preferences dialog as second monitor, but if i configure input on
  monitor i have no signal..

  
  anything i can try?

  regards Frank

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed May 13 15:21:08 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:08ea]
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:08ea]
  InstallationDate: Installed on 2020-04-27 (16 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. G5 5590
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/07/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 0KW84T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G5 5590
  dmi.product.sku: 08EA
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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/plymouth/+bug/1878421/+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 1878517] [NEW] please apply bash 5.0 patch 17

[Kir Kolyshkin]

Public bug reported:

I am using Ubuntu 20.04 for development and has hit a bug in bash 5.0
patch 16.

I can't reproduce it in pure bash, but with bats from https://github.com
/bats-core/bats-core/ it is very easy to repro:

```
# cat << EOF > ya.bats
check() {
echo "check $@"
ls -l /proc/self/fd
}

@test "here file" {
check -p <(echo "hey")
false
}
EOF

$ bats ya.bats
```

Normally the output should contain the line

   lr-x-- 1 kir kir 64 May 14 02:01 63 -> pipe:[4616918]

which is a result of a "here file" created by bash via <(echo "hey").

In my testing, about 50% of runs don't have /dev/fd/63 listed.

I found out this is a manifest of a bug introduced in bash 5.0 patch 16
(see http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-016)

The bug is fixed in 5.0 patch 17 (see
http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-017).

Please update bash to patchlevel 17.

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

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

Title:
  please apply bash 5.0 patch 17

Status in bash package in Ubuntu:
  New

Bug description:
  I am using Ubuntu 20.04 for development and has hit a bug in bash 5.0
  patch 16.

  I can't reproduce it in pure bash, but with bats from
  https://github.com/bats-core/bats-core/ it is very easy to repro:

  ```
  # cat << EOF > ya.bats
  check() {
echo "check $@"
ls -l /proc/self/fd
  }

  @test "here file" {
check -p <(echo "hey")
false
  }
  EOF

  $ bats ya.bats
  ```

  Normally the output should contain the line

 lr-x-- 1 kir kir 64 May 14 02:01 63 -> pipe:[4616918]

  which is a result of a "here file" created by bash via <(echo "hey").

  In my testing, about 50% of runs don't have /dev/fd/63 listed.

  I found out this is a manifest of a bug introduced in bash 5.0 patch
  16 (see http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-016)

  The bug is fixed in 5.0 patch 17 (see
  http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-017).

  Please update bash to patchlevel 17.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1878517/+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 1878517] Re: please apply bash 5.0 patch 17

[Kir Kolyshkin]

Here is a repro that does not involve bats:

https://lists.gnu.org/archive/html/bug-bash/2020-03/msg00062.html

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

Title:
  please apply bash 5.0 patch 17

Status in bash package in Ubuntu:
  New

Bug description:
  I am using Ubuntu 20.04 for development and has hit a bug in bash 5.0
  patch 16.

  I can't reproduce it in pure bash, but with bats from
  https://github.com/bats-core/bats-core/ it is very easy to repro:

  ```
  # cat << EOF > ya.bats
  check() {
echo "check $@"
ls -l /proc/self/fd
  }

  @test "here file" {
check -p <(echo "hey")
false
  }
  EOF

  $ bats ya.bats
  ```

  Normally the output should contain the line

 lr-x-- 1 kir kir 64 May 14 02:01 63 -> pipe:[4616918]

  which is a result of a "here file" created by bash via <(echo "hey").

  In my testing, about 50% of runs don't have /dev/fd/63 listed.

  I found out this is a manifest of a bug introduced in bash 5.0 patch
  16 (see http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-016)

  The bug is fixed in 5.0 patch 17 (see
  http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-017).

  Please update bash to patchlevel 17.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1878517/+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 1774843] Re: apport python exception for python versions which python-apt is not built on

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.11-0ubuntu34

---
apport (2.20.11-0ubuntu34) groovy; urgency=medium

  * apport_python_hook.py: if python apt modules are not built for the python
version then do capture the crash. (LP: #1774843)

 -- Brian Murray   Wed, 13 May 2020 16:17:11 -0700

** Changed in: apport (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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1774843

Title:
  apport python exception for python versions which python-apt is not
  built on

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in python3.7 package in Ubuntu:
  Invalid
Status in python3.8 package in Ubuntu:
  Invalid
Status in apport source package in Bionic:
  In Progress
Status in python3.7 source package in Bionic:
  Won't Fix
Status in python3.8 source package in Bionic:
  Won't Fix
Status in apport source package in Eoan:
  In Progress
Status in python3.7 source package in Eoan:
  Won't Fix
Status in python3.8 source package in Eoan:
  Won't Fix
Status in apport source package in Focal:
  Invalid
Status in python3.7 source package in Focal:
  Invalid
Status in python3.8 source package in Focal:
  Invalid

Bug description:
  [Impact]
  apport's python crash handler runs for every installed version of python e.g. 
on Ubuntu 18.04 LTS it will run for crashes with python3.6 or python3.7 as an 
interpreter. However, python apt modules are only available for the the 
supported version of python so the crash handler generates an exception which 
is annoying.

  [Test Case]
  1) Install the non-default version of python3 e.g. python3.7 on Ubuntu 18.04 
LTS.
  2) Run 'python3.7 -c 'print hello' and observe a Traceback re apt_pkg not 
being found.

  With the version of python3-apport from -proposed you'll not receive
  the Traceback from step # 2.

  [Regression Potential]
  Its possible the crash handler change is incorrect so it should be confirmed 
that we still get python crashes about the system version of python. One way to 
do this is to run 'apport-cli coreutils < /dev/null'.

  [NOTE]
  It isn't necessary to fix this in Ubuntu 20.04 LTS, as there is only 
python3.8 available, so I haven't.

  [Original Description]
  it seems apport installs an exception hook whenever running python3.
  This hook is apparently installed for python3.7 too.
  This exception handler has a dependency on apt_pkg, which is a binary that is 
not compatible with python3.7 it seems (you can't import it, see below)

  As a result, whenever I run a python3.7 script and run into an exception 
(which happens often when writing code), I get an additional exception in the 
exception handler + a copy of the original exception, so three stacktraces in 
total.
  A solution would be to only install the exception hook for the system python  
i.e. python3.6

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

  apport: 2.20.9-0ubuntu7
  python-apt: 1.6.0
  python3.7: 3.7.0~b3-1

  Demo with a trivial error:
  $ python3 -c 'print hello'
    File "", line 1
  print hello
    ^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?

  $ python3.7 -c 'print hello'
    File "", line 1
  print hello
    ^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?
  Error in sys.excepthook:
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in 
apport_excepthook
  from apport.fileutils import likely_packaged, get_recent_crashes
    File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in 

  from apport.report import Report
    File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in 
  import apport.fileutils
    File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in 

  from apport.packaging_impl import impl as packaging
    File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in 

  import apt
    File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in 
  import apt_pkg
  ModuleNotFoundError: No module named 'apt_pkg'

  Original exception was:
    File "", line 1
  print hello
    ^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?

  Python 3.6.5 (default, Apr  1 2018, 05:46:30)
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  >>> import apt_pkg
  >>> apt_pkg.__file__
  '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so'
  >>>

  Python 3.7.0b3 (default, Mar 30 2018, 04:35:22)
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  >> import ap

[Touch-packages] [Bug 1878177] Re: CVE-2020-3810 out-of-bound stack reads in arfile

[Alex Murray]

** Information type changed from Private Security to Public Security

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

Title:
  CVE-2020-3810 out-of-bound stack reads in arfile

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  In https://github.com/Debian/apt/issues/111, an issue was discovered
  where apt's ar implementation performs (unbound) out of bound reads of
  a stack variable.

  Marking this as private security for now to avoid giving it more
  prominence.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1878177/+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 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem

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

Title:
  [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left]
  Recording problem

Status in HWE Next:
  New
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy
  output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa-
  base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that
  now "snd-hda-intel" is loaded instead of sof-audio-pci. While the
  speakers are working fine, I do not have the internal microphone
  working (suspect a digital array).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wittawat   2063 F pulseaudio
   /dev/snd/controlC0:  wittawat   2063 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 12:42:32 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Mic, Left
  Symptom_Type: None of the above
  Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] 
Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8600
  dmi.board.vendor: HP
  dmi.board.version: 44.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dh0xxx
  dmi.product.sku: 7JX54EA#ABD
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1874698/+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 1878333] Re: AppArmor cache entries not removed when profile is deleted

[Daniel Richard G.]

That's why I hedged on having something like "apparmor unload". What
you're saying explains why "restart" and "reload" are distinct actions
(I'd never been clear on this), so having a new action that is "like
'stop' but actually does stop apparmor, even though that is not usually
what you want" makes similar sense.

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

Title:
  AppArmor cache entries not removed when profile is deleted

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  This concerns apparmor 2.13.3-7ubuntu5 in Ubuntu focal.

  If I delete a profile from /etc/apparmor.d/, reboot the system, and
  then look in /var/cache/apparmor/.0/, I still see a file for
  the compiled form of the profile.

  The same occurs if the profile is "deleted" by other means, such as
  symlinking it from /etc/apparmor.d/disable/.

  This behavior caused me some consternation as I was developing an
  alternate profile for a program that already had one, and I continued
  to see old behavior even though I had removed the old profile.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1878333/+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 1878333] Re: AppArmor cache entries not removed when profile is deleted

[John Johansen]

/etc/init.d/apparmor stop cannot and should not invoke aa-teardown. Such
a stop mechanism was the source of many problems and the reason stop was
switch to a no-opin /etc/init.d/apparmor and teardown was added.

Unfortunately systemd implements restart as stop followed by start. This
a very poor fit for apparmor as once the security state is torn down you
have to restart all services or in some cases the entire system.

Admittedly the current situation is less than ideal, there are WI
scheduled to help better address this but atm the stop behavior is
deliberate as on a whole it causes less problems than using teardown.

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

Title:
  AppArmor cache entries not removed when profile is deleted

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  This concerns apparmor 2.13.3-7ubuntu5 in Ubuntu focal.

  If I delete a profile from /etc/apparmor.d/, reboot the system, and
  then look in /var/cache/apparmor/.0/, I still see a file for
  the compiled form of the profile.

  The same occurs if the profile is "deleted" by other means, such as
  symlinking it from /etc/apparmor.d/disable/.

  This behavior caused me some consternation as I was developing an
  alternate profile for a program that already had one, and I continued
  to see old behavior even though I had removed the old profile.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1878333/+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 1878312] Re: Sound input is not automatically switched back from headphones mic to internal microphone

[Hui Wang]

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

This is a duplicate bug of this one：
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065

** This bug has been marked a duplicate of bug 1876065
   After unplug headphones and plug them again no sound can be heard

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

Title:
  Sound input is not automatically switched back from headphones mic to
  internal microphone

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When plugging in headphones, sound input is correctly switched from
  internal microphone to the headphones mic. When the headphones are
  unplugged, sound input is NOT automatically switched back to the
  internal microphone.

  Sound output is switched back and forth correctly.

  This bug started happening on my system after I upgraded from 19.10 to 20.04 
so it is a regression. Attached is pulseaudio log of what happens when I plug 
and unplug my headphones.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anderson   2247 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-08-24 (263 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-25 (17 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/06/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 0W83FH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd01/06/2020:svnDellInc.:pnInspiron7580:pvr:rvnDellInc.:rn0W83FH:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7580
  dmi.product.sku: 08A6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878312/+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 1878312] Re: Sound input is not automatically switched back from headphones mic to internal microphone

[Hui Wang]

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

Please use the testing ppa in the #1876065 and verify if it could fix
the problem.

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

Title:
  Sound input is not automatically switched back from headphones mic to
  internal microphone

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When plugging in headphones, sound input is correctly switched from
  internal microphone to the headphones mic. When the headphones are
  unplugged, sound input is NOT automatically switched back to the
  internal microphone.

  Sound output is switched back and forth correctly.

  This bug started happening on my system after I upgraded from 19.10 to 20.04 
so it is a regression. Attached is pulseaudio log of what happens when I plug 
and unplug my headphones.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anderson   2247 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-08-24 (263 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-25 (17 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/06/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 0W83FH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd01/06/2020:svnDellInc.:pnInspiron7580:pvr:rvnDellInc.:rn0W83FH:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7580
  dmi.product.sku: 08A6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878312/+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 1862080] Re: [MS-7B51, Nvidia GPU 94 HDMI/DP, Digital Out, HDMI] No sound at all

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

Title:
  [MS-7B51, Nvidia GPU 94 HDMI/DP, Digital Out, HDMI] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  If I use xserver-xorg-video-nouveau/focal,now 1:1.0.16-1 amd64
  there is no sound on Display port.
  My graphic card is GTX 1650. 

  Please see bug 1859096. It work with 440 nvidia driver 
  but I want to use Nouveau driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Feb  5 23:50:39 2020
  InstallationDate: Installed on 2020-01-05 (31 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200104)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: HDA NVidia - HDA NVidia
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [MS-7B51, Nvidia GPU 94 HDMI/DP, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Default string
  dmi.board.name: MPG Z390 GAMING PLUS (MS-7B51)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.50:bd02/21/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B51:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ390GAMINGPLUS(MS-7B51):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7B51
  dmi.product.sku: Default string
  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/1862080/+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 1774843] Re: apport python exception for python versions which python-apt is not built on

[Brian Murray]

** Description changed:

+ [Impact]
+ apport's python crash handler runs for every installed version of python e.g. 
on Ubuntu 18.04 LTS it will run for crashes with python3.6 or python3.7 as an 
interpreter. However, python apt modules are only available for the the 
supported version of python so the crash handler generates an exception which 
is annoying.
+ 
+ [Test Case]
+ 1) Install the non-default version of python3 e.g. python3.7 on Ubuntu 18.04 
LTS.
+ 2) Run 'python3.7 -c 'print hello' and observe a Traceback re apt_pkg not 
being found.
+ 
+ With the version of python3-apport from -proposed you'll not receive the
+ Traceback from step # 2.
+ 
+ [Regression Potential]
+ Its possible the crash handler change is incorrect so it should be confirmed 
that we still get python crashes about the system version of python. One way to 
do this is to run 'apport-cli coreutils < /dev/null'.
+ 
+ [NOTE]
+ It isn't necessary to fix this in Ubuntu 20.04 LTS, as there is only 
python3.8 available, so I haven't.
+ 
+ [Original Description]
  it seems apport installs an exception hook whenever running python3.
  This hook is apparently installed for python3.7 too.
  This exception handler has a dependency on apt_pkg, which is a binary that is 
not compatible with python3.7 it seems (you can't import it, see below)
  
  As a result, whenever I run a python3.7 script and run into an exception 
(which happens often when writing code), I get an additional exception in the 
exception handler + a copy of the original exception, so three stacktraces in 
total.
  A solution would be to only install the exception hook for the system python  
i.e. python3.6
- 
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  
  apport: 2.20.9-0ubuntu7
  python-apt: 1.6.0
  python3.7: 3.7.0~b3-1
  
  Demo with a trivial error:
  $ python3 -c 'print hello'
-   File "", line 1
- print hello
-   ^
+   File "", line 1
+ print hello
+   ^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?
  
- 
  $ python3.7 -c 'print hello'
-   File "", line 1
- print hello
-   ^
+   File "", line 1
+ print hello
+   ^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?
  Error in sys.excepthook:
  Traceback (most recent call last):
-   File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in 
apport_excepthook
- from apport.fileutils import likely_packaged, get_recent_crashes
-   File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in 

- from apport.report import Report
-   File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in 
- import apport.fileutils
-   File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in 

- from apport.packaging_impl import impl as packaging
-   File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in 

- import apt
-   File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in 
- import apt_pkg
+   File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in 
apport_excepthook
+ from apport.fileutils import likely_packaged, get_recent_crashes
+   File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in 

+ from apport.report import Report
+   File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in 
+ import apport.fileutils
+   File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in 

+ from apport.packaging_impl import impl as packaging
+   File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in 

+ import apt
+   File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in 
+ import apt_pkg
  ModuleNotFoundError: No module named 'apt_pkg'
  
  Original exception was:
-   File "", line 1
- print hello
-   ^
+   File "", line 1
+ print hello
+   ^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?
  
- 
- Python 3.6.5 (default, Apr  1 2018, 05:46:30) 
+ Python 3.6.5 (default, Apr  1 2018, 05:46:30)
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  >>> import apt_pkg
  >>> apt_pkg.__file__
  '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so'
- >>> 
+ >>>
  
- Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) 
+ Python 3.7.0b3 (default, Mar 30 2018, 04:35:22)
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  >> import apt_pkg
  Traceback (most recent call last):
-   File "", line 1, in 
+   File "", line 1, in 
  ModuleNotFoundError: No module named 'apt_pkg'

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

[Touch-packages] [Bug 1878333] Re: AppArmor cache entries not removed when profile is deleted

[Daniel Richard G.]

A related issue: "/etc/init.d/apparmor stop" should invoke aa-
teardown(8). Depending on the semantics of the apparmor "service," this
could also be "/etc/init.d/apparmor unload" or the like. I was surprised
to find that "apparmor stop" was not actually unloading the profiles, as
I had assumed.

>From the perspective of a sysadmin, I rely on the init scripts to manage
daemons/services without having to know the specific technical details
of how to interact with each one. A major reason why those scripts exist
is to translate a simple start/stop logic into whatever that reasonably
means for a particular daemon or service.

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

Title:
  AppArmor cache entries not removed when profile is deleted

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  This concerns apparmor 2.13.3-7ubuntu5 in Ubuntu focal.

  If I delete a profile from /etc/apparmor.d/, reboot the system, and
  then look in /var/cache/apparmor/.0/, I still see a file for
  the compiled form of the profile.

  The same occurs if the profile is "deleted" by other means, such as
  symlinking it from /etc/apparmor.d/disable/.

  This behavior caused me some consternation as I was developing an
  alternate profile for a program that already had one, and I continued
  to see old behavior even though I had removed the old profile.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1878333/+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 1774843] Re: apport python exception for python versions which python-apt is not built on

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-core-dev/ubuntu/groovy/apport/ubuntu

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

Title:
  apport python exception for python versions which python-apt is not
  built on

Status in Apport:
  New
Status in apport package in Ubuntu:
  In Progress
Status in python3.7 package in Ubuntu:
  Invalid
Status in python3.8 package in Ubuntu:
  Invalid
Status in apport source package in Bionic:
  In Progress
Status in python3.7 source package in Bionic:
  Won't Fix
Status in python3.8 source package in Bionic:
  Won't Fix
Status in apport source package in Eoan:
  In Progress
Status in python3.7 source package in Eoan:
  Won't Fix
Status in python3.8 source package in Eoan:
  Won't Fix
Status in apport source package in Focal:
  Invalid
Status in python3.7 source package in Focal:
  Invalid
Status in python3.8 source package in Focal:
  Invalid

Bug description:
  it seems apport installs an exception hook whenever running python3.
  This hook is apparently installed for python3.7 too.
  This exception handler has a dependency on apt_pkg, which is a binary that is 
not compatible with python3.7 it seems (you can't import it, see below)

  As a result, whenever I run a python3.7 script and run into an exception 
(which happens often when writing code), I get an additional exception in the 
exception handler + a copy of the original exception, so three stacktraces in 
total.
  A solution would be to only install the exception hook for the system python  
i.e. python3.6

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

  apport: 2.20.9-0ubuntu7
  python-apt: 1.6.0
  python3.7: 3.7.0~b3-1

  Demo with a trivial error:
  $ python3 -c 'print hello'
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?

  
  $ python3.7 -c 'print hello'
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in 
apport_excepthook
  from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in 

  from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in 
  import apport.fileutils
File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in 

  from apport.packaging_impl import impl as packaging
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in 

  import apt
File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in 
  import apt_pkg
  ModuleNotFoundError: No module named 'apt_pkg'

  Original exception was:
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?


  Python 3.6.5 (default, Apr  1 2018, 05:46:30) 
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  >>> import apt_pkg
  >>> apt_pkg.__file__
  '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so'
  >>> 

  Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) 
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  >> import apt_pkg
  Traceback (most recent call last):
File "", line 1, in 
  ModuleNotFoundError: No module named 'apt_pkg'

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1774843/+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 1875493] Re: [core] log rotation doesn't properly restart rsyslogd

[Tony Espy]

@ogra This is a bug in the core[16] snap. I'm not sure why we'd even
consider SRU'ing to UC18 or UC20. On both of the those systems, core
wouldn't be the booting snap, so any fix would be a no-op.

Possible ways to fix include:

 - releasing an rsyslog SRU for 16.04, but as Michael points out this
could impact classic

OR

 - patch rsyslog in the core snap to do the right thing

I'll spend more time on this as soon as I have some more cycles and will
try to determine the exact cause of the restart failure.

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

Title:
  [core] log rotation doesn't properly restart rsyslogd

Status in Snappy:
  New
Status in rsyslog package in Ubuntu:
  New

Bug description:
  One of our commercial partners is developing a device agent snap for
  UC16. One of their engineers just shared the following bug report:

  I wanted to give you a heads up on an issue that we encountered with
  one of our gateways (a Dell 3000) regarding a full disk (/writable).
  It seems as though rsyslog had a bad logrotate config and was holding
  on to deleted files as described here:

   - 
https://www.claudiokuenzler.com/blog/861/after-ubuntu-update-trusty-xenial-disk-filled-syslog-logrotate
   - https://bugzilla.redhat.com/show_bug.cgi?id=1713358

  Both df and du where showing different results for the “/writable”
  path on the Dell gateway.

  We were able to copy the lsof binary over and found this:

  $ sudo /tmp/lsof | grep deleted
  ...
  rsyslogd 1765 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted)
  rsyslogd 1765 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted)
  rsyslogd 1765 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted)
  in:imuxso 1765 1776 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog 
(deleted)
  in:imuxso 1765 1776 syslog 6w REG 179,4 45056 130836 /var/log/auth.log 
(deleted)
  in:imuxso 1765 1776 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log 
(deleted)
  in:imklog 1765 1777 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog 
(deleted)
  in:imklog 1765 1777 syslog 6w REG 179,4 45056 130836 /var/log/auth.log 
(deleted)
  in:imklog 1765 1777 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log 
(deleted)
  rs:main 1765 1778 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog 
(deleted)
  rs:main 1765 1778 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted)
  rs:main 1765 1778 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log 
(deleted)
  ...

  Restarting the service freed up the deleted files / disk space:

  sudo service rsyslog restart

  The rsyslog config (/etc/logrotate.d/rsyslog) calls this script post
  rotate:

  /usr/lib/rsyslog/rsyslog-rotate

  Which does not actually kill the rsyslog process:

  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2305 0.7 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n
  admin 2464 0.0 0.0 12984 932 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog
  admin@GR0GP42:~$ sudo /usr/lib/rsyslog/rsyslog-rotate
  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n
  admin 2469 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog

  The fix appears to be using the following command: sudo systemctl
  restart rsyslog >/dev/null 2>&1 || true

  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n
  admin 2482 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog
  admin@GR0GP42:~$ sudo systemctl restart rsyslog >/dev/null 2>&1 || true
  admin@GR0GP42:~$ ps aux | grep rsyslog
  syslog 2487 1.0 0.1 262692 3432 ? Ssl 20:36 0:00 /usr/sbin/rsyslogd -n
  admin 2496 0.0 0.0 12984 980 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1875493/+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 1774843] Re: apport python exception for python versions which python-apt is not built on

[Brian Murray]

** Changed in: python-apt (Ubuntu Eoan)
   Status: Invalid => In Progress

** Changed in: python-apt (Ubuntu Eoan)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Package changed: python-apt (Ubuntu) => apport (Ubuntu)

** Changed in: apport (Ubuntu)
   Status: Invalid => In Progress

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: apport (Ubuntu Bionic)
   Status: Invalid => In Progress

** Changed in: apport (Ubuntu Bionic)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: python3.7 (Ubuntu Bionic)
   Status: Triaged => Won't Fix

** Changed in: python3.7 (Ubuntu Eoan)
   Status: Triaged => Won't Fix

** Changed in: python3.8 (Ubuntu Bionic)
   Status: Triaged => Won't Fix

** Changed in: python3.8 (Ubuntu Eoan)
   Status: Triaged => Won't Fix

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

Title:
  apport python exception for python versions which python-apt is not
  built on

Status in Apport:
  New
Status in apport package in Ubuntu:
  In Progress
Status in python3.7 package in Ubuntu:
  Invalid
Status in python3.8 package in Ubuntu:
  Invalid
Status in apport source package in Bionic:
  In Progress
Status in python3.7 source package in Bionic:
  Won't Fix
Status in python3.8 source package in Bionic:
  Won't Fix
Status in apport source package in Eoan:
  In Progress
Status in python3.7 source package in Eoan:
  Won't Fix
Status in python3.8 source package in Eoan:
  Won't Fix
Status in apport source package in Focal:
  Invalid
Status in python3.7 source package in Focal:
  Invalid
Status in python3.8 source package in Focal:
  Invalid

Bug description:
  it seems apport installs an exception hook whenever running python3.
  This hook is apparently installed for python3.7 too.
  This exception handler has a dependency on apt_pkg, which is a binary that is 
not compatible with python3.7 it seems (you can't import it, see below)

  As a result, whenever I run a python3.7 script and run into an exception 
(which happens often when writing code), I get an additional exception in the 
exception handler + a copy of the original exception, so three stacktraces in 
total.
  A solution would be to only install the exception hook for the system python  
i.e. python3.6

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

  apport: 2.20.9-0ubuntu7
  python-apt: 1.6.0
  python3.7: 3.7.0~b3-1

  Demo with a trivial error:
  $ python3 -c 'print hello'
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?

  
  $ python3.7 -c 'print hello'
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in 
apport_excepthook
  from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in 

  from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in 
  import apport.fileutils
File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in 

  from apport.packaging_impl import impl as packaging
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in 

  import apt
File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in 
  import apt_pkg
  ModuleNotFoundError: No module named 'apt_pkg'

  Original exception was:
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?


  Python 3.6.5 (default, Apr  1 2018, 05:46:30) 
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  >>> import apt_pkg
  >>> apt_pkg.__file__
  '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so'
  >>> 

  Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) 
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  >> import apt_pkg
  Traceback (most recent call last):
File "", line 1, in 
  ModuleNotFoundError: No module named 'apt_pkg'

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1774843/+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 1873607] Re: systemd segv coredump, reboot/poweroff ignored.

[Dan Streetman]

> Still on eoan.  Staying with Ubuntu depends on freeipa support.
> Presently only the freeipa client is supported past eoan, so the future
> is unclear.

oh my, i wasn't aware of bug 1875114.  that does not seem good at all.

> Can the fix be backported?

yep, it's in the upload queue for eoan, so should make it into eoan-
proposed sometime soon.

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

Title:
  systemd segv coredump, reboot/poweroff ignored.

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  In Progress
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  during systemctl daemon-reload, systemd sometimes segfaults while
  serializing a service.

  [test case]

  problem is intermittent, but the upstream bug suggests a reproducer.
  Also see original description.

  [regression potential]

  this adjusts serialization, so any regression would likely occur
  during serialization/deserialization, e.g. at daemon-reload.

  [scope]

  This is needed for Bionic and later.

  this was introduced by commit e266c068b5597e18b2299f9c9d3ee6cf04198c41
  which is included starting in v234.  The commit to fix it is
  e9da62b18af647bfa73807e1c7fc3bfa4bb4b2ac which is not yet included in
  any release.

  The PR to fix this is https://github.com/systemd/systemd/pull/15546

  [other info]

  there is an additional PR that further avoids the error, but has not yet been 
accepted, and may not be accepted as it may not be necessary.
  https://github.com/systemd/systemd/pull/15370

  [original description]

  Proximate syslog:

  Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running:  ip -all netns 
del
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: 
ListenStream= references a path below legacy directory /var/run/, updating 
/var/run/dbus/system_bus_socket → /r
  un/dbus/system_bus_socket; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/sssd.pid → /run/sssd.pid; plea
  se update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/oddjobd.pid → /run/oddjobd.p
  id; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/fail2ban/fail2ban.pid → /r
  un/fail2ban/fail2ban.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/certmonger.pid → /run/cer
  tmonger.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: Reloading.
  Apr 18 16:26:56 gate2 kernel: [  454.966336] systemd[1]: segfault at 50 ip 
55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000]
  Apr 18 16:26:56 gate2 kernel: [  454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 
00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 
1f 84 00 00 00 00 00 <48
  > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d
  Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK:   systemctl 
daemon-reload
  Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running:  systemctl 
enable rssmonitor.service
  Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled
  Apr 18 16:27:24 gate2 kernel: [  482.503042] printk: systemd: 43 output lines 
suppressed due to ratelimiting
  Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.7
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  Date: Sat Apr 18 18:09:06 2020
  InstallationDate: Installed on 2019-11-01 (169 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/v

[Touch-packages] [Bug 1877987] Re: apt search coredumping

[Julian Andres Klode]

I believe that https://salsa.debian.org/apt-
team/apt/-/merge_requests/120 fixes this.

** Information type changed from Private Security to Private

** Information type changed from Private to Public

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

Title:
  apt search coredumping

Status in apt package in Ubuntu:
  New

Bug description:
  root@citoyx:/var/crash# apt search jdk
  Sorting... Done
  Segmentation fault (core dumped)

  May 11 12:34:25 citoyx kernel: [ 1354.337907] apt[10418]: segfault at 
7f67292dcfc0 ip 7f6309ce4997 sp 7ffdab880930 error 4 in 
libapt-pkg.so.6.0.0[7f6309bb5000+147000]
  May 11 12:34:25 citoyx kernel: [ 1354.337916] Code: 48 8b 45 18 48 8b 04 d0 
48 83 c4 08 5b 5d c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 fd 53 48 89 f3 48 83 ec 
08 48 8b 06 48 8b 4e 08 <8b> 10 48 8d 04 d5 00 00 00 00 48 29 d0 48 8b 51 60 48 
8d 04 c2 0f

  
  root@citoyx:/var/crash# cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

  
  apt search is coredumping 
  While apt install/upgrade/update is running fine 

  crash file in attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1877987/+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 1877987] Re: apt search coredumping

[Julian Andres Klode]

(I also believe this is the same issue as
https://errors.ubuntu.com/bucket/?id=/usr/bin/apt%3A11%3Aoperator%3ApkgCache%3A%3ADescFileIterator%3A%3AFile%3ApkgRecords%3A%3ALookup%3AFullTextSearch%3ADoSearch)

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

Title:
  apt search coredumping

Status in apt package in Ubuntu:
  New

Bug description:
  root@citoyx:/var/crash# apt search jdk
  Sorting... Done
  Segmentation fault (core dumped)

  May 11 12:34:25 citoyx kernel: [ 1354.337907] apt[10418]: segfault at 
7f67292dcfc0 ip 7f6309ce4997 sp 7ffdab880930 error 4 in 
libapt-pkg.so.6.0.0[7f6309bb5000+147000]
  May 11 12:34:25 citoyx kernel: [ 1354.337916] Code: 48 8b 45 18 48 8b 04 d0 
48 83 c4 08 5b 5d c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 fd 53 48 89 f3 48 83 ec 
08 48 8b 06 48 8b 4e 08 <8b> 10 48 8d 04 d5 00 00 00 00 48 29 d0 48 8b 51 60 48 
8d 04 c2 0f

  
  root@citoyx:/var/crash# cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

  
  apt search is coredumping 
  While apt install/upgrade/update is running fine 

  crash file in attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1877987/+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 1741045] Re: Change the default resample-method to speex-float-N (N > 1) in daemon.conf

[Sebastien Bacher]

unsure, you are the one who reported an issue/request for change, do you
think you request has been addressed or do you still think changing
would be better?

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

Title:
  Change the default resample-method to speex-float-N (N > 1) in
  daemon.conf

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I suggest changing the default resample-method to speex-float-10,
  instead of speex-float-1, which is the current default now, in
  /etc/pulse/daemon.conf.

  It would look like this in daemon.conf:
  resample-method = speex-float-10

  I have always done that since at least 12.04 LTS. I was not satisfied
  with the sound quality in Ubuntu compared to Windows, so I changed the
  resample-method.

  In my day-to-day usage, it gives better sound quality without
  sacrificing CPU power.

  I have not tried other resample methods. Maybe there are better
  options I don't know about.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amr1696 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  3 14:37:25 2018
  InstallationDate: Installed on 2017-10-02 (92 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-10-05T12:39:48.718018

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1741045/+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 1878312] ProcCpuinfoMinimal.txt

[Andycds]

apport information

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

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

Title:
  Sound input is not automatically switched back from headphones mic to
  internal microphone

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When plugging in headphones, sound input is correctly switched from
  internal microphone to the headphones mic. When the headphones are
  unplugged, sound input is NOT automatically switched back to the
  internal microphone.

  Sound output is switched back and forth correctly.

  This bug started happening on my system after I upgraded from 19.10 to 20.04 
so it is a regression. Attached is pulseaudio log of what happens when I plug 
and unplug my headphones.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anderson   2247 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-08-24 (263 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-25 (17 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/06/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 0W83FH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd01/06/2020:svnDellInc.:pnInspiron7580:pvr:rvnDellInc.:rn0W83FH:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7580
  dmi.product.sku: 08A6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878312/+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 1878312] PulseList.txt

[Andycds]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1878312/+attachment/5371127/+files/PulseList.txt

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

Title:
  Sound input is not automatically switched back from headphones mic to
  internal microphone

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When plugging in headphones, sound input is correctly switched from
  internal microphone to the headphones mic. When the headphones are
  unplugged, sound input is NOT automatically switched back to the
  internal microphone.

  Sound output is switched back and forth correctly.

  This bug started happening on my system after I upgraded from 19.10 to 20.04 
so it is a regression. Attached is pulseaudio log of what happens when I plug 
and unplug my headphones.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anderson   2247 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-08-24 (263 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-25 (17 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/06/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 0W83FH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd01/06/2020:svnDellInc.:pnInspiron7580:pvr:rvnDellInc.:rn0W83FH:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7580
  dmi.product.sku: 08A6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878312/+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 1878312] Dependencies.txt

[Andycds]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1878312/+attachment/5371124/+files/Dependencies.txt

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

Title:
  Sound input is not automatically switched back from headphones mic to
  internal microphone

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When plugging in headphones, sound input is correctly switched from
  internal microphone to the headphones mic. When the headphones are
  unplugged, sound input is NOT automatically switched back to the
  internal microphone.

  Sound output is switched back and forth correctly.

  This bug started happening on my system after I upgraded from 19.10 to 20.04 
so it is a regression. Attached is pulseaudio log of what happens when I plug 
and unplug my headphones.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anderson   2247 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-08-24 (263 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-25 (17 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/06/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 0W83FH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd01/06/2020:svnDellInc.:pnInspiron7580:pvr:rvnDellInc.:rn0W83FH:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7580
  dmi.product.sku: 08A6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878312/+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 1878312] CurrentDmesg.txt

[Andycds]

apport information

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

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

Title:
  Sound input is not automatically switched back from headphones mic to
  internal microphone

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When plugging in headphones, sound input is correctly switched from
  internal microphone to the headphones mic. When the headphones are
  unplugged, sound input is NOT automatically switched back to the
  internal microphone.

  Sound output is switched back and forth correctly.

  This bug started happening on my system after I upgraded from 19.10 to 20.04 
so it is a regression. Attached is pulseaudio log of what happens when I plug 
and unplug my headphones.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anderson   2247 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-08-24 (263 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-25 (17 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/06/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 0W83FH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd01/06/2020:svnDellInc.:pnInspiron7580:pvr:rvnDellInc.:rn0W83FH:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7580
  dmi.product.sku: 08A6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878312/+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 1878312] ProcEnviron.txt

[Andycds]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1878312/+attachment/5371126/+files/ProcEnviron.txt

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

Title:
  Sound input is not automatically switched back from headphones mic to
  internal microphone

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When plugging in headphones, sound input is correctly switched from
  internal microphone to the headphones mic. When the headphones are
  unplugged, sound input is NOT automatically switched back to the
  internal microphone.

  Sound output is switched back and forth correctly.

  This bug started happening on my system after I upgraded from 19.10 to 20.04 
so it is a regression. Attached is pulseaudio log of what happens when I plug 
and unplug my headphones.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anderson   2247 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-08-24 (263 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-25 (17 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/06/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 0W83FH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd01/06/2020:svnDellInc.:pnInspiron7580:pvr:rvnDellInc.:rn0W83FH:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7580
  dmi.product.sku: 08A6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878312/+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 1878322] Re: cupsaddsmb

[Sebastien Bacher]

Thank you for taking the time to report this bug and help make Ubuntu
better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read 'How to report bugs effectively'
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Thanks!

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

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

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

Title:
  cupsaddsmb

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  this app is not into this package !

  ubuntu server 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1878322/+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 1878312] Re: Sound input is not automatically switched back from headphones mic to internal microphone

[Andycds]

apport information

** Tags added: apport-collected focal

** Description changed:

  When plugging in headphones, sound input is correctly switched from
  internal microphone to the headphones mic. When the headphones are
  unplugged, sound input is NOT automatically switched back to the
  internal microphone.
  
  Sound output is switched back and forth correctly.
  
- This bug started happening on my system after I upgraded from 19.10 to
- 20.04 so it is a regression. Attached is pulseaudio log of what happens
- when I plug and unplug my headphones.
+ This bug started happening on my system after I upgraded from 19.10 to 20.04 
so it is a regression. Attached is pulseaudio log of what happens when I plug 
and unplug my headphones.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  anderson   2247 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2019-08-24 (263 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
+ Package: pulseaudio 1:13.99.1-1ubuntu3.2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
+ Tags:  focal
+ Uname: Linux 5.4.0-29-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-04-25 (17 days ago)
+ UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 01/06/2020
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.10.0
+ dmi.board.name: 0W83FH
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A01
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd01/06/2020:svnDellInc.:pnInspiron7580:pvr:rvnDellInc.:rn0W83FH:rvrA01:cvnDellInc.:ct10:cvr:
+ dmi.product.family: Inspiron
+ dmi.product.name: Inspiron 7580
+ dmi.product.sku: 08A6
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1878312/+attachment/5371122/+files/AlsaInfo.txt

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

Title:
  Sound input is not automatically switched back from headphones mic to
  internal microphone

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When plugging in headphones, sound input is correctly switched from
  internal microphone to the headphones mic. When the headphones are
  unplugged, sound input is NOT automatically switched back to the
  internal microphone.

  Sound output is switched back and forth correctly.

  This bug started happening on my system after I upgraded from 19.10 to 20.04 
so it is a regression. Attached is pulseaudio log of what happens when I plug 
and unplug my headphones.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anderson   2247 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-08-24 (263 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-25 (17 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/06/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 0W83FH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd01/06/2020:svnDellInc.:pnInspiron7580:pvr:rvnDellInc.:rn0W83FH:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7580
  dmi.product.sku: 08A6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878312/+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 1878312] Re: Sound input is not automatically switched back from headphones mic to internal microphone

[Sebastien Bacher]

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

  apport-collect 1878312

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

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

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

Title:
  Sound input is not automatically switched back from headphones mic to
  internal microphone

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When plugging in headphones, sound input is correctly switched from
  internal microphone to the headphones mic. When the headphones are
  unplugged, sound input is NOT automatically switched back to the
  internal microphone.

  Sound output is switched back and forth correctly.

  This bug started happening on my system after I upgraded from 19.10 to
  20.04 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878312/+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 1878469] Re: Ubuntu 20.04 causing green vertical stripes on my desktop

[Sebastien Bacher]

Thank you for your bug report, could you add a screenshot showing the
issue and a 'journalctl -b 0' log after hitting the bug?

** Changed in: xorg (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/1878469

Title:
  Ubuntu 20.04 causing green vertical stripes on my desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  As soon as I upgraded to Ubuntu 20.04, two green pixel stripes appeared on my 
desktop.
  They do not interfere with windows when opened, whether they are browsers, 
files or other items, and they do not seem to have an impact on the general 
behavior of the PC.

  Still, something tells me that they are not supposed to be there.

  I have a dual boot, Windows and Ubuntu, and two drivers:

  VGA compatbile controller: Intel UHD Graphics 630 (mobile)
  3D controller: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] 

  Any support would be welcome.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-31.35-lowlatency 5.4.34
  Uname: Linux 5.4.0-31-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 13 18:55:14 2020
  DistUpgraded: 2020-05-13 13:02:22,581 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c]
  InstallationDate: Installed on 2018-12-23 (506 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications 
   Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-lowlatency 
root=UUID=d49b534b-1745-4089-80d9-cb11f85d2570 ro acpi=force 
nvidia.NVreg_EnableBacklightHandler=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-05-13 (0 days ago)
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1878469/+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 1878479] Re: HP-OMEN 17t bc0xxx don't work sound and microphone

[Sebastien Bacher]

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

Title:
  HP-OMEN 17t bc0xxx don't work sound and microphone

Status in linux package in Ubuntu:
  New

Bug description:
  This problem has been resolved for kernel 5.7. * 
https://bugzilla.kernel.org/show_bug.cgi?id=206085 But I can’t work on it 
because I have more problems with the constant relogin 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1878193
  How to solve this problem with kernel trust supported by ubuntu?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878479/+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 1659719] Re: ssh can't call a binary from a snap without the full path

[Steve Langasek]

I know that work was done to ensure /snap/bin was in the default path
for systemd itself and that this should be inherited now by all units.
'systemd-path | grep search-binaries:' shows that it's there on my focal
system.  'sudo ps axe | grep sshd' also shows that it's set in the
PATH environment of the sshd parent processes.  So I'm not sure what is
still resetting the PATH for noninteractive ssh sessions.

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

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

Title:
  ssh can't call a binary from a snap without the full path

Status in Snappy:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Committed
Status in openssh package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  ssh can't call a binary from a snap, it will only work using the full
  path.

  Let's say I have the hello snap installed in 192.168.122.24. Then:

  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello
  elopio@192.168.122.24's password:
  bash: hello: command not found
  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello
  elopio@192.168.122.24's password:
  Hello, world!

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1659719/+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 1659719] Re: ssh can't call a binary from a snap without the full path

[Steve Langasek]

It looks like the likely cause here is that sshd loads pam, which calls
pam_env, which reads /etc/environment, which has a different PATH than
the default one provided by systemd.

We should fix this to be aligned.

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

Title:
  ssh can't call a binary from a snap without the full path

Status in Snappy:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Committed
Status in openssh package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  ssh can't call a binary from a snap, it will only work using the full
  path.

  Let's say I have the hello snap installed in 192.168.122.24. Then:

  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello
  elopio@192.168.122.24's password:
  bash: hello: command not found
  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello
  elopio@192.168.122.24's password:
  Hello, world!

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1659719/+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 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

[Dan Streetman]

** Description changed:

  [impact]
  
  A bridged interface with static ipv4 address and gateway configuration
  will fail to properly add the route via the gateway, leaving the system
  without a globally working network.
  
  [test case]
  
  On a Focal system, remove all network configuration and create this
  netplan:
  
  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]
  
  Replace the interface name 'enp4s0' with the actual interface name on
  the test system.
  
  Reboot the system, and check the route to the gateway, which will be
  missing:
  
  root@lp1860926-f:~# ip r
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4
  
  The route is expected to be present, e.g.:
  
  ubuntu@lp1860926-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4
+ 
+ [test case, pre-focal]
+ 
+ same netplan as above, but remove ethernets: section.  Reboot, and the
+ bridge should have its address and route:
+ 
+ ubuntu@test-e:~$ ip a show br0
+ 3: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
+ link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
+ inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
+valid_lft forever preferred_lft forever
+ ubuntu@test-e:~$ ip r
+ default via 192.168.0.1 dev br0 proto static linkdown 
+ 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 linkdown 
+ 
+ 
+ add and remove carrier, by adding and removing a slave interface:
+ 
+ ubuntu@test-e:~$ sudo ip l set dev ens3 master br0 up
+ ubuntu@test-e:~$ ip a show br0
+ 3: br0:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
+ link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
+ inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
+valid_lft forever preferred_lft forever
+ inet6 fe80::5411:daff:fe23:bb93/64 scope link 
+valid_lft forever preferred_lft forever
+ ubuntu@test-e:~$ sudo ip l set dev ens3 nomaster
+ 
+ 
+ the bridge no longer has its address after losing carrier:
+ 
+ ubuntu@test-e:~$ ip a show br0
+ 3: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
+ link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
+ inet6 fe80::5411:daff:fe23:bb93/64 scope link 
+valid_lft forever preferred_lft forever
+ 
  
  [regression potential]
  
  Any regression would likely involve incorrectly configured network after
  an interface carrier gain/loss.
  
  [scope]
  
  This is needed for Focal, Eoan, and Bionic.
  
  While this only reproduces at boot for Focal, the general loss of
  configuration on carrier loss even when ConfigureWithoutCarrier=true is
  reproducable on all releases except Xenial, which does not have the
  ConfigureWithoutCarrier= parameter.
  
  [original description]
  
  Freshly installed Ubuntu 20.04 fully patched to days date with static IP
  address works fine and survives a reboot
  
  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]
  
  however when converted to a bridged network for kvm
  
  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]
  
  will not survive a reboot and required systemd-network to be restarted or
  @reboot /usr/sbin/netplan apply
  added to the crontab
  
  after a reboot the network can not b eaccseed and a
  systemctl status systemd-networkd produces
  
  systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 979 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 57662)
   Memory: 4.1M
   CGroup: /system.slice/systemd-networkd.service
   └─979 /lib/systemd/systemd-networkd
  
  Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for 
link '5' we don't know about, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: r

[Touch-packages] [Bug 1877528] Re: Applet does not terminate at end of X desktop session

[Bug Watch Updater]

** Changed in: system-config-printer
   Status: New => Fix Released

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

Title:
  Applet does not terminate at end of X desktop session

Status in System Config Printer:
  Fix Released
Status in lightdm package in Ubuntu:
  New
Status in sddm package in Ubuntu:
  New
Status in system-config-printer package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Invalid
Status in system-config-printer package in Debian:
  Unknown

Bug description:
  This concerns system-config-printer 1.5.12-0ubuntu1 in Ubuntu focal.

  I log into the Xfce desktop, and then logout. The screen returns to
  the LightDM login screen.

  A few minutes later, "loginctl list-sessions" shows the following:

  SESSION  UID USERSEAT  TTY  
90 root   
   c2 1000 skunk   seat0  
   c3  116 lightdm seat0  

  3 sessions listed.

  Output from "loginctl session-status c2":

  c2 - skunk (1000)
 Since: Fri 2020-05-08 03:09:05 EDT; 9min ago
Leader: 2530
  Seat: seat0; vc7
   Display: :0
   Service: lightdm; type x11; class user
   Desktop: xubuntu
 State: closing
  Unit: session-c2.scope
└─2856 /usr/bin/python3 
/usr/share/system-config-printer/applet.py

  This process sticks around forever until I kill it, or its parent
  "systemd --user" process. Only then does the session disappear from
  list-sessions.

  When I run "session-status" while I'm logged in, I see a list of
  nearly 30 desktop-related processes. All of them except this one go
  away on logout. This one should too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/system-config-printer/+bug/1877528/+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 1878482] [NEW] EPSON WF 3520 driver problem - PpdFiles: Error

[Galk32]

Public bug reported:

doesn't work

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups 2.3.1-9ubuntu1.1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed May 13 23:17:35 2020
InstallationDate: Installed on 2020-05-06 (6 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lpstat: device for Generic-ESC-P-Dot-Matrix: lpd://192.168.1.133:515/PASSTHRU
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 04f2:b413 Chicony Electronics Co., Ltd FJ Camera
 Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless 
Keyboard/Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: FUJITSU LIFEBOOK A555
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Generic-ESC-P-Dot-Matrix.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Generic-ESC-P-Dot-Matrix.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=85a6cbd6-a8d0-4ee5-ac82-9f54acbb0106 ro quiet splash
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2016
dmi.bios.vendor: FUJITSU // Insyde Software Corp.
dmi.bios.version: 1.21
dmi.board.name: FJNBB3E
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.21:bd05/31/2016:svnFUJITSU:pnLIFEBOOKA555:pvr:rvnFUJITSU:rnFJNBB3E:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.family: LIFEBOOK-FTS
dmi.product.name: LIFEBOOK A555
dmi.sys.vendor: FUJITSU

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


** Tags: amd64 apparmor apport-bug focal

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

Title:
  EPSON WF 3520 driver problem - PpdFiles: Error

Status in cups package in Ubuntu:
  New

Bug description:
  doesn't work

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 13 23:17:35 2020
  InstallationDate: Installed on 2020-05-06 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for Generic-ESC-P-Dot-Matrix: lpd://192.168.1.133:515/PASSTHRU
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b413 Chicony Electronics Co., Ltd FJ Camera
   Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless 
Keyboard/Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU LIFEBOOK A555
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Generic-ESC-P-Dot-Matrix.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Generic-ESC-P-Dot-Matrix.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=85a6cbd6-a8d0-4ee5-ac82-9f54acbb0106 ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2016
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: 1.21
  dmi.board.name: FJNBB3E
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.21:bd05/31/2016:svnFUJITSU:pnLIFEBOOKA555:pvr:rvnFUJITSU:rnFJNBB3E:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK A555
  dmi.sys.vendor: FUJITSU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1878482/+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 1868892] Re: initramfs-tools/hooks/udev for network *.link really sucks

[Dan Streetman]

focal:

ubuntu@lp1868892-f:~$ dpkg -l systemd|grep systemd
ii  systemd245.4-4ubuntu3 amd64system and service manager
ubuntu@lp1868892-f:~$ sudo touch /etc/systemd/network/lp1868892.link
ubuntu@lp1868892-f:~$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.4.0-29-generic
ubuntu@lp1868892-f:~$ sudo lsinitramfs /boot/initrd.img-5.4.0-29-generic | grep 
lp1868892
usr/lib/systemd/network/lp1868892.link
ubuntu@lp1868892-f:~$ sudo mv /etc/systemd/network /etc/systemd/network.abc
ubuntu@lp1868892-f:~$ sudo ln -s network.abc /etc/systemd/network
ubuntu@lp1868892-f:~$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.4.0-29-generic
ubuntu@lp1868892-f:~$ sudo lsinitramfs /boot/initrd.img-5.4.0-29-generic | grep 
lp1868892
ubuntu@lp1868892-f:~$ 


ubuntu@lp1868892-f:~$ sudo rm /etc/systemd/network
ubuntu@lp1868892-f:~$ sudo mv /etc/systemd/network.abc /etc/systemd/network
ubuntu@lp1868892-f:~$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.4.0-31-generic
ubuntu@lp1868892-f:~$ sudo lsinitramfs /boot/initrd.img-5.4.0-31-generic | grep 
lp1868892
usr/lib/systemd/network/lp1868892.link


ubuntu@lp1868892-f:~$ dpkg -l systemd|grep systemd
ii  systemd245.4-4ubuntu3.1 amd64system and service manager
ubuntu@lp1868892-f:~$ sudo touch /etc/systemd/network/lp1868892.link
ubuntu@lp1868892-f:~$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.4.0-31-generic
ubuntu@lp1868892-f:~$ sudo lsinitramfs /boot/initrd.img-5.4.0-31-generic | grep 
lp1868892
usr/lib/systemd/network/lp1868892.link
ubuntu@lp1868892-f:~$ sudo mv /etc/systemd/network /etc/systemd/network.abc
ubuntu@lp1868892-f:~$ sudo ln -s network.abc /etc/systemd/network
ubuntu@lp1868892-f:~$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.4.0-31-generic
ubuntu@lp1868892-f:~$ sudo lsinitramfs /boot/initrd.img-5.4.0-31-generic | grep 
lp1868892
usr/lib/systemd/network/lp1868892.link


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

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

Title:
  initramfs-tools/hooks/udev for network *.link really sucks

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [impact]

  If the /{etc,lib}/systemd/network directory itself is a symlink, the find
  command will not actually find any of the files in the dir it links to.

  [test case]

  $ sudo touch /etc/systemd/network/lp1868892.link
  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic
  ...
  $ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
  usr/lib/systemd/network/lp1868892.link
  $ sudo mv /etc/systemd/network /etc/systemd/network.abc
  $ sudo ln -s network.abc /etc/systemd/network
  $ sudo update-initramfs -u
  $ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
  $ 

  [regression potential]

  this adjusts how link files are included in the initramfs, so
  regressions would likely occur when creating new initramfs, such as
  failure to create initramfs at all, or failure to properly copy link
  files into the initramfs, causing network setup failure.

  [scope]

  this is a Debian/Ubuntu specific file, and the Debian MR was just
  opened, so this is needed for Debian and all releases of Ubuntu.

  [other info]

  This bug likely has a very limited impact, as it is uncommon to
  symlink either the /lib/systemd/network or /etc/systemd/network dirs.

  [original description]

  If one creates e.g. /etc/systemd/network.cu and
  /etc/systemd/network.fc and symlinks  /etc/systemd/network to one of
  them, network setup will fail on reboot, because /usr/share/initramfs-
  tools/hooks/udev does a very poor job: it simply checks for a
  directory instead of the link files and therefore skips copying
  required files to the ram image. Another poor job is done when copying
  the files to the ram image: instead of following symlinks it copies
  them as which in turn makes them useless, because it does not copy the
  related dirs and thus the symlinks point to nothing. So keeping the
  system in an consistent state which such poor scripts is very hard,
  asking for trouble.

  Suggested fix is attached.

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

Re: [Touch-packages] [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.

[Harry Coin]

Still on eoan.  Staying with Ubuntu depends on freeipa support. 
Presently only the freeipa client is supported past eoan, so the future 
is unclear.  Can the fix be backported?

On 5/13/20 3:03 PM, Dan Streetman wrote:
> @hcoin are you still on Eoan or have you moved up to Focal yet?  If
> you're on Focal, could you test the version from -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/1873607

Title:
  systemd segv coredump, reboot/poweroff ignored.

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  In Progress
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  during systemctl daemon-reload, systemd sometimes segfaults while
  serializing a service.

  [test case]

  problem is intermittent, but the upstream bug suggests a reproducer.
  Also see original description.

  [regression potential]

  this adjusts serialization, so any regression would likely occur
  during serialization/deserialization, e.g. at daemon-reload.

  [scope]

  This is needed for Bionic and later.

  this was introduced by commit e266c068b5597e18b2299f9c9d3ee6cf04198c41
  which is included starting in v234.  The commit to fix it is
  e9da62b18af647bfa73807e1c7fc3bfa4bb4b2ac which is not yet included in
  any release.

  The PR to fix this is https://github.com/systemd/systemd/pull/15546

  [other info]

  there is an additional PR that further avoids the error, but has not yet been 
accepted, and may not be accepted as it may not be necessary.
  https://github.com/systemd/systemd/pull/15370

  [original description]

  Proximate syslog:

  Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running:  ip -all netns 
del
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: 
ListenStream= references a path below legacy directory /var/run/, updating 
/var/run/dbus/system_bus_socket → /r
  un/dbus/system_bus_socket; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/sssd.pid → /run/sssd.pid; plea
  se update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/oddjobd.pid → /run/oddjobd.p
  id; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/fail2ban/fail2ban.pid → /r
  un/fail2ban/fail2ban.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/certmonger.pid → /run/cer
  tmonger.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: Reloading.
  Apr 18 16:26:56 gate2 kernel: [  454.966336] systemd[1]: segfault at 50 ip 
55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000]
  Apr 18 16:26:56 gate2 kernel: [  454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 
00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 
1f 84 00 00 00 00 00 <48
  > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d
  Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK:   systemctl 
daemon-reload
  Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running:  systemctl 
enable rssmonitor.service
  Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled
  Apr 18 16:27:24 gate2 kernel: [  482.503042] printk: systemd: 43 output lines 
suppressed due to ratelimiting
  Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.7
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  Date: Sat Apr 18 18:09:06 2020
  InstallationDate: Installed on 2019-11-01 (169 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/@/bo

[Touch-packages] [Bug 1878468] Re: Crackling sound

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  Crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I've installed Kubuntu 20.04 and I have crackling/popping sound. I
  tried to change needed files for pulseaudio and alsa (disabling power
  save), reboot the system and I still have problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kizule 1937 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed May 13 20:47:03 2020
  InstallationDate: Installed on 2020-05-13 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/10/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVU Ver. F.06
  dmi.board.name: 30D5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 82.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVUVer.F.06:bd12/10/2007:svnHewlett-Packard:pn:pvrF.06:rvnHewlett-Packard:rn30D5:rvrKBCVersion82.15:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.version: F.06
  dmi.sys.vendor: Hewlett-Packard
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-13T20:24:18.764608

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878468/+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 1877633] Re: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64

[Jamie Strandboge]

** Changed in: libseccomp (Ubuntu Focal)
   Status: Confirmed => In Progress

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

Title:
  libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the
  getrlimit syscall on arm64

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

Bug description:
  This was reported via the snapcraft forum[1]:

  On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2

  $ lsb_release -d
  Description:  Ubuntu 18.04.4 LTS
  $ scmp_sys_resolver -a aarch64 163
  getrlimit
  $ scmp_sys_resolver -a aarch64 getrlimit
  163

  focal amd64, libseccomp 2.4.3-1ubuntu1 -- *__BROKEN__*

  $ lsb_release -d
  Description:  Ubuntu 20.04 LTS
  $ scmp_sys_resolver -a aarch64 163
  UNKNOWN
  $ scmp_sys_resolver -a aarch64 getrlimit
  -10180

  [1]https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal-
  arm64/17237/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633/+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 1873607] Re: systemd segv coredump, reboot/poweroff ignored.

[Dan Streetman]

@hcoin are you still on Eoan or have you moved up to Focal yet?  If
you're on Focal, could you test the version from -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/1873607

Title:
  systemd segv coredump, reboot/poweroff ignored.

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  In Progress
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  during systemctl daemon-reload, systemd sometimes segfaults while
  serializing a service.

  [test case]

  problem is intermittent, but the upstream bug suggests a reproducer.
  Also see original description.

  [regression potential]

  this adjusts serialization, so any regression would likely occur
  during serialization/deserialization, e.g. at daemon-reload.

  [scope]

  This is needed for Bionic and later.

  this was introduced by commit e266c068b5597e18b2299f9c9d3ee6cf04198c41
  which is included starting in v234.  The commit to fix it is
  e9da62b18af647bfa73807e1c7fc3bfa4bb4b2ac which is not yet included in
  any release.

  The PR to fix this is https://github.com/systemd/systemd/pull/15546

  [other info]

  there is an additional PR that further avoids the error, but has not yet been 
accepted, and may not be accepted as it may not be necessary.
  https://github.com/systemd/systemd/pull/15370

  [original description]

  Proximate syslog:

  Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running:  ip -all netns 
del
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: 
ListenStream= references a path below legacy directory /var/run/, updating 
/var/run/dbus/system_bus_socket → /r
  un/dbus/system_bus_socket; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/sssd.pid → /run/sssd.pid; plea
  se update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/oddjobd.pid → /run/oddjobd.p
  id; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/fail2ban/fail2ban.pid → /r
  un/fail2ban/fail2ban.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/certmonger.pid → /run/cer
  tmonger.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: Reloading.
  Apr 18 16:26:56 gate2 kernel: [  454.966336] systemd[1]: segfault at 50 ip 
55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000]
  Apr 18 16:26:56 gate2 kernel: [  454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 
00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 
1f 84 00 00 00 00 00 <48
  > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d
  Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK:   systemctl 
daemon-reload
  Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running:  systemctl 
enable rssmonitor.service
  Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled
  Apr 18 16:27:24 gate2 kernel: [  482.503042] printk: systemd: 43 output lines 
suppressed due to ratelimiting
  Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.7
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  Date: Sat Apr 18 18:09:06 2020
  InstallationDate: Installed on 2019-11-01 (169 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-46-generic 
root=UUID=82254a10-a9e1-4459-aba0-7876df48d9da ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.

[Touch-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

[Seth Forshee]

** Also affects: linux-azure (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux-gcp (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux-kvm (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux-oracle (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux-riscv (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: linux-azure (Ubuntu)
   Status: New => Invalid

** Changed in: linux-gcp (Ubuntu)
   Status: New => Invalid

** Changed in: linux-kvm (Ubuntu)
   Status: New => Invalid

** Changed in: linux-oracle (Ubuntu)
   Status: New => Invalid

** Changed in: linux-riscv (Ubuntu)
   Status: New => Invalid

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-riscv package in Ubuntu:
  Invalid
Status in rtkit package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux-azure source package in Focal:
  New
Status in linux-gcp source package in Focal:
  New
Status in linux-kvm source package in Focal:
  New
Status in linux-oracle source package in Focal:
  New
Status in linux-riscv source package in Focal:
  New
Status in rtkit source package in Focal:
  Confirmed

Bug description:
  SRU Justification

  Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the
  lowlatency kernel since we expected most RT users to use that kernel.
  However we are getting RT regressions with the generic kernel. Digging
  deeper into this option, it seems to be pretty specialized and to
  require quite a bit of workload-specific configuration/tuning to be
  useful, so it doesn't really seem to make sense for a general-purpose
  kernel.

  Fix: Turn this option back off.

  Test Case: See comment #4.

  Regression Potential: This was turned on to support some docker
  functionality, so this functionality will no longer be available.
  We've had this option off for all releases prior to focal, so this
  seems acceptable.

  ---

  These errors started right after upgrading to 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 10:31:43 2020
  InstallationDate: Installed on 2019-06-18 (315 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665/+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 1878468] [NEW] Crackling sound

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I've installed Kubuntu 20.04 and I have crackling/popping sound. I tried
to change needed files for pulseaudio and alsa (disabling power save),
reboot the system and I still have problem.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  kizule 1937 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Wed May 13 20:47:03 2020
InstallationDate: Installed on 2020-05-13 (0 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/10/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68MVU Ver. F.06
dmi.board.name: 30D5
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 82.15
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVUVer.F.06:bd12/10/2007:svnHewlett-Packard:pn:pvrF.06:rvnHewlett-Packard:rn30D5:rvrKBCVersion82.15:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN
dmi.product.version: F.06
dmi.sys.vendor: Hewlett-Packard
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-13T20:24:18.764608

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


** Tags: amd64 apport-bug focal
-- 
Crackling sound
https://bugs.launchpad.net/bugs/1878468
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver 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 1878479] [NEW] HP-OMEN 17t bc0xxx don't work sound and microphone

[Sergey]

Public bug reported:

This problem has been resolved for kernel 5.7. * 
https://bugzilla.kernel.org/show_bug.cgi?id=206085 But I can’t work on it 
because I have more problems with the constant relogin 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1878193
How to solve this problem with kernel trust supported by ubuntu?

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

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

Title:
  HP-OMEN 17t bc0xxx don't work sound and microphone

Status in xorg package in Ubuntu:
  New

Bug description:
  This problem has been resolved for kernel 5.7. * 
https://bugzilla.kernel.org/show_bug.cgi?id=206085 But I can’t work on it 
because I have more problems with the constant relogin 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1878193
  How to solve this problem with kernel trust supported by ubuntu?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1878479/+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 1878108] Re: new upstream release 2020a

[Brian Murray]

** Changed in: tzdata (Ubuntu Trusty)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: tzdata (Ubuntu Trusty)
   Status: New => In Progress

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

Title:
  new upstream release 2020a

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Trusty:
  In Progress
Status in tzdata source package in Xenial:
  Fix Committed
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Eoan:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed

Bug description:
  There is a new upstream release of tzdata, 2020, which includes the
  following:

    * New upstream release, affecting past and future timestamps:
  - Morocco springs forward on 2020-05-31, not 2020-05-24.
  - Canada's Yukon advanced to -07 year-round on 2020-03-08.
  - America/Nuuk renamed from America/Godthab.

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with "zdump -v
  $region/$timezone_that_changed" (this needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".]
  This is compared to the same output after the updated package got
  installed. If those are different the verification is considered done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1878108/+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 1867375] Re: systemd-networkd: UseRoutes behavior change with introduction of UseGateway param

[Dan Streetman]

thanks for verifying @toshko3!

i marked as verification-done for focal.  (I also gave it a quick test
to verify).

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

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

Title:
  systemd-networkd: UseRoutes behavior change with introduction of
  UseGateway param

Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  In Progress
Status in netplan.io source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in netplan.io source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  In Progress
Status in netplan.io source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Committed
Status in netplan.io source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  In Progress

Bug description:
  [impact]

  the networkd UseRoutes parameter allowed ignoring all routes provided
  by a dhcp4 server, including the route via the dhcp4-provided gateway.
  This was the behavior of networkd until recently, and in Focal the
  UseRoutes parameter does *not* prevent networkd from adding the route
  via the dhcp4-provided gateway.  This is now controlled with a new
  parameter, UseGateway.

  The systemd in Focal unfortunately has part of the upstream code; it
  no longer ignores the gateway route when UseRoutes=false is specified,
  but also it does not include the UseGateway parameter.

  Before Focal, networkd did not allow ignoring dhcpv4 routes and the
  gateway separately; the UseRoutes= parameter either used, or ignored,
  both.  This is why upstream added the UseGateway= paramter, which
  should be backported to allow control of ignoring the dhcpv4 routes
  and gateway separately.

  [test case]

  In Focal, bug 1872589 has a good test case netplan config, but a very
  quick test can be done with the networkd config:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false

  this results in the system incorrectly setting a route via the default
  gateway:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  Before Focal, the above test case shows "correct" behavior, but there
  is no way to ignore the dhcpv4 routes but use the dhcpv4 gateway.
  This pre-Focal, the test case would be to use the UseGateway=
  parameter, e.g.:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false
  UseGateway=true

  which *should* result in the default gateway being configured:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  [regression potential]

  Any regression would likely involve incorrect setting, or ignoring, of
  dhcpv4-provided routes, and/or incorrect setting, or ignoring, of the
  dhcpv4-provided gateway.

  [scope]

  This is fixed by these upstream PRs:
  https://github.com/systemd/systemd/pull/15443
  https://github.com/systemd/systemd/pull/15136
  https://github.com/systemd/systemd/pull/14983

  Parts of all those PRs are required in Focal, Eoan, and Bionic.

  I am not fixing this for Xenial, at this time.

  For Debian, I opened this MR:
  https://salsa.debian.org/systemd-team/systemd/-/merge_requests/92

  For Groovy, I opened this MR:
  
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/383661

  [other info]

  to properly support separation of 'routes' and 'gateways' received via
  dhcp4, SRU releases should also support the UseGateway parameter,
  which is what this bug was originally opened requesting.

  [original description]

  requesting backport of PR https://github.com/systemd/systemd/pull/14983 which 
fixes the issue described in
  https://github.com/systemd/systemd/issues/14982 to 18.04 (bionic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1867375/+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 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

[Dan Streetman]

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

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

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  In Progress
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [impact]

  A bridged interface with static ipv4 address and gateway configuration
  will fail to properly add the route via the gateway, leaving the
  system without a globally working network.

  [test case]

  On a Focal system, remove all network configuration and create this
  netplan:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  Replace the interface name 'enp4s0' with the actual interface name on
  the test system.

  Reboot the system, and check the route to the gateway, which will be
  missing:

  root@lp1860926-f:~# ip r
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  The route is expected to be present, e.g.:

  ubuntu@lp1860926-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  [regression potential]

  Any regression would likely involve incorrectly configured network
  after an interface carrier gain/loss.

  [scope]

  This is needed for Focal, Eoan, and Bionic.

  While this only reproduces at boot for Focal, the general loss of
  configuration on carrier loss even when ConfigureWithoutCarrier=true
  is reproducable on all releases except Xenial, which does not have the
  ConfigureWithoutCarrier= parameter.

  [original description]

  Freshly installed Ubuntu 20.04 fully patched to days date with static
  IP address works fine and survives a reboot

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  however when converted to a bridged network for kvm

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  will not survive a reboot and required systemd-network to be restarted or
  @reboot /usr/sbin/netplan apply
  added to the crontab

  after a reboot the network can not b eaccseed and a
  systemctl status systemd-networkd produces

  systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 979 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 57662)
   Memory: 4.1M
   CGroup: /system.slice/systemd-networkd.service
   └─979 /lib/systemd/systemd-networkd

  Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for 
link '5' we don't know about, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an 
address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring.

  systemctl restart systemd-networkd resolved the issue and a

  systemctl status systemd-network producessystemd-networkd.service - Network 
Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.ser

[Touch-packages] [Bug 1878333] Re: AppArmor cache entries not removed when profile is deleted

[Daniel Richard G.]

Thanks. I am in complete agreement.

I don't need (or even want) AppArmor to automagically update the kernel
state right after changing something under /etc/apparmor.d/, because
having to do a SIGHUP/restart/etc. is already normal practice. But I do
expect that a reboot/reload will take care of that for me, as it does
for other services.

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

Title:
  AppArmor cache entries not removed when profile is deleted

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  This concerns apparmor 2.13.3-7ubuntu5 in Ubuntu focal.

  If I delete a profile from /etc/apparmor.d/, reboot the system, and
  then look in /var/cache/apparmor/.0/, I still see a file for
  the compiled form of the profile.

  The same occurs if the profile is "deleted" by other means, such as
  symlinking it from /etc/apparmor.d/disable/.

  This behavior caused me some consternation as I was developing an
  alternate profile for a program that already had one, and I continued
  to see old behavior even though I had removed the old profile.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1878333/+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 1877528] Re: Applet does not terminate at end of X desktop session

[Daniel Richard G.]

Aaaand the upstream has decided they can't/won't fix this issue.

One thing that bothers me about this whole situation is that, in order
for background services like this one to be cleaned up after logout,
they need to behave "correctly." From my point of view, this is
backwards.

When the system is preparing to reboot, it first sends SIGTERM to all
user processes, waits a few seconds, and then sends SIGKILL. Processes
that behave correctly are allowed to close down cleanly, and those that
don't, are terminated forcibly. If you didn't have that SIGKILL part,
then one badly-behaving process could delay the reboot indefinitely. By
doing things this way, good behavior is rewarded, but not required.

Something like that should be the case for user sessions, although there
are exceptions (screen, tmux, nohup), and SIGKILL might be excessive.
The upstream bug mentioned a few other processes that remained visible
under session-status, and I myself have seen similar behavior from at-
spi2-core (haven't determined yet if a bug report is in order for that
one).

We're going to be fighting a losing battle if every single desktop
background service in Ubuntu has to do things correctly in order to
avoid keeping the session open after logout. There needs to be a
failsafe of some kind.

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

Title:
  Applet does not terminate at end of X desktop session

Status in System Config Printer:
  New
Status in lightdm package in Ubuntu:
  New
Status in sddm package in Ubuntu:
  New
Status in system-config-printer package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Invalid
Status in system-config-printer package in Debian:
  Unknown

Bug description:
  This concerns system-config-printer 1.5.12-0ubuntu1 in Ubuntu focal.

  I log into the Xfce desktop, and then logout. The screen returns to
  the LightDM login screen.

  A few minutes later, "loginctl list-sessions" shows the following:

  SESSION  UID USERSEAT  TTY  
90 root   
   c2 1000 skunk   seat0  
   c3  116 lightdm seat0  

  3 sessions listed.

  Output from "loginctl session-status c2":

  c2 - skunk (1000)
 Since: Fri 2020-05-08 03:09:05 EDT; 9min ago
Leader: 2530
  Seat: seat0; vc7
   Display: :0
   Service: lightdm; type x11; class user
   Desktop: xubuntu
 State: closing
  Unit: session-c2.scope
└─2856 /usr/bin/python3 
/usr/share/system-config-printer/applet.py

  This process sticks around forever until I kill it, or its parent
  "systemd --user" process. Only then does the session disappear from
  list-sessions.

  When I run "session-status" while I'm logged in, I see a list of
  nearly 30 desktop-related processes. All of them except this one go
  away on logout. This one should too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/system-config-printer/+bug/1877528/+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 1878469] [NEW] Ubuntu 20.04 causing green vertical stripes on my desktop

[Luca Palazzotto]

Public bug reported:

As soon as I upgraded to Ubuntu 20.04, two green pixel stripes appeared on my 
desktop.
They do not interfere with windows when opened, whether they are browsers, 
files or other items, and they do not seem to have an impact on the general 
behavior of the PC.

Still, something tells me that they are not supposed to be there.

I have a dual boot, Windows and Ubuntu, and two drivers:

VGA compatbile controller: Intel UHD Graphics 630 (mobile)
3D controller: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] 

Any support would be welcome.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-31.35-lowlatency 5.4.34
Uname: Linux 5.4.0-31-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed May 13 18:55:14 2020
DistUpgraded: 2020-05-13 13:02:22,581 DEBUG icon theme changed, re-reading
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c]
InstallationDate: Installed on 2018-12-23 (506 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
 Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications 
 Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9570
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-lowlatency 
root=UUID=d49b534b-1745-4089-80d9-cb11f85d2570 ro acpi=force 
nvidia.NVreg_EnableBacklightHandler=1
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-05-13 (0 days ago)
dmi.bios.date: 12/25/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.0
dmi.board.name: 0D0T05
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9570
dmi.product.sku: 087C
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
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/1878469

Title:
  Ubuntu 20.04 causing green vertical stripes on my desktop

Status in xorg package in Ubuntu:
  New

Bug description:
  As soon as I upgraded to Ubuntu 20.04, two green pixel stripes appeared on my 
desktop.
  They do not interfere with windows when opened, whether they are browsers, 
files or other items, and they do not seem to have an impact on the general 
behavior of the PC.

  Still, something tells me that they are not supposed to be there.

  I have a dual boot, Windows and Ubuntu, and two drivers:

  VGA compatbile controller: Intel UHD Graphics 630 (mobile)
  3D controller: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] 

  Any support would be welcome.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-31.35-lowlatency 5.4.34
  Uname: Linux 5.4.0-31-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 13 18:55:14 2020
  DistUpgraded: 2020-05-13 13:02:22,581 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c]
  InstallationDate: Installed on 2018-12-23 (506 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 00

[Touch-packages] [Bug 1878108] Re: new upstream release 2020a

[Brian Murray]

** Tags removed: verification-needed verification-needed-bionic 
verification-needed-eoan verification-needed-focal verification-needed-xenial
** Tags added: verification-done verification-done-bionic 
verification-done-eoan verification-done-focal verification-done-xenial

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

Title:
  new upstream release 2020a

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Trusty:
  New
Status in tzdata source package in Xenial:
  Fix Committed
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Eoan:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed

Bug description:
  There is a new upstream release of tzdata, 2020, which includes the
  following:

    * New upstream release, affecting past and future timestamps:
  - Morocco springs forward on 2020-05-31, not 2020-05-24.
  - Canada's Yukon advanced to -07 year-round on 2020-03-08.
  - America/Nuuk renamed from America/Godthab.

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with "zdump -v
  $region/$timezone_that_changed" (this needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".]
  This is compared to the same output after the updated package got
  installed. If those are different the verification is considered done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1878108/+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 495418] Re: Enable GSSAPI support (for likewise-open)

[Andreas Hasenack]

I'm trying[1] to back this out, but it will remove symbols from the
library without bumping the soname. Our next chance is when openldap 2.5
comes out, which will likely bump the soname.


1. 
https://code.launchpad.net/~ahasenack/ubuntu/+source/openldap/+git/openldap/+merge/383797

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

Title:
  Enable GSSAPI support (for likewise-open)

Status in openldap package in Ubuntu:
  Fix Released

Bug description:
  Proposed patch does two things:

  (a) Adds the --with-gssapi autoconf option necessary to
  enable code in libraries/libldap/gssapi.c (i.e #define HAVE_GSSAPI).
  This option was present in 2.4.16 from what I can tell but is not in the 
2.4.18 code in
  lucid.

  (b) Makes guess_service_principal() more robust when trying
  to determine what principal name to use (based on the hostname
  or dns name) when binding to a server.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/495418/+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 1877454] Re: openssh-server hangs with AuthorizedKeysCommand

[Sergio Durigan Junior]

** Description changed:

  [Impact]
  
  On a default Xenial install, when sshd is configured to obtain the list
  of allowed keys using AuthorizedKeysCommand (or the list of allowed
  certificate principals using AuthorizedPrincipalsCommand), and if the
  command pointed by Authorized{Keys,Principals}Command generates a lot of
  output, sshd will hang while reading this same output. In a nutshell,
  the problem happens when the subprocess generates enough data to fill
  the pipe's buffer; in this scenario, sshd will wait(2) on the
  subprocess, which will be blocked trying to write the rest of the
  output.
  
  [Test Case]
  
  In order to reproduce the bug, one can:
  
  $ lxc launch ubuntu-daily:xenial openssh-server-bug1877454
  $ lxc shell openssh-server-bug1877454
  # ssh-keygen
  (no need to choose a passphrase for the key, just hit ENTER on all prompts)
  # cat > authkeyscommand.sh << __EOF__
  #!/bin/bash
  
  cat /root/.ssh/id_rsa.pub
  echo
  head -c 1M < /dev/urandom
  __EOF__
+ # chmod +x authkeyscommand.sh
  # cat >> /etc/ssh/sshd_config << __EOF__
  AuthorizedKeysCommand /root/authkeyscommand.sh
  AuthorizedKeysCommandUser root
  __EOF__
  # systemctl reload sshd.service
  # ssh root@127.0.0.1
  
  You will notice that ssh will stay there waiting for sshd's reply, which
  won't come.  The expected result would be for ssh to succeed.
  
  [Regression Potential]
  
  Since the affected code deals with executing a subprocess, reading its
  output through a pipe, and then relying on wait(2) to determine whether
  the subprocess exited correctly; and considering that this code is
  written in C without the help of features like RAII and with the use of
  goto statements, we are not able to disconsider the chances of making a
  mistake and forgetting to free a resource or to properly read/write
  from/to pipes, for example.  This is, after all, the reason the bug
  happened in the first place.
  
  Having said that, openssh contains extensive tests and the code is well
  organized and relatively easy to follow.  Upon close inspection, there
  doesn't seem to be an evident problem with the backported fixes.
  
  As usual when dealing with a somewhat older distribution, there is
  always the possibility of encountering problems because we will be
  recompiling openssh using the most recent versions of its build
  dependencies.
  
  [Original Description]
  
  Please consider applying this change to openssh-server distributed in Xenial 
(16.04).
  Without it, sshd can sporadically hang when making use of the 
`AuthorizedKeysCommand` option.
  
  https://github.com/openssh/openssh-
  portable/commit/ddd3d34e5c7979ca6f4a3a98a7d219a4ed3d98c2

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

Title:
  openssh-server hangs with AuthorizedKeysCommand

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Xenial:
  Confirmed

Bug description:
  [Impact]

  On a default Xenial install, when sshd is configured to obtain the
  list of allowed keys using AuthorizedKeysCommand (or the list of
  allowed certificate principals using AuthorizedPrincipalsCommand), and
  if the command pointed by Authorized{Keys,Principals}Command generates
  a lot of output, sshd will hang while reading this same output. In a
  nutshell, the problem happens when the subprocess generates enough
  data to fill the pipe's buffer; in this scenario, sshd will wait(2) on
  the subprocess, which will be blocked trying to write the rest of the
  output.

  [Test Case]

  In order to reproduce the bug, one can:

  $ lxc launch ubuntu-daily:xenial openssh-server-bug1877454
  $ lxc shell openssh-server-bug1877454
  # ssh-keygen
  (no need to choose a passphrase for the key, just hit ENTER on all prompts)
  # cat > authkeyscommand.sh << __EOF__
  #!/bin/bash

  cat /root/.ssh/id_rsa.pub
  echo
  head -c 1M < /dev/urandom
  __EOF__
  # chmod +x authkeyscommand.sh
  # cat >> /etc/ssh/sshd_config << __EOF__
  AuthorizedKeysCommand /root/authkeyscommand.sh
  AuthorizedKeysCommandUser root
  __EOF__
  # systemctl reload sshd.service
  # ssh root@127.0.0.1

  You will notice that ssh will stay there waiting for sshd's reply,
  which won't come.  The expected result would be for ssh to succeed.

  [Regression Potential]

  Since the affected code deals with executing a subprocess, reading its
  output through a pipe, and then relying on wait(2) to determine
  whether the subprocess exited correctly; and considering that this
  code is written in C without the help of features like RAII and with
  the use of goto statements, we are not able to disconsider the chances
  of making a mistake and forgetting to free a resource or to properly
  read/write from/to pipes, for example.  This is, after all, the reason
  the bug happened in the first place.

  Having said that, openssh contains extens

[Touch-packages] [Bug 1878108] Re: new upstream release 2020a

[Brian Murray]

The tzdata update on Ubuntu 16.04 LTS is good too.

Get:1 https://ubuntu.osuosl.org/ubuntu xenial-proposed/main amd64 tzdata all 
2020a-0ubuntu0.16.04 [168 kB]
Fetched 168 kB in 2s (73.8 kB/s) 
Preconfiguring packages ...
(Reading database ... 359323 files and directories currently installed.)
Preparing to unpack .../tzdata_2020a-0ubuntu0.16.04_all.deb ...
Unpacking tzdata (2020a-0ubuntu0.16.04) over (2019c-0ubuntu0.16.04) ...
Setting up tzdata (2020a-0ubuntu0.16.04) ...

Current default time zone: 'America/Los_Angeles'
Local time is now:  Wed May 13 11:22:04 PDT 2020.
Universal Time is now:  Wed May 13 18:22:04 UTC 2020.
Run 'dpkg-reconfigure tzdata' if you wish to change it.

bdmurray@clean-xenial-amd64:~$ zdump -v "Africa/Casablanca" > after-update.txt
bdmurray@clean-xenial-amd64:~$ diff -Nurp before-update.txt after-update.txt | 
head -n20
--- before-update.txt   2020-05-13 11:21:29.77600 -0700
+++ after-update.txt2020-05-13 11:22:23.490514776 -0700
@@ -116,8 +116,8 @@ Africa/Casablanca  Sun Jun  9 01:59:59 2
 Africa/Casablanca  Sun Jun  9 02:00:00 2019 UT = Sun Jun  9 03:00:00 2019 +01 
isdst=0 gmtoff=3600
 Africa/Casablanca  Sun Apr 19 01:59:59 2020 UT = Sun Apr 19 02:59:59 2020 +01 
isdst=0 gmtoff=3600
 Africa/Casablanca  Sun Apr 19 02:00:00 2020 UT = Sun Apr 19 02:00:00 2020 +00 
isdst=1 gmtoff=0
-Africa/Casablanca  Sun May 24 01:59:59 2020 UT = Sun May 24 01:59:59 2020 +00 
isdst=1 gmtoff=0
-Africa/Casablanca  Sun May 24 02:00:00 2020 UT = Sun May 24 03:00:00 2020 +01 
isdst=0 gmtoff=3600
+Africa/Casablanca  Sun May 31 01:59:59 2020 UT = Sun May 31 01:59:59 2020 +00 
isdst=1 gmtoff=0
+Africa/Casablanca  Sun May 31 02:00:00 2020 UT = Sun May 31 03:00:00 2020 +01 
isdst=0 gmtoff=3600
 Africa/Casablanca  Sun Apr 11 01:59:59 2021 UT = Sun Apr 11 02:59:59 2021 +01 
isdst=0 gmtoff=3600
 Africa/Casablanca  Sun Apr 11 02:00:00 2021 UT = Sun Apr 11 02:00:00 2021 +00 
isdst=1 gmtoff=0
 Africa/Casablanca  Sun May 16 01:59:59 2021 UT = Sun May 16 01:59:59 2021 +00 
isdst=1 gmtoff=0

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

Title:
  new upstream release 2020a

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Trusty:
  New
Status in tzdata source package in Xenial:
  Fix Committed
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Eoan:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed

Bug description:
  There is a new upstream release of tzdata, 2020, which includes the
  following:

    * New upstream release, affecting past and future timestamps:
  - Morocco springs forward on 2020-05-31, not 2020-05-24.
  - Canada's Yukon advanced to -07 year-round on 2020-03-08.
  - America/Nuuk renamed from America/Godthab.

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with "zdump -v
  $region/$timezone_that_changed" (this needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".]
  This is compared to the same output after the updated package got
  installed. If those are different the verification is considered done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1878108/+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 1872443] Re: /etc/securetty missing: dovecot not working

[Kai Kasurinen]

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

** This bug has been marked a duplicate of bug 1860826
   pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory

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

Title:
  /etc/securetty missing: dovecot not working

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  With Ubuntu 20.04 Focal Fossa, /etc/securetty is missing from the
  "login" package (4.8.1-1ubuntu4).

  This leads to errors such as in /var/log/mail.log when a dovecot auth
  is tried:

  Apr 13 13:08:17 venus dovecot[10588]: imap-login: Login: user=, 
method=PLAIN,
  rip=192.168.123.1, lip=192.168.123.188, mpid=12200, TLS, TLSv1.2 with cipher 
ECDHE-E
  CDSA-AES256-GCM-SHA384 (256/256 bits)
  Apr 13 13:08:18 venus auth[12195]: pam_unix(dovecot:auth): Couldn't open 
/etc/secure
  tty: No such file or directory
  Apr 13 13:08:18 venus auth[12195]: pam_unix(dovecot:auth): Couldn't open 
/etc/secure
  tty: No such file or directory
  Apr 13 13:08:18 venus dovecot[10588]: imap-login: Login: user=, 
method=PLAIN,
  rip=192.168.123.1, lip=192.168.123.188, mpid=12202, TLS, TLSv1.2 with cipher 
ECDHE-E
  CDSA-AES256-GCM-SHA384 (256/256 bits)

  It seems that pam_unix still needs /etc/securetty, but login no longer
  provides it.

  There was a similar bug in debian that seems to be related:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931899

  To my understanding, this is a problem between pam and login packages
  in 20.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1872443/+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 1878108] Re: new upstream release 2020a

[Brian Murray]

The tzdata update on Ubuntu 18.04 LTS is good too.

Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 tzdata all 
2020a-0ubuntu0.18.04 [190 kB]
Fetched 190 kB in 1s (189 kB/s)
Preconfiguring packages ...
(Reading database ... 202126 files and directories currently installed.)
Preparing to unpack .../tzdata_2020a-0ubuntu0.18.04_all.deb ...
Unpacking tzdata (2020a-0ubuntu0.18.04) over (2019c-0ubuntu0.18.04) ...
Setting up tzdata (2020a-0ubuntu0.18.04) ...

Current default time zone: 'America/Los_Angeles'
Local time is now:  Wed May 13 11:15:39 PDT 2020.
Universal Time is now:  Wed May 13 18:15:39 UTC 2020.
Run 'dpkg-reconfigure tzdata' if you wish to change it.

bdmurray@clean-bionic-amd64:~$ zdump -v "Africa/Casablanca" > after-update.txt
bdmurray@clean-bionic-amd64:~$ diff -Nurp before-update.txt after-update.txt | 
head -n 20
--- before-update.txt   2020-05-13 11:13:28.433873105 -0700
+++ after-update.txt2020-05-13 11:16:49.030851720 -0700
@@ -116,8 +116,8 @@ Africa/Casablanca  Sun Jun  9 01:59:59 2
 Africa/Casablanca  Sun Jun  9 02:00:00 2019 UT = Sun Jun  9 03:00:00 2019 +01 
isdst=0 gmtoff=3600
 Africa/Casablanca  Sun Apr 19 01:59:59 2020 UT = Sun Apr 19 02:59:59 2020 +01 
isdst=0 gmtoff=3600
 Africa/Casablanca  Sun Apr 19 02:00:00 2020 UT = Sun Apr 19 02:00:00 2020 +00 
isdst=1 gmtoff=0
-Africa/Casablanca  Sun May 24 01:59:59 2020 UT = Sun May 24 01:59:59 2020 +00 
isdst=1 gmtoff=0
-Africa/Casablanca  Sun May 24 02:00:00 2020 UT = Sun May 24 03:00:00 2020 +01 
isdst=0 gmtoff=3600
+Africa/Casablanca  Sun May 31 01:59:59 2020 UT = Sun May 31 01:59:59 2020 +00 
isdst=1 gmtoff=0
+Africa/Casablanca  Sun May 31 02:00:00 2020 UT = Sun May 31 03:00:00 2020 +01 
isdst=0 gmtoff=3600
 Africa/Casablanca  Sun Apr 11 01:59:59 2021 UT = Sun Apr 11 02:59:59 2021 +01 
isdst=0 gmtoff=3600
 Africa/Casablanca  Sun Apr 11 02:00:00 2021 UT = Sun Apr 11 02:00:00 2021 +00 
isdst=1 gmtoff=0
 Africa/Casablanca  Sun May 16 01:59:59 2021 UT = Sun May 16 01:59:59 2021 +00 
isdst=1 gmtoff=0

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

Title:
  new upstream release 2020a

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Trusty:
  New
Status in tzdata source package in Xenial:
  Fix Committed
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Eoan:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed

Bug description:
  There is a new upstream release of tzdata, 2020, which includes the
  following:

    * New upstream release, affecting past and future timestamps:
  - Morocco springs forward on 2020-05-31, not 2020-05-24.
  - Canada's Yukon advanced to -07 year-round on 2020-03-08.
  - America/Nuuk renamed from America/Godthab.

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with "zdump -v
  $region/$timezone_that_changed" (this needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".]
  This is compared to the same output after the updated package got
  installed. If those are different the verification is considered done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1878108/+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 1878108] Re: new upstream release 2020a

[Brian Murray]

The update is good on Ubuntu 19.10 too.

After this operation, 2,048 B of additional disk space will be used.
Get:1 http://192.168.10.7/ubuntu eoan-proposed/main amd64 tzdata all 
2020a-0ubuntu0.19.10 [208 kB]
Fetched 208 kB in 0s (2,986 kB/s)
Preconfiguring packages ...
(Reading database ... 186389 files and directories currently installed.)
Preparing to unpack .../tzdata_2020a-0ubuntu0.19.10_all.deb ...
Unpacking tzdata (2020a-0ubuntu0.19.10) over (2019c-3) ...
Setting up tzdata (2020a-0ubuntu0.19.10) ...

Current default time zone: 'America/Los_Angeles'
Local time is now:  Wed May 13 11:03:39 PDT 2020.
Universal Time is now:  Wed May 13 18:03:39 UTC 2020.
Run 'dpkg-reconfigure tzdata' if you wish to change it.

bdmurray@clean-eoan-amd64:~$ zdump -v "Africa/Casablanca" > after-update.txt
bdmurray@clean-eoan-amd64:~$ diff -Nurp before-update.txt after-update.txt | 
head -n 20
--- before-update.txt   2020-05-13 11:03:14.006746703 -0700
+++ after-update.txt2020-05-13 11:09:57.982200456 -0700
@@ -116,8 +116,8 @@ Africa/Casablanca  Sun Jun  9 01:59:59 2
 Africa/Casablanca  Sun Jun  9 02:00:00 2019 UT = Sun Jun  9 03:00:00 2019 +01 
isdst=0 gmtoff=3600
 Africa/Casablanca  Sun Apr 19 01:59:59 2020 UT = Sun Apr 19 02:59:59 2020 +01 
isdst=0 gmtoff=3600
 Africa/Casablanca  Sun Apr 19 02:00:00 2020 UT = Sun Apr 19 02:00:00 2020 +00 
isdst=1 gmtoff=0
-Africa/Casablanca  Sun May 24 01:59:59 2020 UT = Sun May 24 01:59:59 2020 +00 
isdst=1 gmtoff=0
-Africa/Casablanca  Sun May 24 02:00:00 2020 UT = Sun May 24 03:00:00 2020 +01 
isdst=0 gmtoff=3600
+Africa/Casablanca  Sun May 31 01:59:59 2020 UT = Sun May 31 01:59:59 2020 +00 
isdst=1 gmtoff=0
+Africa/Casablanca  Sun May 31 02:00:00 2020 UT = Sun May 31 03:00:00 2020 +01 
isdst=0 gmtoff=3600
 Africa/Casablanca  Sun Apr 11 01:59:59 2021 UT = Sun Apr 11 02:59:59 2021 +01 
isdst=0 gmtoff=3600
 Africa/Casablanca  Sun Apr 11 02:00:00 2021 UT = Sun Apr 11 02:00:00 2021 +00 
isdst=1 gmtoff=0
 Africa/Casablanca  Sun May 16 01:59:59 2021 UT = Sun May 16 01:59:59 2021 +00 
isdst=1 gmtoff=0

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

Title:
  new upstream release 2020a

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Trusty:
  New
Status in tzdata source package in Xenial:
  Fix Committed
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Eoan:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed

Bug description:
  There is a new upstream release of tzdata, 2020, which includes the
  following:

    * New upstream release, affecting past and future timestamps:
  - Morocco springs forward on 2020-05-31, not 2020-05-24.
  - Canada's Yukon advanced to -07 year-round on 2020-03-08.
  - America/Nuuk renamed from America/Godthab.

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with "zdump -v
  $region/$timezone_that_changed" (this needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".]
  This is compared to the same output after the updated package got
  installed. If those are different the verification is considered done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1878108/+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 1878108] Re: new upstream release 2020a

[Brian Murray]

The verification for focal looks good to me.

Get:1 http://192.168.10.7/ubuntu focal-proposed/main amd64 tzdata all 
2020a-0ubuntu0.20.04 [293 kB]
Fetched 293 kB in 0s (3,516 kB/s)
Preconfiguring packages ...
(Reading database ... 258739 files and directories currently installed.)
Preparing to unpack .../tzdata_2020a-0ubuntu0.20.04_all.deb ...
Unpacking tzdata (2020a-0ubuntu0.20.04) over (2019c-3ubuntu1) ...
Setting up tzdata (2020a-0ubuntu0.20.04) ...

Current default time zone: 'America/Los_Angeles'
Local time is now:  Wed May 13 10:54:43 PDT 2020.
Universal Time is now:  Wed May 13 17:54:43 UTC 2020.
Run 'dpkg-reconfigure tzdata' if you wish to change it.

bdmurray@clean-focal-amd64:~$ zdump -v Africa/Casablanca > after-update.txt
bdmurray@clean-focal-amd64:~$ diff -Nurp before-update.txt after-update.txt
--- before-update.txt   2020-05-13 10:51:49.783893730 -0700
+++ after-update.txt2020-05-13 10:54:58.547750187 -0700
@@ -116,8 +116,8 @@ Africa/Casablanca  Sun Jun  9 01:59:59 2
 Africa/Casablanca  Sun Jun  9 02:00:00 2019 UT = Sun Jun  9 03:00:00 2019 +01 
isdst=0 gmtoff=3600
 Africa/Casablanca  Sun Apr 19 01:59:59 2020 UT = Sun Apr 19 02:59:59 2020 +01 
isdst=0 gmtoff=3600
 Africa/Casablanca  Sun Apr 19 02:00:00 2020 UT = Sun Apr 19 02:00:00 2020 +00 
isdst=1 gmtoff=0
-Africa/Casablanca  Sun May 24 01:59:59 2020 UT = Sun May 24 01:59:59 2020 +00 
isdst=1 gmtoff=0
-Africa/Casablanca  Sun May 24 02:00:00 2020 UT = Sun May 24 03:00:00 2020 +01 
isdst=0 gmtoff=3600
+Africa/Casablanca  Sun May 31 01:59:59 2020 UT = Sun May 31 01:59:59 2020 +00 
isdst=1 gmtoff=0
+Africa/Casablanca  Sun May 31 02:00:00 2020 UT = Sun May 31 03:00:00 2020 +01 
isdst=0 gmtoff=3600
 Africa/Casablanca  Sun Apr 11 01:59:59 2021 UT = Sun Apr 11 02:59:59 2021 +01 
isdst=0 gmtoff=3600
 Africa/Casablanca  Sun Apr 11 02:00:00 2021 UT = Sun Apr 11 02:00:00 2021 +00 
isdst=1 gmtoff=0
 Africa/Casablanca  Sun May 16 01:59:59 2021 UT = Sun May 16 01:59:59 2021 +00 
isdst=1 gmtoff=0

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

Title:
  new upstream release 2020a

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Trusty:
  New
Status in tzdata source package in Xenial:
  Fix Committed
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Eoan:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed

Bug description:
  There is a new upstream release of tzdata, 2020, which includes the
  following:

    * New upstream release, affecting past and future timestamps:
  - Morocco springs forward on 2020-05-31, not 2020-05-24.
  - Canada's Yukon advanced to -07 year-round on 2020-03-08.
  - America/Nuuk renamed from America/Godthab.

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with "zdump -v
  $region/$timezone_that_changed" (this needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".]
  This is compared to the same output after the updated package got
  installed. If those are different the verification is considered done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1878108/+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 1878333] Re: AppArmor cache entries not removed when profile is deleted

[John Johansen]

Daniel,

Right the profile should be removed on reboot, or service restart,
having stale cache files loaded is a huge problem.

It is the auto-cleanup of old cache files when a profile is manually
deleted/renamed that is a wishlist item.

With this clarification I am moving this from wishlist back to
undecided. And will look into this further.


** Changed in: apparmor (Ubuntu)
   Importance: Wishlist => Undecided

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

Title:
  AppArmor cache entries not removed when profile is deleted

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  This concerns apparmor 2.13.3-7ubuntu5 in Ubuntu focal.

  If I delete a profile from /etc/apparmor.d/, reboot the system, and
  then look in /var/cache/apparmor/.0/, I still see a file for
  the compiled form of the profile.

  The same occurs if the profile is "deleted" by other means, such as
  symlinking it from /etc/apparmor.d/disable/.

  This behavior caused me some consternation as I was developing an
  alternate profile for a program that already had one, and I continued
  to see old behavior even though I had removed the old profile.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1878333/+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 1875910] Re: Command to update mirror list

[Julian Andres Klode]

On the (python-apt) client side, this involves adding an apt.conf
snippet to configure a new index target and then change the code to read
from there.

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

Title:
  Command to update mirror list

Status in Launchpad itself:
  New
Status in python-apt package in Ubuntu:
  Triaged

Bug description:
  I see a lot of issues regarding outdated Ubuntu.mirrors file, I think
  there should be a command that imports the list of mirrors from
  https://launchpad.net/ubuntu/+archivemirrors and updates the
  templates/Ubuntu.mirrors file, then in the UI add a button that can
  update the list of Mirrors. I don't see the point of needing a new
  release every time the list needs to be updated.

  I want a mirror that was updated yesterday, because is the closest to
  my location, but it is not in the list, and as you can see there are
  lots of issues from people that could have been avoided with this.

  This is not really a bug, but a feature.
  Also could be great if there was some kind of filter, like if you select now 
in Ubuntu 19.10 a ftp mirror and update it will fail, and the UI gets broken 
(you can't even close the window, you have to kill it), so doing this update 
should just import those mirrors that are safe to use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1875910/+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 1875910] Re: Command to update mirror list

[Julian Andres Klode]

Mirror lists change on a daily basis, python-apt on less than a point
release basis (it should update mirror lists before point release, but
this does not always happen afaict).

** Changed in: python-apt (Ubuntu)
   Importance: Undecided => High

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

Title:
  Command to update mirror list

Status in Launchpad itself:
  New
Status in python-apt package in Ubuntu:
  Triaged

Bug description:
  I see a lot of issues regarding outdated Ubuntu.mirrors file, I think
  there should be a command that imports the list of mirrors from
  https://launchpad.net/ubuntu/+archivemirrors and updates the
  templates/Ubuntu.mirrors file, then in the UI add a button that can
  update the list of Mirrors. I don't see the point of needing a new
  release every time the list needs to be updated.

  I want a mirror that was updated yesterday, because is the closest to
  my location, but it is not in the list, and as you can see there are
  lots of issues from people that could have been avoided with this.

  This is not really a bug, but a feature.
  Also could be great if there was some kind of filter, like if you select now 
in Ubuntu 19.10 a ftp mirror and update it will fail, and the UI gets broken 
(you can't even close the window, you have to kill it), so doing this update 
should just import those mirrors that are safe to use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1875910/+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 1875910] Re: Command to update mirror list

[Julian Andres Klode]

I think Launchpad should start shipping mirror lists in -updates pocket
(only; probably), so that we can update the mirror lists of installed
systems as part of apt update and don't have to rebuild python-apt and
upgrade everywhere.

** Also affects: launchpad
   Importance: Undecided
   Status: New

** Changed in: python-apt (Ubuntu)
   Status: New => Triaged

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

Title:
  Command to update mirror list

Status in Launchpad itself:
  New
Status in python-apt package in Ubuntu:
  Triaged

Bug description:
  I see a lot of issues regarding outdated Ubuntu.mirrors file, I think
  there should be a command that imports the list of mirrors from
  https://launchpad.net/ubuntu/+archivemirrors and updates the
  templates/Ubuntu.mirrors file, then in the UI add a button that can
  update the list of Mirrors. I don't see the point of needing a new
  release every time the list needs to be updated.

  I want a mirror that was updated yesterday, because is the closest to
  my location, but it is not in the list, and as you can see there are
  lots of issues from people that could have been avoided with this.

  This is not really a bug, but a feature.
  Also could be great if there was some kind of filter, like if you select now 
in Ubuntu 19.10 a ftp mirror and update it will fail, and the UI gets broken 
(you can't even close the window, you have to kill it), so doing this update 
should just import those mirrors that are safe to use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1875910/+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 1877233] Re: Remove inactive Mirrors to Colombia

[Julian Andres Klode]

I don't think it's worth tracking this. There are a ton of mirror
changes on a daily basis, and we can't update the python-apt package
that often.

Releases that will get a point release should get a python-apt update
for that.

Other releases will get the mirror update together with a regular
update.

FWIW, a regular update is in the unapproved queue for all releases.


** Changed in: python-apt (Ubuntu Bionic)
   Status: Triaged => Invalid

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

Title:
  Remove inactive Mirrors to Colombia

Status in Ubuntu:
  Invalid
Status in python-apt package in Ubuntu:
  Fix Released
Status in The Bionic Beaver:
  Invalid
Status in python-apt source package in Bionic:
  Invalid

Bug description:
  Hallo,

  Our mirror at the mirror.upb.edu.co is being hosted any longer but it
  is still showing up on the "Software & Updates" application. Could you
  please remove it? The server is already removed from this list
  https://launchpad.net/ubuntu/+archivemirrors in the Colombia section.

  Thanks a lot.

  Present on bionic (18.04)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1877233/+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 1877233] Re: Remove inactive Mirrors to Colombia

[Julian Andres Klode]

My goal for future releases is to shift that info out of the python-apt
package and into the -updates pocket of the archive, so that the mirror
list is updated as part of apt update.

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

Title:
  Remove inactive Mirrors to Colombia

Status in Ubuntu:
  Invalid
Status in python-apt package in Ubuntu:
  Fix Released
Status in The Bionic Beaver:
  Invalid
Status in python-apt source package in Bionic:
  Invalid

Bug description:
  Hallo,

  Our mirror at the mirror.upb.edu.co is being hosted any longer but it
  is still showing up on the "Software & Updates" application. Could you
  please remove it? The server is already removed from this list
  https://launchpad.net/ubuntu/+archivemirrors in the Colombia section.

  Thanks a lot.

  Present on bionic (18.04)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1877233/+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 997333] Re: ubuntu-bug refuses to file bug reports for packages that aren't installed due to packaging problems

[Tessa]

@brian-murray: oh! when I first tried it after upgrading, it didn't
spawn the details window or open the web browser link or anything. it
appears to be working now, so it must've just been a fluke. definitely
looks better!

** Changed in: apport (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  ubuntu-bug refuses to file bug reports for packages that aren't
  installed due to packaging problems

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu-bug makes it very difficult to file package problem bugs for
  packages that won't install (due to said problems), because it refuses
  to open a bug for a package that isn't installed. If a package isn't
  installed, I'd recommend that ubuntu-bug collect information about the
  package and its dependencies as seen from the local apt cache, as well
  as any conflicts that prevent it from being installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: apport 2.0.1-0ubuntu7
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportLog:
   
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Wed May  9 13:49:29 2012
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to precise on 2012-05-02 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/997333/+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 1877233] Re: Remove inactive Mirrors to Colombia

[Jhosman Lizarazo]

Hello Julian And Brian

All versions of Ubuntu are affected.

they should only appear:

 
mirror.unimagdalena.edu.co
co.archive.ubuntu.com

You can see log of status in: https://status.ubuntu-co.com/

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

Title:
  Remove inactive Mirrors to Colombia

Status in Ubuntu:
  Invalid
Status in python-apt package in Ubuntu:
  Fix Released
Status in The Bionic Beaver:
  Invalid
Status in python-apt source package in Bionic:
  Triaged

Bug description:
  Hallo,

  Our mirror at the mirror.upb.edu.co is being hosted any longer but it
  is still showing up on the "Software & Updates" application. Could you
  please remove it? The server is already removed from this list
  https://launchpad.net/ubuntu/+archivemirrors in the Colombia section.

  Thanks a lot.

  Present on bionic (18.04)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1877233/+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 1861408] Re: firefox apparmor messages

[Launchpad Bug Tracker]

This bug was fixed in the package firefox - 76.0.1+build1-0ubuntu2

---
firefox (76.0.1+build1-0ubuntu2) groovy; urgency=medium

  * Update apparmor profile to allow lsb_release to run with more recent
versions of Python 3 (LP: #1861408)
- debian/usr.bin.firefox.apparmor.14.10
  * Work around clang hanging forever when trying to optimize the build of the
embedded copy of sqlite3 (LP: #1878292)
- debian/patches/s390x-workaround-sqlite3-clang-optimization-hang.patch

 -- Olivier Tilloy   Tue, 12 May 2020
23:11:11 +0200

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

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

Title:
  firefox apparmor messages

Status in apparmor package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
  19.3.

  i see there is newer ubuntu version in
  
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
  , 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
  apparmor.

  i have not found a page for firefox bugs in linux mint sites, so i
  belive i should report here. but i have also asked about that in linux
  mint's irc and then github.

  i have enabled apparmor for firefox and see these types of messages in
  syslog:

  Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
  [system] Activating via systemd: service
  name='org.freedesktop.hostname1' unit='dbus-
  org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
  pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")

  Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5525.077960] audit: type=1400 audit(1580226276.440:27):
  apparmor="DENIED" operation="capable"
  profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
  comm="firefox" capability=21  capname="sys_admin"

  Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
  uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/RealtimeKit1"
  interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
  name="org.freedesktop.RealtimeKit1" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
  member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/Private/RemoteVolumeMonitor"
  interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
  mask="send" name=":1.35" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
  member="ListMounts2" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
  member="LookupMount" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
  [system] Activating via systemd: service
  name='org.freedesktop.hostname1' unit='dbus-
  org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
  pid=15948 comm="/usr/lib/firefox/firefox "
  label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")

  Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
  uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/hostname1"
  interface="org.freedesktop.DBus.Properties" member="GetAll"
  mask="send" name=":1.120" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177
  peer_label="unconfined"

  Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
  member="Change" mask=

[Touch-packages] [Bug 1877233] Re: Remove inactive Mirrors to Colombia

[Julian Andres Klode]

We do not update mirror lists on their own, except for point releases,
and as part of other updates (the python-apt release process
automatically triggers mirror list updates, so this bug won't be
updated).

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

Title:
  Remove inactive Mirrors to Colombia

Status in Ubuntu:
  Invalid
Status in python-apt package in Ubuntu:
  Fix Released
Status in The Bionic Beaver:
  Invalid
Status in python-apt source package in Bionic:
  Triaged

Bug description:
  Hallo,

  Our mirror at the mirror.upb.edu.co is being hosted any longer but it
  is still showing up on the "Software & Updates" application. Could you
  please remove it? The server is already removed from this list
  https://launchpad.net/ubuntu/+archivemirrors in the Colombia section.

  Thanks a lot.

  Present on bionic (18.04)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1877233/+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 1877454] Re: openssh-server hangs with AuthorizedKeysCommand

[Sergio Durigan Junior]

** Description changed:

+ [Impact]
+ 
+ On a default Xenial install, when sshd is configured to obtain the list
+ of allowed keys using AuthorizedKeysCommand (or the list of allowed
+ certificate principals using AuthorizedPrincipalsCommand), and if the
+ command pointed by Authorized{Keys,Principals}Command generates a lot of
+ output, sshd will hang while reading this same output. In a nutshell,
+ the problem happens when the subprocess generates enough data to fill
+ the pipe's buffer; in this scenario, sshd will wait(2) on the
+ subprocess, which will be blocked trying to write the rest of the
+ output.
+ 
+ [Test Case]
+ 
+ In order to reproduce the bug, one can:
+ 
+ $ lxc launch ubuntu-daily:xenial openssh-server-bug1877454
+ $ lxc shell openssh-server-bug1877454
+ # ssh-keygen
+ (no need to choose a passphrase for the key, just hit ENTER on all prompts)
+ # cat > authkeyscommand.sh << __EOF__
+ #!/bin/bash
+ 
+ cat /root/.ssh/id_rsa.pub
+ echo
+ head -c 1M < /dev/urandom
+ __EOF__
+ # cat >> /etc/ssh/sshd_config << __EOF__
+ AuthorizedKeysCommand /root/authkeyscommand.sh
+ AuthorizedKeysCommandUser root
+ __EOF__
+ # systemctl reload sshd.service
+ # ssh root@127.0.0.1
+ 
+ You will notice that ssh will stay there waiting for sshd's reply, which
+ won't come.  The expected result would be for ssh to succeed.
+ 
+ [Regression Potential]
+ 
+ Since the affected code deals with executing a subprocess, reading its
+ output through a pipe, and then relying on wait(2) to determine whether
+ the subprocess exited correctly; and considering that this code is
+ written in C without the help of features like RAII and with the use of
+ goto statements, we are not able to disconsider the chances of making a
+ mistake and forgetting to free a resource or to properly read/write
+ from/to pipes, for example.  This is, after all, the reason the bug
+ happened in the first place.
+ 
+ Having said that, openssh contains extensive tests and the code is well
+ organized and relatively easy to follow.  Upon close inspection, there
+ doesn't seem to be an evident problem with the backported fixes.
+ 
+ As usual when dealing with a somewhat older distribution, there is
+ always the possibility of encountering problems because we will be
+ recompiling openssh using the most recent versions of its build
+ dependencies.
+ 
+ [Original Description]
+ 
  Please consider applying this change to openssh-server distributed in Xenial 
(16.04).
  Without it, sshd can sporadically hang when making use of the 
`AuthorizedKeysCommand` option.
  
  https://github.com/openssh/openssh-
  portable/commit/ddd3d34e5c7979ca6f4a3a98a7d219a4ed3d98c2

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

Title:
  openssh-server hangs with AuthorizedKeysCommand

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Xenial:
  Confirmed

Bug description:
  [Impact]

  On a default Xenial install, when sshd is configured to obtain the
  list of allowed keys using AuthorizedKeysCommand (or the list of
  allowed certificate principals using AuthorizedPrincipalsCommand), and
  if the command pointed by Authorized{Keys,Principals}Command generates
  a lot of output, sshd will hang while reading this same output. In a
  nutshell, the problem happens when the subprocess generates enough
  data to fill the pipe's buffer; in this scenario, sshd will wait(2) on
  the subprocess, which will be blocked trying to write the rest of the
  output.

  [Test Case]

  In order to reproduce the bug, one can:

  $ lxc launch ubuntu-daily:xenial openssh-server-bug1877454
  $ lxc shell openssh-server-bug1877454
  # ssh-keygen
  (no need to choose a passphrase for the key, just hit ENTER on all prompts)
  # cat > authkeyscommand.sh << __EOF__
  #!/bin/bash

  cat /root/.ssh/id_rsa.pub
  echo
  head -c 1M < /dev/urandom
  __EOF__
  # cat >> /etc/ssh/sshd_config << __EOF__
  AuthorizedKeysCommand /root/authkeyscommand.sh
  AuthorizedKeysCommandUser root
  __EOF__
  # systemctl reload sshd.service
  # ssh root@127.0.0.1

  You will notice that ssh will stay there waiting for sshd's reply,
  which won't come.  The expected result would be for ssh to succeed.

  [Regression Potential]

  Since the affected code deals with executing a subprocess, reading its
  output through a pipe, and then relying on wait(2) to determine
  whether the subprocess exited correctly; and considering that this
  code is written in C without the help of features like RAII and with
  the use of goto statements, we are not able to disconsider the chances
  of making a mistake and forgetting to free a resource or to properly
  read/write from/to pipes, for example.  This is, after all, the reason
  the bug happened in the first place.

  Having said that, openssh contains extensive tests and the code is
  well organized and relatively easy t

[Touch-packages] [Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem

[Wittawat Jitkrittum]

The discussion continues here
https://github.com/thesofproject/linux/issues/2097#issuecomment-627880776

** Bug watch added: github.com/thesofproject/linux/issues #2097
   https://github.com/thesofproject/linux/issues/2097

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

Title:
  [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left]
  Recording problem

Status in HWE Next:
  New
Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy
  output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa-
  base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that
  now "snd-hda-intel" is loaded instead of sof-audio-pci. While the
  speakers are working fine, I do not have the internal microphone
  working (suspect a digital array).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wittawat   2063 F pulseaudio
   /dev/snd/controlC0:  wittawat   2063 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 12:42:32 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Mic, Left
  Symptom_Type: None of the above
  Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] 
Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8600
  dmi.board.vendor: HP
  dmi.board.version: 44.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dh0xxx
  dmi.product.sku: 7JX54EA#ABD
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1874698/+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 1872564] Re: /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice

[Sergio Durigan Junior]

** Description changed:

  [Impact]
  
  On a default Focal install, systemd is used when looking up passwd and
  group information:
  
  # grep systemd /etc/nsswitch.conf
  passwd: files systemd
  group:  files systemd
  
  Daemons confined by Apparmor that also query those "databases" will
  cause this Apparmor denial:
  
  audit: type=1400 audit(1586825456.411:247): apparmor="DENIED"
  operation="open" namespace="root//lxd-fb1_"
  profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id"
  pid=7370 comm="named" requested_mask="r" denied_mask="r" fsuid=100
  ouid=100
  
  Many daemons confined by Apparmor also happen to downgrade their
  privileges so they always end up looking up user/group information.
  
- To fix
+ To fix this problem, we had to backport an upstream patch which adds new
+ directives to the 'nameservices' apparmor profile.
  
  [Test Case]
  
  In order to reproduce the bug, one can:
  
  1) launch a Focal container (named fb1 here)
  $ lxc launch images:ubuntu/focal fb1
  
  2) setup apparmor inside the container (already done on official Ubuntu 
images)
  $ lxc exec fb1 -- apt update && lxc exec fb1 -- apt install apparmor -y
  
  3) install bind9
  $ lxc exec fb1 -- apt install bind9 -y
  
  4) check kernel logs for DENIED
  $ journalctl -o cat -b0 -k | grep 'apparmor="DENIED"' | grep -F 
'profile="/usr/sbin/named"'
  
  or, depending on how logging is configured:
  
  $ dmesg | grep 'apparmor="DENIED"' | grep -F 'profile="/usr/sbin/named"'
  
  Step 4, should not return anything. Because systemd is involved in the
  user/group lookups, it currently returns the following:
  
  audit: type=1400 audit(1586826072.115:266): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:267): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:268): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:269): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:270): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  
  [Regression Potential]
  
  In order to fix this issue, 3 separate patches had to be backported.
  They are simple and self-contained, especially two of them, whose
  purposes are to add the definition of the @{run} variable and then to
  add a trailing slash at the end of the "/run" pathname.
  
  The other patch, albeit very simple, adds three statements to the
  'nameservice' profile in order to let processes access (read-only) files
  under "/run/systemd/userdb" and "/proc/sys/kernel/random/boot_id".
  After thinking about the possible cases, the only possible problem I
  could envision was for a program that, not being able to access some of
  these files before, will now be able to do that and therefore exercise a
  part of its codebase which was not being used, possibly uncovering
  latent bugs in this software.  But this is not a regression of apparmor
  per se.
  
  [Original Description]
  
  (Description and Test Case were moved above)
  
  # Workaround
  
  1) remove systemd from nsswitch.conf
  $ lxc exec fb1 -- sed -i 's/ systemd$/ # systemd/' /etc/nsswitch.conf
  2) restart named
  $ lxc exec fb1 -- service named restart
  3) notice no more denials in kernel logs
  
  # Additional information
  
  root@fb1:~# apt-cache policy apparmor
  apparmor:
-   Installed: 2.13.3-7ubuntu4
-   Candidate: 2.13.3-7ubuntu4
-   Version table:
-  *** 2.13.3-7ubuntu4 500
- 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 2.13.3-7ubuntu4
+   Candidate: 2.13.3-7ubuntu4
+   Version table:
+  *** 2.13.3-7ubuntu4 500
+ 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  root@fb1:~# uname -a
  Linux fb1 5.3.0-46-generic #38~18.04.1-Ubuntu SMP Tue Mar 31 04:17:56 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux
  
  root@fb1:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

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

[Touch-packages] [Bug 1877233] Re: Remove inactive Mirrors to Colombia

[Alexander Bejarano]

** Description changed:

  Hallo,
  
  Our mirror at the mirror.upb.edu.co is being hosted any longer but it is
  still showing up on the "Software & Updates" application. Could you
  please remove it? The server is already removed from this list
  https://launchpad.net/ubuntu/+archivemirrors in the Colombia section.
  
  Thanks a lot.
  
  Present on bionic (18.04)
- Present on focal (20.04)

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

Title:
  Remove inactive Mirrors to Colombia

Status in Ubuntu:
  Invalid
Status in python-apt package in Ubuntu:
  Fix Released
Status in The Bionic Beaver:
  Invalid
Status in python-apt source package in Bionic:
  Triaged

Bug description:
  Hallo,

  Our mirror at the mirror.upb.edu.co is being hosted any longer but it
  is still showing up on the "Software & Updates" application. Could you
  please remove it? The server is already removed from this list
  https://launchpad.net/ubuntu/+archivemirrors in the Colombia section.

  Thanks a lot.

  Present on bionic (18.04)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1877233/+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 1878431] Re: [81C4, Realtek ALC298, Speaker, Internal] Playback problem

[Elvis Presley]

I saw in another bug that it would help if I ran RtHDDump.exe from
windows 10.  So I have and that should be attached next.  The sounds in
windows 10 is _great_.

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

Title:
  [81C4, Realtek ALC298, Speaker, Internal] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I get thin tinny sound.
  On ubuntu 19.10 I was able to work around this by running:
  sudo hda-verb /dev/snd/hwC0D0 0x14 SET_CONNECT_SEL 0x0c
  But that doesn't seem to work on 20.04 and I haven't been able to work out 
what I need to do to get sound working acceptably.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  travis36906 F pulseaudio
travis207783 F alsamixer
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 00:58:56 2020
  InstallationDate: Installed on 2020-05-09 (4 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:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: None of the above
  Title: [81C4, Realtek ALC298, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN32WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN32WW:bd10/09/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878431/+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 1878431] Re: [81C4, Realtek ALC298, Speaker, Internal] Playback problem

[Elvis Presley]

** Attachment added: "Output from RtHDDump.exe"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878431/+attachment/5370974/+files/RtHDDump.txt

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

Title:
  [81C4, Realtek ALC298, Speaker, Internal] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I get thin tinny sound.
  On ubuntu 19.10 I was able to work around this by running:
  sudo hda-verb /dev/snd/hwC0D0 0x14 SET_CONNECT_SEL 0x0c
  But that doesn't seem to work on 20.04 and I haven't been able to work out 
what I need to do to get sound working acceptably.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  travis36906 F pulseaudio
travis207783 F alsamixer
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 00:58:56 2020
  InstallationDate: Installed on 2020-05-09 (4 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:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: None of the above
  Title: [81C4, Realtek ALC298, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN32WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN32WW:bd10/09/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878431/+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 1877454] Re: openssh-server hangs with AuthorizedKeysCommand

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/openssh/+git/openssh/+merge/383879

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

Title:
  openssh-server hangs with AuthorizedKeysCommand

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Xenial:
  Confirmed

Bug description:
  Please consider applying this change to openssh-server distributed in Xenial 
(16.04).
  Without it, sshd can sporadically hang when making use of the 
`AuthorizedKeysCommand` option.

  https://github.com/openssh/openssh-
  portable/commit/ddd3d34e5c7979ca6f4a3a98a7d219a4ed3d98c2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1877454/+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 1878433] [NEW] package auditd 1:2.8.5-2ubuntu1 failed to install/upgrade: installed auditd package post-installation script subprocess returned error exit status 1

[Kodiak Firesmith]

Public bug reported:

Audit package installation failure report via ABRT

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: auditd 1:2.8.5-2ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
Uname: Linux 5.3.0-51-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.8
AptOrdering:
 libauparse0:amd64: Install
 auditd:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Wed May 13 11:04:53 2020
ErrorMessage: installed auditd package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2020-03-13 (60 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SourcePackage: audit
Title: package auditd 1:2.8.5-2ubuntu1 failed to install/upgrade: installed 
auditd package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package eoan

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

Title:
  package auditd 1:2.8.5-2ubuntu1 failed to install/upgrade: installed
  auditd package post-installation script subprocess returned error exit
  status 1

Status in audit package in Ubuntu:
  New

Bug description:
  Audit package installation failure report via ABRT

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: auditd 1:2.8.5-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  AptOrdering:
   libauparse0:amd64: Install
   auditd:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed May 13 11:04:53 2020
  ErrorMessage: installed auditd package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2020-03-13 (60 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: audit
  Title: package auditd 1:2.8.5-2ubuntu1 failed to install/upgrade: installed 
auditd package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1878433/+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 1878431] Re: [81C4, Realtek ALC298, Speaker, Internal] Playback problem

[Elvis Presley]

Played around with hda-analyzer and managed to get half decent sound.

I've added the python code it generated.
But I don't know how to configure things so that the volume keys adjust it.

Attachment of the python should be below.

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

Title:
  [81C4, Realtek ALC298, Speaker, Internal] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I get thin tinny sound.
  On ubuntu 19.10 I was able to work around this by running:
  sudo hda-verb /dev/snd/hwC0D0 0x14 SET_CONNECT_SEL 0x0c
  But that doesn't seem to work on 20.04 and I haven't been able to work out 
what I need to do to get sound working acceptably.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  travis36906 F pulseaudio
travis207783 F alsamixer
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 00:58:56 2020
  InstallationDate: Installed on 2020-05-09 (4 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:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: None of the above
  Title: [81C4, Realtek ALC298, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN32WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN32WW:bd10/09/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878431/+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 1878312] Re: Sound input is not automatically switched back from headphones mic to internal microphone

[Brian Murray]

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

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

Title:
  Sound input is not automatically switched back from headphones mic to
  internal microphone

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When plugging in headphones, sound input is correctly switched from
  internal microphone to the headphones mic. When the headphones are
  unplugged, sound input is NOT automatically switched back to the
  internal microphone.

  Sound output is switched back and forth correctly.

  This bug started happening on my system after I upgraded from 19.10 to
  20.04 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878312/+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 1874971] Re: less does not quit by q key before input ends, if it has not displayed full viewport of text

[Bug Watch Updater]

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

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

Title:
  less does not quit by q key before input ends, if it has not displayed
  full viewport of text

Status in LESS:
  New
Status in less package in Ubuntu:
  New

Bug description:
  Test case:

  { for i in $(seq 10); do echo $i; sleep 1; done; } | less

  Press q before left side of pipe has finished and less has not
  displayed whole viewport of text.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: less 487-0.1
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Apr 25 08:45:08 2020
  Dependencies:
   debianutils 4.8.4
   gcc-8-base 8.4.0-1ubuntu1~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.4.0-1ubuntu1~18.04
   libtinfo5 6.1-1ubuntu1.18.04
  InstallationDate: Installed on 2019-07-08 (291 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: less
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/less/+bug/1874971/+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 1878431] Re: [81C4, Realtek ALC298, Speaker, Internal] Playback problem

[Elvis Presley]

** Attachment added: "python generated by  hda-analyzer which makes things 
sound ok"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878431/+attachment/5370972/+files/fixsound

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

Title:
  [81C4, Realtek ALC298, Speaker, Internal] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I get thin tinny sound.
  On ubuntu 19.10 I was able to work around this by running:
  sudo hda-verb /dev/snd/hwC0D0 0x14 SET_CONNECT_SEL 0x0c
  But that doesn't seem to work on 20.04 and I haven't been able to work out 
what I need to do to get sound working acceptably.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  travis36906 F pulseaudio
travis207783 F alsamixer
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 00:58:56 2020
  InstallationDate: Installed on 2020-05-09 (4 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:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: None of the above
  Title: [81C4, Realtek ALC298, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN32WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN32WW:bd10/09/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878431/+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 997333] Re: ubuntu-bug refuses to file bug reports for packages that aren't installed due to packaging problems

[Brian Murray]

On Ubuntu 20.04 LTS I was able to run 'ubuntu-bug weechat', a package
which I do not have installed, and a browser tab for reporting the bug
was opened. Could you explain how this is not working for you?

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

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

Title:
  ubuntu-bug refuses to file bug reports for packages that aren't
  installed due to packaging problems

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu-bug makes it very difficult to file package problem bugs for
  packages that won't install (due to said problems), because it refuses
  to open a bug for a package that isn't installed. If a package isn't
  installed, I'd recommend that ubuntu-bug collect information about the
  package and its dependencies as seen from the local apt cache, as well
  as any conflicts that prevent it from being installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: apport 2.0.1-0ubuntu7
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportLog:
   
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Wed May  9 13:49:29 2012
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to precise on 2012-05-02 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/997333/+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 1878312] [NEW] Sound input is not automatically switched back from headphones mic to internal microphone

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When plugging in headphones, sound input is correctly switched from
internal microphone to the headphones mic. When the headphones are
unplugged, sound input is NOT automatically switched back to the
internal microphone.

Sound output is switched back and forth correctly.

This bug started happening on my system after I upgraded from 19.10 to
20.04 so it is a regression. Attached is pulseaudio log of what happens
when I plug and unplug my headphones.

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


** Tags: bot-comment
-- 
Sound input is not automatically switched back from headphones mic to internal 
microphone
https://bugs.launchpad.net/bugs/1878312
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio 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 1878431] [NEW] [81C4, Realtek ALC298, Speaker, Internal] Playback problem

[Elvis Presley]

Public bug reported:

I get thin tinny sound.
On ubuntu 19.10 I was able to work around this by running:
sudo hda-verb /dev/snd/hwC0D0 0x14 SET_CONNECT_SEL 0x0c
But that doesn't seem to work on 20.04 and I haven't been able to work out what 
I need to do to get sound working acceptably.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  travis36906 F pulseaudio
  travis207783 F alsamixer
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu May 14 00:58:56 2020
InstallationDate: Installed on 2020-05-09 (4 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:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_Type: None of the above
Title: [81C4, Realtek ALC298, Speaker, Internal] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/09/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 8GCN32WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo YOGA C930-13IKB
dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN32WW:bd10/09/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
dmi.product.family: YOGA C930-13IKB
dmi.product.name: 81C4
dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
dmi.product.version: Lenovo YOGA C930-13IKB
dmi.sys.vendor: LENOVO

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

Title:
  [81C4, Realtek ALC298, Speaker, Internal] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I get thin tinny sound.
  On ubuntu 19.10 I was able to work around this by running:
  sudo hda-verb /dev/snd/hwC0D0 0x14 SET_CONNECT_SEL 0x0c
  But that doesn't seem to work on 20.04 and I haven't been able to work out 
what I need to do to get sound working acceptably.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  travis36906 F pulseaudio
travis207783 F alsamixer
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 00:58:56 2020
  InstallationDate: Installed on 2020-05-09 (4 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:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: None of the above
  Title: [81C4, Realtek ALC298, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN32WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN32WW:bd10/09/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO

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

[patrakov]

Another instance of this bug:
https://www.reddit.com/r/archlinux/comments/ghozc1/cantt_get_audio_from_intel_graphics_hdmi_out/

Dear maintainers, maybe it's time to fix the IOMMU driver? Or, if IOMMU
maintainers are indeed unreachable, maybe ALSA maintainers can detect
this condition (iommu on, Haswell HDMI) and at least emit a warning in
the log referencing this bug and a possible workaround?

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

Title:
  Intel HDMI Audio not working with IOMMU enabled

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  New ASRock Z97 Extreme 6 motherboard with an Intel i7 4790S and an
  Nvidia GTX 650.

  Host uses Intel IGD for video and HDMI audio out.

  When I pass kernel flags 'intel_iommu=on' or 'intel_iommu=on,igfx_on'
  HDMI audio no longer functions although the device and modules seem to
  load and I cannot locate any error messages.  In this configuration
  IOMMU functions as expected and I can successfully pass the Nvidia
  card through to a KVM guest using VFIO.

  As per this
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223840) bug
  report and the linked bugzilla thread I attempted to use kernel flag
  'intel_iommu=on,igfx_off'.  This resolves the HDMI audio out but
  breaks IOMMU as in VGA pass through generates DMA errors.

  I'm running from a clean installation of 14.10 with no modifications
  to the kernel or kvm, qemu, libvirt or virt-manager.

  In either scenario above the analogue audio out continues to function,
  I haven't tested the optical out as I have no hardware to do so.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-31-generic 3.16.0-31.41
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kelvin 3468 F pulseaudio
   /dev/snd/controlC3:  kelvin 3468 F pulseaudio
   /dev/snd/controlC0:  kelvin 3468 F pulseaudio
   /dev/snd/controlC1:  kelvin 3468 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Mar  4 12:53:17 2015
  HibernationDevice: RESUME=UUID=4d35060a-85c4-45fd-9f8e-530491588931
  InstallationDate: Installed on 2015-02-26 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 
(20141022.2)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed 
root=UUID=4914f227-6bb0-40bb-a781-9ad7111a996f ro intremap=no_x2apic_optout 
intel_iommu=on,forcedac pci-stub.ids=10de:11c8,10de:0e0b nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-31-generic N/A
   linux-backports-modules-3.16.0-31-generic  N/A
   linux-firmware 1.138.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: Z97 Extreme6
  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.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1428121/+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 1428121]

[joro]

Does it make a difference when you boot with 'intremap=off' on the
kernel command line?

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

Title:
  Intel HDMI Audio not working with IOMMU enabled

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  New ASRock Z97 Extreme 6 motherboard with an Intel i7 4790S and an
  Nvidia GTX 650.

  Host uses Intel IGD for video and HDMI audio out.

  When I pass kernel flags 'intel_iommu=on' or 'intel_iommu=on,igfx_on'
  HDMI audio no longer functions although the device and modules seem to
  load and I cannot locate any error messages.  In this configuration
  IOMMU functions as expected and I can successfully pass the Nvidia
  card through to a KVM guest using VFIO.

  As per this
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223840) bug
  report and the linked bugzilla thread I attempted to use kernel flag
  'intel_iommu=on,igfx_off'.  This resolves the HDMI audio out but
  breaks IOMMU as in VGA pass through generates DMA errors.

  I'm running from a clean installation of 14.10 with no modifications
  to the kernel or kvm, qemu, libvirt or virt-manager.

  In either scenario above the analogue audio out continues to function,
  I haven't tested the optical out as I have no hardware to do so.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-31-generic 3.16.0-31.41
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kelvin 3468 F pulseaudio
   /dev/snd/controlC3:  kelvin 3468 F pulseaudio
   /dev/snd/controlC0:  kelvin 3468 F pulseaudio
   /dev/snd/controlC1:  kelvin 3468 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Mar  4 12:53:17 2015
  HibernationDevice: RESUME=UUID=4d35060a-85c4-45fd-9f8e-530491588931
  InstallationDate: Installed on 2015-02-26 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 
(20141022.2)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed 
root=UUID=4914f227-6bb0-40bb-a781-9ad7111a996f ro intremap=no_x2apic_optout 
intel_iommu=on,forcedac pci-stub.ids=10de:11c8,10de:0e0b nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-31-generic N/A
   linux-backports-modules-3.16.0-31-generic  N/A
   linux-firmware 1.138.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: Z97 Extreme6
  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.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 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.

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