[Touch-packages] [Bug 1860902] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all

[Antonio Chirtu]

Here it is.

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1860902/+attachment/5323483/+files/dmesg.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/1860902

Title:
  [HDA-Intel - HDA Intel PCH, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After installing an update (i can't remember which), i stopped hearing
  sound from the system. It only showed that headphones were
  connected(though they weren't), but even if i connected them, i could
  still hear no sound. I installed PulseAudio, tried changing other
  things, but nothing worked. I remember typing a command, though i
  cannot remember it, and it doesn't appear in my terminal history(i
  think it is in the bug description), and after that the sound appears
  to be playing from "HDMI/DisplayPort".

  Ubuntu 18.04.3 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ana1682 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 26 11:21:04 2020
  InstallationDate: Installed on 2019-08-02 (177 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ana1682 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.8.0
  dmi.board.name: 0JTTXY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.8.0:bd12/05/2018:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JTTXY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078C
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-08-22T15:47:18.564156

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1860902/+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 1860902] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all

[Hui Wang]

yes.

And dmesg > dmesg.txt, then upload the dmesg.txt.

thx.

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After installing an update (i can't remember which), i stopped hearing
  sound from the system. It only showed that headphones were
  connected(though they weren't), but even if i connected them, i could
  still hear no sound. I installed PulseAudio, tried changing other
  things, but nothing worked. I remember typing a command, though i
  cannot remember it, and it doesn't appear in my terminal history(i
  think it is in the bug description), and after that the sound appears
  to be playing from "HDMI/DisplayPort".

  Ubuntu 18.04.3 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ana1682 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 26 11:21:04 2020
  InstallationDate: Installed on 2019-08-02 (177 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ana1682 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.8.0
  dmi.board.name: 0JTTXY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.8.0:bd12/05/2018:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JTTXY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078C
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-08-22T15:47:18.564156

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1860902/+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 1860902] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all

[Antonio Chirtu]

Are you referring to the last row of this file?

** Attachment added: "Screenshot from 2020-01-28 09-13-32.png"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1860902/+attachment/5323482/+files/Screenshot%20from%202020-01-28%2009-13-32.png

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After installing an update (i can't remember which), i stopped hearing
  sound from the system. It only showed that headphones were
  connected(though they weren't), but even if i connected them, i could
  still hear no sound. I installed PulseAudio, tried changing other
  things, but nothing worked. I remember typing a command, though i
  cannot remember it, and it doesn't appear in my terminal history(i
  think it is in the bug description), and after that the sound appears
  to be playing from "HDMI/DisplayPort".

  Ubuntu 18.04.3 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ana1682 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 26 11:21:04 2020
  InstallationDate: Installed on 2019-08-02 (177 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ana1682 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.8.0
  dmi.board.name: 0JTTXY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.8.0:bd12/05/2018:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JTTXY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078C
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-08-22T15:47:18.564156

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

Re: [Touch-packages] [Bug 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red

[Paul Collinsworth]

Could be. Bug 1860178's write-up seems similar to 1860483.

I have been able to use "Settings" in the sda1 install, and switched the 
background to "black", at which point the raster type corruption in the 
desktop went away. Now there's occasionally an odd speckled background 
in the top tool bar, which blanks out to black around the top tool bar 
icons and text, leaving something that looks like video noise between 
the leftmost text/dropdown and the day/time text at the middle, and 
between that middle item and the rightmost icon set. At the same time, 
there's a little noise speckling on the left tool bar, and a bright 
narrow vertical line between the tool bar and the desktop region; all 
that blanks out to black too. The blanking-to-black occurs as the screen 
cursor is traversed over the tool bars.

I am occasionally getting a non-response for item icons associated with 
sda1 installs, just as I have been with items in sdb1. That kind of 
looks to me like the system is losing or overwriting the pointer to the 
app/item associated with the icon. For instance, I still can't get to 
sdb1's "Settings"; I can click on any one of the "Settings" icons, the 
activity indicator runs for a short period, stops, and nothing happens. 
I've waited for a few minutes, up to around 5 or so, just to see if it's 
a matter of timing, but nothing happens. And frequently, after that 
happens, other items become non-responsive as well, up to the point 
where the keyboard and mouse push-button handlers quit responding.

On 1/27/20 7:57 PM, Daniel van Vugt wrote:
> Possibly related to bug 1860178.
>
> ** Also affects: mutter (Ubuntu)
> Importance: Undecided
> Status: New
>

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

Title:
  [nouveau, GeForce 7300 LE] screen background overlaid with scan type
  artifact in red

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  My desktop has both it's usual items in place; toolbar on left and
  desktop icons distributed around the screen. Then there's what appears
  to be a bunch of scan line, raster line artifacts, in red, laid over
  my normal background, which is a star field photo on what is
  ordinarily a black field.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 21 13:04:20 2020
  DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405]
  InstallationDate: Installed on 2016-08-19 (1249 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 531
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago)
  dmi.bios.date: 11/09/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0RY206
  dmi.board.vendor: Dell Inc.
  dmi.board.version: ���
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion:
  dmi.product.name: Inspiron 531
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct  3 10:41:28 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB 

[Touch-packages] [Bug 1856366] Re: PCI/internal sound card not detected on a Swift SF314-57

[Adam]

Hi Paul

> do you still have the problem *without* `dsp_driver=0` on an up-to-
date Ubuntu 19.10 with Linux 5.5-rc6?

I just tried the 5.5 release https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.5/

I also tried newest 1.4.2 from sof project and updadted their github
issue.

The trick with dsp_driver=0 seems not to work anymore. I resorted to
adding "snd_hda_intel.dmic_detect=0" to GRUB_CMDLINE_LINUX_DEFAULT as
suggested at Red Hat link you posted and will get the snd_hda_intel
driver:

[  151.393221] snd_hda_intel :00:1f.3: dmic_detect option is deprecated, 
pass snd-intel-dspcfg.dsp_driver=1 option instead
[  151.393257] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
[  151.393565] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[  151.403720] thermal thermal_zone9: failed to read out thermal zone (-61)
[  151.405115] iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
[  151.435143] snd_hda_codec_generic hdaudioC0D0: autoconfig for Generic: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[  151.435144] snd_hda_codec_generic hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[  151.435145] snd_hda_codec_generic hdaudioC0D0:hp_outs=1 
(0x16/0x0/0x0/0x0/0x0)
[  151.435146] snd_hda_codec_generic hdaudioC0D0:mono: mono_out=0x0
[  151.435146] snd_hda_codec_generic hdaudioC0D0:inputs:
[  151.435147] snd_hda_codec_generic hdaudioC0D0:  Mic=0x19

That works well for me now.

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

Title:
  PCI/internal sound card not detected on a Swift SF314-57

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound card detected with kernel 5.5.0-050500rc1-generic

  1. Description:   Ubuntu 19.10
  Release:  19.10

  2. linux-image-
  unsigned-5.5.0-050500rc1-generic_5.5.0-050500rc1.201912081930_amd64.deb

  3. have at least one soundcard

  4. cat /proc/asound/cards reports:
  --- no soundcards ---

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.5.0-050500rc1-generic x86_64
  NonfreeKernelModules: hda_intel
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 13 22:09:17 2019
  InstallationDate: Installed on 2019-12-13 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Floris_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2019:svnAcer:pnSwiftSF314-57:pvrV1.07:rvnIL:rnFloris_IL:rvrV1.07:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-57
  dmi.product.sku: 
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T20:34:57.551680

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856366/+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 1861063] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Dualshock4 controller doesn't stay connected

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

Bug description:
  Pairing the Dualshock4 controller works somehow, after several
  attempts. I expected this to work out of the box but it does not work
  well at all.

  Once the pairing is completed, if I try to connect it it doesn't stay
  connected.

  I have checked the dmesg and apparently there is a buffer overflow
  somewhere.

  I can pair a bluetooth headset to my laptop and the Dualshock4 pairs
  with my samsung tablet without problems but when I try to pair the
  dualshock4 to the laptop, running Ubuntu 19.10, it does not work.

  Dmesg output:

  
  [4.099796] Bluetooth: Core ver 2.22
  [4.099833] Bluetooth: HCI device and connection manager initialized
  [4.099837] Bluetooth: HCI socket layer initialized
  [4.099839] Bluetooth: L2CAP socket layer initialized
  [4.099842] Bluetooth: SCO socket layer initialized
  [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018
  [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.855413] Bluetooth: BNEP filters: protocol multicast
  [6.855416] Bluetooth: BNEP socket layer initialized
  [   14.234706] Bluetooth: RFCOMM TTY layer initialized
  [   14.234711] Bluetooth: RFCOMM socket layer initialized
  [   14.234715] Bluetooth: RFCOMM ver 1.11
  [  117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow


  
  Release: 
  Description:  Ubuntu 19.10
  Release:  19.10

  
  Package Info:
  bluez:
Installed: 5.50-0ubuntu4
Candidate: 5.50-0ubuntu4
Version table:
   *** 5.50-0ubuntu4 500
  500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 28 14:11:19 2020
  InstallationDate: Installed on 2019-11-26 (62 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FCS33A00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago)
  dmi.bios.date: 03/13/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET68W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FCS33A00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FCS33A00
  dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:A7:A0:C6:7F:AE  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:8289 acl:41 sco:0 events:268 errors:0
TX bytes:9494 acl:44 sco:0 commands:163 errors:0
  syslog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1861063/+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 1861063] Re: Dualshock4 controller doesn't stay connected

[Daniel van Vugt]

It sounds like this might be the problem:

  Bluetooth: Dropping L2CAP data: receive buffer overflow

in which case that would be a kernel bug. So this has been assigned to
the kernel.

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

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

Title:
  Dualshock4 controller doesn't stay connected

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Pairing the Dualshock4 controller works somehow, after several
  attempts. I expected this to work out of the box but it does not work
  well at all.

  Once the pairing is completed, if I try to connect it it doesn't stay
  connected.

  I have checked the dmesg and apparently there is a buffer overflow
  somewhere.

  I can pair a bluetooth headset to my laptop and the Dualshock4 pairs
  with my samsung tablet without problems but when I try to pair the
  dualshock4 to the laptop, running Ubuntu 19.10, it does not work.

  Dmesg output:

  
  [4.099796] Bluetooth: Core ver 2.22
  [4.099833] Bluetooth: HCI device and connection manager initialized
  [4.099837] Bluetooth: HCI socket layer initialized
  [4.099839] Bluetooth: L2CAP socket layer initialized
  [4.099842] Bluetooth: SCO socket layer initialized
  [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018
  [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.855413] Bluetooth: BNEP filters: protocol multicast
  [6.855416] Bluetooth: BNEP socket layer initialized
  [   14.234706] Bluetooth: RFCOMM TTY layer initialized
  [   14.234711] Bluetooth: RFCOMM socket layer initialized
  [   14.234715] Bluetooth: RFCOMM ver 1.11
  [  117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow


  
  Release: 
  Description:  Ubuntu 19.10
  Release:  19.10

  
  Package Info:
  bluez:
Installed: 5.50-0ubuntu4
Candidate: 5.50-0ubuntu4
Version table:
   *** 5.50-0ubuntu4 500
  500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 28 14:11:19 2020
  InstallationDate: Installed on 2019-11-26 (62 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FCS33A00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago)
  dmi.bios.date: 03/13/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET68W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FCS33A00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FCS33A00
  dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:A7:A0:C6:7F:AE  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:8289 acl:41 sco:0 events:268 errors:0
TX bytes:9494 acl:44 sco:0 commands:163 errors:0
  syslog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1861063/+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 1860042] Re: openCL application gives error after update

[Timo Aaltonen]

this is caused by the hardening patch in libclc

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

** Changed in: libclc (Ubuntu)
   Status: Incomplete => Triaged

** Also affects: libclc (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: libclc (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: libclc (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: libclc (Ubuntu Eoan)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  openCL application gives error after update

Status in libclc package in Ubuntu:
  Triaged
Status in libclc source package in Bionic:
  New
Status in libclc source package in Eoan:
  New

Bug description:
  My OpenCL program was working normally until a software update.

  The program prints out:

  ac_rtld error: !s->is_rx
  LLVM failed to upload shader

  when clEnqueueNDRangeKernel is called.

  I've downloaded the source for mesa and traced the problem to the
  gallium radeon driver. The first error message is from

  mesa-19.2.1/src/amd/common/ac_rtld.c

  and the second error message is from

  mesa-19.2.1/src/gallium/drivers/radeonsi/si_compute.c

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libllvm9 1:9-2~ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-lowlatency 4.15.18
  Uname: Linux 4.15.0-74-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 14:35:15 2020
  InstallationDate: Installed on 2018-04-28 (628 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: mesa-opencl-icd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1860042/+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 1860199] Re: OpenCL programs give error messages

[Timo Aaltonen]

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

** This bug has been marked a duplicate of bug 1860042
   openCL application gives error after update

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

Title:
  OpenCL programs give error messages

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  OpenCL programs print

  ac_rtld error: !s->is_rx
  LLVM failed to upload shader

  when calling clEnqueueNDRangeKernel.

  lsb_release -rd displays:

  Description:  Ubuntu 19.10
  Release:  19.10

  apt-cache policy mesa-opencl-icd displays:

  mesa-opencl-icd:
Installed: 19.2.1-1ubuntu1
Candidate: 19.2.1-1ubuntu1
Version table:
   *** 19.2.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: mesa-opencl-icd 19.2.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.427
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 17 23:09:17 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] 
[1002:9874] (rev e1) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:82fe]
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Pavilion Desktop PC 570-p0xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/hostname.seed quiet splash ---
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2017
  dmi.bios.vendor: AMI
  dmi.bios.version: F.20
  dmi.board.asset.tag: CNV7500FYH
  dmi.board.name: 82FE
  dmi.board.vendor: HP
  dmi.board.version: 11
  dmi.chassis.asset.tag: CNV7500FYH
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.20:bd10/30/2017:svnHP:pnHPPavilionDesktopPC570-p0xx:pvr:rvnHP:rn82FE:rvr11:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53311M HP Pavilion
  dmi.product.name: HP Pavilion Desktop PC 570-p0xx
  dmi.product.sku: Z5P18AA#ABL
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860199/+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 1861063] Re: Dualshock4 controller doesn't stay connected

[Goran Josic]

If I try to connect the controller with the usb cable it gets recognized
as pulse audio source.

The controller model is: CUH-ZCT2U

This is the output of the dmesg:

[ 1882.762621] usb 1-1: new full-speed USB device number 6 using xhci_hcd
[ 1882.913951] usb 1-1: New USB device found, idVendor=054c, idProduct=09cc, 
bcdDevice= 1.00
[ 1882.913956] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1882.913960] usb 1-1: Product: Wireless Controller
[ 1882.913962] usb 1-1: Manufacturer: Sony Interactive Entertainment
[ 1882.951627] usbcore: registered new interface driver snd-usb-audio
[ 1882.952799] sony 0003:054C:09CC.0004: failed to retrieve feature report 0x81 
with the DualShock 4 MAC address
[ 1882.952943] sony 0003:054C:09CC.0004: hidraw1: USB HID v81.11 Gamepad [Sony 
Interactive Entertainment Wireless Controller] on usb-:00:14.0-1/input3
[ 1882.952945] sony 0003:054C:09CC.0004: failed to claim input
[ 1883.072399] retire_capture_urb: 28 callbacks suppressed
~ ❯❯❯

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

Title:
  Dualshock4 controller doesn't stay connected

Status in bluez package in Ubuntu:
  New

Bug description:
  Pairing the Dualshock4 controller works somehow, after several
  attempts. I expected this to work out of the box but it does not work
  well at all.

  Once the pairing is completed, if I try to connect it it doesn't stay
  connected.

  I have checked the dmesg and apparently there is a buffer overflow
  somewhere.

  I can pair a bluetooth headset to my laptop and the Dualshock4 pairs
  with my samsung tablet without problems but when I try to pair the
  dualshock4 to the laptop, running Ubuntu 19.10, it does not work.

  Dmesg output:

  
  [4.099796] Bluetooth: Core ver 2.22
  [4.099833] Bluetooth: HCI device and connection manager initialized
  [4.099837] Bluetooth: HCI socket layer initialized
  [4.099839] Bluetooth: L2CAP socket layer initialized
  [4.099842] Bluetooth: SCO socket layer initialized
  [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018
  [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.855413] Bluetooth: BNEP filters: protocol multicast
  [6.855416] Bluetooth: BNEP socket layer initialized
  [   14.234706] Bluetooth: RFCOMM TTY layer initialized
  [   14.234711] Bluetooth: RFCOMM socket layer initialized
  [   14.234715] Bluetooth: RFCOMM ver 1.11
  [  117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow


  
  Release: 
  Description:  Ubuntu 19.10
  Release:  19.10

  
  Package Info:
  bluez:
Installed: 5.50-0ubuntu4
Candidate: 5.50-0ubuntu4
Version table:
   *** 5.50-0ubuntu4 500
  500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 28 14:11:19 2020
  InstallationDate: Installed on 2019-11-26 (62 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FCS33A00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago)
  dmi.bios.date: 03/13/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET68W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FCS33A00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FCS33A00
  dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:A7:A0:C6:7F:AE  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:8289 acl:41 sco:0 events:268 errors:0
TX bytes:9494 acl:44 sco:0 commands:163 errors:0
  syslog:

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

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

[Touch-packages] [Bug 1861063] [NEW] Dualshock4 controller doesn't stay connected

[Goran Josic]

Public bug reported:

Pairing the Dualshock4 controller works somehow, after several attempts.
I expected this to work out of the box but it does not work well at all.

Once the pairing is completed, if I try to connect it it doesn't stay
connected.

I have checked the dmesg and apparently there is a buffer overflow
somewhere.

I can pair a bluetooth headset to my laptop and the Dualshock4 pairs
with my samsung tablet without problems but when I try to pair the
dualshock4 to the laptop, running Ubuntu 19.10, it does not work.

Dmesg output:


[4.099796] Bluetooth: Core ver 2.22
[4.099833] Bluetooth: HCI device and connection manager initialized
[4.099837] Bluetooth: HCI socket layer initialized
[4.099839] Bluetooth: L2CAP socket layer initialized
[4.099842] Bluetooth: SCO socket layer initialized
[4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018
[6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[6.855413] Bluetooth: BNEP filters: protocol multicast
[6.855416] Bluetooth: BNEP socket layer initialized
[   14.234706] Bluetooth: RFCOMM TTY layer initialized
[   14.234711] Bluetooth: RFCOMM socket layer initialized
[   14.234715] Bluetooth: RFCOMM ver 1.11
[  117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow


Release: 
Description:Ubuntu 19.10
Release:19.10


Package Info:
bluez:
  Installed: 5.50-0ubuntu4
  Candidate: 5.50-0ubuntu4
  Version table:
 *** 5.50-0ubuntu4 500
500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: bluez 5.50-0ubuntu4
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 28 14:11:19 2020
InstallationDate: Installed on 2019-11-26 (62 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20FCS33A00
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago)
dmi.bios.date: 03/13/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1FET68W (1.42 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FCS33A00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 4th
dmi.product.name: 20FCS33A00
dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th
dmi.product.version: ThinkPad X1 Carbon 4th
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: E4:A7:A0:C6:7F:AE  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:8289 acl:41 sco:0 events:268 errors:0
TX bytes:9494 acl:44 sco:0 commands:163 errors:0
syslog:

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


** Tags: amd64 apport-bug eoan

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

Title:
  Dualshock4 controller doesn't stay connected

Status in bluez package in Ubuntu:
  New

Bug description:
  Pairing the Dualshock4 controller works somehow, after several
  attempts. I expected this to work out of the box but it does not work
  well at all.

  Once the pairing is completed, if I try to connect it it doesn't stay
  connected.

  I have checked the dmesg and apparently there is a buffer overflow
  somewhere.

  I can pair a bluetooth headset to my laptop and the Dualshock4 pairs
  with my samsung tablet without problems but when I try to pair the
  dualshock4 to the laptop, running Ubuntu 19.10, it does not work.

  Dmesg output:

  
  [4.099796] Bluetooth: Core ver 2.22
  [4.099833] Bluetooth: HCI device and connection manager initialized
  [4.099837] Bluetooth: HCI socket layer initialized
  [4.099839] Bluetooth: L2CAP socket layer initialized
  [4.099842] Bluetooth: SCO socket layer initialized
  [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018
  [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.855413] Bluetooth: BNEP filters: protocol multicast
  [6.855416] Bluetooth: BNEP socket layer initialized
  [   14.234706] Bluetooth: RFCOMM TTY layer initialized
  [   14.234711] Bluetooth: RFCOMM socket layer initialized
  [   14.234715] Bluetooth: RFCOMM ver 1.11
  [  117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow


  
  Release: 
 

[Touch-packages] [Bug 1861043] Re: Xorg freeze

[Daniel van Vugt]

Please reproduce the freeze again, then reboot and immediately run:

  journalctl -b-1 > prevboot.txt

and attach the file 'prevboot.txt' here.


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  Xorg freeze

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  So under high load I can generally cause a freeze in Gnome/Ubuntu.
  This is somewhat expected and likely should be fixed by some sort of
  OOM killer. However that's only part of the problem. Virtual Consoles
  are disabled (`/etc/systemd/logind.conf` `NAutoVTs` by default) and I
  believe that too to be a bug. In the past I could have Switched VT's
  logged in and killed of a high memory/cpu process or two. Now I have
  to hard kill the box and risk loosing in progress work which is
  ungainly.

  If there's a worry about "what will new users do if they accidentally
  hit CTRL+ALT+F\d" maybe instead of disabling it we could change the
  default login message to have a "Don't know how you got here? Hit
  CTLR+ALT+F1 to go back."

  Also because I have to hard restart apport never get's called to show
  exactly why the system is hanging.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu13
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:03:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.44  Sun Dec  8 03:38:56 
UTC 2019
   GCC version:  gcc version 9.2.1 20200123 (Ubuntu 9.2.1-25ubuntu1)
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 27 15:13:07 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.44, 5.4.0-12-generic, x86_64: installed
   nvidia, 440.44, 5.4.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:062b]
 Subsystem: Dell GM108M [GeForce 840M] [1028:062b]
  InstallationDate: Installed on 2020-01-14 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106)
  MachineType: Dell Inc. Latitude E5450
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=37b7ed5e-16a1-4e03-ad70-e85dfec9bf53 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0MVKK7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd07/30/2015:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn0MVKK7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5450
  dmi.product.sku: 062B
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.4-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1861043/+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 1860946] Re: Error or every boot

[Daniel van Vugt]

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

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

Title:
  Error or every boot

Status in Ubuntu:
  Incomplete

Bug description:
  Delay in response infrequent interrution

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Jan 27 07:28:37 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   anbox, 1, 4.15.0-72-generic, x86_64: installed
   anbox, 1, 4.15.0-74-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics 
Controller [1179:fa31]
  InstallationDate: Installed on 2018-08-27 (517 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: TOSHIBA Satellite C50-A
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=02250975-d476-48ef-9a7d-22dbbe5e4c15 ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.30
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PT10F
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.30:bd11/08/2013:svnTOSHIBA:pnSatelliteC50-A:pvrPSCG8G-05500G:rvnIntel:rnPT10F:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: Satellite C50-A
  dmi.product.version: PSCG8G-05500G
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Aug 28 09:45:06 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1860946/+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 1860930] Re: [Asus GX531GX] Internal speakers are sometimes noisy - bad audio

[Daniel van Vugt]

Can you please try the latest kernel and tell us if that improves the
situation?

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5/

** Summary changed:

- Internal speakers are sometimes noisy - bad audio
+ [Asus GX531GX] Internal speakers are sometimes noisy - bad audio

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

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

** Changed in: alsa-driver (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/1860930

Title:
  [Asus GX531GX] Internal speakers are sometimes noisy - bad audio

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have an Asus Zephyrus S GX531GX laptop and a pair of Asus Delta USB
  headphones. When the headphones are plugged in during boot the
  internal speakers won't work. There is only crackling sound coming
  from them. It doesn't help in I unplug the headphones. There is no
  problem if they are not plugged in during boot. I'm using Ubuntu
  19.10.

  Please let me know if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Jan 26 19:26:35 2020
  InstallationDate: Installed on 2019-12-19 (38 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GX531GXR.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GX531GXR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGX531GXR.304:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnZephyrusSGX531GXR_GX531GXR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX531GXR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: Zephyrus S
  dmi.product.name: Zephyrus S GX531GXR_GX531GXR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1860930/+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 1860934] Re: second monitor is not waking up automaticall after boot and sleep

[Daniel van Vugt]

** Tags added: nvidia

** Summary changed:

- second monitor is not waking up automaticall after boot and sleep
+ [nvidia] second monitor is not waking up automatically after boot and sleep

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-435
(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/1860934

Title:
  [nvidia] second monitor is not waking up automatically after boot and
  sleep

Status in nvidia-graphics-drivers-435 package in Ubuntu:
  New

Bug description:
  primary screen : laptop screen
  secondary screen: Samsung Monitor

  secondary monitor is connected to laptop via HDMI port.
  secondary monitor won't wake up after a normal boot.
  secondary monitor will wake up after boot if switch to ctl+alt+f7 and then 
back to graphical.
  blacklisted `nouveau` drivers via an entry in /etc/modeprobe.d/
  set the value for GRUB_CMDLINE_LINUX_DEFAULT to `""` (emprty string) and then 
ran `update-grub`

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 27 07:33:52 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-18-generic, x86_64: installed
   nvidia, 435.21, 5.3.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:0798]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798]
  InstallationDate: Installed on 2020-01-25 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=77709762-71e2-437a-974a-8d580316705f ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 065C71
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd05/17/2019:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.product.sku: 0798
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1860934/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

[Hui Wang]

Reply #5:

No, the change is not in the 1.2.1 and will not apply to 1.2.1. these
confs are ucm1 version, they are only for eoan and bionic. For alsa-lib
1.2.1, the upstream is writing ucm2 confs and it is not finished yet. So
let's SRU the ucm confs for eoan and bionic first. And in future the
ucm2 conf are not in the alsa-lib anymore, they are moved to
https://github.com/alsa-project/alsa-ucm-conf.

In order to help us enable the dmic on eoan and bionic, Intel is
maintaining these ucm1 confs  (https://github.com/thesofproject/alsa-
ucm-conf.git).

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in alsa-lib package in Ubuntu:
  Fix Committed

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1860925] Re: Xorg freeze / nouveau driver fault ?

[Daniel van Vugt]

This looks like a nouveau kernel problem, but can you describe the
problem you are experiencing?

** Tags added: nouveau

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

Title:
  Xorg freeze / nouveau driver fault ?

Status in linux package in Ubuntu:
  New

Bug description:
  june@june-pc:~$ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10
  (Note: upgrade today from 19.04, which also froze randomly)
  
  june@june-pc:~$ apt-cache dump | grep nouveau | grep Package
  Package: xserver-xorg-video-nouveau
  Package: xserver-xorg-video-nouveau:i386
  Package: libdrm-nouveau2
  Package: libdrm-nouveau2:i386
  Package: xserver-xorg-video-nouveau-hwe-18.04
  Package: xserver-xorg-video-nouveau-hwe-18.04:i386
  Package: nouveau-firmware

  june@june-pc:~$ apt-cache policy xserver-xorg-video-nouveau libdrm-nouveau2 
xserver-xorg-video-nouveau-hwe-18.04
  xserver-xorg-video-nouveau:
Installed: 1:1.0.16-1
Candidate: 1:1.0.16-1
Version table:
   *** 1:1.0.16-1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status
  libdrm-nouveau2:
Installed: 2.4.99-1ubuntu1
Candidate: 2.4.99-1ubuntu1
Version table:
   *** 2.4.99-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status
  xserver-xorg-video-nouveau-hwe-18.04:
Installed: (none)
Candidate: 3:14.5
Version table:
   3:14.5 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  
  Kernel MMIO FAULT errors being seen in syslog; such as:

  Jan 26 15:21:44 June-PC kernel: [  354.655752] nouveau :00:10.0: bus: 
MMIO write of  FAULT at 00b030
  Jan 26 15:31:26 June-PC kernel: [  936.671821] nouveau :00:10.0: gr: intr 
0010 [ERROR] nsource 0002 [DATA_ERROR] nstatus 0200 [BAD_ARGUMENT] 
ch 6 [0006b000 gnome-shell[1987]] subc 7 class 4497 mthd 0208 data 04000248

  Seeing some of these while system operating 'normally' but when
  systems freezes needing hard reboot there is generally one or more
  MMIO Fault message just prior.

  No obvious correlation between activity/application in use crash.
  Latest instance, after 19.10 upgrade was system freeze on initial
  opening of Mozilla Thunderbird. Thunderbird then opened fine after
  reboot.

  
  syslog "grep -E "(MMIO|nouv|FAULT|BOOT)"  from boot onwards attached 
("nouveau-driver-syslog-errors.txt")

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 26 15:59:09 2020
  DistUpgraded: 2020-01-26 11:14:39,179 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   NVIDIA Corporation C73 [GeForce 7100 / nForce 630i] [10de:07e1] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] C73 [GeForce 7100 / nForce 630i] 
[1025:026c]
  InstallationDate: Installed on 2020-01-14 (12 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 001 Device 002: ID 0bda:0182 Realtek Semiconductor Corp. USB2.0-CRW
   Bus 001 Device 004: ID 04a9:178d Canon, Inc. PIXMA MG6853
   Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Packard Bell ixtreme M3720
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to eoan on 2020-01-26 (0 days ago)
  dmi.bios.date: 07/21/2009
  dmi.bios.vendor: AMI
  dmi.bios.version: P01-A3
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MCP73PVT-PM
  dmi.board.vendor: Packard Bell
  dmi.chassis.type: 3
  dmi.chassis.vendor: Packard Bell
  dmi.modalias: 

[Touch-packages] [Bug 1860754] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to
  submit batchbuffer: Input/output error]

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

Bug description:
  - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't 
recognize graphic driver.
  - run udo apt-get install xserver-xorg-video-intel
  0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 14:29:01 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd]
  InstallationDate: Installed on 2020-01-24 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. T100HAN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T100HAN.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T100HAN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: T
  dmi.product.name: T100HAN
  dmi.product.sku: ASUS-TabletSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860754/+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 1860847] Re: system is feeze

[Daniel van Vugt]

Please:

1. Reproduce the freeze again, then reboot and run:

   journalctl -b-1 > preboot.txt

   and attach the file here.

2. Try uninstalling the Nvidia driver if you can and tell us if the
problem still happens with the default built-in driver.

** Tags added: nvidia

** Summary changed:

- system is feeze
+ [nvidia] system is feeze

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-390
(Ubuntu)

** Changed in: nvidia-graphics-drivers-390 (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/1860847

Title:
  [nvidia] system is feeze

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  I have problem with graphic cards. After work, when I reboot system
  then system feeze and I can't work. I must change to the recovery mode
  and next work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Jest katalogiem: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.129  Mon Jul 22 21:10:21 
PDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Jan 25 10:07:46 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-18-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-26-generic, x86_64: installed
   nvidia, 390.129, 5.3.0-18-generic, x86_64: installed
   nvidia, 390.129, 5.3.0-26-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Dell GF119M [NVS 4200M] [1028:0494]
  InstallationDate: Installed on 2020-01-24 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=e65c7e31-8fb3-43f7-8a68-c1bb187f8f8c ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 07/11/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0J4TFW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/11/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Jan 25 09:24:56 2020
  xserver.configfile: default
  xserver.errors:
   open /dev/fb0: No such file or directory
   systemd-logind: failed to release device: Device not taken
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1860847/+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 1838181] Re: 3D Application cannot run anymore

[Daniel van Vugt]

See also bug 1860754.

** Summary changed:

- 3D Application cannot run anymore
+ 3D Application cannot run anymore [i965: Failed to submit batchbuffer: 
Input/output error]

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

Title:
  3D Application cannot run anymore [i965: Failed to submit batchbuffer:
  Input/output error]

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

Bug description:
  Since a recent update (done today 2019-07-28) I cannot start
  application that requires 3D (openGL support). It start being slow
  with degraded graphics, then freeze and finally crash with the
  following message :

   > i965: Failed to submit batchbuffer: Input/output error

  It also happened to me when I updated from Bionic Beaver to Disco. The
  Workaround was to reinstall a Bionic Beaver version. Now it does not
  work on this version anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 28 08:58:45 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:80df]
  InstallationDate: Installed on 2019-04-30 (89 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: HP HP ENVY Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic 
root=UUID=a33f3d20-4ebb-4f0d-9401-31c32121600a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.45
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DF
  dmi.board.vendor: HP
  dmi.board.version: 87.72
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.45:bd05/23/2017:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80DF:rvr87.72:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY Notebook
  dmi.product.sku: W6X73EA#ABF
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838181/+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 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]

[Daniel van Vugt]

See also bug 1838181.

** Summary changed:

- ASUS T100HAN boots to a blank screen with a cursor
+ ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit 
batchbuffer: Input/output error]

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

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

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

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

Title:
  ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to
  submit batchbuffer: Input/output error]

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

Bug description:
  - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't 
recognize graphic driver.
  - run udo apt-get install xserver-xorg-video-intel
  0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 14:29:01 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd]
  InstallationDate: Installed on 2020-01-24 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. T100HAN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T100HAN.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T100HAN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: T
  dmi.product.name: T100HAN
  dmi.product.sku: ASUS-TabletSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860754/+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 1860754] [NEW] ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

- After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't 
recognize graphic driver.
- run udo apt-get install xserver-xorg-video-intel
0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 24 14:29:01 2020
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd]
InstallationDate: Installed on 2020-01-24 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub
 Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. T100HAN
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/18/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: T100HAN.221
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: T100HAN
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: T
dmi.product.name: T100HAN
dmi.product.sku: ASUS-TabletSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug eoan ubuntu
-- 
ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit 
batchbuffer: Input/output error]
https://bugs.launchpad.net/bugs/1860754
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mesa 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 1860178] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  [nouveau] Desktop wallpaper is corrupt noise on GeForce 6150SE nForce
  430

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Graphic environment unstable, desktop background degraded. Seems
  consequently to last system upgrade (2020.jan.17)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Jan 17 21:55:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] C61 [GeForce 6150SE nForce 430] 
[1025:0394]
  InstallationDate: Installed on 2019-08-03 (167 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 001 Device 003: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 
multicard reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 04f9:0027 Brother Industries, Ltd HL-2030 Laser 
Printer
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: eMachines EL1358
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=52e5db54-2ea1-48ba-9efe-6b23d1188404 ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-B1
  dmi.board.name: EL1358
  dmi.board.vendor: eMachines
  dmi.chassis.type: 3
  dmi.chassis.vendor: eMachines
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd04/20/2011:svneMachines:pnEL1358:pvr:rvneMachines:rnEL1358:rvr:cvneMachines:ct3:cvr:
  dmi.product.family: eMachines Desktop
  dmi.product.name: EL1358
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.sys.vendor: eMachines
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860178/+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 1860178] Re: [nouveau] Desktop wallpaper is corrupt noise

[Daniel van Vugt]

Possibly related to bug 1860483.

** Summary changed:

- [nouveau] Graphic environment bug
+ [nouveau] Desktop wallpaper is corrupt noise

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

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

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- [nouveau] Desktop wallpaper is corrupt noise
+ [nouveau] Desktop wallpaper is corrupt noise on GeForce 6150SE nForce 430

** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)

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

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

Title:
  [nouveau] Desktop wallpaper is corrupt noise on GeForce 6150SE nForce
  430

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Graphic environment unstable, desktop background degraded. Seems
  consequently to last system upgrade (2020.jan.17)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Jan 17 21:55:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] C61 [GeForce 6150SE nForce 430] 
[1025:0394]
  InstallationDate: Installed on 2019-08-03 (167 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 001 Device 003: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 
multicard reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 04f9:0027 Brother Industries, Ltd HL-2030 Laser 
Printer
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: eMachines EL1358
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=52e5db54-2ea1-48ba-9efe-6b23d1188404 ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-B1
  dmi.board.name: EL1358
  dmi.board.vendor: eMachines
  dmi.chassis.type: 3
  dmi.chassis.vendor: eMachines
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd04/20/2011:svneMachines:pnEL1358:pvr:rvneMachines:rnEL1358:rvr:cvneMachines:ct3:cvr:
  dmi.product.family: eMachines Desktop
  dmi.product.name: EL1358
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.sys.vendor: eMachines
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860178/+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 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red

[Daniel van Vugt]

Possibly related to bug 1860178.

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

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

Title:
  [nouveau, GeForce 7300 LE] screen background overlaid with scan type
  artifact in red

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  My desktop has both it's usual items in place; toolbar on left and
  desktop icons distributed around the screen. Then there's what appears
  to be a bunch of scan line, raster line artifacts, in red, laid over
  my normal background, which is a star field photo on what is
  ordinarily a black field.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 21 13:04:20 2020
  DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405]
  InstallationDate: Installed on 2016-08-19 (1249 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 531
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago)
  dmi.bios.date: 11/09/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0RY206
  dmi.board.vendor: Dell Inc.
  dmi.board.version: ���
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion:
  dmi.product.name: Inspiron 531
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct  3 10:41:28 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard KEYBOARD, id 8
   inputLogitech USB Trackball MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Daniel van Vugt]

> Considering nvidia's market share (80% according to the steam hardware
survey, which will be skewed towards people with discrete GPUs, but
still), I think giving this issue a priority of low is wrong.

That might be true for gaming machines but I don't think that's an
accurate figure for machines running Ubuntu. I don't have the stats
handy but what we see in bug reports is that Intel-only graphics is the
most common type of machine.

I'm not saying this bug won't be fixed, but to suggest most Ubuntu
machines have Nvidia GPUs is incorrect.

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: 

[Touch-packages] [Bug 1845046] Re: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected

[Daniel van Vugt]

Re comment #39, can someone with the privileges please click retry? It
won't let me.

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

Title:
  Bluetooth headphones default to low quality headset mode and fail to
  switch to A2DP when selected

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

Bug description:
  [Impact]

  Whenever I turn on my headphones they'll connect to my computer but
  I'm able to hear the input audio from my microphone and low quality
  output audio. I have to disconnect the headphones in the bluetooth
  devices and reconnect for it to fix the problem.

  [Test Case]

  0. Set up your Bluetooth headphones with Ubuntu.
  1. Turn off the headphones.
  2. Turn on the headphones.
  3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high 
quality, no microphone support).

  [Regression Potential]

  Low. Only the headset code path is affected and the fix has already
  been released for some time in BlueZ 5.51 onward.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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 1821641] Re: [HP Elitebook 840 G1] Screen is upside down on 19.04 daily

[Daniel van Vugt]

You should probably log a new bug for the 2540p.

---

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: linux (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  [HP Elitebook 840 G1] Screen is upside down on 19.04 daily

Status in linux package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  On the 19.04 daily image (2019-03-24), the screen on my laptop is
  completely upside down, from the moment the GUI loads. This does not
  happen on 18.04 and 18.10.

  It appears to be an accelerometer issue since holding the laptop
  upside down flips the image to its correct orientation - basically the
  functionality of the accelerometer is suddenly inverted.

  Please contact me if you want me to help testing the issue on my hardware. 
Thanks!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sharper1380 F pulseaudio
   /dev/snd/controlC1:  sharper1380 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-03-30 (6 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190330)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=1e4bdc5f-0616-42f3-8da2-4ec27df3fc55 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/12/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.44
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: 5CG4430MGN
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.44:bd04/12/2018:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.sku: D1F44AV
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821641/+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 1860764] Re: Line out audio device is missing after resume-from-suspend

[Daniel van Vugt]

Wait, did the problem appear in a daily update or do you mean it
appeared after upgrading from 18.10 to 19.10?

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

Title:
  Line out audio device is missing after resume-from-suspend

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  this problem happened after i updated system
  when i power on after sleeping i have problem with sounds. it doesn't work.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2511 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (362 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (79 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860764/+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 1860764] Re: Line out audio device is missing after resume-from-suspend

[Daniel van Vugt]

Please also try an older kernel like version 5.0, since you say the
regression appeared in an update.

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

Title:
  Line out audio device is missing after resume-from-suspend

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  this problem happened after i updated system
  when i power on after sleeping i have problem with sounds. it doesn't work.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2511 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (362 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (79 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860764/+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 1860764] Re: Line out audio device is missing after resume-from-suspend

[Daniel van Vugt]

Thanks for the bug report. Can you please try the latest kernel and tell
us if that has the same bug?

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5/

** Summary changed:

- problem after pulseaudio updating
+ Line out audio device is missing after resume-from-suspend

** Tags added: resume suspend-resume

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

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

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

Title:
  Line out audio device is missing after resume-from-suspend

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  this problem happened after i updated system
  when i power on after sleeping i have problem with sounds. it doesn't work.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2511 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (362 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (79 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860764/+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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in

[Daniel van Vugt]

Disco has reached end-of-life so will not be receiving fixes. That's why
the tag is removed.

https://wiki.ubuntu.com/Releases

** Tags removed: disco

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in

Status in PulseAudio:
  New
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/193

  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1583801/+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 1776654] Re: systemd upstream sysusers tests fails

[dann frazier]

Upstream PR: https://github.com/systemd/systemd/pull/14681

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

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

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

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

** Changed in: systemd (Ubuntu Focal)
   Status: Expired => In Progress

** Changed in: systemd (Ubuntu Eoan)
   Status: New => In Progress

** Changed in: systemd (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: systemd (Ubuntu Eoan)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: systemd (Ubuntu Focal)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  systemd upstream sysusers tests fails

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Invalid
Status in linux source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  In Progress
Status in linux source package in Focal:
  Invalid
Status in systemd source package in Focal:
  In Progress

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-cosmic-canonical-kernel-team-
  bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz

  == TEST-21-SYSUSERS ==
  make: Entering directory 
'/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS'
  TEST CLEANUP: Sysuser-related tests
  TEST SETUP: Sysuser-related tests
  TEST RUN: Sysuser-related tests
  *** Running test-1.input
  *** Running test-2.input
  *** Running test-3.input
  *** Running test-4.input
  *** Running test unhappy-1.input
  --- /var/tmp/systemd-test.TjNA7s/tmp/err  2018-06-13 00:22:12.805061468 
+
  +++ unhappy-1.expected-err2018-01-28 15:58:17.0 +
  @@ -1 +1 @@
  -Creating user xxx (n/a) with uid 312 and gid 310.
  +Failed to parse UID: '99': Numerical result out of range
   Unexpected error output for unhappy-1.input
  Creating user xxx (n/a) with uid 312 and gid 310.
  make: *** [run] Error 1
  Makefile:4: recipe for target 'run' failed
  make: Leaving directory 
'/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS'

  FAILED TESTS:  test/TEST-21-SYSUSERS
  autopkgtest [00:22:13]: test upstream: ---]
  upstream FAIL non-zero exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776654/+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 1776654] Re: systemd upstream sysusers tests fails

[dann frazier]

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: Expired

** Also affects: systemd (Ubuntu Focal)
   Importance: Undecided
   Status: Expired

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

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

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

Title:
  systemd upstream sysusers tests fails

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Invalid
Status in linux source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  In Progress
Status in linux source package in Focal:
  Invalid
Status in systemd source package in Focal:
  In Progress

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-cosmic-canonical-kernel-team-
  bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz

  == TEST-21-SYSUSERS ==
  make: Entering directory 
'/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS'
  TEST CLEANUP: Sysuser-related tests
  TEST SETUP: Sysuser-related tests
  TEST RUN: Sysuser-related tests
  *** Running test-1.input
  *** Running test-2.input
  *** Running test-3.input
  *** Running test-4.input
  *** Running test unhappy-1.input
  --- /var/tmp/systemd-test.TjNA7s/tmp/err  2018-06-13 00:22:12.805061468 
+
  +++ unhappy-1.expected-err2018-01-28 15:58:17.0 +
  @@ -1 +1 @@
  -Creating user xxx (n/a) with uid 312 and gid 310.
  +Failed to parse UID: '99': Numerical result out of range
   Unexpected error output for unhappy-1.input
  Creating user xxx (n/a) with uid 312 and gid 310.
  make: *** [run] Error 1
  Makefile:4: recipe for target 'run' failed
  make: Leaving directory 
'/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS'

  FAILED TESTS:  test/TEST-21-SYSUSERS
  autopkgtest [00:22:13]: test upstream: ---]
  upstream FAIL non-zero exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776654/+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 1782597] Re: Output of my USB audio device gets progressively bitcrushed

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

