[Touch-packages] [Bug 1877828] Re: Missing feature: disable one specific wireless device meanwhile another remain switched on

2020-05-10 Thread Juhani Numminen
** Package changed: ubuntu => network-manager (Ubuntu)

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

Title:
  Missing feature: disable one specific wireless device meanwhile
  another remain switched on

Status in network-manager package in Ubuntu:
  New

Bug description:
  When working on laptop, we may need an external wifi adapter in order
  to catch a remote access point no working well with the built-in
  wireless card of the laptop. In such case, it would make sense to
  disable the internal wireless card in order to have just the external
  on working. However, Ubuntu does not offer a simple way to do so.

  Moreover, if I click on "Turn off" for the built-in wifi adapter in
  the top right corner menu (see the screenshot), both wifi adapters are
  swtiched off, which is not the desired effect.

  See for example: https://askubuntu.com/questions/168032/how-to-
  disable-built-in-wifi-and-use-only-usb-wifi-card

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

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


[Touch-packages] [Bug 1877828] [NEW] Missing feature: disable one specific wireless device meanwhile another remain switched on

2020-05-10 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When working on laptop, we may need an external wifi adapter in order to
catch a remote access point no working well with the built-in wireless
card of the laptop. In such case, it would make sense to disable the
internal wireless card in order to have just the external on working.
However, Ubuntu does not offer a simple way to do so.

Moreover, if I click on "Turn off" for the built-in wifi adapter in the
top right corner menu (see the screenshot), both wifi adapters are
swtiched off, which is not the desired effect.

See for example: https://askubuntu.com/questions/168032/how-to-disable-
built-in-wifi-and-use-only-usb-wifi-card

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Missing feature: disable one specific wireless device meanwhile another remain 
switched on
https://bugs.launchpad.net/bugs/1877828
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager 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 1877633] Re: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64

2020-05-10 Thread Alex Murray
When generating the list of systems calls for aarch64, libseccomp uses
the generic kernel API headers rather than the architecture specific
ones - and so misses the definitions of getrlimit, setrlimit and clone3
for aarch64 - if this is changed to use arch-specific headers then we
can regenerate the syscalls.csv and these are now present as expected.
Have submitted PRhttps://github.com/seccomp/libseccomp/pull/235 upstream
for feedback.

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

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

Status in libseccomp package in Ubuntu:
  Confirmed
Status in libseccomp source package in Focal:
  Confirmed
Status in libseccomp source package in Groovy:
  Confirmed

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

  On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2

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

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

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

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

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

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


[Touch-packages] [Bug 1866551] Re: software-properties package crashed with desktop on totem launch on ubuntu-mate-1804

2020-05-10 Thread Launchpad Bug Tracker
[Expired for software-properties (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: software-properties (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  software-properties package crashed with desktop on totem launch on
  ubuntu-mate-1804

Status in software-properties package in Ubuntu:
  Expired

Bug description:
  software-properties package crashed with desktop on totem launch on
  ubuntu-mate-1804.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.12
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Mar  8 21:39:01 2020
  InstallationDate: Installed on 2018-05-11 (666 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2020-05-10 Thread Launchpad Bug Tracker
[Expired for ibus (Ubuntu) because there has been no activity for 60
days.]

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

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

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

Status in ibus package in Ubuntu:
  Expired

Bug description:
  the Ubuntu presents an error

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-1~exp1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Mar 11 08:51:28 2020
  ExecutablePath: /usr/lib/ibus/ibus-x11
  InstallationDate: Installed on 2020-03-07 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
  ProcCmdline: /usr/lib/ibus/ibus-x11 --kill-daemon
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7fab42711b86 <__run_exit_handlers+198>:  mov
0x10(%rax),%rdx
   PC (0x7fab42711b86) ok
   source "0x10(%rax)" (0xb1ac969e3c4a0) not located in a known VMA region 
(needed readable region)!
   destination "%rdx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   __GI___poll (fds=0x7fff598bf188, nfds=1, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
   ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
   ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
   xcb_wait_for_reply64 () from /lib/x86_64-linux-gnu/libxcb.so.1
   _XReply () from /lib/x86_64-linux-gnu/libX11.so.6
  Title: ibus-x11 crashed with SIGSEGV in __GI___poll()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

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

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


[Touch-packages] [Bug 1872564] Re: /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice

2020-05-10 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/apparmor/+git/apparmor/+merge/383686

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

Title:
  /proc/sys/kernel/random/boot_id rule missing from
  abstractions/nameservice

Status in apparmor package in Ubuntu:
  Fix Committed

Bug description:
  # Description

  On a default Focal install, systemd is used when looking up passwd and
  group information:

  # grep systemd /etc/nsswitch.conf 
  passwd: files systemd
  group:  files systemd

  Daemons confined by Apparmor that also query those "databases" will
  cause this Apparmor denial:

  audit: type=1400 audit(1586825456.411:247): apparmor="DENIED"
  operation="open" namespace="root//lxd-fb1_"
  profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id"
  pid=7370 comm="named" requested_mask="r" denied_mask="r" fsuid=100
  ouid=100

  Many daemons confined by Apparmor also happen to downgrade their
  privileges so they always end up looking up user/group information.

  # Steps to reproduce

  1) launch a Focal container (named fb1 here)
  $ lxc launch images:ubuntu/focal fb1

  2) setup apparmor inside the container (already done on official Ubuntu 
images)
  $ lxc exec fb1 -- apt update && lxc exec fb1 -- apt install apparmor -y

  3) install bind9
  $ lxc exec fb1 -- apt install bind9 -y

  4) check kernel logs for DENIED
  $ journalctl -o cat -b0 -k | grep 'apparmor="DENIED"' | grep -F 
'profile="/usr/sbin/named"'

  
  Step 4, should not return anything. Because systemd is involved in the 
user/group lookups, it currently returns the following:

  audit: type=1400 audit(1586826072.115:266): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:267): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:268): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:269): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:270): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100

  
  # Workaround

  1) remove systemd from nsswitch.conf
  $ lxc exec fb1 -- sed -i 's/ systemd$/ # systemd/' /etc/nsswitch.conf
  2) restart named
  $ lxc exec fb1 -- service named restart
  3) notice no more denials in kernel logs

  # Additional information

  root@fb1:~# apt-cache policy apparmor
  apparmor:
Installed: 2.13.3-7ubuntu4
Candidate: 2.13.3-7ubuntu4
Version table:
   *** 2.13.3-7ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  root@fb1:~# uname -a
  Linux fb1 5.3.0-46-generic #38~18.04.1-Ubuntu SMP Tue Mar 31 04:17:56 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  root@fb1:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

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

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


[Touch-packages] [Bug 1877269] Re: Ubuntu crashes multiple time due to pulse audio. (alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large)

2020-05-10 Thread Daniel van Vugt
If the machine is out of memory then please reboot and then run the
'ubuntu-bug' or 'apport-cli' command.

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

Title:
  Ubuntu crashes multiple time due to pulse audio. (alsa-util.c:
  snd_pcm_delay() returned a value that is exceptionally large)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  pulseaudio:
Installé : 1:11.1-1ubuntu7.5
Candidat : 1:11.1-1ubuntu7.5
   Table de version :
   *** 1:11.1-1ubuntu7.5 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:11.1-1ubuntu7 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  The OS freezes when using in normal conditions, usually VS Code, Discord app 
and Spotify in browser.
  When it does, I need to hard reboot by holding power button.

  I checked journalctl to confirm it was due to pulseaudio.

  alsa-util.c: snd_pcm_delay() returned a value that is exceptionally
  large

  The above line is always the last to prompt in the boot journal.
  It does not freeze instantly, it progressively freezes down, but sometime 
