[Touch-packages] [Bug 1908064] Re: [Multiple bluetooth speakers, playback] Stuttering sound

[Daniel van Vugt]

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

Bug 1797002 is still open. We don't consider it resolved so this is now
a duplicate of that.

Yes you are free to delete any attachments from this bug that you wish.
In future if you are concerned about the privacy of attachments you can
mark your bugs as Private at the top-right of the page. Then only a very
small team of bug reviewers will be able to see them.

** This bug has been marked a duplicate of bug 1797002
   Bluetooth audio skips while the settings dialog is open

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

Title:
  [Multiple bluetooth speakers, playback] Stuttering sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Constant stuttering sound, stuttering at maybe 10 times/second. More
  than one speaker with the same symptoms.

  Speakers work in Windows 10 / macOS 10.14+ running on same hardware.

  Same speakers work on Ubuntu Mate 18.04 32 bit running on different
  hardware.

  Remote control commands work (play/pause button on speakers).

  Initial pairing and connection requires from 2 to about 10 retries.
  All tested within 1 m distance.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  username3486 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 14 13:49:26 2020
  InstallationDate: Installed on 2020-10-30 (45 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: Crossbeat
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Crossbeat, playback] Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 264.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2E6FAB96566FE58C
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2E6FAB96566FE58C
  dmi.modalias: 
dmi:bvnAppleInc.:bvr264.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C:
  dmi.product.family: MacBook Air
  dmi.product.name: MacBookAir5,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1908064] Re: [Multiple bluetooth speakers, playback] Stuttering sound

[abcdef]

I will be deleting all attachments, unless you think any of them are
strictly necessary?

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

Title:
  [Multiple bluetooth speakers, playback] Stuttering sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Constant stuttering sound, stuttering at maybe 10 times/second. More
  than one speaker with the same symptoms.

  Speakers work in Windows 10 / macOS 10.14+ running on same hardware.

  Same speakers work on Ubuntu Mate 18.04 32 bit running on different
  hardware.

  Remote control commands work (play/pause button on speakers).

  Initial pairing and connection requires from 2 to about 10 retries.
  All tested within 1 m distance.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  username3486 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 14 13:49:26 2020
  InstallationDate: Installed on 2020-10-30 (45 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: Crossbeat
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Crossbeat, playback] Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 264.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2E6FAB96566FE58C
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2E6FAB96566FE58C
  dmi.modalias: 
dmi:bvnAppleInc.:bvr264.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C:
  dmi.product.family: MacBook Air
  dmi.product.name: MacBookAir5,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1908064] Re: [Multiple bluetooth speakers, playback] Stuttering sound

[abcdef]

Thanks for the suggestions. Closing the settings window makes the
problem disappear. Good call.

Unlike the reporter in the linked bug I wouldn't exactly call that a
"solution" (and certainly not "simple") since there is very little
chance I would consider closing the settings window before confirming
that the speaker works properly.

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

Title:
  [Multiple bluetooth speakers, playback] Stuttering sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Constant stuttering sound, stuttering at maybe 10 times/second. More
  than one speaker with the same symptoms.

  Speakers work in Windows 10 / macOS 10.14+ running on same hardware.

  Same speakers work on Ubuntu Mate 18.04 32 bit running on different
  hardware.

  Remote control commands work (play/pause button on speakers).

  Initial pairing and connection requires from 2 to about 10 retries.
  All tested within 1 m distance.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  username3486 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 14 13:49:26 2020
  InstallationDate: Installed on 2020-10-30 (45 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: Crossbeat
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Crossbeat, playback] Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 264.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2E6FAB96566FE58C
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2E6FAB96566FE58C
  dmi.modalias: 
dmi:bvnAppleInc.:bvr264.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C:
  dmi.product.family: MacBook Air
  dmi.product.name: MacBookAir5,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1898603] Re: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers

[Launchpad Bug Tracker]

