[Touch-packages] [Bug 1878670] Re: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2)

2020-05-21 Thread Timo Aaltonen
** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8
  GT2)

Status in OEM Priority Project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  The system freezes frequently then logs out.
  If happens at apparently random times, and using no particular app.

  Extract of syslog is attached.

  Requested info is below:

  1) release
  Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30)

  2) package version
  gnome-session:
Installeret: (ingen)
Kandidat:3.28.1-0ubuntu3
Versionstabel:
   3.28.1-0ubuntu3 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
   3.28.1-0ubuntu2 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) Gnome shouldn't crash

  4) Gnome crashed

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

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


[Touch-packages] [Bug 1879159] Re: Boot Problem

2020-05-21 Thread Alex Murray
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Boot Problem

Status in xorg package in Ubuntu:
  New

Bug description:
  It shows graphics problem during booting and unable to operate mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219
  Uname: Linux 4.4.0-179-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun May 17 13:19:12 2020
  DistUpgraded: 2020-03-29 23:06:17,899 DEBUG /openCache(), new cache size 56855
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0555]
  InstallationDate: Installed on 2020-03-24 (54 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: Dell Inc. Inspiron 3520
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-179-generic 
root=UUID=2e048bbe-fc79-442e-ae8d-aac97ebb2938 ro quiet splash vt.handoff=7 
init=/sbin/upstart
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2020-03-29 (48 days ago)
  dmi.bios.date: 05/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0486TW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/31/2018:svnDellInc.:pnInspiron3520:pvrNotSpecified:rvnDellInc.:rn0486TW:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3520
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun May 17 13:15:51 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   21569 
   vendor SEC
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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


[Touch-packages] [Bug 1879211] Re: Charging my cellphone through usb breaks internet connection.

2020-05-21 Thread Alex Murray
One more thing - I expect your phone has USB Tethering enabled - and so
presents itself as an rndis USB/ethernet device - and then network
manager uses this as a preferred interface to route traffic through
rather than the wireless interface.

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

Title:
  Charging my cellphone through usb breaks internet connection.

Status in network-manager package in Ubuntu:
  New

Bug description:
  I don't know what package is responsible for this. I entered iptables
  because the ip command was not recognized as a package.

  I use the ip route to debug internet problems. Here it is before plugging my 
cellphone through usb:
  #ip route
  default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
  25.0.0.0/8 dev ham0 proto kernel scope link src 25.69.248.65 
  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
  192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.51 metric 600 
  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown 

  Here it is after I plug my cellphone
  #ip route
  default via 192.168.42.129 dev enp0s20f0u1 proto dhcp metric 100 
  default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
  25.0.0.0/8 dev ham0 proto kernel scope link src 25.69.248.65 
  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
  192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.51 metric 600 
  192.168.42.0/24 dev enp0s20f0u1 proto kernel scope link src 192.168.42.114 
metric 100 
  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown 

  So my computer is trying to access all ips using my cellphone as a
  router, which of course fails.

  the command "sudo ip route del default" followed by "sudo ip route add
  default via 192.168.0.1 dev wlp2s0" restores my connection.

  Thank you for your attention. I'm available to answer any questions
  and fix this bug. Reporting this bug was already effort diverted from
  my other tasks, so let's make this count no matter how deep it cuts.

  P.S: I went ahead and marked this bug as a security vulnerability
  because I can think of ways this can be exploited, especially if the
  cellphone can trigger the bug and route traffic so that the user
  doesn't suspect it. If you feel the security impact is small and that
  there are other more important security issues, feel free to unmark it
  and we can deal with it's usability impact, which is probably more
  impactful.

  Regards,
  Tomás.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: iptables 1.6.1-2ubuntu2
  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.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 17 22:59:02 2020
  InstallationDate: Installed on 2019-02-08 (464 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: iptables
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1879211] Re: Charging my cellphone through usb breaks internet connection.

2020-05-21 Thread Alex Murray
This doesn't seem like a security issue to me - I believe this is the
default behaviour when using network manager for tethering - it will
route traffic via the tethered device. I am reassigning this against
network-manager which is likely doing the route setup.

** Information type changed from Private Security to Public

** Package changed: iptables (Ubuntu) => network-manager (Ubuntu)

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

Title:
  Charging my cellphone through usb breaks internet connection.

Status in network-manager package in Ubuntu:
  New

Bug description:
  I don't know what package is responsible for this. I entered iptables
  because the ip command was not recognized as a package.

  I use the ip route to debug internet problems. Here it is before plugging my 
cellphone through usb:
  #ip route
  default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
  25.0.0.0/8 dev ham0 proto kernel scope link src 25.69.248.65 
  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
  192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.51 metric 600 
  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown 

  Here it is after I plug my cellphone
  #ip route
  default via 192.168.42.129 dev enp0s20f0u1 proto dhcp metric 100 
  default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
  25.0.0.0/8 dev ham0 proto kernel scope link src 25.69.248.65 
  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
  192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.51 metric 600 
  192.168.42.0/24 dev enp0s20f0u1 proto kernel scope link src 192.168.42.114 
metric 100 
  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown 

  So my computer is trying to access all ips using my cellphone as a
  router, which of course fails.

  the command "sudo ip route del default" followed by "sudo ip route add
  default via 192.168.0.1 dev wlp2s0" restores my connection.

  Thank you for your attention. I'm available to answer any questions
  and fix this bug. Reporting this bug was already effort diverted from
  my other tasks, so let's make this count no matter how deep it cuts.

  P.S: I went ahead and marked this bug as a security vulnerability
  because I can think of ways this can be exploited, especially if the
  cellphone can trigger the bug and route traffic so that the user
  doesn't suspect it. If you feel the security impact is small and that
  there are other more important security issues, feel free to unmark it
  and we can deal with it's usability impact, which is probably more
  impactful.

  Regards,
  Tomás.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: iptables 1.6.1-2ubuntu2
  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.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 17 22:59:02 2020
  InstallationDate: Installed on 2019-02-08 (464 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: iptables
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2020-05-21 Thread Alex Murray
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  when i was my computer on and start blinking middle of screen please
  solve it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 10:24:02 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Touch-packages] [Bug 1868405] Re: Untranslatable "Monitor of ..."

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

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

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

Title:
  Untranslatable "Monitor of ..."

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  It is impossible to translate string "Monitor of %s". Please add
  gettext call here and export the string into the .pot template.

  
https://git.launchpad.net/ubuntu/+source/pulseaudio/tree/src/pulsecore/sink.c?id=25a10a09f88d51bfd7d80574fa6c329086630531#n373

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

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


[Touch-packages] [Bug 1878327] Re: [Dell Inspiron 1525] Pulse audio update made internal speakers as Dummy Output

2020-05-21 Thread Rajasekharan N
*** This bug is a duplicate of bug 1876065 ***
https://bugs.launchpad.net/bugs/1876065

To anyone landing on this page:

Current version is pulseaudio 1:13.99.1-1ubuntu3.2.

There is a fix/patch in this PPA that you can use it for now until the
next update/release (Version: pulseaudio 1:13.99.1-1ubuntu3.2lp1869819):

https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819

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

Title:
  [Dell Inspiron 1525] Pulse audio update made internal speakers as
  Dummy Output

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I had already reported bug #1876238 where internal speakers are not
  detected but shown as Dummy Output after upgrading Ubuntu from 19.10
  to 20.04 LTS Focal.

  It was solved by this patch:
  https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819

  The current PulseAudio update today reversed that again. Internal
  speakers are not being detected and are shown as Dummy Output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raj2016 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 13 09:02:53 2020
  InstallationDate: Installed on 2016-12-20 (1239 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

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

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


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

2020-05-21 Thread Rajasekharan N
@Kai-Heng Feng (kaihengfeng)

Downloaded the patch and updated the PulseAudio.

The internal speakers, both the headphone jacks and the internal mic,
all are working fine now. (Didn't test the external mic jack.)

Thanks a gazillion.

I can return the borrowed laptop to my neighbor and start working with
mine.

You are a god-sent angel to save me from trouble. May God bless you.

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

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

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

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

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

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

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

  

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

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

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

  Any help greatly appreciated.

  Regards,
  Roman

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

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


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

2020-05-21 Thread Daniel van Vugt
Looks like there's an assertion failure in Xorg (in XorgLogOld.txt) but
that stack trace is almost certainly wrong. Please follow the above
instructions.

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

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

Title:
  Xorg crash

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Fresh Ubuntu 18.04.4 LTS bionic installation.
  Nouveau driver.
  One DVI cable attached directly to the graphics card, and one DVI + one VGA 
attached to the motherboard.
  When I attempted to open "Display" settings the x-org session crashes and 
reverts to the login screen.
  Other programs like Firefox and Terminal seem to run fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-53-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 17:14:11 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] 
[19da:2438]
  InstallationDate: Installed on 2020-05-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Micro-Star International Co., Ltd. MS-7A34
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic 
root=UUID=ddd8f597-f590-4fc5-ac56-8ba3805b40e8 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.90
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350 PC MATE (MS-7A34)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.90:bd12/06/2017:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A34
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Touch-packages] [Bug 1878775] Re: gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from _systemd_session_is_graphical() from _find_gr

2020-05-21 Thread Daniel van Vugt
** Description changed:

+ https://errors.ubuntu.com/problem/ef271ce6e134d51dbb0fde393051bdcce3f16cf8
+ https://errors.ubuntu.com/problem/bd6ce0ebb5afe5054592e605660dff1d41db4f34
+ 
+ ---
+ 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.36.2-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/ef271ce6e134d51dbb0fde393051bdcce3f16cf8 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

Title:
  gnome-shell crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from
  _systemd_session_is_graphical() from _find_graphical_systemd_session()

Status in accountsservice package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/ef271ce6e134d51dbb0fde393051bdcce3f16cf8
  https://errors.ubuntu.com/problem/bd6ce0ebb5afe5054592e605660dff1d41db4f34

  ---

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

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

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


[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

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

If that was true then bug 1878194 would be a duplicate of this one
because this one is older.

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1879525] Re: Add TLS support

2020-05-21 Thread Launchpad Bug Tracker
This bug was fixed in the package busybox - 1:1.30.1-4ubuntu8

---
busybox (1:1.30.1-4ubuntu8) groovy; urgency=medium

  * Enable TLS verification with OpenSSL. LP: #1879533

busybox (1:1.30.1-4ubuntu7) groovy; urgency=medium

  * Enable TLS in initramfs flavour of wget applet, requires openssl. LP:
#1879525

 -- Dimitri John Ledkov   Wed, 20 May 2020 14:44:54
+0100

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

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

Title:
  Add TLS support

Status in busybox package in Ubuntu:
  Fix Released
Status in busybox source package in Focal:
  New

Bug description:
  [Impact]

   * busybox in the initramfs provides wget applet that is used by casper for 
netboot support
   * It does not support https at the moment, but it is desirable that it does
   * There is built-in TLS code, or "fork & execute openssl"
   * Enable the later one, and optionally include /usr/bin/openssl & certs, 
when building casper-like initrds which should support netboot.

  [Test Case]

   * Boot casper created initrd, with break=bottom
   * Configure dhcp based networking
   * Attempt to wget https://start.ubuntu.com/connectivity-check
   * It should succeed

  [Regression Potential]

   * The openssl codepath is optional in busybox wget, and we only include 
openssl & certs for casper.
   * The casper based initrd will grow in size, due to inclusion of openssl & 
certs

  [Other Info]
   
   * Parity with d-i, which includes https support already

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

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


[Touch-packages] [Bug 1879533] Re: busybox does not verify TLS connections with CONFIG_FEATURE_WGET_OPENSSL=y and CONFIG_FEATURE_WGET_HTTPS unset, and doesn't warn either about it

2020-05-21 Thread Launchpad Bug Tracker
This bug was fixed in the package busybox - 1:1.30.1-4ubuntu8

---
busybox (1:1.30.1-4ubuntu8) groovy; urgency=medium

  * Enable TLS verification with OpenSSL. LP: #1879533

busybox (1:1.30.1-4ubuntu7) groovy; urgency=medium

  * Enable TLS in initramfs flavour of wget applet, requires openssl. LP:
#1879525

 -- Dimitri John Ledkov   Wed, 20 May 2020 14:44:54
+0100

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

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

Title:
  busybox does not verify TLS connections with
  CONFIG_FEATURE_WGET_OPENSSL=y and CONFIG_FEATURE_WGET_HTTPS unset, and
  doesn't warn either about it

Status in busybox package in Ubuntu:
  Fix Released
Status in busybox source package in Focal:
  New
Status in busybox source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * CONFIG_FEATURE_WGET_OPENSSL=y enables https support in wget busybox
  applet using openssl

   * CONFIG_FEATURE_WGET_HTTPS=y enables https support in wget busybox
  applet using internal TLS code

   * CVE-2018-1000500 ensured that when CONFIG_FEATURE_WGET_HTTPS=y is
  used, a message is printed to notify the users that TLS verification
  is not perfomed.

   * However, when one configures with CONFIG_FEATURE_WGET_OPENSSL=y and
  CONFIG_FEATURE_WGET_HTTPS unset - no such message is printed.

   * Also TLS verification is not performed under OPENSSL case.

   * When performing https requests, it works openssl s_client and communicates 
with it to perform https download
   * Whilst doing so, it does not pass `-verify_return_error` option, meaning 
any verification errors are ignored

   * There is no warning that TLS verification was not performed

  [Test Case]

   * Preparation: sudo apt install busybox; or build busybox with
  CONFIG_FEATURE_WGET_OPENSSL=y

   * Test case: /bin/busybox wget https://untrusted-root.badssl.com/

   * Expected: download failed, or download suceeds with warning printed
  that verification is disabled

   * Observed: download success without a warning that verification is
  disabled.

  $ /bin/busybox wget https://untrusted-root.badssl.com/
  Connecting to untrusted-root.badssl.com (104.154.89.105:443)
  index.html   100% 
|*|
   600  0:00:00 ETA

  $ cat index.html  | grep certificate
    The certificate for this site is signed using an untrusted root.

  [Regression Potential]

   * The fact that /bin/busybox wget https:// succeeds without TLS
  verification might be relied upon. If this issue is fixed, ensure that
  `--no-check-certificate` is honored.

  [Other Info]

   * Proposed fix

     pass `-verify_return_error` to s_client, unless `--no-check-
  certificate` is specified

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

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


[Touch-packages] [Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

2020-05-21 Thread Hui Wang
We have a private bug which is similar to it. #1875597

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

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:

  
  Summary
  ===

  Internal speakers work as expected, but when plugging headphones
  through the 3.5mm jack, the "Select Audio Device" panel doesn't show
  up (it normally shows up to allow user to select what kind of device
  has been plugged in, be it headphones, microphone or headset). In the
  Sound Settings, the Output Device automatically switches to
  "Headphones - sof-hda-dsp", but no sound can be heard even though the
  vumeter in the Sound Settings moves!

  Steps to reproduce
  ==

  1. Install focal beta
  2. Make sure the sound works as expected using the internal speakers and an 
audio file or Youtube
  3. Plug headphones in jack 3.5mm interface

  Expected Results
  

  - In Sound Settings, the headphones are automatically selected as output 
device
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound
  - Sound can be heard through the headphones

  
  Actual results
  ==

  - In Sound Settings, the headphones are automatically selected as output 
device (OK)
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound (OK)
  - No sound can be heard (Not OK)

  Attached are output of `pactl info` and `pactl list` before and after
  plugging headphones, while playing a tune on Bandcamp in Firefox.

  
  Additional Info
  ===

  Ubuntu: 20.04 beta image
  Certified device: 
  system-manufacturer: Dell Inc.
  system-product-name: Vostro 5590
  bios-version: 1.1.0
  CPU: Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9b41] (rev 02)
  01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1d13] (rev a1)
  kernel-version: 5.4.0-21-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1768 F pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1768 F...m pulseaudio
   /dev/snd/pcmC0D6c:   pieq   1768 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 16:33:27 2020
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/18/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5590
  dmi.product.sku: 095A
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

2020-05-21 Thread Hui Wang
We have a private bug which is similar to it.

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

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:

  
  Summary
  ===

  Internal speakers work as expected, but when plugging headphones
  through the 3.5mm jack, the "Select Audio Device" panel doesn't show
  up (it normally shows up to allow user to select what kind of device
  has been plugged in, be it headphones, microphone or headset). In the
  Sound Settings, the Output Device automatically switches to
  "Headphones - sof-hda-dsp", but no sound can be heard even though the
  vumeter in the Sound Settings moves!

  Steps to reproduce
  ==

  1. Install focal beta
  2. Make sure the sound works as expected using the internal speakers and an 
audio file or Youtube
  3. Plug headphones in jack 3.5mm interface

  Expected Results
  

  - In Sound Settings, the headphones are automatically selected as output 
device
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound
  - Sound can be heard through the headphones

  
  Actual results
  ==

  - In Sound Settings, the headphones are automatically selected as output 