Mozilla Firefox crashes and it freezes no more.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.5
  Uname: Linux 5.1.15-surface-linux-surface x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  saravanane   2071 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  7 11:00:37 2020
  InstallationDate: Installed on 2019-10-01 (218 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 108.2706.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr108.2706.768:bd04/18/2019:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B09F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.sku: Surface_Pro_4
  dmi.product.version: D:0B:09F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

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

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


[Touch-packages] [Bug 1876046] Re: [XPS L501X, Realtek ALC665, Speaker, Internal] "Analog Stereo" and "Build-in speaker" appears "unplugged/unavailable"

2020-05-10 Thread Daniel van Vugt
** Summary changed:

- [XPS L501X, Realtek ALC665, Speaker, Internal]
+ [XPS L501X, Realtek ALC665, Speaker, Internal] "Analog Stereo" and "Build-in 
speaker" appears "unplugged/unavailable"

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

Title:
  [XPS L501X, Realtek ALC665, Speaker, Internal] "Analog Stereo" and
  "Build-in speaker" appears "unplugged/unavailable"

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 19.04 to 20.04 sound did not work. "Analog Stereo" and 
"Build-in speaker" appears "unplugged/unavaiable". I can change it in volume 
control -> configuration to Analog Stereo Duplex (unplugged)(unavaiable) and 
sound does play, but after each reboot computer changes to Digital Stereo 
IEC985 and do not play sound until changed again.
  I did reinstall of alsa and pulse according to some forums but this didn't 
work.
  Before upgrade everything always worked out of the box since 2009 on this 
computer. I know it's a little old but it works excellent! Please help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kwiatek1472 F pulseaudio
   /dev/snd/controlC0:  kwiatek1472 F pulseaudio
   /dev/snd/pcmC0D0c:   kwiatek1472 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kwiatek1472 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Thu Apr 30 09:25:27 2020
  InstallationDate: Installed on 2020-02-25 (64 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kwiatek1472 F pulseaudio
   /dev/snd/controlC0:  kwiatek1472 F pulseaudio
   /dev/snd/pcmC0D0c:   kwiatek1472 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kwiatek1472 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [XPS L501X, Realtek ALC665, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to focal on 2020-04-25 (4 days ago)
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn:rvrA08:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: XPS L501X
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1857335] Re: System volume slider only works between ~90% and 100%.

2020-05-10 Thread Daniel van Vugt
** Package changed: gnome-control-center (Ubuntu) => pulseaudio (Ubuntu)

** Summary changed:

- System volume slider only works between ~90% and 100%.
+ System volume slider only works between ~90% and 100% with a USB 2.0 speaker

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

Title:
  System volume slider only works between ~90% and 100% with a USB 2.0
  speaker

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This is only with my USB 2.0 speaker[1] - with other devices, it works
  fine and the slider's 0% corresponds to silent and 100% full. With my
  USB 2.0 speaker, with the 'output' set to 'Analogue Output - USB2.0
  Device', it only has an effect between about 90% and 100%.

  I took a video of the problem and uploaded it here:

  http://davidmaxwaterman.fastmail.co.uk/xfer/ubuntu_volume_problem.mp4

  [1]
  
https://www.amazon.co.uk/gp/product/B07W1KN1XD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8=1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 23 10:00:17 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-07-19 (156 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2019-10-28 (56 days ago)

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

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


[Touch-packages] [Bug 1838227] Re: Bluetooth "Connection switch" snaps back by itself until after many tries

2020-05-10 Thread Daniel van Vugt
Christopher, please open a new bug for what you experience by running:

  ubuntu-bug gnome-shell

This bug should stay closed while the original reporter hasn't provided
the requested info.


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

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

Title:
  Bluetooth "Connection switch" snaps back by itself until after many
  tries

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Attempting to slide the "Connection" switch in the gui to connect a
  bluetooth device fails initially -- the switch moves but "snaps back"
  by itself immediately.   Clicking on the switch flashes the "busy"
  indicator momentarily, but the switch does not move.   After a while,
  connecting succeeds.

  I don't know if the mouse input is not recognized until the "Nth"
  attempt, or else the connection was in-progress all along but the gui
  was not tracking that correctly.

  Please watch the attached video (use vlc).

  NOTE: This system is running a non-standard kernel 5.2 in order to
  circumvent other problems (see bug 1838180).

  Again, see the video; there is something wrong with how the GUI
  communicates with the kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: bluez 5.50-0ubuntu2
  Uname: Linux 5.2.0-050200-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 28 22:46:28 2019
  InstallationDate: Installed on 2019-02-06 (173 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  InterestingModules: bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic 
root=UUID=75234048-11af-4901-9f89-2c32581f5dd3 ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: Upgraded to disco on 2019-06-27 (31 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  hciconfig:
   
  rfkill:
   
  syslog:
   Jul 28 22:42:11 V-M-Ubuntu-Experimental NetworkManager[828]:   
[1564378931.7693] Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.16.0/libnm-device-plugin-bluetooth.so)
   Jul 28 22:42:22 V-M-Ubuntu-Experimental systemd[1]: Condition check resulted 
in Bluetooth service being skipped.

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

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


[Touch-packages] [Bug 1857335] [NEW] System volume slider only works between ~90% and 100%.

2020-05-10 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

This is only with my USB 2.0 speaker[1] - with other devices, it works
fine and the slider's 0% corresponds to silent and 100% full. With my
USB 2.0 speaker, with the 'output' set to 'Analogue Output - USB2.0
Device', it only has an effect between about 90% and 100%.

I took a video of the problem and uploaded it here:

http://davidmaxwaterman.fastmail.co.uk/xfer/ubuntu_volume_problem.mp4

[1]
https://www.amazon.co.uk/gp/product/B07W1KN1XD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8=1

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-control-center 1:3.34.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 23 10:00:17 2019
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2019-07-19 (156 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to eoan on 2019-10-28 (56 days ago)

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


** Tags: amd64 apport-bug eoan
-- 
System volume slider only works between ~90% and 100%.
https://bugs.launchpad.net/bugs/1857335
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio in Ubuntu.

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


[Touch-packages] [Bug 1877567] Re: Automatic Login

2020-05-10 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1845801 ***
https://bugs.launchpad.net/bugs/1845801

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1845801, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1845801
   [nvidia] Automatic login fails and then all subsequent logins fail. Killing 
gnome-session-binary fixes it, or just not using automatic login.

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

Title:
  Automatic Login

Status in xorg package in Ubuntu:
  New

Bug description:
  Problem
  1. Switched to automatic login option during the fresh install
  2. On a start up Login screen is still shown.
  3. Typing correct user name and password does not start the system.
  4. End up stuck in login loop

  Solution
  1. Restart system
  2. Selected Ubuntu Recovery mode
  3. Select normal boot
  4. System starts
  5. Go to to User Settings and disable automatic login
  6. Reboot
  7. System starts with login screen
  8. Type name and password.
  9. system starts

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:06:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  8 08:04:14 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] [10de:2187] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1650 SUPER] 
[1458:401b]
  InstallationDate: Installed on 2020-05-04 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=f070f159-e92a-44d2-9c1b-d791f0e697c6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: A320M-HDV R4.0
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1877904] [NEW] flowblade irregular file save behavior

2020-05-10 Thread Sanjay Basu
Public bug reported:

Package: flowblade (2.4.0.1-2) [universe]
Ubuntu version: Ubuntu 20.04 LTS

flowblade 2.4.0 (packaged in Ubuntu 20.04) crashes on project file save.

Steps to reproduce:
1. Open flowblade
2. edit videos
3. File --> Save As
4. Choose filename
5. Save

Expected result:  Project is saved

Actual result: Project is saved but save file dialog remains open and
information in terminal shows:

Saving project...
Traceback (most recent call last):
  File "/usr/share/flowblade/Flowblade/projectaction.py", line 492, in 
_save_as_dialog_callback
save_time = time.clock()
AttributeError: module 'time' has no attribute 'clock'


After searching, it seems that in python 3.8, time.clock is deprecated.


Solution: It has been fixed in development version from 
https://github.com/jliljebl/flowblade

Thank you,

Sanjay Basu

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

** Package changed: apport (Ubuntu) => flowblade (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/1877904

Title:
  flowblade irregular file save behavior

Status in flowblade package in Ubuntu:
  New

Bug description:
  Package: flowblade (2.4.0.1-2) [universe]
  Ubuntu version: Ubuntu 20.04 LTS

  flowblade 2.4.0 (packaged in Ubuntu 20.04) crashes on project file
  save.

  Steps to reproduce:
  1. Open flowblade
  2. edit videos
  3. File --> Save As
  4. Choose filename
  5. Save

  Expected result:  Project is saved

  Actual result: Project is saved but save file dialog remains open and
  information in terminal shows:

  Saving project...
  Traceback (most recent call last):
File "/usr/share/flowblade/Flowblade/projectaction.py", line 492, in 
_save_as_dialog_callback
  save_time = time.clock()
  AttributeError: module 'time' has no attribute 'clock'

  
  After searching, it seems that in python 3.8, time.clock is deprecated.

  
  Solution: It has been fixed in development version from 
https://github.com/jliljebl/flowblade

  Thank you,

  Sanjay Basu

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

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


[Touch-packages] [Bug 1877894] Re: "True Wireless" Bluetooth headsets not connecting in Ubuntu 20.04

2020-05-10 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  "True Wireless" Bluetooth headsets not connecting in Ubuntu 20.04

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I upgraded my Ubuntu installation from 19.10 to 20.04 and I have lost
  the ability to connect to any kind of Bluetooth "True Wireless"
  earphones (Apple AirPods, Galaxy Earpods+, etc). Standard Bluetooth
  headphones connect correctly but all "True Wireless" style headphones
  briefly connect then disconnect immediately.

  bluetoothctl output:

  ```
  [bluetooth]# devices
  Device C0:28:8D:1D:42:90 Jaybird X3
  Device 7C:38:AD:4A:C8:F9 Galaxy Buds (C8F9)
  Device 40:26:19:DC:12:E6 Apple AirPods

  [bluetooth]# connect C0:28:8D:1D:42:90
  Attempting to connect to C0:28:8D:1D:42:90
  [CHG] Device C0:28:8D:1D:42:90 Connected: yes
  Connection successful

  [Jaybird X3]# connect 7C:38:AD:4A:C8:F9
  ttempting to connect to 7C:38:AD:4A:C8:F9
  [CHG] Device 7C:38:AD:4A:C8:F9 Connected: yes
  Failed to connect: org.bluez.Error.Failed

  Jaybird X3]# connect 40:26:19:DC:12:E6
  Attempting to connect to 40:26:19:DC:12:E6
  [CHG] Device 40:26:19:DC:12:E6 Connected: yes
  Failed to connect: org.bluez.Error.Failed

  [CHG] Device 40:26:19:DC:12:E6 Connected: no
  [CHG] Device 40:26:19:DC:12:E6 Connected: yes
  [CHG] Device 40:26:19:DC:12:E6 Connected: no

  [Jaybird X3]#

  ```


  ```
  $ lsb_release -rd

  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  ```

  possible packages involved:
  -pulseaudio
  -pulseaudio-module-bluetooth
  -bluez

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  curtis 8167 F pulseaudio
   /dev/snd/controlC2:  curtis 8167 F pulseaudio
   /dev/snd/pcmC2D0c:   curtis 8167 F...m pulseaudio
   /dev/snd/controlC0:  curtis 8167 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 10 15:52:42 2020
  InstallationDate: Installed on 2019-05-24 (352 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: Upgraded to focal on 2020-05-04 (5 days ago)
  dmi.bios.date: 06/20/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1204
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-AR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1204:bd06/20/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Touch-packages] [Bug 1877894] [NEW] "True Wireless" Bluetooth headsets not connecting in Ubuntu 20.04

2020-05-10 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I upgraded my Ubuntu installation from 19.10 to 20.04 and I have lost
the ability to connect to any kind of Bluetooth "True Wireless"
earphones (Apple AirPods, Galaxy Earpods+, etc). Standard Bluetooth
headphones connect correctly but all "True Wireless" style headphones
briefly connect then disconnect immediately.

bluetoothctl output:

```
[bluetooth]# devices
Device C0:28:8D:1D:42:90 Jaybird X3
Device 7C:38:AD:4A:C8:F9 Galaxy Buds (C8F9)
Device 40:26:19:DC:12:E6 Apple AirPods

[bluetooth]# connect C0:28:8D:1D:42:90
Attempting to connect to C0:28:8D:1D:42:90
[CHG] Device C0:28:8D:1D:42:90 Connected: yes
Connection successful

[Jaybird X3]# connect 7C:38:AD:4A:C8:F9
ttempting to connect to 7C:38:AD:4A:C8:F9
[CHG] Device 7C:38:AD:4A:C8:F9 Connected: yes
Failed to connect: org.bluez.Error.Failed

Jaybird X3]# connect 40:26:19:DC:12:E6
Attempting to connect to 40:26:19:DC:12:E6
[CHG] Device 40:26:19:DC:12:E6 Connected: yes
Failed to connect: org.bluez.Error.Failed

[CHG] Device 40:26:19:DC:12:E6 Connected: no
[CHG] Device 40:26:19:DC:12:E6 Connected: yes
[CHG] Device 40:26:19:DC:12:E6 Connected: no

[Jaybird X3]#

```


```
$ lsb_release -rd

Description:Ubuntu 20.04 LTS
Release:20.04
```

possible packages involved:
-pulseaudio
-pulseaudio-module-bluetooth
-bluez

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  curtis 8167 F pulseaudio
 /dev/snd/controlC2:  curtis 8167 F pulseaudio
 /dev/snd/pcmC2D0c:   curtis 8167 F...m pulseaudio
 /dev/snd/controlC0:  curtis 8167 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun May 10 15:52:42 2020
InstallationDate: Installed on 2019-05-24 (352 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: Upgraded to focal on 2020-05-04 (5 days ago)
dmi.bios.date: 06/20/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1204
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-AR
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1204:bd06/20/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS

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


** Tags: amd64 apport-bug focal
-- 
"True Wireless" Bluetooth headsets not connecting in Ubuntu 20.04
https://bugs.launchpad.net/bugs/1877894
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver in Ubuntu.

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


[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-05-10 Thread Matthew Ruffell
I went and looked at the autopkgtest regressions, and they aren't actual
regressions, just transient network problems and slow build timeouts.

chrony autopkgtest regression on armhf:

Need to get 263 kB of archives.
After this operation, 2,048 B of additional disk space will be used.
Err:1 http://ftpmaster.internal/ubuntu bionic-proposed/main armhf kmod armhf 
24-1ubuntu3.4
  Could not connect to ftpmaster.internal:80 (91.189.89.99), connection timed 
out
Err:2 http://ftpmaster.internal/ubuntu bionic-proposed/main armhf libkmod2 
armhf 24-1ubuntu3.4
  Unable to connect to ftpmaster.internal:http:
  
Network problems for this one.

  
All the linux packages for arm64:

autopkgtest [15:44:38]: ERROR: timed out on command 
/tmp/autopkgtest.M7KUyX/build.f2S/src/debian/tests/rebuild
autopkgtest [15:48:48]: test rebuild: ---]
rebuild  FAIL timed out

Slow builds for these packages. Maybe the arm64 build host was having a
bad day.

I think the autopkgtests just need to be re-run.

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

Title:
  QEMU/KVM display is garbled when booting from kernel EFI stub due to
  missing bochs-drm module

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in kmod source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1872863

  [Impact]

  A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the
  kernel EFI stub whenever EFI is enabled. This causes problems for
  QEMU/KVM virtual machines which use the VGA=std video device, as the
  efifb driver yields an unreadable garbled screen. See the attached
  image.

  The correct framebuffer driver to use in this situation is bochs-drm,
  and modprobing it from a HWE kernel fixes the issues.

  bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled
  in LP #1378648 due to bochs-drm causing problems in a PowerKVM
  machine. This problem appears to be fixed now, and bochs-drm has been
  re-enabled for Disco and up, in LP #1795857 and has been proven safe.

  This has also come up again in LP #1823152, as well as chatter on LP
  #1795857 to get this enabled on Bionic.

  The customer which is experiencing this issue cannot switch to VGA=qxl
  as a workaround, and must use VGA=std, hence I suggest we re-enable
  bochs-drm for Bionic.

  [Fix]

  I noticed on Focal, if you boot, the framebuffer is initially efifb:

  [ 0.603716] efifb: probing for efifb
  [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k
  [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1
  [ 0.603736] efifb: scrolling: redraw
  [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
  [ 0.604462] Console: switching to colour frame buffer device 100x37
  [ 0.605829] fb0: EFI VGA frame buffer device

  This soon changes to bochs-drm about a second later:

  [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
0: 0xc000 -> 0xc0ff
  [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
2: 0xc1c8c000 -> 0xc1c8cfff
  [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100)
  [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA
  [ 0.939085] Console: switching to colour dummy device 80x25
  [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console
  [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5.
  [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000.
  [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized
  [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB
  [ 0.942081] [TTM] Initializing pool allocator
  [ 0.942089] [TTM] Initializing DMA pool allocator
  [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 
GB/10.0 GiB)
  [ 0.944019] [drm] Found EDID data blob.
  [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on 
minor 0
  [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device
  [ 0.947712] Console: switching to colour frame buffer device 128x48

  On bionic, the framebuffer never changes from efifb, since the bochs-
  drm kernel module is not built, and it is also present on the module
  banlist in /etc/modprobe.d/blacklist-framebuffer.conf

  bochs-drm needs to be enabled to be built in the kernel config, and
  removed from the module blacklist in kmod.

  [Testcase]

  Create a new QEMU/KVM virtual machine, I used virt-manager. Before you
  install the OS, check the box to modify settings before install. In
  the "Overview" tab, enable EFI by setting the firmware to "UEFI
  x86_64: /usr/share/OVMF/OVMF_CODE.secboot.fd".

  Set the video device to qxl while you install Bionic. Once the install
  is done, reboot, do 

[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-05-10 Thread Matthew Ruffell
I repeated the same SRU verification as before, this time using kmod
from -proposed.

I installed a fresh Bionic KVM, with EFI enabled. I upgraded the system
to use the latest -updates packages. Linux 4.15.0-99-generic and Kmod
24-1ubuntu3.3 were installed. I shut the machine down, set the VGA
device to vga=std, and rebooted. The screen was garbled and unreadable.

I then ssh'd in, enabled -proposed, and installed Linux
4.15.0-100-generic, and kmod 24-1ubuntu3.4. I rebooted, and the display
came up great, and was perfectly readable. Attached screenshot as proof.

Relevent details from dmesg:

[1.137544] checking generic (c000 1d5000) vs hw (c000 100)
[1.137545] fb: switching to bochsdrmfb from EFI VGA
[1.137918] Console: switching to colour dummy device 80x25
[1.140305] [drm] Found bochs VGA, ID 0xb0c5.
[1.140308] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000.
[1.140616] [TTM] Zone  kernel: Available graphics memory: 2011058 kiB
[1.140619] [TTM] Initializing pool allocator
[1.140622] [TTM] Initializing DMA pool allocator
[1.146542] fbcon: bochsdrmfb (fb0) is primary device
[1.149357] Console: switching to colour frame buffer device 128x48
[1.151830] bochs-drm :00:01.0: fb0: bochsdrmfb frame buffer device
[1.168977] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on 
minor 0

lsmod:

$ lsmod | grep bochs
bochs_drm  20480  1
ttm   106496  1 bochs_drm
drm_kms_helper172032  1 bochs_drm
drm   401408  4 drm_kms_helper,bochs_drm,ttm

Since the Linux package builds bochs-drm, and the kmod package removes
the blacklist, I am happy to mark this verified for both packages.

** Attachment added: "screenshot of vga=std with 4.15.0-100-generic and kmod 
24-1ubuntu3.4"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872863/+attachment/5369638/+files/Screenshot%20from%202020-05-11%2010-41-12.png

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

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

Title:
  QEMU/KVM display is garbled when booting from kernel EFI stub due to
  missing bochs-drm module

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in kmod source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1872863

  [Impact]

  A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the
  kernel EFI stub whenever EFI is enabled. This causes problems for
  QEMU/KVM virtual machines which use the VGA=std video device, as the
  efifb driver yields an unreadable garbled screen. See the attached
  image.

  The correct framebuffer driver to use in this situation is bochs-drm,
  and modprobing it from a HWE kernel fixes the issues.

  bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled
  in LP #1378648 due to bochs-drm causing problems in a PowerKVM
  machine. This problem appears to be fixed now, and bochs-drm has been
  re-enabled for Disco and up, in LP #1795857 and has been proven safe.

  This has also come up again in LP #1823152, as well as chatter on LP
  #1795857 to get this enabled on Bionic.

  The customer which is experiencing this issue cannot switch to VGA=qxl
  as a workaround, and must use VGA=std, hence I suggest we re-enable
  bochs-drm for Bionic.

  [Fix]

  I noticed on Focal, if you boot, the framebuffer is initially efifb:

  [ 0.603716] efifb: probing for efifb
  [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k
  [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1
  [ 0.603736] efifb: scrolling: redraw
  [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
  [ 0.604462] Console: switching to colour frame buffer device 100x37
  [ 0.605829] fb0: EFI VGA frame buffer device

  This soon changes to bochs-drm about a second later:

  [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
0: 0xc000 -> 0xc0ff
  [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
2: 0xc1c8c000 -> 0xc1c8cfff
  [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100)
  [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA
  [ 0.939085] Console: switching to colour dummy device 80x25
  [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console
  [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5.
  [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000.
  [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized
  [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB
  [ 0.942081] [TTM] Initializing pool allocator
  [ 0.942089] [TTM] Initializing DMA 

[Touch-packages] [Bug 1741045] Re: Change the default resample-method to speex-float-N (N > 1) in daemon.conf

2020-05-10 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: Unknown => Fix Released

** Changed in: pulseaudio
   Importance: Wishlist => Unknown

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

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

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

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS

2020-05-10 Thread Dan Lenski
It appears you are using *OpenConnect*, although both the strings
OpenVPN and OpenConnect appear in prior posts. These are *completely
different* VPN clients.

You are using an *ancient* old release of OpenConnect v7.06. The
automatic MTU detection logic has been vastly improved in newer versions
of OpenConnect: https://www.infradead.org/openconnect/changelog.html

So yes, this is indeed a bug in OpenConnect's MTU handling, but likely
one which we've long since fixed upstream.

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

Title:
  SSH fails with connection timed out - in VPN and hangs here "expecting
  SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS

Status in linux package in Ubuntu:
  Invalid
Status in openconnect package in Ubuntu:
  Confirmed
Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  Hello Team,

  SSH timeout issue, once connect to VPN.

  Environment

  ==
  Dell XPS 9570 
  Ubuntu 16.04.6 Xenial Xerus)
  kernel - 4.15.0-55-generic

  $dpkg -l | grep -i openssh
  ii  openssh-client 1:7.2p2-4ubuntu2.8  --> 
  ii  openssh-server 1:7.2p2-4ubuntu2.8  
  ii  openssh-sftp-server  1:7.2p2-4ubuntu2.8

  
  VPN tunnel info 
  
  vpn0  Link encap:UNSPEC  HWaddr 
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:IP  P-t-P:xx  Mask:255.255.252.0
inet6 addr: fe80::b8e2:bea4:2e62:fe08/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1406  Metric:1
RX packets:962 errors:0 dropped:0 overruns:0 frame:0
TX packets:1029 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:87839 (87.8 KB)  TX bytes:238740 (238.7 KB)

  Issue
  
  Unable to connect to any host via ssh or sftp after VPN connection 

  Tried 
  =

  Reinstalled the openssh-client package and still no luck. May I know
  why the default cipher is not taking/hanging? Please let me know .
  There were no recent changes.

  
  Workaround
  ===
  Able to connect to ssh / sftp $ssh -c aes128-ctr   user@IP

  
  Below is the debug ssh client logs ===
  ==

  $ssh -vvv  user@ip
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug2: resolving "IP" port 22
  debug2: ssh_connect_direct: needpriv 0
  debug1: Connecting to IP [IP] port 22.
  debug1: Connection established.
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_rsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 
Ubuntu-4ubuntu0.3
  debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400
  debug2: fd 3 setting O_NONBLOCK
  debug1: Authenticating to IP:22 as 'user'
  debug3: send packet: type 20
  debug1: SSH2_MSG_KEXINIT sent
  debug3: receive packet: type 20
  debug1: SSH2_MSG_KEXINIT received
  debug2: local client KEXINIT proposal
  debug2: KEX algorithms: 
curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c
  debug2: host key algorithms: 
ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
  debug2: ciphers ctos: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
  debug2: ciphers stoc: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
  debug2: MACs ctos: 

[Touch-packages] [Bug 1877892] Re: lvmcache man page lacks warning about unclean shutdowns

2020-05-10 Thread pauldoo
I raised this on linux-lvm mailing list recently, and included links
there to previous posts of this problem: https://www.redhat.com/archives
/linux-lvm/2020-May/msg0.html

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

Title:
  lvmcache man page lacks warning about unclean shutdowns

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Hello,
  The man page for lvmcache lacks any warnings about the behaviour of lvmcache 
when unclean shutdowns occur.  In particular an unclean shutdown results in the 
entire cache being marked dirty on next boot and a lengthy write out of the 
entire cache begins.  This occurs regardless of the mode (writethrough or 
writeback).

  This behaviour has been raised previously on upstream linux-lvm and
  dm-devel mailing lists, but the situation has not changed since at
  least 2014.  I don't expect the implementation to be changed therfor,
  only that the documentation be updated to highlight this behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 10 20:55:55 2020
  SourcePackage: lvm2
  UpgradeStatus: Upgraded to focal on 2020-04-24 (15 days ago)

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

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


[Touch-packages] [Bug 1877892] [NEW] lvmcache man page lacks warning about unclean shutdowns

2020-05-10 Thread pauldoo
Public bug reported:

Hello,
The man page for lvmcache lacks any warnings about the behaviour of lvmcache 
when unclean shutdowns occur.  In particular an unclean shutdown results in the 
entire cache being marked dirty on next boot and a lengthy write out of the 
entire cache begins.  This occurs regardless of the mode (writethrough or 
writeback).

This behaviour has been raised previously on upstream linux-lvm and dm-
devel mailing lists, but the situation has not changed since at least
2014.  I don't expect the implementation to be changed therfor, only
that the documentation be updated to highlight this behaviour.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lvm2 2.03.07-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun May 10 20:55:55 2020
SourcePackage: lvm2
UpgradeStatus: Upgraded to focal on 2020-04-24 (15 days ago)

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


** Tags: amd64 apport-bug focal wayland-session

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

Title:
  lvmcache man page lacks warning about unclean shutdowns

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Hello,
  The man page for lvmcache lacks any warnings about the behaviour of lvmcache 
when unclean shutdowns occur.  In particular an unclean shutdown results in the 
entire cache being marked dirty on next boot and a lengthy write out of the 
entire cache begins.  This occurs regardless of the mode (writethrough or 
writeback).

  This behaviour has been raised previously on upstream linux-lvm and
  dm-devel mailing lists, but the situation has not changed since at
  least 2014.  I don't expect the implementation to be changed therfor,
  only that the documentation be updated to highlight this behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 10 20:55:55 2020
  SourcePackage: lvm2
  UpgradeStatus: Upgraded to focal on 2020-04-24 (15 days ago)

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

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


[Touch-packages] [Bug 1877875] Re: Pressing Alt+F1 with mouse cursor over the Applcations leads to focus move to Applications, the menus are unusable as result

2020-05-10 Thread Norbert
Caused by some mess with customizations from other flavors.
The normally installed Ubuntu MATE is not affected.

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Invalid

** Changed in: mate-panel (Ubuntu)
   Status: New => Incomplete

** Changed in: mate-panel (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Pressing Alt+F1 with mouse cursor over the Applcations leads to focus
  move to Applications, the menus are unusable as result

Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in mate-panel package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Have Ubuntu MATE 20.04 LTS installed
  2. Login to session, choose Traditional desktop layout in MATE Tweak
  3. Move move cursor over Applications menu
  4. Press + to open Applications menu
  5. Press  or 

  Expected results:
  * focus moves with  or  to corresponding one of the 
menu items - Applications, Places, System

  Actual results:
  * focus is stuck on Applications menu, about which mouse cursor is located 
(see screencast)

  ProblemType: Bug
  DistroRelease: Ubuntu Kylin 20.04
  Package: mate-panel 1.24.0-2 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 5.4.0-29.33-lowlatency 5.4.30
  Uname: Linux 5.4.0-29-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sun May 10 18:57:48 2020
  InstallationDate: Installed on 2020-04-22 (17 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200422)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1877875/+subscriptions

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


[Touch-packages] [Bug 1858152] Re: fstrim.service no longer trims /home partition

2020-05-10 Thread Jeffery To
At this moment, this issue is still present in focal. It would be nice
if this can be fixed for an LTS release.

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

Title:
  fstrim.service no longer trims /home partition

Status in Util-Linux-ng:
  Unknown
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  When I was running disco, fstrim.service would trim all of my
  partitions:

  Oct 21 00:00:18 computer systemd[1]: Starting Discard unused blocks on 
filesystems from /etc/fstab...
  Oct 21 00:00:37 computer fstrim[9588]: /home: 25 GiB (26797150208 bytes) 
trimmed on /dev/mapper/ubuntu--vg-home
  Oct 21 00:00:37 computer fstrim[9588]: /boot: 805.4 MiB (844546048 bytes) 
trimmed on /dev/sda5
  Oct 21 00:00:37 computer fstrim[9588]: /: 5.5 GiB (5929816064 bytes) trimmed 
on /dev/mapper/ubuntu--vg-root
  Oct 21 00:00:37 computer systemd[1]: fstrim.service: Succeeded.
  Oct 21 00:00:37 computer systemd[1]: Started Discard unused blocks on 
filesystems from /etc/fstab.

  After upgrading to eoan, my /home partition is no longer trimmed:

  Oct 28 00:00:21 computer systemd[1]: Starting Discard unused blocks on 
filesystems from /etc/fstab...
  Oct 28 00:00:32 computer fstrim[24667]: /boot: 781.1 MiB (819011584 bytes) 
trimmed on /dev/sda5
  Oct 28 00:00:32 computer fstrim[24667]: /: 7.2 GiB (7696994304 bytes) trimmed 
on /dev/mapper/ubuntu--vg-root
  Oct 28 00:00:32 computer systemd[1]: fstrim.service: Succeeded.
  Oct 28 00:00:32 computer systemd[1]: Started Discard unused blocks on 
filesystems from /etc/fstab.

  Checking the unit file (/lib/systemd/system/fstrim.service), I noticed
  there is a "ProtectHome=yes" option. Removing this option caused my
  /home partition to be trimmed once again.

  I believe the "ProtectSystem=strict" option may also cause partitions
  in non-standard partition schemes to be skipped by fstrim.service
  (although I have not tested this).

To manage notifications about this bug go to:
https://bugs.launchpad.net/util-linux-ng/+bug/1858152/+subscriptions

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


[Touch-packages] [Bug 1877887] [NEW] [USB-Audio - Scarlett 2i2 USB, playback] fails after a while

2020-05-10 Thread MIchael Porter
Public bug reported:

I am encountering some very bizarre and difficult to reliably replicate
issues.

I am using a Focusrite Scarlett 2i2 USB audio interface, and am having a
number of issues that I did not have in older version of ubuntu (these
issues started occuring sometime in 19.04-19.10, can't remember which).

I am having three major issues. Number one is, if USB autosuspend is
enabled, it will stop working completely until reboot after anywhere
from a few minutes to several hours. Reconnecting the device does not
fix it and it seems to not power on at all, with dmesg reporting a
"usb_set_interface failed -110" error. Sometimes this bug can be
recreated by manually disconnecting and reconnecting the device, however
I was unable to replicate it in this manner at the time of filing the
bug.

Another (presumably related) issue I am having is that if I reconnect
the device and it doesn't fail, it outputs very crackly audio, as if the
bitrate or sample rate were set incorrectly. This persists until a
restart of pulseaudio. Previously, I had a similar bug where it would
randomly start doing the crackly audio thing until reconnecting the
device and in this case a restart of pulse did *not* fix the problem. I
am unsure if this issue still happens as it was fairly rare.

The third problem is that sometimes when performing a suspend/wake
cycle, the interface will power cycle several times, in intervals of
15-30 seconds or so before staying on properly.

As previously mentioned, these issues are fairly new and did not occur
in older versions of ubuntu. I have confirmed that the audio interface
works fine under windows.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun May 10 14:09:28 2020
InstallationDate: Installed on 2020-05-08 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: USB-Audio - microKEY-37
Symptom_PulseAudioLog:
 
Symptom_Type: Sound works for a while, then breaks
Title: [USB-Audio - Scarlett 2i2 USB, playback] fails after a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/19/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P5.40
dmi.board.name: AB350 Gaming K4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug focal

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

Title:
  [USB-Audio - Scarlett 2i2 USB, playback] fails after a while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I am encountering some very bizarre and difficult to reliably
  replicate issues.

  I am using a Focusrite Scarlett 2i2 USB audio interface, and am having
  a number of issues that I did not have in older version of ubuntu
  (these issues started occuring sometime in 19.04-19.10, can't remember
  which).

  I am having three major issues. Number one is, if USB autosuspend is
  enabled, it will stop working completely until reboot after anywhere
  from a few minutes to several hours. Reconnecting the device does not
  fix it and it seems to not power on at all, with dmesg reporting a
  "usb_set_interface failed -110" error. Sometimes this bug can be
  recreated by manually disconnecting and reconnecting the device,
  however I was unable to replicate it in this manner at the time of
  filing the bug.

  Another (presumably related) issue I am having is that if I reconnect
  the device and it doesn't fail, it outputs very crackly audio, as if
  the bitrate or sample rate were set incorrectly. This persists until a
  restart of pulseaudio. Previously, I had a similar bug where it would
  randomly start doing the crackly audio thing until reconnecting the
  device and in this case a restart of pulse did *not* fix the problem.
  I am unsure if this issue still happens as it was fairly rare.

  The third problem is that sometimes when performing a suspend/wake
  cycle, the interface will power cycle several times, in intervals of
  15-30 

[Touch-packages] [Bug 1873764] Re: CUPS Apparmor Error opening /proc/sys/kernel/random/boot_id

2020-05-10 Thread Chriss
see comment #3, forgot to add:
sudo apparmor_status
4 processes are in enforce mode.
   /usr/sbin/cups-browsed (188070) 
   /usr/sbin/cupsd (188069) 
   /usr/lib/cups/notifier/dbus (188098) /usr/sbin/cupsd
   /snap/canonical-livepatch/95/canonical-livepatchd (956) 
snap.canonical-livepatch.canonical-livepatchd

dmesg:
 [42055.571610] audit: type=1400 audit(1589134509.618:1427): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=188069 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0

Using: 
sudo aa-complain usr.sbin.cupsd
sudo aa-complain /usr/sbin/cups-browsed
removed the error messages.

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

Title:
  CUPS Apparmor Error opening /proc/sys/kernel/random/boot_id

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  I noted the following messages on a just installed Ubuntu Focal:

  $ dmesg | grep cups
  [ 1769.505132] audit: type=1400 audit(1587372138.575:3011): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=15230 
comm="cups-browsed" capability=23  capname="sys_nice"
  [ 1776.623181] audit: type=1400 audit(1587372145.693:3012): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=15510 
comm="cups-browsed" capability=23  capname="sys_nice"
  [ 2040.426033] audit: type=1400 audit(1587372409.494:3013): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2040.426044] audit: type=1400 audit(1587372409.494:3014): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2040.426074] audit: type=1400 audit(1587372409.494:3015): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2040.426092] audit: type=1400 audit(1587372409.494:3016): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2040.426106] audit: type=1400 audit(1587372409.494:3017): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2041.404914] audit: type=1400 audit(1587372410.473:3018): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2041.404920] audit: type=1400 audit(1587372410.473:3019): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2041.404926] audit: type=1400 audit(1587372410.473:3020): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2041.404953] audit: type=1400 audit(1587372410.473:3021): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2041.404963] audit: type=1400 audit(1587372410.473:3022): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2071.925327] audit: type=1400 audit(1587372440.994:3028): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2071.925330] audit: type=1400 audit(1587372440.994:3029): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2071.925337] audit: type=1400 audit(1587372440.994:3030): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2071.925382] audit: type=1400 audit(1587372440.994:3031): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2071.925391] audit: type=1400 audit(1587372440.994:3032): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 

[Touch-packages] [Bug 1877884] [NEW] OpenVSwitch Support: no package for `nm-openvswitch`

2020-05-10 Thread Kathryn Morgan
Public bug reported:

Ubuntu 20.04 LTS
Package Version: NA
Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support.

Expected:
  Running the following:
`nmcli con up ovs-mgmt1`
`nmcli connection add type ovs-interface con-name mgmt1 ifname mgmt1 ip4 
192.168.16.2/24 gw4 192.168.16.1 master internal`
  Should raise the ovs interface(es) defined.

Actual results:
  `Connection activation failed: NetworkManager plugin for 'ovs-interface' 
unavailable`
  `Connection activation failed: NetworkManager plugin for 'ovs-port' 
unavailable`
  `Connection activation failed: NetworkManager plugin for 'ovs-bridge' 
unavailable`
*depending on interface type being raised

Argument:
  As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard 
method to raise OVS interfaces without resorting to depricated ifscripts. deb 
based releases dropped NetworkManager nm-* support for OVS in favor of 
networkd. rpm based releases have dropped networkd in favor of NetworkManager.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Ubuntu 20.04 LTS
  Package Version: NA
  Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support.
  
- 
  Expected:
-   Running the following:
- `nmcli con up ovs-mgmt1`
- `nmcli connection add type ovs-interface con-name mgmt1 ifname mgmt1 ip4 
192.168.16.2/24 gw4 192.168.16.1 master internal`
-   Should raise the ovs interface(es) defined. 
- 
+   Running the following:
+ ```
+ nmcli con up ovs-mgmt1
+ nmcli connection add type ovs-interface con-name mgmt1 ifname mgmt1 ip4 
192.168.16.2/24 gw4 192.168.16.1 master internal
+ ```
+   Should raise the ovs interface(es) defined.
  
  Actual results:
- `Error: Connection activation failed: NetworkManager plugin for 
'ovs-interface' unavailable`
- `Error: Connection activation failed: NetworkManager plugin for 
'ovs-port' unavailable`
- `Error: Connection activation failed: NetworkManager plugin for 
'ovs-bridge' unavailable`
+ `Error: Connection activation failed: NetworkManager plugin for 
'ovs-interface' unavailable`
+ `Error: Connection activation failed: NetworkManager plugin for 
'ovs-port' unavailable`
+ `Error: Connection activation failed: NetworkManager plugin for 
'ovs-bridge' unavailable`
  *depending on interface type being raised
  
- 
  Argument:
-   As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard 
method to raise OVS interfaces without resorting to depricated ifscripts. deb 
based releases dropped NetworkManager nm-* support for OVS in favor of 
networkd. rpm based releases have dropped networkd in favor of NetworkManager.
+   As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard 
method to raise OVS interfaces without resorting to depricated ifscripts. deb 
based releases dropped NetworkManager nm-* support for OVS in favor of 
networkd. rpm based releases have dropped networkd in favor of NetworkManager.

** Description changed:

  Ubuntu 20.04 LTS
  Package Version: NA
  Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support.
  
  Expected:
    Running the following:
  ```
  nmcli con up ovs-mgmt1
- nmcli connection add type ovs-interface con-name mgmt1 ifname mgmt1 ip4 
192.168.16.2/24 gw4 192.168.16.1 master internal
+ nmcli connection add type ovs-interface \
+   con-name mgmt1 ifname mgmt1   \
+   ip4 192.168.16.2/24 gw4 192.168.16.1 master internal
  ```
    Should raise the ovs interface(es) defined.
  
  Actual results:
  `Error: Connection activation failed: NetworkManager plugin for 
'ovs-interface' unavailable`
  `Error: Connection activation failed: NetworkManager plugin for 
'ovs-port' unavailable`
  `Error: Connection activation failed: NetworkManager plugin for 
'ovs-bridge' unavailable`
  *depending on interface type being raised
  
  Argument:
    As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard 
method to raise OVS interfaces without resorting to depricated ifscripts. deb 
based releases dropped NetworkManager nm-* support for OVS in favor of 
networkd. rpm based releases have dropped networkd in favor of NetworkManager.

** Description changed:

  Ubuntu 20.04 LTS
  Package Version: NA
  Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support.
  
  Expected:
    Running the following:
  ```
- nmcli con up ovs-mgmt1
  nmcli connection add type ovs-interface \
-   con-name mgmt1 ifname mgmt1   \
-   ip4 192.168.16.2/24 gw4 192.168.16.1 master internal
+   con-name mgmt1 ifname mgmt1   \
+   ip4 192.168.16.2/24 gw4 192.168.16.1 master internal
+ nmcli con up ovs-mgmt1
  ```
    Should raise the ovs interface(es) defined.
  
  Actual results:
  `Error: Connection activation failed: NetworkManager plugin for 
'ovs-interface' unavailable`
  `Error: Connection activation failed: 

[Touch-packages] [Bug 1873764] Re: CUPS Apparmor Error opening /proc/sys/kernel/random/boot_id

2020-05-10 Thread Chriss
Same happens for HP Laser 107 with driver installed from
https://support.hp.com/us-en/drivers/selfservice/hp-laser-100-printer-
series/24494339/model/24494342 using cups with cups error "Filter
failed" when printing.

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

Title:
  CUPS Apparmor Error opening /proc/sys/kernel/random/boot_id

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  I noted the following messages on a just installed Ubuntu Focal:

  $ dmesg | grep cups
  [ 1769.505132] audit: type=1400 audit(1587372138.575:3011): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=15230 
comm="cups-browsed" capability=23  capname="sys_nice"
  [ 1776.623181] audit: type=1400 audit(1587372145.693:3012): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=15510 
comm="cups-browsed" capability=23  capname="sys_nice"
  [ 2040.426033] audit: type=1400 audit(1587372409.494:3013): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2040.426044] audit: type=1400 audit(1587372409.494:3014): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2040.426074] audit: type=1400 audit(1587372409.494:3015): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2040.426092] audit: type=1400 audit(1587372409.494:3016): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2040.426106] audit: type=1400 audit(1587372409.494:3017): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2041.404914] audit: type=1400 audit(1587372410.473:3018): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2041.404920] audit: type=1400 audit(1587372410.473:3019): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2041.404926] audit: type=1400 audit(1587372410.473:3020): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2041.404953] audit: type=1400 audit(1587372410.473:3021): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2041.404963] audit: type=1400 audit(1587372410.473:3022): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2071.925327] audit: type=1400 audit(1587372440.994:3028): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2071.925330] audit: type=1400 audit(1587372440.994:3029): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2071.925337] audit: type=1400 audit(1587372440.994:3030): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2071.925382] audit: type=1400 audit(1587372440.994:3031): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 2071.925391] audit: type=1400 audit(1587372440.994:3032): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  
  It happened after installing Brother DCPL3550CDW Linux drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups-daemon 2.3.1-9ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-lowlatency 5.4.30
  Uname: Linux 5.4.0-25-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: 

[Touch-packages] [Bug 1876046] Re: [XPS L501X, Realtek ALC665, Speaker, Internal]

2020-05-10 Thread Charles Bruce
I have a Dell XPS L501X with exactly the same problem. The fix above:

> volume control -> configuration to Analog Stereo Duplex (unplugged)

I the only thing that has worked for me.

I've tried multiple other suggestions on other sites, include renaming
.config/pulse folder then reboot, force-reload of alsa, removing the
pulse-audio and alsa-base packages from the system, and reinstalling
them, and reviewing all settings in alsa mixer.

Ubuntu works perfectly on this laptop. I had 19.04 previously, and sound
worked fine. An upgrade to 20.04 didn't work as selecting the nVidia
video driver nvidia-driver-390 would not let the OS boot into the GUI.
What is strange is a complete wipe and reinstall of 20.04 from scratch
worked fine, and that video driver was selected automatically.

I'm so glad I found this post, as I now have sound again. For now I'm
content changing the setting by hand after a reboot.

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

Title:
  [XPS L501X, Realtek ALC665, Speaker, Internal]

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 19.04 to 20.04 sound did not work. "Analog Stereo" and 
"Build-in speaker" appears "unplugged/unavaiable". I can change it in volume 
control -> configuration to Analog Stereo Duplex (unplugged)(unavaiable) and 
sound does play, but after each reboot computer changes to Digital Stereo 
IEC985 and do not play sound until changed again.
  I did reinstall of alsa and pulse according to some forums but this didn't 
work.
  Before upgrade everything always worked out of the box since 2009 on this 
computer. I know it's a little old but it works excellent! Please help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kwiatek1472 F pulseaudio
   /dev/snd/controlC0:  kwiatek1472 F pulseaudio
   /dev/snd/pcmC0D0c:   kwiatek1472 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kwiatek1472 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Thu Apr 30 09:25:27 2020
  InstallationDate: Installed on 2020-02-25 (64 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kwiatek1472 F pulseaudio
   /dev/snd/controlC0:  kwiatek1472 F pulseaudio
   /dev/snd/pcmC0D0c:   kwiatek1472 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kwiatek1472 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [XPS L501X, Realtek ALC665, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to focal on 2020-04-25 (4 days ago)
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn:rvrA08:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: XPS L501X
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1877879] [NEW] segfault in iris_dri.so

2020-05-10 Thread Lukas Hejtmanek
Public bug reported:

As of Ubuntu 20.04, on intel graphics with intel driver (not
modesetting), I got segfault whenever anything tries to use GL.

This happens unless I export MESA_LOADER_DRIVER_OVERRIDE=i965. One says
that it does not happen with modesetting driver.

(gdb) run
Starting program: /usr/bin/glxgears 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x717cf700 (LWP 97070)]
[New Thread 0x7fffebfff700 (LWP 97071)]
[New Thread 0x70fce700 (LWP 97072)]
[New Thread 0x7fffeb7fe700 (LWP 97073)]

Thread 1 "glxgears" received signal SIGSEGV, Segmentation fault.
0x76a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
(gdb) where
#0  0x76a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#1  0x76c42de4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#2  0x76a59e5d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#3  0x76a5aa95 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4  0x76099774 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#5  0x711e in ?? ()
#6  0x6c88 in ?? ()
#7  0x77ace0b3 in __libc_start_main (main=0x6410, argc=1, 
argv=0x7fffe698, init=, fini=, 
rtld_fini=, stack_end=0x7fffe688) at ../csu/libc-start.c:308
#8  0x6f0a in ?? ()
(gdb) 

I believe, this is a bug in mesa tracked here:
https://gitlab.freedesktop.org/mesa/mesa/issues/1358

packages versions:
libgl1-mesa-dri:amd64 20.0.4-2ubuntu1 amd64 
xserver-xorg-video-intel  2:2.99.917+git20200226-1amd64
xserver-xorg-core 2:1.20.8-2ubuntu2   amd64

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

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

Title:
  segfault in iris_dri.so

Status in mesa package in Ubuntu:
  New

Bug description:
  As of Ubuntu 20.04, on intel graphics with intel driver (not
  modesetting), I got segfault whenever anything tries to use GL.

  This happens unless I export MESA_LOADER_DRIVER_OVERRIDE=i965. One
  says that it does not happen with modesetting driver.

  (gdb) run
  Starting program: /usr/bin/glxgears 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x717cf700 (LWP 97070)]
  [New Thread 0x7fffebfff700 (LWP 97071)]
  [New Thread 0x70fce700 (LWP 97072)]
  [New Thread 0x7fffeb7fe700 (LWP 97073)]

  Thread 1 "glxgears" received signal SIGSEGV, Segmentation fault.
  0x76a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  (gdb) where
  #0  0x76a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #1  0x76c42de4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #2  0x76a59e5d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #3  0x76a5aa95 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #4  0x76099774 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  #5  0x711e in ?? ()
  #6  0x6c88 in ?? ()
  #7  0x77ace0b3 in __libc_start_main (main=0x6410, argc=1, 
argv=0x7fffe698, init=, fini=, 
rtld_fini=, stack_end=0x7fffe688) at ../csu/libc-start.c:308
  #8  0x6f0a in ?? ()
  (gdb) 

  I believe, this is a bug in mesa tracked here:
  https://gitlab.freedesktop.org/mesa/mesa/issues/1358

  packages versions:
  libgl1-mesa-dri:amd64 20.0.4-2ubuntu1 
amd64 
  xserver-xorg-video-intel  2:2.99.917+git20200226-1
amd64
  xserver-xorg-core 2:1.20.8-2ubuntu2   
amd64

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

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


[Touch-packages] [Bug 1877875] [NEW] Pressing Alt+F1 with mouse cursor over the Applcations leads to focus move to Applications, the menus are unusable as result

2020-05-10 Thread Norbert
Public bug reported:

Steps to reproduce:
1. Have Ubuntu MATE 20.04 LTS installed
2. Login to session, choose Traditional desktop layout in MATE Tweak
3. Move move cursor over Applications menu
4. Press + to open Applications menu
5. Press  or 

Expected results:
* focus moves with  or  to corresponding one of the menu 
items - Applications, Places, System

Actual results:
* focus is stuck on Applications menu, about which mouse cursor is located (see 
screencast)

ProblemType: Bug
DistroRelease: Ubuntu Kylin 20.04
Package: mate-panel 1.24.0-2 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 5.4.0-29.33-lowlatency 5.4.30
Uname: Linux 5.4.0-29-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Sun May 10 18:57:48 2020
InstallationDate: Installed on 2020-04-22 (17 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200422)
SourcePackage: mate-panel
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: mate-panel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "menus.gif"
   https://bugs.launchpad.net/bugs/1877875/+attachment/5369525/+files/menus.gif

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Pressing Alt+F1 with mouse cursor over the Applcations leads to focus
  move to Applications, the menus are unusable as result

Status in gtk+3.0 package in Ubuntu:
  New
Status in mate-panel package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu MATE 20.04 LTS installed
  2. Login to session, choose Traditional desktop layout in MATE Tweak
  3. Move move cursor over Applications menu
  4. Press + to open Applications menu
  5. Press  or 

  Expected results:
  * focus moves with  or  to corresponding one of the 
menu items - Applications, Places, System

  Actual results:
  * focus is stuck on Applications menu, about which mouse cursor is located 
(see screencast)

  ProblemType: Bug
  DistroRelease: Ubuntu Kylin 20.04
  Package: mate-panel 1.24.0-2 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 5.4.0-29.33-lowlatency 5.4.30
  Uname: Linux 5.4.0-29-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sun May 10 18:57:48 2020
  InstallationDate: Installed on 2020-04-22 (17 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200422)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1877875/+subscriptions

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


[Touch-packages] [Bug 1685754]

2020-05-10 Thread A7x-gnome
This issue was fixed in systemd by
https://github.com/systemd/systemd/pull/15318. Debian cherry-picked that
change into 245.4-3, so Debian bullseye and buster-backports have the
fix, as does Ubuntu 20.04 (focal).

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

Title:
  'systemd --user' unduly forces umask=0022

Status in gedit:
  Invalid
Status in gnome-session:
  Invalid
Status in GNOME Terminal:
  Confirmed
Status in Nautilus:
  Invalid
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  In order to set the default umask of my users to 027 or 007, I
  followed the instructions provided in 'man pam_umask' :

  In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
  'umask=007' (for myself).

  Then, MOST graphical applications systematically run with the correct
  umask.

  In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
  it systematically displays 0007.

  But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
  it systematically displays 0022.

  That is BAD, and is a security issue.

  
  Workaround :  Inside the newly created '/etc/profile.d/umask.sh', and in each 
'~/.bashrc', add following content :
  UMASK="$(grep  -o  "^$USER:.*,umask=0[0-7]*"  /etc/passwd)"
  if  [ "$UMASK" ];  then
umask  "${UMASK#$USER:*,umask=}"
  fi

  
  In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.

  Thank you in advance for a quick correction.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 24 08:36:58 2017
  InstallationDate: Installed on 2017-03-28 (26 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1685754] Re: 'systemd --user' unduly forces umask=0022

2020-05-10 Thread Richard Hansen
** Also affects: systemd via
   https://github.com/systemd/systemd/issues/6077
   Importance: Unknown
   Status: Unknown

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

Title:
  'systemd --user' unduly forces umask=0022

Status in gedit:
  Invalid
Status in gnome-session:
  Invalid
Status in GNOME Terminal:
  Confirmed
Status in Nautilus:
  Invalid
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  In order to set the default umask of my users to 027 or 007, I
  followed the instructions provided in 'man pam_umask' :

  In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
  'umask=007' (for myself).

  Then, MOST graphical applications systematically run with the correct
  umask.

  In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
  it systematically displays 0007.

  But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
  it systematically displays 0022.

  That is BAD, and is a security issue.

  
  Workaround :  Inside the newly created '/etc/profile.d/umask.sh', and in each 
'~/.bashrc', add following content :
  UMASK="$(grep  -o  "^$USER:.*,umask=0[0-7]*"  /etc/passwd)"
  if  [ "$UMASK" ];  then
umask  "${UMASK#$USER:*,umask=}"
  fi

  
  In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.

  Thank you in advance for a quick correction.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 24 08:36:58 2017
  InstallationDate: Installed on 2017-03-28 (26 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1685754] Re: gnome-terminal unduly forces umask=0022

2020-05-10 Thread Richard Hansen
** Tags removed: focal

** Summary changed:

- gnome-terminal unduly forces umask=0022
+ 'systemd --user' unduly forces umask=0022

** Changed in: gnome-terminal (Ubuntu)
   Status: Confirmed => Invalid

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

** Changed in: gnome-session
   Status: New => Invalid

** Changed in: nautilus
   Status: Confirmed => 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/1685754

Title:
  'systemd --user' unduly forces umask=0022

Status in gedit:
  Invalid
Status in gnome-session:
  Invalid
Status in GNOME Terminal:
  Confirmed
Status in Nautilus:
  Invalid
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  In order to set the default umask of my users to 027 or 007, I
  followed the instructions provided in 'man pam_umask' :

  In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
  'umask=007' (for myself).

  Then, MOST graphical applications systematically run with the correct
  umask.

  In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
  it systematically displays 0007.

  But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
  it systematically displays 0022.

  That is BAD, and is a security issue.

  
  Workaround :  Inside the newly created '/etc/profile.d/umask.sh', and in each 
'~/.bashrc', add following content :
  UMASK="$(grep  -o  "^$USER:.*,umask=0[0-7]*"  /etc/passwd)"
  if  [ "$UMASK" ];  then
umask  "${UMASK#$USER:*,umask=}"
  fi

  
  In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.

  Thank you in advance for a quick correction.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 24 08:36:58 2017
  InstallationDate: Installed on 2017-03-28 (26 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1876962] Re: package libxml2:amd64 2.9.4+dfsg1-6.1ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con

2020-05-10 Thread Mattia Rizzolo
Did you try to contact user support for this?

That's clearly some kind of installation error, likely from some
interrupted process.

Try `sudo dpkg --configure -a` followed by `sudo apt -f install`, if
that doesn't work then an `apt install --reinstall libxml2`.

If you can't bring it to heel, please ask at user support for
directions.

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

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

Title:
  package libxml2:amd64 2.9.4+dfsg1-6.1ubuntu1.3 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libxml2 package in Ubuntu:
  Incomplete

Bug description:
  Fresh install of Ubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libxml2:amd64 2.9.4+dfsg1-6.1ubuntu1.3
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  Uname: Linux 4.15.0-99-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  AptOrdering:
   python3-distupgrade:amd64: Install
   python3-update-manager:amd64: Install
   update-manager-core:amd64: Install
   update-manager:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue May  5 17:56:48 2020
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2020-05-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.1
  SourcePackage: libxml2
  Title: package libxml2:amd64 2.9.4+dfsg1-6.1ubuntu1.3 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1827498] Re: Geoclue 2 very high memory usage

2020-05-10 Thread Ian Turner
I saw this issue using geoclue-2.0 2.5.3-1ubuntu1 on eoan.

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

Title:
  Geoclue 2 very high memory usage

Status in geoclue package in Ubuntu:
  Confirmed

Bug description:
  After geoclue 2 running at high CPU for some minutes I found CPU usage
  had dropped to zero but geoclue was still hogging a whopping 11GB of
  memory (the PC has 16GB). I stopped the geoclue service to recover the
  memory.

  Kubuntu 18.04

  $ apt-cache policy geoclue-2.0
  geoclue-2.0:
Installed: 2.4.7-1ubuntu1
Candidate: 2.4.7-1ubuntu1
Version table:
   *** 2.4.7-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Happy to provide other info on request.

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

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


[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

2020-05-10 Thread Dan Streetman
@american your issue has nothing to do with this bug; this applies only
to bridges with static configuration.  You are not using a bridge and
you are not using static configuration.

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

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

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

Bug description:
  [impact]

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

  [test case]

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

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

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

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

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

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

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

  [regression potential]

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

  [scope]

  This is needed for Focal, Eoan, and Bionic.

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

  [original description]

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

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

  however when converted to a bridged network for kvm

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

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

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

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

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

  systemctl restart systemd-networkd resolved the issue and a

  systemctl status systemd-network 

[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

2020-05-10 Thread Dan Streetman
I changed the f/g status back; also I set groovy to fit committed.

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

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

** Changed in: systemd (Ubuntu Groovy)
   Status: In Progress => Fix Committed

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

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

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

Bug description:
  [impact]

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

  [test case]

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

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

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

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

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

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

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

  [regression potential]

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

  [scope]

  This is needed for Focal, Eoan, and Bionic.

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

  [original description]

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

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

  however when converted to a bridged network for kvm

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

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

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

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

  Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for 
link '5' we don't know about, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an 
address we don't remember: 

[Touch-packages] [Bug 1876046] Re: [XPS L501X, Realtek ALC665, Speaker, Internal]

2020-05-10 Thread kffiatek
So, I've tried. Reinstalling did not help. Also, problem is even worse
on kubuntu i've tried. There is no option "Analog Stereo Duplex
(unplugged)(unavailable)" to choose and turn on sound.

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

Title:
  [XPS L501X, Realtek ALC665, Speaker, Internal]

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 19.04 to 20.04 sound did not work. "Analog Stereo" and 
"Build-in speaker" appears "unplugged/unavaiable". I can change it in volume 
control -> configuration to Analog Stereo Duplex (unplugged)(unavaiable) and 
sound does play, but after each reboot computer changes to Digital Stereo 
IEC985 and do not play sound until changed again.
  I did reinstall of alsa and pulse according to some forums but this didn't 
work.
  Before upgrade everything always worked out of the box since 2009 on this 
computer. I know it's a little old but it works excellent! Please help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kwiatek1472 F pulseaudio
   /dev/snd/controlC0:  kwiatek1472 F pulseaudio
   /dev/snd/pcmC0D0c:   kwiatek1472 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kwiatek1472 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Thu Apr 30 09:25:27 2020
  InstallationDate: Installed on 2020-02-25 (64 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kwiatek1472 F pulseaudio
   /dev/snd/controlC0:  kwiatek1472 F pulseaudio
   /dev/snd/pcmC0D0c:   kwiatek1472 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kwiatek1472 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [XPS L501X, Realtek ALC665, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to focal on 2020-04-25 (4 days ago)
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn:rvrA08:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: XPS L501X
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1877856] [NEW] Display garbled after resume from suspect

2020-05-10 Thread Joshua Colson
Public bug reported:

I just upgraded 18.04 -> 20.04. Then after resuming from suspend on my
laptop, the display is garbled blocks of random colors. It changes
frequently to other random colors. Power cycling the laptop clears the
issue, but only until it is suspended again.

The VT3 console shows:

nouveau :01:00.0: gr: PGRAPH_TLB flush idle timeout fail

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun May 10 05:53:41 2020
DistUpgraded: 2020-05-09 01:40:08,730 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: Dell GT218M [NVS 3100M] [1028:040a]
MachineType: Dell Inc. Latitude E6410
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=/dev/mapper/ubuntu--vg-root ro
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-05-09 (1 days ago)
dmi.bios.date: 12/05/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 0K42JR
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0K42JR:rvrA03:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6410
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Sat May 19 22:08:24 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Display garbled after resume from suspect

Status in xorg package in Ubuntu:
  New

Bug description:
  I just upgraded 18.04 -> 20.04. Then after resuming from suspend on my
  laptop, the display is garbled blocks of random colors. It changes
  frequently to other random colors. Power cycling the laptop clears the
  issue, but only until it is suspended again.

  The VT3 console shows:

  nouveau :01:00.0: gr: PGRAPH_TLB flush idle timeout fail

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 10 05:53:41 2020
  DistUpgraded: 2020-05-09 01:40:08,730 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: Dell GT218M [NVS 3100M] [1028:040a]
  MachineType: Dell Inc. Latitude E6410
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-05-09 (1 days ago)
  dmi.bios.date: 12/05/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0K42JR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0K42JR:rvrA03:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6410
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.
  

[Touch-packages] [Bug 1859308] Re: software-properties-gtk erroneously reports that Intel Wireless-AC 9260 device is not working

2020-05-10 Thread Mason Bee
For me it works on 5GHz but not on 2GHz wireless.

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

Title:
  software-properties-gtk erroneously reports that Intel Wireless-AC
  9260 device is not working

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 20.04 (development branch), as of today, Additional Drivers
  (software-properties-gtk 0.98.6) reports that the device "Intel
  Corporation: Wireless-AC 9260" is not working, and suggests using a
  manually installed driver (cf. screenshot).

  However the device is working correctly:

    * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show
  that its driver iwlwifi is in use
    * ls /lib/firmware/*9260* show that the appropriate firmware files
  are present

  And I am indeed writing this bug report connected to an ac (5 GHz)
  wifi network, where I can verify a ~130-160 Mbps download speed, so
  software-properties-gtk shouldn't report the device as not working and
  suggest manually installing a driver. Not sure why it says so?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.6
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 12 00:53:43 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-12-29 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 574287] Re: tasksel: forcefully removes packages when tasks overlap

2020-05-10 Thread Colonel Angus
Like Elias M Ward, I installed lamp-server using taskel. It didn't work
as expected and upon uninstalling, taskel removed everything. I came
back to my desk, and the system was shot. No network, no desktop,
nothing. Luckily, this was a fresh install, so a reinstall was the
quickest way to get a usable system.

Very, very poorly thought out.

Ten years later? Wow.

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

Title:
  tasksel: forcefully removes packages when tasks overlap

Status in apt package in Ubuntu:
  Invalid
Status in tasksel package in Ubuntu:
  Confirmed
Status in tasksel package in Debian:
  Fix Released

Bug description:
  TEST CASE

  1. Boot Lucid LiveCD

  2. run "sudo tasksel" and select "virtual machine host"

  3. run "sudo tasksel" and deselect "virtual machine host"

  4. watch how tasksel uninstalls your system

  OBSERVATIONS

  What seems to happen is that apt vengefully removes ALL of the items
  associated with one task, including several base dependencies of other
  tasks (e.g. ubuntu-desktop)

  One illustrative example is the openssh-server task:
  This one includes the packages openssh-server, tcpd and libwrap0.
  From a normal ubuntu-desktop (e.g. ~liveCD) both tcpd and libwrap0 are 
already installed, and the task-install pulls in only openssh-server.
  However when the task is removed, all these three packages (openssh-server, 
tcpd and libwrap0) are forcefully removed.
  Since libwrap0 is a core dependency of gnome, a large part of gnome will be 
removed alongside the removal of the task.

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

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


[Touch-packages] [Bug 1877726] Re: [HDA-Intel - HD-Audio Generic, playback] USB sound with Rodecaster Pro not working

2020-05-10 Thread nils
[NOTE: Apologies for the paste, but for some reason the answer got
deleted from askubuntu (This post is hidden. It was deleted 12 hours ago
by fossfreedom♦. ...so much for "freedom" ; ) If someone can tell me
why, I would appreciate it. I gave the answer (Rodecaster appears not to
be supported) and showed a lot of debugging effort leading to that
conclusion.]

I have the same issue... I tried many things, but could not get the
Rodecaster working. I did learn quite a bit and got the Scarlett 2i2
working though.

  - lsusb
Bus 001 Device 002: ID 19f7:0011 RODE Microphones RODECaster Pro
  - ls -al /dev/snd/by-id/
lrwxrwxrwx 1 root root  12 May  6 11:44 
usb-RODE_Microphones_RODECaster_Pro_001A-01 -> ../controlC2
  - cat /proc/asound/cards
2 [Pro]: USB-Audio - RODECaster Pro
RODE Microphones RODECaster Pro at usb-:01:00.0-3, high speed
  - cat /proc/asound/modules 
0 snd_usb_audio
1 snd_hda_intel
  - lsmod | grep snd_usb_audio looks OK
  - arecord --list-devices does not show it
  - aplay -L shows usbstream:CARD=GenericHD-Audio GenericUSB Stream 
Output and a lot of other (normal motherboard) devices but nothing with Rode 
and nothing else USB
  - aplay --device=usbstream
ALSA lib pcm_usb_stream.c:486:(_snd_pcm_usb_stream_open) Invalid type for 
card
aplay: main:828: audio open error: Invalid argument
  - cat /proc/asound/pcm does not show it
  - editing /etc/modprobe.d/alsa-base.conf to add these two lines at the end:
options snd-usb-audio index=0
options snd-hda-intel index=1 ...but no change after a reboot. Idea from 
https://unix.stackexchange.com/questions/220224/alsa-not-detecting-my-soundcard
  - editing /etc/modprobe.d/alsa-base.conf to add options snd 
slots=snd-usb-audio,snd-hda-intel did not change anything either
  - blacklisting snd_hda_intel in /etc/modprobe.d/blacklist-sound.conf by 
adding blacklist snd_hda_intel to that file (create it if necessary) and 
rebooting disabled it, but did not help with the USB sound for the Rodecaster
  - pulseaudio -k && sudo alsa force-reload after the changes (instead of a 
reboot) doesn't change anything either. Note: pulseaudio restarts itself and 
does not need to be manually restarted (Is there another way to restart the 
sound system if pulseaudio/ALSA don't work?)

The Answer (as it appears to me at least):

  - The Rodecaster is recognized as a USB device, but somehow not recognized by 
Alsa
  - I grabbed a Scarlett 2i2 gen3 
(https://wiki.linuxaudio.org/wiki/hardware_support)
  - edited /etc/modprobe.d/alsa-base.conf to comment out #options snd-usb-audio 
index=-2 to allow snd-usb-audio to be the first device
  - edited /etc/modprobe.d/alsa-base.conf to add options snd 
slots=snd-usb-audio,snd-hda-intel at the end to have the USB audio before the 
HDA Intel
  - pulseaudio -k && sudo alsa force-reload to reload the alsa config

Then the Scarlett showed up. Leaving the HDA Intel first did not let the
Scarlett show up.

Helpful info:

  - https://www.alsa-project.org/main/index.php/Help_To_Debug ...the 
alsa-info.sh looks like a fairly complete alsa debugging info summary generator
  - https://wiki.ubuntu.com/DebuggingSoundProblems
  - bug filed: 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877726

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

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

Status in alsa-driver package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

2020-05-10 Thread Andrew Welham
each server starts if the other is not running, but starting them
together caused this issue

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

Title:
  DHCP Cluster crashes after a few hours

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872118/+subscriptions

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


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

2020-05-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

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

Status in linux package in Ubuntu:
  Confirmed
Status in rtkit package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in rtkit source package in Focal:
  Confirmed

Bug description:
  SRU Justification

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

  Fix: Turn this option back off.

  Test Case: See comment #4.

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

  ---

  These errors started right after upgrading to 20.04.

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

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

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


[Touch-packages] [Bug 1877542] Re: Ubuntu 18.04.4 Inspiron 5379 No sound ALC3253 alsa-driver

2020-05-10 Thread Alex
** Summary changed:

- Ubuntu 18.04 No sound ALC3253  alsa-driver
+ Ubuntu 18.04.4 Inspiron 5379 No sound ALC3253  alsa-driver

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

Title:
  Ubuntu 18.04.4 Inspiron 5379 No sound ALC3253  alsa-driver

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,
  After last general update sound stops working on all interfaces. speakers, 
headphones nor HDMI provide any sound output even bluetooth headphones can't be 
connected.
  It seems that interface is connected to HDMI
  aplay -l

   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3253 Analog [ALC3253 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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


[Touch-packages] [Bug 1877717] Re: Sound stop working after wakeup

2020-05-10 Thread Svetov Mikhail
root@svmk-laptop:/var/log# grep pulseaudio syslog
May 10 16:08:31 svmk-laptop pulseaudio[87919]: Error opening PCM device 
front:0: Нет такого файла или каталога


** Attachment added: "Output of command `pacmd list`"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877717/+attachment/5369385/+files/pacmd_list.out.txt

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

Title:
  Sound stop working after wakeup

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  I don't know how to reproduce this bug. 
  Sometimes after notebook wakup sound stop working.
  pulseaudio -k fixes this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1925 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sat May  9 15:43:32 2020
  InstallationDate: Installed on 2018-04-03 (766 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to focal on 2020-04-24 (14 days ago)
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83C9
  dmi.board.vendor: HP
  dmi.board.version: 32.59
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd06/29/2017:svnHP:pnHPEnvy:pvrType1ProductConfigId:rvnHP:rn83C9:rvr32.59:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV NOTEBOOK
  dmi.product.name: HP Envy
  dmi.product.sku: 2PQ29EA#ACB
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Touch-packages] [Bug 1877829] [NEW] Won't reconnect to shared headphones

2020-05-10 Thread Alistair Cunningham
Public bug reported:

In Ubuntu 19.04, I could use my Sony WH-1000XM3 headphones with both my
laptop running Ubuntu, and my Android smartphone. The headphones would
pair with both, and I could simply re-enable the connection in Ubuntu or
Android to connect to the headphones if the other device had been using
the headphones last.

In Ubuntu 20.04, Ubuntu now refuses to reconnect to the headphones if my
Android phone was using the headphones last. I have to manually unpair
the headphones and re-pair them again. This is very inconvenient.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun May 10 15:44:22 2020
InstallationDate: Installed on 2017-08-16 (997 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20HFCTO1WW
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to focal on 2020-04-12 (27 days ago)
dmi.bios.date: 11/29/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1WET57W (1.36 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET57W(1.36):bd11/29/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470s
dmi.product.name: 20HFCTO1WW
dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
dmi.product.version: ThinkPad T470s
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: F8:59:71:8D:1A:16  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:20456 acl:96 sco:0 events:2692 errors:0
TX bytes:604938 acl:84 sco:0 commands:2573 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T23:41:27.085337

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


** Tags: amd64 apport-bug focal

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

Title:
  Won't reconnect to shared headphones

Status in bluez package in Ubuntu:
  New

Bug description:
  In Ubuntu 19.04, I could use my Sony WH-1000XM3 headphones with both
  my laptop running Ubuntu, and my Android smartphone. The headphones
  would pair with both, and I could simply re-enable the connection in
  Ubuntu or Android to connect to the headphones if the other device had
  been using the headphones last.

  In Ubuntu 20.04, Ubuntu now refuses to reconnect to the headphones if
  my Android phone was using the headphones last. I have to manually
  unpair the headphones and re-pair them again. This is very
  inconvenient.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun May 10 15:44:22 2020
  InstallationDate: Installed on 2017-08-16 (997 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HFCTO1WW
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to focal on 2020-04-12 (27 days ago)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: