[Touch-packages] [Bug 1929647] Re: debian helper tools for python never updates

[pleabargain]

select all fails to include debian python option 
see gif

** Attachment added: "select all"
   
https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1929647/+attachment/5500827/+files/cannot%20select%20Peek%202021-05-28%2007-16.gif

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

Title:
  debian helper tools for python never updates

Status in python-debian package in Ubuntu:
  New

Bug description:
  software updater prompts new updates
  debian helper tools for python is always one of them but I cannot select the 
checkbox
  so

  debian helper tools for python never updates


  Here's the screen shot
  https://i.imgur.com/AjDd5yo.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1929647/+subscriptions

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

[Touch-packages] [Bug 1929817] Re: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only)

[Hui Wang]

** Summary changed:

- [SRU] pulseaudio: let a signle alsa mixer support up to 8 channels
+ [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal 
only)

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

Title:
  [SRU] pulseaudio: let a single alsa mixer support up to 8 channels
  (focal only)

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

Bug description:
  [Impact]
  Many Lenovo laptops have up to 4 microphones (microphone array), before the 
linux kernel 5.11, the alsa mixer for digital microphone is 2 channels, and the 
PA in the focal also supports up to 2 chanels for a single alsa mixer, so the 
PA in the focal works well with linux kernel 5.10 and lower on those Lenovo 
laptops. But we are going to install hirsute kernel (5.11) to the focal, the PA 
in the focal can't handle 4 channels of the digital mic, it will use pure 
software volume for digital mic, user can't adjust hardware volume of the 
digital mic anymore.

  
  [Fix]
  Backport 2 patches from PA-14.2, the PA in the hirsute (21.04) already have 
these 2 patches, so this SRU is for focal only. After applying these 2 patches, 
the PA could handle up to 8 channels for a single alsa mixer. 

  [Test]
  Install patched PA on Lenovo laptops with 4 digital microphone, I could 
change the hardware input volume of digital mic through pulseaudio. I also 
installed patched PA to some old lenovo and Dell machines, all output and input 
devices worked as well as before, there is no regression observed.

  [Where problems could occur]
  This could introduce a regression on the output/input volume control, for 
example, the output or input volume only supports software volume in the PA, 
users can't adjust the hardware volume through pulseaudio anymore. But this 
regression possibility is very low, first the hirsute already has these 2 
patches, second I already tested these 2 patches on different machines, all 
worked as well as before.

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

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

[Touch-packages] [Bug 1929833] Re: bluez: meshctl missing

[Daniel van Vugt]

** Tags added: impish

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

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

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

Title:
  bluez: meshctl missing

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  bluez has added a new tool for BT mesh handling.

  Debian has a new binary package: https://packages.debian.org/bullseye
  /bluez-meshd

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

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

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

[Touch-packages] [Bug 1929854] Re: Vital and critical configuration files get overridden by system updates without warning

[Daniel van Vugt]

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

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

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

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

Title:
  Vital and critical configuration files get overridden by system
  updates without warning

Status in grub2 package in Ubuntu:
  New
Status in libx11 package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  New

Bug description:
  • In my /usr/share/X11/locale/en_US.UTF-8/Compose I have about 10'000 lines 
of special compose keys defined.
  • In my /boot/grub/grub.cfg I have a very complicated special setup for my 
various boot configurations, and a 5-sec timout for my EFI-config.
  • My /etc/ssh/sshd_config contains a well-balanced configuration 

  All these files are regularly overridden WITHOUT EVEN A SINGLE WARNING
  or ASKING BACK by ubuntu system setups (discover).

  I set all of them to read-only by root and no-access for group and
  other users, but they still get overridden by every other system
  update.  I even have a shutdown process in place which should actually
  make sure that changes to these files are reverted by writing a backup
  copy over any newly installed override — unfortunately, everything I
  did to run either a custom shutdown process or a startup process with
  systemd turned out to not work and be a nightmare to make work.

  How somebody could be as bold as to override vital configuration files
  like this without even asking  for consent is one of the strange
  miracles in this world which I'll probably never understand.  However,
  if "ubuntu" is really what it translates to, it should take a little
  bit more care about pre-existing configurations on systems on which it
  is set up and running well — until one system update suddenly
  jeopardizes the functioning of the entire system.  I'm pretty sure
  these are not the only configuration files which are carelessly just
  overridden.  They're just the ones every other update breaks my system
  and inflinges on my the costs of hours of research until I find out
  that — of course — it was an overridden critical system configuration
  again.  The really mean thing is that you don't notice anything when
  you run the update … only next time you start your system and of
  course are not aware anymore that you did a system update, the new
  (absolutely wrong and/or insufficent) settings are in place and shoot
  you in the leg.

  Take an example from gentoo's etc-update feature which lets you merge
  new configuration files with pre-existing ones using a diff3-update.
  I went away from gentoo for other reasons, but I always praised that
  feature.

  Please make sure immediately that critical configuration files do not
  get overridden if they are non-writable by root, and then gradually
  introduce a system that merges changes to configuration files with the
  current situation on the target system.  Or at least present the
  configs that would be changed in a particular directory, so that
  anybody who is interested in preserving local settings could merge
  them in a suitable way.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu May 27 18:48:15 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297]
  InstallationDate: Installed on 2021-01-15 (132 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20QQS0KL13
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-53-generic 
root=UUID=35cef147-e021-4bdd-b8db-31a3192c8a6a ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2020
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2NET38W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QQS0KL13
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: ZF211710
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 

[Touch-packages] [Bug 1929817] Re: [SRU] pulseaudio: let a signle alsa mixer support up to 8 channels

[Daniel van Vugt]

** Tags added: focal

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

Title:
  [SRU] pulseaudio: let a signle alsa mixer support up to 8 channels

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

Bug description:
  [Impact]
  Many Lenovo laptops have up to 4 microphones (microphone array), before the 
linux kernel 5.11, the alsa mixer for digital microphone is 2 channels, and the 
PA in the focal also supports up to 2 chanels for a single alsa mixer, so the 
PA in the focal works well with linux kernel 5.10 and lower on those Lenovo 
laptops. But we are going to install hirsute kernel (5.11) to the focal, the PA 
in the focal can't handle 4 channels of the digital mic, it will use pure 
software volume for digital mic, user can't adjust hardware volume of the 
digital mic anymore.

  
  [Fix]
  Backport 2 patches from PA-14.2, the PA in the hirsute (21.04) already have 
these 2 patches, so this SRU is for focal only. After applying these 2 patches, 
the PA could handle up to 8 channels for a single alsa mixer. 

  [Test]
  Install patched PA on Lenovo laptops with 4 digital microphone, I could 
change the hardware input volume of digital mic through pulseaudio. I also 
installed patched PA to some old lenovo and Dell machines, all output and input 
devices worked as well as before, there is no regression observed.

  [Where problems could occur]
  This could introduce a regression on the output/input volume control, for 
example, the output or input volume only supports software volume in the PA, 
users can't adjust the hardware volume through pulseaudio anymore. But this 
regression possibility is very low, first the hirsute already has these 2 
patches, second I already tested these 2 patches on different machines, all 
worked as well as before.

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

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

[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort

[jeremyszu]

** Tags added: originate-from-1929152 stella

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

Title:
  Xorg xserver got signal 6 to abort

Status in Mesa:
  Unknown
Status in OEM Priority Project:
  In Progress
Status in mesa package in Ubuntu:
  New

Bug description:
  I run checkbox job
  com.canonical.certification::memory/memory_stress_ng on focal, and the
  xserver stops unexpectedly with the following stacktrace:

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

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

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

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

[Touch-packages] [Bug 1609700] Re: username is not saved in openconnect connection dialog

[Bug Watch Updater]

** Changed in: fedora
   Status: Confirmed => Won't Fix

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

Title:
  username is not saved in openconnect connection dialog

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-openconnect package in Ubuntu:
  Fix Released
Status in Fedora:
  Won't Fix

Bug description:
  Happening again on Eoan 19.10!


  Hi,

  I clicked on "save passwords" but only the password is filled in
  automatically when I open the connection dialog. The "Username" field
  is empty!

  This happens for a SSLVPN configuration.

  For another VPN config (don't know which type) everything is ok.

  openconnect: 7.06-2build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+subscriptions

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

[Touch-packages] [Bug 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)

[MarkF]

@Piotr, I've given up on this. I was less concerned about security than
I was about the user experience. If the installer knows it's going to
drop the connection, why not inform the user of this? It's really
unnerving to have your connection drop, and think there's some kind of
bug going on. It's little satisfaction to learn later it's not a bug.

I don't know what it is with *buntu, but I've given up. They don't care
about attracting more people. It's a circle-the-wagons approach. I say
it to anyone who will listen: Re-open Bug#1. *buntu has lost its way.
Shuttleworth should look at his contemporaries (who've moved on to
launching cars into space, and being the richest men in the world). He
should ask why he got left behind. Windows 10 was a windfall to the
Linux Desktop, and we're still missing the point.

I've moved on to a non-buntu based distro. Peace be upon all.

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

Title:
  Installer disconnects wifi (after choosing download while installing,
  3rd party)

Status in systemd:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Won't Fix

Bug description:
  ISO testing 20.04 daily 20200314. On the Live desktop I connect to
  wifi. When I click the install icon, and choose to install 3rd party
  (leaving download while installing checked), the wifi disconnects.

  I rebooted and tried again to make sure it wasn't something random.
  (It happened exactly the same.).

  This is an older Dell E5420 laptop with Broadcom BCM4313 wireless
  card. (Today's Lubuntu had a wifi-related problem too. I couldn't
  connect to wifi upon reboot after install. I had to reboot a 2nd time
  for it to work. I reported that to their Discourse forum, not reported
  as a bug yet.).

  I apologize that I don't know the package or pid to report this for.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18
  Uname: Linux 5.4.0-14-lowlatency x86_64
  NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.441
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Mar 14 20:29:15 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:049b]
  LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314)
  MachineType: Dell Inc. Latitude E5420
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed 
initrd=/casper/initrd quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0H5TG2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)