Title:
  Output of my USB audio device gets progressively bitcrushed

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After a while (between 5 and 10min), the output of my MOTU Ultralite
  AVB usb sound card gets dirtier and faintier (sounds like a
  bitcrushing effect) until there is no sound anymore. Sometimes muting
  the sound and switching to internal audio device and back to the motu
  will make the sound clean again, sometimes not. The Motu works ok with
  windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 19 16:52:34 2018
  InstallationDate: Installed on 2016-05-01 (809 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: UltraLite AVB Baptiste - UltraLite AVB Baptiste
  Symptom_PulseAudioLog:
   juil. 19 16:29:48 multivac pulseaudio[1945]: [autospawn] core-util.c: Home 
directory not accessible: Permission non accordée
   juil. 19 16:29:48 multivac pulseaudio[1945]: [autospawn] lock-autospawn.c: 
Impossible d'accèder au verrou autonome.
   juil. 19 16:29:48 multivac pulseaudio[1945]: [pulseaudio] main.c: Failed to 
acquire autospawn lock
   juil. 19 16:30:00 multivac dbus-daemon[1441]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.52' (uid=108 pid=3980 
comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined")
   juil. 19 16:30:06 multivac systemd[1]: session-c1.scope: Killing process 
3980 (pulseaudio) with signal SIGTERM.
  Symptom_Type: Sound works for a while, then breaks
  Title: [USB-Audio - UltraLite AVB Baptiste, playback] fails after a while
  UpgradeStatus: Upgraded to bionic on 2018-05-29 (50 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1782597/+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 1858802] Autopkgtest regression report (util-linux/2.31.1-0.4ubuntu3.5)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted util-linux (2.31.1-0.4ubuntu3.5) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

lxcfs/3.0.3-0ubuntu1~18.04.1 (s390x)
gnocchi/4.2.5-0ubuntu1 (armhf)
systemd/237-3ubuntu10.33 (amd64)
postgresql-10/10.10-0ubuntu0.18.04.1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#util-linux

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  libblkid: no bcache UUID due to ambivalent detection of bcache and
  xfs_external_log for regular xfs in bcache backing device

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Bionic:
  Fix Committed
Status in util-linux source package in Disco:
  Won't Fix
Status in util-linux source package in Eoan:
  Fix Committed
Status in util-linux source package in Focal:
  Fix Released
Status in util-linux package in Debian:
  Unknown

Bug description:
  [Impact]

   * Users with an XFS filesystem on top of bcache
     (this is seen on some ceph, cloud deployments)
     might fail to reference the bcache device by
     UUID or other udev properties.

   * The journal of the regular XFS filesystem in
     the bcache device is incorrectly detected as
     an XFS external log; so two superblocks are
     detected (bcache and xfs_external_log).

   * Thus blkid fails with ambivalent superblocks
     detected then doesn't provide the usual udev
     properties (UUID, etc.)

   * The fix improves the probe function for XFS
     external log so it detects it's regular XFS
     and bails out.

  [Test Case]

   * See test steps detailed in comment #7 and later.
     - Create an XFS filesystem with the journal/log
   in the beginning of the bcache device (< 256K).
     - Stop the bcache device.
     - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'.

     $ sudo make-bcache -B $BACKING_DEV
     $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV
     $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop
     $ sudo blkid -o udev -p $BACKING_DEV

  [Regression Potential]

   * The patch only changes the detection function
     for XFS external log to be more general about
     the sector where the magic of regular XFS may
     be found (which is shifted inside the bcache.)

   * It still checks at sector zero (the only one
     checked previously), so this behavior didn't
     change.

   * Possible regressions are actual XFS external
     log devices that are not anymore detected as
     such. (Although that would probably indicate
     a different bug in libblkid.)

  [Other Info]
   * upstream commit:
     
https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory

[Bug Watch Updater]

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

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

Title:
  pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or
  directory

Status in pam package in Ubuntu:
  Confirmed
Status in pam package in Debian:
  New

Bug description:
  Hello, after upgrading to focal I found the following in my journalctl
  output:

  Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory

  
  The login package stopped packaging this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656
  and now forcibly removes the file:
  https://paste.ubuntu.com/p/myh9cGWrHD/

  However, the pam package's pam_unix.so module has not yet been adapted to 
ignore this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-modules 1.3.1-5ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Fri Jan 24 23:35:33 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pam
  UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1860826/+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 1776654] Re: systemd upstream sysusers tests fails

[dann frazier]

Notice in the log in comment #6 that the unexpected error we are seeing
for "unhappy-2" is the expected error for "unhappy-1".

I wonder if there's a race here:

# tests for error conditions
for f in unhappy-*.input; do
echo "*** Running test $f"
rm -f $TESTDIR/etc/*
cp $f $TESTDIR/usr/lib/sysusers.d/test.conf
systemd-sysusers --root=$TESTDIR 2> /dev/null
journalctl -t systemd-sysusers -o cat | tail -n1 > 
$TESTDIR/tmp/err


That is, is it guaranteed that journalctl will see the errors from 
systemd-sysusers immediately? Is there something we could use to force it? Is 
that what 'journalctl --flush' does?

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

Title:
  systemd upstream sysusers tests fails

Status in linux package in Ubuntu:
  Expired
Status in systemd package in Ubuntu:
  Expired
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in linux source package in Cosmic:
  Expired

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-cosmic-canonical-kernel-team-
  bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz

  == TEST-21-SYSUSERS ==
  make: Entering directory 
'/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS'
  TEST CLEANUP: Sysuser-related tests
  TEST SETUP: Sysuser-related tests
  TEST RUN: Sysuser-related tests
  *** Running test-1.input
  *** Running test-2.input
  *** Running test-3.input
  *** Running test-4.input
  *** Running test unhappy-1.input
  --- /var/tmp/systemd-test.TjNA7s/tmp/err  2018-06-13 00:22:12.805061468 
+
  +++ unhappy-1.expected-err2018-01-28 15:58:17.0 +
  @@ -1 +1 @@
  -Creating user xxx (n/a) with uid 312 and gid 310.
  +Failed to parse UID: '99': Numerical result out of range
   Unexpected error output for unhappy-1.input
  Creating user xxx (n/a) with uid 312 and gid 310.
  make: *** [run] Error 1
  Makefile:4: recipe for target 'run' failed
  make: Leaving directory 
'/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS'

  FAILED TESTS:  test/TEST-21-SYSUSERS
  autopkgtest [00:22:13]: test upstream: ---]
  upstream FAIL non-zero exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776654/+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 1776654] Re: systemd upstream sysusers tests fails

[dann frazier]

Another instance:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/s/systemd/20200127_181441_fb524@/log.gz

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

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

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

Title:
  systemd upstream sysusers tests fails

Status in linux package in Ubuntu:
  Expired
Status in systemd package in Ubuntu:
  Expired
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in linux source package in Cosmic:
  Expired

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-cosmic-canonical-kernel-team-
  bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz

  == TEST-21-SYSUSERS ==
  make: Entering directory 
'/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS'
  TEST CLEANUP: Sysuser-related tests
  TEST SETUP: Sysuser-related tests
  TEST RUN: Sysuser-related tests
  *** Running test-1.input
  *** Running test-2.input
  *** Running test-3.input
  *** Running test-4.input
  *** Running test unhappy-1.input
  --- /var/tmp/systemd-test.TjNA7s/tmp/err  2018-06-13 00:22:12.805061468 
+
  +++ unhappy-1.expected-err2018-01-28 15:58:17.0 +
  @@ -1 +1 @@
  -Creating user xxx (n/a) with uid 312 and gid 310.
  +Failed to parse UID: '99': Numerical result out of range
   Unexpected error output for unhappy-1.input
  Creating user xxx (n/a) with uid 312 and gid 310.
  make: *** [run] Error 1
  Makefile:4: recipe for target 'run' failed
  make: Leaving directory 
'/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS'

  FAILED TESTS:  test/TEST-21-SYSUSERS
  autopkgtest [00:22:13]: test upstream: ---]
  upstream FAIL non-zero exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776654/+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 1861043] [NEW] Xorg freeze

[Christopher]

Public bug reported:

So under high load I can generally cause a freeze in Gnome/Ubuntu. This
is somewhat expected and likely should be fixed by some sort of OOM
killer. However that's only part of the problem. Virtual Consoles are
disabled (`/etc/systemd/logind.conf` `NAutoVTs` by default) and I
believe that too to be a bug. In the past I could have Switched VT's
logged in and killed of a high memory/cpu process or two. Now I have to
hard kill the box and risk loosing in progress work which is ungainly.

If there's a worry about "what will new users do if they accidentally
hit CTRL+ALT+F\d" maybe instead of disabling it we could change the
default login message to have a "Don't know how you got here? Hit
CTLR+ALT+F1 to go back."

Also because I have to hard restart apport never get's called to show
exactly why the system is hanging.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu13
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
.proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:03:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.44  Sun Dec  8 03:38:56 
UTC 2019
 GCC version:  gcc version 9.2.1 20200123 (Ubuntu 9.2.1-25ubuntu1)
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 27 15:13:07 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 440.44, 5.4.0-12-generic, x86_64: installed
 nvidia, 440.44, 5.4.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Since before I upgraded
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 5500 [1028:062b]
   Subsystem: Dell GM108M [GeForce 840M] [1028:062b]
InstallationDate: Installed on 2020-01-14 (13 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106)
MachineType: Dell Inc. Latitude E5450
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=37b7ed5e-16a1-4e03-ad70-e85dfec9bf53 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/30/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0MVKK7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd07/30/2015:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn0MVKK7:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5450
dmi.product.sku: 062B
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.4-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal freeze has-fix has-workaround 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/1861043

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  So under high load I can generally cause a freeze in Gnome/Ubuntu.
  This is somewhat expected and likely should be fixed by some sort of
  OOM killer. However that's only part of the problem. Virtual Consoles
  are disabled (`/etc/systemd/logind.conf` `NAutoVTs` by default) and I
  believe that too to be a bug. In the past I could have Switched VT's
  logged in and killed of a high memory/cpu process or two. Now I have
  to hard kill the box and risk loosing in progress work which is
  ungainly.

  If there's a worry about "what will new users do if they accidentally
  hit CTRL+ALT+F\d" maybe instead of disabling it we could change the
  default login message to have a "Don't know how you got here? Hit
  CTLR+ALT+F1 to go 

[Touch-packages] [Bug 1860956] Re: network-manager 1.16.0-0ubuntu2 ADT test failure with linux 5.0.0-40.44

[Khaled El Mously]

Thanks Sebastien. This is from Disco actually.

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

Title:
  network-manager 1.16.0-0ubuntu2 ADT test failure with linux
  5.0.0-40.44

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Testing failed on:
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/ppc64el/n/network-manager/20200124_174131_d1990@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1860956/+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 69724] Re: Mawk does not support Posix character classes in expressions

[Bug Watch Updater]

** Changed in: mawk (Debian)
   Status: Confirmed => Fix Released

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

Title:
  Mawk does not support Posix character classes in expressions

Status in mawk package in Ubuntu:
  Triaged
Status in mawk package in Debian:
  Fix Released

Bug description:
  Binary package hint: mawk

  Mawk does not support Posix character classes, such as [:upper:] and
  [:lower:], in regular expressions.  This makes it more difficult to
  write portable Awk scripts (since [A-Z] match lower-case characters in
  Gawk using non-English locales)

  E.G.:

  $ echo x | mawk '/[[:lower:]]/'
  $ echo x | gawk '/[[:lower:]]/'
  x
  $

  Attached is a patch to fix this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/69724/+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 1782577] Re: docker: impossible to create image with python3 because tzdata

[revo]

With the env variable : 
ENV DEBIAN_FRONTEND noninteractive

the Dockerfile is built successfully

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

Title:
  docker: impossible to create image with python3 because tzdata

Status in cloud-images:
  New
Status in debconf package in Ubuntu:
  New
Status in debconf package in Debian:
  New

Bug description:
  In my application I have to use both "supervisor" and some ML stuff,
  so I need to include python-3, numpy and pandas

  FROM ubuntu:latest
  RUN apt-get update
  RUN apt-get install -y supervisor python3 python3-pip python3-pymongo 
python3-numpy python3-pandas

  This appends with the current ubuntu:latest

  sha256:30e04ddada6eb09c12330c7df72cad1573916c7100168c34076808169ff6d805

  When I try to make a built of this, I seems that python3 depends on
  tzdata (and many other things), but then it stops waiting for a user
  input, and I unable to send an input by hand or other way

  Setting up libldap-common (2.4.45+dfsg-1ubuntu1) ...
  Setting up libreadline7:amd64 (7.0-3) ...
  Setting up tzdata (2018d-1) ...
  debconf: unable to initialize frontend: Dialog
  debconf: (TERM is not set, so the dialog frontend is not usable.)
  debconf: falling back to frontend: Readline
  Configuring tzdata
  --

  Please select the geographic area in which you live. Subsequent configuration
  questions will narrow this down by presenting a list of cities, representing
  the time zones in which they are located.

1. Africa  4. Australia  7. Atlantic  10. Pacific  13. Etc
2. America 5. Arctic 8. Europe11. SystemV
3. Antarctica  6. Asia   9. Indian12. US
  Geographic area: 

  So I am unable to create my docker image!!

  This is some kind of regression, 2 weeks ago it worked

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1782577/+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 1858802] Autopkgtest regression report (util-linux/2.27.1-6ubuntu3.10)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted util-linux (2.27.1-6ubuntu3.10) for 
xenial have finished running.
The following regressions have been reported in tests triggered by the package:

nplan/0.32~16.04.7 (amd64)
mysql-5.7/5.7.28-0ubuntu0.16.04.2 (i386, ppc64el, amd64)
zfs-linux/0.6.5.6-0ubuntu28 (ppc64el)
lxd/2.0.11-0ubuntu1~16.04.4 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html#util-linux

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  libblkid: no bcache UUID due to ambivalent detection of bcache and
  xfs_external_log for regular xfs in bcache backing device

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Bionic:
  Fix Committed
Status in util-linux source package in Disco:
  Won't Fix
Status in util-linux source package in Eoan:
  Fix Committed
Status in util-linux source package in Focal:
  Fix Released
Status in util-linux package in Debian:
  Unknown

Bug description:
  [Impact]

   * Users with an XFS filesystem on top of bcache
     (this is seen on some ceph, cloud deployments)
     might fail to reference the bcache device by
     UUID or other udev properties.

   * The journal of the regular XFS filesystem in
     the bcache device is incorrectly detected as
     an XFS external log; so two superblocks are
     detected (bcache and xfs_external_log).

   * Thus blkid fails with ambivalent superblocks
     detected then doesn't provide the usual udev
     properties (UUID, etc.)

   * The fix improves the probe function for XFS
     external log so it detects it's regular XFS
     and bails out.

  [Test Case]

   * See test steps detailed in comment #7 and later.
     - Create an XFS filesystem with the journal/log
   in the beginning of the bcache device (< 256K).
     - Stop the bcache device.
     - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'.

     $ sudo make-bcache -B $BACKING_DEV
     $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV
     $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop
     $ sudo blkid -o udev -p $BACKING_DEV

  [Regression Potential]

   * The patch only changes the detection function
     for XFS external log to be more general about
     the sector where the magic of regular XFS may
     be found (which is shifted inside the bcache.)

   * It still checks at sector zero (the only one
     checked previously), so this behavior didn't
     change.

   * Possible regressions are actual XFS external
     log devices that are not anymore detected as
     such. (Although that would probably indicate
     a different bug in libblkid.)

  [Other Info]
   * upstream commit:
     
https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1781428] Autopkgtest regression report (pulseaudio/1:8.0-0ubuntu3.11)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted pulseaudio (1:8.0-0ubuntu3.11) for 
xenial have finished running.
The following regressions have been reported in tests triggered by the package:

openjdk-8/8u222-b10-1ubuntu1~16.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html#pulseaudio

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  please enable snap mediation support

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed
Status in pulseaudio source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Ubuntu 16.10 added rudimentary snap support to disable audio recording if the 
connecting process was a snap. By Ubuntu 18.04, something changed in the build 
resulting in 'Enable Snappy support: no' with audio recording no longer being 
mediated by pulseaudio (access to the pulseaudio socket continued to be 
mediated by snapd's apparmor policy). This resulted in any application with the 
pulseaudio interface connected to be able to also record. Ubuntu 16.04 never 
had mediation patches and always allowed recording when the pulseaudio 
interface was connected.

  To correct this situation but not regress existing behavior, Ubuntu
  19.04's pulseaudio was updated patch to allow playback to all
  connected clients (snaps or not), record by classic snaps (see bug
  1787324) and record by strict mode snaps if either the pulseaudio or
  new-in-snapd-2.41 audio-record interfaces were connected. With this
  change, snapd is in a position to migrate snaps to the new audio-
  playback and audio-record interfaces and properly mediate audio
  recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio-
  interface-deprecation/13418).

  The patch to pulseaudio consists of adding a module, enabling it in
  default.pa and then when it is enabled, pulseaudio when faced with a
  record operation will, when the connecting process is a snap (ie, its
  security label (ie, apparmor label) starts with 'snap.'), query snapd
  via its control socket to ask if the snap is classic and if not,
  whether the pulseaudio or audio-record interfaces are connected.
  Adjusting pulseaudio in the manner does not require coordination with
  any release of snapd. It does need a newer version of snapd-glib,
  which was recently updated to 1.49 in the last SRU.

  [Test Case]

  IMPORTANT: if updating pulseaudio while the session is running, either
  need to reboot for the test or kill pulseaudio so it can restart with
  the new snap policy

  For unconfined applications:
  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  For confined, non-snap applications:
  $ sudo apt-get install evince

  $ aa-exec -p /usr/bin/evince -- paplay
  /usr/share/sounds/alsa/Noise.wav && echo yes

  $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && 
echo "yes"  # ctrl-c to stop recording
  ^Cyes

  $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes"
  yes

  For classic snaps:
  $ sudo snap install test-snapd-classic-confinement --classic

  $ snap run --shell test-snapd-classic-confinement

  $ cat /proc/self/attr/current   # verify we are classic confined
  snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain)

  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  $ exit # out of snap run --shell

  For strict snaps with pulseaudio:
  $ sudo snap install test-snapd-pulseaudio --edge

  $ snap connections test-snapd-pulseaudio
  Interface   Plug  Slot Notes
  pulseaudio  test-snapd-pulseaudio:pulseaudio  :pulseaudio  -

  $ test-snapd-pulseaudio.play --help  # ensure SNAP dirs are created
  ...

  $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-
  pulseaudio/common/

  $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav 
&& echo yes
  xcb_connection_has_error() returned true
  yes

  (note, the xcb_connection_has_error() message is due to the x11
  interface not being connecting which is unrelated to mediation. x11 is
  left out to ensure that just audio-playback/audio-record are tested)

  $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass
  ...
  ^Cyes

  $ 

[Touch-packages] [Bug 1860994] Re: Indicator menu is too wide

[Nicholas Guriev]

** Tags added: eoan

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

Title:
  Indicator menu is too wide

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  The indicator's context menu does not appear to have a maximal width.
  This leads to an unattractive appearance when the show-events key in
  the com.canonical.indicator.datetime schema is true (default value)
  and there is an event with quite long name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1860994/+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 1860994] Re: Indicator menu is too wide

[Nicholas Guriev]

Khurshid Alam, yes, it is MATE. Here is an Apport output, sorry I did
not realize to attach it earlier.

** Attachment added: "Apport.log"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1860994/+attachment/5323320/+files/Apport.log

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

Title:
  Indicator menu is too wide

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  The indicator's context menu does not appear to have a maximal width.
  This leads to an unattractive appearance when the show-events key in
  the com.canonical.indicator.datetime schema is true (default value)
  and there is an event with quite long name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1860994/+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 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory

[Balint Reczey]

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

** Changed in: pam (Debian)
 Remote watch: Debian Bug tracker #674857 => Debian Bug tracker #936071

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

Title:
  pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or
  directory

Status in pam package in Ubuntu:
  Confirmed
Status in pam package in Debian:
  Unknown

Bug description:
  Hello, after upgrading to focal I found the following in my journalctl
  output:

  Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory

  
  The login package stopped packaging this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656
  and now forcibly removes the file:
  https://paste.ubuntu.com/p/myh9cGWrHD/

  However, the pam package's pam_unix.so module has not yet been adapted to 
ignore this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-modules 1.3.1-5ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Fri Jan 24 23:35:33 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pam
  UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1860826/+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 1783881] Re: ltp-syscalls: msgstress03 fails because systemd limits number of processes

[Sean Feole]

** Tags added: 5.3

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

Title:
  ltp-syscalls: msgstress03 fails because systemd limits number of
  processes

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in systemd source package in Bionic:
  New

Bug description:
  As systemd limits the number of processes, this test will fail because
  it can't fork enough processes. That is limited to when the test is
  run after logging as user 1000, then running sudo. I guess that
  logging as root may not cause this to happen.

  # ./testcases/bin/msgstress03 
  Fork failed (may be OK if under stress)
  Fork failed (may be OK if under stress)
  msgstress031  TFAIL  :  msgstress03.c:157:  Fork failed (may be OK if 
under stress)
  #

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+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 1860985] Re: packagekitd using 100% CPU

[Julian Andres Klode]

Well, we can't discuss two issues in one bug. The setting is completely
irrelevant for PackageKit, as that controls APT's downloading of new
update information. That said, I think we did override that somewhere so
that PackageKit does not download it either. Please open a separate bug
report for that.

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

Title:
  packagekitd using 100% CPU

Status in packagekit package in Ubuntu:
  Incomplete

Bug description:
  That's all I can report at this stage. Any attempt to kill it or
  disable the service fails and up goes its CPU usage, fans blowing the
  works!

  packagekit status give 
  Jan 27 13:59:02 owen-Precision-M4600 https[820460]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 http[820454]: Libgcrypt warning: missing 
initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 store[820894]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 https[820443]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 https[820455]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying 
to obtain org.freedesktop.packagekit.system-sources-refresh auth 
(only_trusted:0)
  Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained 
auth for org.freedesktop.packagekit.system-sources-refresh
  Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: refresh-cache 
transaction /29159_bdcaeddd from uid 1000 finished with cancelled-priority 
after 2137ms
  Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying 
to obtain org.freedesktop.packagekit.system-sources-refresh auth 
(only_trusted:0)
  Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained 
auth for org.freedesktop.packagekit.system-sources-refresh

  I am uid: 1000. It would be helpful if it gave some indication as to
  "the application". I can't find anywhere to admin this. It looks like
  my trust level is too low "only_trusted:0"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: packagekit 1.1.13-2
  Uname: Linux 5.5.0-050500rc7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Jan 27 13:54:13 2020
  InstallationDate: Installed on 2017-12-06 (782 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: packagekit
  UpgradeStatus: Upgraded to focal on 2019-11-13 (74 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1860985/+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 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory

[Balint Reczey]

@seb128 reading the referenced bug further reveals that I'm waiting for
PAM maintainers' input on this.

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

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

** Changed in: pam (Ubuntu)
 Assignee: Balint Reczey (rbalint) => (unassigned)

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

Title:
  pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or
  directory

Status in pam package in Ubuntu:
  Confirmed
Status in pam package in Debian:
  Unknown

Bug description:
  Hello, after upgrading to focal I found the following in my journalctl
  output:

  Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory

  
  The login package stopped packaging this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656
  and now forcibly removes the file:
  https://paste.ubuntu.com/p/myh9cGWrHD/

  However, the pam package's pam_unix.so module has not yet been adapted to 
ignore this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-modules 1.3.1-5ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Fri Jan 24 23:35:33 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pam
  UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1860826/+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 1860855] Re: packagekitd crashed with SIGSEGV

[Julian Andres Klode]

This bug was fixed in the package apt - 1.9.8

---
apt (1.9.8) experimental; urgency=medium

  * pkgcache.cc: Mix PACKAGE_VERSION into the cache hash
  * mmap: Do not look for empty pool unless we need to
  * apt-verbatim.ent: Update ubuntu-codename from disco to focal
  * NewGroup: Create GrpIterator after allocation (fix segfault)

 -- Julian Andres Klode   Mon, 27 Jan 2020 13:25:52
+0100

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

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

Title:
  packagekitd crashed with SIGSEGV

Status in apt package in Ubuntu:
  Fix Released
Status in packagekit package in Ubuntu:
  Invalid

Bug description:
  Message popped up about there being a system error.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: packagekit 1.1.13-2
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Sat Jan 25 13:28:12 2020
  ExecutablePath: /usr/lib/packagekit/packagekitd
  InstallationDate: Installed on 2020-01-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/sh
  SegvAnalysis:
   Segfault happened at: 0x7f8244d2f5e3:mov%eax,(%rdx)
   PC (0x7f8244d2f5e3) ok
   source "%eax" ok
   destination "(%rdx)" (0x7f8235e09040) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: packagekit
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libapt-pkg.so.5.90
   ?? () from /lib/x86_64-linux-gnu/libapt-pkg.so.5.90
   ?? () from /lib/x86_64-linux-gnu/libapt-pkg.so.5.90
   ?? () from /lib/x86_64-linux-gnu/libapt-pkg.so.5.90
   ?? () from /lib/x86_64-linux-gnu/libapt-pkg.so.5.90
  Title: packagekitd crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1860855/+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 1860855] Re: packagekitd crashed with SIGSEGV

[Julian Andres Klode]

(Sorry, the bug is not listed in the changelog, so closed it with
syncpackage, so it does not get forgotten - will take some time to
migrate from proposed to release pocket)

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

Title:
  packagekitd crashed with SIGSEGV

Status in apt package in Ubuntu:
  Fix Released
Status in packagekit package in Ubuntu:
  Invalid

Bug description:
  Message popped up about there being a system error.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: packagekit 1.1.13-2
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Sat Jan 25 13:28:12 2020
  ExecutablePath: /usr/lib/packagekit/packagekitd
  InstallationDate: Installed on 2020-01-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/sh
  SegvAnalysis:
   Segfault happened at: 0x7f8244d2f5e3:mov%eax,(%rdx)
   PC (0x7f8244d2f5e3) ok
   source "%eax" ok
   destination "(%rdx)" (0x7f8235e09040) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: packagekit
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libapt-pkg.so.5.90
   ?? () from /lib/x86_64-linux-gnu/libapt-pkg.so.5.90
   ?? () from /lib/x86_64-linux-gnu/libapt-pkg.so.5.90
   ?? () from /lib/x86_64-linux-gnu/libapt-pkg.so.5.90
   ?? () from /lib/x86_64-linux-gnu/libapt-pkg.so.5.90
  Title: packagekitd crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1860855/+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 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory

[Sebastien Bacher]

Looks like Balint has been looking at that problem from the Debian side,
assigning to him

@Balint, feel free to unassign if I got that wrong :)

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

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

** Changed in: pam (Ubuntu)
 Assignee: (unassigned) => Balint Reczey (rbalint)

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

Title:
  pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or
  directory

Status in pam package in Ubuntu:
  Confirmed
Status in pam package in Debian:
  Unknown

Bug description:
  Hello, after upgrading to focal I found the following in my journalctl
  output:

  Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory

  
  The login package stopped packaging this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656
  and now forcibly removes the file:
  https://paste.ubuntu.com/p/myh9cGWrHD/

  However, the pam package's pam_unix.so module has not yet been adapted to 
ignore this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-modules 1.3.1-5ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Fri Jan 24 23:35:33 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pam
  UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1860826/+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 1860985] Re: packagekitd using 100% CPU

[Owen]

The PPA was deb [arch=amd64] http://dl.google.com/linux/webdesigner/deb/
stable main

The linked ticket does sound like the issue, but my other concern is
despite setting the "Automatically check for updates" to "Never" is
Software and Updates the system continues to look for update at quite a
high frequency and even when packagekitd is "idle" it still uses 20% CPU

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

Title:
  packagekitd using 100% CPU

Status in packagekit package in Ubuntu:
  Incomplete

Bug description:
  That's all I can report at this stage. Any attempt to kill it or
  disable the service fails and up goes its CPU usage, fans blowing the
  works!

  packagekit status give 
  Jan 27 13:59:02 owen-Precision-M4600 https[820460]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 http[820454]: Libgcrypt warning: missing 
initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 store[820894]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 https[820443]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 https[820455]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying 
to obtain org.freedesktop.packagekit.system-sources-refresh auth 
(only_trusted:0)
  Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained 
auth for org.freedesktop.packagekit.system-sources-refresh
  Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: refresh-cache 
transaction /29159_bdcaeddd from uid 1000 finished with cancelled-priority 
after 2137ms
  Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying 
to obtain org.freedesktop.packagekit.system-sources-refresh auth 
(only_trusted:0)
  Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained 
auth for org.freedesktop.packagekit.system-sources-refresh

  I am uid: 1000. It would be helpful if it gave some indication as to
  "the application". I can't find anywhere to admin this. It looks like
  my trust level is too low "only_trusted:0"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: packagekit 1.1.13-2
  Uname: Linux 5.5.0-050500rc7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Jan 27 13:54:13 2020
  InstallationDate: Installed on 2017-12-06 (782 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: packagekit
  UpgradeStatus: Upgraded to focal on 2019-11-13 (74 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1860985/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device

[Mauricio Faria de Oliveira]

Verification done on bionic-proposed.
Now libblkid1 detects only the bcache superblock and prints udev/uuid variables.

$ lsb_release -cs
bionic

$ DISK_IMG=disk.img
$ rm -f $DISK_IMG
$ dd if=/dev/zero of=$DISK_IMG bs=1G count=0 seek=1
$ BACKING_DEV=$(sudo losetup --find --show $DISK_IMG)
$ sudo make-bcache -B $BACKING_DEV
$ BCACHE_DEV="$(readlink -e /sys/block/$(basename $BACKING_DEV)/bcache/dev)"
$ BCACHE_DEV="/dev/$(basename $BCACHE_DEV)"
$ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV
$ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop

$ sudo hexdump -C $BACKING_DEV | grep -m2 -e XFSB -e 'fe ed ba be'
2000  58 46 53 42 00 00 10 00  00 00 00 00 00 03 f0 00  |XFSB|
7000  fe ed ba be 00 00 00 01  00 00 00 02 00 00 02 00  ||

bionic-updates:
---

$ dpkg -s libblkid1 | grep -i version
Version: 2.31.1-0.4ubuntu3.4

$ sudo blkid -o udev -p $BACKING_DEV
ID_FS_AMBIVALENT=other:bcache other:xfs_external_log

bionic-proposed:
---

$ apt-cache madison libblkid1 | grep proposed
 libblkid1 | 2.31.1-0.4ubuntu3.5 | http://archive.ubuntu.com/ubuntu 
bionic-proposed/main amd64 Packages

$ sudo apt install libblkid1 -y

$ dpkg -s libblkid1 | grep -i version:
Version: 2.31.1-0.4ubuntu3.5

$ sudo blkid -o udev -p $BACKING_DEV
ID_FS_UUID=7879f264-a1e6-4b7f-8fd0-2565c10adc44
ID_FS_UUID_ENC=7879f264-a1e6-4b7f-8fd0-2565c10adc44
ID_FS_TYPE=bcache
ID_FS_USAGE=other

** Tags added: verification-done-bionic

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

Title:
  libblkid: no bcache UUID due to ambivalent detection of bcache and
  xfs_external_log for regular xfs in bcache backing device

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Bionic:
  Fix Committed
Status in util-linux source package in Disco:
  Won't Fix
Status in util-linux source package in Eoan:
  Fix Committed
Status in util-linux source package in Focal:
  Fix Released
Status in util-linux package in Debian:
  Unknown

Bug description:
  [Impact]

   * Users with an XFS filesystem on top of bcache
     (this is seen on some ceph, cloud deployments)
     might fail to reference the bcache device by
     UUID or other udev properties.

   * The journal of the regular XFS filesystem in
     the bcache device is incorrectly detected as
     an XFS external log; so two superblocks are
     detected (bcache and xfs_external_log).

   * Thus blkid fails with ambivalent superblocks
     detected then doesn't provide the usual udev
     properties (UUID, etc.)

   * The fix improves the probe function for XFS
     external log so it detects it's regular XFS
     and bails out.

  [Test Case]

   * See test steps detailed in comment #7 and later.
     - Create an XFS filesystem with the journal/log
   in the beginning of the bcache device (< 256K).
     - Stop the bcache device.
     - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'.

     $ sudo make-bcache -B $BACKING_DEV
     $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV
     $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop
     $ sudo blkid -o udev -p $BACKING_DEV

  [Regression Potential]

   * The patch only changes the detection function
     for XFS external log to be more general about
     the sector where the magic of regular XFS may
     be found (which is shifted inside the bcache.)

   * It still checks at sector zero (the only one
     checked previously), so this behavior didn't
     change.

   * Possible regressions are actual XFS external
     log devices that are not anymore detected as
     such. (Although that would probably indicate
     a different bug in libblkid.)

  [Other Info]
   * upstream commit:
     
https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device

[Mauricio Faria de Oliveira]

Verification done on eoan-proposed.
Now libblkid1 detects only the bcache superblock and prints udev/uuid variables.

$ lsb_release -cs
eoan

$ DISK_IMG=disk.img
$ rm -f $DISK_IMG
$ dd if=/dev/zero of=$DISK_IMG bs=1G count=0 seek=1
$ BACKING_DEV=$(sudo losetup --find --show $DISK_IMG)
$ sudo make-bcache -B $BACKING_DEV
$ BCACHE_DEV="$(readlink -e /sys/block/$(basename $BACKING_DEV)/bcache/dev)"
$ BCACHE_DEV="/dev/$(basename $BCACHE_DEV)"
$ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV
$ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop

$ sudo hexdump -C $BACKING_DEV | grep -m2 -e XFSB -e 'fe ed ba be'
2000  58 46 53 42 00 00 10 00  00 00 00 00 00 03 f0 00  |XFSB|
7000  fe ed ba be 00 00 00 01  00 00 00 02 00 00 02 00  ||

eoan-updates:
---

$ dpkg -s libblkid1 | grep -i version:
Version: 2.34-0.1ubuntu2.1

$ sudo blkid -o udev -p $BACKING_DEV
ID_FS_AMBIVALENT=other:bcache other:xfs_external_log

eoan-proposed:
---

$ apt-cache madison libblkid1 | grep proposed
 libblkid1 | 2.34-0.1ubuntu2.2 | http://archive.ubuntu.com/ubuntu 
eoan-proposed/main amd64 Packages

$ sudo apt install libblkid1 -y

$ dpkg -s libblkid1 | grep -i version:
Version: 2.34-0.1ubuntu2.2

$ sudo blkid -o udev -p $BACKING_DEV
ID_FS_UUID=55bac736-a3dc-4d9a-80e9-330ba46dd97d
ID_FS_UUID_ENC=55bac736-a3dc-4d9a-80e9-330ba46dd97d
ID_FS_TYPE=bcache
ID_FS_USAGE=other

** Tags added: verification-done-eoan

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

Title:
  libblkid: no bcache UUID due to ambivalent detection of bcache and
  xfs_external_log for regular xfs in bcache backing device

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Bionic:
  Fix Committed
Status in util-linux source package in Disco:
  Won't Fix
Status in util-linux source package in Eoan:
  Fix Committed
Status in util-linux source package in Focal:
  Fix Released
Status in util-linux package in Debian:
  Unknown

Bug description:
  [Impact]

   * Users with an XFS filesystem on top of bcache
     (this is seen on some ceph, cloud deployments)
     might fail to reference the bcache device by
     UUID or other udev properties.

   * The journal of the regular XFS filesystem in
     the bcache device is incorrectly detected as
     an XFS external log; so two superblocks are
     detected (bcache and xfs_external_log).

   * Thus blkid fails with ambivalent superblocks
     detected then doesn't provide the usual udev
     properties (UUID, etc.)

   * The fix improves the probe function for XFS
     external log so it detects it's regular XFS
     and bails out.

  [Test Case]

   * See test steps detailed in comment #7 and later.
     - Create an XFS filesystem with the journal/log
   in the beginning of the bcache device (< 256K).
     - Stop the bcache device.
     - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'.

     $ sudo make-bcache -B $BACKING_DEV
     $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV
     $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop
     $ sudo blkid -o udev -p $BACKING_DEV

  [Regression Potential]

   * The patch only changes the detection function
     for XFS external log to be more general about
     the sector where the magic of regular XFS may
     be found (which is shifted inside the bcache.)

   * It still checks at sector zero (the only one
     checked previously), so this behavior didn't
     change.

   * Possible regressions are actual XFS external
     log devices that are not anymore detected as
     such. (Although that would probably indicate
     a different bug in libblkid.)

  [Other Info]
   * upstream commit:
     
https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device

[Mauricio Faria de Oliveira]

Verification done on xenial-proposed.
Now libblkid1 detects only the bcache superblock and prints udev/uuid variables.

$ lsb_release -cs
xenial

$ DISK_IMG=disk.img
$ rm -f $DISK_IMG
$ dd if=/dev/zero of=$DISK_IMG bs=1G count=0 seek=1
$ BACKING_DEV=$(sudo losetup --find --show $DISK_IMG)
$ sudo make-bcache -B $BACKING_DEV
$ BCACHE_DEV="$(readlink -e /sys/block/$(basename $BACKING_DEV)/bcache/dev)"
$ BCACHE_DEV="/dev/$(basename $BCACHE_DEV)"
$ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV
$ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop

$ sudo hexdump -C $BACKING_DEV | grep -m2 -e XFSB -e 'fe ed ba be'
2000  58 46 53 42 00 00 10 00  00 00 00 00 00 03 f0 00  |XFSB|
7000  fe ed ba be 00 00 00 01  00 00 00 02 00 00 00 14  ||

xenial-updates:
---

$ dpkg -s libblkid1 | grep -i version
Version: 2.27.1-6ubuntu3.9

$ sudo blkid -o udev -p $BACKING_DEV
ID_FS_AMBIVALENT=other:bcache other:xfs_external_log

xenial-proposed:
---

$ apt-cache madison libblkid1 | grep proposed
 libblkid1 | 2.27.1-6ubuntu3.10 | http://archive.ubuntu.com/ubuntu 
xenial-proposed/main amd64 Packages

$ sudo apt install libblkid1 -y

$ dpkg -s libblkid1 | grep -i version
Version: 2.27.1-6ubuntu3.10

$ sudo blkid -o udev -p $BACKING_DEV
ID_FS_UUID=6cdf846c-52ea-4f24-8554-7302c41bca8f
ID_FS_UUID_ENC=6cdf846c-52ea-4f24-8554-7302c41bca8f
ID_FS_TYPE=bcache
ID_FS_USAGE=other

** Tags added: verification-done-xenial

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

Title:
  libblkid: no bcache UUID due to ambivalent detection of bcache and
  xfs_external_log for regular xfs in bcache backing device

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Bionic:
  Fix Committed
Status in util-linux source package in Disco:
  Won't Fix
Status in util-linux source package in Eoan:
  Fix Committed
Status in util-linux source package in Focal:
  Fix Released
Status in util-linux package in Debian:
  Unknown

Bug description:
  [Impact]

   * Users with an XFS filesystem on top of bcache
     (this is seen on some ceph, cloud deployments)
     might fail to reference the bcache device by
     UUID or other udev properties.

   * The journal of the regular XFS filesystem in
     the bcache device is incorrectly detected as
     an XFS external log; so two superblocks are
     detected (bcache and xfs_external_log).

   * Thus blkid fails with ambivalent superblocks
     detected then doesn't provide the usual udev
     properties (UUID, etc.)

   * The fix improves the probe function for XFS
     external log so it detects it's regular XFS
     and bails out.

  [Test Case]

   * See test steps detailed in comment #7 and later.
     - Create an XFS filesystem with the journal/log
   in the beginning of the bcache device (< 256K).
     - Stop the bcache device.
     - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'.

     $ sudo make-bcache -B $BACKING_DEV
     $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV
     $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop
     $ sudo blkid -o udev -p $BACKING_DEV

  [Regression Potential]

   * The patch only changes the detection function
     for XFS external log to be more general about
     the sector where the magic of regular XFS may
     be found (which is shifted inside the bcache.)

   * It still checks at sector zero (the only one
     checked previously), so this behavior didn't
     change.

   * Possible regressions are actual XFS external
     log devices that are not anymore detected as
     such. (Although that would probably indicate
     a different bug in libblkid.)

  [Other Info]
   * upstream commit:
     
https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1860994] Re: Indicator menu is too wide

[Khurshid Alam]

Which theme are you using ? Looks like mate which doesn't have calendar
widget styles for indicator-datetime.

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

Title:
  Indicator menu is too wide

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  The indicator's context menu does not appear to have a maximal width.
  This leads to an unattractive appearance when the show-events key in
  the com.canonical.indicator.datetime schema is true (default value)
  and there is an event with quite long name.

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

[Jeremy Ebert]

I have the same issue on a HP Spectre Folio 13 with ubuntu 19.10.
Internal microphone does not work. Headset microphone is detected when
connected through a usb-c hub.

-- 
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 1860042] Re: openCL application gives error after update

[Nikolas Hericks]

Hi,

looks as I have the same issue:

Jan 27 12:26:44  libreoffice-calc.desktop[21996]: ac_rtld error: 
!s->is_rx
Jan 27 12:26:44  libreoffice-calc.desktop[21996]: LLVM failed to upload 
shader

with mesa-opencl-icd 19.2.1-1ubuntu1~18.04.1

Kind regards,

Nikolas

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

Title:
  openCL application gives error after update

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  My OpenCL program was working normally until a software update.

  The program prints out:

  ac_rtld error: !s->is_rx
  LLVM failed to upload shader

  when clEnqueueNDRangeKernel is called.

  I've downloaded the source for mesa and traced the problem to the
  gallium radeon driver. The first error message is from

  mesa-19.2.1/src/amd/common/ac_rtld.c

  and the second error message is from

  mesa-19.2.1/src/gallium/drivers/radeonsi/si_compute.c

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libllvm9 1:9-2~ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-lowlatency 4.15.18
  Uname: Linux 4.15.0-74-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 14:35:15 2020
  InstallationDate: Installed on 2018-04-28 (628 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: mesa-opencl-icd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860042/+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 1860994] Re: Indicator menu is too wide

[Sebastien Bacher]

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Indicator menu is too wide

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  The indicator's context menu does not appear to have a maximal width.
  This leads to an unattractive appearance when the show-events key in
  the com.canonical.indicator.datetime schema is true (default value)
  and there is an event with quite long name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1860994/+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 1860994] [NEW] Indicator menu is too wide

[Nicholas Guriev]

Public bug reported:

The indicator's context menu does not appear to have a maximal width.
This leads to an unattractive appearance when the show-events key in the
com.canonical.indicator.datetime schema is true (default value) and
there is an event with quite long name.

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Screenshot at 2020-01-27 16-58-54.png"
   
https://bugs.launchpad.net/bugs/1860994/+attachment/5323318/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%B2%202020-01-27%2016-58-54.png

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

Title:
  Indicator menu is too wide

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  The indicator's context menu does not appear to have a maximal width.
  This leads to an unattractive appearance when the show-events key in
  the com.canonical.indicator.datetime schema is true (default value)
  and there is an event with quite long name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1860994/+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 1860042] Re: openCL application gives error after update

[Timo Aaltonen]

But someone said on your other bug (1860199) that mesa master works
already, so just post your patch here first.

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

Title:
  openCL application gives error after update

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  My OpenCL program was working normally until a software update.

  The program prints out:

  ac_rtld error: !s->is_rx
  LLVM failed to upload shader

  when clEnqueueNDRangeKernel is called.

  I've downloaded the source for mesa and traced the problem to the
  gallium radeon driver. The first error message is from

  mesa-19.2.1/src/amd/common/ac_rtld.c

  and the second error message is from

  mesa-19.2.1/src/gallium/drivers/radeonsi/si_compute.c

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libllvm9 1:9-2~ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-lowlatency 4.15.18
  Uname: Linux 4.15.0-74-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 14:35:15 2020
  InstallationDate: Installed on 2018-04-28 (628 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: mesa-opencl-icd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860042/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

[Łukasz Zemczak]

Is the same change still present in the current focal-proposed alsa-lib
1.2.1.2-2 ?

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in alsa-lib package in Ubuntu:
  Fix Committed

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs

[Joseph Yasi]

I'm marking this as also affects alsa-plugins since that is shipping a
jack plugin by default, and this bug is triggered when jack isn't even
running. Programs that scan for ALSA devices pick up that jack plugin
and trigger the double close.

** Also affects: alsa-plugins (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  libjack-jackd2-0 double close on a failure to connect to jackd which
  causes crashes in multithreaded programs

Status in alsa-plugins package in Ubuntu:
  New
Status in jackd2 package in Ubuntu:
  Confirmed
Status in jackd2 package in Debian:
  Confirmed

Bug description:
  After upgrading to Ubuntu 19.04, I started experiencing sporadic
  crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded
  alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin
  is enabled by default in /etc/alsa/conf.d/50-jack.conf.

  The crashes are caused by a race condition when kodi's audio engine
  thread is enumerating the ALSA sound devices, and the udev thread is
  enumerating the udev devices triggered by the sound device add from
  turning the AVR on.

  When enumerating the ALSA jack plugin device, it tries to connect to
  connect to jackd. Since I don't have jackd installed, it fails to
  connect. libjack closes the socket on error, and then closes it again
  in it's cleanup code. Since it's closing the same file descriptor
  twice, it interacts with other threads that have potentially opened
  file descriptors, and causes the crash.

  This same bug could potentially affect other multi-threaded programs
  that enumerate ALSA devices.

  Fix committed upstream:
  
https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1833479/+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 1860985] Re: packagekitd using 100% CPU

[Julian Andres Klode]

Bugs happen, but w/o being able to reproduce them, there's not much we
can do here. What was the PPA that caused this? It does sound like I
fixed this upstream:
https://github.com/hughsie/PackageKit/pull/321/commits/9a2eab81a792b6ff55950fd53ee76a481f331d9f

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

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

Title:
  packagekitd using 100% CPU

Status in packagekit package in Ubuntu:
  Incomplete

Bug description:
  That's all I can report at this stage. Any attempt to kill it or
  disable the service fails and up goes its CPU usage, fans blowing the
  works!

  packagekit status give 
  Jan 27 13:59:02 owen-Precision-M4600 https[820460]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 http[820454]: Libgcrypt warning: missing 
initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 store[820894]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 https[820443]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 https[820455]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying 
to obtain org.freedesktop.packagekit.system-sources-refresh auth 
(only_trusted:0)
  Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained 
auth for org.freedesktop.packagekit.system-sources-refresh
  Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: refresh-cache 
transaction /29159_bdcaeddd from uid 1000 finished with cancelled-priority 
after 2137ms
  Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying 
to obtain org.freedesktop.packagekit.system-sources-refresh auth 
(only_trusted:0)
  Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained 
auth for org.freedesktop.packagekit.system-sources-refresh

  I am uid: 1000. It would be helpful if it gave some indication as to
  "the application". I can't find anywhere to admin this. It looks like
  my trust level is too low "only_trusted:0"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: packagekit 1.1.13-2
  Uname: Linux 5.5.0-050500rc7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Jan 27 13:54:13 2020
  InstallationDate: Installed on 2017-12-06 (782 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: packagekit
  UpgradeStatus: Upgraded to focal on 2019-11-13 (74 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1860985/+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 1860855] Re: packagekitd crashed with SIGSEGV

[Julian Andres Klode]

This is fixed in APT 1.9.8, which will be synced later today.

** Information type changed from Private to Public

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

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

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

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

Title:
  packagekitd crashed with SIGSEGV

Status in apt package in Ubuntu:
  Fix Committed
Status in packagekit package in Ubuntu:
  Invalid

Bug description:
  Message popped up about there being a system error.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: packagekit 1.1.13-2
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Sat Jan 25 13:28:12 2020
  ExecutablePath: /usr/lib/packagekit/packagekitd
  InstallationDate: Installed on 2020-01-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/sh
  SegvAnalysis:
   Segfault happened at: 0x7f8244d2f5e3:mov%eax,(%rdx)
   PC (0x7f8244d2f5e3) ok
   source "%eax" ok
   destination "(%rdx)" (0x7f8235e09040) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: packagekit
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libapt-pkg.so.5.90
   ?? () from /lib/x86_64-linux-gnu/libapt-pkg.so.5.90
   ?? () from /lib/x86_64-linux-gnu/libapt-pkg.so.5.90
   ?? () from /lib/x86_64-linux-gnu/libapt-pkg.so.5.90
   ?? () from /lib/x86_64-linux-gnu/libapt-pkg.so.5.90
  Title: packagekitd crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1860855/+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 1858802] Please test proposed package

[Łukasz Zemczak]

Hello Mauricio, or anyone else affected,

Accepted util-linux into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/util-
linux/2.27.1-6ubuntu3.10 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: util-linux (Ubuntu Disco)
   Status: In Progress => Won't Fix

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

Title:
  libblkid: no bcache UUID due to ambivalent detection of bcache and
  xfs_external_log for regular xfs in bcache backing device

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Bionic:
  Fix Committed
Status in util-linux source package in Disco:
  Won't Fix
Status in util-linux source package in Eoan:
  Fix Committed
Status in util-linux source package in Focal:
  Fix Released
Status in util-linux package in Debian:
  Unknown

Bug description:
  [Impact]

   * Users with an XFS filesystem on top of bcache
     (this is seen on some ceph, cloud deployments)
     might fail to reference the bcache device by
     UUID or other udev properties.

   * The journal of the regular XFS filesystem in
     the bcache device is incorrectly detected as
     an XFS external log; so two superblocks are
     detected (bcache and xfs_external_log).

   * Thus blkid fails with ambivalent superblocks
     detected then doesn't provide the usual udev
     properties (UUID, etc.)

   * The fix improves the probe function for XFS
     external log so it detects it's regular XFS
     and bails out.

  [Test Case]

   * See test steps detailed in comment #7 and later.
     - Create an XFS filesystem with the journal/log
   in the beginning of the bcache device (< 256K).
     - Stop the bcache device.
     - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'.

     $ sudo make-bcache -B $BACKING_DEV
     $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV
     $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop
     $ sudo blkid -o udev -p $BACKING_DEV

  [Regression Potential]

   * The patch only changes the detection function
     for XFS external log to be more general about
     the sector where the magic of regular XFS may
     be found (which is shifted inside the bcache.)

   * It still checks at sector zero (the only one
     checked previously), so this behavior didn't
     change.

   * Possible regressions are actual XFS external
     log devices that are not anymore detected as
     such. (Although that would probably indicate
     a different bug in libblkid.)

  [Other Info]
   * upstream commit:
     
https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device

[Łukasz Zemczak]

Hello Mauricio, or anyone else affected,

Accepted util-linux into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/util-
linux/2.31.1-0.4ubuntu3.5 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: util-linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Changed in: util-linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  libblkid: no bcache UUID due to ambivalent detection of bcache and
  xfs_external_log for regular xfs in bcache backing device

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Bionic:
  Fix Committed
Status in util-linux source package in Disco:
  Won't Fix
Status in util-linux source package in Eoan:
  Fix Committed
Status in util-linux source package in Focal:
  Fix Released
Status in util-linux package in Debian:
  Unknown

Bug description:
  [Impact]

   * Users with an XFS filesystem on top of bcache
     (this is seen on some ceph, cloud deployments)
     might fail to reference the bcache device by
     UUID or other udev properties.

   * The journal of the regular XFS filesystem in
     the bcache device is incorrectly detected as
     an XFS external log; so two superblocks are
     detected (bcache and xfs_external_log).

   * Thus blkid fails with ambivalent superblocks
     detected then doesn't provide the usual udev
     properties (UUID, etc.)

   * The fix improves the probe function for XFS
     external log so it detects it's regular XFS
     and bails out.

  [Test Case]

   * See test steps detailed in comment #7 and later.
     - Create an XFS filesystem with the journal/log
   in the beginning of the bcache device (< 256K).
     - Stop the bcache device.
     - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'.

     $ sudo make-bcache -B $BACKING_DEV
     $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV
     $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop
     $ sudo blkid -o udev -p $BACKING_DEV

  [Regression Potential]

   * The patch only changes the detection function
     for XFS external log to be more general about
     the sector where the magic of regular XFS may
     be found (which is shifted inside the bcache.)

   * It still checks at sector zero (the only one
     checked previously), so this behavior didn't
     change.

   * Possible regressions are actual XFS external
     log devices that are not anymore detected as
     such. (Although that would probably indicate
     a different bug in libblkid.)

  [Other Info]
   * upstream commit:
     
https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1860985] Re: packagekitd using 100% CPU

[Owen Savill]

So now running at about 33% CPU. It was a broken update PPA. Really!
Exactly how many times a second are the PPAs being checked for updates?!
It's a broken PPA, surely the package manager can handle a broken PPA
better than 100% CPU usage. And exactly what is it doing that requires
20% CPU usage when it's idle?!

Is there an admin program for this? I think it only needs to update a
couple of times a day. The only admin I've found offers very few options
as to the frequency of update checking and none of them seem to work. It
slows down boot, even though this should be disabled and it's consuming
far too much CPU given that it's showing as auto checks disabled.

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

Title:
  packagekitd using 100% CPU

Status in packagekit package in Ubuntu:
  New

Bug description:
  That's all I can report at this stage. Any attempt to kill it or
  disable the service fails and up goes its CPU usage, fans blowing the
  works!

  packagekit status give 
  Jan 27 13:59:02 owen-Precision-M4600 https[820460]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 http[820454]: Libgcrypt warning: missing 
initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 store[820894]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 https[820443]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 https[820455]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying 
to obtain org.freedesktop.packagekit.system-sources-refresh auth 
(only_trusted:0)
  Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained 
auth for org.freedesktop.packagekit.system-sources-refresh
  Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: refresh-cache 
transaction /29159_bdcaeddd from uid 1000 finished with cancelled-priority 
after 2137ms
  Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying 
to obtain org.freedesktop.packagekit.system-sources-refresh auth 
(only_trusted:0)
  Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained 
auth for org.freedesktop.packagekit.system-sources-refresh

  I am uid: 1000. It would be helpful if it gave some indication as to
  "the application". I can't find anywhere to admin this. It looks like
  my trust level is too low "only_trusted:0"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: packagekit 1.1.13-2
  Uname: Linux 5.5.0-050500rc7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Jan 27 13:54:13 2020
  InstallationDate: Installed on 2017-12-06 (782 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: packagekit
  UpgradeStatus: Upgraded to focal on 2019-11-13 (74 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1860985/+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 1860985] [NEW] packagekitd using 100% CPU

[Owen Savill]

Public bug reported:

That's all I can report at this stage. Any attempt to kill it or disable
the service fails and up goes its CPU usage, fans blowing the works!

packagekit status give 
Jan 27 13:59:02 owen-Precision-M4600 https[820460]: Libgcrypt warning: missing 
initialization - please fix the application
Jan 27 13:59:02 owen-Precision-M4600 http[820454]: Libgcrypt warning: missing 
initialization - please fix the application
Jan 27 13:59:02 owen-Precision-M4600 store[820894]: Libgcrypt warning: missing 
initialization - please fix the application
Jan 27 13:59:02 owen-Precision-M4600 https[820443]: Libgcrypt warning: missing 
initialization - please fix the application
Jan 27 13:59:02 owen-Precision-M4600 https[820455]: Libgcrypt warning: missing 
initialization - please fix the application
Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying to 
obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained auth 
for org.freedesktop.packagekit.system-sources-refresh
Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: refresh-cache 
transaction /29159_bdcaeddd from uid 1000 finished with cancelled-priority 
after 2137ms
Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying to 
obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained auth 
for org.freedesktop.packagekit.system-sources-refresh

I am uid: 1000. It would be helpful if it gave some indication as to
"the application". I can't find anywhere to admin this. It looks like my
trust level is too low "only_trusted:0"

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: packagekit 1.1.13-2
Uname: Linux 5.5.0-050500rc7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Jan 27 13:54:13 2020
InstallationDate: Installed on 2017-12-06 (782 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: packagekit
UpgradeStatus: Upgraded to focal on 2019-11-13 (74 days ago)

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


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

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

Title:
  packagekitd using 100% CPU

Status in packagekit package in Ubuntu:
  New

Bug description:
  That's all I can report at this stage. Any attempt to kill it or
  disable the service fails and up goes its CPU usage, fans blowing the
  works!

  packagekit status give 
  Jan 27 13:59:02 owen-Precision-M4600 https[820460]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 http[820454]: Libgcrypt warning: missing 
initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 store[820894]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 https[820443]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 https[820455]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying 
to obtain org.freedesktop.packagekit.system-sources-refresh auth 
(only_trusted:0)
  Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained 
auth for org.freedesktop.packagekit.system-sources-refresh
  Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: refresh-cache 
transaction /29159_bdcaeddd from uid 1000 finished with cancelled-priority 
after 2137ms
  Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying 
to obtain org.freedesktop.packagekit.system-sources-refresh auth 
(only_trusted:0)
  Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained 
auth for org.freedesktop.packagekit.system-sources-refresh

  I am uid: 1000. It would be helpful if it gave some indication as to
  "the application". I can't find anywhere to admin this. It looks like
  my trust level is too low "only_trusted:0"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: packagekit 1.1.13-2
  Uname: Linux 5.5.0-050500rc7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Jan 27 13:54:13 2020
  InstallationDate: Installed on 2017-12-06 (782 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: packagekit
  UpgradeStatus: Upgraded to focal on 2019-11-13 (74 days ago)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device

[Łukasz Zemczak]

Hello Mauricio, or anyone else affected,

Accepted util-linux into eoan-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/util-
linux/2.34-0.1ubuntu2.2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: util-linux (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

Title:
  libblkid: no bcache UUID due to ambivalent detection of bcache and
  xfs_external_log for regular xfs in bcache backing device

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  In Progress
Status in util-linux source package in Bionic:
  In Progress
Status in util-linux source package in Disco:
  In Progress
Status in util-linux source package in Eoan:
  Fix Committed
Status in util-linux source package in Focal:
  Fix Released
Status in util-linux package in Debian:
  Unknown

Bug description:
  [Impact]

   * Users with an XFS filesystem on top of bcache
     (this is seen on some ceph, cloud deployments)
     might fail to reference the bcache device by
     UUID or other udev properties.

   * The journal of the regular XFS filesystem in
     the bcache device is incorrectly detected as
     an XFS external log; so two superblocks are
     detected (bcache and xfs_external_log).

   * Thus blkid fails with ambivalent superblocks
     detected then doesn't provide the usual udev
     properties (UUID, etc.)

   * The fix improves the probe function for XFS
     external log so it detects it's regular XFS
     and bails out.

  [Test Case]

   * See test steps detailed in comment #7 and later.
     - Create an XFS filesystem with the journal/log
   in the beginning of the bcache device (< 256K).
     - Stop the bcache device.
     - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'.

     $ sudo make-bcache -B $BACKING_DEV
     $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV
     $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop
     $ sudo blkid -o udev -p $BACKING_DEV

  [Regression Potential]

   * The patch only changes the detection function
     for XFS external log to be more general about
     the sector where the magic of regular XFS may
     be found (which is shifted inside the bcache.)

   * It still checks at sector zero (the only one
     checked previously), so this behavior didn't
     change.

   * Possible regressions are actual XFS external
     log devices that are not anymore detected as
     such. (Although that would probably indicate
     a different bug in libblkid.)

  [Other Info]
   * upstream commit:
     
https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

[Igor Maric]

This is a huge issue in business environment. I can't understand that we
don't have this in 2020 when all other platform has it and even now its
importance is a wishlist? Come on! It's impossible to have a
conversation using Bluetooth, audio is unusable.

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+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 1857051] Re: Please add ${distro_id}ESM:${distro_codename}-infra-security and ${distro_id}ESMApps:${distro_codename}-apps-security to allowed origins (on Ubuntu)

[Francis Ginther]

** Tags added: id-5e2af6c2292b6f85495764a9

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

Title:
  Please add ${distro_id}ESM:${distro_codename}-infra-security  and
  ${distro_id}ESMApps:${distro_codename}-apps-security to allowed
  origins (on Ubuntu)

Status in unattended-upgrades package in Ubuntu:
  New
Status in unattended-upgrades source package in Trusty:
  New
Status in unattended-upgrades source package in Xenial:
  New
Status in unattended-upgrades source package in Bionic:
  New

Bug description:
  [Impact]

   * Changes to the ESM repo naming and the introduction of the new esm-infra 
and esm-apps suites require an update to unattended-upgrades to ensure the 
security pockets are used.
   * This change will ensure users are actually receiving updates, where as 
today they will not without making manual changes.

  [Test Case]

   * 1) Bionic and Xenial ESM-Apps/ESM-infra with Ubuntu Pro
   * 2) Trusty ESM

  [Regression Potential]

   * This change is ensuring users actually receive security updates when using 
ESM. Therefore, 1) users of ESM-apps on Ubuntu Pro and 2) ESM-infra on Trusty 
will be the only users affected.
   * The possible issue would be if/when users receive actual security updates 
that then regress or cause issues to the system.

  [Other Info]
   
  Previous description:

  ESM -infra-security and -apps-security will need to
  participate in unattended upgrades.

  Currently /etc/apt/apt.conf.d/50unattended-upgrades provides:
  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}ESM:${distro_codename}";
  }

  Given that there have been ESM apt pocket renames over the last few
  months, the above ESM allowed-origin should not apply anymore and can
  be dropped or replaced.

  See RT #C122697 and #C121067 for the pocket/suite renames related to
  ESM

  What is needed after the ESM apt pocket/suite renames:

  Support for unattended upgrades for ESM for Infrastructure customers:

  Unattended-Upgrade::Allowed-Origins {
    // Extended Security Maintenance; doesn't necessarily exist for
    // every release and this system may not have it installed, but if
    // available, the policy for updates is such that unattended-upgrades
    // should also install from here by default.
    "${distro_id}ESM:${distro_codename}-infra-security";
    "${distro_id}ESMApps:${distro_codename}-apps-security";
  };

  === Confirmed proper origin on an attached Trusty instance with ESM-
  infra enabled:

   500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main amd64 Packages
   release 
v=14.04,o=UbuntuESM,a=trusty-infra-security,n=trusty,l=UbuntuESM,c=main

  === Confirmed proper origins on Bionic for enabled ESM-infra and ESM-apps on 
an AWS Ubuntu PRO instance:
   500 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security/main amd64 
Packages
   release 
v=18.04,o=UbuntuESM,a=bionic-infra-security,n=bionic,l=UbuntuESM,c=main,b=amd64

   500 https://esm.ubuntu.com/apps/ubuntu bionic-apps-security/main amd64 
Packages
   release 
v=18.04,o=UbuntuESMApps,a=bionic-apps-security,n=bionic,l=UbuntuESMApps,c=main,b=amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1857051/+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 1860903] Re: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.5 failed to install/upgrade: 该软件包正处于非常不稳定的状态； 您最好在配置它之前，先重新安装它

[Balint Reczey]

>From DpkgTerminalLog.txt :

(Reading database ... The system currently has 215127 files and directories 
installed.)
Preparing to unpack ... / xserver-xorg-lts-utopic_3% 3a13_amd64.deb ...
Unpacking xserver-xorg-lts-utopic (3:13) ...
dpkg: Error processing package unattended-upgrades (--configure):
 The software package is in a very unstable state;
You'd better reinstall it before configuring it


Please try running:

apt-get -f install

This should fix the issue or reveal more details.

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Incomplete

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

Title:
  package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.5 failed to
  install/upgrade: 该软件包正处于非常不稳定的状态； 您最好在配置它之前，先重新安装它

Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  could you help me

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.7~16.04.5
  ProcVersionSignature: Ubuntu 4.15.0-74.83~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.21
  AptOrdering:
   xserver-xorg-lts-utopic: Install
   unattended-upgrades: Configure
   xserver-xorg-lts-utopic: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Jan 26 14:44:29 2020
  ErrorMessage: 该软件包正处于非常不稳定的状态； 您最好在配置它之前，先重新安装它
  InstallationDate: Installed on 2020-01-26 (0 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.5 failed to 
install/upgrade: 该软件包正处于非常不稳定的状态； 您最好在配置它之前，先重新安装它
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic: [modified]
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2020-01-26T11:34:12.040926

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1860903/+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 1848522] Re: Backport packages for 18.04.4 HWE stack

[Launchpad Bug Tracker]

This bug was fixed in the package xserver-xorg-video-ati-hwe-18.04 -
1:19.0.1-1ubuntu1~18.04.1

---
xserver-xorg-video-ati-hwe-18.04 (1:19.0.1-1ubuntu1~18.04.1) bionic; 
urgency=medium

  * Backport for 18.04.3 HWE stack update. (LP: #1848522)

xserver-xorg-video-ati (1:19.0.1-1ubuntu1) eoan; urgency=medium

  * dri3-always-flush-glamor.diff: Fix broken tooltips. (LP: #1841718)

 -- Timo Aaltonen   Thu, 17 Oct 2019 16:13:15 +0300

** Changed in: xserver-xorg-video-ati-hwe-18.04 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 18.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-9 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-9 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.4 images.

  [Test case]

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

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

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

  libclc: more or less just adds support for new llvm

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

  xserver: a new git snapshot (or maybe a point-release)

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

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

[Launchpad Bug Tracker]

This bug was fixed in the package xserver-xorg-video-amdgpu-hwe-18.04 -
19.0.1-1ubuntu1~18.04.1

---
xserver-xorg-video-amdgpu-hwe-18.04 (19.0.1-1ubuntu1~18.04.1) bionic; 
urgency=medium

  * Backport for 18.04.3 HWE stack update. (LP: #1848522)

xserver-xorg-video-amdgpu (19.0.1-1ubuntu1) eoan; urgency=medium

  * dri3-always-flush-glamor.diff: Fix broken tooltips. (LP: #1841718)

 -- Timo Aaltonen   Thu, 17 Oct 2019 16:13:12 +0300

** Changed in: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 18.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-9 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in llvm-toolchain-9 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Released
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  These are needed for 18.04.4 images.

  [Test case]

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

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

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

  libclc: more or less just adds support for new llvm

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

  xserver: a new git snapshot (or maybe a point-release)

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1848522/+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 1860504] Re: software-properties-gtk fails to launch via "Additional Drivers" or via terminal

[Sebastian Straszak]

dpkg -l | grep software-properties
ii  python3-software-properties0.98.5   
  all  manage the repositories that you install software from
ii  software-properties-common 0.98.5   
  all  manage the repositories that you install software from 
(common)
ii  software-properties-gtk0.98.5   
  all  manage the repositories that you install software from (gtk)

debsums software-properties-common
/usr/bin/add-apt-repository   OK
/usr/lib/python3/dist-packages/softwareproperties/dbus/SoftwarePropertiesDBus.py
 OK
/usr/lib/python3/dist-packages/softwareproperties/dbus/__init__.pyOK
/usr/lib/software-properties/software-properties-dbus OK
/usr/share/dbus-1/system-services/com.ubuntu.SoftwareProperties.service   OK
/usr/share/doc/software-properties-common/copyright   OK
/usr/share/man/man1/add-apt-repository.1.gz   OK
/usr/share/polkit-1/actions/com.ubuntu.softwareproperties.policy  OK

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

Title:
  software-properties-gtk fails to launch via "Additional Drivers" or
  via terminal

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Issue present since reinstall of Ubuntu. Originally thought similar to
  (https://askubuntu.com/questions/789966/software-updates-crashes-and-
  will-not-open) but solutions did not work, even though terminal output
  (https://pastebin.com/FpD1MFC3) is highly similar.

  I have tested using a new user and the issue remains.

  1)
  Description:  Ubuntu 19.10
  Release:  19.10
  Linux version 5.3.0-26-generic (buildd@lgw01-amd64-013) (gcc version 9.2.1 
20191008 (Ubuntu 9.2.1-9ubuntu2))
  2)
  software-properties-gtk:
    Installed: 0.98.5
    Candidate: 0.98.5
    Version table:
   *** 0.98.5 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/main i386 Packages
  100 /var/lib/dpkg/status
  3)
  Additional Drivers utility should launch when executing command 
"software-properties-gtk" with or without root.
  4)
  Long error fight between dbus and python3.

  A note on attempted solutions. Reinstalling dbus/dbus-x11 and
  following the noted askubuntu thread did not help.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.98.5
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 22 03:48:12 2020
  InstallationDate: Installed on 2020-01-14 (8 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1860504/+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 1854588] Re: Clicking 'Install' on gdebi-gtk makes it vanish ONLY when .deb opened from Chrome/Firefox

[Nicholas Harvey]

Still seeing this issue on 19.10 with Firefox and 20.04 also.

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

Title:
  Clicking 'Install' on gdebi-gtk makes it vanish ONLY when .deb opened
  from Chrome/Firefox

Status in Ubuntu MATE:
  New
Status in gdebi package in Ubuntu:
  New

Bug description:
  Before anyone says this bug already exists... it doesn't (at least as
  far as I can see).  It's just that a lot of similar bugs do/did exist
  where people have also experienced the same symptoms (of gdebi-gtk
  vanishing upon clicking 'Install').

  So yes this is the same symptoms, but it must be a different cause as
  the circumstances are different and doesn't have the same resolution.

  The meat of it...

  Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or 
with Chrome if you installed that) go to any site that offers a .deb package 
and either...
  a) choose to open it directly from the browser (rather than saving it to 
'Downloads' folder)
  b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that 
file from within the browser itself.

  You should find that gdebi-gtk appears but vanishes the moment you
  click 'Install' without a prompt for a password, an explanation or the
  package actually getting installed.

  This bug has existed since the beginning of Ubuntu 18.04 however it's
  been largely confused with other similar bugs.  I've had it on half a
  dozen machines and confirmed it exists with IRC users on #ubuntu-mate
  of freenode.

  However with *this* bug (compared to others) gdebi-gtk works perfectly
  fine if you run it from the terminal or just double click the .deb
  package from your file manager.

  It's the kind of bug which if you're a hardened desktop Linux user,
  you'd just work around it...

  But if you're a novice and you can't get a simple thing like
  Teamviewer installed (which is a .deb, and a thing I might ask someone
  to do over the phone to try to help them) you likely get fed up and
  re-install Windows :S

  Any input on this would be brilliant as I can't seem to get any
  logs/output.

  ~lantizia

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

Re: [Touch-packages] [Bug 1859963] Re: Info package on Ubuntu Focal comes preinstalled with desktop file

[Norbert Preining]

Hi Sebastian,

> @Norbert, it's not the ideal solution no, those .desktop are not really
> good desktop applications and ideally they would be dropped in

What do you do on the Ubuntu side with say
julia.desktop
which starts a julia shell?
Similarly: ocaml, R, SageMath, ... there are quite a lot of applications
with Terminal=true?

Hide all of them in Gnome?

Best

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

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

Title:
  Info package on Ubuntu Focal comes preinstalled with desktop file

Status in One Hundred Papercuts:
  New
Status in texinfo package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  The "info" package that is preinstalled on Ubuntu Focal ships with a
  "info.desktop" file that adds a "TeXInfo" desktop launcher displayed
  among other apps. The launcher opens a terminal application that is
  confusing and user unfriendly for many users. Users that actually want
  to use info can do it using a terminal. Please, consider removing the
  desktop file or at least set it to not show among other apps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1859963/+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 1860504] Re: software-properties-gtk fails to launch via "Additional Drivers" or via terminal

[Sebastien Bacher]

What's the output of those commands?
$ dpkg -l | grep software-propoerties
$ debsums software-properties-common
(you might need to install debsums if the command is not available)

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Low

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

Title:
  software-properties-gtk fails to launch via "Additional Drivers" or
  via terminal

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Issue present since reinstall of Ubuntu. Originally thought similar to
  (https://askubuntu.com/questions/789966/software-updates-crashes-and-
  will-not-open) but solutions did not work, even though terminal output
  (https://pastebin.com/FpD1MFC3) is highly similar.

  I have tested using a new user and the issue remains.

  1)
  Description:  Ubuntu 19.10
  Release:  19.10
  Linux version 5.3.0-26-generic (buildd@lgw01-amd64-013) (gcc version 9.2.1 
20191008 (Ubuntu 9.2.1-9ubuntu2))
  2)
  software-properties-gtk:
    Installed: 0.98.5
    Candidate: 0.98.5
    Version table:
   *** 0.98.5 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/main i386 Packages
  100 /var/lib/dpkg/status
  3)
  Additional Drivers utility should launch when executing command 
"software-properties-gtk" with or without root.
  4)
  Long error fight between dbus and python3.

  A note on attempted solutions. Reinstalling dbus/dbus-x11 and
  following the noted askubuntu thread did not help.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.98.5
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 22 03:48:12 2020
  InstallationDate: Installed on 2020-01-14 (8 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1860504/+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 1860877] Re: No way to edit online account settings after creation

[Sebastien Bacher]

Thank you for your bug report. That looks like an upstream issue, could
you report it on https://gitlab.gnome.org/GNOME/gnome-online-
accounts/issues ?

** Package changed: gnome-control-center (Ubuntu) => gnome-online-
accounts (Ubuntu)

** Changed in: gnome-online-accounts (Ubuntu)
   Importance: Undecided => Low

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

Title:
  No way to edit online account settings after creation

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  I set up a nextcloud account in the "online accounts" section of the ubuntu 
settings.
  https://help.ubuntu.com/stable/ubuntu-help/accounts.html.en

  However, there appears to be no way to edit the settings afterwards,
  for instance to change the password.

  Both in the settings and the documentation this option is completely
  missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1860877/+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 1859963] Re: Info package on Ubuntu Focal comes preinstalled with desktop file

[Sebastien Bacher]

@Norbert, it's not the ideal solution no, those .desktop are not really
good desktop applications and ideally they would be dropped in
Debian, meanwhile I don't want to add a delta to texinfo in
Ubuntu so that will do the trick

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

Title:
  Info package on Ubuntu Focal comes preinstalled with desktop file

Status in One Hundred Papercuts:
  New
Status in texinfo package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  The "info" package that is preinstalled on Ubuntu Focal ships with a
  "info.desktop" file that adds a "TeXInfo" desktop launcher displayed
  among other apps. The launcher opens a terminal application that is
  confusing and user unfriendly for many users. Users that actually want
  to use info can do it using a terminal. Please, consider removing the
  desktop file or at least set it to not show among other apps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1859963/+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 1860877] [NEW] No way to edit online account settings after creation

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I set up a nextcloud account in the "online accounts" section of the ubuntu 
settings.
https://help.ubuntu.com/stable/ubuntu-help/accounts.html.en

However, there appears to be no way to edit the settings afterwards, for
instance to change the password.

Both in the settings and the documentation this option is completely
missing.

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Low
 Status: New

-- 
No way to edit online account settings after creation
https://bugs.launchpad.net/bugs/1860877
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gnome-online-accounts 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 1860946] Re: Error or every boot

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to 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: xorg (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Error or every boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Delay in response infrequent interrution

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Jan 27 07:28:37 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   anbox, 1, 4.15.0-72-generic, x86_64: installed
   anbox, 1, 4.15.0-74-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics 
Controller [1179:fa31]
  InstallationDate: Installed on 2018-08-27 (517 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: TOSHIBA Satellite C50-A
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=02250975-d476-48ef-9a7d-22dbbe5e4c15 ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.30
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PT10F
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.30:bd11/08/2013:svnTOSHIBA:pnSatelliteC50-A:pvrPSCG8G-05500G:rvnIntel:rnPT10F:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: Satellite C50-A
  dmi.product.version: PSCG8G-05500G
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Aug 28 09:45:06 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1860946/+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 1860956] Re: network-manager 1.16.0-0ubuntu2 ADT test failure with linux 5.0.0-40.44

[Sebastien Bacher]

Thank you for your bug report. The log is from disco, is that an issue in 19.10 
or focal?
We are not likely to fix disco test issues at this point...

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  network-manager 1.16.0-0ubuntu2 ADT test failure with linux
  5.0.0-40.44

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Testing failed on:
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/ppc64el/n/network-manager/20200124_174131_d1990@/log.gz

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