[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected
  as output, not speakers

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  Starting in Kernel 5.4.0-48-generic on Mint Linux 20 Cinnamon my sound
  output is detected as "headphones" instead of Speakers when this
  laptop doesn't even have any headphones connected at all... reverting
  to a prior kernel fixes the problem and then the output is correctly
  Speakers... I cannot possibly use sound on Kernel 5.4.0-48-generic and
  the Mint Linux support chat said I should file a bug for this because
  this kernel broke something.

  See attached detailed log reports for more info...

  Thanks team!!!

  Best Regards,

  -Avery Tarasov
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chr0meice2   2656 F pulseaudio
   /dev/snd/controlC0:  chr0meice2   2656 F pulseaudio
   /dev/snd/pcmC0D0c:   chr0meice2   2656 F...m pulseaudio
   /dev/snd/pcmC0D0p:   chr0meice2   2656 F...m pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-10-05 (0 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  ulyana
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/01/2019
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P95_96_97Ex,Rx
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.13:bd10/01/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P95_96_97Ex,Rx
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Touch-packages] [Bug 1899797] Re: dns does not resolve some names after updating kernel from 4.15.0-117 to a newer sub_version like -118 or -121

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  dns does not resolve some names after updating kernel from 4.15.0-117
  to a newer sub_version like -118 or -121

Status in linux package in Ubuntu:
  Expired
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  This morning i've got a kernel update. After that I could not send
  mails using thunderbird contacting my mail provider kontent.com.

  The last working system was: Linux server 4.15.0-117-generic
  #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64
  GNU/Linux

  I tried 4.15.0-118 and 4.15.0-121 but using these I could not resolve:
  smtp.kontent.com - but I could resolve www.google.de.

  So it seems that using the newer kernels 118 and 121 I can not resolve
  some but not all addresses.

  I returned to kernel 4.15.0-117 and everything works fine again.

  systemd-resolve --status
  Global
   DNS Servers: 172.30.30.1<--- this is an local router next to my 
"server"
DNS Domain: ami.intranet
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

  Link 2 (enp0s25)
Current Scopes: DNS
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 172.30.30.1
DNS Domain: ~.
ami.intranet
  andreas@server:~$ host smtp.kontent.com
  smtp.kontent.com has address 81.88.40.61

  doning the same with a newer kernel results in a "SERVERFAIL 2 error"

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

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

[Touch-packages] [Bug 1906101] Re: no sound via speakers or headphone port on Carbon X1 6th

[Kai-Heng Feng]

Can you please attach dmesg without any parameter/workaround?

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

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

Title:
  no sound via speakers or headphone port on Carbon X1 6th

Status in alsa-lib package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I recently upgraded from 18.04 to 20.04. The sound worked without
  problems before upgrade, but now I don'get any sound at all from the
  speakers or the headphone jack.

  This seems similar to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697 (although
  that bug is reported as resolved). I tried adding model=generic
  dmic_detect=0 to my alsa-base.conf, as reported in that ticket, but it
  did not help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.8
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Nov 28 18:36:36 2020
  InstallationDate: Installed on 2018-07-27 (855 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-11-24 (4 days ago)
  dmi.bios.date: 10/13/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET75W (1.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KGCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET75W(1.50):bd10/13/2020:svnLENOVO:pn20KGCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KGCTO1WW
  dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  misha  2223 F pulseaudio
   /dev/snd/pcmC0D0p:   misha  2223 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.04
  HibernationDevice: resume=UUID=85cedc6b-f3ef-4152-a471-35fa0ee621a1
  InstallationDate: Installed on 2018-07-27 (859 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KGCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=7d9c3e7d-d2d0-45a2-a598-2ee37d17a0fa ro 
resume=UUID=85cedc6b-f3ef-4152-a471-35fa0ee621a1 quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-54-generic N/A
   linux-backports-modules-5.4.0-54-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-11-24 (7 days ago)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET75W (1.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KGCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET75W(1.50):bd10/13/2020:svnLENOVO:pn20KGCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KGCTO1WW
  dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1907905] Re: buging

[Daniel van Vugt]

Please attach a photo or video of the problem so we can understand what
you are seeing.

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

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

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

Title:
  buging

Status in Ubuntu:
  Incomplete

Bug description:
  just have a lot of gren points and com`s and disapiering picture

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 12 15:32:53 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:5000]
  InstallationDate: Installed on 2020-11-14 (27 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 33663VG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-32-generic 
root=UUID=d4192c33-e4f0-4468-8ebe-426000ec3852 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2013
  dmi.bios.release: 2.54
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H0ET94WW (2.54 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 33663VG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 2.54
  dmi.modalias: 
dmi:bvnLENOVO:bvrH0ET94WW(2.54):bd08/02/2013:br2.54:efr2.54:svnLENOVO:pn33663VG:pvrThinkPadEdgeE530c:rvnLENOVO:rn33663VG:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Edge E530c
  dmi.product.name: 33663VG
  dmi.product.sku: LENOVO_MT_3366
  dmi.product.version: ThinkPad Edge E530c
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1~ubuntu0.20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1908071] Re: The video card driver is not working well

[Daniel van Vugt]

You appear to have the 'oibaf' PPA installed which is not supported and
is known to cause bugs.

Please use the 'ppa-purge' tool to remove that PPA from the system, then
reboot and if you experience any more problems then open a new bug.


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

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

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

Title:
  The video card driver is not working well

Status in Ubuntu:
  Invalid

Bug description:
  1)lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  2)apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu15
Candidate: 1:7.7+19ubuntu15
Version table:
   *** 1:7.7+19ubuntu15 500
  500 http://ua.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

  3)Normal work

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon Dec 14 15:49:46 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics [103c:86a0]
  InstallationDate: Installed on 2020-12-13 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 413c:8505 Dell Computer Corp. Dell Universal Receiver
   Bus 001 Device 002: ID 04ca:7095 Lite-On Technology Corp. HP HD Camera
   Bus 001 Device 004: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProBook 450 G7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic 
root=UUID=227ec1da-8070-4974-9577-9fe4a7428d90 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/19/2020
  dmi.bios.release: 6.1
  dmi.bios.vendor: HP
  dmi.bios.version: S71 Ver. 01.06.01
  dmi.board.name: 86A0
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 02.2D.00
  dmi.chassis.asset.tag: 5CD024GVZP
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 2.45
  dmi.modalias: 
dmi:bvnHP:bvrS71Ver.01.06.01:bd10/19/2020:br6.1:efr2.45:svnHP:pnHPProBook450G7:pvr:rvnHP:rn86A0:rvrKBCVersion02.2D.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 450 G7
  dmi.product.sku: 6YY26AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103+git2012121830.d034db~oibaf~g
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0~git2012130730.6a34a6~oibaf~g
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1908064] Re: [Multiple bluetooth speakers, playback] Stuttering sound

[Daniel van Vugt]

1. This is probably an issue with the Bluetooth kernel driver. Please
run:

   lspci -kv > lspci.txt
   lsusb > lsusb.txt

   and attach the resulting text files here.

2. Please ensure the latest driver is installed by running:

   sudo apt install bcmwl-kernel-source

   and then reboot.

3. Try closing Settings, in case you are experiencing bug 1797002.


** Tags added: a2dp

** Tags added: a2dp-skip

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

Title:
  [Multiple bluetooth speakers, playback] Stuttering sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Constant stuttering sound, stuttering at maybe 10 times/second. More
  than one speaker with the same symptoms.

  Speakers work in Windows 10 / macOS 10.14+ running on same hardware.

  Same speakers work on Ubuntu Mate 18.04 32 bit running on different
  hardware.

  Remote control commands work (play/pause button on speakers).

  Initial pairing and connection requires from 2 to about 10 retries.
  All tested within 1 m distance.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  username3486 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 14 13:49:26 2020
  InstallationDate: Installed on 2020-10-30 (45 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: Crossbeat
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Crossbeat, playback] Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 264.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2E6FAB96566FE58C
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2E6FAB96566FE58C
  dmi.modalias: 
dmi:bvnAppleInc.:bvr264.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C:
  dmi.product.family: MacBook Air
  dmi.product.name: MacBookAir5,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1907886] Re: avinfo is missing

[Daniel van Vugt]

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

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

** Tags added: focal groovy

** Tags removed: groovy
** Tags added: hirsute

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

Title:
  avinfo is missing

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  The "avinfo" command line tools available in bluez/tools
  (https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/tools) is not
  available in the package.

  The package bluez-tools (https://packages.ubuntu.com/groovy/bluez-
  tools) seems to map another project external to bluez
  (https://github.com/khvzak/bluez-tools) and not the "tools" folder of
  bluez.

  "avinfo" is used for example in order to check which codecs are
  supported by a headphone set (see https://github.com/EHfive
  /pulseaudio-modules-bt/issues/31#issuecomment-462717049).

  Maybe have "bluez-tools" map the "tools" folder of bluez, and move the
  other project to another package?

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

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

[Touch-packages] [Bug 1907906] Re: i want some support

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

Title:
  i want some support

Status in Ubuntu:
  Incomplete

Bug description:
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 12 15:39:57 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:5000]
  InstallationDate: Installed on 2020-11-14 (27 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 33663VG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-32-generic 
root=UUID=d4192c33-e4f0-4468-8ebe-426000ec3852 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2013
  dmi.bios.release: 2.54
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H0ET94WW (2.54 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 33663VG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 2.54
  dmi.modalias: 
dmi:bvnLENOVO:bvrH0ET94WW(2.54):bd08/02/2013:br2.54:efr2.54:svnLENOVO:pn33663VG:pvrThinkPadEdgeE530c:rvnLENOVO:rn33663VG:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Edge E530c
  dmi.product.name: 33663VG
  dmi.product.sku: LENOVO_MT_3366
  dmi.product.version: ThinkPad Edge E530c
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1~ubuntu0.20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1907882] Re: paprefs does not find modules

[Daniel van Vugt]

** Tags added: groovy

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

Title:
  paprefs does not find modules

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  on ubuntu 20.10 paprefs does not find modules, as it uses a hardcoded path.
  workaround:
  cd /usr/lib
  sudo ln -s pulse-13.99.2 pulse-13.99

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

  strace paprefs 2>&1 |grep /lib/pulse
  access("/usr/lib/pulse-13.99/modules/module-esound-protocol-tcp.so", F_OK) = 
-1 ENOENT (No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-native-protocol-tcp.so", F_OK) = 
-1 ENOENT (No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-zeroconf-publish.so", F_OK) = -1 
ENOENT (No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-zeroconf-discover.so", F_OK) = -1 
ENOENT (No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-raop-discover.so", F_OK) = -1 
ENOENT (No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-rtp-recv.so", F_OK) = -1 ENOENT 
(No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-rtp-send.so", F_OK) = -1 ENOENT 
(No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-rygel-media-server.so", F_OK) = 
-1 ENOENT (No such file or directory)

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

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

[Touch-packages] [Bug 1907865] Re: Xorg crash

[Daniel van Vugt]

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

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

** Summary changed:

- Xorg crash
+ Session crash

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

Title:
  Session crash

Status in Ubuntu:
  Incomplete

Bug description:
  I can't reliably reproduce this crash, and I don't know, even
  approximately, what's causing it, or what I might be doing to possibly
  cause it.  It just randomly crashes, and dumps me back to the login
  screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 11 15:35:06 2020
  DistUpgraded: 2020-10-07 09:25:09,468 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: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06de]
  InstallationDate: Installed on 2016-12-06 (1466 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5470
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to focal on 2020-10-07 (65 days ago)
  dmi.bios.date: 06/15/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.3
  dmi.board.name: 0VHKV0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn0VHKV0:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5470
  dmi.product.sku: 06DE
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2020-12-09T15:53:03.120486
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Fri Aug 17 21:02:51 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1523 
   vendor BOE
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Touch-packages] [Bug 1908167] Re: pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic

[Hui Wang]

** Tags added: oem-priority originate-from-1895332 somerville

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

Title:
  pulseaudio: the headset-mic or heapdhone-mic could not be selected
  automatically if there is no internal mic

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Groovy:
  In Progress
Status in pulseaudio source package in Hirsute:
  In Progress

Bug description:
  this bug is for tracking purpose.

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

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

[Touch-packages] [Bug 1908167] [NEW] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic

[Hui Wang]

Public bug reported:

this bug is for tracking purpose.

** Affects: pulseaudio (Ubuntu)
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: In Progress

** Affects: pulseaudio (Ubuntu Focal)
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: In Progress

** Affects: pulseaudio (Ubuntu Groovy)
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: In Progress

** Affects: pulseaudio (Ubuntu Hirsute)
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: In Progress

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

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

** Also affects: pulseaudio (Ubuntu Hirsute)
   Importance: High
 Assignee: Hui Wang (hui.wang)
   Status: In Progress

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

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

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

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

** Changed in: pulseaudio (Ubuntu Focal)
   Status: New => In Progress

** Changed in: pulseaudio (Ubuntu Groovy)
   Status: New => In Progress

** Changed in: pulseaudio (Ubuntu Groovy)
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: pulseaudio (Ubuntu Focal)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

Title:
  pulseaudio: the headset-mic or heapdhone-mic could not be selected
  automatically if there is no internal mic

Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Groovy:
  In Progress
Status in pulseaudio source package in Hirsute:
  In Progress

Bug description:
  this bug is for tracking purpose.

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

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

[Touch-packages] [Bug 1903903] Re: [MSI MS-17C5] "Analog Stereo Duplex" profile keeps disappearing

[Daniel van Vugt]

If you're using KDE on 20.10 then you might want to look at bug 1897965.

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

Title:
  [MSI MS-17C5] "Analog Stereo Duplex" profile keeps disappearing

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After every reboot, the profile named "Analog Stereo Duplex" keeps
  disappearing on my laptop; only "Analog Stereo Input" and "Analog
  Stereo Output" are present. Without "duplex", I cannot use both the
  built-in microphone and the speakers/headphones at the same time.

  A workaround I found is to remove the user's configuration for
  pulseaudio and restart it:

  rm -rf .config/pulse
  pulseaudio -k

  This brings the "Analog Stereo Duplex" profile back until the next
  reboot.

  This problem started after an upgrade from Ubuntu 20.04 to 20.10.

  I made a screencast of this: https://youtu.be/Vlz5471EYVQ

  The laptop is MSI WE73-8SK.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-output-speaker.conf]
  ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14
  Uname: Linux 5.8.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Nov 11 10:50:54 2020
  InstallationDate: Installed on 2019-01-08 (673 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-29 (13 days ago)
  dmi.bios.date: 05/20/2019
  dmi.bios.release: 1.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C5IWS.10F
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17C5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C5IWS.10F:bd05/20/2019:br1.15:svnMicro-StarInternationalCo.,Ltd.:pnWE738SK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C5:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: WE
  dmi.product.name: WE73 8SK
  dmi.product.sku: 17C5.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Touch-packages] [Bug 1908073] Re: package python3 3.8.2-0ubuntu2 failed to install/upgrade: new python3 package pre-removal script subprocess returned error exit status 127

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package python3 3.8.2-0ubuntu2 failed to install/upgrade: new python3
  package pre-removal script subprocess returned error exit status 127

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  dont know

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  AptOrdering:
   python3:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Dec 14 18:15:13 2020
  ErrorMessage: new python3 package pre-removal script subprocess returned 
error exit status 127
  InstallationDate: Installed on 2020-12-03 (10 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, unpackaged
  PythonDetails: /usr/bin/python3.8, Python 3.8.5, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.2
  SourcePackage: python3-defaults
  Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: new python3 
package pre-removal script subprocess returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1908073/+subscriptions

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

[Touch-packages] [Bug 1908073] Re: package python3 3.8.2-0ubuntu2 failed to install/upgrade: new python3 package pre-removal script subprocess returned error exit status 127

[Seth Arnold]

** Information type changed from Private Security to Public

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

Title:
  package python3 3.8.2-0ubuntu2 failed to install/upgrade: new python3
  package pre-removal script subprocess returned error exit status 127

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  dont know

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  AptOrdering:
   python3:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Dec 14 18:15:13 2020
  ErrorMessage: new python3 package pre-removal script subprocess returned 
error exit status 127
  InstallationDate: Installed on 2020-12-03 (10 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, unpackaged
  PythonDetails: /usr/bin/python3.8, Python 3.8.5, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.2
  SourcePackage: python3-defaults
  Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: new python3 
package pre-removal script subprocess returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1908073/+subscriptions

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

[Touch-packages] [Bug 1871641] Re: Ubuntu never finishes booting: A start job is running for Hold until boot process finishes up (3min 7s / no limit) -- removing 'splash' kernel parm fixes it

[Daniel van Vugt]

Mordi,

Please ensure you have the latest updates installed:

  sudo apt update
  sudo apt full-upgrade

then reboot and tell us if you still experience the problem.

** Changed in: plymouth (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Ubuntu never finishes booting: A start job is running for Hold until
  boot process finishes up (3min 7s / no limit) -- removing 'splash'
  kernel parm fixes it

Status in plymouth package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Boot process freezes at the splash screen and nothing happens after
  that. The computer can be suspended and it is able to return from
  suspend. Boot is possible by pressing escape early in the process to
  bypass plymouth.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: plymouth 0.9.4git20200323-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  Date: Wed Apr  8 14:30:13 2020
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  InstallationDate: Installed on 2020-04-08 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: LENOVO 7469A23
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=e12af5fd-b700-4292-8727-70345cb61c8e ro quiet splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=e12af5fd-b700-4292-8727-70345cb61c8e ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6DET72WW (3.22 )
  dmi.board.name: 7469A23
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6DET72WW(3.22):bd10/25/2012:svnLENOVO:pn7469A23:pvrThinkPadX200s:rvnLENOVO:rn7469A23:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X200s
  dmi.product.name: 7469A23
  dmi.product.version: ThinkPad X200s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1907905] Re: buging

[Seth Arnold]

** Information type changed from Private Security to Public

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

Title:
  buging

Status in xorg package in Ubuntu:
  New

Bug description:
  just have a lot of gren points and com`s and disapiering picture

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 12 15:32:53 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:5000]
  InstallationDate: Installed on 2020-11-14 (27 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 33663VG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-32-generic 
root=UUID=d4192c33-e4f0-4468-8ebe-426000ec3852 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2013
  dmi.bios.release: 2.54
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H0ET94WW (2.54 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 33663VG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 2.54
  dmi.modalias: 
dmi:bvnLENOVO:bvrH0ET94WW(2.54):bd08/02/2013:br2.54:efr2.54:svnLENOVO:pn33663VG:pvrThinkPadEdgeE530c:rvnLENOVO:rn33663VG:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Edge E530c
  dmi.product.name: 33663VG
  dmi.product.sku: LENOVO_MT_3366
  dmi.product.version: ThinkPad Edge E530c
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1~ubuntu0.20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1908153] [NEW] [Alienware 15 R4, Realtek ALC3266, Black Headphone Out or internal speakers] Underruns, dropouts or crackling sound

[Dave Taylor]

Public bug reported:

With this latest update (Linux 5.4.0-58), the sound is now crackling.
Feels like DMA buffer underruns, but I'm not sure.  Not seeing a
significant CPU load that might have aggravated it, nor am I seeing any
complaints in syslog or kern.log.  Restarting pulseaudio and running
alsa force-reload had no effect.

These sound issues started with the same update that caused the
ath10k_pci driver to become extremely unreliable (filed as bug 1908106).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ddt   22891 F pulseaudio
 /dev/snd/controlC0:  ddt   22891 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 14 14:55:14 2020
InstallationDate: Installed on 2020-03-23 (266 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Symptom_PulseAudioLog:
 Dec 14 07:32:47 ddtlap dbus-daemon[859]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.32' (uid=124 pid=1157 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
 Dec 14 08:11:14 ddtlap pulseaudio[1157]: Failed to create sink input: sink is 
suspended.
 Dec 14 08:12:19 ddtlap pulseaudio[1157]: Failed to create sink input: sink is 
suspended.
 Dec 14 08:13:47 ddtlap dbus-daemon[859]: [system] Rejected send message, 0 
matched rules; type="method_return", sender=":1.70" (uid=1000 pid=1553 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") 
interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" 
destination=":1.3" (uid=0 pid=855 comm="/usr/lib/bluetooth/bluetoothd " 
label="unconfined")
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [Alienware 15 R4, Realtek ALC3266, Black Headphone Out, Left] Underruns, 
dropouts or crackling sound
UpgradeStatus: Upgraded to focal on 2020-05-12 (216 days ago)
dmi.bios.date: 04/18/2019
dmi.bios.vendor: Alienware
dmi.bios.version: 1.7.0
dmi.board.name: Alienware 15 R4
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Alienware
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnAlienware:bvr1.7.0:bd04/18/2019:svnAlienware:pnAlienware15R4:pvr1.7.0:rvnAlienware:rnAlienware15R4:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
dmi.product.family: Alienware
dmi.product.name: Alienware 15 R4
dmi.product.sku: 0876
dmi.product.version: 1.7.0
dmi.sys.vendor: Alienware

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


** Tags: amd64 apport-bug focal

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

Title:
  [Alienware 15 R4, Realtek ALC3266, Black Headphone Out or internal
  speakers] Underruns, dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  With this latest update (Linux 5.4.0-58), the sound is now crackling.
  Feels like DMA buffer underruns, but I'm not sure.  Not seeing a
  significant CPU load that might have aggravated it, nor am I seeing
  any complaints in syslog or kern.log.  Restarting pulseaudio and
  running alsa force-reload had no effect.

  These sound issues started with the same update that caused the
  ath10k_pci driver to become extremely unreliable (filed as bug
  1908106).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ddt   22891 F pulseaudio
   /dev/snd/controlC0:  ddt   22891 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 14 14:55:14 2020
  InstallationDate: Installed on 2020-03-23 (266 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback 

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

[DDD]

i don't have dmic_datect=0 in alsa conf, only:
options snd-hda-intel index=1 model=laptop-dmic

if i delete this, i still have no mic.

-- 
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 1908140] [NEW] Bond DHCP fails on Ubuntu Server 20.04 netplan

[Ryan]

Public bug reported:

I recently installed Ubuntu Server 20.04 to replace an ESXi server.
During the installation, I configured a bonded interface for two
ethernet interfaces. I configured the bond on my ZyXel GS1900-8 as a
static LAG. During the setup process, the link came up successfully and
was leased an IP via DHCP.

All subsequent boots have failed to acquire an IP address for the bonded
interface. Sometimes, if I allow dhcp4 on the enslaved interfaces, and
run sudo dhclient -r && sudo dhclient, the enslaved interfaces will be
leased an IP address _and_ the bond will get an IP address. I know this
is not proper as dhclient and systemd-networkd do not mix.

Also, I would like to configure this as a LACP bond instead. I have
enabled LACP on the switch with priority 65535 and "IP/MAC address" load
balancing algorithm, switched the LAG from static to LACP, and altered
netplan to use the 802.3ad bond mode.

Please let me know what, if anything, I'm doing wrong here. I've looked
around at as many netplan DHCP bond posts here as I could find to no
avail. See below for configuration files and command outputs. I cannot
give you the output of `lsb_release -rd` as the package is not installed
and there's no connection to install it.

$ cat /etc/netplan/00-bond.yaml
network:
  version: 2
  renderer: networkd
  ethernets:
eth0:
  dhcp4: false
eth1:
  dhcp4: false
  bonds:
bond0:
  dhcp4: true
  interfaces:
- eth0
- eth1
  parameters:
mode: 802.3ad

$ sudo journalctl -b -u systemd-networkd
Dec 14 08:06:47 lore systemd[1]: Starting Network Service...
Dec 14 08:06:47 lore systemd-networkd[852]: bond0: netdev ready
Dec 14 08:06:47 lore systemd-networkd[852]: Enumeration completed.
Dec 14 08:06:47 lore systemd[1]: Started Network Service.
Dec 14 08:06:47 lore systemd-networkd[852]: bond0: IPv6 successfully enabled
Dec 14 08:06:47 lore systemd-networkd[852]: bond0: Link UP
Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link 
'7' we don't know about, ignoring.
Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link 
'7' we don't know about, ignoring.
Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link 
'7' we don't know about, ignoring.
Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link 
'7' we don't know about, ignoring.
Dec 14 08:08:53 lore systemd-networkd[852]: docker0: Link UP

$ sudo ip a
lo:  mtu 65536 qdisc noqueue state UNKNOWN group default 
qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred lft forever
eno1:  mtu 1500 qdisk noop state DOWN group default qlen 
1000
link/ether 0c:c4:7a:c6:c3:46 brd ff:ff:ff:ff:ff:ff
eno2:  mtu 1500 qdisk noop state DOWN group default qlen 
1000
link/ether 0c:c4:7a:c6:c3:47 brd ff:ff:ff:ff:ff:ff
eth0:  mtu 1500 qdisc noop state DOWN group default qlen 
1000
link/ether 0c:c4:7a:c6:c6:a2 brd ff:ff:ff:ff:ff:ff
eth1:  mtu 1500 qdisc noop state DOWN group default qlen 
1000
link/ether 0c:c4:7a:c6:c6:a3 brd ff:ff:ff:ff:ff:ff
bond0:  mtu 1500 qdisk noqueue state 
DOWN group default qlen 1000
link/ether 52:8b:2c:cc:a0:15 brd ff:ff:ff:ff:ff:ff
docker0:  mtu 1500 qdisc noqueue state DOWN 
group default
link/ether 02:42:26:1c:1b:39 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker 0
   valid_lft forever preferred_lft forever

$ cat /run/systemd/network/10-netplan-bond0.netdev
[NetDev]
Name=bond0
Kind=bond

[Bond]
Mode=802.3ad

$ cat /run/systemd/network/10-netplan-bond0.network
[Match]
Name=bond0

[Network]
DHCP=ipv4
LinkLocalAddressing=ipv6
ConfigureWithoutCarrier=yes

[DHCP]
RouteMetric=100
UseMTU=true

$ cat /run/systemd/network/10-netplan-eth0.network
[Match]
Name=eth0

[Network]
LinkLocalAddressing=no
Bond=bond0

$ cat /run/systemd/network/10-netplan-eth1.network
[Match]
Name=eth1

[Network]
LinkLocalAddressing=no
Bond=bond0

$ cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: down
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Peer Notification Delay (ms): 0

802.3ad info
LACP rate: slow
Min links: 0
Aggregator selection policy (ad_select): stable

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

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

Title:
  Bond DHCP fails on Ubuntu Server 20.04 netplan

Status in systemd package in Ubuntu:
  New

Bug description:
  I recently installed Ubuntu Server 20.04 to replace an ESXi server.
  During the installation, I configured a bonded interface for two
  ethernet 

[Touch-packages] [Bug 1908136] Re: no_proxy=::1 is not honored by curl in Bionic and earlier versions

[Balint Reczey]

** Summary changed:

- no_proxy=::1 is not honored in Bionic and earlier versions
+ no_proxy=::1 is not honored by curl in Bionic and earlier versions

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

Title:
  no_proxy=::1 is not honored by curl in Bionic and earlier versions

Status in Auto Package Testing:
  New
Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Xenial:
  New
Status in curl source package in Bionic:
  New
Status in curl source package in Focal:
  Fix Released

Bug description:
  Bionic:

  env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html
  * Could not resolve proxy: foo
  * Closing connection 0
  curl: (5) Could not resolve proxy: foo

  Focal:

  $ env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html
  * Uses proxy env variable no_proxy == '::1'
  *   Trying ::1:80...
  * TCP_NODELAY set
  * Immediate connect fail for ::1: Network is unreachable
  * Closing connection 0
  curl: (7) Couldn't connect to server

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1908136/+subscriptions

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

[Touch-packages] [Bug 1481779] Re: apt-get autoremove crashes my system

[Jahoner D]

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

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

Title:
  apt-get autoremove crashes my system

Status in apt package in Ubuntu:
  Confirmed

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

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

[Touch-packages] [Bug 1908136] Re: no_proxy=::1 is not honored in Bionic and earlier versions

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~rbalint/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/395336

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

Title:
  no_proxy=::1 is not honored in Bionic and earlier versions

Status in Auto Package Testing:
  New
Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Xenial:
  New
Status in curl source package in Bionic:
  New
Status in curl source package in Focal:
  Fix Released

Bug description:
  Bionic:

  env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html
  * Could not resolve proxy: foo
  * Closing connection 0
  curl: (5) Could not resolve proxy: foo

  Focal:

  $ env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html
  * Uses proxy env variable no_proxy == '::1'
  *   Trying ::1:80...
  * TCP_NODELAY set
  * Immediate connect fail for ::1: Network is unreachable
  * Closing connection 0
  curl: (7) Couldn't connect to server

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1908136/+subscriptions

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

[Touch-packages] [Bug 1908136] Re: no_proxy=::1 is not honored in Bionic and earlier versions

[Balint Reczey]

Recently the autopkgtest infrastructure configuration has been changed
to add ::1 to no_proxy. This works on Focal and up, but breaks unknown
number of tests in Bionic and earlier releases.


commit f3679e7609b2f03d59aca28fe7329e4228350200
Author: Steve Langasek 
Date:   Fri Dec 4 12:00:02 2020 -0800

Include ipv6 localhost in the list of addresses not to use the proxy for.

This fixes schleuder autopkgtest failure on armhf, which tries to connect
to [::1]:4443 and fails because it's routed to the proxy.

This failure does not affect the VM-based autopkgtest runners because
containers also have some strangeness regarding binding to ::1 being treated
as bindv6only=1, and schleuder's test only requires that ipv4 *or* ipv6
succeeds; but the change is appropriate across all architectures.

 lxc-slave-admin/setup-adt-lxc.commands | 2 +-
 tools/armhf-lxd-slave.userdata | 2 +-
 worker-config-production/worker-bos01-arm64.conf   | 2 +-
 worker-config-production/worker-bos01-ppc64el.conf | 2 +-
 worker-config-production/worker-bos01-s390x.conf   | 2 +-
 worker-config-production/worker-bos01.conf | 2 +-
 worker-config-production/worker-bos02-arm64.conf   | 2 +-
 worker-config-production/worker-bos02-ppc64el.conf | 2 +-
 worker-config-production/worker-bos02-s390x.conf   | 2 +-
 worker-config-production/worker-canonistack.conf   | 2 +-
 worker-config-production/worker-lxd.conf   | 2 +-
 worker-config-production/worker.conf   | 2 +-
 12 files changed, 12 insertions(+), 12 deletions(-)

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

Title:
  no_proxy=::1 is not honored in Bionic and earlier versions

Status in Auto Package Testing:
  New
Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Xenial:
  New
Status in curl source package in Bionic:
  New
Status in curl source package in Focal:
  Fix Released

Bug description:
  Bionic:

  env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html
  * Could not resolve proxy: foo
  * Closing connection 0
  curl: (5) Could not resolve proxy: foo

  Focal:

  $ env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html
  * Uses proxy env variable no_proxy == '::1'
  *   Trying ::1:80...
  * TCP_NODELAY set
  * Immediate connect fail for ::1: Network is unreachable
  * Closing connection 0
  curl: (7) Couldn't connect to server

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1908136/+subscriptions

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

[Touch-packages] [Bug 1908136] Re: no_proxy=::1 is not honored in Bionic and earlier versions

[Balint Reczey]

Upstream bug:
https://github.com/curl/curl/issues/2353

** Also affects: auto-package-testing
   Importance: Undecided
   Status: New

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

Title:
  no_proxy=::1 is not honored in Bionic and earlier versions

Status in Auto Package Testing:
  New
Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Xenial:
  New
Status in curl source package in Bionic:
  New
Status in curl source package in Focal:
  Fix Released

Bug description:
  Bionic:

  env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html
  * Could not resolve proxy: foo
  * Closing connection 0
  curl: (5) Could not resolve proxy: foo

  Focal:

  $ env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html
  * Uses proxy env variable no_proxy == '::1'
  *   Trying ::1:80...
  * TCP_NODELAY set
  * Immediate connect fail for ::1: Network is unreachable
  * Closing connection 0
  curl: (7) Couldn't connect to server

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1908136/+subscriptions

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

[Touch-packages] [Bug 1908136] [NEW] no_proxy=::1 is not honored in Bionic and earlier versions

[Balint Reczey]

Public bug reported:

Bionic:

env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html
* Could not resolve proxy: foo
* Closing connection 0
curl: (5) Could not resolve proxy: foo

Focal:

$ env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html
* Uses proxy env variable no_proxy == '::1'
*   Trying ::1:80...
* TCP_NODELAY set
* Immediate connect fail for ::1: Network is unreachable
* Closing connection 0
curl: (7) Couldn't connect to server

** Affects: auto-package-testing
 Importance: Undecided
 Status: New

** Affects: curl (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: curl (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: curl (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: curl (Ubuntu Focal)
 Importance: Undecided
 Status: Fix Released

** Also affects: curl (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Also affects: curl (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

** Bug watch added: github.com/curl/curl/issues #2353
   https://github.com/curl/curl/issues/2353

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

Title:
  no_proxy=::1 is not honored in Bionic and earlier versions

Status in Auto Package Testing:
  New
Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Xenial:
  New
Status in curl source package in Bionic:
  New
Status in curl source package in Focal:
  Fix Released

Bug description:
  Bionic:

  env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html
  * Could not resolve proxy: foo
  * Closing connection 0
  curl: (5) Could not resolve proxy: foo

  Focal:

  $ env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html
  * Uses proxy env variable no_proxy == '::1'
  *   Trying ::1:80...
  * TCP_NODELAY set
  * Immediate connect fail for ::1: Network is unreachable
  * Closing connection 0
  curl: (7) Couldn't connect to server

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1908136/+subscriptions

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

[Touch-packages] [Bug 1876383] Re: issues with full screen videos

[Launchpad Bug Tracker]

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

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

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

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

Title:
  issues with full screen videos

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When watching MP4 clips using the default app (videos) I have a display issue.
  When clicking on the full screen button here is what happens:

  1- screen goes blank for a few seconds
  2- a new videos window opens up with displaying the move but it it is not 
maximized or in full screen
  3- The original maximized window stays in the background with a still picture

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  1 17:21:04 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Iris Plus Graphics 650 [8086:5927] (rev 06) (prog-if 00 
[VGA controller])
 Subsystem: Intel Corporation Iris Plus Graphics 650 [8086:2068]
  InstallationDate: Installed on 2020-04-24 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/19/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0070.2018.1019.1503
  dmi.board.name: NUC7i7BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31145-304
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0070.2018.1019.1503:bd10/19/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-304:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1876577] Re: fullscreen in browser and video player with fractional scaling(150%) enabled corrupted display

[Launchpad Bug Tracker]

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

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

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

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

Title:
  fullscreen in browser and video player with fractional scaling(150%)
  enabled corrupted display

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  when fractional scaling is enabled for example 150%, trying to
  fullscreen the video playing in the browser or in the video player,
  display suddenly goes black, and then video resolution size is reduced
  to 1/4 of the actual screen size, with a still frame from the video as
  background and every app opened in the bacground becomes so large that
  it goes out of the window. also the mouse cursor stuck on the screen
  if auto login is disabled

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 18:20:08 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] 
[1002:687f] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Vega 10 XL/XT [Radeon RX Vega 56/64] 
[1043:04c4]
  InstallationDate: Installed on 2020-04-24 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=a12e4265-d2f1-4a68-b9f4-840dc9e18df1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5406
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1901609] Re: signond causes qprocess crash

[Rik Mills]

On 14/12/2020 18:48, Łukasz Zemczak wrote:
> Sadly I cannot release the focal SRU as it seems that the signon package
> FTBFS on ppc64el there:
> 
> https://launchpad.net/ubuntu/+source/signon/8.59+17.10.20170606-0ubuntu2.20.04.1/+build/20365793
> 
> It seems to have built fine previously. Can someone take a look?
> 
> ** Changed in: signon (Ubuntu Focal)
>Status: Fix Committed => Incomplete
> 

seems that failed to build without a log, so likely a launchpad 'burp'.
a retry made it build ok

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

Title:
  signond causes qprocess crash

Status in signon package in Ubuntu:
  Fix Released
Status in signon source package in Focal:
  Incomplete
Status in signon source package in Groovy:
  Fix Released
Status in signon source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Without the patch users are unable to add google accounts because signond 
crashes.
  This prevents users from using KDE's online accounts feature for google.
  The fix for this is to drop the no-rtti compile flag as qprocess relies on 
type info. This has no real downside for the user as it simply brings in type 
info.

  [Test Case]

  - in a plasma session
  - install kio-gdrive
  - run `systemsettings5 kcm_kaccounts`
  - add a new account
  - click on google
  - wait for login window to appear
  - signond shouldn't be crashing

  [Where problems could occur]

  Cannot think of any. It simply adds type info to the objects. Also
  upstream has rtti disabled for months and I'm not aware of any
  problems.

  [Other Info]

  This is a fairly grave issue as far as user experience is concerned.

  
  

  
  I'm reporting this bug upstream from where I found it, since I've learned 
that the signond package in KDE Neon is sourced from Ubuntu focal.

  This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64)
  from Focal Fossa

  Steps to reproduce:

  1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon)
  2. Install the kaccounts integration and kio-gdrive packages.
  3. Open System settings and navigate to "Online Accounts"
  4. Press "+ Add New Account"
  5. Select "Google"

  Observed behaviour:

  - Window that would ask for authentication fails to load, and Online Accounts 
goes back to overview
  - system logs show a segfault in libqt5core.so which can be traced to a 
failure in qporcess, casued by signond (see links for further details)

  Expected behaviour:
  - New window opens with a webview where Google authentication credentials can 
be posted.
  - When qprocess runs it does not crash.

  Further reference information at the following links:

  1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034

  3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts-
  sso/signond/-/merge_requests/27

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

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

[Touch-packages] [Bug 1773476] Re: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present

[B. C. Schmerker]

Actually would have been a bug against either apt or dpkg, which failed
to clean up /var after Kernel package removal.  Since upgraded to ubuntu
Focal, closing Bug.


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

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

Title:
  linux-firmware 1.157.19 attempts to generate
  /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no
  corresponding vmlinuz present

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic,
  4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed,
  sudo dpkg-reconfigure linux-firmware returns the following to Console:

  update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic
  update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic
  update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic
  update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic
  update-initramfs: Generating /boot/initrd.img-4.8.0-56
  WARNING: missing /lib/modules/4.8.0-56
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file 
or directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or 
directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file 
or directory
  update-initramfs: Generating /boot/initrd.img-4.8.0
  WARNING: missing /lib/modules/4.8.0
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or 
directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or 
directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or 
directory
  update-initramfs: Generating /boot/initrd.img-4.4.0-127-generic

  Same configuration report for "Setting up linux-firmware..." with sudo
  apt(-get) install (--reinstall) linux-firmware and sudo apt-get
  upgrade linux-firmware.  Therefore:

  Reproducible: Always
  Steps to reproduce: sudo apt install (--reinstall) linux-firmware or sudo 
dpkg-reconfigure linux-firmware.
  Actual results, excepting actually installed Kernel Image packages:

  update-initramfs: Generating /boot/initrd.img-4.8.0-56
  WARNING: missing /lib/modules/4.8.0-56
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file 
or directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or 
directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file 
or directory
  update-initramfs: Generating /boot/initrd.img-4.8.0
  WARNING: missing /lib/modules/4.8.0
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or 
directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or 
directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or 
directory

  Expected results, excepting actually installed Kernel Image packages:

  No attempt to generate /boot/initrd.img for missing kernels, thus no
  warnings, errors or fatals.

  UPDATE:  Solved via sudo rm -rf /var/lib/initramfs-tools/4.8.0 && sudo
  rm -rf /var/lib/initramfs-tools/4.8.0-56.  Recommend check for bug(s)
  in apt and dpkg of which this Bug may be a depend, as automatic
  housecleaning failed me in this specific case.

  ---
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CurrentDesktop: Unity
  Dependencies:

  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2017-05-17 (373 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Package: linux-firmware 1.157.19 [origin: unknown]
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17
  Tags: xenial third-party-packages
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip 

[Touch-packages] [Bug 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Mathew Hodson]

** Bug watch removed: github.com/systemd/systemd/issues #12616
   https://github.com/systemd/systemd/issues/12616

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Won't Fix
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

     On Xenial X runs on VT7 thus the graphical environment is not affected in 
the default configuration, but the keyboard-configuration postinst maintaner 
script still changes mode on vt1-6, thus at the beginning set VT1 to raw mode 
to observe the change:
     $  sudo kbd_mode -s -C /dev/tty1
     $ sudo kbd_mode -C /dev/tty1
     The keyboard is in raw (scancode) mode

   * Install or reinstall kbd-configuration

     $ sudo apt install --reinstall keyboard-configuration
     ...
     Setting up keyboard-configuration (1.178ubuntu11) ...
     Your console font configuration will be updated the next time your system
     boots. If you 

[Touch-packages] [Bug 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Mathew Hodson]

A patch was applied to console-setup so that --force is only used with
debian-installer, which you can see here:
https://launchpadlibrarian.net/420660116/console-
setup_1.191ubuntu1_1.191ubuntu2.diff.gz

You can see the current code for Groovy at
https://git.launchpad.net/ubuntu/+source/console-setup/tree/debian
/keyboard-
configuration.postinst?h=ubuntu/groovy=4c8bc0d16b2b0dcefe2a38e3060e38863b7bb736#n113

Since this bug was closed when that patch was released, please report a
new bug so it can be determined if another fix is needed.

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Won't Fix
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

     On Xenial X runs on VT7 thus the graphical environment is not affected in 
the default configuration, but the keyboard-configuration postinst maintaner 
script still changes mode on vt1-6, thus at the beginning set 

[Touch-packages] [Bug 1906565] Re: traceback when running apport as non-root user

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.1-0ubuntu2.28

---
apport (2.20.1-0ubuntu2.28) xenial; urgency=medium

  * data/apport: only drop supplemental groups if the user is root. (LP:
#1906565)

 -- Brian Murray   Thu, 03 Dec 2020 10:33:00 -0800

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Bionic:
  Fix Released
Status in apport source package in Focal:
  Fix Released
Status in apport source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

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

[Touch-packages] [Bug 1906565] Re: traceback when running apport as non-root user

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.9-0ubuntu7.21

---
apport (2.20.9-0ubuntu7.21) bionic; urgency=medium

  * data/apport: only drop supplemental groups if the user is root. (LP:
#1906565)

 -- Brian Murray   Thu, 03 Dec 2020 09:39:34 -0800

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

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

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Bionic:
  Fix Released
Status in apport source package in Focal:
  Fix Released
Status in apport source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

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

[Touch-packages] [Bug 1899100] Re: whoopsie assert failure: double free or corruption (fasttop)

[Launchpad Bug Tracker]

This bug was fixed in the package whoopsie - 0.2.62ubuntu0.6

---
whoopsie (0.2.62ubuntu0.6) bionic; urgency=medium

  * Attempt to fix double free issue (LP: #1899100)
- src/whoopsie.c: reject duplicate keys, re-order certain operations.
- src/tests/data/crash/invalid_key_duplicate,
  src/tests/test_parse_report.c: added test for duplicate keys.

 -- Brian Murray   Wed, 02 Dec 2020 09:35:52 -0800

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

Title:
  whoopsie assert failure: double free or corruption (fasttop)

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Bionic:
  Fix Released
Status in whoopsie source package in Focal:
  Fix Released
Status in whoopsie source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  whoopsie is crashing somewhat regularly. There are a couple of crashes in the 
Error Tracker which look similar:

  https://errors.ubuntu.com/problem/5c1f68854a0f3bd5e263f1cd35e4dd944c9e90bd
  https://errors.ubuntu.com/problem/5d7e641dc46229c08389420fdd74a7473d2dec98

  As of yet (2020-11-22) neither crash is happening with whoopsie
  version 0.2.73.

  [Test Case]
  We don't have a manual test case for this crash report but given the number 
of crashes in the Error Tracker and the number of users of whoopsie the absence 
of the same crash occurring with the new version of whoopsie should be enough 
to consider this verified.

  [Regression Potential]
  Whoopsie will no longer upload crash reports with duplicate keys but this was 
not something it should have been doing in the first place. That being said we 
should also test whoopsie with a sample of crashes (apport-test-crashes) and 
ensure they are received by the staging version of the Ubuntu Error Tracker.

  Original Description
  
  Apport popped up saying whoopsie had crashed (I assume during a previous 
crash report upload?)

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AssertionMessage: double free or corruption (fasttop)
  CasperMD5CheckResult: skip
  CrashCounter: 1
  Date: Fri Oct  9 08:08:56 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2019-11-18 (325 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  RelatedPackageVersions: apport-noui N/ASignal: 6SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption 
(fasttop)") at malloc.c:5389
   _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at 
malloc.c:4298
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: double free or corruption (fasttop)
  UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago)
  UserGroups: N/A
  separator:

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

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

[Touch-packages] [Bug 1901609] Re: signond causes qprocess crash

[Łukasz Zemczak]

Sadly I cannot release the focal SRU as it seems that the signon package
FTBFS on ppc64el there:

https://launchpad.net/ubuntu/+source/signon/8.59+17.10.20170606-0ubuntu2.20.04.1/+build/20365793

It seems to have built fine previously. Can someone take a look?

** Changed in: signon (Ubuntu Focal)
   Status: Fix Committed => Incomplete

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

Title:
  signond causes qprocess crash

Status in signon package in Ubuntu:
  Fix Released
Status in signon source package in Focal:
  Incomplete
Status in signon source package in Groovy:
  Fix Released
Status in signon source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Without the patch users are unable to add google accounts because signond 
crashes.
  This prevents users from using KDE's online accounts feature for google.
  The fix for this is to drop the no-rtti compile flag as qprocess relies on 
type info. This has no real downside for the user as it simply brings in type 
info.

  [Test Case]

  - in a plasma session
  - install kio-gdrive
  - run `systemsettings5 kcm_kaccounts`
  - add a new account
  - click on google
  - wait for login window to appear
  - signond shouldn't be crashing

  [Where problems could occur]

  Cannot think of any. It simply adds type info to the objects. Also
  upstream has rtti disabled for months and I'm not aware of any
  problems.

  [Other Info]

  This is a fairly grave issue as far as user experience is concerned.

  
  

  
  I'm reporting this bug upstream from where I found it, since I've learned 
that the signond package in KDE Neon is sourced from Ubuntu focal.

  This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64)
  from Focal Fossa

  Steps to reproduce:

  1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon)
  2. Install the kaccounts integration and kio-gdrive packages.
  3. Open System settings and navigate to "Online Accounts"
  4. Press "+ Add New Account"
  5. Select "Google"

  Observed behaviour:

  - Window that would ask for authentication fails to load, and Online Accounts 
goes back to overview
  - system logs show a segfault in libqt5core.so which can be traced to a 
failure in qporcess, casued by signond (see links for further details)

  Expected behaviour:
  - New window opens with a webview where Google authentication credentials can 
be posted.
  - When qprocess runs it does not crash.

  Further reference information at the following links:

  1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034

  3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts-
  sso/signond/-/merge_requests/27

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

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

[Touch-packages] [Bug 1906565] Re: traceback when running apport as non-root user

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.11-0ubuntu27.14

---
apport (2.20.11-0ubuntu27.14) focal; urgency=medium

  * data/apport: only drop supplemental groups if the user is root. (LP:
#1906565)

 -- Brian Murray   Thu, 03 Dec 2020 09:26:27 -0800

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

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Bionic:
  Fix Released
Status in apport source package in Focal:
  Fix Released
Status in apport source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

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

[Touch-packages] [Bug 1899100] Re: whoopsie assert failure: double free or corruption (fasttop)

[Launchpad Bug Tracker]

This bug was fixed in the package whoopsie - 0.2.69ubuntu0.2

---
whoopsie (0.2.69ubuntu0.2) focal; urgency=medium

  * Attempt to fix double free issue (LP: #1899100)
- src/whoopsie.c: reject duplicate keys, re-order certain operations.
- src/tests/data/crash/invalid_key_duplicate,
  src/tests/test_parse_report.c: added test for duplicate keys.

 -- Brian Murray   Wed, 02 Dec 2020 09:29:08 -0800

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

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

Title:
  whoopsie assert failure: double free or corruption (fasttop)

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Bionic:
  Fix Released
Status in whoopsie source package in Focal:
  Fix Released
Status in whoopsie source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  whoopsie is crashing somewhat regularly. There are a couple of crashes in the 
Error Tracker which look similar:

  https://errors.ubuntu.com/problem/5c1f68854a0f3bd5e263f1cd35e4dd944c9e90bd
  https://errors.ubuntu.com/problem/5d7e641dc46229c08389420fdd74a7473d2dec98

  As of yet (2020-11-22) neither crash is happening with whoopsie
  version 0.2.73.

  [Test Case]
  We don't have a manual test case for this crash report but given the number 
of crashes in the Error Tracker and the number of users of whoopsie the absence 
of the same crash occurring with the new version of whoopsie should be enough 
to consider this verified.

  [Regression Potential]
  Whoopsie will no longer upload crash reports with duplicate keys but this was 
not something it should have been doing in the first place. That being said we 
should also test whoopsie with a sample of crashes (apport-test-crashes) and 
ensure they are received by the staging version of the Ubuntu Error Tracker.

  Original Description
  
  Apport popped up saying whoopsie had crashed (I assume during a previous 
crash report upload?)

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AssertionMessage: double free or corruption (fasttop)
  CasperMD5CheckResult: skip
  CrashCounter: 1
  Date: Fri Oct  9 08:08:56 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2019-11-18 (325 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  RelatedPackageVersions: apport-noui N/ASignal: 6SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption 
(fasttop)") at malloc.c:5389
   _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at 
malloc.c:4298
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: double free or corruption (fasttop)
  UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago)
  UserGroups: N/A
  separator:

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

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

[Touch-packages] [Bug 730307] Re: ALT-F[1-8] switches to text console

[Mathew Hodson]

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

** This bug has been marked a duplicate of bug 520546
   [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT 
switch from Alt+Left/Right

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

Title:
  ALT-F[1-8] switches to text console

Status in console-tools package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: xorg

  Related bug: bug 463762 (probably exactly the same bug)

  not only ALT-CTRL-F[1-8] switches to the text console from X-Server,
  but also ALT-F[1-8] does this switching. I don't know where this comes
  from, but it breaks lots of stuff, i.e. ALT-F4 to close an app, ALT-F2
  to open the quick-start-applet, ... This happens not only on my
  desktop, but also on a GDM login desktop too.

  Strange thing is that if I switch back to the X-Server from the text
  console with ALT-F7, the actual keyboard action is executed in the
  X-Server, i.e. if I press ALT-F4, the text console is shown, when I
  switch back, the current application is closed!

  I saw this a while ago after update from 8.04 to 10.04 LTS on a
  different laptop (Toshiba with Nvidia graphix), and now the same bug
  on a fresh install of 10.10 on Lenovo X200t.

  I am using Russian keyboard layout. Once I delete the Russian keyboard
  layout and log-out, the bug is gone. But even without the Russian
  layout the bug returns after reboot. But then it goes away after I add
  the Russian layout and log out then log in. It seems that changing the
  layout disables the bug until next reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: xorg 1:7.5+6ubuntu3
  ProcVersionSignature: Ubuntu 2.6.35-27.48-generic-pae 2.6.35.11
  Uname: Linux 2.6.35-27-generic-pae i686
  Architecture: i386
  DRM.card0.DP.1:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.DP.2:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.DP.3:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.HDMI.A.1:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.HDMI.A.2:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.LVDS.1:
   status: connected
   enabled: enabled
   dpms: On
   modes: 1280x800
   edid-base64: 
AP///wAwrhFAAC0SAQOAGhB46oXFlFdPiicgUFQBAQEBAQEBAQEBAQEBAQEBwBsAq1AgEDA0QDMABaMQAAAZwBsAq1AgEDA0QDMABaMQAAAZDwCBCjyBCjweAABMo1cx/gBMVE4xMjFBUDAzMDAxAOw=
  DRM.card0.VGA.1:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  Date: Mon Mar  7 00:52:19 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1)
  MachineType: LENOVO 7448CTO
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-27-generic-pae 
root=UUID=6c8fd8aa-fe87-482a-869a-2254bd16f22c ro quiet splash
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: xorg
  dmi.bios.date: 12/02/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WET67WW (3.17 )
  dmi.board.name: 7448CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WET67WW(3.17):bd12/02/2010:svnLENOVO:pn7448CTO:pvrThinkPadX200Tablet:rvnLENOVO:rn7448CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7448CTO
  dmi.product.version: ThinkPad X200 Tablet
  dmi.sys.vendor: LENOVO
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   codename:   maverick
   architecture:   i686
   kernel: 2.6.35-27-generic-pae

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

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

[Touch-packages] [Bug 1823327] Re: booting cloud images on a Multipass Windows hosted enviroment is slow in the initramfs stage due to font setup / framebuffer issues

[Mathew Hodson]

** Changed in: cloud-images
   Status: New => Fix Released

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

Title:
  booting cloud images on a Multipass Windows hosted enviroment is slow
  in the initramfs stage due to font setup / framebuffer issues

Status in cloud-images:
  Fix Released
Status in console-setup package in Ubuntu:
  Fix Released
Status in console-setup source package in Bionic:
  Won't Fix

Bug description:
  Booting an azure kernel Cosmic cloud image with multipass on Windows
  10 pro takes a long time. Using systemd-analyze 25 seconds in kernel
  boot time is reported. Digging into this, the kernel boot time is
  actually ~5 seconds, the other 20 seconds before systemd init is
  exec'd is actually in the initramfs. I've instrumented the kernel to
  record the exec and exit times of each process in the kernel and the
  top offending processes in initramfs during boot are:

  Duration PID process
  14.86832 262 /scripts/init-top/console_setup
  2.48749 263 /bin/setfont
  2.45357 268 /bin/setfont
  2.44657 291 /bin/setfont
  2.44392 286 /bin/setfont
  2.43545 279 /bin/setfont
  2.43161 274 /bin/setfont
  1.19233 255 /scripts/init-top/framebuffer

  console_setup is calling setfont 7 times and each time setfint is
  taking more than 2.4 seconds to complete. Also the framebuffer program
  is taking over a second to run.

  For Disco with azure kernel:

  Duration PID process
  14.19028 275 console_setup
  2.39020 276 setfont
  2.34020 281 setfont
  2.32915 293 setfont
  2.32389 289 setfont
  2.32319 285 setfont
  2.32178 297 setfont
  1.11417 268 framebuffer

  For Xenial with generic kernel:

  Duration PID process
  15.01832 232 console_setup
  2.52273 233 setfont
  2.50960 238 setfont
  2.48476 250 setfont
  2.46333 256 setfont
  2.46289 262 setfont
  2.44667 268 setfont
  1.07674 225 framebuffer

  For Xenial with azure kernel:
  15.00529 260 console_setup
  2.49699 261 setfont
  2.47591 292 setfont
  2.47443 266 setfont
  2.47131 286 setfont
  2.46812 280 setfont
  2.45780 274 setfont
  1.07095 253 framebuffer

  so it seems to occur across releases with generic and azure kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1823327/+subscriptions

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

[Touch-packages] [Bug 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Mathew Hodson]

** No longer affects: xorg-server (Ubuntu)

** No longer affects: xorg-server (Ubuntu Lucid)

** No longer affects: xorg-server (Ubuntu Maverick)

** No longer affects: xorg-server (Ubuntu Xenial)

** No longer affects: xorg-server (Ubuntu Bionic)

** No longer affects: xorg-server (Ubuntu Cosmic)

** No longer affects: xorg-server (Ubuntu Disco)

** No longer affects: xorg-server (Ubuntu Eoan)

** No longer affects: linux (Ubuntu Bionic)

** No longer affects: linux (Ubuntu Cosmic)

** No longer affects: linux (Ubuntu Disco)

** No longer affects: linux (Ubuntu Eoan)

** No longer affects: kbd (Ubuntu Maverick)

** No longer affects: kbd (Ubuntu Lucid)

** No longer affects: console-setup (Ubuntu Maverick)

** No longer affects: console-setup (Ubuntu Lucid)

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Won't Fix
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

  

[Touch-packages] [Bug 1906565] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for apport has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Bionic:
  Fix Committed
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

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

[Touch-packages] [Bug 1901609] Re: signond causes qprocess crash

[Launchpad Bug Tracker]

This bug was fixed in the package signon -
8.59+17.10.20170606-0ubuntu2.20.10.1

---
signon (8.59+17.10.20170606-0ubuntu2.20.10.1) groovy; urgency=medium

  * Add ubuntu_01_rtti.diff to remove the no rtti flags as they'd
break compatibility with QProcess (LP: #1901609)
  * Build depend on quilt and integrate into debian/rules. Since this
this source uses the legacy v1 format we need to manually wire up
patching instead of having dpkg-source handle it

 -- Harald Sitter   Mon, 23 Nov 2020 13:24:59 +0100

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

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

Title:
  signond causes qprocess crash

Status in signon package in Ubuntu:
  Fix Released
Status in signon source package in Focal:
  Fix Committed
Status in signon source package in Groovy:
  Fix Released
Status in signon source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Without the patch users are unable to add google accounts because signond 
crashes.
  This prevents users from using KDE's online accounts feature for google.
  The fix for this is to drop the no-rtti compile flag as qprocess relies on 
type info. This has no real downside for the user as it simply brings in type 
info.

  [Test Case]

  - in a plasma session
  - install kio-gdrive
  - run `systemsettings5 kcm_kaccounts`
  - add a new account
  - click on google
  - wait for login window to appear
  - signond shouldn't be crashing

  [Where problems could occur]

  Cannot think of any. It simply adds type info to the objects. Also
  upstream has rtti disabled for months and I'm not aware of any
  problems.

  [Other Info]

  This is a fairly grave issue as far as user experience is concerned.

  
  

  
  I'm reporting this bug upstream from where I found it, since I've learned 
that the signond package in KDE Neon is sourced from Ubuntu focal.

  This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64)
  from Focal Fossa

  Steps to reproduce:

  1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon)
  2. Install the kaccounts integration and kio-gdrive packages.
  3. Open System settings and navigate to "Online Accounts"
  4. Press "+ Add New Account"
  5. Select "Google"

  Observed behaviour:

  - Window that would ask for authentication fails to load, and Online Accounts 
goes back to overview
  - system logs show a segfault in libqt5core.so which can be traced to a 
failure in qporcess, casued by signond (see links for further details)

  Expected behaviour:
  - New window opens with a webview where Google authentication credentials can 
be posted.
  - When qprocess runs it does not crash.

  Further reference information at the following links:

  1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034

  3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts-
  sso/signond/-/merge_requests/27

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

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

[Touch-packages] [Bug 1901609] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for signon has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  signond causes qprocess crash

Status in signon package in Ubuntu:
  Fix Released
Status in signon source package in Focal:
  Fix Committed
Status in signon source package in Groovy:
  Fix Released
Status in signon source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Without the patch users are unable to add google accounts because signond 
crashes.
  This prevents users from using KDE's online accounts feature for google.
  The fix for this is to drop the no-rtti compile flag as qprocess relies on 
type info. This has no real downside for the user as it simply brings in type 
info.

  [Test Case]

  - in a plasma session
  - install kio-gdrive
  - run `systemsettings5 kcm_kaccounts`
  - add a new account
  - click on google
  - wait for login window to appear
  - signond shouldn't be crashing

  [Where problems could occur]

  Cannot think of any. It simply adds type info to the objects. Also
  upstream has rtti disabled for months and I'm not aware of any
  problems.

  [Other Info]

  This is a fairly grave issue as far as user experience is concerned.

  
  

  
  I'm reporting this bug upstream from where I found it, since I've learned 
that the signond package in KDE Neon is sourced from Ubuntu focal.

  This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64)
  from Focal Fossa

  Steps to reproduce:

  1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon)
  2. Install the kaccounts integration and kio-gdrive packages.
  3. Open System settings and navigate to "Online Accounts"
  4. Press "+ Add New Account"
  5. Select "Google"

  Observed behaviour:

  - Window that would ask for authentication fails to load, and Online Accounts 
goes back to overview
  - system logs show a segfault in libqt5core.so which can be traced to a 
failure in qporcess, casued by signond (see links for further details)

  Expected behaviour:
  - New window opens with a webview where Google authentication credentials can 
be posted.
  - When qprocess runs it does not crash.

  Further reference information at the following links:

  1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034

  3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts-
  sso/signond/-/merge_requests/27

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

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

[Touch-packages] [Bug 1906565] Re: traceback when running apport as non-root user

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.11-0ubuntu50.3

---
apport (2.20.11-0ubuntu50.3) groovy; urgency=medium

  * data/apport: only drop supplemental groups if we are root. (LP:
#1906565)

 -- Brian Murray   Wed, 02 Dec 2020 12:51:33 -0800

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

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Bionic:
  Fix Committed
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

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

[Touch-packages] [Bug 1899100] Re: whoopsie assert failure: double free or corruption (fasttop)

[Brian Murray]

Looking at the Error Tracker crash buckets linked to from the bug
description the version of the package from focal-proposed and bionic-
proposed does not appear. Additionally, I was unable to find any similar
looking crashes in the Error Tracker so there are no new "double free"
buckets with the version of the package from -proposed. Subsequently,
I'm setting the tags to verification-done.

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

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

Title:
  whoopsie assert failure: double free or corruption (fasttop)

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Bionic:
  Fix Committed
Status in whoopsie source package in Focal:
  Fix Committed
Status in whoopsie source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  whoopsie is crashing somewhat regularly. There are a couple of crashes in the 
Error Tracker which look similar:

  https://errors.ubuntu.com/problem/5c1f68854a0f3bd5e263f1cd35e4dd944c9e90bd
  https://errors.ubuntu.com/problem/5d7e641dc46229c08389420fdd74a7473d2dec98

  As of yet (2020-11-22) neither crash is happening with whoopsie
  version 0.2.73.

  [Test Case]
  We don't have a manual test case for this crash report but given the number 
of crashes in the Error Tracker and the number of users of whoopsie the absence 
of the same crash occurring with the new version of whoopsie should be enough 
to consider this verified.

  [Regression Potential]
  Whoopsie will no longer upload crash reports with duplicate keys but this was 
not something it should have been doing in the first place. That being said we 
should also test whoopsie with a sample of crashes (apport-test-crashes) and 
ensure they are received by the staging version of the Ubuntu Error Tracker.

  Original Description
  
  Apport popped up saying whoopsie had crashed (I assume during a previous 
crash report upload?)

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AssertionMessage: double free or corruption (fasttop)
  CasperMD5CheckResult: skip
  CrashCounter: 1
  Date: Fri Oct  9 08:08:56 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2019-11-18 (325 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  RelatedPackageVersions: apport-noui N/ASignal: 6SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption 
(fasttop)") at malloc.c:5389
   _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at 
malloc.c:4298
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: double free or corruption (fasttop)
  UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago)
  UserGroups: N/A
  separator:

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

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

[Touch-packages] [Bug 1849886] Re: lightdm does not work on eoan on raspberry pi 4

[Roman]

Using the GTK greeter and also tried Slick greeter, both show nothing -
a blank screen - and I would have to ctrl alt f1, get to a terminal
screen, put in a username and password there and then "startx" but the
f7 or wherever the lightdm goes, that does not work when switching to
it.

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

Title:
  lightdm does not work on eoan on raspberry pi 4

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  if you follow the directions on
  https://wiki.ubuntu.com/ARM/RaspberryPi

  sudo apt-get install xubuntu-desktop

  about 20% thru the installation it will ask which window manager you want 
(using dpkg-reconfigure).
  if you select lightdm, you will only get a blank greeter screen after you 
reboot.

  using sudo dpkg-reconfigure gdm3

  resets this to gdm3 and after a reboot, everything is fine.

  this was done on a clean armhf eoan install on a 4gb raspberry pi 4B.

  I have done the install several times.   This bug is repeatable.

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

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

[Touch-packages] [Bug 1906627] Please test proposed package

[Łukasz Zemczak]

Hello Rolf, or anyone else affected,

Accepted adcli into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/adcli/0.8.2-1ubuntu1.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, what testing has been
performed on the package 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.

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

Title:
  GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active
  Directory, causing recent adcli regression

Status in adcli package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 package in Ubuntu:
  Fix Released
Status in adcli source package in Bionic:
  Fix Committed
Status in cyrus-sasl2 source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  A recent release of adcli 0.8.2-1ubuntu1 to bionic-updates caused a
  regression for some users when attempting to join a Active Directory
  realm. adcli introduced a default behaviour change, moving from GSS-
  API to GSS-SPNEGO as the default channel encryption algorithm.

  adcli uses the GSS-SPNEGO implementation from libsasl2-modules-gssapi-
  mit, a part of cyrus-sasl2. The implementation seems to have some
  compatibility issues with particular configurations of Active
  Directory on recent Windows Server systems.

  Particularly, adcli sends a ldap query to the domain controller, which
  responds with a tcp ack, but never returns a ldap response. The
  connection just hangs at this point and no more traffic is sent.

  You can see it on the packet trace below:

  https://paste.ubuntu.com/p/WRnnRMGBPm/

  On Focal, where the implementation of GSS-SPNEGO is working, we see a
  full exchange, and adcli works as expected:

  https://paste.ubuntu.com/p/8668pJrr2m/

  The fix is to not assume use of confidentiality and integrity modes,
  and instead use the flags negotiated by GSS-API during the initial
  handshake, as required by Microsoft's implementation.

  [Testcase]

  You will need to set up a Windows Server 2019 system, install and
  configure Active Directory and enable LDAP extensions and configure
  LDAPS and import the AD SSL certificate to the Ubuntu client. Create
  some users in Active Directory.

  On the Ubuntu client, set up /etc/hosts with the hostname of the
  Windows Server machine, if your system isn't configured for AD DNS.

  From there, install adcli 0.8.2-1 from -release.

  $ sudo apt install adcli

  Set up a packet trace with tcpdump:

  $ sudo tcpdump -i any port '(389 or 3268 or 636 or 3269)'

  Next, join the AD realm using the normal GSS-API:

  # adcli join --verbose -U Administrator --domain WIN-
  SB6JAS7PH22.testing.local --domain-controller WIN-
  SB6JAS7PH22.testing.local --domain-realm TESTING.LOCAL

  You will be prompted for Administrator's passowrd.

  The output should look like the below:

  https://paste.ubuntu.com/p/NWHGQn746D/

  Next, enable -proposed, and install adcli 0.8.2-1ubuntu1 which caused the 
regression.
  Repeat the above steps. Now you should see the connection hang.

  https://paste.ubuntu.com/p/WRnnRMGBPm/

  Finally, install the fixed cyrus-sasl2 package from -proposed

  https://launchpad.net/~mruffell/+archive/ubuntu/lp1906627-test

  $ sudo apt-get update
  $ sudo apt install libsasl2-2 libsasl2-modules libsasl2-modules-db 
libsasl2-modules-gssapi-mit

  Repeat the steps. GSS-SPNEGO should be working as intended, and you
  should get output like below:

  https://paste.ubuntu.com/p/W5cJNGvCsx/

  [Where problems could occur]

  Since we are changing the implementation of GSS-SPNEGO, and cyrus-
  sasl2 is the library which provides it, we can potentially break any
  package which depends on libsasl2-modules-gssapi-mit for GSS-SPNEGO.

  $ apt rdepends libsasl2-modules-gssapi-mit
  libsasl2-modules-gssapi-mit
  Reverse Depends:
   |Suggests: ldap-utils
    Depends: adcli
    Conflicts: libsasl2-modules-gssapi-heimdal
   |Suggests: libsasl2-modules
  

[Touch-packages] [Bug 1829297] Re: ibus-ui-gtk3 crashed with SIGSEGV in tcache_get()

[Gunnar Hjalmarsson]

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

** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

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

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in tcache_get()

Status in ibus package in Ubuntu:
  New

Bug description:
  browser reading and listening to a yutube-stream, suddeny this bug
  message pops up

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-50.54-lowlatency 4.15.18
  Uname: Linux 4.15.0-50-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Wed May 15 23:10:18 2019
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2018-08-08 (280 days ago)
  InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  SegvAnalysis:
   Segfault happened at: 0x7f550a55f207 <__GI___libc_malloc+407>:   mov
(%rdx),%rdi
   PC (0x7f550a55f207) ok
   source "(%rdx)" (0x6e6f662f6374652f) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   tcache_get (tc_idx=2) at malloc.c:2943
   __GI___libc_malloc (bytes=48) at malloc.c:3050
   ?? () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
   FcStrSetAdd () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
   FcConfigParseAndLoad () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
  Title: ibus-ui-gtk3 crashed with SIGSEGV in tcache_get()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio avahi avahi-autoipd backup bin bluetooth cdrom colord 
crontab daemon dialout dip disk fax floppy games geoclue gnats input irc kmem 
lightdm list lp lpadmin mail man messagebus mlocate netdev news nopasswdlogin 
operator plugdev proxy pulse pulse-access root rtkit sambashare saned sasl 
scanner shadow src ssh ssl-cert staff sudo sys tape video

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

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

[Touch-packages] [Bug 1843958] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()

[Gunnar Hjalmarsson]

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

** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

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

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  I was adding a new user in system settings in the liveusb version of
  Ubuntu 19.10 alpha when the error message appeared bellow the other
  windows. I didn't notice anything crashing, AFAICR

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: ibus 1.5.19-4ubuntu2
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.415
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 13 22:16:39 2019
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fac162ecf3e :movl   
$0xfbad8004,0x20(%rsp)
   PC (0x7fac162ecf3e) ok
   source "$0xfbad8004" ok
   destination "0x20(%rsp)" (0x7ffdf646afd0) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ibus_bus_get_engines_by_names () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ?? ()
   ?? ()
   g_cclosure_marshal_VOID__STRINGv () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Touch-packages] [Bug 1870921] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()

[Gunnar Hjalmarsson]

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

** This bug is no longer a duplicate of bug 1870747
   ibus-ui-gtk3 crashed with SIGABRT in raise()
** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()

Status in ibus package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  5 14:44:58 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2020-04-05 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Touch-packages] [Bug 1872071] Re: ibus-x11 crashed with SIGSEGV in __GI___poll()

[Gunnar Hjalmarsson]

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

** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

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

Title:
  ibus-x11 crashed with SIGSEGV in __GI___poll()

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  This happened at start up after software updater requested a restart.I 
attached 
  unattended-upgrades.log
  unattended-upgrades-dpkg.log
  dpkg.log
  to show what packages were installed before the restart.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 07:16:32 2020
  ExecutablePath: /usr/libexec/ibus-x11
  InstallationDate: Installed on 2020-03-14 (26 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  ProcCmdline: /usr/libexec/ibus-x11 --kill-daemon
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f6b2b2919f6 <__run_exit_handlers+198>:  mov
0x10(%rax),%rdx
   PC (0x7f6b2b2919f6) ok
   source "0x10(%rax)" (0x1042f359537650) not located in a known VMA region 
(needed readable region)!
   destination "%rdx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   __GI___poll (fds=0x7f6af80067e0, nfds=3, timeout=1766) at 
../sysdeps/unix/sysv/linux/poll.c:29
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ibus_main () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ?? ()
  Title: ibus-x11 crashed with SIGSEGV in __GI___poll()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

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

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

[Touch-packages] [Bug 1872217] Re: ibus-x11 crashed with SIGSEGV in __GI___poll()

[Gunnar Hjalmarsson]

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

** This bug is no longer a duplicate of bug 1872071
   ibus-x11 crashed with SIGSEGV in __GI___poll()
** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

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

Title:
  ibus-x11 crashed with SIGSEGV in __GI___poll()

Status in ibus package in Ubuntu:
  New

Bug description:
  Problema constantes de Ibus

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Apr 11 14:10:03 2020
  ExecutablePath: /usr/libexec/ibus-x11
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/libexec/ibus-x11 --kill-daemon
  ProcEnviron:
   LANG=es_VE.UTF-8
   LANGUAGE=es_VE:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7fc97abc69f6 <__run_exit_handlers+198>:  mov
0x10(%rax),%rdx
   PC (0x7fc97abc69f6) ok
   source "0x10(%rax)" (0xb143e205ad8c0) not located in a known VMA region 
(needed readable region)!
   destination "%rdx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   __GI___poll (fds=0x55f25e1ac530, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ibus_main () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ?? ()
  Title: ibus-x11 crashed with SIGSEGV in __GI___poll()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

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

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

[Touch-packages] [Bug 1870747] Re: ibus-ui-gtk3 crashed with SIGABRT in raise()

[Gunnar Hjalmarsson]

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

** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in raise()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 13:27:38 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Touch-packages] [Bug 1907956] Re: ubiquity crash on whoopsie removal, Xubuntu 21.04 minimal install

[Brian Murray]

** Tags added: rls-hh-incoming

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

Title:
  ubiquity crash on whoopsie removal, Xubuntu 21.04 minimal install

Status in ubiquity package in Ubuntu:
  New
Status in whoopsie package in Ubuntu:
  New

Bug description:
  Xubuntu hirsute 20201213 minimal install crashed on whoopsie removal
  but finished installing. This is 1907951 with hopefully more crash
  information.

  Related logs identified:
  Dec 13 12:37:05 xubuntu ubiquity: Purging configuration files for whoopsie 
(0.2.73) ...
  Dec 13 12:37:05 xubuntu ubiquity: #015
  Dec 13 12:37:05 xubuntu ubiquity: Running in chroot, ignoring command 
'daemon-reload'#015
  Dec 13 12:37:05 xubuntu ubiquity: message repeated 2 times: [ Running in 
chroot, ignoring command 'daemon-reload'#015]
  Dec 13 12:37:05 xubuntu ubiquity: rm:
  Dec 13 12:37:05 xubuntu ubiquity: cannot remove 
'/var/lib/whoopsie/whoopsie-id'
  Dec 13 12:37:05 xubuntu ubiquity: : No such file or directory
  Dec 13 12:37:05 xubuntu ubiquity: #015
  Dec 13 12:37:05 xubuntu ubiquity: dpkg: error processing package whoopsie 
(--purge):
  Dec 13 12:37:05 xubuntu ubiquity: #015
  Dec 13 12:37:05 xubuntu ubiquity:  installed whoopsie package post-removal 
script subprocess returned error exit status 1
  Dec 13 12:37:05 xubuntu ubiquity: #015

  Looks like it's a bug in the postrm script:
  #! /bin/sh

  set -e

  #DEBHELPER#

  if [ "$1" = "purge" ]; then
  deluser --quiet --system whoopsie > /dev/null || true
  chmod g-s /var/crash >/dev/null 2>&1
  chgrp root /var/crash >/dev/null 2>&1
  rm /var/lib/whoopsie/whoopsie-id >/dev/null
  fi

  exit 0

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.3
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.456
  Date: Sun Dec 13 07:40:33 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Xubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201213)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  RebootRequiredPkgs:
   linux-image-5.8.0-25-generic
   linux-base
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1843195] Re: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()

[Gunnar Hjalmarsson]

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

** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

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

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  switch user not working.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: ibus 1.5.19-4ubuntu2
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  2 18:03:59 2019
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2019-08-27 (12 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   __vfprintf_internal (s=0x7f84e5081f5f, format=0x25 , ap=0x7ffe1ea7fc20, mode_flags=2) at 
vfprintf-internal.c:1289
   __vfprintf_internal (s=0x4, format=0x7ffe1ea7fc20 "\030", ap=0x2, 
mode_flags=) at ../libio/libioP.h:947
  Title: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Touch-packages] [Bug 1869484] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

[Gunnar Hjalmarsson]

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

** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  i don't know what's happened

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 27 23:00:56 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2018-08-07 (598 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Touch-packages] [Bug 1880371] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()

[Gunnar Hjalmarsson]

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

** This bug is no longer a duplicate of bug 1869484
   ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()
** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()

Status in ibus package in Ubuntu:
  New

Bug description:
  Happened after i logged in into the Ubuntu account.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-lowlatency 5.4.34
  Uname: Linux 5.4.0-31-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 24 02:05:33 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2020-02-08 (105 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to focal on 2020-04-20 (33 days ago)
  UserGroups: adm boinc cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742
  separator:

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

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

[Touch-packages] [Bug 1870843] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()

[Gunnar Hjalmarsson]

This crash type seems to not be present in 20.10, so let's consider it
fixed for now. Closing.

** Changed in: ibus (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()

Status in ibus package in Ubuntu:
  Fix Released

Bug description:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 13:03:51 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fee4f4e8f5b : orq
$0x0,(%rsp)
   PC (0x7fee4f4e8f5b) ok
   source "$0x0" ok
   destination "(%rsp)" (0x7ffe02368d40) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ibus_bus_get_engines_by_names () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ?? ()
   ?? ()
   g_cclosure_marshal_VOID__STRINGv () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Touch-packages] [Bug 1883355] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()

[Gunnar Hjalmarsson]

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

** This bug is no longer a duplicate of bug 1869484
   ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()
** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()

Status in ibus package in Ubuntu:
  New

Bug description:
  Happened on startup of pc.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  Uname: Linux 5.4.0-37-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 13 01:11:52 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2020-02-08 (125 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to focal on 2020-04-20 (53 days ago)
  UserGroups: adm boinc cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742
  separator:

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

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

[Touch-packages] [Bug 1906741] Re: Firefox sometimes causes garbled audio

[Olivier Tilloy]

I am tentatively adding a pulseaudio task.

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

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

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

Title:
  Firefox sometimes causes garbled audio

Status in firefox package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Opening certain applications/websites at the same time as Firefox
  causes the audio to become garbled.

  The audio sounds distorted with an echo.

  Certain actions are guaranteed to cause this, but it can also
  happening when only running instances of Firefox.

  I've been able to consistently cause this by launching Zoom from a link 
within Firefox. 
  This does not occur when using Chrome. 

  The only way to fix the issue is to shut down all audio-related
  programs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 83.0+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rdevans   55475 F pulseaudio
   /dev/snd/controlC0:  rdevans   55475 F pulseaudio
   /dev/snd/controlC3:  rdevans   55475 F pulseaudio
   /dev/snd/controlC1:  rdevans   55475 F pulseaudio
  BuildID: 20201112153044
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  3 16:55:36 2020
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-10-20 (1140 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 10.0.0.1 dev enp7s0 proto dhcp metric 100 
   10.0.0.0/24 dev enp7s0 proto kernel scope link src 10.0.0.7 metric 100 
   169.254.0.0/16 dev enp7s0 scope link metric 1000
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=83.0/20201112153044 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2020-11-12 (21 days ago)
  dmi.bios.date: 02/18/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: H67M
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd02/18/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M: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/firefox/+bug/1906741/+subscriptions

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

[Touch-packages] [Bug 1871625] Re: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()

[Gunnar Hjalmarsson]

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

** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

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

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()

Status in ibus package in Ubuntu:
  New

Bug description:
  There is a similar bug but it is on 19.10. I got this on 20.04 after I
  closed and reopened my session.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  8 14:46:26 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2018-04-07 (732 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fdcf7d9b9e1 <__vfprintf_internal+1>:nop
%edx
   PC (0x7fdcf7d9b9e1) ok
   source "%edx" ok
   Stack memory exhausted (SP below stack segment)
   SP (0x7fff10ee8da0) not located in a known VMA region (needed readable 
region)!
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop: __vfprintf_internal (s=0x7fff10ee9340, format=0x7fdcf818e0e9 
"%s\n", ap=0x7fff10eeba00, mode_flags=2) at vfprintf-internal.c:1289
  Title: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()
  UpgradeStatus: Upgraded to focal on 2020-04-04 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  separator:

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

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

[Touch-packages] [Bug 1879958] Re: /usr/libexec/ibus-ui-gtk3:11:__vfprintf_internal:buffered_vfprintf:IO_validate_vtable:__vfprintf_internal:___fprintf_chk

[Gunnar Hjalmarsson]

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

** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

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

Title:
  /usr/libexec/ibus-ui-
  
gtk3:11:__vfprintf_internal:buffered_vfprintf:IO_validate_vtable:__vfprintf_internal:___fprintf_chk

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
ibus.  This problem was most recently seen with package version 
1.5.22-2ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/3a012dedb557f699d32a1f5c166d0c6e0ecd2c70 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1878215] Re: ibus crash

[Gunnar Hjalmarsson]

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

** This bug is no longer a duplicate of bug 1879958
   
/usr/libexec/ibus-ui-gtk3:11:__vfprintf_internal:buffered_vfprintf:IO_validate_vtable:__vfprintf_internal:___fprintf_chk
** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

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

Title:
  ibus crash

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  ibus crash

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue May 12 16:59:54 2020
  InstallationDate: Installed on 2017-12-13 (880 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to focal on 2020-04-21 (21 days ago)

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

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

[Touch-packages] [Bug 1906600] Re: WiFi disconnects continually (goes "down" in NetworkManager)

[Allan Yaklin]

I have been running the mainline kernel since Saturday and have not seen
any of the network disconnect notifications or password prompts since. I
had been seeing several of them a day since the kernel update described
in my original comment, so it appears the problem has been fixed for me.

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Michael Heller]

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

Problem has been fixed for my setup:

- Kernel: 5.4.0-56-generic
- OS: Xubuntu 20.04.01 LTS
- Machine: HP-ZBook-14u-G6
- Headset: FreeVoice Space Stereo

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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

[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Michael Heller]

Problem has been fixed for my setup:

- Kernel: 5.4.0-56-generic
- OS: Xubuntu 20.04.01 LTS
- Machine: HP-ZBook-14u-G6
- Headset: FreeVoice Space Stereo

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1908063] Re: gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal error when connecting to QEMU aarch64 gdbstub

[Peter Maydell]

It looks like the reason QEMU's test suite passed was that the older
Ubuntu gdb didn't have a fix for LP:1901026 (support remote connection
over UNIX domain socket), so the test suite would simply skip the
offending test and never get as far as falling over the assertion
failure. After pulling various old binaries out of my backups to test
I'm forced to conclude that I was simply misremembering by-hand use of
the gdbstub working and I must not have used it as recently as I'd
thought. So this is a bug, but not a regression.

A possible set of commits for a cherry-picked fix would be
c8ec2f334c3751c28d5f and 4ef0bef68cfc777e59156fce1 (which together
remove the hard-coded limit on register size and thus also the
assertion), but the former is not a completely trivial patch. I haven't
attempted such a cherry-pick to see if it works.

A workaround is to tell QEMU not to emulate SVE (eg with "-cpu
max,sve=off" -- it is the large SVE vector registers which trigger the
problem.


** Summary changed:

- gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal error 
when connecting to QEMU aarch64 gdbstub
+ gdb-multiarch 8.1.1-0ubuntu1: assertion failure or internal error when 
connecting to QEMU aarch64 gdbstub

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

Title:
  gdb-multiarch 8.1.1-0ubuntu1: assertion failure or internal error when
  connecting to QEMU aarch64 gdbstub

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  New

Bug description:
  This bug is a regression introduced in 8.1.1-0ubuntu1 for Bionic --
  the previous 8.1-0ubuntu3.2 gdb works fine with QEMU's gdbstub.

  Reproduce:
  Get the sources for QEMU 5.2.0, and build the aarch64-linux-user target. (It 
looks like Bionic's QEMU is old enough that it doesn't provoke this gdb error.)

  Run
   qemu-aarch64 -g 1234 path/to/some/aarch64/binary

  In another terminal, start gdb-multiarch. At the (gdb) prompt, type
  "target remote :1234". GDB will dump core:

  (gdb) target remote :1234
  Remote debugging using :1234
  Recursive internal problem.
  Aborted (core dumped)

  You can see a variant of this also in the QEMU test suite with "make
  -C your-qemu-build-dir check-tcg", where the error message includes an
  assertion failure:

  [...]

  timeout 60  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/guest-debug/run-test.py --gdb 
/usr/bin/gdb-multiarch --qemu 
/home/petmay01/linaro/qemu-from-laptop/qemu/build/aarch64-linux/qemu-aarch64 
--qargs "" --bin sha1 --test 
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/gdbstub/sha1.py 
>  run-gdbstub-sha1.out
  /build/gdb-veKdC1/gdb-8.1.1/gdb/regcache.c:122: internal-error: void* 
init_regcache_descr(gdbarch*): Assertion `MAX_REGISTER_SIZE >= 
descr->sizeof_register[i]' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.

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

  Aborted (core dumped)
  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/Makefile.target:51:
 recipe for target 'run-gdbstub-sha1' failed

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

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

[Touch-packages] [Bug 1907789] Re: 2.35.50 breaks ld -no-pie

[Christian Ehrhardt ]

FYI - fix submitted to qemu upstream and for now added to the qemu package. If 
upstream eventually prefers a different solution I can refresh it accordingly.
=> https://lists.gnu.org/archive/html/qemu-devel/2020-12/msg03684.html

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

Title:
  2.35.50 breaks ld -no-pie

Status in binutils:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  In Progress

Bug description:
  The qemu build reaches (and always did) a step where it tries to link some
  img files. That is done via the command:
$ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s 
-o multiboot.img multiboot.o

  Recently that still works in Debian [1] but no more in Ubuntu [2].

  I think that the new binutils broke me.
  In hirsute proposed those are at 2.35.50.20201210-0ubuntu1

  The issue is easily isolated, and by copying the two files around I
  found the following:

  Hirsute: 2.35.50.20201210-0ubuntu1 - bad
  Hirsute: 2.35.50.20201207-0ubuntu1 - bad
  Sid: 2.35.1-4  - good
  Groovy:  2.35.1-1ubuntu1   - good
  Focal:   2.34-6ubuntu1 - good

  I'll attach these two files to the bug, just thro them into a directory and
  run the command:
   $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o

  If that is an intentional change please guide how this is now supposed
  to work.

  [1]: 
https://buildd.debian.org/status/fetch.php?pkg=qemu=amd64=1%3A5.2%2Bdfsg-2=1607598738=1
  [2]: 
https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD

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

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

[Touch-packages] [Bug 1846334] Re: cupsd assert failure: free(): invalid pointer

[Till Kamppeter]

Hirsute has now the newest CUPS (2.3.3op1) with all fixes and patches.
This should also include the patch mentioned.

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

Title:
  cupsd assert failure: free(): invalid pointer

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Just running in the background, no user action (printing)

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-daemon 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AssertionMessage: free(): invalid pointer
  Date: Tue Oct  1 19:41:35 2019
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2019-02-09 (234 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Lpstat:
   device for HP_LaserJet_CM1415fn_44A808_: 
implicitclass://HP_LaserJet_CM1415fn_44A808_/
   device for Samsung_C48x_Series_SEC84251900EE44_: 
implicitclass://Samsung_C48x_Series_SEC84251900EE44_/
  MachineType: Dell Inc. Latitude E6530
  Papersize: letter
  PpdFiles:
   HP_LaserJet_CM1415fn_44A808_: LaserJet CM1415fn - IPP Everywhere
   Samsung_C48x_Series_SEC84251900EE44_: C48x Series - IPP Everywhere
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic 
root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic 
root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f923ecb83a5 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f923ecb652a "free(): invalid pointer") at 
malloc.c:5332
   _int_free (av=, p=, have_lock=0) at 
malloc.c:4173
   ?? () from /lib/x86_64-linux-gnu/libcups.so.2
   ippDelete () from /lib/x86_64-linux-gnu/libcups.so.2
  Title: cupsd assert failure: free(): invalid pointer
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A22
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.sku: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  separator:

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

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

[Touch-packages] [Bug 1907789] Re: 2.35.50 breaks ld -no-pie

[Bug Watch Updater]

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

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


On 2020-12-11T10:05:19+00:00 Matthias Klose wrote:

works with the 2.35 branch, fails with the trunk:

$ ld.gold -pie
ld.gold: fatal error: no input files

$ ld.gold -no-pie
ld.gold: fatal error: no input files

$ ld.bfd -pie
ld.bfd: no input files

$ ld.bfd -no-pie
ld.bfd: Error: unable to disambiguate: -no-pie (did you mean --no-pie ?)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/comments/3


On 2020-12-11T13:13:48+00:00 Hjl-tools wrote:

It is caused by

commit 983d925db6a09ac90f6bed90be16eb69267b58e0
Author: Nick Clifton 
Date:   Mon Oct 5 13:53:59 2020 +0100

Update the BFD linker so that it deprecates grouped short options.

* lexsup.c (parse_args): Generate an error or warning message when
multiple short options are used together.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/comments/4


On 2020-12-11T13:18:48+00:00 Hjl-tools wrote:

$ valgrind ./ld/ld-new -no-pie
==290969== Memcheck, a memory error detector
==290969== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==290969== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info
==290969== Command: ./ld/ld-new -no-pie
==290969== 
==290969== Conditional jump or move depends on uninitialised value(s)
==290969==at 0x409A96: parse_args (lexsup.c:749)
==290969==by 0x403DC6: main (ldmain.c:370)
==290969== 
./ld/ld-new: Error: unable to disambiguate: -no-pie (did you mean --no-pie ?)
==290969== 
==290969== HEAP SUMMARY:
==290969== in use at exit: 21,161 bytes in 10 blocks
==290969==   total heap usage: 72 allocs, 62 frees, 43,232 bytes allocated
==290969== 
==290969== LEAK SUMMARY:
==290969==definitely lost: 0 bytes in 0 blocks
==290969==indirectly lost: 0 bytes in 0 blocks
==290969==  possibly lost: 0 bytes in 0 blocks
==290969==still reachable: 21,161 bytes in 10 blocks
==290969== suppressed: 0 bytes in 0 blocks
==290969== Rerun with --leak-check=full to see details of leaked memory
==290969== 
==290969== Use --track-origins=yes to see where uninitialised values come from
==290969== For lists of detected and suppressed errors, rerun with: -s
==290969== ERROR SUMMARY: 2 errors from 1 contexts (suppressed: 0 from 0)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/comments/5


On 2020-12-11T13:48:11+00:00 Hjl-tools wrote:

longind may not be set by getopt_long_only:

diff --git a/ld/lexsup.c b/ld/lexsup.c
index 0d10bc6fba..60e3f7d8b5 100644
--- a/ld/lexsup.c
+++ b/ld/lexsup.c
@@ -735,6 +735,7 @@ parse_args (unsigned argc, char **argv)
   /* getopt_long_only is like getopt_long, but '-' as well as '--'
can indicate a long option.  */
   opterr = 0;
+  longind = -1;
   last_optind = optind;
   optc = getopt_long_only (argc, argv, shortopts, longopts, );
   if (optc == '?')

Reply at:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/comments/6


On 2020-12-11T13:55:31+00:00 Hjl-tools wrote:

   LONGIND returns the index in LONGOPT of the long-named option found.
   It is only valid when a long-named option has been found by the most
   recent call.

Since the long option isn't found, LONGIND is undefined.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/comments/7


On 2020-12-11T15:26:17+00:00 Nickc wrote:


Not to be facetious but did we ever really support -no-pie ?

It does not appear to be documented, and it looks like it is treated
internally as two options: -n and -o-pie.

I have a patch that fixes the uninitialised memory problem detected
by valgrind, but I am wondering whether it is better to add explicit
support for -no-pie as an option to turn off -pie, or else keep the
linker's error message, and maybe add a --no-pie option instead.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/comments/8


On 2020-12-11T15:44:44+00:00 Hjl-tools wrote:

(In reply to Nick Clifton from comment #5)
> Not to be facetious but did we ever really support -no-pie ?
>

ld/testsuite/config/default.exp: set NOPIE_LDFLAGS "-no-pie"

Reply at:

[Touch-packages] [Bug 1902244] Re: Backport packages for 20.04.2 HWE stack

[Timo Aaltonen]

** Summary changed:

- Backport packages for 20.04.1 HWE stack
+ Backport packages for 20.04.2 HWE stack

** Description changed:

  [Impact]
  
- These are needed for 20.04.1 images.
+ These are needed for 20.04.2 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-11: a new package, no regression potential on it's own
  
  libclc: just a rebuild against the new llvm
  
  libglvnd: mostly just EGL headers sync from Khronos, needed by mesa
  
  mesa: a new major release, but we'll pull the final stable release of
  20.2.x series, so there shouldn't be any regressions left at that point
  
  xserver: a new point-release
  
  xorg drivers: modest updates, if any

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

Title:
  Backport packages for 20.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libglvnd package in Ubuntu:
  Invalid
Status in llvm-toolchain-11 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in libglvnd source package in Focal:
  Fix Committed
Status in llvm-toolchain-11 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Confirmed

Bug description:
  [Impact]

  These are needed for 20.04.2 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-11: a new package, no regression potential on it's own

  libclc: just a rebuild against the new llvm

  libglvnd: mostly just EGL headers sync from Khronos, needed by mesa

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

  xserver: a new point-release

  xorg drivers: modest updates, if any

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

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

[Touch-packages] [Bug 1903300] Re: systemd-networkd silently fails to set vxlan multicast group

[Dan Streetman]

** Description changed:

+ [impact]
+ 
+ setting VXLAN.Group does not correctly configure multicast group
+ 
+ [test case]
+ 
+ taken from upstream bug, example networkd config:
+ 
+ [NetDev]
+ Kind=vxlan
+ Name=myvx
+ 
+ [VXLAN]
+ VNI=1
+ Group=ff02::42:1
+ DestinationPort=8472
+ 
+ After restarting systemd-networkd the VXLAN device is created, but the
+ group address is not assigned. Use ip -d link show myvx and networkctl
+ show myvx to verify.
+ 
+ [regression potential]
+ 
+ any regression would likely cause problems only with VXLAN netdevs
+ created by networkd.
+ 
+ [scope]
+ 
+ this is needed only for f.
+ 
+ this was introduced by upstream commit 83cb24ac20b which was first in
+ v243, so this bug does not exist in b and earlier.
+ 
+ this was fixed by upstream commit
+ 7c9b26900cc33daf080627daf5904de74c1ef267 (and two following commits)
+ which were first included in v246, so this is already fixed in g and
+ later.
+ 
+ [original description]
+ 
+ 
  Fixed upstream, please include [1].
  
  Thank you.
- 
  
  [1] https://github.com/systemd/systemd/pull/15397
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Nov  6 14:16:19 2020
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=C.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=C.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=97786d27-c04a-4592-a087-f19a689468a9 ro console=tty1 console=ttyS0
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-08-27 (70 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-5.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-5.1:cvnQEMU:ct1:cvrpc-q35-5.1:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-5.1
  dmi.sys.vendor: QEMU

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

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

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

** Changed in: systemd (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu Focal)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

Title:
  systemd-networkd silently fails to set vxlan multicast group

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress

Bug description:
  [impact]

  setting VXLAN.Group does not correctly configure multicast group

  [test case]

  taken from upstream bug, example networkd config:

  [NetDev]
  Kind=vxlan
  Name=myvx

  [VXLAN]
  VNI=1
  Group=ff02::42:1
  DestinationPort=8472

  After restarting systemd-networkd the VXLAN device is created, but the
  group address is not assigned. Use ip -d link show myvx and networkctl
  show myvx to verify.

  [regression potential]

  any regression would likely cause problems only with VXLAN netdevs
  created by networkd.

  [scope]

  this is needed only for f.

  this was introduced by upstream commit 83cb24ac20b which was first in
  v243, so this bug does not exist in b and earlier.

  this was fixed by upstream commit
  7c9b26900cc33daf080627daf5904de74c1ef267 (and two following commits)
  which were first included in v246, so this is already fixed in g and
  later.

  [original description]

  
  Fixed upstream, please include [1].

  Thank you.

  [1] https://github.com/systemd/systemd/pull/15397

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Nov  6 14:16:19 2020
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=97786d27-c04a-4592-a087-f19a689468a9 ro console=tty1 console=ttyS0
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-08-27 (70 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org
  dmi.chassis.type: 1
  

[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Georgi Petkov]

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

Correction: 
Kernel: 5.4.0-58-generic

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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

[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Georgi Petkov]

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

Problem has been fixed for my setup:

- Kernel: 5.4.0-55-generic
- OS: Xubuntu 20.04.01 LTS
- Machine: Lenovo ThinkPad T14
- Headset: Audio-Technica ATH-S200BT

So far I haven't been able to hear how they sound with this profile and
it sounds awful. So now since I did, I do not recommend using it for
good quality calls.

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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

[Touch-packages] [Bug 1908063] Re: gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal error when connecting to QEMU aarch64 gdbstub

[Peter Maydell]

Further testing with the old gdb-8.1-0ubuntu3 package shows that this
isn't a regression since then, as that version fails too. I must have
been misled by the apt history.log somehow; sorry for the confusion
there.

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

Title:
  gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal
  error when connecting to QEMU aarch64 gdbstub

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  New

Bug description:
  This bug is a regression introduced in 8.1.1-0ubuntu1 for Bionic --
  the previous 8.1-0ubuntu3.2 gdb works fine with QEMU's gdbstub.

  Reproduce:
  Get the sources for QEMU 5.2.0, and build the aarch64-linux-user target. (It 
looks like Bionic's QEMU is old enough that it doesn't provoke this gdb error.)

  Run
   qemu-aarch64 -g 1234 path/to/some/aarch64/binary

  In another terminal, start gdb-multiarch. At the (gdb) prompt, type
  "target remote :1234". GDB will dump core:

  (gdb) target remote :1234
  Remote debugging using :1234
  Recursive internal problem.
  Aborted (core dumped)

  You can see a variant of this also in the QEMU test suite with "make
  -C your-qemu-build-dir check-tcg", where the error message includes an
  assertion failure:

  [...]

  timeout 60  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/guest-debug/run-test.py --gdb 
/usr/bin/gdb-multiarch --qemu 
/home/petmay01/linaro/qemu-from-laptop/qemu/build/aarch64-linux/qemu-aarch64 
--qargs "" --bin sha1 --test 
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/gdbstub/sha1.py 
>  run-gdbstub-sha1.out
  /build/gdb-veKdC1/gdb-8.1.1/gdb/regcache.c:122: internal-error: void* 
init_regcache_descr(gdbarch*): Assertion `MAX_REGISTER_SIZE >= 
descr->sizeof_register[i]' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.

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

  Aborted (core dumped)
  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/Makefile.target:51:
 recipe for target 'run-gdbstub-sha1' failed

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

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

[Touch-packages] [Bug 1908071] [NEW] The video card driver is not working well

[Serhiy Melnyk]

Public bug reported:

1)lsb_release -rd
Description:Ubuntu 20.10
Release:20.10

2)apt-cache policy xorg
xorg:
  Installed: 1:7.7+19ubuntu15
  Candidate: 1:7.7+19ubuntu15
  Version table:
 *** 1:7.7+19ubuntu15 500
500 http://ua.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
100 /var/lib/dpkg/status

3)Normal work

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
Uname: Linux 5.8.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.2
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Mon Dec 14 15:49:46 2020
DistUpgraded: Fresh install
DistroCodename: groovy
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company UHD Graphics [103c:86a0]
InstallationDate: Installed on 2020-12-13 (1 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 413c:8505 Dell Computer Corp. Dell Universal Receiver
 Bus 001 Device 002: ID 04ca:7095 Lite-On Technology Corp. HP HD Camera
 Bus 001 Device 004: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP ProBook 450 G7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic 
root=UUID=227ec1da-8070-4974-9577-9fe4a7428d90 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/19/2020
dmi.bios.release: 6.1
dmi.bios.vendor: HP
dmi.bios.version: S71 Ver. 01.06.01
dmi.board.name: 86A0
dmi.board.vendor: HP
dmi.board.version: KBC Version 02.2D.00
dmi.chassis.asset.tag: 5CD024GVZP
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 2.45
dmi.modalias: 
dmi:bvnHP:bvrS71Ver.01.06.01:bd10/19/2020:br6.1:efr2.45:svnHP:pnHPProBook450G7:pvr:rvnHP:rn86A0:rvrKBCVersion02.2D.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ProBook
dmi.product.name: HP ProBook 450 G7
dmi.product.sku: 6YY26AV
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.103+git2012121830.d034db~oibaf~g
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0~git2012130730.6a34a6~oibaf~g
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug groovy third-party-packages 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/1908071

Title:
  The video card driver is not working well

Status in xorg package in Ubuntu:
  New

Bug description:
  1)lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  2)apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu15
Candidate: 1:7.7+19ubuntu15
Version table:
   *** 1:7.7+19ubuntu15 500
  500 http://ua.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

  3)Normal work

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon Dec 14 15:49:46 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics [103c:86a0]
  InstallationDate: Installed on 2020-12-13 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 413c:8505 Dell Computer Corp. Dell Universal Receiver
   Bus 001 Device 002: ID 04ca:7095 Lite-On Technology Corp. HP HD Camera
   Bus 001 Device 004: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProBook 450 G7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic 
root=UUID=227ec1da-8070-4974-9577-9fe4a7428d90 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/19/2020
  dmi.bios.release: 6.1
  dmi.bios.vendor: HP
  dmi.bios.version: S71 Ver. 

[Touch-packages] [Bug 1908067] [NEW] systemd-fsckd test fails on groovy checking plymouth-start isactive

[Dan Streetman]

Public bug reported:

[impact]

systemd-fsckd test fails on groovy because plymouth-start service is
active

[test case]

check autopkgtest logs of systemd-fsckd test case on groovy

[regression potential]

incorrectly passed, or failed, systemd-fsckd test

[scope]

this is needed only for groovy.

the plymouth-start.service did not include RemainAfterExit=true before groovy, 
so the service is expected to be inactive when checked by the test before 
groovy. this is already fixed in hirsute:
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c46eda821e97df5595a4cdc5f5c41a9b49a51745

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: systemd (Ubuntu Groovy)
 Importance: Low
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

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

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

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

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

** Changed in: systemd (Ubuntu Groovy)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Description changed:

  [impact]
  
  systemd-fsckd test fails on groovy because plymouth-start service is
  active
  
  [test case]
  
  check autopkgtest logs of systemd-fsckd test case on groovy
  
  [regression potential]
  
  incorrectly passed, or failed, systemd-fsckd test
  
  [scope]
  
  this is needed only for groovy.
  
- the plymouth-start.service did not include RemainAfterExit=true before
- groovy, so the service is expected to be inactive when checked by the
- test before groovy. this is already fixed in hirsute, and this is just a
- backport of that fix to groovy.
+ the plymouth-start.service did not include RemainAfterExit=true before 
groovy, so the service is expected to be inactive when checked by the test 
before groovy. this is already fixed in hirsute:
+ 
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c46eda821e97df5595a4cdc5f5c41a9b49a51745

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

Title:
  systemd-fsckd test fails on groovy checking plymouth-start isactive

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Groovy:
  In Progress

Bug description:
  [impact]

  systemd-fsckd test fails on groovy because plymouth-start service is
  active

  [test case]

  check autopkgtest logs of systemd-fsckd test case on groovy

  [regression potential]

  incorrectly passed, or failed, systemd-fsckd test

  [scope]

  this is needed only for groovy.

  the plymouth-start.service did not include RemainAfterExit=true before 
groovy, so the service is expected to be inactive when checked by the test 
before groovy. this is already fixed in hirsute:
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c46eda821e97df5595a4cdc5f5c41a9b49a51745

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

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

[Touch-packages] [Bug 1907789] Re: 2.35.50 breaks ld -no-pie

[Christian Ehrhardt ]

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

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

** Changed in: qemu (Ubuntu)
 Assignee: (unassigned) => Christian Ehrhardt  (paelzer)

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

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

Title:
  2.35.50 breaks ld -no-pie

Status in binutils:
  Unknown
Status in binutils package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  In Progress

Bug description:
  The qemu build reaches (and always did) a step where it tries to link some
  img files. That is done via the command:
$ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s 
-o multiboot.img multiboot.o

  Recently that still works in Debian [1] but no more in Ubuntu [2].

  I think that the new binutils broke me.
  In hirsute proposed those are at 2.35.50.20201210-0ubuntu1

  The issue is easily isolated, and by copying the two files around I
  found the following:

  Hirsute: 2.35.50.20201210-0ubuntu1 - bad
  Hirsute: 2.35.50.20201207-0ubuntu1 - bad
  Sid: 2.35.1-4  - good
  Groovy:  2.35.1-1ubuntu1   - good
  Focal:   2.34-6ubuntu1 - good

  I'll attach these two files to the bug, just thro them into a directory and
  run the command:
   $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o

  If that is an intentional change please guide how this is now supposed
  to work.

  [1]: 
https://buildd.debian.org/status/fetch.php?pkg=qemu=amd64=1%3A5.2%2Bdfsg-2=1607598738=1
  [2]: 
https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD

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

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

[Touch-packages] [Bug 1908064] [NEW] [Multiple bluetooth speakers, playback] Stuttering sound

[abcdef]

Public bug reported:

Constant stuttering sound, stuttering at maybe 10 times/second. More
than one speaker with the same symptoms.

Speakers work in Windows 10 / macOS 10.14+ running on same hardware.

Same speakers work on Ubuntu Mate 18.04 32 bit running on different
hardware.

Remote control commands work (play/pause button on speakers).

Initial pairing and connection requires from 2 to about 10 retries. All
tested within 1 m distance.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.2-1ubuntu2.1
ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
Uname: Linux 5.8.0-33-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu50.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  username3486 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 14 13:49:26 2020
InstallationDate: Installed on 2020-10-30 (45 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: Crossbeat
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [Crossbeat, playback] Underruns, dropouts or crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/10/2020
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 264.0.0.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-2E6FAB96566FE58C
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir5,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-2E6FAB96566FE58C
dmi.modalias: 
dmi:bvnAppleInc.:bvr264.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C:
dmi.product.family: MacBook Air
dmi.product.name: MacBookAir5,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


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

** Description changed:

  Constant stuttering sound, stuttering at maybe 10 times/second. More
  than one speaker with the same symptoms.
  
  Speakers work in Windows 10 / macOS 10.14+ running on same hardware.
  
  Same speakers work on Ubuntu Mate 18.04 32 bit running on different
  hardware.
  
  Remote control commands work (play/pause button on speakers).
  
  Initial pairing and connection requires from 2 to about 10 retries. All
  tested within 1 m distance.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  andreas3486 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  username3486 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 14 13:49:26 2020
  InstallationDate: Installed on 2020-10-30 (45 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=sv_SE.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=sv_SE.UTF-8
+  SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: Crossbeat
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Crossbeat, playback] Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 264.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2E6FAB96566FE58C
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2E6FAB96566FE58C
  dmi.modalias: 
dmi:bvnAppleInc.:bvr264.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C:
  dmi.product.family: MacBook Air
  dmi.product.name: MacBookAir5,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

Title:
  [Multiple bluetooth speakers, playback] Stuttering sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Constant stuttering sound, stuttering at maybe 10 times/second. More
  

[Touch-packages] [Bug 1907789] Re: 2.35.50 breaks ld -no-pie

[Matthias Klose]

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

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

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

Title:
  2.35.50 breaks ld -no-pie

Status in binutils:
  Unknown
Status in binutils package in Ubuntu:
  Fix Committed

Bug description:
  The qemu build reaches (and always did) a step where it tries to link some
  img files. That is done via the command:
$ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s 
-o multiboot.img multiboot.o

  Recently that still works in Debian [1] but no more in Ubuntu [2].

  I think that the new binutils broke me.
  In hirsute proposed those are at 2.35.50.20201210-0ubuntu1

  The issue is easily isolated, and by copying the two files around I
  found the following:

  Hirsute: 2.35.50.20201210-0ubuntu1 - bad
  Hirsute: 2.35.50.20201207-0ubuntu1 - bad
  Sid: 2.35.1-4  - good
  Groovy:  2.35.1-1ubuntu1   - good
  Focal:   2.34-6ubuntu1 - good

  I'll attach these two files to the bug, just thro them into a directory and
  run the command:
   $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o

  If that is an intentional change please guide how this is now supposed
  to work.

  [1]: 
https://buildd.debian.org/status/fetch.php?pkg=qemu=amd64=1%3A5.2%2Bdfsg-2=1607598738=1
  [2]: 
https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD

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

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

[Touch-packages] [Bug 1900008] Re: Sessions of screen does not keep running in background

[Gustavo A . Díaz]

Hi,

Sure, I will let you know here the results. Also, I will try to modify
login.conf as suggested in the link before doing any test. But anyways,
is this was not affected in my other upgrades installations, I don't
think that is the problem here, but won't hurt me trying.

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

Title:
  Sessions of screen does not keep running in background

Status in screen package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  In a new fresh installed 20.04, when I use screen command and close
  the terminal (not closing screen sesion), then I can't recover it with
  screen -x, since does not exist. I can only recover screen sesion if
  the original terminal running screen is not being closed.

  For some reason, this is closing screen session of that user:

  Oct 15 13:32:45 pc-caja2 systemd[1]: session-66.scope: Succeeded.
  Oct 15 13:32:45 pc-caja2 systemd[1]: Stopped Session 66 of user usuario.

  This does not happen in an upgraded system from 18.04 to 20.04.

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

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

[Touch-packages] [Bug 1908063] Re: gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal error when connecting to QEMU aarch64 gdbstub

[Matthias Klose]

** Also affects: gdb (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 gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1908063

Title:
  gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal
  error when connecting to QEMU aarch64 gdbstub

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  New

Bug description:
  This bug is a regression introduced in 8.1.1-0ubuntu1 for Bionic --
  the previous 8.1-0ubuntu3.2 gdb works fine with QEMU's gdbstub.

  Reproduce:
  Get the sources for QEMU 5.2.0, and build the aarch64-linux-user target. (It 
looks like Bionic's QEMU is old enough that it doesn't provoke this gdb error.)

  Run
   qemu-aarch64 -g 1234 path/to/some/aarch64/binary

  In another terminal, start gdb-multiarch. At the (gdb) prompt, type
  "target remote :1234". GDB will dump core:

  (gdb) target remote :1234
  Remote debugging using :1234
  Recursive internal problem.
  Aborted (core dumped)

  You can see a variant of this also in the QEMU test suite with "make
  -C your-qemu-build-dir check-tcg", where the error message includes an
  assertion failure:

  [...]

  timeout 60  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/guest-debug/run-test.py --gdb 
/usr/bin/gdb-multiarch --qemu 
/home/petmay01/linaro/qemu-from-laptop/qemu/build/aarch64-linux/qemu-aarch64 
--qargs "" --bin sha1 --test 
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/gdbstub/sha1.py 
>  run-gdbstub-sha1.out
  /build/gdb-veKdC1/gdb-8.1.1/gdb/regcache.c:122: internal-error: void* 
init_regcache_descr(gdbarch*): Assertion `MAX_REGISTER_SIZE >= 
descr->sizeof_register[i]' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.

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

  Aborted (core dumped)
  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/Makefile.target:51:
 recipe for target 'run-gdbstub-sha1' failed

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

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

[Touch-packages] [Bug 1908063] [NEW] gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal error when connecting to QEMU aarch64 gdbstub

[Peter Maydell]

Public bug reported:

This bug is a regression introduced in 8.1.1-0ubuntu1 for Bionic -- the
previous 8.1-0ubuntu3.2 gdb works fine with QEMU's gdbstub.

Reproduce:
Get the sources for QEMU 5.2.0, and build the aarch64-linux-user target. (It 
looks like Bionic's QEMU is old enough that it doesn't provoke this gdb error.)

Run
 qemu-aarch64 -g 1234 path/to/some/aarch64/binary

In another terminal, start gdb-multiarch. At the (gdb) prompt, type
"target remote :1234". GDB will dump core:

(gdb) target remote :1234
Remote debugging using :1234
Recursive internal problem.
Aborted (core dumped)

You can see a variant of this also in the QEMU test suite with "make -C
your-qemu-build-dir check-tcg", where the error message includes an
assertion failure:

[...]

timeout 60  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/guest-debug/run-test.py --gdb 
/usr/bin/gdb-multiarch --qemu 
/home/petmay01/linaro/qemu-from-laptop/qemu/build/aarch64-linux/qemu-aarch64 
--qargs "" --bin sha1 --test 
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/gdbstub/sha1.py 
>  run-gdbstub-sha1.out
/build/gdb-veKdC1/gdb-8.1.1/gdb/regcache.c:122: internal-error: void* 
init_regcache_descr(gdbarch*): Assertion `MAX_REGISTER_SIZE >= 
descr->sizeof_register[i]' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

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

Aborted (core dumped)
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/Makefile.target:51:
 recipe for target 'run-gdbstub-sha1' failed

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

** Affects: gdb (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 gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1908063

Title:
  gdb-multiarch 8.1.1-0ubuntu1 regression: assertion failure or internal
  error when connecting to QEMU aarch64 gdbstub

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  New

Bug description:
  This bug is a regression introduced in 8.1.1-0ubuntu1 for Bionic --
  the previous 8.1-0ubuntu3.2 gdb works fine with QEMU's gdbstub.

  Reproduce:
  Get the sources for QEMU 5.2.0, and build the aarch64-linux-user target. (It 
looks like Bionic's QEMU is old enough that it doesn't provoke this gdb error.)

  Run
   qemu-aarch64 -g 1234 path/to/some/aarch64/binary

  In another terminal, start gdb-multiarch. At the (gdb) prompt, type
  "target remote :1234". GDB will dump core:

  (gdb) target remote :1234
  Remote debugging using :1234
  Recursive internal problem.
  Aborted (core dumped)

  You can see a variant of this also in the QEMU test suite with "make
  -C your-qemu-build-dir check-tcg", where the error message includes an
  assertion failure:

  [...]

  timeout 60  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/guest-debug/run-test.py --gdb 
/usr/bin/gdb-multiarch --qemu 
/home/petmay01/linaro/qemu-from-laptop/qemu/build/aarch64-linux/qemu-aarch64 
--qargs "" --bin sha1 --test 
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/gdbstub/sha1.py 
>  run-gdbstub-sha1.out
  /build/gdb-veKdC1/gdb-8.1.1/gdb/regcache.c:122: internal-error: void* 
init_regcache_descr(gdbarch*): Assertion `MAX_REGISTER_SIZE >= 
descr->sizeof_register[i]' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.

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

  Aborted (core dumped)
  
/home/petmay01/linaro/qemu-from-laptop/qemu/tests/tcg/multiarch/Makefile.target:51:
 recipe for target 'run-gdbstub-sha1' failed

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

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

[Touch-packages] [Bug 1906986] Re: defective ir-keytable udev rule → custom keytable does not get loaded

[Tore Anderson]

Probably. My (fully updated) 20.04.1 LTS box is still at version
1.18.0-2build1, though.

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

Title:
  defective ir-keytable udev rule → custom keytable does not get loaded

Status in v4l-utils package in Ubuntu:
  Incomplete

Bug description:
  ir-keytable v1.18.0-2build1 ships /lib/udev/rules.d/60-ir-
  keytable.rules containing the following rule:

  ACTION=="add", SUBSYSTEM=="rc", RUN+="/usr/bin/ir-keytable -a
  /etc/rc_maps.cfg -s $name"

  After upgrading to Focal, this does not get triggered at boot, nor if
  I (re)insert my receiver when the system is running. Therefore, the
  custom keytable does not get loaded.

  This is the udev events that occur when I insert the receiver:

  $ sudo udevadm monitor
  monitor will print the received events for:
  UDEV - the event which udev sends out after rule processing
  KERNEL - the kernel uevent

  KERNEL[1195.829011] add  /devices/pci:00/:00:14.0/usb1/1-3 (usb)
  KERNEL[1195.834989] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 (usb)
  KERNEL[1195.874055] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/lirc0 (lirc)
  KERNEL[1195.875019] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11 (input)
  KERNEL[1195.875183] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11/event3 (input)
  KERNEL[1196.134164] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/wakeup/wakeup21 (wakeup)
  KERNEL[1196.134448] bind 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 (usb)
  KERNEL[1196.134704] bind /devices/pci:00/:00:14.0/usb1/1-3 (usb)
  UDEV  [1196.158923] add  /devices/pci:00/:00:14.0/usb1/1-3 (usb)
  UDEV  [1196.174559] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 (usb)
  UDEV  [1196.194750] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/lirc0 (lirc)
  UDEV  [1196.196268] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11 (input)
  UDEV  [1196.197180] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/wakeup/wakeup21 (wakeup)
  UDEV  [1196.224577] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11/event3 (input)
  UDEV  [1196.231346] bind 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 (usb)
  UDEV  [1196.244978] bind /devices/pci:00/:00:14.0/usb1/1-3 (usb)

  Note how there's no «(rc)» displayed on any of the lines, which means
  that the «SUBSYSTEM=="rc"» condition from the udev rule filters all of
  the above events.

  I found a rule that works at https://www.mail-archive.com/linux-
  me...@vger.kernel.org/msg117165.html:

  ACTION=="add", SUBSYSTEM=="input", SUBSYSTEMS=="rc", KERNEL=="event*",
  ENV{.rc_sysdev}="$id", RUN+="/usr/bin/ir-keytable -a /etc/rc_maps.cfg
  -s $env{.rc_sysdev}"

  Creating a custom /etc/udev/rules.d/60-ir-keytable.rules file
  containing this rule solves the problem; now my custom keymap is
  loaded at boot, as it did before (when I was running Bionic).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ir-keytable 1.18.0-2build1 [modified: usr/bin/ir-keytable]
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Dec  6 18:05:06 2020
  SourcePackage: v4l-utils
  UpgradeStatus: Upgraded to focal on 2020-12-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/v4l-utils/+bug/1906986/+subscriptions

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

[Touch-packages] [Bug 1908051] [NEW] error: Argument 7: Cannot convert from `void Unity.Internal.ScopeChannel.OwnerWatcher.owner_changed

[Jose Riha]

Public bug reported:

make returns:

unity-protocol.vapi:242.4-242.43: warning: DBus methods are recommended to 
throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async void set_view_type (uint 
view_type) throws GLib.IOError;

unity-launcher.vala:61.5-61.42: warning: DBus methods are recommended to throw 
at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public HashTable query ()
^^
unity-scope-channel.vala:312.33-312.50: error: Argument 7: Cannot convert from 
`void Unity.Internal.ScopeChannel.OwnerWatcher.owner_changed 
(GLib.DBusConnection, string, string, string, string, GLib.Variant)' to `void 
GLib.DBusSignalCallback (GLib.DBusConnection, string?, string, string, string, 
GLib.Variant)'
  DBusSignalFlags.NONE, this.owner_changed);
^^
unity-scope-channel.vala:269.9-269.52: warning: Access to possible `null'. 
Perform a check or use an unsafe cast.
(transfer_model as DiffModel).commit_changes ();

unity-synchronizer.vala:93.5-93.18: warning: `GLib.HashTable.add' has been 
deprecated since vala-0.26. Use GenericSet.add
unity-aggregator-scope-private.vala:434.7-434.28: warning: `GLib.HashTable.add' 
has been deprecated since vala-0.26. Use GenericSet.add
unity-aggregator-scope-private.vala:606.7-606.72: warning: Access to possible 
`null'. Perform a check or use an unsafe cast.
  (category_merger as CategoryMergerByField).map_subscope_categories 
(scope_id, proxy.categories_model);
  ^^
unity-aggregator-scope-private.vala:1308.7-1308.66: warning: Access to possible 
`null'. Perform a check or use an unsafe cast.
  (category_merger as CategoryMergerByScope).add_scope_mapping (owner, 
scope_id);
  
unity-aggregator-scope-private.vala:1352.7-1352.66: warning: Access to possible 
`null'. Perform a check or use an unsafe cast.
  (category_merger as CategoryMergerByScope).add_scope_mapping (owner, 
master_scope_id);
  
unity-scope-loader.vala:41.49-41.69: warning: `GLib.ModuleFlags.BIND_LAZY' has 
been deprecated since vala-0.46. Use LAZY
unity-sound-menu-mpris.vala:475.5-475.27: warning: DBus methods are recommended 
to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void raise() throws IOError{
^^^
unity-sound-menu-mpris.vala:580.5-580.32: warning: DBus methods are recommended 
to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void play_pause() throws IOError

unity-sound-menu-mpris.vala:585.5-585.26: warning: DBus methods are recommended 
to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void next() throws IOError
^^
unity-sound-menu-mpris.vala:590.5-590.30: warning: DBus methods are recommended 
to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void previous() throws IOError
^^
unity-sound-menu-mpris.vala:709.5-709.39: warning: DBus methods are recommended 
to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void activate_playlist (ObjectPath playlist_id) throws IOError
^^^
unity-sound-menu-mpris.vala:714.5-714.48: warning: DBus methods are recommended 
to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async PlaylistDetails[] get_playlists (uint32 index,

unity-sound-menu-mpris.vala:407.5-407.55: warning: DBus methods are recommended 
to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async void EnableTrackSpecificItems (ObjectPath 
object_path, string desktop_id) throws IOError;
^^^
unity-sound-menu-mpris.vala:408.5-408.56: warning: DBus methods are recommended 
to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async void EnablePlayerSpecificItems (ObjectPath 
object_path, string desktop_id) throws IOError;

Compilation failed: 1 error(s), 22 warning(s)
make[2]: *** [Makefile:1391: libunity_la_vala.stamp] Error 1
make[2]: Leaving directory '/home/jose/tmp/libunity/src'
make[1]: *** [Makefile:573: all-recursive] Error 1
make[1]: Leaving directory '/home/jose/tmp/libunity'
make: *** [Makefile:477: all] Error 2

Distro: Arch Linux

Related: https://aur.archlinux.org/packages/libunity/

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

-- 
You received this 

[Touch-packages] [Bug 1907906] Re: i want some support

[Sebastien Bacher]

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

Title:
  i want some support

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 12 15:39:57 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:5000]
  InstallationDate: Installed on 2020-11-14 (27 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 33663VG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-32-generic 
root=UUID=d4192c33-e4f0-4468-8ebe-426000ec3852 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2013
  dmi.bios.release: 2.54
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H0ET94WW (2.54 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 33663VG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 2.54
  dmi.modalias: 
dmi:bvnLENOVO:bvrH0ET94WW(2.54):bd08/02/2013:br2.54:efr2.54:svnLENOVO:pn33663VG:pvrThinkPadEdgeE530c:rvnLENOVO:rn33663VG:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Edge E530c
  dmi.product.name: 33663VG
  dmi.product.sku: LENOVO_MT_3366
  dmi.product.version: ThinkPad Edge E530c
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1~ubuntu0.20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1906986] Re: defective ir-keytable udev rule → custom keytable does not get loaded

[Sebastien Bacher]

Thank you for your bug report, that's what got fixed in
https://bugs.launchpad.net/ubuntu/+source/v4l-utils/1.20.0-2 right ?

** Changed in: v4l-utils (Ubuntu)
   Importance: Undecided => High

** Changed in: v4l-utils (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  defective ir-keytable udev rule → custom keytable does not get loaded

Status in v4l-utils package in Ubuntu:
  Incomplete

Bug description:
  ir-keytable v1.18.0-2build1 ships /lib/udev/rules.d/60-ir-
  keytable.rules containing the following rule:

  ACTION=="add", SUBSYSTEM=="rc", RUN+="/usr/bin/ir-keytable -a
  /etc/rc_maps.cfg -s $name"

  After upgrading to Focal, this does not get triggered at boot, nor if
  I (re)insert my receiver when the system is running. Therefore, the
  custom keytable does not get loaded.

  This is the udev events that occur when I insert the receiver:

  $ sudo udevadm monitor
  monitor will print the received events for:
  UDEV - the event which udev sends out after rule processing
  KERNEL - the kernel uevent

  KERNEL[1195.829011] add  /devices/pci:00/:00:14.0/usb1/1-3 (usb)
  KERNEL[1195.834989] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 (usb)
  KERNEL[1195.874055] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/lirc0 (lirc)
  KERNEL[1195.875019] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11 (input)
  KERNEL[1195.875183] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11/event3 (input)
  KERNEL[1196.134164] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/wakeup/wakeup21 (wakeup)
  KERNEL[1196.134448] bind 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 (usb)
  KERNEL[1196.134704] bind /devices/pci:00/:00:14.0/usb1/1-3 (usb)
  UDEV  [1196.158923] add  /devices/pci:00/:00:14.0/usb1/1-3 (usb)
  UDEV  [1196.174559] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 (usb)
  UDEV  [1196.194750] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/lirc0 (lirc)
  UDEV  [1196.196268] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11 (input)
  UDEV  [1196.197180] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/wakeup/wakeup21 (wakeup)
  UDEV  [1196.224577] add  
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11/event3 (input)
  UDEV  [1196.231346] bind 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 (usb)
  UDEV  [1196.244978] bind /devices/pci:00/:00:14.0/usb1/1-3 (usb)

  Note how there's no «(rc)» displayed on any of the lines, which means
  that the «SUBSYSTEM=="rc"» condition from the udev rule filters all of
  the above events.

  I found a rule that works at https://www.mail-archive.com/linux-
  me...@vger.kernel.org/msg117165.html:

  ACTION=="add", SUBSYSTEM=="input", SUBSYSTEMS=="rc", KERNEL=="event*",
  ENV{.rc_sysdev}="$id", RUN+="/usr/bin/ir-keytable -a /etc/rc_maps.cfg
  -s $env{.rc_sysdev}"

  Creating a custom /etc/udev/rules.d/60-ir-keytable.rules file
  containing this rule solves the problem; now my custom keymap is
  loaded at boot, as it did before (when I was running Bionic).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ir-keytable 1.18.0-2build1 [modified: usr/bin/ir-keytable]
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Dec  6 18:05:06 2020
  SourcePackage: v4l-utils
  UpgradeStatus: Upgraded to focal on 2020-12-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/v4l-utils/+bug/1906986/+subscriptions

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

[Touch-packages] [Bug 1907865] Re: Xorg crash

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

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

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I can't reliably reproduce this crash, and I don't know, even
  approximately, what's causing it, or what I might be doing to possibly
  cause it.  It just randomly crashes, and dumps me back to the login
  screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 11 15:35:06 2020
  DistUpgraded: 2020-10-07 09:25:09,468 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: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06de]
  InstallationDate: Installed on 2016-12-06 (1466 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5470
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to focal on 2020-10-07 (65 days ago)
  dmi.bios.date: 06/15/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.3
  dmi.board.name: 0VHKV0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn0VHKV0:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5470
  dmi.product.sku: 06DE
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2020-12-09T15:53:03.120486
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Fri Aug 17 21:02:51 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1523 
   vendor BOE
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Touch-packages] [Bug 1907870] Re: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9

[Sebastien Bacher]

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

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

Title:
  Secondary screen detected but black screen with Intel UHD graphics on
  kernel 5.9

Status in linux package in Ubuntu:
  New

Bug description:
  Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS.

  The problem:

  When i connect to my external monitor (a Samsung BX2250) via HDMI, the
  screen is detected (i can see it in display settings) but the external
  monitor remains black. Seams like a bad frequency or resolution. I
  tried adding a new mode to xrandr with no luck. Also i tried different
  versions of kernels from 5.4 to 5.9.

  I am using Ubuntu 20.10

  This is my lspci

  0:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c)
  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02)
  00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c)
  00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal 
Subsytem
  00:14.0 USB controller: Intel Corporation Device 02ed
  00:14.2 RAM memory: Intel Corporation Device 02ef
  00:14.3 Network controller: Intel Corporation Wireless-AC 9462
  00:14.5 SD Host controller: Intel Corporation Device 02f5
  00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host 
Controller
  00:16.0 Communication controller: Intel Corporation Comet Lake Management 
Engine Interface
  00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller
  00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0)
  00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0)
  00:1f.0 ISA bridge: Intel Corporation Device 0284
  00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8
  00:1f.4 SMBus: Intel Corporation Device 02a3
  00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI 
(flash) Controller
  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
  02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01)

  inxi -Gx output:

  Graphics:  Device-1: Intel UHD Graphics vendor: Hewlett-Packard driver: i915 
v: kernel bus ID: 00:02.0 
 Device-2: Lite-On HP HD Camera type: USB driver: uvcvideo bus ID: 
1-2:2 
 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: 
fbdev,vesa resolution: 1366x768~60Hz 
 OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 
20.2.1 direct render: Yes 

  xrandr output (with hdmi cable connected to external monitor):

  Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384
  eDP-1 connected primary 1366x768+0+0 (normal left inverted right x axis y 
axis) 309mm x 173mm
 1366x768  60.06*+  40.04  
 1360x768  59.8059.96  
 1280x720  60.0059.9959.8659.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  HDMI-1 connected (normal left inverted right x axis y axis)
 1920x1080 60.00 +  50.0059.94  
 1920x1080i60.0050.0059.94  
 1600x1200 60.00  
 1680x1050 59.88  
 1280x1024 75.0260.02  
 1440x900  74.9859.90  
 1280x960  60.00  
 1280x800  59.91  
 1152x864  75.00  
 1280x720  60.0050.0059.94  
 1024x768  75.0370.0760.00  
 832x624   74.55  
 800x600   72.1975.0060.3256.25  
 720x576   50.00  
 720x480   60.0059.94  
 640x480   75.0072.8166.6760.0059.94  
 720x400   70.08  
  DP-1 disconnected (normal left inverted right x axis y axis)
  HDMI-2 disconnected (normal left inverted right x axis y axis)
  --- 
  

[Touch-packages] [Bug 330833] Re: NetworkManager always overwrites default route when connecting to OpenVPN network

[Valerio Bozzolan]

I also can reproduce this issue with NetworkManager of Ubuntu 20.04
Focal Fossa (network-manager 1.22.10-1ubuntu2.2).

If I create an OpenVPN server WITHOUT 'redirect-gateway' and if I use
the command line OpenVPN client directly as-is, it works. It does NOT
create a new default gateway (because I do not want it).

/usr/sbin/openvpn --config file.ovpn

Instead. If I import that configuration in Network Manager, the "use
this connection only for resources on this network" is unchecked and
probably that's the cause of the creation of a new additional default
route, wrong for these cases.

Any plan about how to fix this issue in NetworkManager?

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

Title:
  NetworkManager always overwrites default route when connecting to
  OpenVPN network

Status in NetworkManager-OpenVPN:
  Invalid
Status in network-manager package in Ubuntu:
  Invalid
Status in network-manager-openvpn package in Ubuntu:
  Fix Released
Status in network-manager package in Debian:
  New
Status in network-manager package in Fedora:
  Invalid

Bug description:
  Binary package hint: network-manager

  My office VPN has IMAP, (forwarding) DNS services and not much else.
  It doesn't forward client traffic to the Internet. This means I can't
  use the VPN server as a default gateway.

  Every time I connect to the VPN using NetworkManager/OpenVPN, my
  routing table gets a default route to the VPN. I've tried everything
  to avoid this in both the Intrepid package and the version from the
  network manager PPA with no success. Even telling NetworkManager to
  ignore routes from the server doesn't work.

  As it is right now, I have to connect to the VPN, delete the default
  route, and re-add my wireless router as the default gateway before I
  can have both email and web access.

  See attached routing table details.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  NonfreeKernelModules: nvidia
  Package: network-manager 0.7-0ubuntu1~nm1~intrepid1
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  Uname: Linux 2.6.27-11-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/330833/+subscriptions

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

[Touch-packages] [Bug 1874020] Re: Jack clients cannot use real-time scheduling with kernel 5.4.0-25-generic

[Sebastien Bacher]

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

** This bug has been marked a duplicate of bug 1873315
   5.4.0-24.28 does not seem to apply rtprio, whereas -21 does.

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

Title:
  Jack clients cannot use real-time scheduling with kernel
  5.4.0-25-generic

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  With kernels 5.4.0-24-generic and 5.4.0-25-generic Jack client applications 
can no longer use real-time scheduling. Kernel 5.4.0-23-generic works.
  For example starting guitarix or ardour produces the following logs on stderr:

  Cannot use real-time scheduling (RR/5)(1: Operation not permitted)
  JackClient::AcquireSelfRealTime error

  The following is a strace from an older (working) kernel:

  sched_get_priority_min(SCHED_FIFO)  = 1
  sched_get_priority_max(SCHED_FIFO)  = 99
  sched_get_priority_min(SCHED_FIFO)  = 1
  sched_get_priority_max(SCHED_FIFO)  = 99
  mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 
0x7fd5c307c000
  mprotect(0x7fd5c307d000, 8388608, PROT_READ|PROT_WRITE) = 0
  clone(child_stack=0x7fd5c387b9f0, 
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CL
  ONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, 
parent_tid=[47564], tls=0x7fd5c3
  87c700, child_tidptr=0x7fd5c387c9d0) = 47564
  sched_setscheduler(47564, SCHED_FIFO, [1]) = 0

  
  Compare against an strace with an affected kernel:

  sched_get_priority_min(SCHED_FIFO)  = 1
  sched_get_priority_max(SCHED_FIFO)  = 99
  sched_get_priority_min(SCHED_FIFO)  = 1
  sched_get_priority_max(SCHED_FIFO)  = 99
  mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 
0x7f8d827ee000
  mprotect(0x7f8d827ef000, 8388608, PROT_READ|PROT_WRITE) = 0
  clone(child_stack=0x7f8d82fed9f0, 
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CL
  ONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, 
parent_tid=[21592], tls=0x7f8d82
  fee700, child_tidptr=0x7f8d82fee9d0) = 21592
  sched_setscheduler(21592, SCHED_FIFO, [1]) = -1 EPERM (Operation not 
permitted)

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

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

[Touch-packages] [Bug 1849886] Re: lightdm does not work on eoan on raspberry pi 4

[Sebastien Bacher]

Those still having the issue on focal, which greeter are you using? It
could be the same issue than https://launchpad.net/ubuntu/+source
/lightdm-gtk-greeter/2.0.6-0ubuntu2 ?

** Changed in: lightdm (Ubuntu)
   Status: Confirmed => Incomplete

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

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

Title:
  lightdm does not work on eoan on raspberry pi 4

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  if you follow the directions on
  https://wiki.ubuntu.com/ARM/RaspberryPi

  sudo apt-get install xubuntu-desktop

  about 20% thru the installation it will ask which window manager you want 
(using dpkg-reconfigure).
  if you select lightdm, you will only get a blank greeter screen after you 
reboot.

  using sudo dpkg-reconfigure gdm3

  resets this to gdm3 and after a reboot, everything is fine.

  this was done on a clean armhf eoan install on a 4gb raspberry pi 4B.

  I have done the install several times.   This bug is repeatable.

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

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

[Touch-packages] [Bug 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button

[Sebastien Bacher]

@Martin, could you add a screenshot from the issue under xorg as well as
a 'journalctl -b 0' log from the session?

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

Title:
  Snap 'ed applicaitons have garbage on top of the window Close [x]
  button

Status in adwaita-icon-theme package in Ubuntu:
  Confirmed
Status in gnome-themes-extra package in Ubuntu:
  Confirmed
Status in humanity-icon-theme package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in ubuntu-mono package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 19.10 installed
  2. Install GNOME application as a Snap - for example with

  sudo snap install gedit gnome-calculator

  3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the
  one of the following:

  * Adwaita
  * DMZ-Black
  * DMZ-White
  * hicolor
  * HighContrast
  * Humanity
  * Humanity-Dark
  * LoginIcons

  For example - Adwaita theme with Adwaita icon set.

  4. Open GNOME Calculator as a Snap application:

 /snap/bin/gnome-calculator

  Expected result:

  * GNOME Calculator looks as any other GTK application

  Actual result:

  * GNOME Calculator has garbage on top of the window Close [x] button

  ---

  Notes: 
  1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868
  2. one can use the script below to check all possible Theme<->Icon 
combinations:

  ```
  #!/bin/bash

  DISPLAY=:0

  for t in $(ls -1 /usr/share/themes/)
  do 
for i in $(ls -1 /usr/share/icons/)
do

  echo -e "\nTheme: $t, Icons: $i\n"

gsettings set org.gnome.desktop.interface gtk-theme "$t"
gsettings set org.gnome.desktop.interface icon-theme "$i"

  /snap/bin/gnome-calculator

#read -r -s -p "Press  for next theme"   
done
  done

  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: snapd 2.41+19.10.1
  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: Sat Feb  1 17:55:09 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+subscriptions

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

[Touch-packages] [Bug 1863369] Re: Livepatch is running, but appears OFF in 'software & updates'

[Sebastien Bacher]

@Luca, are you using network-manager or not as described in the previous
comments?

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

Title:
  Livepatch is running, but appears OFF in 'software & updates'

Status in software-properties package in Ubuntu:
  New

Bug description:
  I have a similar problem to #1758980 Enabling LivePatch fails, but not so 
sure it is the same. When I verify Livepatch status (sudo canonical-livepatch 
status):
  client-version: 9.4.8
  architecture: x86_64
  cpu-model: Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz
  last-check: 2020-02-14T09:29:57-03:00
  boot-time: 2020-02-14T07:29:23-03:00
  uptime: 2h26m29s
  status:
  - kernel: 4.15.0-76.86-generic
running: true
livepatch:
  checkState: checked
  patchState: nothing-to-apply
  version: ""
  fixes: ""

  But in 'Software & Updates' Livepatch tab all I got is 'OFF', and I
  can't switch ON or click on it. It is written 'Livepatch requires an
  internet connection'. Is this a known bug to be ignored, or something
  else that must be fixed?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1863369/+subscriptions

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

[Touch-packages] [Bug 1846334] Re: cupsd assert failure: free(): invalid pointer

[Sebastien Bacher]

The Debian report suggests there is a fix proposed on
https://github.com/apple/cups/issues/5826 which has been backported to
Debian

** Bug watch added: github.com/apple/cups/issues #5826
   https://github.com/apple/cups/issues/5826

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

Title:
  cupsd assert failure: free(): invalid pointer

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Just running in the background, no user action (printing)

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-daemon 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AssertionMessage: free(): invalid pointer
  Date: Tue Oct  1 19:41:35 2019
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2019-02-09 (234 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Lpstat:
   device for HP_LaserJet_CM1415fn_44A808_: 
implicitclass://HP_LaserJet_CM1415fn_44A808_/
   device for Samsung_C48x_Series_SEC84251900EE44_: 
implicitclass://Samsung_C48x_Series_SEC84251900EE44_/
  MachineType: Dell Inc. Latitude E6530
  Papersize: letter
  PpdFiles:
   HP_LaserJet_CM1415fn_44A808_: LaserJet CM1415fn - IPP Everywhere
   Samsung_C48x_Series_SEC84251900EE44_: C48x Series - IPP Everywhere
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic 
root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic 
root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f923ecb83a5 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f923ecb652a "free(): invalid pointer") at 
malloc.c:5332
   _int_free (av=, p=, have_lock=0) at 
malloc.c:4173
   ?? () from /lib/x86_64-linux-gnu/libcups.so.2
   ippDelete () from /lib/x86_64-linux-gnu/libcups.so.2
  Title: cupsd assert failure: free(): invalid pointer
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A22
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.sku: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  separator:

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

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

[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

[Julian Andres Klode]

** Changed in: apt (Ubuntu)
 Assignee: Sebastián Astudillo (zhoku) => (unassigned)

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Confirmed
Status in apt source package in Focal:
  Triaged
Status in apt source package in Groovy:
  Triaged
Status in apt package in Debian:
  Unknown

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  So what we do is change that to a warning.

  [Test case]
  Not available right now. Issues can flare up and then disappear again.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020