[Piotr]

@Dimitri John Ledkov I had also this issue. I know now that this will be
not fixed. This problem is not affect my security? I am safe? This
worried me because Network Manager save wi-fi password. Can you answer?

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

Title:
  Installer disconnects wifi (after choosing download while installing,
  3rd party)

Status in systemd:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Won't Fix

Bug description:
  ISO testing 20.04 daily 20200314. On the Live desktop I connect to
  wifi. When I click the install icon, and choose to install 3rd party
  (leaving download while installing checked), the wifi disconnects.

  I rebooted and tried again to make sure it wasn't something random.
  (It happened exactly the same.).

  This is an older Dell E5420 laptop with Broadcom BCM4313 wireless
  card. (Today's Lubuntu had a wifi-related problem too. I couldn't
  connect to wifi upon reboot after install. I had to reboot a 2nd time
  for it to work. I reported that to their Discourse forum, not reported
  as a bug yet.).

  I apologize that I don't know the package or pid to report this for.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18
  Uname: Linux 5.4.0-14-lowlatency x86_64
  NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.441
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Mar 14 20:29:15 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:049b]
  LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314)
  MachineType: Dell Inc. Latitude E5420
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed 
initrd=/casper/initrd quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0H5TG2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio - 1:14.2-2ubuntu2

---
pulseaudio (1:14.2-2ubuntu2) impish; urgency=medium

  * d/p/0016-check_off_profile_when_switching_profile.patch
  * d/p/0017-add_dynamic_priority_bonus_base_for_alsa_profiles.patch
Fix a "Rear Mic" always showing on input list when using dual codec.
(LP: #1929371)

 -- Jeremy Szu   Tue, 25 May 2021 12:41:39
+

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

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

Title:
  [SRU] there is always a "Rear Microphone - Built-in Audio" option on
  the input device list even if the microphone is unplugged

Status in OEM Priority Project:
  Triaged
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]
  In Lenovo P520, which using a codec for front panel, the other codec for rear 
panel and both are on a same card.

  In this case, the rear Mic will present on input devices of "Sound
  Settings" even if attaching nothing to rear mic jack.

  [Fix]
  For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl 
because of
  ```
control.18 {
iface CARD
name 'Rear Mic Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
  ```
  After applying "Rear Mic Jack", the rear Mic will not always there anymore 
but it's not there as well if hot-plugging audio device on rear mic. Thus, it 
needs to change pulseaudio to handle if all devices are off cases.

  For pulseaudio, if there is no any audio devices attached, then
  attaching an input device on rear mic jack. The port will not be
  selected automatically because the profiles is off. It needs patch
  pulseaudio to check off profiles (for dual codec case).

  [Test]
  After applying these patches, the rear mic jack works good in all cases (boot 
without mic and then attach mic, boot with mic and then hotplug it) and other 
functions (line-in / line-out) work pretty well.

  [Where problems could occur]
  This change only apply the bonus on below cases:
  ```
  if ((has_input_port && found_available_input_port && !has_output_port) ||
  (has_output_port && found_available_output_port && !has_input_port) ||
  (has_input_port && found_available_input_port && has_output_port && 
found_available_output_port)) 
  ```
  and these cases have been tested.
  If there are some complex codec design then it might cause problem but so far 
we didn't see that.

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

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

[Touch-packages] [Bug 1152187] Re: [MIR] systemd

[Steve Beattie]

Yes, the systemd-container package will end up in main, likely for the
current package in bionic-updates, and thus will be reflected that way
in rmadison etc.

For the record, ack from the Ubuntu Security Team on promoting the
systemd-container binary from universe to main in bionic.

Thanks.

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

Title:
  [MIR] systemd

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Incomplete

Bug description:
  * The package is in universe and built on all archs:
  https://launchpad.net/ubuntu/+source/systemd/44-10ubuntu1

  * Rationale:

  - in a first step we want systemd-services promoted to replace ubuntu-
  system-services

  -  We will also want to move from consolekit to logind soon
  (https://blueprints.launchpad.net/ubuntu/+spec/foundations-1303
  -consolekit-logind-migration)

  - udev has been merged in the systemd source upstream so we will want
  to build it from there at some point as well

  we don't plan to use the systemd init system at this point

  * Security:

  there has been some security issues in the past
  http://secunia.com/advisories/search/?search=systemd
  http://secunia.com/advisories/48220/
  http://secunia.com/advisories/48208/
  http://secunia.com/advisories/48331/

  Those are mostly logind issue and have been fixed upstream.

  Our current package is outdated but we do plan to update it before
  starting using logind. There should be no issue with the services

  * Quality:
  - there is no RC bug in debian: 
http://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=systemd
  - there is no bug open in launchpad: 
https://launchpad.net/ubuntu/+source/systemd/+bugs
  - upstream is active and responsive to issues

  The desktop bugs team is subscribed to the package in launchpad,
  foundations/desktop will maintain the package and look to the bug
  reports regularly.

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

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

[Touch-packages] [Bug 1197712] Re: 0.9.8.0-0ubuntu13 is causing conf prompt

[slarassarklay]

Die Website https://mr.bet/at/game/view/demo/railroad ist zu jeder Zeit
die beste Art von Online-Einnahmen. Davon bin ich jeden Tag mehr und
mehr überzeugt.

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

Title:
  0.9.8.0-0ubuntu13 is causing conf prompt

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Got a conf promt. not sure why =)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1197712/+subscriptions

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

[Touch-packages] [Bug 1929854] Re: Vital and critical configuration files get overridden by system updates without warning

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => xorg (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/1929854

Title:
  Vital and critical configuration files get overridden by system
  updates without warning

Status in xorg package in Ubuntu:
  New

Bug description:
  • In my /usr/share/X11/locale/en_US.UTF-8/Compose I have about 10'000 lines 
of special compose keys defined.
  • In my /boot/grub/grub.cfg I have a very complicated special setup for my 
various boot configurations, and a 5-sec timout for my EFI-config.
  • My /etc/ssh/sshd_config contains a well-balanced configuration 

  All these files are regularly overridden WITHOUT EVEN A SINGLE WARNING
  or ASKING BACK by ubuntu system setups (discover).

  I set all of them to read-only by root and no-access for group and
  other users, but they still get overridden by every other system
  update.  I even have a shutdown process in place which should actually
  make sure that changes to these files are reverted by writing a backup
  copy over any newly installed override — unfortunately, everything I
  did to run either a custom shutdown process or a startup process with
  systemd turned out to not work and be a nightmare to make work.

  How somebody could be as bold as to override vital configuration files
  like this without even asking  for consent is one of the strange
  miracles in this world which I'll probably never understand.  However,
  if "ubuntu" is really what it translates to, it should take a little
  bit more care about pre-existing configurations on systems on which it
  is set up and running well — until one system update suddenly
  jeopardizes the functioning of the entire system.  I'm pretty sure
  these are not the only configuration files which are carelessly just
  overridden.  They're just the ones every other update breaks my system
  and inflinges on my the costs of hours of research until I find out
  that — of course — it was an overridden critical system configuration
  again.  The really mean thing is that you don't notice anything when
  you run the update … only next time you start your system and of
  course are not aware anymore that you did a system update, the new
  (absolutely wrong and/or insufficent) settings are in place and shoot
  you in the leg.

  Take an example from gentoo's etc-update feature which lets you merge
  new configuration files with pre-existing ones using a diff3-update.
  I went away from gentoo for other reasons, but I always praised that
  feature.

  Please make sure immediately that critical configuration files do not
  get overridden if they are non-writable by root, and then gradually
  introduce a system that merges changes to configuration files with the
  current situation on the target system.  Or at least present the
  configs that would be changed in a particular directory, so that
  anybody who is interested in preserving local settings could merge
  them in a suitable way.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu May 27 18:48:15 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297]
  InstallationDate: Installed on 2021-01-15 (132 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20QQS0KL13
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-53-generic 
root=UUID=35cef147-e021-4bdd-b8db-31a3192c8a6a ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2020
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2NET38W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QQS0KL13
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: ZF211710
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET38W(1.23):bd06/04/2020:br1.23:efr1.14:svnLENOVO:pn20QQS0KL13:pvrThinkPadP53:rvnLENOVO:rn20QQS0KL13:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P53
  dmi.product.name: 20QQS0KL13
  dmi.product.sku: LENOVO_MT_20QQ_BU_Think_FM_ThinkPad P53
  dmi.product.version: ThinkPad P53
  dmi.sys.vendor: LENOVO
  

[Touch-packages] [Bug 1929854] [NEW] Vital and critical configuration files get overridden by system updates without warning

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

• In my /usr/share/X11/locale/en_US.UTF-8/Compose I have about 10'000 lines of 
special compose keys defined.
• In my /boot/grub/grub.cfg I have a very complicated special setup for my 
various boot configurations, and a 5-sec timout for my EFI-config.
• My /etc/ssh/sshd_config contains a well-balanced configuration 

All these files are regularly overridden WITHOUT EVEN A SINGLE WARNING
or ASKING BACK by ubuntu system setups (discover).

I set all of them to read-only by root and no-access for group and other
users, but they still get overridden by every other system update.  I
even have a shutdown process in place which should actually make sure
that changes to these files are reverted by writing a backup copy over
any newly installed override — unfortunately, everything I did to run
either a custom shutdown process or a startup process with systemd
turned out to not work and be a nightmare to make work.

How somebody could be as bold as to override vital configuration files
like this without even asking  for consent is one of the strange
miracles in this world which I'll probably never understand.  However,
if "ubuntu" is really what it translates to, it should take a little bit
more care about pre-existing configurations on systems on which it is
set up and running well — until one system update suddenly jeopardizes
the functioning of the entire system.  I'm pretty sure these are not the
only configuration files which are carelessly just overridden.  They're
just the ones every other update breaks my system and inflinges on my
the costs of hours of research until I find out that — of course — it
was an overridden critical system configuration again.  The really mean
thing is that you don't notice anything when you run the update … only
next time you start your system and of course are not aware anymore that
you did a system update, the new (absolutely wrong and/or insufficent)
settings are in place and shoot you in the leg.

Take an example from gentoo's etc-update feature which lets you merge
new configuration files with pre-existing ones using a diff3-update.  I
went away from gentoo for other reasons, but I always praised that
feature.

Please make sure immediately that critical configuration files do not
get overridden if they are non-writable by root, and then gradually
introduce a system that merges changes to configuration files with the
current situation on the target system.  Or at least present the configs
that would be changed in a particular directory, so that anybody who is
interested in preserving local settings could merge them in a suitable
way.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: KDE
Date: Thu May 27 18:48:15 2021
DistUpgraded: Fresh install
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297]
InstallationDate: Installed on 2021-01-15 (132 days ago)
InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
MachineType: LENOVO 20QQS0KL13
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-53-generic 
root=UUID=35cef147-e021-4bdd-b8db-31a3192c8a6a ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/04/2020
dmi.bios.release: 1.23
dmi.bios.vendor: LENOVO
dmi.bios.version: N2NET38W (1.23 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QQS0KL13
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: ZF211710
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET38W(1.23):bd06/04/2020:br1.23:efr1.14:svnLENOVO:pn20QQS0KL13:pvrThinkPadP53:rvnLENOVO:rn20QQS0KL13:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P53
dmi.product.name: 20QQS0KL13
dmi.product.sku: LENOVO_MT_20QQ_BU_Think_FM_ThinkPad P53
dmi.product.version: ThinkPad P53
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: 

[Touch-packages] [Bug 1929292] Re: ubiquity crashes whilst trying to use ubuntu-bug

[Brian Murray]

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

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

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

** Tags removed: rls-ff-incoming

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

Title:
  ubiquity crashes whilst trying to use ubuntu-bug

Status in apport package in Ubuntu:
  In Progress

Bug description:
  Multiple identities can be used for authentication:
   1.  user,,, (user)
   2.  Jon Thackray,,, (jon)
  Choose identity to authenticate as (1-2): 2
  Password: 
  polkit-agent-helper-1: pam_authenticate failed: Authentication failure
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.
  ERROR: hook /usr/share/apport/package-hooks/source_ubiquity.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_ubiquity.py", line 158, in 
add_info
  add_installation_log(report, 'Casper', 'casper.log')
File "/usr/share/apport/package-hooks/source_ubiquity.py", line 29, in 
add_installation_log
  if isinstance(report[ident], bytes):
File "/usr/lib/python3.8/collections/__init__.py", line 1010, in __getitem__
  raise KeyError(key)
  KeyError: 'Casper'

  My installation doesn't have /var/log/partman

  jon@frobenius:/var/lib$ lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  jon@frobenius:/var/lib$ apt-cache policy ubiquity
  ubiquity:
Installed: (none)
Candidate: 20.04.15.11
Version table:
   20.04.15.11 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   20.04.15 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  I expected to be able to report a bug I've found in qmail-run, but
  this seems to be a barrier to entry

  Instead I got to report ubiquity preventing me from reporting a bug

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat May 22 13:36:26 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-05-14 (8 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1929292] Re: ubiquity crashes whilst trying to use ubuntu-bug

[Launchpad Bug Tracker]

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

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

Title:
  ubiquity crashes whilst trying to use ubuntu-bug

Status in apport package in Ubuntu:
  In Progress

Bug description:
  Multiple identities can be used for authentication:
   1.  user,,, (user)
   2.  Jon Thackray,,, (jon)
  Choose identity to authenticate as (1-2): 2
  Password: 
  polkit-agent-helper-1: pam_authenticate failed: Authentication failure
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.
  ERROR: hook /usr/share/apport/package-hooks/source_ubiquity.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_ubiquity.py", line 158, in 
add_info
  add_installation_log(report, 'Casper', 'casper.log')
File "/usr/share/apport/package-hooks/source_ubiquity.py", line 29, in 
add_installation_log
  if isinstance(report[ident], bytes):
File "/usr/lib/python3.8/collections/__init__.py", line 1010, in __getitem__
  raise KeyError(key)
  KeyError: 'Casper'

  My installation doesn't have /var/log/partman

  jon@frobenius:/var/lib$ lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  jon@frobenius:/var/lib$ apt-cache policy ubiquity
  ubiquity:
Installed: (none)
Candidate: 20.04.15.11
Version table:
   20.04.15.11 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   20.04.15 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  I expected to be able to report a bug I've found in qmail-run, but
  this seems to be a barrier to entry

  Instead I got to report ubiquity preventing me from reporting a bug

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat May 22 13:36:26 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-05-14 (8 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1929292] Re: ubiquity crashes whilst trying to use ubuntu-bug

[Brian Murray]

** Package changed: ubiquity (Ubuntu) => apport (Ubuntu)

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

Title:
  ubiquity crashes whilst trying to use ubuntu-bug

Status in apport package in Ubuntu:
  In Progress

Bug description:
  Multiple identities can be used for authentication:
   1.  user,,, (user)
   2.  Jon Thackray,,, (jon)
  Choose identity to authenticate as (1-2): 2
  Password: 
  polkit-agent-helper-1: pam_authenticate failed: Authentication failure
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.
  ERROR: hook /usr/share/apport/package-hooks/source_ubiquity.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_ubiquity.py", line 158, in 
add_info
  add_installation_log(report, 'Casper', 'casper.log')
File "/usr/share/apport/package-hooks/source_ubiquity.py", line 29, in 
add_installation_log
  if isinstance(report[ident], bytes):
File "/usr/lib/python3.8/collections/__init__.py", line 1010, in __getitem__
  raise KeyError(key)
  KeyError: 'Casper'

  My installation doesn't have /var/log/partman

  jon@frobenius:/var/lib$ lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  jon@frobenius:/var/lib$ apt-cache policy ubiquity
  ubiquity:
Installed: (none)
Candidate: 20.04.15.11
Version table:
   20.04.15.11 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   20.04.15 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  I expected to be able to report a bug I've found in qmail-run, but
  this seems to be a barrier to entry

  Instead I got to report ubiquity preventing me from reporting a bug

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat May 22 13:36:26 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2021-05-14 (8 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1929292] [NEW] ubiquity crashes whilst trying to use ubuntu-bug

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Multiple identities can be used for authentication:
 1.  user,,, (user)
 2.  Jon Thackray,,, (jon)
Choose identity to authenticate as (1-2): 2
Password: 
polkit-agent-helper-1: pam_authenticate failed: Authentication failure
 AUTHENTICATION FAILED ===
Error executing command as another user: Not authorized

This incident has been reported.
ERROR: hook /usr/share/apport/package-hooks/source_ubiquity.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook
symb['add_info'](report, ui)
  File "/usr/share/apport/package-hooks/source_ubiquity.py", line 158, in 
add_info
add_installation_log(report, 'Casper', 'casper.log')
  File "/usr/share/apport/package-hooks/source_ubiquity.py", line 29, in 
add_installation_log
if isinstance(report[ident], bytes):
  File "/usr/lib/python3.8/collections/__init__.py", line 1010, in __getitem__
raise KeyError(key)
KeyError: 'Casper'

My installation doesn't have /var/log/partman

jon@frobenius:/var/lib$ lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04

jon@frobenius:/var/lib$ apt-cache policy ubiquity
ubiquity:
  Installed: (none)
  Candidate: 20.04.15.11
  Version table:
 20.04.15.11 500
500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
 20.04.15 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

I expected to be able to report a bug I've found in qmail-run, but this
seems to be a barrier to entry

Instead I got to report ubiquity preventing me from reporting a bug

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat May 22 13:36:26 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
InstallationDate: Installed on 2021-05-14 (8 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
SourcePackage: ubiquity
Symptom: installation
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal rls-ff-incoming ubiquity-20.04.15.10
-- 
ubiquity crashes whilst trying to use ubuntu-bug
https://bugs.launchpad.net/bugs/1929292
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apport in Ubuntu.

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

[Touch-packages] [Bug 1929754] Re: Influx installed without my installing it

[Dan Streetman]

You can remove debs or snaps from your system if you want, of course,
subject to whatever dependency requirements for packages/applications
that you want on your system.

In any case there doesn't appear to be any bug here, so I'll close this
bug report.

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

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

Title:
  Influx installed without my installing it

Status in systemd package in Ubuntu:
  Invalid

Bug description:
   On my webserver, recently upgraded to 21.04, I am chasing some
  security issues and I find two instances of influxdb running.

   That's interesting because I never installed it, further checking
  apt it shows NOT installed, yet, there it is.

   The parent process is systemd, of course fucking Poettering polluting my 
system again, and
  it seems to be linked to the lingering function of systemd sessions.

   I don't want it, is there a way to get rid of it other than
  replacing Ubuntu with a non systemd Linux like mxlinux?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.6
  Uname: Linux 5.12.4 x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Wed May 26 14:51:10 2021
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.12.4 
root=UUID=a9844279-752c-4aeb-9338-a7771c7b5d06 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1ubuntu1.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-eoan
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-eoan:cvnQEMU:ct1:cvrpc-i440fx-eoan:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-eoan
  dmi.sys.vendor: QEMU

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

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

[Touch-packages] [Bug 1926547] Re: Add Dell Privacy Mic Mute Key mapping

[Dan Streetman]

I uploaded the patched systemd to the groovy queue already; will the
patch for this bug actually break/regress anything? if not then let's
leave it in

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

Title:
  Add Dell Privacy Mic Mute Key mapping

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
     GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * The change can only work with kernel commit on some specific hardware, ex. 
Latitude 9520. The commit series is 
"hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree.
     https://patchwork.kernel.org/project/alsa-devel/list/?series=465445
   * This change has been verified on Dell machine.

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

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

[Touch-packages] [Bug 1929849] [NEW] ftbfs on hirsute due to kernel changing type of RFKILL_EVENT_SIZE_V1

[Dan Streetman]

Public bug reported:

[impact]

ftbfs

[test case]

try to build, e.g.:

https://launchpadlibrarian.net/540746512/buildlog_ubuntu-hirsute-
amd64.systemd_247.3-3ubuntu3.1_BUILDING.txt.gz

../src/rfkill/rfkill.c: In function ‘load_state’:
../src/rfkill/rfkill.c:180:15: warning: comparison of integer expressions of 
different signedness: ‘ssize_t’ {aka ‘long int’} and ‘long unsigned int’ 
[-Wsign-compare]
  180 | if (l < RFKILL_EVENT_SIZE_V1)

[regression potential]

any regression would likely cause ftbfs or could cause improper
reading/parsing of the kernel rfkill data

[scope]

this is needed only for h

this is fixed upstream in systemd by commit ab1aa6368a8 which was pulled
into i already.

this does not exist for g or earlier, as the upstream kernel commit
71826654ce401 changed the macro value and introduced this problem, and
that was first included in kernel v5.12 and then backported into hirsute
v5.11 kernel in commit a8c36c7222055 which was first included in
Ubuntu-5.11.0-18.19

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

** Affects: systemd (Ubuntu Hirsute)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

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

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

** Changed in: systemd (Ubuntu Hirsute)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Hirsute)
   Importance: Undecided => Medium

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

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

Title:
  ftbfs on hirsute due to kernel changing type of RFKILL_EVENT_SIZE_V1

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Hirsute:
  In Progress

Bug description:
  [impact]

  ftbfs

  [test case]

  try to build, e.g.:

  https://launchpadlibrarian.net/540746512/buildlog_ubuntu-hirsute-
  amd64.systemd_247.3-3ubuntu3.1_BUILDING.txt.gz

  ../src/rfkill/rfkill.c: In function ‘load_state’:
  ../src/rfkill/rfkill.c:180:15: warning: comparison of integer expressions of 
different signedness: ‘ssize_t’ {aka ‘long int’} and ‘long unsigned int’ 
[-Wsign-compare]
180 | if (l < RFKILL_EVENT_SIZE_V1)

  [regression potential]

  any regression would likely cause ftbfs or could cause improper
  reading/parsing of the kernel rfkill data

  [scope]

  this is needed only for h

  this is fixed upstream in systemd by commit ab1aa6368a8 which was
  pulled into i already.

  this does not exist for g or earlier, as the upstream kernel commit
  71826654ce401 changed the macro value and introduced this problem, and
  that was first included in kernel v5.12 and then backported into
  hirsute v5.11 kernel in commit a8c36c7222055 which was first included
  in Ubuntu-5.11.0-18.19

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

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

[Touch-packages] [Bug 1916418] Re: Custom properties set with ENV{WHATEVER} in parent no longer imported with IMPORT{parent} in udev rule

[Jonathan Kamens]

This appears to no longer be an issue with the current versions of
systemd and udev in 21.04.


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

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

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

Title:
  Custom properties set with ENV{WHATEVER} in parent no longer imported
  with IMPORT{parent} in udev rule

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Invalid
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  DisplayLink uses these udev rules to start the displaylink service
  when a displaylink device is plugged in:

  ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb",
  ATTR{idVendor}=="17e9", IMPORT{builtin}="usb_id",
  ENV{DISPLAYLINK_DEVNAME}="$env{DEVNAME}",
  
ENV{DISPLAYLINK_DEVICE_ID}="$env{ID_BUS}-$env{BUSNUM}-$env{DEVNUM}-$env{ID_SERIAL}",
  ENV{REMOVE_CMD}="/opt/displaylink/udev.sh $root
  $env{DISPLAYLINK_DEVICE_ID} $env{DISPLAYLINK_DEVNAME}"

  ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb",
  ATTRS{idVendor}=="17e9", ATTR{bInterfaceClass}=="ff",
  ATTR{bInterfaceProtocol}=="03", IMPORT{parent}="DISPLAYLINK*",
  RUN+="/opt/displaylink/udev.sh $root $env{DISPLAYLINK_DEVICE_ID}
  $env{DISPLAYLINK_DEVNAME}"

  The important thing to note here is that the first rule is for the
  device that is the parent of the device triggers the second rule, and
  the first rule sets ENV{DISPLAYLINK_DEVNAME} and
  ENV{DISPLAYLINK_DEVICE_ID}, and the second rule attempts to import
  them with IMPORT{parent} and then use them.

  This worked fine in 20.04.

  It does not work in 21.04.

  When the second rule is triggered, DISPLAYLINK_DEVICE_ID and
  DISPLAYLINK_DEVNAME are not set.

  I have confirmed via udevadm monitor that the variables are getting
  set on the parent.

  I have confirmed via udevadm info --attribute-walk that the device
  triggering the second rule is the child of the device triggering the
  first one.

  I have tried to import the variables explicitly instead of using a
  glob pattern and that doesn't work either.

  When I modify the rule to import DEVNAME, ID_BUS, BUSNUM, DEVNUM, and
  ID_SERIAL directly, that works. The problem appears to be that these
  custom properties we are setting in the parent can't be imported in
  the child.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: udev 247.3-1ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 60-brother-libsane-type1.rules 99-displaylink.rules~ 
70-snap.core.rules 70-snap.snap-store.rules 99-x10.rules 
60-brother-brscan4-libsane-type1.rules 50-yubikey.rules 
70-snap.canonical-livepatch.rules 70-snap.gnome-system-monitor.rules 
70-snap.chromium.rules 99-displaylink.rules
  Date: Sun Feb 21 19:21:20 2021
  InstallationDate: Installed on 2019-01-02 (781 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to hirsute on 2021-02-21 (0 days ago)
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1925823] Re: losts or misinterprets the newline character coming from mouse paste

[Péter Prőhle]

In addition to the correct behaviour of the GNU bash, I will not get
that disturbing fancy behaviour of the Ubuntu 21.04 version, that

instead of executing the command

the dropped command is shown in reverse video.

Hence the bug in question is clearly an Ubuntu re-packaging issue.

** Summary changed:

- losts or misinterprets the newline character coming from mouse paste
+ Ubuntu version of BASH losts or misinterprets the newline character coming 
from mouse paste

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

Title:
  Ubuntu version of BASH losts or misinterprets the newline character
  coming from mouse paste

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  Quiete a few experients shows, that bash misinterprets the newline-
  character coming from mouse paste, while in the same terminals the
  emacs or vim or alpine and many other character oriented programs
  interprest correctly.

  The problem is specific to the situation when we are at a bash prompt
  of a new version of bash we got in Ubuntu 21.04. As soon as I invoke
  an ssh session, the interpretation of the newline-caharcter becomes
  correct, since the remote older bash interprets correctly.

  >>> Newline bug of first kind:

  If there is a complete bash command with terminating newline in the
  cut and paste buffer,

  and it is pasted into a gnome-terminal,

  then the command is *not* executed, the newline is ignored by the
  terminal.

  >>> Newline bug of second kind:

  If I prepare a bash command say

  cp  target-directory

  and I collect into the paste buffer "source-file newline-character"

  and I drop it IN BETWEEN the prepared "cp" and "target-directory"

  then the result is wrong:

  instead of interpreting the newline-character as "push enter"

  the command is broken into the followint 2 lines:

  cp source-file

  target-directory

  and I get an error message about missing target specification.

  cp: missing destination file operand after 'source-file'
  Try 'cp --help' for more information.
  bash: target-directory: Is a directory

  I found better to make this original bug descripton more informative.

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

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

[Touch-packages] [Bug 1925823] Re: losts or misinterprets the newline character coming from mouse paste

[Péter Prőhle]

The bug is NOT the error of the original GNU package, but of the way how
it is integrated into the Ubuntu 21.04, because if I download the GNU
package itself, compile and try, then it works fine.

In detail what I did:

mkdir -p ~/bash

cd   ~/bash

rm -fr bash-*

sudo apt-get -y install byacc

wget https://ftp.gnu.org/gnu/bash/bash-5.1.tar.gz

tar xvzf bash-*.tar.gz
rm   bash-*.tar.gz
cd   bash-*

time ( ./configure ; make )

env -i PATH="$PWD:$PATH" ./bash --noprofile --norc

and here if I do the same cut and paste tests, and drop a command with a
terminating line feed character, then this bash binary will simply
execute it ...

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

Title:
  Ubuntu version of BASH losts or misinterprets the newline character
  coming from mouse paste

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  Quiete a few experients shows, that bash misinterprets the newline-
  character coming from mouse paste, while in the same terminals the
  emacs or vim or alpine and many other character oriented programs
  interprest correctly.

  The problem is specific to the situation when we are at a bash prompt
  of a new version of bash we got in Ubuntu 21.04. As soon as I invoke
  an ssh session, the interpretation of the newline-caharcter becomes
  correct, since the remote older bash interprets correctly.

  >>> Newline bug of first kind:

  If there is a complete bash command with terminating newline in the
  cut and paste buffer,

  and it is pasted into a gnome-terminal,

  then the command is *not* executed, the newline is ignored by the
  terminal.

  >>> Newline bug of second kind:

  If I prepare a bash command say

  cp  target-directory

  and I collect into the paste buffer "source-file newline-character"

  and I drop it IN BETWEEN the prepared "cp" and "target-directory"

  then the result is wrong:

  instead of interpreting the newline-character as "push enter"

  the command is broken into the followint 2 lines:

  cp source-file

  target-directory

  and I get an error message about missing target specification.

  cp: missing destination file operand after 'source-file'
  Try 'cp --help' for more information.
  bash: target-directory: Is a directory

  I found better to make this original bug descripton more informative.

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

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

[Touch-packages] [Bug 1925823] Re: losts or misinterprets the newline character coming from mouse paste

[Péter Prőhle]

If I remain inside Ubuntu 21.04, but compile the previous version of
bash, then the error disappears, ... this suggest that the erorr is not
the consequence of the version of Ubuntu, but the "bash, version
5.1.4(1)-release" itself, or perhaps an Ubuntu specific configuration of
the environment.  In detail:

mkdir ~/bash

cd ~/bash

wget https://ftp.gnu.org/gnu/bash/bash-5.0.tar.gz

tar xvzf bash-5.0.tar.gz

cd bash-5.0

sudo apt-get install byacc

./configure

make

env -i PATH="$PWD:$PATH" ./bash --noprofile --norc

and here if I drop something containing a line feed character, the bash
will correctly execute the currently edited commandline

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

Title:
  losts or misinterprets the newline character coming from mouse paste

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  Quiete a few experients shows, that bash misinterprets the newline-
  character coming from mouse paste, while in the same terminals the
  emacs or vim or alpine and many other character oriented programs
  interprest correctly.

  The problem is specific to the situation when we are at a bash prompt
  of a new version of bash we got in Ubuntu 21.04. As soon as I invoke
  an ssh session, the interpretation of the newline-caharcter becomes
  correct, since the remote older bash interprets correctly.

  >>> Newline bug of first kind:

  If there is a complete bash command with terminating newline in the
  cut and paste buffer,

  and it is pasted into a gnome-terminal,

  then the command is *not* executed, the newline is ignored by the
  terminal.

  >>> Newline bug of second kind:

  If I prepare a bash command say

  cp  target-directory

  and I collect into the paste buffer "source-file newline-character"

  and I drop it IN BETWEEN the prepared "cp" and "target-directory"

  then the result is wrong:

  instead of interpreting the newline-character as "push enter"

  the command is broken into the followint 2 lines:

  cp source-file

  target-directory

  and I get an error message about missing target specification.

  cp: missing destination file operand after 'source-file'
  Try 'cp --help' for more information.
  bash: target-directory: Is a directory

  I found better to make this original bug descripton more informative.

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

-- 
Mailing list: https://launchpad.net/~touch-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,

I did not forgot this, but I reallt didn' t have time to test in a VM.

But, I've installed a new machine with same OS (KDE Neon 20.04) and the
same thing happens.

So, like I said before, this does not happen don upgraded machine from
18.04 to 20.04.

I will try to test in VM with Gnome desktop (and Ubuntu 20.04) as soon
as I can.

-- 
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 1929833] [NEW] bluez: meshctl missing

[Markus Becker]

Public bug reported:

bluez has added a new tool for BT mesh handling.

Debian has a new binary package: https://packages.debian.org/bullseye
/bluez-meshd

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

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

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

Title:
  bluez: meshctl missing

Status in bluez package in Ubuntu:
  New

Bug description:
  bluez has added a new tool for BT mesh handling.

  Debian has a new binary package: https://packages.debian.org/bullseye
  /bluez-meshd

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

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

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

[Touch-packages] [Bug 1774632] Re: The symbolic link /etc/resolv.conf points to the wrong file by default

[Per Olav Kroka]

I just want to confirm that this is a problem.  I have had it for a
while and not found another workaround (until now) than restarting the
machine.

If this is NOT a bug then something "close by" is a bug.

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

Title:
  The symbolic link /etc/resolv.conf points to the wrong file by default

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When using nslookup for local machine names, the local DNS was being
  ignored (not queried) and none of the local machines could be found.

  After much research and digging, it was discovered that the cause was
  the incorrect symbolic link /etc/resolv.conf file.

  The default install caused systemd-resolve to configure the link to point to 
the stub file:
  /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

  Reomving that link and pointing it to the correct file solved the DNS lookup 
issue. The correct link looks like this:
  /etc/resolv.conf -> /run/systemd/resolve/resolv.conf

  
  Steps used to test the bug before fixing the link is to perform an nslookup 
on a local (non FQDN) machine that is in your local DNS (my router is my DNS 
server for this case) Here is an example of the incorrect output:

  $ nslookup web1

  Server: 127.0.0.53
  Address:127.0.0.53#53

  ** server can't find web1: SERVFAIL

  
  Switching the symbolic link solves the problem. Here is my solution:

  $ sudo rm -f /etc/resolv.conf
  $ sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

  
  After switching the symbolic link, the nslookup functions properly.

  $ nslookup web1

  Server: 192.168.1.1
  Address:192.168.1.1#53

  Name:   web1
  Address: 192.168.1.107

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  1 05:28:41 2018
  InstallationDate: Installed on 2018-01-20 (131 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. Inspiron 5755
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=7fe151d3-4033-4903-b356-341d9f16e124 ro acpi=force
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2018-04-28 (33 days ago)
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0VY15F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/27/2015:svnDellInc.:pnInspiron5755:pvrA08:rvnDellInc.:rn0VY15F:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 5755
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1929824] [NEW] Icons do not appear in the Qt version of "Software & Updates"

[Omer I.S.]

Public bug reported:

Icons (excluding "V" icons) do not appear in the Qt version of "Software
& Updates".

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Icons do not appear in the Qt version of "Software & Updates"

Status in software-properties package in Ubuntu:
  New