device (OK)
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound (OK)
  - No sound can be heard (Not OK)

  Attached are output of `pactl info` and `pactl list` before and after
  plugging headphones, while playing a tune on Bandcamp in Firefox.

  
  Additional Info
  ===

  Ubuntu: 20.04 beta image
  Certified device: 
  system-manufacturer: Dell Inc.
  system-product-name: Vostro 5590
  bios-version: 1.1.0
  CPU: Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9b41] (rev 02)
  01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1d13] (rev a1)
  kernel-version: 5.4.0-21-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1768 F pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1768 F...m pulseaudio
   /dev/snd/pcmC0D6c:   pieq   1768 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 16:33:27 2020
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/18/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5590
  dmi.product.sku: 095A
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1879751] Re: ALSA sees my intel soundcards but pulseaudio does not. Error is : "Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa-card.so: /usr/lib/pulse-13.99.1/m

2020-05-21 Thread Hui Wang
snd_use_case_parse_ctl_elem_id() is defined in the latest libasound2
(>=1.2.1), maybe reinstall the libaousnd2 and pulseaudio could help.

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

Title:
  ALSA sees my intel soundcards but pulseaudio does not.  Error is :
  "Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa-
  card.so: /usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined
  symbol: snd_use_case_parse_ctl_elem_id, version ALSA_0.9"

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  ALSA sees my intel soundcards but pulseaudio does not.

  'pavucontrol' sees only a "Dummy" device.

  #journalctl|grep pulse' gives "pulseaudio[18489]: Failed to open
  module /usr/lib/pulse-13.99.1/modules/module-alsa-card.so:
  /usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined symbol:
  snd_use_case_parse_ctl_elem_id, version ALSA_0.9"

  Making pulseaudio from source fixes the problem/

  (Linux CF-C2CQAZXCM 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29
  14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux 20.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed May 20 12:48:07 2020
  InstallationDate: Installed on 2015-04-29 (1848 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-05-05 (15 days ago)
  dmi.bios.date: 09/12/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.00L21
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: CFC2-2
  dmi.board.vendor: Panasonic Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Panasonic Corporation
  dmi.chassis.version: 001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.00L21:bd09/12/2018:svnPanasonicCorporation:pnCF-C2CQAZXCM:pvr002:rvnPanasonicCorporation:rnCFC2-2:rvr1:cvnPanasonicCorporation:ct10:cvr001:
  dmi.product.family: CFC2-2
  dmi.product.name: CF-C2CQAZXCM
  dmi.product.sku: CF-C2CQAZXCM
  dmi.product.version: 002
  dmi.sys.vendor: Panasonic Corporation
  mtime.conffile..etc.init.d.apport: 2020-02-26T22:18:45

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

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


[Touch-packages] [Bug 1311056] Autopkgtest regression report (python-apt/1.6.5ubuntu0.3)

2020-05-21 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted python-apt (1.6.5ubuntu0.3) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

unattended-upgrades/unknown (armhf)
aptdaemon/1.1.1+bzr982-0ubuntu19.2 (armhf)
python-aptly/0.12.10-1 (arm64)


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

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

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

Thank you!

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

Title:
  [SRU] apt-add-repository adds duplicate commented/disabled source
  lines

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  Fix Committed
Status in python-apt source package in Bionic:
  Fix Committed
Status in python-apt source package in Eoan:
  Fix Committed

Bug description:
  Impact
  ==

  Under most circumstances, the impact is minimal (a few extra redundant
  comment lines in apt sources. However, if users are automating source
  removal / addition on a machine (as in comment 11), there is the
  potential to wind up with an excessively large (and thus slow to
  parse) apt sources configuration.

  Test packages for the supported releases are available from the
  following PPA:

  https://launchpad.net/~waveform/+archive/ubuntu/python-apt

  Built from the source which can be found in the following branches:

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-xenial

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-bionic

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-eoan

  Test Case
  =

  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the presence of one uncommented "deb" line, and one commented 
"deb-src" line
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the uncommented "deb" line is still there but the commented "deb-src" 
line has now been duplicated
  * sudo add-apt-repository ppa:waveform/python-apt
  * sudo apt upgrade  # update python-apt to fixed version
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note there has been no further duplication of the commented "deb-src" line

  Regression Potential
  

  Minimal; test cases have been added to cover the duplication case, and
  to cover the enabling of sources (which was not covered by existing
  tests, but was part of the code altered to fix the duplication case),
  and insertion of sources at a position (again, not covered by existing
  tests but modified as part of the fix). The test case has been used
  successfully on all targeted releases (xenial, bionic, and eoan).

  Original Description
  

  Trusty Tahr 14.04

  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list
  deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y 
ppa:aims/aims-desktop
  gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created
  gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created
  gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created
  gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)
  OK
  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb 
http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#

  That deb-src line should have stayed commented out, and not been
  duplicated. (Commented deb lines should of course be uncommented, as
  already fixed per https://bugs.launchpad.net/ubuntu/+source/python-
  apt/+bug/1042916 .)

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

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


[Touch-packages] [Bug 1311056] Autopkgtest regression report (python-apt/1.9.0ubuntu1.4)

2020-05-21 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted python-apt (1.9.0ubuntu1.4) for eoan 
have finished running.
The following regressions have been reported in tests triggered by the package:

ubiquity/19.10.21 (armhf)
aptdaemon/1.1.1+bzr982-0ubuntu28.1 (arm64, armhf)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#python-apt

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

Thank you!

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

Title:
  [SRU] apt-add-repository adds duplicate commented/disabled source
  lines

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  Fix Committed
Status in python-apt source package in Bionic:
  Fix Committed
Status in python-apt source package in Eoan:
  Fix Committed

Bug description:
  Impact
  ==

  Under most circumstances, the impact is minimal (a few extra redundant
  comment lines in apt sources. However, if users are automating source
  removal / addition on a machine (as in comment 11), there is the
  potential to wind up with an excessively large (and thus slow to
  parse) apt sources configuration.

  Test packages for the supported releases are available from the
  following PPA:

  https://launchpad.net/~waveform/+archive/ubuntu/python-apt

  Built from the source which can be found in the following branches:

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-xenial

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-bionic

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-eoan

  Test Case
  =

  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the presence of one uncommented "deb" line, and one commented 
"deb-src" line
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the uncommented "deb" line is still there but the commented "deb-src" 
line has now been duplicated
  * sudo add-apt-repository ppa:waveform/python-apt
  * sudo apt upgrade  # update python-apt to fixed version
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note there has been no further duplication of the commented "deb-src" line

  Regression Potential
  

  Minimal; test cases have been added to cover the duplication case, and
  to cover the enabling of sources (which was not covered by existing
  tests, but was part of the code altered to fix the duplication case),
  and insertion of sources at a position (again, not covered by existing
  tests but modified as part of the fix). The test case has been used
  successfully on all targeted releases (xenial, bionic, and eoan).

  Original Description
  

  Trusty Tahr 14.04

  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list
  deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y 
ppa:aims/aims-desktop
  gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created
  gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created
  gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created
  gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)
  OK
  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb 
http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#

  That deb-src line should have stayed commented out, and not been
  duplicated. (Commented deb lines should of course be uncommented, as
  already fixed per https://bugs.launchpad.net/ubuntu/+source/python-
  apt/+bug/1042916 .)

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

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


[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2020-05-21 Thread MegaBrutal
Hi Steve, Julian, Łukasz, everyone,

Sorry that I didn't test the package on time – my life circumstances
have significantly changed since I reported this bug, nowadays I don't
have enough free time to do as much testing as I did back in the day.
I've been using the workaround ever since then, returning to this now
after more than 4 years really feels nostalgic.

I still had my test VM from 2016, upgraded it up to Eoan and confirmed
the problem was present there as well. Then I installed the new lvm2
package which just got into -updates and indeed it fixed the issue. I
know this finding is not so useful after Julian has already tested, but
I wanted to see.

Since this problem was present from Wily and been around in all Ubuntu
releases onwards, are you going to port this fix to all currently
supported releases? While it's fixed for Bionic and Eoan; Xenial, Focal,
and the actual development version (Groovy) are still affected. Now that
I caught up on this again, do you want me to verify the problem in all
the remaining releases?

Anyway, thanks everyone who contributed to fixing this! :)

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

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Fix Released
Status in lvm2 package in Debian:
  Incomplete

Bug description:
  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.

  [Test case]

  1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv

  Reboot and check that it still boots.

  6. Remove mdadm
  7. Upgrade to lvm2 from proposed

  Reboot and check that it still boots.

  8. Downgrade lvm2 to release

  Reboot and check that it fails to boot

  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.

  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

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

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


[Touch-packages] [Bug 1861250] Re: Apparmor error failed to start profiles

2020-05-21 Thread Christian Boltz
Indeed, that's not really helpful :-(

Another idea - does

apparmor_parser -r /etc/apparmor.d/

print any output? (If yes, please paste or attach it.)

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

Title:
  Apparmor error failed to start profiles

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  OS Ubuntu focal fossa 20.04
  On boot error message - Apparmor Failed to start profiles.

  Steps attempted to correct

  1.sudo as status

  lee@lee-desktop:~$ sudo aa-status
  apparmor module is loaded.
  53 profiles are loaded.
  51 profiles are in enforce mode.
 /sbin/dhclient
 /snap/core/8268/usr/lib/snapd/snap-confine
 /snap/core/8268/usr/lib/snapd/snap-confine//mount-namespace-capture-helper
 /usr/bin/evince
 /usr/bin/evince-previewer
 /usr/bin/evince-previewer//sanitized_helper
 /usr/bin/evince-thumbnailer
 /usr/bin/evince//sanitized_helper
 /usr/bin/man
 /usr/lib/NetworkManager/nm-dhcp-client.action
 /usr/lib/NetworkManager/nm-dhcp-helper
 /usr/lib/connman/scripts/dhclient-script
 /usr/lib/cups/backend/cups-pdf
 /usr/lib/lightdm/lightdm-guest-session
 /usr/lib/lightdm/lightdm-guest-session//chromium
 /usr/lib/snapd/snap-confine
 /usr/lib/snapd/snap-confine//mount-namespace-capture-helper
 /usr/lib/telepathy/mission-control-5
 /usr/lib/telepathy/telepathy-*
 /usr/lib/telepathy/telepathy-*//pxgsettings
 /usr/lib/telepathy/telepathy-*//sanitized_helper
 /usr/lib/telepathy/telepathy-ofono
 /usr/sbin/cups-browsed
 /usr/sbin/cupsd
 /usr/sbin/cupsd//third_party
 /usr/sbin/ippusbxd
 /usr/sbin/tcpdump
 /usr/share/hplip/plugin.py
 /usr/share/hplip/sendfax.py
 /usr/share/hplip/setup.py
 /usr/share/hplip/systray.py
 /usr/share/hplip/toolbox.py
 libreoffice-senddoc
 libreoffice-soffice//gpg
 libreoffice-xpdfimport
 lsb_release
 man_filter
 man_groff
 nvidia_modprobe
 nvidia_modprobe//kmod
 snap-update-ns.core
 snap-update-ns.gnome-calculator
 snap-update-ns.gnome-characters
 snap-update-ns.gnome-logs
 snap-update-ns.gnome-system-monitor
 snap.core.hook.configure
 snap.gnome-calculator.gnome-calculator
 snap.gnome-characters.gnome-characters
 snap.gnome-logs.gnome-logs
 snap.gnome-system-monitor.gnome-system-monitor
 system_tor
  2 profiles are in complain mode.
 libreoffice-oopslash
 libreoffice-soffice
  3 processes have profiles defined.
  3 processes are in enforce mode.
 /usr/lib/telepathy/mission-control-5 (3090) 
 /usr/sbin/cupsd (1646) 
 /usr/bin/tor (1861) system_tor
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.
  lee@lee-desktop:~$ 

  2.sudo /etc/init.d/apparmor restart

  lee@lee-desktop:~$ sudo /etc/init.d/apparmor restart
  Restarting apparmor (via systemctl): apparmor.serviceJob for apparmor.service 
failed because the control process exited with error code.
  See "systemctl status apparmor.service" and "journalctl -xe" for details.
   failed!
  lee@lee-desktop:~$ 

  3.sudo rm -rf /etc/apparmor.d/cache/*

  4. sudo /etc/init.d/apparmor restart

  lee@lee-desktop:~$ sudo /etc/init.d/apparmor restart
  Restarting apparmor (via systemctl): apparmor.serviceJob for apparmor.service 
failed because the control process exited with error code.
  See "systemctl status apparmor.service" and "journalctl -xe" for details.
   failed!
  lee@lee-desktop:~$ 

  Thanks,

  Lee

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apparmor 2.13.3-7ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 28 23:19:19 2020
  InstallationDate: Installed on 2013-08-08 (2365 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=d2e1abc4-e044-467e-8cc2-57cbe4ef3115 ro drm.debug=0xe plymouth:debug
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-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-21 Thread Florian Obradovic
Same here:

/etc/netplan/01-netcfg.yaml

network:
  version: 2
  renderer: networkd
  ethernets:
eno1:
  dhcp4: no
  bridges:
br0:
  dhcp4: yes
  interfaces:
- eno1
  addresses:
- 192.168.xx.xx/24
- 2a02:...::xx/64
  gateway4: 192.168.xx.xx
  gateway6: fe80::...
  nameservers:
   addresses: [192.168.xx.xx]

sudo add-apt-repository ppa:ddstreet/lp1860926
sudo apt-get update

FIXED it for me.

-- 
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 Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Released

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

  [test case, pre-focal]

  same netplan as above, but remove ethernets: section.  Reboot, and the
  bridge should have its address and route:

  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
 valid_lft forever preferred_lft forever
  ubuntu@test-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static linkdown 
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 linkdown 

  
  add and remove carrier, by adding and removing a slave interface:

  ubuntu@test-e:~$ sudo ip l set dev ens3 master br0 up
  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
 valid_lft forever preferred_lft forever
  inet6 fe80::5411:daff:fe23:bb93/64 scope link 
 valid_lft forever preferred_lft forever
  ubuntu@test-e:~$ sudo ip l set dev ens3 nomaster

  
  the bridge no longer has its address after losing carrier:

  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::5411:daff:fe23:bb93/64 scope link 
 valid_lft forever preferred_lft forever


  [regression potential]

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

  [scope]

  This is needed for Focal, Eoan, and Bionic.

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

  [original description]

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

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

  however when converted to a bridged network for kvm

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

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

  after a reboot the network 

[Touch-packages] [Bug 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

2020-05-21 Thread Guilherme G. Piccoli
This was greatly debugged by LP user WGH in https://bugs.launchpad.net
/cloud-images/+bug/1573095/comments/46 - it's really a flaw on
initramfs, I managed to workaround the issue with "quiet" parameter
(system boots normally ,even with the wrong serial console).

Investigation continues... I guess this LP may end-up being a duplicate of 
1573095.
Thanks,


Guilherme

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

Title:
  machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel get stucks at boot if console=ttyS* is specified in the kernel
  cmdline and that serial HW isn't available on the system.

  Reproduced with:
  4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next 
(mainline)

  Removing the non-existent 'console=ttyS*' parameter fixes the
  situation.

  I tested it using KVM/qemu, but it has been brought to my attention
  that it was reproducible in VMware as well.

  I think it is safe to say that it is unlikely to be specifics to a
  certain virtualization technology type.

  Didn't test on baremetal yet.

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

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


[Touch-packages] [Bug 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

2020-05-21 Thread Eric Desrochers
** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

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

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => High

** Changed in: initramfs-tools (Ubuntu)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

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

Title:
  machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel get stucks at boot if console=ttyS* is specified in the kernel
  cmdline and that serial HW isn't available on the system.

  Reproduced with:
  4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next 
(mainline)

  Removing the non-existent 'console=ttyS*' parameter fixes the
  situation.

  I tested it using KVM/qemu, but it has been brought to my attention
  that it was reproducible in VMware as well.

  I think it is safe to say that it is unlikely to be specifics to a
  certain virtualization technology type.

  Didn't test on baremetal yet.

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

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


[Touch-packages] [Bug 1311056] Autopkgtest regression report (python-apt/1.1.0~beta1ubuntu0.16.04.9)

2020-05-21 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted python-apt (1.1.0~beta1ubuntu0.16.04.9) 
for xenial have finished running.
The following regressions have been reported in tests triggered by the package:

apport/2.20.1-0ubuntu2.23 (i386)
aptdaemon/1.1.1+bzr982-0ubuntu14.2 (armhf)


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

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

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

Thank you!

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

Title:
  [SRU] apt-add-repository adds duplicate commented/disabled source
  lines

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  Fix Committed
Status in python-apt source package in Bionic:
  Fix Committed
Status in python-apt source package in Eoan:
  Fix Committed

Bug description:
  Impact
  ==

  Under most circumstances, the impact is minimal (a few extra redundant
  comment lines in apt sources. However, if users are automating source
  removal / addition on a machine (as in comment 11), there is the
  potential to wind up with an excessively large (and thus slow to
  parse) apt sources configuration.

  Test packages for the supported releases are available from the
  following PPA:

  https://launchpad.net/~waveform/+archive/ubuntu/python-apt

  Built from the source which can be found in the following branches:

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-xenial

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-bionic

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-eoan

  Test Case
  =

  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the presence of one uncommented "deb" line, and one commented 
"deb-src" line
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the uncommented "deb" line is still there but the commented "deb-src" 
line has now been duplicated
  * sudo add-apt-repository ppa:waveform/python-apt
  * sudo apt upgrade  # update python-apt to fixed version
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note there has been no further duplication of the commented "deb-src" line

  Regression Potential
  

  Minimal; test cases have been added to cover the duplication case, and
  to cover the enabling of sources (which was not covered by existing
  tests, but was part of the code altered to fix the duplication case),
  and insertion of sources at a position (again, not covered by existing
  tests but modified as part of the fix). The test case has been used
  successfully on all targeted releases (xenial, bionic, and eoan).

  Original Description
  

  Trusty Tahr 14.04

  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list
  deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y 
ppa:aims/aims-desktop
  gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created
  gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created
  gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created
  gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)
  OK
  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb 
http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#

  That deb-src line should have stayed commented out, and not been
  duplicated. (Commented deb lines should of course be uncommented, as
  already fixed per https://bugs.launchpad.net/ubuntu/+source/python-
  apt/+bug/1042916 .)

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

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


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

2020-05-21 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

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

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

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Fresh Ubuntu 18.04.4 LTS bionic installation.
  Nouveau driver.
  One DVI cable attached directly to the graphics card, and one DVI + one VGA 
attached to the motherboard.
  When I attempted to open "Display" settings the x-org session crashes and 
reverts to the login screen.
  Other programs like Firefox and Terminal seem to run fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-53-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 17:14:11 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] 
[19da:2438]
  InstallationDate: Installed on 2020-05-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Micro-Star International Co., Ltd. MS-7A34
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic 
root=UUID=ddd8f597-f590-4fc5-ac56-8ba3805b40e8 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.90
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350 PC MATE (MS-7A34)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.90:bd12/06/2017:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A34
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Touch-packages] [Bug 1879905] Re: Can no longer connect to Ubuntu WPA hotspot after upgrade to 20.04

2020-05-21 Thread Sebastien Bacher
Thanks

** Changed in: network-manager (Ubuntu)
   Status: New => Triaged

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

** Also affects: network-manager via
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/450
   Importance: Unknown
   Status: Unknown

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

Title:
  Can no longer connect to Ubuntu WPA hotspot  after upgrade to 20.04

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  I upgraded my Ubuntu client to 20.04 and could continue to connect to
  my WPA Hotspot running on an Ubuntu server. Upon update of the server
  to 20.04 I could no longer connect with any of my various client OSs.

  After using the updated network-manager from
  https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/1870359, I can now connect to the hotspot from all of my
  machines running many flavors of OS (Windows, MacOS, Android, Ubuntu
  19.10), but I cannot connect from my machine running Ubuntu 20.04.

  If I turn off the encryption on the hotspot or turn on WEP encryption
  (using nm-connection-editor), then I can connect.

  Seeing that my client running 19.10 can connect, I'm not sure if this
  is a problem specif to my particular laptop running 20.04, or if it is
  rather a problem that any client updating to 20.04 will have. I will
  update my other 19.10 machine, that is currently working with the WPA
  hotspot, to help differentiate between these two possibilities.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 10:51:00 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   #dns-nameservers 8.8.8.8 8.8.4.4
  IpRoute:
   default via 192.168.0.1 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.17 metric 600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-10-31T09:47:24.831648
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

2020-05-21 Thread Eric Desrochers
** Summary changed:

- kernel get stuck at boot if specified 'console=ttyS* ' doesn't exist.
+ machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  kernel get stucks at boot if console=ttyS* is specified in the kernel
  cmdline and that serial HW isn't available on the system.

  Reproduced with:
  4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next 
(mainline)

  Removing the non-existent 'console=ttyS*' parameter fixes the
  situation.

  I tested it using KVM/qemu, but it has been brought to my attention
  that it was reproducible in VMware as well.

  I think it is safe to say that it is unlikely to be specifics to a
  certain virtualization technology type.

  Didn't test on baremetal yet.

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

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


[Touch-packages] [Bug 1879206] Re: cups hplip not install printer

2020-05-21 Thread Stefano Dall'Agata
You can remove the print queue (cancel the job) and then disconnect and 
reconnect the printer.
A new print queue is not automatically recreated.

~$ lpstat -v
dispositivo per DeskJet_3630: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
dispositivo per HP_DeskJet_3630_series: 
dnssd://HP%20DeskJet%203630%20series%20%5B9B20BB%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-f439099b20bb

~$ driverless
ipp://DeskJet%203630%20series%20%5BCN8AM7H3230658%5D._ipp._tcp.local/
ipp://HP%20DeskJet%203630%20series%20%5B9B20BB%5D._ipp._tcp.local/

~$ ps auxwww | grep ippusbxd
root   72414  0.0  0.0 565272  5712 ?Sl   22:10   0:00 
/usr/sbin/ippusbxd --bus-device 001:009 --from-port 6 --logging
stefano72551  0.0  0.0  19756   760 pts/0S+   22:13   0:00 grep 
--color=auto ippusbxd


** Attachment added: "ippusbxd  appears in red"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+attachment/5375328/+files/hplip%20cups.png

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1876884] Re: netplan using incorrect renderer

2020-05-21 Thread Steve Langasek
The initramfs-tools change is reasonable, but I disagree that the
dropbear behavior is "correct".  The use of 'critical' for network
interfaces should be limited to those that actually need to be up for
the root filesystem to be available.  Using dropbear for a one-time
unlock of the rootfs at boot is not that.  Especially given that the
dropbear bottom hook /specifically deconfigures/ the network interface,
it should not be inducing netplan to output yaml that sets 'critical'.

Either the configure_networking function should be extended to take an
option to skip the 'critical' setting, or dropbear should do some
cleanup in its bottom script.

** Changed in: dropbear (Ubuntu Focal)
   Status: Invalid => Triaged

** Changed in: dropbear (Ubuntu Groovy)
   Status: Invalid => Triaged

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

Title:
  netplan using incorrect renderer

Status in dropbear package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in netplan.io package in Ubuntu:
  Invalid
Status in dropbear source package in Focal:
  Triaged
Status in initramfs-tools source package in Focal:
  New
Status in netplan.io source package in Focal:
  Invalid
Status in dropbear source package in Groovy:
  Triaged
Status in initramfs-tools source package in Groovy:
  Fix Released
Status in netplan.io source package in Groovy:
  Invalid

Bug description:
  After upgrading ubuntu desktop from 19.10 to 20.04, it's impossible to enable 
screen sharing.
  It used to work fine on 19.10. 

  When clicking the enable/disable toggle, the following message is
  logged in journalctl:

  Failed to enable service vino-server:
  GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Sharing cannot be
  enabled on this network, status is '0'

  This is reproducible on both computers I've upgraded. They're both on
  the latest 20.04 package updates as of today.

  I've done some research to rule out common faults:

  $ cat /etc/netplan/01-network-manager-all.yaml 
  # Let NetworkManager manage all devices on this system
  network:
version: 2
renderer: NetworkManager

  (Yes, I've ofc ran netplan apply, but the file already had this
  content anyway.)

  $ cat /etc/NetworkManager/NetworkManager.conf 
  [main]
  plugins=ifupdown,keyfile

  [ifupdown]
  managed=false

  [device]
  wifi.scan-rand-mac-address=no

  
  Also, this seems unrelated to #1871787:
  $ dpkg -l |grep gnome-settings-daemon
  ii  gnome-settings-daemon  3.36.0-1ubuntu2
  ii  gnome-settings-daemon-common   3.36.0-1ubuntu2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-17 (108 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-28 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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


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

2020-05-21 Thread mm
My current workaround: downgrade isc-dhcp-server to 18.04 package
version.

-- 
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 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2020-05-21 Thread Steve Langasek
You might also want to try 'sudo vgck -t s5lp8-vg' first before
committing changes with --updatemetadata.

** Changed in: lvm2 (Ubuntu Focal)
Milestone: None => ubuntu-20.04.1

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

Title:
  LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting
  for device /dev/mapper/s5lp8--v g-home

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 source package in Focal:
  Confirmed

Bug description:
  After upgrading an LPAR configured with LVM from 18.04 to 20.04 /home is no 
longer mounted.
  During boot the console shows Timed out waiting for device 
/dev/mapper/s5lp8--vg-home

  Please see the attached dist-upgrade logs and console output for more
  detail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381/+subscriptions

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


[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2020-05-21 Thread Steve Langasek
John, are you able to confirm that a 'sudo vgck --updatemetadata
s5lp8-vg' fixes this for you?

Also, before running that command, can you post the output of 'sudo
vgdisplay' on this system?

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

Title:
  LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting
  for device /dev/mapper/s5lp8--v g-home

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 source package in Focal:
  Confirmed

Bug description:
  After upgrading an LPAR configured with LVM from 18.04 to 20.04 /home is no 
longer mounted.
  During boot the console shows Timed out waiting for device 
/dev/mapper/s5lp8--vg-home

  Please see the attached dist-upgrade logs and console output for more
  detail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381/+subscriptions

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


[Touch-packages] [Bug 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]

2020-05-21 Thread mm
My current workaround: downgrade isc-dhcp-server to 18.04 package
version.

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

Title:
  isc-dhcp-server crashing constantly [Ubuntu 20.04]

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  isc-dhcp-server crashing constantly (sometimes within seconds or minutes, 
sometimes within hours) with the following error messages:
  Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service.
  Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ??
  Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ??
  Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ??
  Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ??
  Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ??
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.

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

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


[Touch-packages] [Bug 1861250] Re: Apparmor error failed to start profiles

2020-05-21 Thread Sven
● apparmor.service - Load AppArmor profiles
 Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Thu 2020-05-21 20:56:02 CEST; 
3min 38s ago
   Docs: man:apparmor(7)
 https://gitlab.com/apparmor/apparmor/wikis/home/
Process: 7127 ExecStart=/lib/apparmor/apparmor.systemd reload (code=exited, 
status=1/FAILURE)
   Main PID: 7127 (code=exited, status=1/FAILURE)

No further hint, what's wrong...

** Changed in: apparmor (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  Apparmor error failed to start profiles

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  OS Ubuntu focal fossa 20.04
  On boot error message - Apparmor Failed to start profiles.

  Steps attempted to correct

  1.sudo as status

  lee@lee-desktop:~$ sudo aa-status
  apparmor module is loaded.
  53 profiles are loaded.
  51 profiles are in enforce mode.
 /sbin/dhclient
 /snap/core/8268/usr/lib/snapd/snap-confine
 /snap/core/8268/usr/lib/snapd/snap-confine//mount-namespace-capture-helper
 /usr/bin/evince
 /usr/bin/evince-previewer
 /usr/bin/evince-previewer//sanitized_helper
 /usr/bin/evince-thumbnailer
 /usr/bin/evince//sanitized_helper
 /usr/bin/man
 /usr/lib/NetworkManager/nm-dhcp-client.action
 /usr/lib/NetworkManager/nm-dhcp-helper
 /usr/lib/connman/scripts/dhclient-script
 /usr/lib/cups/backend/cups-pdf
 /usr/lib/lightdm/lightdm-guest-session
 /usr/lib/lightdm/lightdm-guest-session//chromium
 /usr/lib/snapd/snap-confine
 /usr/lib/snapd/snap-confine//mount-namespace-capture-helper
 /usr/lib/telepathy/mission-control-5
 /usr/lib/telepathy/telepathy-*
 /usr/lib/telepathy/telepathy-*//pxgsettings
 /usr/lib/telepathy/telepathy-*//sanitized_helper
 /usr/lib/telepathy/telepathy-ofono
 /usr/sbin/cups-browsed
 /usr/sbin/cupsd
 /usr/sbin/cupsd//third_party
 /usr/sbin/ippusbxd
 /usr/sbin/tcpdump
 /usr/share/hplip/plugin.py
 /usr/share/hplip/sendfax.py
 /usr/share/hplip/setup.py
 /usr/share/hplip/systray.py
 /usr/share/hplip/toolbox.py
 libreoffice-senddoc
 libreoffice-soffice//gpg
 libreoffice-xpdfimport
 lsb_release
 man_filter
 man_groff
 nvidia_modprobe
 nvidia_modprobe//kmod
 snap-update-ns.core
 snap-update-ns.gnome-calculator
 snap-update-ns.gnome-characters
 snap-update-ns.gnome-logs
 snap-update-ns.gnome-system-monitor
 snap.core.hook.configure
 snap.gnome-calculator.gnome-calculator
 snap.gnome-characters.gnome-characters
 snap.gnome-logs.gnome-logs
 snap.gnome-system-monitor.gnome-system-monitor
 system_tor
  2 profiles are in complain mode.
 libreoffice-oopslash
 libreoffice-soffice
  3 processes have profiles defined.
  3 processes are in enforce mode.
 /usr/lib/telepathy/mission-control-5 (3090) 
 /usr/sbin/cupsd (1646) 
 /usr/bin/tor (1861) system_tor
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.
  lee@lee-desktop:~$ 

  2.sudo /etc/init.d/apparmor restart

  lee@lee-desktop:~$ sudo /etc/init.d/apparmor restart
  Restarting apparmor (via systemctl): apparmor.serviceJob for apparmor.service 
failed because the control process exited with error code.
  See "systemctl status apparmor.service" and "journalctl -xe" for details.
   failed!
  lee@lee-desktop:~$ 

  3.sudo rm -rf /etc/apparmor.d/cache/*

  4. sudo /etc/init.d/apparmor restart

  lee@lee-desktop:~$ sudo /etc/init.d/apparmor restart
  Restarting apparmor (via systemctl): apparmor.serviceJob for apparmor.service 
failed because the control process exited with error code.
  See "systemctl status apparmor.service" and "journalctl -xe" for details.
   failed!
  lee@lee-desktop:~$ 

  Thanks,

  Lee

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apparmor 2.13.3-7ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 28 23:19:19 2020
  InstallationDate: Installed on 2013-08-08 (2365 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=d2e1abc4-e044-467e-8cc2-57cbe4ef3115 ro drm.debug=0xe plymouth:debug
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Touch-packages] [Bug 1832333] Re: There is no firejail-default profile in Ubuntu

2020-05-21 Thread Reiner Herrmann
The AppArmor local override file is generated since 0.9.58.2-1.

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

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

Title:
  There is no firejail-default profile in Ubuntu

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New
Status in firejail package in Ubuntu:
  Fix Released

Bug description:
  Firejail requires the firejail-default apparmor profile in
  /etc/apparmor.d to work together with apparmor but that doesn't exist
  in Ubuntu 19.04. After I had added firejail-default to /etc/apparmor.d
  and firejail-local to /etc/apparmor.d/local everything was OK.

  Could this be default in Ubuntu?

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

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


[Touch-packages] [Bug 1774843] Re: apport python exception for python versions which python-apt is not built on

2020-05-21 Thread Brian Murray
Hmm, that was a bad paste here is the regression test for 19.10:

bdmurray@clean-eoan-amd64:~$ apport-cli coreutils < /dev/null

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (1.6 KB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): Traceback (most recent call last):
  File "/usr/bin/apport-cli", line 387, in 
if not app.run_argv():
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 711, in run_argv
return self.run_report_bug()
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 550, in 
run_report_bug
response = self.ui_present_report_details(allowed_to_report)
  File "/usr/bin/apport-cli", line 213, in ui_present_report_details
response = dialog.run()
  File "/usr/bin/apport-cli", line 101, in run
multi_char)
  File "/usr/bin/apport-cli", line 49, in raw_input_char
saved_attributes = termios.tcgetattr(file)
termios.error: (25, 'Inappropriate ioctl for device')

And for Ubuntu 18.04 LTS:

bdmurray@clean-bionic-amd64:~$ apport-cli coreutils < /dev/null

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (1.6 KB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): Traceback (most recent call last):
  File "/usr/bin/apport-cli", line 387, in 
if not app.run_argv():
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 693, in run_argv
return self.run_report_bug()
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 532, in 
run_report_bug
response = self.ui_present_report_details(allowed_to_report)
  File "/usr/bin/apport-cli", line 213, in ui_present_report_details
response = dialog.run()
  File "/usr/bin/apport-cli", line 101, in run
multi_char)
  File "/usr/bin/apport-cli", line 49, in raw_input_char
saved_attributes = termios.tcgetattr(file)
termios.error: (25, 'Inappropriate ioctl for device')


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

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

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

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

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

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

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

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

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

  [Original Description]
  it seems apport installs an exception hook whenever running python3.
  This hook is apparently installed for python3.7 too.
  

[Touch-packages] [Bug 1774843] Re: apport python exception for python versions which python-apt is not built on

2020-05-21 Thread Brian Murray
Verified on Ubuntu 19.10:

bdmurray@clean-bionic-amd64:~$ apt-cache policy python3-apport
python3-apport:
  Installed: 2.20.9-0ubuntu7.15
  Candidate: 2.20.9-0ubuntu7.15
  Version table:
 *** 2.20.9-0ubuntu7.15 500
500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic-proposed/main i386 Packages
100 /var/lib/dpkg/status
 2.20.9-0ubuntu7.14 500
500 http://192.168.10.7/ubuntu bionic-updates/main amd64 Packages
500 http://192.168.10.7/ubuntu bionic-updates/main i386 Packages
500 http://192.168.10.7/ubuntu bionic-security/main amd64 Packages
500 http://192.168.10.7/ubuntu bionic-security/main i386 Packages
 2.20.9-0ubuntu7 500
500 http://192.168.10.7/ubuntu bionic/main amd64 Packages
500 http://192.168.10.7/ubuntu bionic/main i386 Packages
bdmurray@clean-bionic-amd64:~$ python3.7 -c 'print hello'
  File "", line 1
print hello
  ^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)?

and the regression test passes:

bdmurray@clean-bionic-amd64:~$ apt-cache policy python3-apport
python3-apport:
  Installed: 2.20.9-0ubuntu7.15
  Candidate: 2.20.9-0ubuntu7.15
  Version table:
 *** 2.20.9-0ubuntu7.15 500
500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic-proposed/main i386 Packages
100 /var/lib/dpkg/status
 2.20.9-0ubuntu7.14 500
500 http://192.168.10.7/ubuntu bionic-updates/main amd64 Packages
500 http://192.168.10.7/ubuntu bionic-updates/main i386 Packages
500 http://192.168.10.7/ubuntu bionic-security/main amd64 Packages
500 http://192.168.10.7/ubuntu bionic-security/main i386 Packages
 2.20.9-0ubuntu7 500
500 http://192.168.10.7/ubuntu bionic/main amd64 Packages
500 http://192.168.10.7/ubuntu bionic/main i386 Packages
bdmurray@clean-bionic-amd64:~$ python3.7 -c 'print hello'
  File "", line 1
print hello
  ^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)?

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

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

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

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

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

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

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

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

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

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

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

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

  Demo with a trivial error:
  $ python3 -c 'print hello'
    File "", line 1
  print 

[Touch-packages] [Bug 1774843] Re: apport python exception for python versions which python-apt is not built on

2020-05-21 Thread Brian Murray
Verified on Ubuntu 18.04 LTS:

bdmurray@clean-bionic-amd64:~$ apt-cache policy python3-apport
python3-apport:
  Installed: 2.20.9-0ubuntu7.15
  Candidate: 2.20.9-0ubuntu7.15
  Version table:
 *** 2.20.9-0ubuntu7.15 500
500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic-proposed/main i386 Packages
100 /var/lib/dpkg/status
 2.20.9-0ubuntu7.14 500
500 http://192.168.10.7/ubuntu bionic-updates/main amd64 Packages
500 http://192.168.10.7/ubuntu bionic-updates/main i386 Packages
500 http://192.168.10.7/ubuntu bionic-security/main amd64 Packages
500 http://192.168.10.7/ubuntu bionic-security/main i386 Packages
 2.20.9-0ubuntu7 500
500 http://192.168.10.7/ubuntu bionic/main amd64 Packages
500 http://192.168.10.7/ubuntu bionic/main i386 Packages
bdmurray@clean-bionic-amd64:~$ python3.7 -c 'print hello'
  File "", line 1
print hello
  ^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1879751] Re: ALSA sees my intel soundcards but pulseaudio does not. Error is : "Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa-card.so: /usr/lib/pulse-13.99.1/m

2020-05-21 Thread Phil Macias
I purged and installed jackd1
I never had but then installed jackd
I never had but then installed timidity

Rebooted and still only the dummy device and

#journalctl |grep pulseaudio

 Failed to open module "module-alsa-card".
May 21 13:47:15 CF-C2CQAZXCM pulseaudio[3849]: Failed to open module 
/usr/lib/pulse-13.99.1/modules/module-alsa-card.so: 
/usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined symbol: 
snd_use_case_parse_ctl_elem_id, version ALSA_0.9

alsamixer sees the cards

__END__

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

Title:
  ALSA sees my intel soundcards but pulseaudio does not.  Error is :
  "Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa-
  card.so: /usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined
  symbol: snd_use_case_parse_ctl_elem_id, version ALSA_0.9"

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  ALSA sees my intel soundcards but pulseaudio does not.

  'pavucontrol' sees only a "Dummy" device.

  #journalctl|grep pulse' gives "pulseaudio[18489]: Failed to open
  module /usr/lib/pulse-13.99.1/modules/module-alsa-card.so:
  /usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined symbol:
  snd_use_case_parse_ctl_elem_id, version ALSA_0.9"

  Making pulseaudio from source fixes the problem/

  (Linux CF-C2CQAZXCM 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29
  14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux 20.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed May 20 12:48:07 2020
  InstallationDate: Installed on 2015-04-29 (1848 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-05-05 (15 days ago)
  dmi.bios.date: 09/12/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.00L21
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: CFC2-2
  dmi.board.vendor: Panasonic Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Panasonic Corporation
  dmi.chassis.version: 001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.00L21:bd09/12/2018:svnPanasonicCorporation:pnCF-C2CQAZXCM:pvr002:rvnPanasonicCorporation:rnCFC2-2:rvr1:cvnPanasonicCorporation:ct10:cvr001:
  dmi.product.family: CFC2-2
  dmi.product.name: CF-C2CQAZXCM
  dmi.product.sku: CF-C2CQAZXCM
  dmi.product.version: 002
  dmi.sys.vendor: Panasonic Corporation
  mtime.conffile..etc.init.d.apport: 2020-02-26T22:18:45

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

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


[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

2020-05-21 Thread Rob Robertson
*** This bug is a duplicate of bug 1576559 ***
https://bugs.launchpad.net/bugs/1576559

This is not a duplicate of bug 1576559.   It is a duplicate of #1878194

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1879206] Re: cups hplip not install printer

2020-05-21 Thread Till Kamppeter
On the machine where you still have the problem could you remove your
print queue and then unplug and re-plug the printer? Does a new print
queue get automatically created?

What is the output of the following commands and post the output here:

lpstat -v
driverless
ps auxwww | grep ippusbxd

If a queue actually got auto-created for your printer, couls you attach
the queue's PPD file from /etc/cups/ppd/ here?

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

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

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1861941] Missing required logs.

2020-05-21 Thread Ubuntu Kernel Bot
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1861941

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in bcache-tools source package in Focal:
  New
Status in linux source package in Focal:
  Invalid
Status in linux-signed source package in Focal:
  New
Status in systemd source package in Focal:
  Invalid
Status in bcache-tools source package in Groovy:
  Fix Released
Status in linux source package in Groovy:
  Incomplete
Status in linux-signed source package in Groovy:
  New
Status in systemd source package in Groovy:
  Invalid

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2020-05-21 Thread Brian Murray
** Package changed: ubuntu-release-upgrader (Ubuntu) => lvm2 (Ubuntu)

** Tags removed: rls-ff-incoming

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

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

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

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

Title:
  LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting
  for device /dev/mapper/s5lp8--v g-home

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 source package in Focal:
  Confirmed

Bug description:
  After upgrading an LPAR configured with LVM from 18.04 to 20.04 /home is no 
longer mounted.
  During boot the console shows Timed out waiting for device 
/dev/mapper/s5lp8--vg-home

  Please see the attached dist-upgrade logs and console output for more
  detail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381/+subscriptions

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


Re: [Touch-packages] [Bug 1813679] Re: vim-gtk can no longer save to non-group-writable files in GVFS SFTP mounts in 18.04

2020-05-21 Thread Adam Novak
I haven't upgraded to Focal yet, but it's still an open issue upstream:
https://github.com/vim/vim/issues/5237

May 20, 2020 5:49 AM, "Sebastien Bacher"  wrote:

> Is that still an issue in focal?
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1813679
> 
> Title:
> vim-gtk can no longer save to non-group-writable files in GVFS SFTP
> mounts in 18.04
> 
> Status in gvfs package in Ubuntu:
> Invalid
> Status in nautilus package in Ubuntu:
> Invalid
> Status in vim package in Ubuntu:
> New
> 
> Bug description:
> In Ubuntu 16.04, with gvim 7.4.1689, I can open files over GVFS SSH
> mounts (by going to `ssh://wherever` in the address bar in the file
> browser and double-clicking on the file), edit them, and save them.
> 
> In Ubuntu 18.04, when I install `vim-gtk` and try to do the same
> thing, I can open the files just fine, but when I try to save them I
> get a message that Vim "Can't open file for writing".
> 
> If I check out the Vim source tree and build and install vim
> v7.4.1689, which is what Xenial is shipping now, and use *that* gvim
> on Ubuntu 18.04, I can save over SSH mounts. I can also save fine from
> gedit.
> 
> Something is wrong with the gvim shipping with 18.04.
> 
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: vim-gtk (not installed)
> ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
> Uname: Linux 4.15.0-44-generic x86_64
> NonfreeKernelModules: nvidia_modeset nvidia
> ApportVersion: 2.20.9-0ubuntu7.5
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> Date: Mon Jan 28 15:55:56 2019
> ProcEnviron:
> TERM=xterm-256color
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: vim
> UpgradeStatus: No upgrade log present (probably fresh install)
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+subscriptions

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

Title:
  vim-gtk can no longer save to non-group-writable files in GVFS SFTP
  mounts in 18.04

Status in gvfs package in Ubuntu:
  Invalid
Status in nautilus package in Ubuntu:
  Invalid
Status in vim package in Ubuntu:
  New

Bug description:
  In Ubuntu 16.04, with gvim 7.4.1689, I can open files over GVFS SSH
  mounts (by going to `ssh://wherever` in the address bar in the file
  browser and double-clicking on the file), edit them, and save them.

  In Ubuntu 18.04, when I install `vim-gtk` and try to do the same
  thing, I can open the files just fine, but when I try to save them I
  get a message that Vim "Can't open file for writing".

  If I check out the Vim source tree and build and install vim
  v7.4.1689, which is what Xenial is shipping now, and use *that* gvim
  on Ubuntu 18.04, I can save over SSH mounts. I can also save fine from
  gedit.

  Something is wrong with the gvim shipping with 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vim-gtk (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 28 15:55:56 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

2020-05-21 Thread Ryan Harper
@Balint

I do not thing the fix you're released is correct, can you upload a new
version without the scripts?

Also, we should fix make-bcache -B to ensure that cset.uuid is not
initialized; that may be why the kernel thinks it should emit the
CACHED_UUID if the suerpblock of the device has a cset.uuid value
(versus None).

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  New
Status in linux-signed package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in bcache-tools source package in Focal:
  New
Status in linux source package in Focal:
  Invalid
Status in linux-signed source package in Focal:
  New
Status in systemd source package in Focal:
  Invalid
Status in bcache-tools source package in Groovy:
  Fix Released
Status in linux source package in Groovy:
  New
Status in linux-signed source package in Groovy:
  New
Status in systemd source package in Groovy:
  Invalid

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1659719] Re: ssh can't call a binary from a snap without the full path

2020-05-21 Thread Brian Murray
** Changed in: pam (Ubuntu Groovy)
   Importance: Undecided => Medium

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

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

Status in Snappy:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Groovy:
  Fix Released
Status in openssh source package in Groovy:
  Confirmed
Status in pam source package in Groovy:
  Confirmed
Status in snapd source package in Groovy:
  Confirmed

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

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

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

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

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


[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

2020-05-21 Thread Ryan Harper
Digging deeper and walking through this in a focal vm, I'm seeing some
strange things.

Starting with a clean disk, and just creating the backing device like
so:

make-bcache -B /dev/vdb

We see /dev/bcache0 get created with vdb as the backing device.  Now,
after this, I see:

/dev/bcache/by-uuid/ -> ../../bcache0

This is unexpected.  It should *only* appear once the bcache0 device is
actively cached;  that is the bcache driver should not emit CACHED_UUID,
until the UUID is actually cached, which only happens once we've
registered a cache device with the bcache0 device.  We need to look at
the kernel source to see if the SAUCE patch isn't quite right, or some
other part of bcache code has changed.

Next issue, blkid now detects the bcache dev.uuid, and this shows up
like so:

# udevadm test-builtin blkid /sys/class/block/vdb
...
vdb: Probe /dev/vdb with raid and offset=0
ID_FS_UUID=d7d7e025-b8d2-43cb-a5df-c240ba1418dc
ID_FS_UUID_ENC=d7d7e025-b8d2-43cb-a5df-c240ba1418dc
ID_FS_TYPE=bcache
ID_FS_USAGE=other

Note, it shows up as an FS_UUID, but it is *NOT* an fs_uuid; there is no
filesystem on this device at all at this time;  it does have a bcache
superblock, note the FS_UUID matches the dev.uuid of the backing device.

# bcache-super-show /dev/vdb
sb.magicok
sb.first_sector 8 [match]
sb.csum 29D6774A332A280B [match]
sb.version  1 [backing device]

dev.label   (empty)
dev.uuidd7d7e025-b8d2-43cb-a5df-c240ba1418dc
dev.sectors_per_block   1
dev.sectors_per_bucket  1024
dev.data.first_sector   16
dev.data.cache_mode 0 [writethrough]
dev.data.cache_state0 [detached]

cset.uuid   37b37bc1-e185-4825-8900-579df102b7d6

It's also curious that cset.uuid has a UUID, as there are no csets
created; IMO this is also a bug and it should be 0, null, or empty.

Now, here's where the udev fights over the links.  The backing device,
vdb, triggers this rule in 60-persistent-storage.rules:

# by-label/by-uuid links (filesystem metadata)
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", 
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"

This creates confusion due to the CACHED_UUID also being emitted from
the kernel, like so:

root@ubuntu:/run/udev/links# ls -al 
/dev/disk/by-uuid/d7d7e025-b8d2-43cb-a5df-c240ba1418dc 
lrwxrwxrwx 1 root root 9 May 21 16:39 
/dev/disk/by-uuid/d7d7e025-b8d2-43cb-a5df-c240ba1418dc -> ../../vdb
root@ubuntu:/run/udev/links# ls -al 
/dev/bcache/by-uuid/d7d7e025-b8d2-43cb-a5df-c240ba1418dc
lrwxrwxrwx 1 root root 13 May 21 16:39 
/dev/bcache/by-uuid/d7d7e025-b8d2-43cb-a5df-c240ba1418dc -> ../../bcache0

There we have two devices both claiming the backing devices dev.uuid
value, with two different block names.

So, in summary, there are two problems to fix:

1) blkid on bcache devices should not report FS_UUID values when
FS_TYPE=bcache; there is no filesystem on it; this will need to be
discussed upstream

2) our kernel (need to check mainline vs. ours) emits CACHED_UUID when
the bcache0 is created, but no cache is attached:  see this udev event:

KERNEL[2217.605118] change   /devices/virtual/block/bcache0 (block)
ACTION=change
DEVPATH=/devices/virtual/block/bcache0
SUBSYSTEM=block
DRIVER=bcache
CACHED_UUID=d7d7e025-b8d2-43cb-a5df-c240ba1418dc
CACHED_LABEL=
DEVNAME=/dev/bcache0
DEVTYPE=disk
SEQNUM=5890
MAJOR=251
MINOR=0




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

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

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  New
Status in linux-signed package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in bcache-tools source package in Focal:
  New
Status in linux source package in Focal:
  Invalid
Status in linux-signed source package in Focal:
  New
Status in systemd source package in Focal:
  Invalid
Status in bcache-tools source package in Groovy:
  Fix Released
Status in linux source package in Groovy:
  New
Status in linux-signed source package in Groovy:
  New
Status in systemd source package in Groovy:
  Invalid

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy 

[Touch-packages] [Bug 1874381] [NEW] LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

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

After upgrading an LPAR configured with LVM from 18.04 to 20.04 /home is no 
longer mounted.
During boot the console shows Timed out waiting for device 
/dev/mapper/s5lp8--vg-home

Please see the attached dist-upgrade logs and console output for more
detail.

** Affects: ubuntu-z-systems
 Importance: High
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: Confirmed

** Affects: lvm2 (Ubuntu)
 Importance: High
 Assignee: Canonical Foundations Team (canonical-foundations)
 Status: Confirmed


** Tags: rls-ff-incoming s390x
-- 
LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for 
device /dev/mapper/s5lp8--v g-home
https://bugs.launchpad.net/bugs/1874381
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to lvm2 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 1878517] Re: please apply bash 5.0 patch 17

2020-05-21 Thread Brian Murray
** Changed in: bash (Ubuntu)
   Status: New => Triaged

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

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

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

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

** Tags removed: rls-ff-incoming

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

Title:
  please apply bash 5.0 patch 17

Status in bash package in Ubuntu:
  Triaged
Status in bash source package in Focal:
  Triaged

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

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

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

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

  $ bats ya.bats
  ```

  Normally the output should contain the line

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

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

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

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

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

  Please update bash to patchlevel 17.

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

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


[Touch-packages] [Bug 1874461] Re: gconf2.0 crashes repeatedly on upgrade to focal fossa

2020-05-21 Thread Brian Murray
** Tags removed: rls-ff-incoming

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

Title:
  gconf2.0 crashes repeatedly on upgrade to focal fossa

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  Running update-manager -p today just before the release of focal
  fossa, the install halted during package configuration with a gconf2.0
  crash. I had to dismiss about 30 dialogs before the install completed,
  each exactly the same.

  I run stock ubuntu, except that I use the standard Gnome desktop
  instead of the Ubuntu unity Gnome variant. The machine in question has
  been upgraded from 18.04 to 19.10 & now to 20.04

  Since this package is now marked as only required for legacy
  applications, perhaps it needs removing before the focal upgrade?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: GNOME
  Date: Thu Apr 23 15:43:05 2020
  InstallationDate: Installed on 2018-07-19 (643 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago)
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.apport.crashdb.conf: 2019-04-29T12:11:49.292007

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

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


[Touch-packages] [Bug 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423

2020-05-21 Thread Ludovic Rousseau
Please generate a pcscd log.
See https://ccid.apdu.fr/#support

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

Title:
  pcscd doesn't support ActivKEy SIM B/N: 0945423

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not 
recognized by pcscd. Since it is not recognized, it is also not recognized by 
VMware Workstation VM which runs Windows. Banking software running in windows 
doesn't see the key and can't authenticate me.
  Few years ago, this was working on Ubuntu 18.04, so it must be something in 
version between.
  After restart of the pcscd service, USB key shows green light, but few 
seconds after it goes to red.

  sudo service pcscd status
  ● pcscd.service - PC/SC Smart Card Daemon
   Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor 
preset: enabled)
   Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago
  TriggeredBy: ● pcscd.socket
 Docs: man:pcscd(8)
 Main PID: 230408 (pcscd)
Tasks: 5 (limit: 57614)
   Memory: 1.9M
   CGroup: /system.slice/pcscd.service
   └─230408 /usr/sbin/pcscd --foreground --auto-exit

  svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon.
  svi 21 15:48:01 rodigerlaptop1 pcscd[230408]:  
ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 
ifdhandler.c:1221:IFDHPowerICC() PowerUp failed
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 
eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 
0x80100016

  Result of pcsc_scan
  sudo pcsc_scan 
  Using reader plug'n play mechanism
  Scanning present readers...
  Waiting for the first reader...found one
  Scanning present readers...
  0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
   
  Thu May 21 15:44:16 2020
   Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
Event number: 0
Card state: Card inserted, Unresponsive card, 

  So USB key is visible

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pcscd 1.8.26-3
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 15:38:57 2020
  SourcePackage: pcsc-lite
  UpgradeStatus: Upgraded to focal on 2020-05-11 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1879960/+subscriptions

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


[Touch-packages] [Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

2020-05-21 Thread Yuri
@Pierre Equoy:

It looks like you are having 2 issues. The Sound selection UI not
appearing and no sound coming out after plug-in. Can you have a look at
this question https://answers.launchpad.net/ubuntu/+question/690501. Is
this the problem you are having with sound. Should I link my question to
your bug report?

It seems like its an issue with Dell's hardware and whatever changes
were made between 19.10 -> 20.04

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

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:

  
  Summary
  ===

  Internal speakers work as expected, but when plugging headphones
  through the 3.5mm jack, the "Select Audio Device" panel doesn't show
  up (it normally shows up to allow user to select what kind of device
  has been plugged in, be it headphones, microphone or headset). In the
  Sound Settings, the Output Device automatically switches to
  "Headphones - sof-hda-dsp", but no sound can be heard even though the
  vumeter in the Sound Settings moves!

  Steps to reproduce
  ==

  1. Install focal beta
  2. Make sure the sound works as expected using the internal speakers and an 
audio file or Youtube
  3. Plug headphones in jack 3.5mm interface

  Expected Results
  

  - In Sound Settings, the headphones are automatically selected as output 
device
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound
  - Sound can be heard through the headphones

  
  Actual results
  ==

  - In Sound Settings, the headphones are automatically selected as output 
device (OK)
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound (OK)
  - No sound can be heard (Not OK)

  Attached are output of `pactl info` and `pactl list` before and after
  plugging headphones, while playing a tune on Bandcamp in Firefox.

  
  Additional Info
  ===

  Ubuntu: 20.04 beta image
  Certified device: 
  system-manufacturer: Dell Inc.
  system-product-name: Vostro 5590
  bios-version: 1.1.0
  CPU: Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9b41] (rev 02)
  01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1d13] (rev a1)
  kernel-version: 5.4.0-21-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1768 F pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1768 F...m pulseaudio
   /dev/snd/pcmC0D6c:   pieq   1768 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 16:33:27 2020
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/18/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5590
  dmi.product.sku: 095A
  dmi.sys.vendor: Dell Inc.

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

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


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

2020-05-21 Thread Rajasekharan N
PPA statistics

Activity

3 updates added during the past month.

Currently 0 packages building and 1 package waiting to build.

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

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

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

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

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

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

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

  

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

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

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

  Any help greatly appreciated.

  Regards,
  Roman

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

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


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

2020-05-21 Thread Rajasekharan N
I'm able to get only this version: pulseaudio 1:13.99.1-1ubuntu3.2.

The following are seen as pending:

i386 build of pulseaudio 1:13.99.1-1ubuntu3.2lp1869819 in ubuntu focal RELEASE
Pending (2510)
amd64 build of pulseaudio 1:13.99.1-1ubuntu3.2lp1869819 in ubuntu focal RELEASE
Pending (2510)

Pardon me if I am going wrong somewhere.

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

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

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

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

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

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

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

  

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

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

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

  Any help greatly appreciated.

  Regards,
  Roman

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

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


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

2020-05-21 Thread Kai-Heng Feng
Sorry, I re-uploaded a new one with version is greater than the current
one. Please test that instead.

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

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

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

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

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

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

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

  

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

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

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

  Any help greatly appreciated.

  Regards,
  Roman

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

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


[Touch-packages] [Bug 1874461] Re: gconf2.0 crashes repeatedly on upgrade to focal fossa

2020-05-21 Thread Steve Langasek
** Package changed: ubuntu-release-upgrader (Ubuntu) => gconf (Ubuntu)

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

Title:
  gconf2.0 crashes repeatedly on upgrade to focal fossa

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  Running update-manager -p today just before the release of focal
  fossa, the install halted during package configuration with a gconf2.0
  crash. I had to dismiss about 30 dialogs before the install completed,
  each exactly the same.

  I run stock ubuntu, except that I use the standard Gnome desktop
  instead of the Ubuntu unity Gnome variant. The machine in question has
  been upgraded from 18.04 to 19.10 & now to 20.04

  Since this package is now marked as only required for legacy
  applications, perhaps it needs removing before the focal upgrade?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: GNOME
  Date: Thu Apr 23 15:43:05 2020
  InstallationDate: Installed on 2018-07-19 (643 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago)
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.apport.crashdb.conf: 2019-04-29T12:11:49.292007

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

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


[Touch-packages] [Bug 1874461] [NEW] gconf2.0 crashes repeatedly on upgrade to focal fossa

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

Running update-manager -p today just before the release of focal fossa,
the install halted during package configuration with a gconf2.0 crash. I
had to dismiss about 30 dialogs before the install completed, each
exactly the same.

I run stock ubuntu, except that I use the standard Gnome desktop instead
of the Ubuntu unity Gnome variant. The machine in question has been
upgraded from 18.04 to 19.10 & now to 20.04

Since this package is now marked as only required for legacy
applications, perhaps it needs removing before the focal upgrade?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.18
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: GNOME
Date: Thu Apr 23 15:43:05 2020
InstallationDate: Installed on 2018-07-19 (643 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago)
VarLogDistupgradeTermlog:

mtime.conffile..etc.apport.crashdb.conf: 2019-04-29T12:11:49.292007

** Affects: gconf (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug dist-upgrade focal rls-ff-incoming
-- 
gconf2.0 crashes repeatedly on upgrade to focal fossa
https://bugs.launchpad.net/bugs/1874461
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gconf 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 1879980] [NEW] Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

2020-05-21 Thread Guilherme G. Piccoli
Public bug reported:

Description will be saved for further SRU template, the details of the
issue will be exposed in comments

** Affects: cryptsetup (Ubuntu)
 Importance: Medium
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: Confirmed

** Affects: initramfs-tools (Ubuntu)
 Importance: Medium
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: Confirmed

** Affects: mdadm (Ubuntu)
 Importance: Medium
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: Confirmed


** Tags: sts

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

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

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

** Changed in: mdadm (Ubuntu)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Medium

** Changed in: initramfs-tools (Ubuntu)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

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

Title:
  Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

Status in cryptsetup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in mdadm package in Ubuntu:
  Confirmed

Bug description:
  Description will be saved for further SRU template, the details of the
  issue will be exposed in comments

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

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


[Touch-packages] [Bug 1659719] Re: ssh can't call a binary from a snap without the full path

2020-05-21 Thread Brian Murray
** Also affects: pam (Ubuntu Groovy)
   Importance: Undecided
   Status: Confirmed

** Also affects: openssh (Ubuntu Groovy)
   Importance: Undecided
   Status: Confirmed

** Also affects: livecd-rootfs (Ubuntu Groovy)
   Importance: Medium
 Assignee: Oliver Grawert (ogra)
   Status: Fix Released

** Also affects: snapd (Ubuntu Groovy)
   Importance: Undecided
   Status: Confirmed

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

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

Status in Snappy:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Groovy:
  Fix Released
Status in openssh source package in Groovy:
  Confirmed
Status in pam source package in Groovy:
  Confirmed
Status in snapd source package in Groovy:
  Confirmed

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

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

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

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

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


[Touch-packages] [Bug 1879977] [NEW] Xorg crash

2020-05-21 Thread Robert Sandell
Public bug reported:

Fresh Ubuntu 18.04.4 LTS bionic installation.
Nouveau driver.
One DVI cable attached directly to the graphics card, and one DVI + one VGA 
attached to the motherboard.
When I attempted to open "Display" settings the x-org session crashes and 
reverts to the login screen.
Other programs like Firefox and Terminal seem to run fine.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-53-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu May 21 17:14:11 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] 
[19da:2438]
InstallationDate: Installed on 2020-05-21 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: Micro-Star International Co., Ltd. MS-7A34
ProcEnviron:
 LANGUAGE=en_ZA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic 
root=UUID=ddd8f597-f590-4fc5-ac56-8ba3805b40e8 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/06/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.90
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B350 PC MATE (MS-7A34)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.90:bd12/06/2017:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A34
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic crash ubuntu

** Attachment added: "crash.zip"
   https://bugs.launchpad.net/bugs/1879977/+attachment/5375228/+files/crash.zip

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  Fresh Ubuntu 18.04.4 LTS bionic installation.
  Nouveau driver.
  One DVI cable attached directly to the graphics card, and one DVI + one VGA 
attached to the motherboard.
  When I attempted to open "Display" settings the x-org session crashes and 
reverts to the login screen.
  Other programs like Firefox and Terminal seem to run fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-53-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 17:14:11 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] 
[19da:2438]
  InstallationDate: Installed on 2020-05-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Micro-Star International Co., Ltd. MS-7A34
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic 
root=UUID=ddd8f597-f590-4fc5-ac56-8ba3805b40e8 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  

[Touch-packages] [Bug 1659719] Re: ssh can't call a binary from a snap without the full path

2020-05-21 Thread Brian Murray
** Changed in: livecd-rootfs (Ubuntu)
   Status: Fix Committed => Fix Released

** Tags removed: rls-gg-incoming

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 507728] Re: man page missing for slapo-nssov

2020-05-21 Thread Andreas Hasenack
This was fixed in 2.4.47+dfsg-2ubuntu1) for disco.

** Changed in: openldap (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  man page missing for slapo-nssov

Status in openldap package in Ubuntu:
  Fix Released

Bug description:
  source package: openldap (2.4.18-0ubuntu1)

  >lsb_release -rd
  Description:  Ubuntu 9.10
  Release:  9.10

   >apt-cache policy slapd
  slapd:
Installed: 2.4.18-0ubuntu1
Candidate: 2.4.18-0ubuntu1
Version table:
   *** 2.4.18-0ubuntu1 0
  500 http://us.archive.ubuntu.com karmic/main Packages
  100 /var/lib/dpkg/status

  the man page for the nss overlay (e.g. slapo-nssov) is not present.

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

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


Re: [Touch-packages] [Bug 1879488] Re: raw NEF thumbnails not processed

2020-05-21 Thread Christians
Having small thumbnails is better than having no thumbnails. To attract
a wider audience Ubuntu must have a better out-of-the box experience.

On 21/05/2020 08:37, Sebastien Bacher wrote:
> Thanks for reporting upstream, indeed the situation is suboptimal if
> adding the mimetype makes the image viewer open those files in low
> resolution...
>
> ** Changed in: gdk-pixbuf (Ubuntu)
>Status: Confirmed => Triaged
>

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

Title:
  raw NEF thumbnails not processed

Status in gdk-pixbuf package in Ubuntu:
  Triaged

Bug description:
  Raw NEF thumbnails are not displayed in Nautilus.

  FIX

  Add missing mime types to  /usr/share/thumbnailers/gdk-pixbuf-
  thumbnailer.thumbnailer

  This is described here https://askubuntu.com/questions/283072
  /nautilus-isnt-displaying-thumbnails-for-my-nef-files-photo-raw

  RAW mime types to add: image/x-3fr;image/x-adobe-
  dng;image/x-arw;image/x-bay;image/x-canon-cr2;image/x-canon-
  
crw;image/x-cap;image/x-cr2;image/x-crw;image/x-dcr;image/x-dcraw;image/x-dcs;image/x-dng;image/x-drf;image/x-eip;image/x-erf;image/x-fff;image/x
  -fuji-raf;image/x-iiq;image/x-k25;image/x-kdc;image/x-mef;image/x
  -minolta-mrw;image/x-mos;image/x-mrw;image/x-nef;image/x-nikon-
  nef;image/x-nrw;image/x-olympus-orf;image/x-orf;image/x-panasonic-
  raw;image/x-panasonic-raw2;image/x-pef;image/x-pentax-
  
pef;image/x-ptx;image/x-pxn;image/x-r3d;image/x-raf;image/x-raw;image/x-rw2;image/x-rwl;image/x-rwz;image/x
  -samsung-srw;image/x-sigma-x3f;image/x-sony-arw;image/x-sony-
  sr2;image/x-sony-srf;image/x-sr2;image/x-srf;image/x-x3f;

  Please consider changing the thumbnailer conifg so it will work out of
  the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-bin 2.40.0+dfsg-3 [modified: 
usr/share/thumbnailers/gdk-pixbuf-thumbnailer.thumbnailer]
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 19 12:48:25 2020
  InstallationDate: Installed on 2020-05-11 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1879488/+subscriptions

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


[Touch-packages] [Bug 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory

2020-05-21 Thread Brian Murray
** Tags removed: champagne

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

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

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

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

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

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

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

  Thanks

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

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

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


[Touch-packages] [Bug 1876035] Re: Consider making '-o Acquire::Retries=3' the default for 'apt-get update/install/dist-upgrade'

2020-05-21 Thread Brian Murray
** Tags removed: champagne

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

Title:
  Consider making '-o Acquire::Retries=3' the default for 'apt-get
  update/install/dist-upgrade'

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Groovy:
  Confirmed

Bug description:
  Hi,

  We operate archive.ubuntu.com as well as mirrors of it in various
  places. We're getting reports of various CI/CD jobs failing. Sometimes
  due to routing issues, issues with overloaded servers/VMs hosting
  archive, etc.

  Any chance we can make '-o Acquire::Retries=3' the default for 'apt-
  get update/install/dist-upgrade'? Preferably with a randomised skew
  between retries.

  Also, any chance of having apt-get retry with different IPs/hosts
  returned from the DNS lookup? (e.g. for archive.ubuntu.com -
  91.189.88.142, 91.189.88.152, ...).

  Thanks.

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

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


[Touch-packages] [Bug 1874501] Re: vgscan --mknodes creates block device multipath nodes in /dev/mapper

2020-05-21 Thread Brian Murray
** Also affects: lvm2 (Ubuntu Groovy)
   Importance: Undecided
   Status: Fix Committed

** Tags removed: rls-gg-incoming

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

Title:
  vgscan --mknodes creates block device multipath nodes in /dev/mapper

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in lvm2 package in Ubuntu:
  Fix Committed
Status in lvm2 source package in Groovy:
  Fix Committed

Bug description:
  Description:Ubuntu 20.04 LTS
  Release:20.04

  # apt-cache policy multipath-tools
  multipath-tools:
Installed: 0.8.3-1ubuntu2
Candidate: 0.8.3-1ubuntu2
Version table:
   *** 0.8.3-1ubuntu2 500
  500 http://ports.ubuntu.com/ubuntu-ports focal/main s390x Packages
  100 /var/lib/dpkg/status

  
  /dev/mapper/mpatha is symlink which points to ../../dm-X device

  /dev/mapper/mpath is block device

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: multipath-tools 0.8.3-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: s390x
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  Date: Thu Apr 23 17:32:12 2020
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release s390x 
(20200423.1)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: multipath-tools
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.multipath.conf:
   defaults {
   user_friendly_names yes
   skip_kpartx no
   verbosity 4
   }
  mtime.conffile..etc.multipath.conf: 2020-04-23T15:47:28.659850

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874501/+subscriptions

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


[Touch-packages] [Bug 1879525] Re: Add TLS support

2020-05-21 Thread Brian Murray
** Tags removed: rls-gg-incoming

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

Title:
  Add TLS support

Status in busybox package in Ubuntu:
  In Progress
Status in busybox source package in Focal:
  New

Bug description:
  [Impact]

   * busybox in the initramfs provides wget applet that is used by casper for 
netboot support
   * It does not support https at the moment, but it is desirable that it does
   * There is built-in TLS code, or "fork & execute openssl"
   * Enable the later one, and optionally include /usr/bin/openssl & certs, 
when building casper-like initrds which should support netboot.

  [Test Case]

   * Boot casper created initrd, with break=bottom
   * Configure dhcp based networking
   * Attempt to wget https://start.ubuntu.com/connectivity-check
   * It should succeed

  [Regression Potential]

   * The openssl codepath is optional in busybox wget, and we only include 
openssl & certs for casper.
   * The casper based initrd will grow in size, due to inclusion of openssl & 
certs

  [Other Info]
   
   * Parity with d-i, which includes https support already

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

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


[Touch-packages] [Bug 1774843] Autopkgtest regression report (apport/2.20.9-0ubuntu7.15)

2020-05-21 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted apport (2.20.9-0ubuntu7.15) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

apport/2.20.9-0ubuntu7.15 (amd64)


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

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

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

Thank you!

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  

[Touch-packages] [Bug 1875927] Re: add support for phys_port_name attribute in Xenial/16.04LTS

2020-05-21 Thread Eric Desrochers
** Description changed:

  [Impact]
  In Xenial/16.04LTS, one can't generate network interface name from 
"phys_port_name" attribute.
  
  "phys_port_name" indicates the interface physical port name within the
  NIC.
  
  [Test Case]
  
  Check that udev (systemd-udevd) provides the phys_port_name property
  Tests should be done on kernel versions: v4.15 (HWE)
  
  # cat /sys/class/net//phys_port_name
  yyy
  
  Look if interface name contains the 'phys_port_name':
  
  $ ip link show
  
  3: ens3nyyy:  ...
  
  
  [Regression Potential]
  
  * This piece of code is already in place in Bionic (systemd) and late.
  AFAICT, nothing has been reported since then with regards to this feature.
  
  * phys_port_name kernel support has been introduced in v4.1, but none of
  the current v4.4 Xenial kernel drivers uses it (minus rocker which is a
  test bed software switch for devel work on switchdev, it has no real
  function)
  
  # Xenial - kernel v4.4
  config-4.4.0-142-generic:# CONFIG_NET_SWITCHDEV is not set
  
  No drivers uses the phys_port_name method at all + NET_SWITCHDEV is not
  even turned on.
  
  # Xenial HWE - kernel v4.15
  config-4.15.0-99-generic:CONFIG_NET_SWITCHDEV=y
  
  Meaning if a regression arise, it will be limited to the HWE kernel (v4.15) 
and to the "Ethernet switch device driver model (switchdev)":
  mlx5
  mlxsw
  bnxt
  sfc (solarflar)
  
  --
  drivers/net/ethernet:
  --
  broadcom/bnxt/bnxt_vfr.c: .ndo_get_phys_port_name = 
bnxt_vf_rep_get_phys_port_name
  broadcom/bnxt/bnxt.c: .ndo_get_phys_port_name = bnxt_get_phys_port_name
  cavium/liquidio/lio_vf_rep.c: .ndo_get_phys_port_name = 
lio_vf_rep_phys_port_name,
  mellanox/mlx5/core/en_rep.c:  .ndo_get_phys_port_name  = 
mlx5e_rep_get_phys_port_name,
  mellanox/mlxsw/switchx2.c:.ndo_get_phys_port_name = 
mlxsw_sx_port_get_phys_port_name,
  mellanox/mlxsw/spectrum.c:.ndo_get_phys_port_name = 
mlxsw_sp_port_get_phys_port_name,
  netronome/nfp/nfp_net_repr.c: .ndo_get_phys_port_name = 
nfp_port_get_phys_port_name,
  netronome/nfp/nfp_net_common.c:   .ndo_get_phys_port_name = 
nfp_port_get_phys_port_name,
  rocker/rocker_main.c: .ndo_get_phys_port_name = 
rocker_port_get_phys_port_name,
  sfc/efx.c:.ndo_get_phys_port_name = efx_get_phys_port_name,
  --
  
  # On other more specific kernels the regression potential can be
  expanded to virtio-net driver as well.
  
  # cloud-init may taint the result as it renames switchdev(s) after
  systemd at first initialization (even without the phys_port_name
  support) as follows:
  
  (Testing on a sfc card / server deployed by MAAS)
  
  syslog:May 20 22:12:43 OBFUSCATED_HOST kernel: [ 36.199674] sfc :08:00.1 
ens1f1: renamed from eth1 ## systemd
  syslog:May 20 22:12:43 OBFUSCATED_HOST kernel: [ 37.128236] sfc :08:00.0 
ens1f0: renamed from eth0 ## systemd
  
  syslog:May 20 22:12:43 OBFUSCATED_HOST kernel: [ 84.653460] sfc :08:00.0 
ens1f0np0: renamed from ens1f0 ## cloud-init
  syslog:May 20 22:12:43 OBFUSCATED_HOST kernel: [ 84.697177] sfc :08:00.1 
ens1f1np1: renamed from ens1f1 ## cloud-init
  
  cloud-init.log:2020-05-20 22:04:53,980 - util.py[DEBUG]: Running command 
['ip', 'link', 'set', 'ens1f0', 'name', 'ens1f0np0'] with allowed return codes 
[0] (shell=False, capture=True)
  cloud-init.log:2020-05-20 22:04:54,016 - util.py[DEBUG]: Running command 
['ip', 'link', 'set', 'ens1f1', 'name', 'ens1f1np1'] with allowed return codes 
[0] (shell=False, capture=True)
  
+ systemd:
+ ... OBFUSCATED_HOST systemd[1]: sys-subsystem-net-devices-ens1f1.device: Dev 
sys-subsystem-net-devices-ens1f1.device appeared twice with different sysfs 
paths /sys/devices/pci:00/:00:03.0/:08:00.1/net/ens1f1 and 
/sys/devices/pci:00/:00:03.0/:08:00.1/net/ens1f1np1
+ 
  # 1 concern was raise here by ddstreet:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1875927/comments/1
  
  Here's the result of the test I have performed:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1875927/comments/5
  
  This change indeed rename existing switchdev interfaces to add the
  'phys_port_name' (if any) into it. I'm afraid this will be a non-
  acceptable behaviour change in stable release and won't be SRU'able.
  
  More discussion on this topic to come 
  
  [Other informations]
  
https://github.com/systemd/systemd/commit/4887b656c22af059d4e833de7b56544f24951184
  https://github.com/systemd/systemd/pull/4506
  
  [Original Description]
  
  It has been brought to my attention that systemd in Xenial/16.04LTS
  doesn't have support for phys_port_name[0] attribute.
  
  The support has been first introduced in systemd version "232" via:
  
https://github.com/systemd/systemd/commit/4887b656c22af059d4e833de7b56544f24951184
  https://github.com/systemd/systemd/pull/4506
  
  Bionic and late have the necessary bits ( systemd >232), but not Xenial
  (229)[1]
  
  Support for "phys_port_name" has been first introduced in the kernel
  

[Touch-packages] [Bug 1787272] Re: Administrators are not added to adm group

2020-05-21 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

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

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

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

Title:
  Administrators are not added to adm group

Status in accountsservice package in Ubuntu:
  Incomplete

Bug description:
  Currently administrators are only added to the sudo group. This was
  fixed a long time ago by https://bugs.launchpad.net/ubuntu/+source
  /gnome-control-center/+bug/810907, but there has likely been a
  regression.

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

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


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

2020-05-21 Thread Łukasz Zemczak
Hello Jan, or anyone else affected,

Accepted python-apt into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/python-
apt/1.1.0~beta1ubuntu0.16.04.9 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

Title:
  [SRU] apt-add-repository adds duplicate commented/disabled source
  lines

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  Fix Committed
Status in python-apt source package in Bionic:
  Fix Committed
Status in python-apt source package in Eoan:
  Fix Committed

Bug description:
  Impact
  ==

  Under most circumstances, the impact is minimal (a few extra redundant
  comment lines in apt sources. However, if users are automating source
  removal / addition on a machine (as in comment 11), there is the
  potential to wind up with an excessively large (and thus slow to
  parse) apt sources configuration.

  Test packages for the supported releases are available from the
  following PPA:

  https://launchpad.net/~waveform/+archive/ubuntu/python-apt

  Built from the source which can be found in the following branches:

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-xenial

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-bionic

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-eoan

  Test Case
  =

  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the presence of one uncommented "deb" line, and one commented 
"deb-src" line
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the uncommented "deb" line is still there but the commented "deb-src" 
line has now been duplicated
  * sudo add-apt-repository ppa:waveform/python-apt
  * sudo apt upgrade  # update python-apt to fixed version
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note there has been no further duplication of the commented "deb-src" line

  Regression Potential
  

  Minimal; test cases have been added to cover the duplication case, and
  to cover the enabling of sources (which was not covered by existing
  tests, but was part of the code altered to fix the duplication case),
  and insertion of sources at a position (again, not covered by existing
  tests but modified as part of the fix). The test case has been used
  successfully on all targeted releases (xenial, bionic, and eoan).

  Original Description
  

  Trusty Tahr 14.04

  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list
  deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y 
ppa:aims/aims-desktop
  gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created
  gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created
  gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created
  gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)
  OK
  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb 
http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#

  That deb-src line should have stayed commented out, 

[Touch-packages] [Bug 1878775] Re: gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from _systemd_session_is_graphical() from _find_gr

2020-05-21 Thread Sebastien Bacher
The issue is in accountsservice, it would be useful to know if the fix
for bug #1843982 makes a difference there

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

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

Title:
  gnome-shell crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from
  _systemd_session_is_graphical() from _find_graphical_systemd_session()

Status in accountsservice package in Ubuntu:
  New

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

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

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


[Touch-packages] [Bug 1311056] Re: [SRU] apt-add-repository adds duplicate commented/disabled source lines

2020-05-21 Thread Łukasz Zemczak
Hello Jan, or anyone else affected,

Accepted python-apt into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/python-
apt/1.6.5ubuntu0.3 in a few hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-bionic

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

** Tags added: verification-needed-xenial

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

Title:
  [SRU] apt-add-repository adds duplicate commented/disabled source
  lines

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  Fix Committed
Status in python-apt source package in Bionic:
  Fix Committed
Status in python-apt source package in Eoan:
  Fix Committed

Bug description:
  Impact
  ==

  Under most circumstances, the impact is minimal (a few extra redundant
  comment lines in apt sources. However, if users are automating source
  removal / addition on a machine (as in comment 11), there is the
  potential to wind up with an excessively large (and thus slow to
  parse) apt sources configuration.

  Test packages for the supported releases are available from the
  following PPA:

  https://launchpad.net/~waveform/+archive/ubuntu/python-apt

  Built from the source which can be found in the following branches:

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-xenial

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-bionic

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-eoan

  Test Case
  =

  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the presence of one uncommented "deb" line, and one commented 
"deb-src" line
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the uncommented "deb" line is still there but the commented "deb-src" 
line has now been duplicated
  * sudo add-apt-repository ppa:waveform/python-apt
  * sudo apt upgrade  # update python-apt to fixed version
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note there has been no further duplication of the commented "deb-src" line

  Regression Potential
  

  Minimal; test cases have been added to cover the duplication case, and
  to cover the enabling of sources (which was not covered by existing
  tests, but was part of the code altered to fix the duplication case),
  and insertion of sources at a position (again, not covered by existing
  tests but modified as part of the fix). The test case has been used
  successfully on all targeted releases (xenial, bionic, and eoan).

  Original Description
  

  Trusty Tahr 14.04

  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list
  deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y 
ppa:aims/aims-desktop
  gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created
  gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created
  gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created
  gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)
  OK
  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb 
http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty 

[Touch-packages] [Bug 1311056] Re: [SRU] apt-add-repository adds duplicate commented/disabled source lines

2020-05-21 Thread Łukasz Zemczak
Hello Jan, or anyone else affected,

Accepted python-apt into eoan-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/python-
apt/1.9.0ubuntu1.4 in a few hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-eoan

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

Title:
  [SRU] apt-add-repository adds duplicate commented/disabled source
  lines

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  In Progress
Status in python-apt source package in Bionic:
  In Progress
Status in python-apt source package in Eoan:
  Fix Committed

Bug description:
  Impact
  ==

  Under most circumstances, the impact is minimal (a few extra redundant
  comment lines in apt sources. However, if users are automating source
  removal / addition on a machine (as in comment 11), there is the
  potential to wind up with an excessively large (and thus slow to
  parse) apt sources configuration.

  Test packages for the supported releases are available from the
  following PPA:

  https://launchpad.net/~waveform/+archive/ubuntu/python-apt

  Built from the source which can be found in the following branches:

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-xenial

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-bionic

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-eoan

  Test Case
  =

  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the presence of one uncommented "deb" line, and one commented 
"deb-src" line
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the uncommented "deb" line is still there but the commented "deb-src" 
line has now been duplicated
  * sudo add-apt-repository ppa:waveform/python-apt
  * sudo apt upgrade  # update python-apt to fixed version
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note there has been no further duplication of the commented "deb-src" line

  Regression Potential
  

  Minimal; test cases have been added to cover the duplication case, and
  to cover the enabling of sources (which was not covered by existing
  tests, but was part of the code altered to fix the duplication case),
  and insertion of sources at a position (again, not covered by existing
  tests but modified as part of the fix). The test case has been used
  successfully on all targeted releases (xenial, bionic, and eoan).

  Original Description
  

  Trusty Tahr 14.04

  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list
  deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y 
ppa:aims/aims-desktop
  gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created
  gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created
  gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created
  gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)
  OK
  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb 
http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src 

[Touch-packages] [Bug 1878775] Re: gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from _systemd_session_is_graphical() from _find_gr

2020-05-21 Thread Sebastien Bacher
** Package changed: gnome-shell (Ubuntu) => accountsservice (Ubuntu)

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

Title:
  gnome-shell crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from
  _systemd_session_is_graphical() from _find_graphical_systemd_session()

Status in accountsservice package in Ubuntu:
  New

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

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

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


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

2020-05-21 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1879958 ***
https://bugs.launchpad.net/bugs/1879958

** This bug has been marked a duplicate of bug 1879958
   
/usr/libexec/ibus-ui-gtk3:11:__vfprintf_internal:buffered_vfprintf:IO_validate_vtable:__vfprintf_internal:___fprintf_chk

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

Title:
  ibus crash

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  ibus crash

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue May 12 16:59:54 2020
  InstallationDate: Installed on 2017-12-13 (880 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to focal on 2020-04-21 (21 days ago)

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

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


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

2020-05-21 Thread errors.ubuntu.com bug bridge
Public bug reported:

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

** Affects: ibus (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: focal

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

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

Status in ibus package in Ubuntu:
  Confirmed

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

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

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


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

2020-05-21 Thread Sebastien Bacher
** Changed in: ibus (Ubuntu)
   Importance: Undecided => High

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

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

Status in ibus package in Ubuntu:
  Confirmed

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

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

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


[Touch-packages] [Bug 1879960] [NEW] pcscd doesn't support ActivKEy SIM B/N: 0945423

2020-05-21 Thread Dejan
Public bug reported:

I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not 
recognized by pcscd. Since it is not recognized, it is also not recognized by 
VMware Workstation VM which runs Windows. Banking software running in windows 
doesn't see the key and can't authenticate me.
Few years ago, this was working on Ubuntu 18.04, so it must be something in 
version between.
After restart of the pcscd service, USB key shows green light, but few seconds 
after it goes to red.

sudo service pcscd status
● pcscd.service - PC/SC Smart Card Daemon
 Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor 
preset: enabled)
 Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago
TriggeredBy: ● pcscd.socket
   Docs: man:pcscd(8)
   Main PID: 230408 (pcscd)
  Tasks: 5 (limit: 57614)
 Memory: 1.9M
 CGroup: /system.slice/pcscd.service
 └─230408 /usr/sbin/pcscd --foreground --auto-exit

svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon.
svi 21 15:48:01 rodigerlaptop1 pcscd[230408]:  
ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE
svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 
commands.c:249:CmdPowerOn Card absent or mute
svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 
commands.c:249:CmdPowerOn Card absent or mute
svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 
commands.c:249:CmdPowerOn Card absent or mute
svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 
ifdhandler.c:1221:IFDHPowerICC() PowerUp failed
svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 
eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 
0x80100016

Result of pcsc_scan
sudo pcsc_scan 
Using reader plug'n play mechanism
Scanning present readers...
Waiting for the first reader...found one
Scanning present readers...
0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
 
Thu May 21 15:44:16 2020
 Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
  Event number: 0
  Card state: Card inserted, Unresponsive card, 

So USB key is visible

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pcscd 1.8.26-3
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu May 21 15:38:57 2020
SourcePackage: pcsc-lite
UpgradeStatus: Upgraded to focal on 2020-05-11 (10 days ago)

** Affects: pcsc-lite (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 pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1879960

Title:
  pcscd doesn't support ActivKEy SIM B/N: 0945423

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not 
recognized by pcscd. Since it is not recognized, it is also not recognized by 
VMware Workstation VM which runs Windows. Banking software running in windows 
doesn't see the key and can't authenticate me.
  Few years ago, this was working on Ubuntu 18.04, so it must be something in 
version between.
  After restart of the pcscd service, USB key shows green light, but few 
seconds after it goes to red.

  sudo service pcscd status
  ● pcscd.service - PC/SC Smart Card Daemon
   Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor 
preset: enabled)
   Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago
  TriggeredBy: ● pcscd.socket
 Docs: man:pcscd(8)
 Main PID: 230408 (pcscd)
Tasks: 5 (limit: 57614)
   Memory: 1.9M
   CGroup: /system.slice/pcscd.service
   └─230408 /usr/sbin/pcscd --foreground --auto-exit

  svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon.
  svi 21 15:48:01 rodigerlaptop1 pcscd[230408]:  
ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 
ifdhandler.c:1221:IFDHPowerICC() PowerUp failed
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 
eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 
0x80100016

  Result of pcsc_scan
  sudo pcsc_scan 
  Using reader plug'n play mechanism
  Scanning present readers...
  Waiting for the first reader...found one
  Scanning present readers...
  0: ActivIdentity Activkey_Sim [CCID 

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

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

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

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

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

Status in ibus package in Ubuntu:
  Confirmed

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

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

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


[Touch-packages] [Bug 1878775] [NEW] gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from _systemd_session_is_graphical() from _find_

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

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

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


** Tags: focal
-- 
gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() 
from g_autoptr_cleanup_generic_gfree() from _systemd_session_is_graphical() 
from _find_graphical_systemd_session()
https://bugs.launchpad.net/bugs/1878775
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to accountsservice 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 1784163] Re: gnome-initial-setup hangs enabling livepatch

2020-05-21 Thread Sebastien Bacher
** Changed in: gnome-online-accounts (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-initial-setup (Ubuntu)
   Importance: Undecided => Low

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

Title:
  gnome-initial-setup hangs enabling livepatch

Status in gnome-initial-setup package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded from Artful to Bionic. gnome-initial-setup ran. It
  asked me if I wanted to enable Livepatch, and I agreed. I believe my
  Internet connection was working fine at the time. It gave me a
  username/password prompt. After entering those in it asked me for a
  2FA code. After entering that in, I got a spinner with "Connecting..."
  in the bottom left, but nothing further happens. It's been about ten
  minutes hung like that.

  I tried to click the Cancel button but nothing happened. Then I tried
  to close the app from the bar on the left (right click -> Quit) but
  nothing happened.

  After the previous actions, netstat reports no TCP connections on IPv4
  nor IPv6. It's appears not to be "Connecting" to anything.

  Expected: at least some kind of timeout reporting failure so I can
  progress with any other "initial setup" actions.

  A few things about my installation:

  I installed this laptop with Artful initially, around the beta1
  milestone. I dist upgraded it to Artful after release. Before
  upgrading to Bionic I made sure it was fully up to date.

  apport-bug didn't work. After I click Send, I got no browser prompt to
  finish my report. This might be because I have an unusual Firefox
  setup (multiple profiles).

  I noticed that I have bionic-proposed enabled. This is unintentional.
  It seems likely that I had artful-proposed enabled for test purposes
  previously. I did have a pin deprioritising it, but it refers to
  artful specifically so doesn't seem to have acted on Bionic, so
  unfortunately I've ended up upgrading all the way up to bionic-
  proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1784163/+subscriptions

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


[Touch-packages] [Bug 1871185] Re: urls in ubuntu-bug's dialog not really clickable

2020-05-21 Thread Olivier Tilloy
Thanks Brian!

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

Title:
  urls in ubuntu-bug's dialog not really clickable

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed

Bug description:
  when ubuntu-bug report suggests filing a bug report directly in
  launchpad for snap packages, the displayed url is clickable but the
  url stops at the first + symbol. see attachment.

  Test Case
  -
  1) On an Ubuntu 20.04 LTS system run 'ubuntu-bug chromium'
  2) Observe a "the problem cannot be reported" message with a link that is not 
fully highlighted

  With the version of apport from -proposed the link will be fully
  highlighted and will be clickable.

  Regression Potential
  
  The re for what constitutes a url is just improved and the snap dialog is the 
only one I can find with a url in it. Given that url highlighting is "broken" 
there isn't any potential for regression.

  Original Description
  
  ProblemType: BugDistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8.8
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportLog:

  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CrashReports: 640:1000:124:8919925:2020-03-29 20:16:13.456640958 
+0200:2020-03-29 20:16:14.456640958 
+0200:/var/crash/_usr_bin_python3.7.1000.crash
  CurrentDesktop: XFCE
  Date: Mon Apr  6 19:50:16 2020
  InstallationDate: Installed on 2020-03-18 (18 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: allSourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2020-05-21 Thread Łukasz Zemczak
Hello Bart, or anyone else affected,

Accepted apport into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.9-0ubuntu7.15 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  from apport.packaging_impl import impl as packaging
    File 

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

2020-05-21 Thread Łukasz Zemczak
Hello Bart, or anyone else affected,

Accepted apport into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu8.9 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-bionic

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1774843] Re: apport python exception for python versions which python-apt is not built on

2020-05-21 Thread Łukasz Zemczak
Seeing that focal is an LTS, don't you think that it might still useful
to have this 'fix' for that series? Currently we only have python3.8,
but I assume we might backport newer python versions in the future.
Wouldn't that make people potentially affected by this bug then?

I'll accept it as is, but let's reconsider pushing it to focal as well.

** Changed in: apport (Ubuntu Eoan)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-eoan

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  Python 3.7.0b3 (default, Mar 30 2018, 04:35:22)
  [GCC 7.3.0] on linux
  Type "help", 

[Touch-packages] [Bug 1879905] Re: Can no longer connect to Ubuntu WPA hotspot after upgrade to 20.04

2020-05-21 Thread Krister
The upstream report is here:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/2f8a4e90

** Bug watch added: 
gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #450
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/450

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

Title:
  Can no longer connect to Ubuntu WPA hotspot  after upgrade to 20.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  I upgraded my Ubuntu client to 20.04 and could continue to connect to
  my WPA Hotspot running on an Ubuntu server. Upon update of the server
  to 20.04 I could no longer connect with any of my various client OSs.

  After using the updated network-manager from
  https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/1870359, I can now connect to the hotspot from all of my
  machines running many flavors of OS (Windows, MacOS, Android, Ubuntu
  19.10), but I cannot connect from my machine running Ubuntu 20.04.

  If I turn off the encryption on the hotspot or turn on WEP encryption
  (using nm-connection-editor), then I can connect.

  Seeing that my client running 19.10 can connect, I'm not sure if this
  is a problem specif to my particular laptop running 20.04, or if it is
  rather a problem that any client updating to 20.04 will have. I will
  update my other 19.10 machine, that is currently working with the WPA
  hotspot, to help differentiate between these two possibilities.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 10:51:00 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   #dns-nameservers 8.8.8.8 8.8.4.4
  IpRoute:
   default via 192.168.0.1 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.17 metric 600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-10-31T09:47:24.831648
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1879905] Re: Can no longer connect to Ubuntu WPA hotspot after upgrade to 20.04

2020-05-21 Thread Krister
Oops..
  the upstream report is here:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/450

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

Title:
  Can no longer connect to Ubuntu WPA hotspot  after upgrade to 20.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  I upgraded my Ubuntu client to 20.04 and could continue to connect to
  my WPA Hotspot running on an Ubuntu server. Upon update of the server
  to 20.04 I could no longer connect with any of my various client OSs.

  After using the updated network-manager from
  https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/1870359, I can now connect to the hotspot from all of my
  machines running many flavors of OS (Windows, MacOS, Android, Ubuntu
  19.10), but I cannot connect from my machine running Ubuntu 20.04.

  If I turn off the encryption on the hotspot or turn on WEP encryption
  (using nm-connection-editor), then I can connect.

  Seeing that my client running 19.10 can connect, I'm not sure if this
  is a problem specif to my particular laptop running 20.04, or if it is
  rather a problem that any client updating to 20.04 will have. I will
  update my other 19.10 machine, that is currently working with the WPA
  hotspot, to help differentiate between these two possibilities.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 10:51:00 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   #dns-nameservers 8.8.8.8 8.8.4.4
  IpRoute:
   default via 192.168.0.1 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.17 metric 600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-10-31T09:47:24.831648
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1878969] Re: time-epoch never changes in SRUs

2020-05-21 Thread Dimitri John Ledkov
Thank you balint for cherrypicking this! It builds with the
debian/changelog time in groovy now!

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

Title:
  time-epoch never changes in SRUs

Status in ubuntu-core-initramfs:
  New
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Focal:
  New

Bug description:
  [Impact]

   * Systems without hwclock come up with a fixed time epoch which is not 
updated in SRUs
   * Ideally booting with a newer built of systemd should move time epoch to be 
at least when systemd was last built. For example to the value of 
SOURCE_DATE_EPOCH.

  [Test Case]

   * Boot without network NTP or hwclock
   * Observe that the epoch is the same as the time when NEWS entry in the 
systemd source code was last touched.
   * Boot newer update of systemd, observe that the time epoch is at least 2020

  [Regression Potential]

   * Bad epoch, may result in unable to perform TLS connections,
  validated GPG signatures, and snapd assertions. Changing epoch to be
  more recent is desired. Some machines may rely on the fact that
  "bionic" without hwclock always comes up in year 2018. But in practice
  that is incorrect thing to do.

  [Other Info]
   
   * By default

  option('time-epoch', type : 'integer', value : '-1',
 description : 'time epoch for time clients')

  in systemd is set to the modification time of the NEW entry
  time_epoch = run_command(stat, '-c', '%Y', NEWS).stdout().to_int()

  If available, it should be set to SOURCE_DATE_EPOCH=1585051767 value
  to be compliant with the https://reproducible-
  builds.org/docs/timestamps/ specification.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1878969/+subscriptions

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


[Touch-packages] [Bug 1879087] Re: dbus errors, frequent roaming and unstable connectivity

2020-05-21 Thread Thomas M Steenholdt
Thank you for taking care of this so swiftly.

I don't believe I have much to add to the test-case. From testing
locally I can see that the warnings disappear from the log and the
connection _seems_ more stable. I underscore _seems_ because I have not
been able to figure out which other parts of the system are actually
using these particular dbus messages, if any. If nobody is actually
using these, the perceived improvement could be placebo.

I will keep testing though, because I've generally been struggling with
a stable wifi connection on 20.04.

Thanks again.

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

Title:
  dbus errors, frequent roaming and unstable connectivity

Status in wpa package in Ubuntu:
  Fix Committed

Bug description:
  * Impact
  extra roaming events are been generated

  * Test case
  check the wpa_supplicant log, it should have warnings
  dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3

  the roaming events should not be too frequent

  * Regression potential
  check that wifi connection keep working correctly

  
  --

  When using this version of wpa_supplicant with my company
  WPA2-Enterprise wireless setup, I'm experiencing far too frequent
  roaming events (even when not moving around) accompanied by hiccups in
  connectivity. I also see these messages in the wpa_supplicant log:

  dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property RoamTime in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property SessionLength in object 
/fi/w1/wpa_supplicant1/Interfaces/3

  Having done a little research, at least the dbus errors seem to be
  fixed by this commit upstream:

  
https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756

  So I built a version of wpa_supplicant including this particular patch
  and installed on my machine. Apart from solving the dbus errors
  completely, it seems to have had a positive impact on the frequent
  roaming and unstable connectivity as well (I've run for a day with no
  burst of roaming events at all, where they used to happen every few
  minutes most of the time.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: wpasupplicant 2:2.9-1ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sat May 16 16:47:27 2020
  InstallationDate: Installed on 2020-05-12 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2020-05-21 Thread Rajasekharan N
@Kai-Heng Feng (kaihengfeng)

Added the PPA, updated, and rebooted the system.

Still showing as "Dummy Output.'

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

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

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

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

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

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

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

  

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

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

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

  Any help greatly appreciated.

  Regards,
  Roman

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

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


[Touch-packages] [Bug 1876882] Re: Backport packages for 18.04.5 HWE stack

2020-05-21 Thread Łukasz Zemczak
Hello Timo, or anyone else affected,

Accepted llvm-toolchain-10 into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/llvm-
toolchain-10/1:10.0.0-4ubuntu1~18.04.1 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Changed in: llvm-toolchain-10 (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  Backport packages for 18.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-10 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  New
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-10 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  Fix Committed
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 18.04.5 images.

  [Test case]

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

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

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

  libclc: more or less just adds support for new llvm

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

  xserver: a new point-release

  xorg drivers: modest updates, if any

  [Other info]

  mesa and libclc will migrate to llvm-10 in a separate upload

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

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


[Touch-packages] [Bug 1879945] Re: package mime-support 3.64ubuntu1 failed to install/upgrade: el subproceso visualizador de diferencias entre conffiles devolvió el código de salida de error 127

2020-05-21 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package mime-support 3.64ubuntu1 failed to install/upgrade: el
  subproceso visualizador de diferencias entre conffiles devolvió el
  código de salida de error 127

Status in mime-support package in Ubuntu:
  New

Bug description:
  none

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: mime-support 3.64ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu May 21 14:37:40 2020
  ErrorMessage: el subproceso visualizador de diferencias entre conffiles 
devolvió el código de salida de error 127
  InstallationDate: Installed on 2020-02-23 (88 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: mime-support
  Title: package mime-support 3.64ubuntu1 failed to install/upgrade: el 
subproceso visualizador de diferencias entre conffiles devolvió el código de 
salida de error 127
  UpgradeStatus: Upgraded to focal on 2020-05-21 (0 days ago)
  mtime.conffile..etc.mime.types: 2020-05-06T13:49:46.794140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1879945/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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-21 Thread Dan Streetman
autopkgtest remaining failing tests:

systemd (ppc64el): this has always failed, ignore.
snapd (ii386): this has failed in i386 for a long time due to missing i386 
deps/snaps, ignore

-- 
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 Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Released

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

  [test case, pre-focal]

  same netplan as above, but remove ethernets: section.  Reboot, and the
  bridge should have its address and route:

  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
 valid_lft forever preferred_lft forever
  ubuntu@test-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static linkdown 
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 linkdown 

  
  add and remove carrier, by adding and removing a slave interface:

  ubuntu@test-e:~$ sudo ip l set dev ens3 master br0 up
  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
 valid_lft forever preferred_lft forever
  inet6 fe80::5411:daff:fe23:bb93/64 scope link 
 valid_lft forever preferred_lft forever
  ubuntu@test-e:~$ sudo ip l set dev ens3 nomaster

  
  the bridge no longer has its address after losing carrier:

  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::5411:daff:fe23:bb93/64 scope link 
 valid_lft forever preferred_lft forever


  [regression potential]

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

  [scope]

  This is needed for Focal, Eoan, and Bionic.

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

  [original description]

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

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

  however when converted to a bridged network for kvm

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

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

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

  systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 

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

2020-05-21 Thread Dan Streetman
autopkgtest analysis for eoan above in comment 43, analysis for focal
above in comment 37

-- 
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 Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Released

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

  [test case, pre-focal]

  same netplan as above, but remove ethernets: section.  Reboot, and the
  bridge should have its address and route:

  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
 valid_lft forever preferred_lft forever
  ubuntu@test-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static linkdown 
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 linkdown 

  
  add and remove carrier, by adding and removing a slave interface:

  ubuntu@test-e:~$ sudo ip l set dev ens3 master br0 up
  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
 valid_lft forever preferred_lft forever
  inet6 fe80::5411:daff:fe23:bb93/64 scope link 
 valid_lft forever preferred_lft forever
  ubuntu@test-e:~$ sudo ip l set dev ens3 nomaster

  
  the bridge no longer has its address after losing carrier:

  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::5411:daff:fe23:bb93/64 scope link 
 valid_lft forever preferred_lft forever


  [regression potential]

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

  [scope]

  This is needed for Focal, Eoan, and Bionic.

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

  [original description]

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

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

  however when converted to a bridged network for kvm

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

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

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

  systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: 

[Touch-packages] [Bug 1879927] Re: Merge wpa 2:2.9.0-13 (main) from Debian unstable (main)

2020-05-21 Thread Sebastien Bacher
Thanks but we are tools for tracking packages that need a merge, see
https://merges.ubuntu.com/main.html , there is no need to open bugs for
those on launchpad

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

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

Title:
  Merge wpa 2:2.9.0-13 (main) from Debian unstable (main)

Status in wpa package in Ubuntu:
  New

Bug description:
  Please merge wpa 2:2.9.0-13 (main) from Debian unstable (main)

  The Debian package carries some upstream cherry-picks that are nice to
  have in Ubuntu, plus the packaging updates.

  Sorry, I can't work on this merge myself.

  These Ubuntu changes can be dropped because they are already in Debian:
 * debian/patches/git_realtek_macrand.patch:
  - backport an upstream patch to fix issues with some realtek cards
when MAC address randomization is enabled (lp: #1867908)
 * SECURITY UPDATE: Incorrect indication of disconnection in certain
   situations
   - debian/patches/CVE-2019-16275.patch: silently ignore management
 frame from unexpected source address in src/ap/drv_callbacks.c,
 src/ap/ieee882_11.c.
   - CVE-2019-16275

  Remaining changes specific to Ubuntu:
 * debian/patches/wpa_service_ignore-on-isolate.patch: add
   IgnoreOnIsolate=yes so that when switching "runlevels" in oem-config
   will not kill off wpa and cause wireless to be unavailable on first
   boot.
 * debian/patches/session-ticket.patch: disable the TLS Session Ticket
   extension to fix auth with 802.1x PEAP on some hardware.

  Changelog entries since current groovy version 2:2.9-1ubuntu7:

  wpa (2:2.9.0-13) unstable; urgency=medium

* Apply upstream patches:
  - Avoid sending invalid mgmt frames at startup
  - Increase introspection buffer size for D-Bus

   -- Andrej Shadura   Tue, 19 May 2020 14:29:29
  +0200

  wpa (2:2.9.0-12) unstable; urgency=medium

* Add an upstream patch to fix the MAC randomisation issue with some cards
  (LP: #1867908).

   -- Andrej Shadura   Tue, 24 Mar 2020 11:13:16
  +0100

  wpa (2:2.9.0-11) unstable; urgency=medium

* Actually add autopkgtest for libwpa-client-dev and libwpa_test.c.

   -- Andrej Shadura   Sat, 07 Mar 2020 13:18:19
  +0100

  wpa (2:2.9.0-10) unstable; urgency=medium

* Rename the package with the client library to libwpa-client-dev.

   -- Andrej Shadura   Tue, 25 Feb 2020 20:19:52
  +0100

  wpa (2:2.9.0-9) unstable; urgency=medium

[ Terry Burton ]
* Build and install eapol_test in eapoltest package (Closes: #700870)

[ Didier Raboud ]
* Backport upstream patch to fix build with Debian's VERSION_STR.

[ Andrew Lee (李健秋) ]
* Build libwpa-dev binary package which contains a static
  libwpa_client library and the wpa_ctrl header with an example program.

[ Andrej Shadura ]
* Add a patch to provide the BIT() macro locally in wpa_ctrl.h.
* Patch the example to use stddef.h and wpa_ctrl.h from the global location.
* Add an autopkgtest for libwpa-dev and libwpa_test.c.

   -- Andrej Shadura   Tue, 25 Feb 2020 18:21:35
  +0100

  wpa (2:2.9.0-8) unstable; urgency=medium

* Reupload as 2.9.0 to undo an accidental experimental upload to
  unstable.

   -- Andrej Shadura   Sat, 22 Feb 2020 11:25:29
  +0300

  wpa (2:2.9-7) unstable; urgency=medium

* Apply upstream patches:
  - trace: handle binutils bfd.h breakage
  - Check for FT support when selecting FT suites (Closes: #942164)

   -- Andrej Shadura   Sat, 15 Feb 2020 16:42:04
  +0100

  wpa (2:2.9-6) unstable; urgency=medium

[ Debian Janitor ]
* Use secure URI in Homepage field.
* Move source package lintian overrides to debian/source.
* Use canonical URL in Vcs-Browser.
* Rely on pre-initialized dpkg-architecture variables.
* Update standards version to 4.4.1, no changes needed.

[ Andrej Shadura ]
* Disable CONFIG_DRIVER_MACSEC_QCA on kfreebsd.

   -- Andrej Shadura   Mon, 13 Jan 2020 16:28:58
  +0100

  wpa (2:2.9-5) unstable; urgency=medium

* Fix erroneously inverted logic in postinst.

   -- Andrej Shadura   Mon, 13 Jan 2020 10:48:26
  +0100

  wpa (2:2.9-4) unstable; urgency=medium

[ Helmut Grohne ]
* Fix FTCBFS: Don’t export CC=cc (Closes: #921998).

[ Andrej Shadura ]
* Don’t act in hostapd.postinst if we’re running in a chrootless root.
* Apply an upstream patch:
  - wpa_supplicant: Do not try to detect PSK mismatch during PTK rekeying.

   -- Andrej Shadura   Mon, 13 Jan 2020 10:37:10
  +0100

  wpa (2:2.9-3) unstable; urgency=medium

* Add pkg.wpa.nogui and noudeb build profiles.

   -- Andrej Shadura   Fri, 04 Oct 2019 11:47:15
  +0200

  wpa (2:2.9-2) unstable; urgency=medium

* SECURITY UPDATE:
  - AP mode PMF disconnection protection bypass.
More details:
   

[Touch-packages] [Bug 1875927] Re: add support for phys_port_name attribute in Xenial/16.04LTS

2020-05-21 Thread Eric Desrochers
** Description changed:

  [Impact]
  In Xenial/16.04LTS, one can't generate network interface name from 
"phys_port_name" attribute.
  
  "phys_port_name" indicates the interface physical port name within the
  NIC.
  
  [Test Case]
  
  Check that udev (systemd-udevd) provides the phys_port_name property
  Tests should be done on kernel versions: v4.15 (HWE)
  
  # cat /sys/class/net//phys_port_name
  yyy
  
  Look if interface name contains the 'phys_port_name':
  
  $ ip link show
  
  3: ens3nyyy:  ...
  
  
  [Regression Potential]
  
  * This piece of code is already in place in Bionic (systemd) and late.
  AFAICT, nothing has been reported since then with regards to this feature.
  
  * phys_port_name kernel support has been introduced in v4.1, but none of
  the current v4.4 Xenial kernel drivers uses it (minus rocker which is a
  test bed software switch for devel work on switchdev, it has no real
  function)
  
  # Xenial - kernel v4.4
  config-4.4.0-142-generic:# CONFIG_NET_SWITCHDEV is not set
  
  No drivers uses the phys_port_name method at all + NET_SWITCHDEV is not
  even turned on.
  
  # Xenial HWE - kernel v4.15
  config-4.15.0-99-generic:CONFIG_NET_SWITCHDEV=y
  
  Meaning if a regression arise, it will be limited to the HWE kernel (v4.15) 
and to the "Ethernet switch device driver model (switchdev)":
  mlx5
  mlxsw
  bnxt
  sfc (solarflar)
  
  --
  drivers/net/ethernet:
  --
  broadcom/bnxt/bnxt_vfr.c: .ndo_get_phys_port_name = 
bnxt_vf_rep_get_phys_port_name
  broadcom/bnxt/bnxt.c: .ndo_get_phys_port_name = bnxt_get_phys_port_name
  cavium/liquidio/lio_vf_rep.c: .ndo_get_phys_port_name = 
lio_vf_rep_phys_port_name,
  mellanox/mlx5/core/en_rep.c:  .ndo_get_phys_port_name  = 
mlx5e_rep_get_phys_port_name,
  mellanox/mlxsw/switchx2.c:.ndo_get_phys_port_name = 
mlxsw_sx_port_get_phys_port_name,
  mellanox/mlxsw/spectrum.c:.ndo_get_phys_port_name = 
mlxsw_sp_port_get_phys_port_name,
  netronome/nfp/nfp_net_repr.c: .ndo_get_phys_port_name = 
nfp_port_get_phys_port_name,
  netronome/nfp/nfp_net_common.c:   .ndo_get_phys_port_name = 
nfp_port_get_phys_port_name,
  rocker/rocker_main.c: .ndo_get_phys_port_name = 
rocker_port_get_phys_port_name,
  sfc/efx.c:.ndo_get_phys_port_name = efx_get_phys_port_name,
  --
  
  # On other more specific kernels the regression potential can be
  expanded to virtio-net driver as well.
  
  # cloud-init may taint the result as it renames switchdev(s) after
  systemd at first initialization (even without the phys_port_name
  support) as follows:
  
  (Testing on a sfc card / server deployed by MAAS)
  
  syslog:May 20 22:12:43 OBFUSCATED_HOST kernel: [ 36.199674] sfc :08:00.1 
ens1f1: renamed from eth1 ## systemd
  syslog:May 20 22:12:43 OBFUSCATED_HOST kernel: [ 37.128236] sfc :08:00.0 
ens1f0: renamed from eth0 ## systemd
  
  syslog:May 20 22:12:43 OBFUSCATED_HOST kernel: [ 84.653460] sfc :08:00.0 
ens1f0np0: renamed from ens1f0 ## cloud-init
  syslog:May 20 22:12:43 OBFUSCATED_HOST kernel: [ 84.697177] sfc :08:00.1 
ens1f1np1: renamed from ens1f1 ## cloud-init
  
  cloud-init.log:2020-05-20 22:04:53,980 - util.py[DEBUG]: Running command 
['ip', 'link', 'set', 'ens1f0', 'name', 'ens1f0np0'] with allowed return codes 
[0] (shell=False, capture=True)
  cloud-init.log:2020-05-20 22:04:54,016 - util.py[DEBUG]: Running command 
['ip', 'link', 'set', 'ens1f1', 'name', 'ens1f1np1'] with allowed return codes 
[0] (shell=False, capture=True)
  
- **
- Concern:
+ # 1 concern was raise here by ddstreet:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1875927/comments/1
  
- Result:
+ Here's the result of the test I have performed:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1875927/comments/5
- **
  
  [Other informations]
  
https://github.com/systemd/systemd/commit/4887b656c22af059d4e833de7b56544f24951184
  https://github.com/systemd/systemd/pull/4506
  
  [Original Description]
  
  It has been brought to my attention that systemd in Xenial/16.04LTS
  doesn't have support for phys_port_name[0] attribute.
  
  The support has been first introduced in systemd version "232" via:
  
https://github.com/systemd/systemd/commit/4887b656c22af059d4e833de7b56544f24951184
  https://github.com/systemd/systemd/pull/4506
  
  Bionic and late have the necessary bits ( systemd >232), but not Xenial
  (229)[1]
  
  Support for "phys_port_name" has been first introduced in the kernel
  with v4.1[2]
  
  [0]
  - https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
  - 
https://www.freedesktop.org/software/systemd/man/systemd.net-naming-scheme.html
  - https://www.kernel.org/doc/Documentation/networking/switchdev.txt
  
  [1]
  # git systemd/systemd
  git describe --contains 4887b656c22af059d4e833de7b56544f24951184
  v232~15
  
  # rmadison
   => systemd | 229-4ubuntu21.27 | xenial-updates
   systemd | 237-3ubuntu10.39 | bionic-updates
   systemd | 240-6ubuntu5.8   | disco-updates
   systemd | 

[Touch-packages] [Bug 1879945] [NEW] package mime-support 3.64ubuntu1 failed to install/upgrade: el subproceso visualizador de diferencias entre conffiles devolvió el código de salida de error 127

2020-05-21 Thread Carmen
Public bug reported:

none

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mime-support 3.64ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu May 21 14:37:40 2020
ErrorMessage: el subproceso visualizador de diferencias entre conffiles 
devolvió el código de salida de error 127
InstallationDate: Installed on 2020-02-23 (88 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: mime-support
Title: package mime-support 3.64ubuntu1 failed to install/upgrade: el 
subproceso visualizador de diferencias entre conffiles devolvió el código de 
salida de error 127
UpgradeStatus: Upgraded to focal on 2020-05-21 (0 days ago)
mtime.conffile..etc.mime.types: 2020-05-06T13:49:46.794140

** Affects: mime-support (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package mime-support 3.64ubuntu1 failed to install/upgrade: el
  subproceso visualizador de diferencias entre conffiles devolvió el
  código de salida de error 127

Status in mime-support package in Ubuntu:
  New

Bug description:
  none

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: mime-support 3.64ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu May 21 14:37:40 2020
  ErrorMessage: el subproceso visualizador de diferencias entre conffiles 
devolvió el código de salida de error 127
  InstallationDate: Installed on 2020-02-23 (88 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: mime-support
  Title: package mime-support 3.64ubuntu1 failed to install/upgrade: el 
subproceso visualizador de diferencias entre conffiles devolvió el código de 
salida de error 127
  UpgradeStatus: Upgraded to focal on 2020-05-21 (0 days ago)
  mtime.conffile..etc.mime.types: 2020-05-06T13:49:46.794140

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1879945/+subscriptions

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


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

2020-05-21 Thread Kai-Heng Feng
I pushed a new package to the PPA, please use it for now:
https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819

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

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

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

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

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

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

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

  

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

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

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

  Any help greatly appreciated.

  Regards,
  Roman

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

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


[Touch-packages] [Bug 1879533] Re: busybox does not verify TLS connections with CONFIG_FEATURE_WGET_OPENSSL=y and CONFIG_FEATURE_WGET_HTTPS unset, and doesn't warn either about it

2020-05-21 Thread Francis Ginther
** Tags added: id-5ec405c08ffc87364ab8cf50

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

Title:
  busybox does not verify TLS connections with
  CONFIG_FEATURE_WGET_OPENSSL=y and CONFIG_FEATURE_WGET_HTTPS unset, and
  doesn't warn either about it

Status in busybox package in Ubuntu:
  Fix Committed
Status in busybox source package in Focal:
  New
Status in busybox source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

   * CONFIG_FEATURE_WGET_OPENSSL=y enables https support in wget busybox
  applet using openssl

   * CONFIG_FEATURE_WGET_HTTPS=y enables https support in wget busybox
  applet using internal TLS code

   * CVE-2018-1000500 ensured that when CONFIG_FEATURE_WGET_HTTPS=y is
  used, a message is printed to notify the users that TLS verification
  is not perfomed.

   * However, when one configures with CONFIG_FEATURE_WGET_OPENSSL=y and
  CONFIG_FEATURE_WGET_HTTPS unset - no such message is printed.

   * Also TLS verification is not performed under OPENSSL case.

   * When performing https requests, it works openssl s_client and communicates 
with it to perform https download
   * Whilst doing so, it does not pass `-verify_return_error` option, meaning 
any verification errors are ignored

   * There is no warning that TLS verification was not performed

  [Test Case]

   * Preparation: sudo apt install busybox; or build busybox with
  CONFIG_FEATURE_WGET_OPENSSL=y

   * Test case: /bin/busybox wget https://untrusted-root.badssl.com/

   * Expected: download failed, or download suceeds with warning printed
  that verification is disabled

   * Observed: download success without a warning that verification is
  disabled.

  $ /bin/busybox wget https://untrusted-root.badssl.com/
  Connecting to untrusted-root.badssl.com (104.154.89.105:443)
  index.html   100% 
|*|
   600  0:00:00 ETA

  $ cat index.html  | grep certificate
    The certificate for this site is signed using an untrusted root.

  [Regression Potential]

   * The fact that /bin/busybox wget https:// succeeds without TLS
  verification might be relied upon. If this issue is fixed, ensure that
  `--no-check-certificate` is honored.

  [Other Info]

   * Proposed fix

     pass `-verify_return_error` to s_client, unless `--no-check-
  certificate` is specified

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

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


  1   2   >