Bug description:
  Icons (excluding "V" icons) do not appear in the Qt version of
  "Software & Updates".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1929824/+subscriptions

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

[Touch-packages] [Bug 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged

[Hui Wang]

@seb128,

There is one more pulseaudio SRU for focal, if possible, could you
please merge them to be a single upload.

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1929817

Thanks.

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

Title:
  [SRU] there is always a "Rear Microphone - Built-in Audio" option on
  the input device list even if the microphone is unplugged

Status in OEM Priority Project:
  Triaged
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]
  In Lenovo P520, which using a codec for front panel, the other codec for rear 
panel and both are on a same card.

  In this case, the rear Mic will present on input devices of "Sound
  Settings" even if attaching nothing to rear mic jack.

  [Fix]
  For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl 
because of
  ```
control.18 {
iface CARD
name 'Rear Mic Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
  ```
  After applying "Rear Mic Jack", the rear Mic will not always there anymore 
but it's not there as well if hot-plugging audio device on rear mic. Thus, it 
needs to change pulseaudio to handle if all devices are off cases.

  For pulseaudio, if there is no any audio devices attached, then
  attaching an input device on rear mic jack. The port will not be
  selected automatically because the profiles is off. It needs patch
  pulseaudio to check off profiles (for dual codec case).

  [Test]
  After applying these patches, the rear mic jack works good in all cases (boot 
without mic and then attach mic, boot with mic and then hotplug it) and other 
functions (line-in / line-out) work pretty well.

  [Where problems could occur]
  This change only apply the bonus on below cases:
  ```
  if ((has_input_port && found_available_input_port && !has_output_port) ||
  (has_output_port && found_available_output_port && !has_input_port) ||
  (has_input_port && found_available_input_port && has_output_port && 
found_available_output_port)) 
  ```
  and these cases have been tested.
  If there are some complex codec design then it might cause problem but so far 
we didn't see that.

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

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

[Touch-packages] [Bug 1929817] Re: [SRU] pulseaudio: let a signle alsa mixer support up to 8 channels

[Hui Wang]

** Description changed:

- This is for tracking purpose.
+ [Impact]
+ Many Lenovo laptops have up to 4 microphones (microphone array), before the 
linux kernel 5.11, the alsa mixer for digital microphone is 2 channels, and the 
PA in the focal also supports up to 2 chanels for a single alsa mixer, so the 
PA in the focal works well with linux kernel 5.10 and lower on those Lenovo 
laptops. But we are going to install hirsute kernel (5.11) to the focal, the PA 
in the focal can't handle 4 channels of the digital mic, it will use pure 
software volume for digital mic, user can't adjust hardware volume of the 
digital mic anymore.
+ 
+ 
+ [Fix]
+ Backport 2 patches from PA-14.2, the PA in the hirsute (21.04) already have 
these 2 patches, so this SRU is for focal only. After applying these 2 patches, 
the PA could handle up to 8 channels for a single alsa mixer. 
+ 
+ [Test]
+ Install patched PA on Lenovo laptops with 4 digital microphone, I could 
change the hardware input volume of digital mic through pulseaudio. I also 
installed patched PA to some old lenovo and Dell machines, all output and input 
devices worked as well as before, there is no regression observed.
+ 
+ [Where problems could occur]
+ This could introduce a regression on the output/input volume control, for 
example, the output or input volume only supports software volume in the PA, 
users can't adjust the hardware volume through pulseaudio anymore. But this 
regression possibility is very low, first the hirsute already has these 2 
patches, second I already tested these 2 patches on different machines, all 
worked as well as before.

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

Title:
  [SRU] pulseaudio: let a signle alsa mixer support up to 8 channels

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

Bug description:
  [Impact]
  Many Lenovo laptops have up to 4 microphones (microphone array), before the 
linux kernel 5.11, the alsa mixer for digital microphone is 2 channels, and the 
PA in the focal also supports up to 2 chanels for a single alsa mixer, so the 
PA in the focal works well with linux kernel 5.10 and lower on those Lenovo 
laptops. But we are going to install hirsute kernel (5.11) to the focal, the PA 
in the focal can't handle 4 channels of the digital mic, it will use pure 
software volume for digital mic, user can't adjust hardware volume of the 
digital mic anymore.

  
  [Fix]
  Backport 2 patches from PA-14.2, the PA in the hirsute (21.04) already have 
these 2 patches, so this SRU is for focal only. After applying these 2 patches, 
the PA could handle up to 8 channels for a single alsa mixer. 

  [Test]
  Install patched PA on Lenovo laptops with 4 digital microphone, I could 
change the hardware input volume of digital mic through pulseaudio. I also 
installed patched PA to some old lenovo and Dell machines, all output and input 
devices worked as well as before, there is no regression observed.

  [Where problems could occur]
  This could introduce a regression on the output/input volume control, for 
example, the output or input volume only supports software volume in the PA, 
users can't adjust the hardware volume through pulseaudio anymore. But this 
regression possibility is very low, first the hirsute already has these 2 
patches, second I already tested these 2 patches on different machines, all 
worked as well as before.

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

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

[Touch-packages] [Bug 1929817] Re: [SRU] pulseaudio: let a signle alsa mixer support up to 8 channels

[Hui Wang]

This is the debdiff for focal. Thx.


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

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

Title:
  [SRU] pulseaudio: let a signle alsa mixer support up to 8 channels

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

Bug description:
  This is for tracking purpose.

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

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

[Touch-packages] [Bug 1929817] [NEW] [SRU] pulseaudio: let a signle alsa mixer support up to 8 channels

[Hui Wang]

Public bug reported:

This is for tracking purpose.

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

** Affects: pulseaudio (Ubuntu Focal)
 Importance: High
 Status: In Progress

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

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

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

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

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

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

Title:
  [SRU] pulseaudio: let a signle alsa mixer support up to 8 channels

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

Bug description:
  This is for tracking purpose.

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

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

[Touch-packages] [Bug 1785383] Re: missing EDNS0 record confuses systemd-resolved

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/403382

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

Title:
  missing EDNS0 record confuses systemd-resolved

Status in systemd:
  Fix Released
Status in dnsmasq package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in dnsmasq source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  In Progress
Status in dnsmasq source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in dnsmasq source package in Groovy:
  Fix Released
Status in systemd source package in Groovy:
  In Progress
Status in dnsmasq source package in Hirsute:
  Fix Released
Status in systemd source package in Hirsute:
  In Progress
Status in dnsmasq source package in Impish:
  Fix Released
Status in systemd source package in Impish:
  Triaged

Bug description:
  [Impact]
  dnsmasq 2.79 and below omits EDNS0 OPT records when returning an empty answer 
for a domain it is authoritative for. systemd-resolved seems to get confused by 
this in certain circumstances; when using the stub resolver and requesting an 
address for which there are no  records, there can sometimes be a five 
second hang in resolution.

  [Fix]
  This is fixed by upstream commit 
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78

  Not sure if it is worth cherry picking? I imagine the most likely
  trigger will be dnsmasq on routers which are not likely to be running
  Ubuntu, but maybe just in case.

  I also think there are some logic issues in systemd-resolved, upstream
  bug filed:

  https://github.com/systemd/systemd/issues/9785

  [Test Case]
  Simple-ish test case for bionic:

  ---
  IFACE=dummy0
  SUBNET=10.0.0

  ip link add $IFACE type dummy
  ifconfig $IFACE ${SUBNET}.1/24
  dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo 
--host-record=test.test,${SUBNET}.1 --server=/test/ &

  dig -t a test.test @10.0.0.1 | grep EDNS
  # should return "; EDNS ..."
  dig -t  test.test @10.0.0.1 | grep EDNS
  # again, should return "; EDNS ..." but doesn't
  ---

  To reproduce the systemd-resolved side of the problem

  ---
  # as above, but
  # now configure systemd-resolved to look at only 10.0.0.1, then

  systemd-resolve --reset-server-features
  # should exhibit five second delay then connect, assuming sshd is running :)
  ssh test.test
  ---

  
  More detailed test case for focal and later:

  install dnsmasq on a bionic system and start it, listening to an
  interface that is externally reachable, e.g. for a normal libvirt vm
  with interface name 'ens3':

  IFACE=ens3
  dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo 
--host-record=test.test,1.2.3.4 --server=/test/

  note that the '1.2.3.4' address doesn't matter, any addr is ok.

  then setup a test system that can reach the dnsmasq system, and
  configure networkd to use the dnsmasq server, e.g. using config like:

  [Match]
  Name=ens3

  [Network]
  DHCP=yes
  DNS=DNSMASQ_IP_ADDRESS
  Domains=test

  [DHCPv4]
  UseDNS=no
  UseDomains=no

  replace 'DNSMASQ_IP_ADDRESS' with the addr of the bionic system where
  dnsmasq is running, and replace 'ens3' with whatever the test system
  interface name is. Then restart systemd-networkd, and test:

  systemd-resolve --reset-server-features
  systemd-resolve --flush-caches
  host test.test

  The lookup using 'host' should complete immediately;.

  [Discussion]
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dnsmasq-base 2.79-1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sat Aug  4 11:33:56 2018
  InstallationDate: Installed on 2018-05-31 (64 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1785383] Re: missing EDNS0 record confuses systemd-resolved

[Dan Streetman]

** Description changed:

  [Impact]
  dnsmasq 2.79 and below omits EDNS0 OPT records when returning an empty answer 
for a domain it is authoritative for. systemd-resolved seems to get confused by 
this in certain circumstances; when using the stub resolver and requesting an 
address for which there are no  records, there can sometimes be a five 
second hang in resolution.
  
  [Fix]
  This is fixed by upstream commit 
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78
  
  Not sure if it is worth cherry picking? I imagine the most likely
  trigger will be dnsmasq on routers which are not likely to be running
  Ubuntu, but maybe just in case.
  
  I also think there are some logic issues in systemd-resolved, upstream
  bug filed:
  
  https://github.com/systemd/systemd/issues/9785
  
  [Test Case]
- Simple-ish test case:
+ Simple-ish test case for bionic:
  
  ---
  IFACE=dummy0
  SUBNET=10.0.0
  
  ip link add $IFACE type dummy
  ifconfig $IFACE ${SUBNET}.1/24
- dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo 
--host-record=test.test,${SUBNET}.1 &
+ dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo 
--host-record=test.test,${SUBNET}.1 --server=/test/ &
  
  dig -t a test.test @10.0.0.1 | grep EDNS
  # should return "; EDNS ..."
  dig -t  test.test @10.0.0.1 | grep EDNS
  # again, should return "; EDNS ..." but doesn't
  ---
  
  To reproduce the systemd-resolved side of the problem
  
  ---
  # as above, but
  # now configure systemd-resolved to look at only 10.0.0.1, then
  
  systemd-resolve --reset-server-features
  # should exhibit five second delay then connect, assuming sshd is running :)
  ssh test.test
  ---
+ 
+ 
+ More detailed test case for focal and later:
+ 
+ install dnsmasq on a bionic system and start it, listening to an
+ interface that is externally reachable, e.g. for a normal libvirt vm
+ with interface name 'ens3':
+ 
+ IFACE=ens3
+ dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo 
--host-record=test.test,1.2.3.4 --server=/test/
+ 
+ note that the '1.2.3.4' address doesn't matter, any addr is ok.
+ 
+ then setup a test system that can reach the dnsmasq system, and
+ configure networkd to use the dnsmasq server, e.g. using config like:
+ 
+ [Match]
+ Name=ens3
+ 
+ [Network]
+ DHCP=yes
+ DNS=DNSMASQ_IP_ADDRESS
+ Domains=test
+ 
+ [DHCPv4]
+ UseDNS=no
+ UseDomains=no
+ 
+ replace 'DNSMASQ_IP_ADDRESS' with the addr of the bionic system where
+ dnsmasq is running, and replace 'ens3' with whatever the test system
+ interface name is. Then restart systemd-networkd, and test:
+ 
+ systemd-resolve --reset-server-features
+ systemd-resolve --flush-caches
+ host test.test
+ 
+ The lookup using 'host' should complete immediately;.
  
  [Discussion]
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dnsmasq-base 2.79-1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sat Aug  4 11:33:56 2018
  InstallationDate: Installed on 2018-05-31 (64 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  missing EDNS0 record confuses systemd-resolved

Status in systemd:
  Fix Released
Status in dnsmasq package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in dnsmasq source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  In Progress
Status in dnsmasq source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in dnsmasq source package in Groovy:
  Fix Released
Status in systemd source package in Groovy:
  In Progress
Status in dnsmasq source package in Hirsute:
  Fix Released
Status in systemd source package in Hirsute:
  In Progress
Status in dnsmasq source package in Impish:
  Fix Released
Status in systemd source package in Impish:
  Triaged

Bug description:
  [Impact]
  dnsmasq 2.79 and below omits EDNS0 OPT records when returning an empty answer 
for a domain it is authoritative for. systemd-resolved seems to get confused by 
this in certain circumstances; when using the stub resolver and requesting an 
address for which there are no  records, there can sometimes be a five 
second hang in resolution.

  [Fix]
  This is fixed by upstream commit 
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78

  Not sure if it is worth cherry picking? I imagine the most likely
  trigger will be dnsmasq on routers which are not likely to be running
  

[Touch-packages] [Bug 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged

[Sebastien Bacher]

Uploaded to focal, 20.10 is probably not worth doing at this point

** No longer affects: alsa-ucm-conf (Ubuntu Groovy)

** No longer affects: pulseaudio (Ubuntu Groovy)

** Changed in: alsa-ucm-conf (Ubuntu Focal)
   Status: New => Fix Committed

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

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

Title:
  [SRU] there is always a "Rear Microphone - Built-in Audio" option on
  the input device list even if the microphone is unplugged

Status in OEM Priority Project:
  Triaged
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]
  In Lenovo P520, which using a codec for front panel, the other codec for rear 
panel and both are on a same card.

  In this case, the rear Mic will present on input devices of "Sound
  Settings" even if attaching nothing to rear mic jack.

  [Fix]
  For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl 
because of
  ```
control.18 {
iface CARD
name 'Rear Mic Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
  ```
  After applying "Rear Mic Jack", the rear Mic will not always there anymore 
but it's not there as well if hot-plugging audio device on rear mic. Thus, it 
needs to change pulseaudio to handle if all devices are off cases.

  For pulseaudio, if there is no any audio devices attached, then
  attaching an input device on rear mic jack. The port will not be
  selected automatically because the profiles is off. It needs patch
  pulseaudio to check off profiles (for dual codec case).

  [Test]
  After applying these patches, the rear mic jack works good in all cases (boot 
without mic and then attach mic, boot with mic and then hotplug it) and other 
functions (line-in / line-out) work pretty well.

  [Where problems could occur]
  This change only apply the bonus on below cases:
  ```
  if ((has_input_port && found_available_input_port && !has_output_port) ||
  (has_output_port && found_available_output_port && !has_input_port) ||
  (has_input_port && found_available_input_port && has_output_port && 
found_available_output_port)) 
  ```
  and these cases have been tested.
  If there are some complex codec design then it might cause problem but so far 
we didn't see that.

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

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

[Touch-packages] [Bug 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix

[Launchpad Bug Tracker]

This bug was fixed in the package pam - 1.1.8-3.6ubuntu2.18.04.3

---
pam (1.1.8-3.6ubuntu2.18.04.3) bionic; urgency=medium

  * Backport pam_faillock module from pam 1.4.0 (LP: #1927796)
- debian/patches-applied/add_pam_faillock.patch: add module.
- debian/patches-applied/pam_faillock_create_directory: create dir
  before creating file in modules/pam_faillock/faillock.c.
- debian/rules: set execute permissions on pam_faillock test.
- debian/libpam-modules-bin.install: install faillock binary and man
  page.

 -- Marc Deslauriers   Thu, 08 Apr 2021
07:27:58 -0400

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

Title:
  [SRU]pam_tally2 can cause accounts to be locked by correct password.
  pam_faillock use is the recommended fix

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Bionic:
  Fix Released
Status in pam source package in Focal:
  Fix Released
Status in pam source package in Groovy:
  Fix Released
Status in pam source package in Hirsute:
  Fix Released
Status in pam source package in Impish:
  Fix Released

Bug description:
  [IMPACT]
  There is a known issue in pam_tally2 which may cause an account to be lock 
down even with correct password, in a busy node environment where simultaneous 
logins takes place (https://github.com/linux-pam/linux-pam/issues/71).

  There are already two customer cases from Canonical clients
  complaining about this behavior (00297697 and 00303806).

  Also, potentially, this will cause further problems in the future,
  since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to
  lock accounts when wrong passwords are used. And both benchmarks - but
  specially STIG - requires use of a lot of audit rules, which can lead
  to the busy node environment.

  The issue impacts all pam_tally2 versions distributed in all currently
  supported Ubuntu versions and also the next unreleased one. Note that,
  according to https://github.com/linux-pam/linux-pam/issues/71, there
  is no plan to fix this issue!

  [FIX]
  This fix proposes to add pam_faillock module to the PAM package, so users of 
pam_tally2 having issues can migrate to pam_faillock. We also plan to modify 
the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but 
in order to do so, we need the pam_faillock module to be available.

  Note that we don't propose to remove pam_tally2, since not every user
  of this module is affected.

  [TEST]
  Tested on a VM installed with Focal server iso and on another with Bionic 
server iso. Enabled pam_faillock module as recommeded by its man page. Then 
tried to log over ssh with an incorrect password, until the account got locked. 
Waited for the configured grace time to unlock and logged in using the correct 
password.

  Note that, since the pam_tally2 issue is caused by a racing condition,
  with a hard to recreate environment (we could not even reproduce it
  with pam_tally2), we could not reproduce the conditions to test
  pam_faillock with.

  [REGRESSION POTENTIAL]
  The regression potential for this is small, since we're not removing the old 
pam_tally2 module, just adding another one. So anyone still using pam_tally2 
will be able to do so.

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

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

[Touch-packages] [Bug 1458336] Re: Allow users to decide which apps can display anything in the circle

[Rüdiger Kupper]

See also 
https://github.com/ubports/ubuntu-touch/issues/1391#issuecomment-600214923.
It suggestes using the "circle message" app in order to display emergency data 
on the lock screen. However, it is not very useful if the message is not shown 
directly after boot.

** Bug watch added: github.com/ubports/ubuntu-touch/issues #1391
   https://github.com/ubports/ubuntu-touch/issues/1391

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

Title:
  Allow users to decide which apps can display anything in the circle

Status in Canonical System Image:
  New
Status in libusermetrics package in Ubuntu:
  Confirmed

Bug description:
  Currently a user has no control over which apps can display stuff in
  the circle. Potentially an app could show there something what a user
  do not want. It would be nice to have for example setting (like for
  notifications) which apps are allowed to use the circle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1458336/+subscriptions

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

[Touch-packages] [Bug 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged

[Sebastien Bacher]

Upload to Impish and Hirsute now, Focal is coming

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

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

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

Title:
  [SRU] there is always a "Rear Microphone - Built-in Audio" option on
  the input device list even if the microphone is unplugged

Status in OEM Priority Project:
  Triaged
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  New
Status in pulseaudio source package in Focal:
  New
Status in alsa-ucm-conf source package in Groovy:
  New
Status in pulseaudio source package in Groovy:
  New
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]
  In Lenovo P520, which using a codec for front panel, the other codec for rear 
panel and both are on a same card.

  In this case, the rear Mic will present on input devices of "Sound
  Settings" even if attaching nothing to rear mic jack.

  [Fix]
  For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl 
because of
  ```
control.18 {
iface CARD
name 'Rear Mic Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
  ```
  After applying "Rear Mic Jack", the rear Mic will not always there anymore 
but it's not there as well if hot-plugging audio device on rear mic. Thus, it 
needs to change pulseaudio to handle if all devices are off cases.

  For pulseaudio, if there is no any audio devices attached, then
  attaching an input device on rear mic jack. The port will not be
  selected automatically because the profiles is off. It needs patch
  pulseaudio to check off profiles (for dual codec case).

  [Test]
  After applying these patches, the rear mic jack works good in all cases (boot 
without mic and then attach mic, boot with mic and then hotplug it) and other 
functions (line-in / line-out) work pretty well.

  [Where problems could occur]
  This change only apply the bonus on below cases:
  ```
  if ((has_input_port && found_available_input_port && !has_output_port) ||
  (has_output_port && found_available_output_port && !has_input_port) ||
  (has_input_port && found_available_input_port && has_output_port && 
found_available_output_port)) 
  ```
  and these cases have been tested.
  If there are some complex codec design then it might cause problem but so far 
we didn't see that.

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

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

[Touch-packages] [Bug 1926843] Re: online accounts integration with fb isn't working

[Lars Martin Hambro]

its its possible to add windows 10 hello safety login?
Or button to open in browser like edge in windows 10? so its can use password 
on maskines to login? or its hard to add? did not need 2 ways login or be its 
safety issue in linux?

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

Title:
  online accounts integration with fb isn't working

Status in gnome-online-accounts package in Ubuntu:
  Fix Released
Status in gnome-online-accounts source package in Focal:
  Fix Committed
Status in gnome-online-accounts source package in Hirsute:
  Fix Committed

Bug description:
  * Impact

  The online accounts setting are proposing a facebook item which isn't
  working

  * Test case

  Go to settings -> online account, browse the accounts option proposed,
  facebook shouldn't be in the list since it doesn't work.

  * Regression potential

  The change is to disable the facebook provider using the upstream
  provided build option. Check that facebook isn't listed anymore but
  that the other providers still are. Since it's a build option change
  it could fail to build so check for that as well on launchpad.

  Since the facebook service currently doesn't consider gnome-online-
  accounts as a valid client there should be no user with that provider
  configured. Even if there were since the service isn't working they
  would see a functional regression.

  ---

  Hi i tryed to use gnome-control-center online-accounts to make easy
  like windows 10 to login to email or add other login so its more easy
  with ID to use pincode or other ID fingerprint and other.

  But its look its much issue compared with windows 10 with thunderbird,
  firefox, and other program.

  Worst is facebook only little windows with issue with login?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-online-accounts 3.38.1-1ubuntu1
  Uname: Linux 5.12.0-051200-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  1 19:38:03 2021
  InstallationDate: Installed on 2019-05-07 (725 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+subscriptions

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

[Touch-packages] [Bug 1926843] Re: online accounts integration with fb isn't working

[Lars Martin Hambro]

yes gnome-online-accounts (3.38.1-1ubuntu1.1
https://i.ibb.co/K6RGY0k/onlineaccountv2.png

But its be nice with instagram and facebook option later. Its not other
ways to fix other than hackmicrosoft to get .exe files from windows 10
stores and install in on wine and hope its works.

Sorry becouse long time but its did not help me much.

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

Title:
  online accounts integration with fb isn't working

Status in gnome-online-accounts package in Ubuntu:
  Fix Released
Status in gnome-online-accounts source package in Focal:
  Fix Committed
Status in gnome-online-accounts source package in Hirsute:
  Fix Committed

Bug description:
  * Impact

  The online accounts setting are proposing a facebook item which isn't
  working

  * Test case

  Go to settings -> online account, browse the accounts option proposed,
  facebook shouldn't be in the list since it doesn't work.

  * Regression potential

  The change is to disable the facebook provider using the upstream
  provided build option. Check that facebook isn't listed anymore but
  that the other providers still are. Since it's a build option change
  it could fail to build so check for that as well on launchpad.

  Since the facebook service currently doesn't consider gnome-online-
  accounts as a valid client there should be no user with that provider
  configured. Even if there were since the service isn't working they
  would see a functional regression.

  ---

  Hi i tryed to use gnome-control-center online-accounts to make easy
  like windows 10 to login to email or add other login so its more easy
  with ID to use pincode or other ID fingerprint and other.

  But its look its much issue compared with windows 10 with thunderbird,
  firefox, and other program.

  Worst is facebook only little windows with issue with login?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-online-accounts 3.38.1-1ubuntu1
  Uname: Linux 5.12.0-051200-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  1 19:38:03 2021
  InstallationDate: Installed on 2019-05-07 (725 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+subscriptions

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

[Touch-packages] [Bug 1925320] Re: Backport packages for 20.04.3 HWE stack

[Kai-Chuan Hsieh]

Try to enable proposed channel and update the libdrm and mesa on ADL-S.

The graphic works good on it.
Attach the system info. 

** Attachment added: "gfx-info.log"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1925320/+attachment/5500621/+files/gfx-info.log

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

Title:
  Backport packages for 20.04.3 HWE stack

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

Bug description:
  [Impact]

  These are needed for 20.04.3 images.

  [Test case]

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

  [What could go wrong]

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+subscriptions

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