[Touch-packages] [Bug 1748956] Re: replace uses of net-tools with iproute2

[Christian Ehrhardt ]

** Tags added: server-next server-triage-discuss

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

Title:
  replace uses of net-tools with iproute2

Status in byobu:
  Fix Committed
Status in byobu package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  As ubuntu goes forward, net-tools is looking to be dropped.

  Byobu currently depends on net-tools.  That code should be replaced by
  iproute2.

  
  Related bugs:
   * bug 925145: cloud-init  Use ip instead of ifconfig and route

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: byobu 5.124-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 12 13:34:27 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (935 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: byobu
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1749774] Re: include fwupd packages in Server Seed

[Christian Ehrhardt ]

** Tags added: server-next server-triage-discuss

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

Title:
  include fwupd packages in Server Seed

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  fwupd is the closest we have to a standard mechanism currently for
  doing in-band firmware updates in a vendor agnostic way.  As long as
  the vendors provide firmware blobs in an appropriately formatted
  package, fwupd (or fwupdate) can install those firmware blobs from
  within Ubuntu.

  Because of this, we should include the related packages in the server
  seed.  The main components all live in Main currently.  As far as I
  can tell (verified on a Bionic install), nothing in the current server
  seed pulls in fwupd, fwupdate, or fwupdate-signed as a dependency.

  ubuntu@xwing:~$ apt-cache policy fwup*

  fwupdate:
Installed: (none)
Candidate: 10-2
Version table:
   10-2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  fwupd:
Installed: (none)
Candidate: 1.0.4-3build1
Version table:
   1.0.4-3build1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  fwupdate-signed:
Installed: (none)
Candidate: 1.17+10-2
Version table:
   1.17+10-2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

[Touch-packages] [Bug 1380702] Re: No keyboards shortcuts in QT apps

[Dmitry Shachnev]

This bug was only relevant to Unity. Please file a new bug, preferably
upstream to https://bugreports.qt.io and preferably after testing with
Ubuntu 19.04 (which has newer Qt).

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

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  Fix Released
Status in Canonical System Image:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Xenial:
  Fix Released
Status in qtbase-opensource-src source package in Yakkety:
  Won't Fix

Bug description:
  Impact
  ==

  This affects all Qt applications on Unity and other desktops which use
  global menu, either via appmenu-qt5 or via native implementation on
  Yakkety.

  Any shortcut is not working if the corresponding action is attached
  only to the menubar (i.e. and not also to the toolbar). It can be
  reproduced with almost any application by removing the toolbar (right-
  clicking on it and deselecting it).

  Test Case
  =

  * Open Qt Assistant;
  * Press Ctrl+T (this action is not on the toolbar).

  Expected: a new tab should be opened. Current result: nothing happens.

  In Yakkety the fix should work both with and without appmenu-qt5.

  Proposed Fix
  

  The proposed fix is a backport of the upstream fix at
  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=287f548d4c7cc594.

  Actually just the qshortcut.cpp part would be sufficient, but the
  other parts make sure it plays fine together with https://cgit.kde.org
  /plasma-integration.git/commit/?id=aef74e97e2ed462a.

  Regression Potential
  

  The fix is in Zesty for 1½ months now (in upstream even longer), and
  so far nobody complained. People have verified that the fix works (see
  comment #63).

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions

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

[Touch-packages] [Bug 1333140] Re: Fix udev rules to consider mmc rpmb partitions

[Atomos Lyu]

** Changed in: udev (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  Fix udev rules to consider mmc rpmb partitions

Status in systemd package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Invalid
Status in udev package in Ubuntu:
  Fix Released
Status in udisks package in Ubuntu:
  Triaged
Status in udev source package in Precise:
  Invalid
Status in udisks source package in Precise:
  Triaged
Status in systemd source package in Trusty:
  Fix Released
Status in udisks source package in Trusty:
  Triaged

Bug description:
  As per JEDEC 4.5 spec for eMMC devices,
  There is a new partitions as part of eMMC storage devices it self. (Further 
details please refer eMMC spec)

  *In Linux Kernel@ 3.10.33, mmc driver has created a new partitions
  with "mmcblkXrpmb" if device expresses it support of RPMB.

  Issues observed:

  issue 1:
  RPMB (Replay Protected Memory Block), A signed access to a Replay Protected 
Memory Block is provided. This function provides means for the system to store 
data to the specific memory area in an authenticated and replay protected 
manner.
  In that case, any read/write access to this partition device will report 
errors.

  issue 2:
  The by-path, line is wrongly mapping to platform-sdhci-tegra.1  -> 
mmcblk2rpmb were as
  it should be platform-sdhci-tegra.1  -> mmcblk2

  ls -l /dev/disk/by-path/
  total 0
  lrwxrwxrwx 1 root root 17 Jan  3  2000 platform-sdhci-tegra.1 -> 
../../mmcblk2rpmb
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.1-part1 -> 
../../mmcblk2p1
  lrwxrwxrwx 1 root root 13 Jan  3  2000 platform-sdhci-tegra.2 -> ../../mmcblk1
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.2-part1 -> 
../../mmcblk1p1
  lrwxrwxrwx 1 root root 17 Jan  3  2000 platform-sdhci-tegra.3 -> 
../../mmcblk0rpmb
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.3-part1 -> 
../../mmcblk0p1
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.3-part2 -> 
../../mmcblk0p2

  We have locally resolved in our platform in this file 60-persistent-
  storage.rules

  For issue 1: (with this rule)
  # skip block read for partitions of type rpmb
  KERNEL=="mmcblk[0-9]rpmb", SUBSYSTEM=="block", GOTO="persistent_storage_end"

  For issue 2:
  ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL=="mmcblk[0-9]rpmb", 
SYMLINK+="disk/by-path/$env{ID_PATH}-rpmb"
  ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL!="mmcblk[0-9]rpmb", 
SYMLINK+="disk/by-path/$env{ID_PATH}"

  Please consider this issues fix in next udev release .

  
  SRU INFO: This is mostly an issue with running backported kernels on 12.04 
and 14.04. There is no test case which would reproduce this on arbitrary 
hardware, but there are several reporters which are in a position to verify a 
proposed update.

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

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

[Touch-packages] [Bug 1828505] [NEW] sudo apt-get upgrade E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) E: Unable to acquire the dpkg frontend lock (/

[Himangshu]

Public bug reported:

I am having problem in upgarde. terminal showing

sudo apt-get upgrade
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource 
temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is 
another process using it?

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  sudo apt-get upgrade E: Could not get lock /var/lib/dpkg/lock-frontend
  - open (11: Resource temporarily unavailable) E: Unable to acquire the
  dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process
  using it?

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  I am having problem in upgarde. terminal showing

  sudo apt-get upgrade
  E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource 
temporarily unavailable)
  E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is 
another process using it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1828505/+subscriptions

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

[Touch-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Hui Wang]

I guess you alsa driver works after booing up, but the pulseaudio fails
to get your built in sound card via alsa-lib.

To check it, after booing up, run pactl list cards, I guess you could
only see one dummy card and one nvidia hdmi audio card; after sudo alsa
force-reload and run pactl list cards, you will see one built in audio
card and one nvidia hdmi audio card.

If it does, we need to debug pulseaduio to check why it fails to detect
built-in card after booing up.

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 508522] Re: Mic is not available with A2DP Bluetooth profile

[Daniel van Vugt]

Since we are still getting complaints about this issue and my comment
#40 was not accompanied with an exact verified fix, this bug is
reopened.

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

** Tags added: bionic

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

Title:
  Mic is not available with A2DP Bluetooth profile

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pulseaudio

  I'm testing a Nokia BH-905i headset (see 
http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The 
Bluetooth module correctly identifies the headset and the both audio profiles 
"HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music 
playback only A2DP is suitable (HSP/HFP sounds like listening to music played 
through an old telephone). A2DP does not have an INPUT mode, so use of the 
headset for VoiP isn't possible.
  What would be needed is a separate selection to allow to select A2DP for 
output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do 
that (or they switch on the fly?).

  Formal structure:
  1) Ubuntu 10.10
  2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  consisting og pluseaudio, pulseaudio-esound-compat, 
pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, 
pulseaudio-utils
  3) Select high quality audio output and still use the Bluetooth microphone
  4) Had to choose: either high quality audio or "telephone quality" with 
microphone

  I can change the profile without the Bluetooth connection dropping,
  but that's ridiculous. E.g. listening to music, a call comes in. Then
  I would need to switch the profile before answering. Please note that
  in Windows, Mac OS, iOS, Android, and Windows Mobile it's done
  automatically.

  Check out attached screencast.

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oivasyuv   2309 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17'
     Mixer name : 'Analog Devices AD1984A'
     Components : 'HDA:11d4194a,103c30e8,00100400'
     Controls  : 22
     Simple ctrls  : 14
  Date: Sat Jan 16 22:31:41 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: pulseaudio 1:0.9.19-0ubuntu4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-17-generic-pae i686

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

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

[Touch-packages] [Bug 508522] Re: Mic is not available with A2DP Bluetooth profile

[Daniel van Vugt]

Interesting though, that we are only getting complaints about Ubuntu
18.04 now. Maybe the problem was fixed in a later release?

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

Title:
  Mic is not available with A2DP Bluetooth profile

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pulseaudio

  I'm testing a Nokia BH-905i headset (see 
http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The 
Bluetooth module correctly identifies the headset and the both audio profiles 
"HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music 
playback only A2DP is suitable (HSP/HFP sounds like listening to music played 
through an old telephone). A2DP does not have an INPUT mode, so use of the 
headset for VoiP isn't possible.
  What would be needed is a separate selection to allow to select A2DP for 
output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do 
that (or they switch on the fly?).

  Formal structure:
  1) Ubuntu 10.10
  2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  consisting og pluseaudio, pulseaudio-esound-compat, 
pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, 
pulseaudio-utils
  3) Select high quality audio output and still use the Bluetooth microphone
  4) Had to choose: either high quality audio or "telephone quality" with 
microphone

  I can change the profile without the Bluetooth connection dropping,
  but that's ridiculous. E.g. listening to music, a call comes in. Then
  I would need to switch the profile before answering. Please note that
  in Windows, Mac OS, iOS, Android, and Windows Mobile it's done
  automatically.

  Check out attached screencast.

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oivasyuv   2309 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17'
     Mixer name : 'Analog Devices AD1984A'
     Components : 'HDA:11d4194a,103c30e8,00100400'
     Controls  : 22
     Simple ctrls  : 14
  Date: Sat Jan 16 22:31:41 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: pulseaudio 1:0.9.19-0ubuntu4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-17-generic-pae i686

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

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

[Touch-packages] [Bug 1828393] Re: Unable to use bluetooth headset with mic and a2dp audio

[Daniel van Vugt]

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

> Every device supports high fidelity audio while using headset with
mic. This needs to enable two profiles at once: headset_head_unit and
a2dp_sink.

I really hope you are right there, but I don't know enough about the
Bluetooth specs to confirm that multiple profiles can run simultaneously
(at least on most devices).

Regardless, I have reopened bug 508522 covering this issue.

** This bug has been marked a duplicate of bug 508522
   Mic is not available with A2DP Bluetooth profile

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

Title:
  Unable to use bluetooth headset with mic and a2dp audio

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Every device supports high fidelity audio while using headset with
  mic. This needs to enable two profiles at once: headset_head_unit and
  a2dp_sink. Right now this is impossible and I need to switch between
  profiles when listening to music and joining a call. In any case, the
  sound quality of HSP/HFP used in the headset_head_unit profile is
  horrible to have a call.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  9 13:20:26 2019
  InstallationDate: Installed on 2018-11-20 (169 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET35W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1711087] Re: ad2p sink profile mic not available

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 508522
   Mic is not available with A2DP Bluetooth profile

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

Title:
  ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I have a bose soundsport bluetooth headset. When I select the ad2p
  sink profile there is no microphone available. Only with the HSP
  profile my microphone is available.

  It's really annoying to have to switch between profiles to make a call
  or to listen to normal quality music.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeroen 3801 F pulseaudio
   /dev/snd/controlC0:  jeroen 3801 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Aug 16 11:02:37 2017
  InstallationDate: Installed on 2017-05-10 (98 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1773IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1773
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GS70 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Touch-packages] [Bug 1828393] Re: Unable to use bluetooth headset with mic and a2dp audio

[Daniel van Vugt]

** Tags added: a2dp

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

Title:
  Unable to use bluetooth headset with mic and a2dp audio

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Every device supports high fidelity audio while using headset with
  mic. This needs to enable two profiles at once: headset_head_unit and
  a2dp_sink. Right now this is impossible and I need to switch between
  profiles when listening to music and joining a call. In any case, the
  sound quality of HSP/HFP used in the headset_head_unit profile is
  horrible to have a call.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  9 13:20:26 2019
  InstallationDate: Installed on 2018-11-20 (169 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET35W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 841409] Re: GEdit is the only choice as Calendar application in Default Applications dialog

[Julien Olivier]

I've reported is as a gnome-calendar bug here:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1828491

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

Title:
  GEdit is the only choice as Calendar application in Default
  Applications dialog

Status in gnome-control-center:
  Expired
Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in desktop-file-utils source package in Oneiric:
  Won't Fix
Status in gtk+3.0 source package in Oneiric:
  Won't Fix
Status in desktop-file-utils source package in Precise:
  Fix Released
Status in gtk+3.0 source package in Precise:
  Triaged

Bug description:
  In Ubuntu Oneiric (11.10) beta1, opening the Default Applications dialog 
(System Settings -> System Information), GEdit is selected (and only possible 
choice) for Calendar items.
  I think this is not expected, since it is not so useful to open calendar data 
as standard text).

  In Oneiric Thunderbird is default email client. Currently Thunderbird7 beta 
is installed, and I noticed the Lightning extension for Calendar is not 
compatible with it yet.
  Will Thunderbird/Lightining be possible values for Calendar applications?

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.1.90-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic i686
  Architecture: i386
  Date: Mon Sep  5 00:56:27 2011
  ProcEnviron:
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-09-03 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/841409/+subscriptions

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

[Touch-packages] [Bug 841409] Re: GEdit is the only choice as Calendar application in Default Applications dialog

[Julien Olivier]

I have gnome-calendar installed on Ubuntu 19.04, and gedit is still
displayed as the only available choice in the default app settings. The
workaround was to run the following: gio mime text/calendar
org.gnome.Calendar.desktop

Now gnome-calendar appears as the default (and only) calendar app...

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

Title:
  GEdit is the only choice as Calendar application in Default
  Applications dialog

Status in gnome-control-center:
  Expired
Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in desktop-file-utils source package in Oneiric:
  Won't Fix
Status in gtk+3.0 source package in Oneiric:
  Won't Fix
Status in desktop-file-utils source package in Precise:
  Fix Released
Status in gtk+3.0 source package in Precise:
  Triaged

Bug description:
  In Ubuntu Oneiric (11.10) beta1, opening the Default Applications dialog 
(System Settings -> System Information), GEdit is selected (and only possible 
choice) for Calendar items.
  I think this is not expected, since it is not so useful to open calendar data 
as standard text).

  In Oneiric Thunderbird is default email client. Currently Thunderbird7 beta 
is installed, and I noticed the Lightning extension for Calendar is not 
compatible with it yet.
  Will Thunderbird/Lightining be possible values for Calendar applications?

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.1.90-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic i686
  Architecture: i386
  Date: Mon Sep  5 00:56:27 2011
  ProcEnviron:
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-09-03 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/841409/+subscriptions

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

[Touch-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

I rebooted and went into the "Ubuntu" desktop and looked at the sound
settings.  It shows an output tab and said "dummy".  I clicked and was
able to switch it to the nvidia card.  I think maybe the nvidia card was
off, which it should be since there's no output device connected.

I went back into my regular environment and observed that the nvidia
output was available but not the built-in sound.  I ran aplay test.wav
and could see in pavucontrol that sound output was going to the nvidia
output.  (It shows a real-time output level bar.)

I ran alsa force-reload.  When I do this the message "Terminating
processes: " appears and instantly at that point, the built in
sound appears in pavucontrol on the configuration tab.  For some reason
though, in this case, even after I selected it, I still got no sound.  I
rebooted again, went straight into my normal environment, confirmed that
only the nvidia card was available, ran 'alsa force-reload', the built-
in sound appears instantly as described above, then there is a many
second delay while alsa loads and messages about loading of sound driver
modules appears.  And then I can play sound, e.g. with aplay.

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  

[Touch-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

If I look at the sound settings using pavucontrol (I don't normally use
gnome and don't seem to have a program called gnome-sound-setting
installed) then under the configuration tab I see the nvidia hardware
but not the built in audio.  (The nvidia card has only HDMI and my
speakers don't have that input, so I can't try using that.  I don't have
any devices with HDMI input.)

After running 'alsa force-reload' the built-in audio appears as a
configuration option.

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 1828474] Re: package sudo 1.8.3p1-1ubuntu3.7 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

[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 sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1828474

Title:
  package sudo 1.8.3p1-1ubuntu3.7 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in sudo package in Ubuntu:
  New

Bug description:
  idk

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: sudo 1.8.3p1-1ubuntu3.7
  ProcVersionSignature: Ubuntu 3.13.0-117.164~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-117-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.15
  AptOrdering:
   sudo: Remove
   sudo-ldap: Install
   sudo-ldap: Configure
  Architecture: amd64
  Date: Wed May  8 22:12:11 2019
  DuplicateSignature: package:sudo:1.8.3p1-1ubuntu3.7:subprocess installed 
pre-removal script returned error exit status 1
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MarkForUpload: True
  SourcePackage: sudo
  Title: package sudo 1.8.3p1-1ubuntu3.7 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to precise on 2019-05-09 (0 days ago)
  VisudoCheck: /etc/sudoers: parsed OK

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

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

[Touch-packages] [Bug 1828474] Re: package sudo 1.8.3p1-1ubuntu3.7 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

[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 sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1828474

Title:
  package sudo 1.8.3p1-1ubuntu3.7 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in sudo package in Ubuntu:
  New

Bug description:
  idk

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: sudo 1.8.3p1-1ubuntu3.7
  ProcVersionSignature: Ubuntu 3.13.0-117.164~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-117-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.15
  AptOrdering:
   sudo: Remove
   sudo-ldap: Install
   sudo-ldap: Configure
  Architecture: amd64
  Date: Wed May  8 22:12:11 2019
  DuplicateSignature: package:sudo:1.8.3p1-1ubuntu3.7:subprocess installed 
pre-removal script returned error exit status 1
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MarkForUpload: True
  SourcePackage: sudo
  Title: package sudo 1.8.3p1-1ubuntu3.7 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to precise on 2019-05-09 (0 days ago)
  VisudoCheck: /etc/sudoers: parsed OK

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

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

[Touch-packages] [Bug 1717352] Re: Locale settings broken after debootstrap installation

[Gunnar Hjalmarsson]

Is this behavior reproducible on 18.04? If it is, can you please explain
what you did to make that "Install Language" show up.

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Incomplete

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

Title:
  Locale settings broken after debootstrap installation

Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  After installing Ubuntu 17.10 through debootstrap (because I
  stubbornly want to use ZFS), locale settings are broken. I've tested
  on a regular installation, where they operate fine.

  When trying to switch to English (United Kingdom), I found out that
  the only option is "English"... a dozen times

  Please see added screenshot for more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.25.92.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm zfs zunicode zavl zcommon znvpair nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 14 22:14:04 2017
  ExecutablePath: /usr/bin/gnome-control-center
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1717352/+subscriptions

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

[Touch-packages] [Bug 1524215] Re: Lenovo B50-70 inverted internal microphone

[Hui Wang]

@Michat,

Could you send your patch to upstream maillist? alsa-devel@alsa-
project.org

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

Title:
  Lenovo B50-70 inverted internal microphone

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978 
  Attached the alsa-info txt to this bug
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marian 1981 F pulseaudio
   /dev/snd/pcmC1D0c:   marian 1981 F...m pulseaudio
   /dev/snd/pcmC1D0p:   marian 1981 F...m pulseaudio
   /dev/snd/controlC1:  marian 1981 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=10570c82-8e52-4379-9a8e-2e30baae9f63
  InstallationDate: Installed on 2015-09-10 (90 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20384
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=1791e4c1-12de-4fef-88b1-31716c981648 ro quiet splash
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: Upgraded to wily on 2015-10-24 (45 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9DCN34WW(V3.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo B50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9DCN34WW(V3.04):bd07/21/2015:svnLENOVO:pn20384:pvrLenovoB50-70:rvnLENOVO:rnLenovoB50-70:rvrNODPK:cvnLENOVO:ct10:cvrLenovoB50-70:
  dmi.product.name: 20384
  dmi.product.version: Lenovo B50-70
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1727470] Re: [RFE] Automatically update the Ubuntu version strings in python-apt

[Adolfo Jayme]

** Changed in: ubuntu-translations
   Status: New => Triaged

** Changed in: ubuntu-translations
   Importance: Undecided => Medium

** Changed in: python-apt (Ubuntu)
   Status: New => Triaged

** Changed in: python-apt (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [RFE] Automatically update the Ubuntu version strings in python-apt

Status in Ubuntu Translations:
  Triaged
Status in python-apt package in Ubuntu:
  Triaged

Bug description:
  Every time there is a new Ubuntu release, some strings need to be
  manually translated although the only thing that is changing is the
  Ubuntu version and code name. Please, consider updating these strings
  automatically based on a translated template. It would help many
  translators.

  These strings are:
  Ubuntu xx.yy 'Code Name'
  Cdrom with Ubuntu xx.yy 'Code Name'

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

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

[Touch-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Hui Wang]

According to the log of ls and aply -l, your audio hardware is
recognized by the driver after booting up.

And alsa is ready to work, I can't find any problem here. I guess you
could run 'aplay test.wav' to play sound after booting up without "sudo
alsa force-reload"

you wrote "After rebooting I have no sound. My sound device doesn't show
up at all in the mixer.", does it mean there is only a dummy output in
the gnome-sound-setting?

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 1766659] Re: pppoeconf should not be in Ubuntu Desktop

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-meta - 1.433

---
ubuntu-meta (1.433) eoan; urgency=medium

  * update.cfg:
- Switch to eoan
  * Refreshed dependencies
  * Added gdm3 to desktop [s390x], desktop-minimal [s390x]
  * Added gnome-initial-setup to desktop-minimal-recommends [s390x],
desktop-recommends [s390x]
  * Removed ppp from desktop-minimal-recommends, desktop-recommends
  * Removed pppconfig from desktop-minimal-recommends, desktop-
recommends
  * Removed pppoeconf from desktop-minimal-recommends, desktop-
recommends.  LP: #1766659.

 -- Steve Langasek   Thu, 09 May 2019
15:53:04 -0700

** Changed in: ubuntu-meta (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  pppoeconf should not be in Ubuntu Desktop

Status in pppoeconf package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  pppoeconf should not be in Ubuntu Desktop

  As network-manager on Ubuntu Desktop configures PPP connection all by
  itself, with ppp recommends and ppp-dev build-depends.

  pppoeconf should not ship in Ubuntu desktop in Bionic, and thus should
  not pull in ifupdown on Ubuntu Desktop.

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

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

[Touch-packages] [Bug 1717983] Re: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration

[Steve Langasek]

Based on https://bugs.launchpad.net/ubuntu/+source/ubuntu-
meta/+bug/1717983/comments/9, marking this done for cloud-init.

** Changed in: cloud-init (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 resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1717983

Title:
  replacement of isc-dhcp-client with with systemd-networkd for dhclient
  needs integration

Status in avahi package in Ubuntu:
  Invalid
Status in cloud-init package in Ubuntu:
  Fix Released
Status in controlaula package in Ubuntu:
  Invalid
Status in ddclient package in Ubuntu:
  Triaged
Status in maas package in Ubuntu:
  Invalid
Status in madwimax package in Ubuntu:
  Triaged
Status in ntp package in Ubuntu:
  Fix Released
Status in openresolv package in Ubuntu:
  Won't Fix
Status in resolvconf package in Ubuntu:
  Won't Fix
Status in samba package in Ubuntu:
  Triaged
Status in sendmail package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Won't Fix

Bug description:
  dhclient has been used as the dhcp client in Ubuntu and debian for
  many years. Over time, many packages have integrated with dhclient.
  The list below is of packages that have declared a dependency and
  those that have shipped hooks to be invoked by dhclient.

  As we move to systemd-networkd these will have to be addressed.

  # ./get-rdeps isc-dhcp-client | sort -u
  breaks - initramfs-tools (initramfs-tools)
  depends - dracut (dracut-network)
  depends - isc-dhcp (isc-dhcp-client-ddns)
  depends - libguestfs (libguestfs0)
  depends - maas (python3-maas-provisioningserver)
  depends - netscript-2.4 (netscript-2.4)
  depends - network-manager (network-manager)
  depends - ubuntu-meta (ubuntu-minimal)
  depends - walinuxagent (walinuxagent)
  depends - whereami (whereami)
  depends - wicd (wicd-daemon)
  depends - wifi-radar (wifi-radar)
  enhances - resolvconf (resolvconf)
  recommends - avahi (avahi-autoipd)
  recommends - ifupdown (ifupdown)
  recommends - ifupdown2 (ifupdown2)
  recommends - madwimax (madwimax)

  $ apt-file search '/etc/dhcp/' | grep 'hooks.d/' | sed 's,:.*,,' | sort -u
  avahi-autoipd
  cloud-init
  controlaula
  ddclient
  isc-dhcp-client
  ntp
  ntpdate
  openresolv
  resolvconf
  samba-common
  sendmail-base
  systemd
  whereami

  Another possible integration point that is not likely listed in the package
  dependencies is reading of the leases file for additional information.
  As an example, Azure advertises the location of its http based metadata
  service as an option in a dhclient response.  cloud-init will read the
  lease files to find the correct address.

  Related bugs:
   * bug 1713803: replacement of resolvconf with systemd needs integration 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: isc-dhcp-client 4.3.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 12:46:31 2017
  DhclientLeases:

  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (788 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1717983] Re: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration

[Steve Langasek]

ubuntu-meta retains a dependency on isc-dhcp-client for use in initramfs
(via initramfs-tools integration), and application which will not be
replaced by networkd for the foreseeable future.

** Changed in: ubuntu-meta (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  replacement of isc-dhcp-client with with systemd-networkd for dhclient
  needs integration

Status in avahi package in Ubuntu:
  Invalid
Status in cloud-init package in Ubuntu:
  Fix Released
Status in controlaula package in Ubuntu:
  Invalid
Status in ddclient package in Ubuntu:
  Triaged
Status in maas package in Ubuntu:
  Invalid
Status in madwimax package in Ubuntu:
  Triaged
Status in ntp package in Ubuntu:
  Fix Released
Status in openresolv package in Ubuntu:
  Won't Fix
Status in resolvconf package in Ubuntu:
  Won't Fix
Status in samba package in Ubuntu:
  Triaged
Status in sendmail package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Won't Fix

Bug description:
  dhclient has been used as the dhcp client in Ubuntu and debian for
  many years. Over time, many packages have integrated with dhclient.
  The list below is of packages that have declared a dependency and
  those that have shipped hooks to be invoked by dhclient.

  As we move to systemd-networkd these will have to be addressed.

  # ./get-rdeps isc-dhcp-client | sort -u
  breaks - initramfs-tools (initramfs-tools)
  depends - dracut (dracut-network)
  depends - isc-dhcp (isc-dhcp-client-ddns)
  depends - libguestfs (libguestfs0)
  depends - maas (python3-maas-provisioningserver)
  depends - netscript-2.4 (netscript-2.4)
  depends - network-manager (network-manager)
  depends - ubuntu-meta (ubuntu-minimal)
  depends - walinuxagent (walinuxagent)
  depends - whereami (whereami)
  depends - wicd (wicd-daemon)
  depends - wifi-radar (wifi-radar)
  enhances - resolvconf (resolvconf)
  recommends - avahi (avahi-autoipd)
  recommends - ifupdown (ifupdown)
  recommends - ifupdown2 (ifupdown2)
  recommends - madwimax (madwimax)

  $ apt-file search '/etc/dhcp/' | grep 'hooks.d/' | sed 's,:.*,,' | sort -u
  avahi-autoipd
  cloud-init
  controlaula
  ddclient
  isc-dhcp-client
  ntp
  ntpdate
  openresolv
  resolvconf
  samba-common
  sendmail-base
  systemd
  whereami

  Another possible integration point that is not likely listed in the package
  dependencies is reading of the leases file for additional information.
  As an example, Azure advertises the location of its http based metadata
  service as an option in a dhclient response.  cloud-init will read the
  lease files to find the correct address.

  Related bugs:
   * bug 1713803: replacement of resolvconf with systemd needs integration 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: isc-dhcp-client 4.3.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 12:46:31 2017
  DhclientLeases:

  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (788 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1451102] Re: upstart user sessions needs replacement

[Steve Langasek]

Resolved in recent releases.

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  upstart user sessions needs replacement

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  While the system init now works much faster, more reliable and
  maintainable the user session is still a mess. Would be great to git
  rid of upstart in here as well or at least document workaround which
  would allow to manually disable upstart for user sessions and replace
  it with systemd units.

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

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

[Touch-packages] [Bug 1550566] Re: ubuntu-minimal should not throw in rsyslog anymore

[Steve Langasek]

Assigning to Dimitri for a sanity check of whether we can drop rsyslog
from ubuntu-minimal without impacting any of our core use cases.

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  ubuntu-minimal should not throw in rsyslog anymore

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  the regular and used log is systemd-journald - and should be. So there
  is no reason for rsyslog in an normal installation. Maybe rsyslog
  should be degraded to a suggest.

  Cheers Alf

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-standard 1.348
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Feb 26 23:52:28 2016
  InstallationDate: Installed on 2016-02-24 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160222.2)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1752417] Re: [ffe] including network-manager-openvpn-gnome, network-manager-l2tp-gnome, and network-manager-strongswan in the default installation

[Steve Langasek]

network-manager-openvpn-gnome is now included by default.  Assigning to
Desktop Team for evaluation of the other packages.

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Ubuntu Desktop (ubuntu-desktop)

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

Title:
  [ffe] including network-manager-openvpn-gnome, network-manager-l2tp-
  gnome, and network-manager-strongswan in the default installation

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager-openvpn package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  network-manager lists only PPTP as an available VPN client connection
  type (and also offers to import a file). I'd expect L2TP-over-IPSec
  and IKEv1/IKEv2 options as well.

  In fact, most major desktop OSes have removed PPTP altogether because
  it's insecure, and Ubuntu should probably do so in 18.04 as well, at
  least from the GUI!

  $ apt list network-manager
  Llistant… Fet
  network-manager/bionic,now 1.10.4-1ubuntu2 amd64 [instal·lat]

  $ uname -a
  Linux machinename 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  Codename: bionic

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

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

[Touch-packages] [Bug 1494540] Re: Add vsdx mimetype

[Steve Langasek]

** Package changed: ubuntu-meta (Ubuntu) => mime-support (Ubuntu)

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

Title:
  Add vsdx mimetype

Status in mime-support package in Ubuntu:
  New

Bug description:
  There is no new visual studio file mimetype support. (vsdx)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1494540/+subscriptions

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

[Touch-packages] [Bug 1526824] Re: boot on uefi directly instead of grub

[Steve Langasek]

This request is inconsistent with the overall design of Ubuntu's boot
handling.

And I disagree with the assertion that this is error-prone.  Use of GRUB
makes Ubuntu boot more error-resistant.

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Won't Fix

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

Title:
  boot on uefi directly instead of grub

Status in ubuntu-meta package in Ubuntu:
  Won't Fix

Bug description:
  Right now even on modern systems with UEFI, Ubuntu is booted via grub2
  bootloader. This is slow, error-prone and completely unnecessary.
  Would be much better and faster to make GNU/Linux kernel bootable
  directly by UEFI firmware. This would also simplify dual-boot setups.

  An example of how to pass kernel command-line parameters is shown in:
  
http://harald.hoyer.xyz/2015/02/25/single-uefi-executable-for-kernelinitrdcmdline/

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

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

[Touch-packages] [Bug 1616742] Re: xdiagnose does nothing in Wayland

[Steve Langasek]

xdiagnose is no longer referenced by the ubuntu-desktop seed in recent
releases.

** Changed in: ubuntu-meta (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  xdiagnose does nothing in Wayland

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in xdiagnose package in Ubuntu:
  Triaged

Bug description:
  What happens
  ===
  1. Try Ubuntu GNOME 16.10 Beta on a computer using open source graphics 
drivers (Intel is recommended).
  2. On the login screen, select your user name. Before entering your password, 
click the gear button and choose "GNOME on Wayland". Enter your password and 
log in.
  3. Try to run xdiagnose.
  4. Nothing happens

  What I expected
  ===
  1. xdiagnose could be adapted to analyze and report issues with Wayland
  2. xdiagnose could explain why it doesn't work on Wayland
  3. Otherwise, it would be nice if xdiagnose wouldn't show up in the 
Activities Overview when Wayland is running but that's more complicated. (Maybe 
XDG_CURRENT_DESKTOP could be expanded to add Wayland as a string and 
xdiagnose.desktop could add NotShowIn=Wayland)

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

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

[Touch-packages] [Bug 1582421] Re: removing upstart breaks user login

[Steve Langasek]

I'm sorry, but you forcibly removed a package which was a *correct*
dependency of the ubuntu-desktop metapackage in Ubuntu 16.04.  The fact
that this resulted in a broken system is not a bug in the ubuntu-meta
package.

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  removing upstart breaks user login

Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  After "apt remove upstart" it's impossible to login into user's
  session via lightdm on xubuntu 16.04 - I thought we've finally ditched
  that junk, how come it still breaks the system on removal?

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

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

[Touch-packages] [Bug 1823550] Re: GtkSourceView (gedit - Text Editor and others) wrongly has monospaced font in dropdown (context) menu

[Martin Wimpress]

** Changed in: mate-themes (Ubuntu)
   Status: Confirmed => Invalid

** Also affects: ubuntu-mate-artwork (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-mate-artwork (Ubuntu)
   Status: New => Triaged

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

Title:
  GtkSourceView (gedit - Text Editor and others) wrongly has monospaced
  font in dropdown (context) menu

Status in GtkSourceView:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in gtksourceview3 package in Ubuntu:
  Invalid
Status in mate-themes package in Ubuntu:
  Invalid
Status in pluma package in Ubuntu:
  Invalid
Status in ubuntu-mate-artwork package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 17.04 or later installed
  2. Open any application with GtkSourceView component - such as Pluma, Gedit, 
Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache 
rdepends libgtksourceview-3.0-1`)
  3. Click right mouse button on text zone

  Expected result:
  * dropdown menu has normal font as all other interface elements

  Actual result:
  * dropdwon menu wrongly has monospaced font

  Notes:
  * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 
releases.
  * seems to be caused by GTK3 library

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pluma 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  7 20:13:24 2019
  InstallationDate: Installed on 2018-08-07 (243 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pluma
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

[Dimitri John Ledkov]

** Changed in: bash (Ubuntu Trusty)
   Status: In Progress => Won't Fix

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

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Trusty:
  Won't Fix
Status in bash source package in Xenial:
  Fix Committed
Status in bash source package in Bionic:
  Fix Committed
Status in bash source package in Cosmic:
  Fix Released
Status in bash source package in Disco:
  Fix Committed
Status in bash source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

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

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

[Touch-packages] [Bug 1717352] Re: Locale settings broken after debootstrap installation

[Steve Langasek]

> Fixed by installing:

> language-pack-en
> language-pack-en-base
> language-pack-gnome-en
> language-pack-gnome-en-base

> I think those packages should be dependencies of ubuntu-desktop.

They should not.  Selection of language packages is part of the
installation process, which you bypassed by manually debootstrapping; we
will not include a dependency on the English langpacks (introducing
overhead for all non-English users) to work around this.

Marking invalid for ubuntu-meta.

It sounds like there is still a bug in how the language options are
being displayed in the UI however, so the gnome task remains open.

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Invalid

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

Title:
  Locale settings broken after debootstrap installation

Status in gnome-control-center package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  After installing Ubuntu 17.10 through debootstrap (because I
  stubbornly want to use ZFS), locale settings are broken. I've tested
  on a regular installation, where they operate fine.

  When trying to switch to English (United Kingdom), I found out that
  the only option is "English"... a dozen times

  Please see added screenshot for more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.25.92.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm zfs zunicode zavl zcommon znvpair nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 14 22:14:04 2017
  ExecutablePath: /usr/bin/gnome-control-center
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1717352/+subscriptions

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

[Touch-packages] [Bug 1671395] Re: Danish translation missing in ISO files

[Steve Langasek]

Sorry, but the languages included on the ISO are prioritized by number
of world speakers; and of course, Danish is rather far down that list.
All languages are available for installation from the network as part of
the install process.

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Danish translation missing in ISO files

Status in ubuntu-meta package in Ubuntu:
  Won't Fix

Bug description:
  I would like to be able to test Ubuntu live with danish translation
  but danish translation does not seem to be included in the ISO files
  (like ubuntu-16.10-desktop-amd64.iso).

  So i would like danish translation to be included for Unity and all
  the other software that comes with Ubuntu by default, so that users
  can try Ubuntu live with danish translation without having to download
  danish translation, switching to danish and logging out and in again
  in order to use it.

  Also i would like to know where i can see which languages are included
  in the ISO files.

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

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

[Touch-packages] [Bug 1748956] Re: replace uses of net-tools with iproute2

[Steve Langasek]

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Canonical Server Team (canonical-server)

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

Title:
  replace uses of net-tools with iproute2

Status in byobu:
  Fix Committed
Status in byobu package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  As ubuntu goes forward, net-tools is looking to be dropped.

  Byobu currently depends on net-tools.  That code should be replaced by
  iproute2.

  
  Related bugs:
   * bug 925145: cloud-init  Use ip instead of ifconfig and route

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: byobu 5.124-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 12 13:34:27 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (935 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: byobu
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1766659] Re: pppoeconf should not be in Ubuntu Desktop

[Steve Langasek]

** Changed in: ubuntu-meta (Ubuntu)
   Importance: Critical => Medium

** Changed in: ubuntu-meta (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  pppoeconf should not be in Ubuntu Desktop

Status in pppoeconf package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Committed

Bug description:
  pppoeconf should not be in Ubuntu Desktop

  As network-manager on Ubuntu Desktop configures PPP connection all by
  itself, with ppp recommends and ppp-dev build-depends.

  pppoeconf should not ship in Ubuntu desktop in Bionic, and thus should
  not pull in ifupdown on Ubuntu Desktop.

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

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

[Touch-packages] [Bug 1734794] Re: Install of ubuntu-desktop login loop

[Steve Langasek]

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Ubuntu Desktop (ubuntu-desktop)

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

Title:
  Install of ubuntu-desktop login loop

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Tested on clean VM. To repro install ubuntu-17.10 server edition

  > sudo apt update
  > sudo apt upgrade
  > sudo apt install ubuntu-desktop --no-install-recommends
  > sudo reboot
  # Reboots to graphical login screen. After entering username password returns 
to graphical login for both Ubuntu and Ubuntu on Xorg
  # Switch to tty2
  > sudo apt install gsettings-ubuntu-schemas
  # Switch to tty1
  # Login now works

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Mon Nov 27 19:50:24 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2017-11-28 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-17-generic 
root=UUID=3fb3b989-6bd0-43f4-a49e-04af4ecac2f2 ro rootflags=subvol=@
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  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/ubuntu-meta/+bug/1734794/+subscriptions

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

[Touch-packages] [Bug 1736371] Re: Feature Request: Syncthing integration

[Steve Langasek]

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Ubuntu Desktop (ubuntu-desktop)

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

Title:
  Feature Request: Syncthing integration

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  since the removal of Ubuntu One filehosting, a nice, well-integrated
  filesync in Ubuntu desktop is missing. It would be a welcome addition
  to have filesync back as an out-of-the box feature.

  Syncthing is a proven open-source p2p filesync software. The software
  has a track record of many years under active development, the
  developer community is alive and well. It seems to be stable and the
  architecture seems sound. (I cannot comment on its security
  implications, though.)

  Syncthing is server-less, it doesn't require a central/cloud server.
  The usability leaves a lot to be desired and the current installation
  and end-user experience is poor for a novice user.

  The most successful part of Ubuntu desktop's mission has always been
  making complicated Linux software easier to use for novice end-users.

  Therefore my request is that Ubuntu considers spending development
  resources on improving the user experience of Syncthing.

  - Make Syncthing a part of a default Ubuntu desktop installation.
  - Design a better end-user interface for remote sync device management.
  - Design a better end-user interface for seamless filemanager integration.
  - Add a possible, optional encrypted cloud storage sync service.

  Thanks.

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

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

[Touch-packages] [Bug 1753894] Re: Bionic LiveCD: Boot time is very slow

[Steve Langasek]

Work was indeed done on this issue prior to bionic release, so I think
this should be considered resolved now.

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Fix Released

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

Title:
  Bionic LiveCD: Boot time is very slow

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  I'm not sure what package to report this against.

  The Ubuntu Bionic LiveCD boots VERY slowly compared to previous
  LiveCDs (Trusty, Xenial, etc.)

  I read this is being worked on (see: https://community.ubuntu.com/t
  /desktop-newsletter-19th-jan-2018/3524 "General" section), but I
  wanted to file this bug just to formally report the problem.

  Boot time on my machine is over 3 minutes, feels more live 5 or 6
  minutes. That's much higher than other distros I test, like Linux
  Mint, or Ubuntu Mate 16.04, Xubuntu 17.10, pretty much anything other
  than the main Bionic daily ISO boots a lot faster.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: plymouth 0.9.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.389
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  7 04:00:32 2018
  DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  MachineType: Acer AO722
  ProcCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash ---
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash ---
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE10-BZ
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.08
  dmi.modalias: 
dmi:bvnAcer:bvrV1.08:bd12/06/2011:svnAcer:pnAO722:pvrV1.08:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.08:
  dmi.product.family: Type1Family
  dmi.product.name: AO722
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1749774] Re: include fwupd packages in Server Seed

[Steve Langasek]

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Canonical Server Team (canonical-server)

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

Title:
  include fwupd packages in Server Seed

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  fwupd is the closest we have to a standard mechanism currently for
  doing in-band firmware updates in a vendor agnostic way.  As long as
  the vendors provide firmware blobs in an appropriately formatted
  package, fwupd (or fwupdate) can install those firmware blobs from
  within Ubuntu.

  Because of this, we should include the related packages in the server
  seed.  The main components all live in Main currently.  As far as I
  can tell (verified on a Bionic install), nothing in the current server
  seed pulls in fwupd, fwupdate, or fwupdate-signed as a dependency.

  ubuntu@xwing:~$ apt-cache policy fwup*

  fwupdate:
Installed: (none)
Candidate: 10-2
Version table:
   10-2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  fwupd:
Installed: (none)
Candidate: 1.0.4-3build1
Version table:
   1.0.4-3build1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  fwupdate-signed:
Installed: (none)
Candidate: 1.17+10-2
Version table:
   1.17+10-2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

[Touch-packages] [Bug 1740161] Re: Update supported-misc-servers for postgresql

[Steve Langasek]

These are replaced with the -10 equivalents now.

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Fix Released

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

Title:
  Update supported-misc-servers for postgresql

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  At the top of platform.bionic supported-misc-servers is

  Database:

   * postgresql-plperl-9.5
   * postgresql-plpython-9.5
   * postgresql-plpython3-9.5
   * postgresql-pltcl-9.5

  Please check whether those lines are still necessary. If so, please
  update them (postgresql-10 is current) and maybe converted them to
  wildcards.

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

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

[Touch-packages] [Bug 1727088] Re: No indicator icons for qt apps

[Steve Langasek]

Thank you for reporting this problem.  Ubuntu 17.10 is no longer
supported, and I believe this issue is resolved in later releases by
virtue of indicators no longer being used as the standard interface on
the Ubuntu desktop.  If you still see problems, please reopen this bug.

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Fix Released

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

Title:
  No indicator icons for qt apps

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  On a freshly installed ubuntu 17.10 the indicator/topicons will not
  show up for qt apps, like mumble.

  This is fixed by installing the sni-qt package.

  Since it's not common knowledge to install that package manually,
  maybe it should be installed by default on the 18.04 release to have
  more applications working out of the box with the indicators/topicons?

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

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

[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

[Dimitri John Ledkov]

(xenial-amd64)root@ottawa:~# env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
(xenial-amd64)root@ottawa:~# dpkg-query -W bash
bash4.3-14ubuntu1.3

Xenial looks good.

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

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

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Trusty:
  In Progress
Status in bash source package in Xenial:
  Fix Committed
Status in bash source package in Bionic:
  Fix Committed
Status in bash source package in Cosmic:
  Fix Released
Status in bash source package in Disco:
  Fix Committed
Status in bash source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

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

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

[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

[Dimitri John Ledkov]

(bionic-amd64)root@ottawa:~# env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
(bionic-amd64)root@ottawa:~# dpkg-query -W bash
bash4.4.18-2ubuntu1.1

Bionic looks good.

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

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

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Trusty:
  In Progress
Status in bash source package in Xenial:
  Fix Committed
Status in bash source package in Bionic:
  Fix Committed
Status in bash source package in Cosmic:
  Fix Released
Status in bash source package in Disco:
  Fix Committed
Status in bash source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

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

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

[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

[Dimitri John Ledkov]

(disco-amd64)root@ottawa:~# env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
(disco-amd64)root@ottawa:~# dpkg-query -W bash
bash5.0-3ubuntu1.1


Disco looks good.

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

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

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Trusty:
  In Progress
Status in bash source package in Xenial:
  Fix Committed
Status in bash source package in Bionic:
  Fix Committed
Status in bash source package in Cosmic:
  Fix Released
Status in bash source package in Disco:
  Fix Committed
Status in bash source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

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

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

[Touch-packages] [Bug 1766659] Re: pppoeconf should not be in Ubuntu Desktop

[Steve Langasek]

This did not get acked in time for bionic but still needs doing on eoan;
merging now.

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

Title:
  pppoeconf should not be in Ubuntu Desktop

Status in pppoeconf package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Committed

Bug description:
  pppoeconf should not be in Ubuntu Desktop

  As network-manager on Ubuntu Desktop configures PPP connection all by
  itself, with ppp recommends and ppp-dev build-depends.

  pppoeconf should not ship in Ubuntu desktop in Bionic, and thus should
  not pull in ifupdown on Ubuntu Desktop.

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

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

[Touch-packages] [Bug 1798457] Re: Provide curtin-requirements and server-ship-live seeds

[Steve Langasek]

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Fix Released

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

Title:
  Provide curtin-requirements and server-ship-live seeds

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Provide curtin-requirements and server-ship-live seeds

  and make cdimage use them for server live images.

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

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

[Touch-packages] [Bug 1792004] Re: built-in PATH seems to have sbin and bin out of order; and inconsistent

[Dimitri John Ledkov]

(xenial-amd64)root@ottawa:~# env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
(xenial-amd64)root@ottawa:~# dpkg-query -W bash
bash4.3-14ubuntu1.3

Xenial looks good.

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

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

Title:
  built-in PATH seems to have sbin and bin out of order; and
  inconsistent

Status in apt package in Ubuntu:
  Fix Released
Status in bash package in Ubuntu:
  Fix Released
Status in busybox package in Ubuntu:
  New
Status in dash package in Ubuntu:
  New
Status in dpkg package in Ubuntu:
  Won't Fix
Status in pam package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in bash source package in Xenial:
  Fix Committed
Status in bash source package in Bionic:
  Fix Committed
Status in bash source package in Disco:
  Fix Committed
Status in bash package in Debian:
  New

Bug description:
  [Impact]

   * For consistency reasons sbin should be ordered before bin in PATH.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  And check that matching pairs in PATH, have /sbin variant leading /bin
  variant.

  [Regression Potential]

   * Ubuntu does not ship duplicate binries, with different behaviour
  between /sbin and /bin, thus all binaries will continue to be found in
  all locations. Also PATH is normally already set in the environment,
  and this change only affects the fallback path when bash is executed
  without any environment, i.e. booting with 'init=/bin/bash'

  [Other Info]
   
   * Original bug report detailing inconsistent paths between various shells.

  ---

  
  $ env -u PATH /bin/sh -c 'echo $PATH'
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ env -u PATH /bin/dash -c 'echo $PATH'
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ systemd-run --unit test-env env # ... and check journal for PATH
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ env -u PATH /bin/bash -c 'echo $PATH'
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  $ env -u PATH /bin/busybox sh -c 'echo $PATH'
  /sbin:/usr/sbin:/bin:/usr/bin

  $ grep 'export PATH=' -r initramfs-tools-0.131ubuntu10/
  initramfs-tools-0.131ubuntu10/mkinitramfs:export PATH='/usr/bin:/sbin:/bin'
  initramfs-tools-0.131ubuntu10/init:export PATH=/sbin:/usr/sbin:/bin:/usr/bin

  dracut.sh has DRACUT_PATH=${DRACUT_PATH:-/sbin /bin /usr/sbin /usr/bin} 
exported as PATH
  dracut-047+31/modules.d/99shutdown/shutdown.sh:export 
PATH=/usr/sbin:/usr/bin:/sbin:/bin

  $ cat /etc/environment
  
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"

  apt & dpkg => should probably initiate /usr/local-less PATH

  Imho the rest should probably be harmonised to:

  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin

  ===

  From a duplicate
  https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080 :

  $ for i in 12.04 12.10 13.04 13.10 14.04 14.10 15.04 15.10 16.04; do echo $i; 
docker run -it --rm ubuntu:$i bash -c "unset PATH; /bin/bash -c 'echo \$PATH'"; 
done
  12.04
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  12.10
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  13.04
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  13.10
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  14.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  14.10
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  15.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  15.10
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  16.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  I believe later releases of bash, do too include CWD in the built-in
  PATH.

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

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

[Touch-packages] [Bug 1792004] Re: built-in PATH seems to have sbin and bin out of order; and inconsistent

[Dimitri John Ledkov]

(disco-amd64)root@ottawa:~# env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
(disco-amd64)root@ottawa:~# dpkg-query -W bash
bash5.0-3ubuntu1.1


Disco looks good.

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

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

Title:
  built-in PATH seems to have sbin and bin out of order; and
  inconsistent

Status in apt package in Ubuntu:
  Fix Released
Status in bash package in Ubuntu:
  Fix Released
Status in busybox package in Ubuntu:
  New
Status in dash package in Ubuntu:
  New
Status in dpkg package in Ubuntu:
  Won't Fix
Status in pam package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in bash source package in Xenial:
  Fix Committed
Status in bash source package in Bionic:
  Fix Committed
Status in bash source package in Disco:
  Fix Committed
Status in bash package in Debian:
  New

Bug description:
  [Impact]

   * For consistency reasons sbin should be ordered before bin in PATH.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  And check that matching pairs in PATH, have /sbin variant leading /bin
  variant.

  [Regression Potential]

   * Ubuntu does not ship duplicate binries, with different behaviour
  between /sbin and /bin, thus all binaries will continue to be found in
  all locations. Also PATH is normally already set in the environment,
  and this change only affects the fallback path when bash is executed
  without any environment, i.e. booting with 'init=/bin/bash'

  [Other Info]
   
   * Original bug report detailing inconsistent paths between various shells.

  ---

  
  $ env -u PATH /bin/sh -c 'echo $PATH'
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ env -u PATH /bin/dash -c 'echo $PATH'
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ systemd-run --unit test-env env # ... and check journal for PATH
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ env -u PATH /bin/bash -c 'echo $PATH'
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  $ env -u PATH /bin/busybox sh -c 'echo $PATH'
  /sbin:/usr/sbin:/bin:/usr/bin

  $ grep 'export PATH=' -r initramfs-tools-0.131ubuntu10/
  initramfs-tools-0.131ubuntu10/mkinitramfs:export PATH='/usr/bin:/sbin:/bin'
  initramfs-tools-0.131ubuntu10/init:export PATH=/sbin:/usr/sbin:/bin:/usr/bin

  dracut.sh has DRACUT_PATH=${DRACUT_PATH:-/sbin /bin /usr/sbin /usr/bin} 
exported as PATH
  dracut-047+31/modules.d/99shutdown/shutdown.sh:export 
PATH=/usr/sbin:/usr/bin:/sbin:/bin

  $ cat /etc/environment
  
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"

  apt & dpkg => should probably initiate /usr/local-less PATH

  Imho the rest should probably be harmonised to:

  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin

  ===

  From a duplicate
  https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080 :

  $ for i in 12.04 12.10 13.04 13.10 14.04 14.10 15.04 15.10 16.04; do echo $i; 
docker run -it --rm ubuntu:$i bash -c "unset PATH; /bin/bash -c 'echo \$PATH'"; 
done
  12.04
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  12.10
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  13.04
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  13.10
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  14.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  14.10
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  15.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  15.10
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  16.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  I believe later releases of bash, do too include CWD in the built-in
  PATH.

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

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

[Touch-packages] [Bug 1816024] Re: ubuntu-desktop should not hard depend on update-notifier (make it a recommended dep instead)

[Steve Langasek]

update-notifier is part of the designed experience of the Ubuntu Desktop
and it should not be necessary to remove it to address the issues you've
identified.  Reassigning to update-notifier.

** Package changed: ubuntu-meta (Ubuntu) => update-notifier (Ubuntu)

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

Title:
  ubuntu-desktop should not hard depend on update-notifier (make it a
  recommended dep instead)

Status in update-notifier package in Ubuntu:
  Confirmed

Bug description:
  The package `ubuntu-desktop` hard depends on `update-notifier` which
  is not good. It would be much better if it were a recommended
  dependency.

  Namely, the problem I initially wanted to report was with `update-
  notifier` not being configurable enough so it shows itself when you
  run apt manually on the command line. Pretty sure there's plenty of
  legitimate scenarios where desktops would be managed from command
  line. Think fleets of desktops in an office managed with SaltStack.
  Think scheduling updates to specific periods of time, outside of which
  you do not want to be nagged, even on single computers. And disabling
  updates from the Ubuntu Software app does not prevent the nagging when
  you operate `apt` manually. Neither does dconf-editor's com.ubuntu
  .update-notifier.no-show-notifications.

  Anyway, removing `update-notifier` solved the problem and then I
  realized that indeed, on machines where you do not want GUI for
  updates, you simply remove the package.

  And so this report is made. Please make it a recommended, not a hard
  dep of the desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1816024/+subscriptions

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

[Touch-packages] [Bug 1792004] Re: built-in PATH seems to have sbin and bin out of order; and inconsistent

[Dimitri John Ledkov]

(bionic-amd64)root@ottawa:~# env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
(bionic-amd64)root@ottawa:~# dpkg-query -W bash
bash4.4.18-2ubuntu1.1

Bionic looks good.

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

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

Title:
  built-in PATH seems to have sbin and bin out of order; and
  inconsistent

Status in apt package in Ubuntu:
  Fix Released
Status in bash package in Ubuntu:
  Fix Released
Status in busybox package in Ubuntu:
  New
Status in dash package in Ubuntu:
  New
Status in dpkg package in Ubuntu:
  Won't Fix
Status in pam package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in bash source package in Xenial:
  Fix Committed
Status in bash source package in Bionic:
  Fix Committed
Status in bash source package in Disco:
  Fix Committed
Status in bash package in Debian:
  New

Bug description:
  [Impact]

   * For consistency reasons sbin should be ordered before bin in PATH.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  And check that matching pairs in PATH, have /sbin variant leading /bin
  variant.

  [Regression Potential]

   * Ubuntu does not ship duplicate binries, with different behaviour
  between /sbin and /bin, thus all binaries will continue to be found in
  all locations. Also PATH is normally already set in the environment,
  and this change only affects the fallback path when bash is executed
  without any environment, i.e. booting with 'init=/bin/bash'

  [Other Info]
   
   * Original bug report detailing inconsistent paths between various shells.

  ---

  
  $ env -u PATH /bin/sh -c 'echo $PATH'
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ env -u PATH /bin/dash -c 'echo $PATH'
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ systemd-run --unit test-env env # ... and check journal for PATH
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ env -u PATH /bin/bash -c 'echo $PATH'
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  $ env -u PATH /bin/busybox sh -c 'echo $PATH'
  /sbin:/usr/sbin:/bin:/usr/bin

  $ grep 'export PATH=' -r initramfs-tools-0.131ubuntu10/
  initramfs-tools-0.131ubuntu10/mkinitramfs:export PATH='/usr/bin:/sbin:/bin'
  initramfs-tools-0.131ubuntu10/init:export PATH=/sbin:/usr/sbin:/bin:/usr/bin

  dracut.sh has DRACUT_PATH=${DRACUT_PATH:-/sbin /bin /usr/sbin /usr/bin} 
exported as PATH
  dracut-047+31/modules.d/99shutdown/shutdown.sh:export 
PATH=/usr/sbin:/usr/bin:/sbin:/bin

  $ cat /etc/environment
  
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"

  apt & dpkg => should probably initiate /usr/local-less PATH

  Imho the rest should probably be harmonised to:

  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin

  ===

  From a duplicate
  https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080 :

  $ for i in 12.04 12.10 13.04 13.10 14.04 14.10 15.04 15.10 16.04; do echo $i; 
docker run -it --rm ubuntu:$i bash -c "unset PATH; /bin/bash -c 'echo \$PATH'"; 
done
  12.04
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  12.10
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  13.04
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  13.10
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  14.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  14.10
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  15.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  15.10
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  16.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  I believe later releases of bash, do too include CWD in the built-in
  PATH.

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

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

[Touch-packages] [Bug 1816288] Re: netboot/mini.iso should allow Ubuntu Minimal desktop Installation

[Steve Langasek]

The mini iso is not guaranteed to offer the complete set of features
provided by the desktop installer.

** Package changed: ubuntu-meta (Ubuntu) => debian-installer (Ubuntu)

** Changed in: debian-installer (Ubuntu)
   Status: New => Won't Fix

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

Title:
  netboot/mini.iso should allow Ubuntu Minimal desktop Installation

Status in debian-installer package in Ubuntu:
  Won't Fix
Status in tasksel package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Download netboot/mini.iso for Ubuntu 18.04 LTS ( 
http://cdimage.ubuntu.com/netboot/bionic/ )
  2. Launch installer.
  3. Wait for "Software selection" to be shown

  Expected results:
  user is able to select Ubuntu minimal desktop

  Actual results:
  user is unable to select Ubuntu minimal desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: tasksel 3.34ubuntu11
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 17 13:10:05 2019
  InstallationDate: Installed on 2019-02-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: tasksel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Adrian Mariano]

Summary: looks to me like aplay -l is showing the intel hardware.  No

adrian> ls -la /dev/snd
total 0
0 drwxr-xr-x   3 root root  320 May  9 18:07 ./
0 drwxr-xr-x  20 root root 5080 May  9 18:07 ../
0 drwxr-xr-x   2 root root   80 May  9 18:07 by-path/
0 crw-rw+  1 root audio 116,  7 May  9 18:07 controlC0
0 crw-rw+  1 root audio 116, 12 May  9 18:07 controlC1
0 crw-rw+  1 root audio 116,  6 May  9 18:07 hwC0D0
0 crw-rw+  1 root audio 116, 11 May  9 18:07 hwC1D0
0 crw-rw+  1 root audio 116,  3 May  9 18:07 pcmC0D0c
0 crw-rw+  1 root audio 116,  2 May  9 18:07 pcmC0D0p
0 crw-rw+  1 root audio 116,  4 May  9 18:07 pcmC0D1p
0 crw-rw+  1 root audio 116,  5 May  9 18:07 pcmC0D2c
0 crw-rw+  1 root audio 116,  8 May  9 18:13 pcmC1D3p
0 crw-rw+  1 root audio 116,  9 May  9 18:13 pcmC1D7p
0 crw-rw+  1 root audio 116, 10 May  9 18:13 pcmC1D8p
0 crw-rw+  1 root audio 116,  1 May  9 18:07 seq
0 crw-rw+  1 root audio 116, 33 May  9 18:07 timer
adrian> aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
adrian> sudo chmod a+rw /dev/snd/*
[sudo] password for adrian: 
adrian> aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
adrian> ls -la /dev/snd
total 0
0 drwxr-xr-x   3 root root  320 May  9 18:07 ./
0 drwxr-xr-x  20 root root 5080 May  9 18:07 ../
0 drwxrwxrwx   2 root root   80 May  9 18:07 by-path/
0 crw-rw-rw-+  1 root audio 116,  7 May  9 18:07 controlC0
0 crw-rw-rw-+  1 root audio 116, 12 May  9 18:07 controlC1
0 crw-rw-rw-+  1 root audio 116,  6 May  9 18:07 hwC0D0
0 crw-rw-rw-+  1 root audio 116, 11 May  9 18:07 hwC1D0
0 crw-rw-rw-+  1 root audio 116,  3 May  9 18:15 pcmC0D0c
0 crw-rw-rw-+  1 root audio 116,  2 May  9 18:15 pcmC0D0p
0 crw-rw-rw-+  1 root audio 116,  4 May  9 18:15 pcmC0D1p
0 crw-rw-rw-+  1 root audio 116,  5 May  9 18:07 pcmC0D2c
0 crw-rw-rw-+  1 root audio 116,  8 May  9 18:15 pcmC1D3p
0 crw-rw-rw-+  1 root audio 116,  9 May  9 18:15 pcmC1D7p
0 crw-rw-rw-+  1 root audio 116, 10 May  9 18:15 pcmC1D8p
0 crw-rw+  1 root audio 116,  1 May  9 18:15 seq
0 crw-rw-rw-+  1 root audio 116, 33 May  9 18:07 timer

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 

[Touch-packages] [Bug 1796193] Re: unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

[Brian Murray]

I tested an upgrade from xenial to bionic today and did not receive a
conffile prompt regarding /etc/cron.daily/apt-compat and part of the
output you've pasted leads me to believe the file did not exist on the
system which you were upgrading. Have you run into this any more?

Additionally, I've sorted out the issue in ubuntu-release-upgrader for
Eoan. If you want it SRU'ed let us know.

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

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

Title:
  unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

Status in apt package in Ubuntu:
  Incomplete
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in apt source package in Eoan:
  Incomplete
Status in ubuntu-release-upgrader source package in Eoan:
  In Progress

Bug description:
  I'm trying to do some automated testing that involved upgrading a
  system from xenial to bionic, so I need it to not ask for user input.

  Before running do-release-upgrade, the system got a fresh dist-upgrade
  and reboot.

  To avoid interactive responses, I'm using:
  $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive

  Part way through the upgrade, I do get prompted for something though:
  Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ...

  Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ...

  Processing triggers for libc-bin (2.27-3ubuntu1) ...

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file
  or directory

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or
  directory

  Setting up apt (1.6.3ubuntu0.1) ...

  Installing new version of config file /etc/apt/apt.conf.d/01autoremove
  ...


  Configuration file '/etc/cron.daily/apt-compat'

   ==> Deleted (by you or by a script) since installation.

   ==> Package distributor has shipped an updated version.

 What would you like to do about it ?  Your options are:

  Y or I  : install the package maintainer's version

  N or O  : keep your currently-installed version

D : show the differences between the versions

Z : start a shell to examine the situation

   The default action is to keep your current version.

  Comparing the sha1 of apt-compat before the upgrade to another xenial
  system that has been unmodified, they are the same:

  In /var/log/dist-upgrade/main.log, I also found this:
  2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: 
'/etc/cron.daily/apt-compat'
  2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 
'str'' when trying to write to the conffile

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

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

[Touch-packages] [Bug 1777512] Re: key retrieval timeouts cause failures

[Jason Hobbs]

** Tags added: cpe-onsite

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

Title:
  key retrieval timeouts cause failures

Status in CDO QA System Tests:
  Confirmed
Status in software-properties package in Ubuntu:
  New

Bug description:
  We have been seeing keyserver timeouts causing failed runs at an
  increased rate recently (over the last 6+ months). Here is an example
  failure:

  [10.244.40.32] sudo: add-apt-repository -k https://keyserver.ubuntu.com/ 
--yes "ppa:curtin-dev/proposed"
  [10.244.40.32] out: Error: retrieving gpg key timed out.

  One idea is that this needs to be addressed by making the client
  (software-properties) more robust.

  
  We have an RT about this:
  https://portal.admin.canonical.com/C112309/

To manage notifications about this bug go to:
https://bugs.launchpad.net/cdoqa-system-tests/+bug/1777512/+subscriptions

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

[Touch-packages] [Bug 1796193] Re: unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu-release-upgrader

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

Title:
  unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

Status in apt package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in apt source package in Eoan:
  Confirmed
Status in ubuntu-release-upgrader source package in Eoan:
  In Progress

Bug description:
  I'm trying to do some automated testing that involved upgrading a
  system from xenial to bionic, so I need it to not ask for user input.

  Before running do-release-upgrade, the system got a fresh dist-upgrade
  and reboot.

  To avoid interactive responses, I'm using:
  $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive

  Part way through the upgrade, I do get prompted for something though:
  Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ...

  Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ...

  Processing triggers for libc-bin (2.27-3ubuntu1) ...

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file
  or directory

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or
  directory

  Setting up apt (1.6.3ubuntu0.1) ...

  Installing new version of config file /etc/apt/apt.conf.d/01autoremove
  ...


  Configuration file '/etc/cron.daily/apt-compat'

   ==> Deleted (by you or by a script) since installation.

   ==> Package distributor has shipped an updated version.

 What would you like to do about it ?  Your options are:

  Y or I  : install the package maintainer's version

  N or O  : keep your currently-installed version

D : show the differences between the versions

Z : start a shell to examine the situation

   The default action is to keep your current version.

  Comparing the sha1 of apt-compat before the upgrade to another xenial
  system that has been unmodified, they are the same:

  In /var/log/dist-upgrade/main.log, I also found this:
  2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: 
'/etc/cron.daily/apt-compat'
  2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 
'str'' when trying to write to the conffile

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

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

[Touch-packages] [Bug 1796193] Re: unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

[Brian Murray]

** Tags removed: rls-ee-incoming

** Also affects: apt (Ubuntu Eoan)
   Importance: Medium
   Status: Confirmed

** Also affects: ubuntu-release-upgrader (Ubuntu Eoan)
   Importance: Medium
 Assignee: Brian Murray (brian-murray)
   Status: In Progress

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

Title:
  unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

Status in apt package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in apt source package in Eoan:
  Confirmed
Status in ubuntu-release-upgrader source package in Eoan:
  In Progress

Bug description:
  I'm trying to do some automated testing that involved upgrading a
  system from xenial to bionic, so I need it to not ask for user input.

  Before running do-release-upgrade, the system got a fresh dist-upgrade
  and reboot.

  To avoid interactive responses, I'm using:
  $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive

  Part way through the upgrade, I do get prompted for something though:
  Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ...

  Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ...

  Processing triggers for libc-bin (2.27-3ubuntu1) ...

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file
  or directory

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or
  directory

  Setting up apt (1.6.3ubuntu0.1) ...

  Installing new version of config file /etc/apt/apt.conf.d/01autoremove
  ...


  Configuration file '/etc/cron.daily/apt-compat'

   ==> Deleted (by you or by a script) since installation.

   ==> Package distributor has shipped an updated version.

 What would you like to do about it ?  Your options are:

  Y or I  : install the package maintainer's version

  N or O  : keep your currently-installed version

D : show the differences between the versions

Z : start a shell to examine the situation

   The default action is to keep your current version.

  Comparing the sha1 of apt-compat before the upgrade to another xenial
  system that has been unmodified, they are the same:

  In /var/log/dist-upgrade/main.log, I also found this:
  2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: 
'/etc/cron.daily/apt-compat'
  2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 
'str'' when trying to write to the conffile

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

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

[Touch-packages] [Bug 1796193] Re: unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

[Brian Murray]

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Triaged => In Progress

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

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

Title:
  unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

Status in apt package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress

Bug description:
  I'm trying to do some automated testing that involved upgrading a
  system from xenial to bionic, so I need it to not ask for user input.

  Before running do-release-upgrade, the system got a fresh dist-upgrade
  and reboot.

  To avoid interactive responses, I'm using:
  $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive

  Part way through the upgrade, I do get prompted for something though:
  Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ...

  Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ...

  Processing triggers for libc-bin (2.27-3ubuntu1) ...

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file
  or directory

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or
  directory

  Setting up apt (1.6.3ubuntu0.1) ...

  Installing new version of config file /etc/apt/apt.conf.d/01autoremove
  ...


  Configuration file '/etc/cron.daily/apt-compat'

   ==> Deleted (by you or by a script) since installation.

   ==> Package distributor has shipped an updated version.

 What would you like to do about it ?  Your options are:

  Y or I  : install the package maintainer's version

  N or O  : keep your currently-installed version

D : show the differences between the versions

Z : start a shell to examine the situation

   The default action is to keep your current version.

  Comparing the sha1 of apt-compat before the upgrade to another xenial
  system that has been unmodified, they are the same:

  In /var/log/dist-upgrade/main.log, I also found this:
  2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: 
'/etc/cron.daily/apt-compat'
  2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 
'str'' when trying to write to the conffile

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

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

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

[Adam Conrad]

Hello Dimitri, or anyone else affected,

Accepted bash into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bash/4.3-14ubuntu1.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 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1792004

Title:
  built-in PATH seems to have sbin and bin out of order; and
  inconsistent

Status in apt package in Ubuntu:
  Fix Released
Status in bash package in Ubuntu:
  Fix Released
Status in busybox package in Ubuntu:
  New
Status in dash package in Ubuntu:
  New
Status in dpkg package in Ubuntu:
  Won't Fix
Status in pam package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in bash source package in Xenial:
  Fix Committed
Status in bash source package in Bionic:
  Fix Committed
Status in bash source package in Disco:
  Fix Committed
Status in bash package in Debian:
  New

Bug description:
  [Impact]

   * For consistency reasons sbin should be ordered before bin in PATH.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  And check that matching pairs in PATH, have /sbin variant leading /bin
  variant.

  [Regression Potential]

   * Ubuntu does not ship duplicate binries, with different behaviour
  between /sbin and /bin, thus all binaries will continue to be found in
  all locations. Also PATH is normally already set in the environment,
  and this change only affects the fallback path when bash is executed
  without any environment, i.e. booting with 'init=/bin/bash'

  [Other Info]
   
   * Original bug report detailing inconsistent paths between various shells.

  ---

  
  $ env -u PATH /bin/sh -c 'echo $PATH'
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ env -u PATH /bin/dash -c 'echo $PATH'
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ systemd-run --unit test-env env # ... and check journal for PATH
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ env -u PATH /bin/bash -c 'echo $PATH'
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  $ env -u PATH /bin/busybox sh -c 'echo $PATH'
  /sbin:/usr/sbin:/bin:/usr/bin

  $ grep 'export PATH=' -r initramfs-tools-0.131ubuntu10/
  initramfs-tools-0.131ubuntu10/mkinitramfs:export PATH='/usr/bin:/sbin:/bin'
  initramfs-tools-0.131ubuntu10/init:export PATH=/sbin:/usr/sbin:/bin:/usr/bin

  dracut.sh has DRACUT_PATH=${DRACUT_PATH:-/sbin /bin /usr/sbin /usr/bin} 
exported as PATH
  dracut-047+31/modules.d/99shutdown/shutdown.sh:export 
PATH=/usr/sbin:/usr/bin:/sbin:/bin

  $ cat /etc/environment
  
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"

  apt & dpkg => should probably initiate /usr/local-less PATH

  Imho the rest should probably be harmonised to:

  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin

  ===

  From a duplicate
  https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080 :

  $ for i in 12.04 12.10 13.04 13.10 14.04 14.10 15.04 15.10 16.04; do echo $i; 
docker run -it --rm ubuntu:$i bash -c "unset PATH; /bin/bash -c 'echo \$PATH'"; 
done
  12.04
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  12.10
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  13.04
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  13.10
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  14.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  14.10
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  15.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  15.10
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  16.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  I believe later releases of bash, do too include CWD in the built-in
  PATH.

To manage notifications about this bug go 

[Touch-packages] [Bug 1792004] Re: built-in PATH seems to have sbin and bin out of order; and inconsistent

[Adam Conrad]

Hello Dimitri, or anyone else affected,

Accepted bash into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bash/4.4.18-2ubuntu1.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 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: bash (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed-bionic

** Changed in: bash (Ubuntu Xenial)
   Status: New => 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1792004

Title:
  built-in PATH seems to have sbin and bin out of order; and
  inconsistent

Status in apt package in Ubuntu:
  Fix Released
Status in bash package in Ubuntu:
  Fix Released
Status in busybox package in Ubuntu:
  New
Status in dash package in Ubuntu:
  New
Status in dpkg package in Ubuntu:
  Won't Fix
Status in pam package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in bash source package in Xenial:
  Fix Committed
Status in bash source package in Bionic:
  Fix Committed
Status in bash source package in Disco:
  Fix Committed
Status in bash package in Debian:
  New

Bug description:
  [Impact]

   * For consistency reasons sbin should be ordered before bin in PATH.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  And check that matching pairs in PATH, have /sbin variant leading /bin
  variant.

  [Regression Potential]

   * Ubuntu does not ship duplicate binries, with different behaviour
  between /sbin and /bin, thus all binaries will continue to be found in
  all locations. Also PATH is normally already set in the environment,
  and this change only affects the fallback path when bash is executed
  without any environment, i.e. booting with 'init=/bin/bash'

  [Other Info]
   
   * Original bug report detailing inconsistent paths between various shells.

  ---

  
  $ env -u PATH /bin/sh -c 'echo $PATH'
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ env -u PATH /bin/dash -c 'echo $PATH'
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ systemd-run --unit test-env env # ... and check journal for PATH
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  $ env -u PATH /bin/bash -c 'echo $PATH'
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  $ env -u PATH /bin/busybox sh -c 'echo $PATH'
  /sbin:/usr/sbin:/bin:/usr/bin

  $ grep 'export PATH=' -r initramfs-tools-0.131ubuntu10/
  initramfs-tools-0.131ubuntu10/mkinitramfs:export PATH='/usr/bin:/sbin:/bin'
  initramfs-tools-0.131ubuntu10/init:export PATH=/sbin:/usr/sbin:/bin:/usr/bin

  dracut.sh has DRACUT_PATH=${DRACUT_PATH:-/sbin /bin /usr/sbin /usr/bin} 
exported as PATH
  dracut-047+31/modules.d/99shutdown/shutdown.sh:export 
PATH=/usr/sbin:/usr/bin:/sbin:/bin

  $ cat /etc/environment
  
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"

  apt & dpkg => should probably initiate /usr/local-less PATH

  Imho the rest should probably be harmonised to:

  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin

  ===

  From a duplicate
  https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080 :

  $ for i in 12.04 12.10 13.04 13.10 14.04 14.10 15.04 15.10 16.04; do echo $i; 
docker run -it --rm ubuntu:$i bash -c "unset PATH; /bin/bash -c 'echo \$PATH'"; 
done
  12.04
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  12.10
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  13.04
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  13.10
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  14.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  14.10
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  15.04
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
  15.10
  

[Touch-packages] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash

[Adam Conrad]

Hello Philippe, or anyone else affected,

Accepted bash into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bash/4.4.18-2ubuntu1.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 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: bash (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Trusty:
  In Progress
Status in bash source package in Xenial:
  Fix Committed
Status in bash source package in Bionic:
  Fix Committed
Status in bash source package in Cosmic:
  Fix Released
Status in bash source package in Disco:
  Fix Committed
Status in bash source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

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

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

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

[Adam Conrad]

Hello Philippe, or anyone else affected,

Accepted bash into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bash/4.3-14ubuntu1.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 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 bash in Ubuntu.
https://bugs.launchpad.net/bugs/1614080

Title:
  PATH contains dot when PATH is unset before running bash

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Trusty:
  In Progress
Status in bash source package in Xenial:
  Fix Committed
Status in bash source package in Bionic:
  Fix Committed
Status in bash source package in Cosmic:
  Fix Released
Status in bash source package in Disco:
  Fix Committed
Status in bash source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The fallback path built into bash contains '.' which leads to
  unexpected addition of the current working directory. It should not be
  there, just like it isnt' in pre-precise and cosmic+.

  [Test Case]

   * $ env -u PATH /bin/bash -c 'echo $PATH'

  Should not have '.' as any component. Nor should there be any empty
  components, i.e. '::'.

  [Regression Potential]

   * Normally PATH is always set by either init, systemd, or any other
  hypervisor. Thus this only affects executions under bash, when it was
  started without any environment - e.g. booting with 'init=/bin/bash'.

  [Other Info]
   
   * Original bug report.

  On ubuntu 16.04 (but also 14.04), running bash with PATH unset always
  adds '.' to PATH:

  philippe@pv-desktop:~$ echo $PATH
  
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  philippe@pv-desktop:~$ unset PATH
  philippe@pv-desktop:~$ /bin/bash
  philippe@pv-desktop:~$ echo $PATH
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

  Even when testing in a virtual machine / docker, and erasing
  /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem
  still happens.

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

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

[Touch-packages] [Bug 1380702] Re: No keyboards shortcuts in QT apps

[adin]

How can I test this?  I'm checking #73 but the link is dead.  I'm in
Ubuntu 18.10 and the shortcut for Ctrl+Alt+Space is still not working on
texstudio (other shortcuts seem to be working), this should be a similar
behavior to #75 but it isn't.

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

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  Fix Released
Status in Canonical System Image:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Xenial:
  Fix Released
Status in qtbase-opensource-src source package in Yakkety:
  Won't Fix

Bug description:
  Impact
  ==

  This affects all Qt applications on Unity and other desktops which use
  global menu, either via appmenu-qt5 or via native implementation on
  Yakkety.

  Any shortcut is not working if the corresponding action is attached
  only to the menubar (i.e. and not also to the toolbar). It can be
  reproduced with almost any application by removing the toolbar (right-
  clicking on it and deselecting it).

  Test Case
  =

  * Open Qt Assistant;
  * Press Ctrl+T (this action is not on the toolbar).

  Expected: a new tab should be opened. Current result: nothing happens.

  In Yakkety the fix should work both with and without appmenu-qt5.

  Proposed Fix
  

  The proposed fix is a backport of the upstream fix at
  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=287f548d4c7cc594.

  Actually just the qshortcut.cpp part would be sufficient, but the
  other parts make sure it plays fine together with https://cgit.kde.org
  /plasma-integration.git/commit/?id=aef74e97e2ed462a.

  Regression Potential
  

  The fix is in Zesty for 1½ months now (in upstream even longer), and
  so far nobody complained. People have verified that the fix works (see
  comment #63).

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions

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

[Touch-packages] [Bug 1824111] Re: Backport packages for 18.04.3 HWE stack

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/19.0.2-1ubuntu1~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 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: mesa (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/1824111

Title:
  Backport packages for 18.04.3 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-8 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Committed
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-8 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:
  New
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  New
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  New

Bug description:
  [Impact]

  These are needed for 18.04.3 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-8: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

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

  xserver: a new minor release

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

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

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

[Touch-packages] [Bug 1796193] Re: unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

[Brian Murray]

The following error message is from the conffile function in
DistUpgradeViewNonInteractive.py

2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required,
not 'str'' when trying to write to the conffile

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

Status in apt package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged

Bug description:
  I'm trying to do some automated testing that involved upgrading a
  system from xenial to bionic, so I need it to not ask for user input.

  Before running do-release-upgrade, the system got a fresh dist-upgrade
  and reboot.

  To avoid interactive responses, I'm using:
  $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive

  Part way through the upgrade, I do get prompted for something though:
  Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ...

  Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ...

  Processing triggers for libc-bin (2.27-3ubuntu1) ...

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file
  or directory

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or
  directory

  Setting up apt (1.6.3ubuntu0.1) ...

  Installing new version of config file /etc/apt/apt.conf.d/01autoremove
  ...


  Configuration file '/etc/cron.daily/apt-compat'

   ==> Deleted (by you or by a script) since installation.

   ==> Package distributor has shipped an updated version.

 What would you like to do about it ?  Your options are:

  Y or I  : install the package maintainer's version

  N or O  : keep your currently-installed version

D : show the differences between the versions

Z : start a shell to examine the situation

   The default action is to keep your current version.

  Comparing the sha1 of apt-compat before the upgrade to another xenial
  system that has been unmodified, they are the same:

  In /var/log/dist-upgrade/main.log, I also found this:
  2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: 
'/etc/cron.daily/apt-compat'
  2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 
'str'' when trying to write to the conffile

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

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

[Touch-packages] [Bug 1796193] Re: unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: New => Confirmed

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

Title:
  unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

Status in apt package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged

Bug description:
  I'm trying to do some automated testing that involved upgrading a
  system from xenial to bionic, so I need it to not ask for user input.

  Before running do-release-upgrade, the system got a fresh dist-upgrade
  and reboot.

  To avoid interactive responses, I'm using:
  $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive

  Part way through the upgrade, I do get prompted for something though:
  Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ...

  Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ...

  Processing triggers for libc-bin (2.27-3ubuntu1) ...

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file
  or directory

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or
  directory

  Setting up apt (1.6.3ubuntu0.1) ...

  Installing new version of config file /etc/apt/apt.conf.d/01autoremove
  ...


  Configuration file '/etc/cron.daily/apt-compat'

   ==> Deleted (by you or by a script) since installation.

   ==> Package distributor has shipped an updated version.

 What would you like to do about it ?  Your options are:

  Y or I  : install the package maintainer's version

  N or O  : keep your currently-installed version

D : show the differences between the versions

Z : start a shell to examine the situation

   The default action is to keep your current version.

  Comparing the sha1 of apt-compat before the upgrade to another xenial
  system that has been unmodified, they are the same:

  In /var/log/dist-upgrade/main.log, I also found this:
  2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: 
'/etc/cron.daily/apt-compat'
  2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 
'str'' when trying to write to the conffile

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

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

[Touch-packages] [Bug 1796193] Re: unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

[Launchpad Bug Tracker]

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

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

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

Title:
  unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

Status in apt package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged

Bug description:
  I'm trying to do some automated testing that involved upgrading a
  system from xenial to bionic, so I need it to not ask for user input.

  Before running do-release-upgrade, the system got a fresh dist-upgrade
  and reboot.

  To avoid interactive responses, I'm using:
  $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive

  Part way through the upgrade, I do get prompted for something though:
  Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ...

  Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ...

  Processing triggers for libc-bin (2.27-3ubuntu1) ...

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file
  or directory

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or
  directory

  Setting up apt (1.6.3ubuntu0.1) ...

  Installing new version of config file /etc/apt/apt.conf.d/01autoremove
  ...


  Configuration file '/etc/cron.daily/apt-compat'

   ==> Deleted (by you or by a script) since installation.

   ==> Package distributor has shipped an updated version.

 What would you like to do about it ?  Your options are:

  Y or I  : install the package maintainer's version

  N or O  : keep your currently-installed version

D : show the differences between the versions

Z : start a shell to examine the situation

   The default action is to keep your current version.

  Comparing the sha1 of apt-compat before the upgrade to another xenial
  system that has been unmodified, they are the same:

  In /var/log/dist-upgrade/main.log, I also found this:
  2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: 
'/etc/cron.daily/apt-compat'
  2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 
'str'' when trying to write to the conffile

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

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

[Touch-packages] [Bug 1796193] Re: unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

[Brian Murray]

** Also affects: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

Status in apt package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged

Bug description:
  I'm trying to do some automated testing that involved upgrading a
  system from xenial to bionic, so I need it to not ask for user input.

  Before running do-release-upgrade, the system got a fresh dist-upgrade
  and reboot.

  To avoid interactive responses, I'm using:
  $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive

  Part way through the upgrade, I do get prompted for something though:
  Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ...

  Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ...

  Processing triggers for libc-bin (2.27-3ubuntu1) ...

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file
  or directory

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or
  directory

  Setting up apt (1.6.3ubuntu0.1) ...

  Installing new version of config file /etc/apt/apt.conf.d/01autoremove
  ...


  Configuration file '/etc/cron.daily/apt-compat'

   ==> Deleted (by you or by a script) since installation.

   ==> Package distributor has shipped an updated version.

 What would you like to do about it ?  Your options are:

  Y or I  : install the package maintainer's version

  N or O  : keep your currently-installed version

D : show the differences between the versions

Z : start a shell to examine the situation

   The default action is to keep your current version.

  Comparing the sha1 of apt-compat before the upgrade to another xenial
  system that has been unmodified, they are the same:

  In /var/log/dist-upgrade/main.log, I also found this:
  2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: 
'/etc/cron.daily/apt-compat'
  2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 
'str'' when trying to write to the conffile

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

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

[Touch-packages] [Bug 1824111] Re: Backport packages for 18.04.3 HWE stack

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted libclc into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libclc/0.2.0+git20190306-1~ubuntu18.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 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: libclc (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/1824111

Title:
  Backport packages for 18.04.3 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-8 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Committed
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-8 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  New
Status in xorg-server-hwe-18.04 source package in Bionic:
  New
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  New
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  New

Bug description:
  [Impact]

  These are needed for 18.04.3 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-8: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

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

  xserver: a new minor release

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

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

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

[Touch-packages] [Bug 1828454] Re: i18n: Wrong french translation of "Mbits/s" as "Mo/s"

[dhenry]

Mo [french] = Mega octets [french] = Mega Bytes [english]

There's already a suggestion for 261, and I added a new one for 281, but
I don't know if/when it will be reviewed. The current suggestions for
261 have been added since 2008 and 2011!

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

Title:
  i18n: Wrong french translation of "Mbits/s" as "Mo/s"

Status in Ubuntu Translations:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  When running "nmcli device wifi", the list of avalaible SSID appears
  with their rate.

  In english (LANG=C), the rate unit is "Mbit/s".
  In french (LANG=fr_FR.UTF-8), it has been translated to "Mo/s", which means 
"MBytes/s"!

  Assuming the original (english) unit is correct, then it should stay
  "Mbit/s" in french.

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

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

[Touch-packages] [Bug 1828454] Re: i18n: Wrong french translation of "Mbits/s" as "Mo/s"

[Hans Joachim Desserud]

Thanks for reporting.

Looks like two string have been translated to "Mo/s".

https://translations.launchpad.net/ubuntu/eoan/+source/network-manager/+pots/networkmanager/fr/261/+translate
https://translations.launchpad.net/ubuntu/eoan/+source/network-manager/+pots/networkmanager/fr/281/+translate

I don't know French well enough to do it myself, but it is possible to
add a new translation suggestion.

** Also affects: ubuntu-translations
   Importance: Undecided
   Status: New

** Tags added: eoan

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

Title:
  i18n: Wrong french translation of "Mbits/s" as "Mo/s"

Status in Ubuntu Translations:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  When running "nmcli device wifi", the list of avalaible SSID appears
  with their rate.

  In english (LANG=C), the rate unit is "Mbit/s".
  In french (LANG=fr_FR.UTF-8), it has been translated to "Mo/s", which means 
"MBytes/s"!

  Assuming the original (english) unit is correct, then it should stay
  "Mbit/s" in french.

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

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

[Touch-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

[Thadeu Lima de Souza Cascardo]

Still need to fix it so it will exit when unit is failed, and maybe
after some timeout.


---
 debian/tests/storage | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/debian/tests/storage b/debian/tests/storage
index 04d11c8..47fbe81 100755
--- a/debian/tests/storage
+++ b/debian/tests/storage
@@ -73,6 +73,8 @@ class CryptsetupTest(FakeDriveTestBase):
 subprocess.call(['umount', self.plaintext_dev], 
stderr=subprocess.DEVNULL)
 subprocess.call(['systemctl', 'start', '--no-ask-password', 
'systemd-cryptsetup@%s.service' % self.plaintext_name],
 stderr=subprocess.STDOUT)
+while subprocess.call(['systemctl', 'is-active', 
'systemd-cryptsetup@%s.service' % self.plaintext_name], 
stderr=subprocess.STDOUT) != 0:
+pass
 subprocess.call(['systemctl', 'stop', 'systemd-cryptsetup@%s.service' 
% self.plaintext_name],
 stderr=subprocess.STDOUT)
 if os.path.exists('/etc/crypttab'):
--

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in udisks2 package in Ubuntu:
  New

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

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

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

[Touch-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

[Thadeu Lima de Souza Cascardo]

With systemd storage test, I got two different situations:

Also on amd64, the test is still flaky, it needs to wait for the unit to
be active before stopping it, otherwise it's canceled. I will send a
comment with a preview of a fix.

On ppc64el, however, even after that fix, the patch will fail once in a
while, with /lib/systemd/systemd-cryptsetup crashing on an invalid free.
I started investigating that, but still can't figure what the real
problem is. Maybe some corruption going on, but really hard to catch
when, as running under valgrind doesn't allow the bug to be reproduced.

Cascardo.

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in udisks2 package in Ubuntu:
  New

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

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

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

[Touch-packages] [Bug 1828454] [NEW] i18n: Wrong french translation of "Mbits/s" as "Mo/s"

[dhenry]

Public bug reported:

When running "nmcli device wifi", the list of avalaible SSID appears
with their rate.

In english (LANG=C), the rate unit is "Mbit/s".
In french (LANG=fr_FR.UTF-8), it has been translated to "Mo/s", which means 
"MBytes/s"!

Assuming the original (english) unit is correct, then it should stay
"Mbit/s" in french.

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

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

Title:
  i18n: Wrong french translation of "Mbits/s" as "Mo/s"

Status in network-manager package in Ubuntu:
  New

Bug description:
  When running "nmcli device wifi", the list of avalaible SSID appears
  with their rate.

  In english (LANG=C), the rate unit is "Mbit/s".
  In french (LANG=fr_FR.UTF-8), it has been translated to "Mo/s", which means 
"MBytes/s"!

  Assuming the original (english) unit is correct, then it should stay
  "Mbit/s" in french.

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

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

[Touch-packages] [Bug 1825972] Re: Remove gnome 2 stack + linsmith from eoan

[Julian Andres Klode]

New chromium has just migrated to release pocket.

** Changed in: libgnome-keyring (Ubuntu)
   Status: Incomplete => New

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

Title:
  Remove gnome 2 stack + linsmith from eoan

Status in gnome-vfs package in Ubuntu:
  New
Status in libbonobo package in Ubuntu:
  New
Status in libbonoboui package in Ubuntu:
  New
Status in libgnome package in Ubuntu:
  New
Status in libgnome-keyring package in Ubuntu:
  New
Status in libgnomeui package in Ubuntu:
  Fix Released
Status in linsmith package in Ubuntu:
  Fix Released
Status in orbit2 package in Ubuntu:
  New

Bug description:
  Please remove these packages from eoan. They are not shipped in Debian
  buster, unmaintained since 2015 and the libgnome-keyring one has not
  been updated for libgcrypt{11,20}-dev rename.

  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnome-keyring
  Reverse-Depends
  ===
  * libgnomeui-0  (for libgnome-keyring0)
  * libgnomeui-dev(for libgnome-keyring-dev)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnomeui
  Reverse-Depends
  ===
  * linsmith  (for libgnomeui-0)

  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco src:linsmith
  Reverse-Recommends
  ==
  * electronics-radio-dev (for linsmith)
  * hamradio-antenna  (for linsmith)
  * science-electronics   (for linsmith)

  Packages without architectures listed are reverse-dependencies in:
  amd64, arm64, armhf, i386, ppc64el, s390x

  Also, these other related packages do not have reverse dependencies
  either, and can be removed:

  $ reverse-depends -r eoan src:libbonoboui -b
  No reverse dependencies found
  $ reverse-depends -r eoan src:libgnome -b
  Reverse-Build-Depends
  =
  * libbonoboui   (for libgnome2-dev)

  $ reverse-depends -r eoan src:libbonobo -b
  Reverse-Build-Depends
  =
  * libbonoboui   (for libbonobo2-dev)
  * libgnome  (for libbonobo2-dev)

  $ reverse-depends -r eoan src:gnome-vfs -b
  Reverse-Build-Depends
  =
  * libgnome  (for libgnomevfs2-dev)

  $ reverse-depends -r eoan src:orbit2 -b
  Reverse-Build-Depends
  =
  * libbonobo (for liborbit2-dev)

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

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

[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

[Till Kamppeter]

Good news, the network-manager SRU is not broken or wrong, but an
additional SRU, on systemd, is needed to actually fix this bug.

I got a hint from Iain Lane (Laney, thank you very much) to the
following fix in systemd upstream:

https://github.com/systemd/systemd/commit/a97a3b256

and backported it to Bionic's systemd package (debdiff attached). With
the network-manager SRU from -proposed attached plus the patched systemd
package installed the problem goes away. If I repeat the test of [Test
Case] (after a reboot) the DNS requests to any of the VPN's domains go
actually only to the VPN's DNS.

** Patch added: "systemd_237-3ubuntu10.21_237-3ubuntu10.22.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1754671/+attachment/5262723/+files/systemd_237-3ubuntu10.21_237-3ubuntu10.22.debdiff

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

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

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

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

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

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Triaged

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

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

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

[Touch-packages] [Bug 1818564] Re: directory permission sanity checks

[Brian Murray]

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

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

Title:
  directory permission sanity checks

Status in apport package in Ubuntu:
  Triaged

Bug description:
  Hello, we've received a surprising number of bug reports that include
  lines from ufw's sanity checks on / permissions are incorrect; it's
  been a recurring feature of systemd-tmpfiles bug reports as well.

  I think apport should include a similar report if / /etc /lib /usr
  /tmp etc have incorrect user, group, or permissions.

  Thanks

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

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

[Touch-packages] [Bug 1777512] Re: rt #112309: keyserver.ubuntu.com increased failure rates over past few days

[Jason Hobbs]

Sub'd ~field-high.

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

** Summary changed:

- rt #112309: keyserver.ubuntu.com increased failure rates over past few days
+ key retrieval timeouts cause failures

** Description changed:

- keyserver failures more often than usual! not just our team experiencing
- it - several other teams have reported it too.
+ We have been seeing keyserver timeouts causing failed runs at an
+ increased rate recently (over the last 6+ months). Here is an example
+ failure:
  
+ [10.244.40.32] sudo: add-apt-repository -k https://keyserver.ubuntu.com/ 
--yes "ppa:curtin-dev/proposed"
+ [10.244.40.32] out: Error: retrieving gpg key timed out.
+ 
+ One idea is that this needs to be addressed by making the client
+ (software-properties) more robust.
+ 
+ 
+ We have an RT about this:
  https://portal.admin.canonical.com/C112309/

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

Title:
  key retrieval timeouts cause failures

Status in CDO QA System Tests:
  Confirmed
Status in software-properties package in Ubuntu:
  New

Bug description:
  We have been seeing keyserver timeouts causing failed runs at an
  increased rate recently (over the last 6+ months). Here is an example
  failure:

  [10.244.40.32] sudo: add-apt-repository -k https://keyserver.ubuntu.com/ 
--yes "ppa:curtin-dev/proposed"
  [10.244.40.32] out: Error: retrieving gpg key timed out.

  One idea is that this needs to be addressed by making the client
  (software-properties) more robust.

  
  We have an RT about this:
  https://portal.admin.canonical.com/C112309/

To manage notifications about this bug go to:
https://bugs.launchpad.net/cdoqa-system-tests/+bug/1777512/+subscriptions

-- 
Mailing list: https://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 1786574] Re: remove i2c-i801 from blacklist

[Khairul Aizat Kamarudzzaman]

Hi Aaron,
Thanks for your prompt replied.

I can't find the file synaptics.c to patch , mind to advise me how to patch ?
On May 9 2019, at 10:21 pm, AaronMa  wrote:
> Hi, Khairul,
> Could you try the attached patch?
>
> you can apply this patch in latest kernel.
> And give it a try? no kernel parameter needed.
>
> If it works, I will upstream it.
> Thanks in advance.
> ** Patch added: 
> "0002-Input-synaptics-remove-X240-from-the-topbuttonpad-li.patch"
> https://bugs.launchpad.net/hwe-next/+bug/1786574/+attachment/5262688/+files/0002-Input-synaptics-remove-X240-from-the-topbuttonpad-li.patch
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1786574
>
> Title:
> remove i2c-i801 from blacklist
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/hwe-next/+bug/1786574/+subscriptions
>

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Cosmic:
  In Progress

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

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

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

[Touch-packages] [Bug 1828439] Re: false error message displaying printer out of paper

[Marc Deslauriers]

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

** This bug has been marked a duplicate of bug 1828401
   9.26~dfsg+0-0ubuntu0.18.04.9 breaks cups printing of pdf

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

Title:
  false error message displaying printer out of paper

Status in cups package in Ubuntu:
  New

Bug description:
  error message saying that the printer (network printer) is out of
  paper when i want to print and when i try to print the test page,
  whereas the self-test page prints correctly without paper problem and
  other people on the network printer print correctly

  1) release of Ubuntu : Ubuntu 18.04.2 LTS

  2) cups:
Installed: 2.2.7-1ubuntu2.4
Candidate: 2.2.7-1ubuntu2.4
Version table:
   *** 2.2.7-1ubuntu2.4 500
  500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.2.7-1ubuntu2.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   2.2.7-1ubuntu2 500
  500 http://ca.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  3) i expected the printing to occur

  4) an message say that the printing is stopped and in the settings it
  says that the printer is out of paper. However, there is paper in the
  printer, the self-test print page is printed correctly and other
  people can use this network printer without issue

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.4
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  9 12:15:56 2019
  InstallationDate: Installed on 2018-09-17 (233 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  Lpstat:
   device for Toshiba-e-Studio-523: socket://172.23.156.17:9100
   device for Toshiba-e-Studio-523-2: socket://172.23.156.17:9100
   device for TOSHIBA-e-STUDIO523: 
dnssd://TOSHIBA%20e-STUDIO523-04409643._printer._tcp.local/
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 413c:301a Dell Computer Corp. 
   Bus 001 Device 002: ID 413c:2113 Dell Computer Corp. 
   Bus 001 Device 005: ID 1004:631c LG Electronics, Inc. G2/Optimus Android 
Phone [MTP mode]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision Tower 3620
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/TOSHIBA-e-STUDIO523.ppd', 
'/etc/cups/ppd/Toshiba-e-Studio-523.ppd', 
'/etc/cups/ppd/Toshiba-e-Studio-523-2.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/TOSHIBA-e-STUDIO523.ppd: Permission denied
   grep: /etc/cups/ppd/Toshiba-e-Studio-523.ppd: Permission denied
   grep: /etc/cups/ppd/Toshiba-e-Studio-523-2.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=865b6827-276d-4151-b478-227f380b71de ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2019-01-21 (107 days ago)
  dmi.bios.date: 11/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.11.2
  dmi.board.name: 0MWYPT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.11.2:bd11/07/2018:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn0MWYPT:rvrA02:cvnDellInc.:ct3:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision Tower 3620
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1796193] Re: unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

[David Ames]

Yes, for juju series upgrades.

The following will work around the problem:

echo 'DPkg::options { "--force-confdef"; };' > /etc/apt/apt.conf.d
/50unattended-upgrades

I'll leave the decision on if this remains a bug up to others.

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

Title:
  unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

Status in apt package in Ubuntu:
  New

Bug description:
  I'm trying to do some automated testing that involved upgrading a
  system from xenial to bionic, so I need it to not ask for user input.

  Before running do-release-upgrade, the system got a fresh dist-upgrade
  and reboot.

  To avoid interactive responses, I'm using:
  $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive

  Part way through the upgrade, I do get prompted for something though:
  Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ...

  Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ...

  Processing triggers for libc-bin (2.27-3ubuntu1) ...

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file
  or directory

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or
  directory

  Setting up apt (1.6.3ubuntu0.1) ...

  Installing new version of config file /etc/apt/apt.conf.d/01autoremove
  ...


  Configuration file '/etc/cron.daily/apt-compat'

   ==> Deleted (by you or by a script) since installation.

   ==> Package distributor has shipped an updated version.

 What would you like to do about it ?  Your options are:

  Y or I  : install the package maintainer's version

  N or O  : keep your currently-installed version

D : show the differences between the versions

Z : start a shell to examine the situation

   The default action is to keep your current version.

  Comparing the sha1 of apt-compat before the upgrade to another xenial
  system that has been unmodified, they are the same:

  In /var/log/dist-upgrade/main.log, I also found this:
  2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: 
'/etc/cron.daily/apt-compat'
  2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 
'str'' when trying to write to the conffile

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

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

[Touch-packages] [Bug 1524215] Re: Lenovo B50-70 inverted internal microphone

[Ubuntu Foundations Team Bug Bot]

The attachment
"fix_for_lenovo_b50-70_inverted_internal_microphone_bug.patch" seems to
be a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Lenovo B50-70 inverted internal microphone

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978 
  Attached the alsa-info txt to this bug
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marian 1981 F pulseaudio
   /dev/snd/pcmC1D0c:   marian 1981 F...m pulseaudio
   /dev/snd/pcmC1D0p:   marian 1981 F...m pulseaudio
   /dev/snd/controlC1:  marian 1981 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=10570c82-8e52-4379-9a8e-2e30baae9f63
  InstallationDate: Installed on 2015-09-10 (90 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20384
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=1791e4c1-12de-4fef-88b1-31716c981648 ro quiet splash
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: Upgraded to wily on 2015-10-24 (45 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9DCN34WW(V3.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo B50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9DCN34WW(V3.04):bd07/21/2015:svnLENOVO:pn20384:pvrLenovoB50-70:rvnLENOVO:rnLenovoB50-70:rvrNODPK:cvnLENOVO:ct10:cvrLenovoB50-70:
  dmi.product.name: 20384
  dmi.product.version: Lenovo B50-70
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1828439] [NEW] false error message displaying printer out of paper

[Nuxaryn]

Public bug reported:

error message saying that the printer (network printer) is out of paper
when i want to print and when i try to print the test page, whereas the
self-test page prints correctly without paper problem and other people
on the network printer print correctly

1) release of Ubuntu : Ubuntu 18.04.2 LTS

2) cups:
  Installed: 2.2.7-1ubuntu2.4
  Candidate: 2.2.7-1ubuntu2.4
  Version table:
 *** 2.2.7-1ubuntu2.4 500
500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 2.2.7-1ubuntu2.2 500
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
 2.2.7-1ubuntu2 500
500 http://ca.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

3) i expected the printing to occur

4) an message say that the printing is stopped and in the settings it
says that the printer is out of paper. However, there is paper in the
printer, the self-test print page is printed correctly and other people
can use this network printer without issue

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.4
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname: Linux 4.15.0-48-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu May  9 12:15:56 2019
InstallationDate: Installed on 2018-09-17 (233 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
Lpstat:
 device for Toshiba-e-Studio-523: socket://172.23.156.17:9100
 device for Toshiba-e-Studio-523-2: socket://172.23.156.17:9100
 device for TOSHIBA-e-STUDIO523: 
dnssd://TOSHIBA%20e-STUDIO523-04409643._printer._tcp.local/
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 413c:301a Dell Computer Corp. 
 Bus 001 Device 002: ID 413c:2113 Dell Computer Corp. 
 Bus 001 Device 005: ID 1004:631c LG Electronics, Inc. G2/Optimus Android Phone 
[MTP mode]
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision Tower 3620
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/TOSHIBA-e-STUDIO523.ppd', 
'/etc/cups/ppd/Toshiba-e-Studio-523.ppd', 
'/etc/cups/ppd/Toshiba-e-Studio-523-2.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/TOSHIBA-e-STUDIO523.ppd: Permission denied
 grep: /etc/cups/ppd/Toshiba-e-Studio-523.ppd: Permission denied
 grep: /etc/cups/ppd/Toshiba-e-Studio-523-2.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=865b6827-276d-4151-b478-227f380b71de ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: Upgraded to bionic on 2019-01-21 (107 days ago)
dmi.bios.date: 11/07/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.11.2
dmi.board.name: 0MWYPT
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.11.2:bd11/07/2018:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn0MWYPT:rvrA02:cvnDellInc.:ct3:cvr:
dmi.product.family: Precision
dmi.product.name: Precision Tower 3620
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apparmor apport-bug bionic third-party-packages

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

Title:
  false error message displaying printer out of paper

Status in cups package in Ubuntu:
  New

Bug description:
  error message saying that the printer (network printer) is out of
  paper when i want to print and when i try to print the test page,
  whereas the self-test page prints correctly without paper problem and
  other people on the network printer print correctly

  1) release of Ubuntu : Ubuntu 18.04.2 LTS

  2) cups:
Installed: 2.2.7-1ubuntu2.4
Candidate: 2.2.7-1ubuntu2.4
Version table:
   *** 2.2.7-1ubuntu2.4 500
  500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.2.7-1ubuntu2.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   2.2.7-1ubuntu2 500
  500 http://ca.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  3) i expected the printing to occur

  4) an message say that the printing is stopped and in the settings it
  says that the printer is out of paper. However, there is paper in the
  printer, the self-test print page is printed correctly and other
  people can use this network printer without issue

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.4
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  9 12:15:56 2019
  InstallationDate: 

[Touch-packages] [Bug 1818564] Re: directory permission sanity checks

[Steve Langasek]

** Tags removed: rls-ee-incoming
** Tags added: rls-ee-notfixing

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

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

Title:
  directory permission sanity checks

Status in apport package in Ubuntu:
  New

Bug description:
  Hello, we've received a surprising number of bug reports that include
  lines from ufw's sanity checks on / permissions are incorrect; it's
  been a recurring feature of systemd-tmpfiles bug reports as well.

  I think apport should include a similar report if / /etc /lib /usr
  /tmp etc have incorrect user, group, or permissions.

  Thanks

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

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

[Touch-packages] [Bug 1825000] Re: Add ability for mirrors to distinguish interactive and non-interactive apt runs

[Julian Andres Klode]

** Changed in: apt (Ubuntu)
   Importance: Undecided => Wishlist

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

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

Title:
  Add ability for mirrors to distinguish interactive and non-interactive
  apt runs

Status in apt package in Ubuntu:
  Triaged

Bug description:
  As part of a larger scale plan to manage traffic to the main archive
  servers it would be useful if apt could provide a facility for us to
  identify interactive vs. non-interactive traffic on the server side,
  ideally via a header of some kind.

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

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

[Touch-packages] [Bug 1796193] Re: unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

[Julian Andres Klode]

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

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

Title:
  unattended do-release-upgrade asks about /etc/cron.daily/apt-compat

Status in apt package in Ubuntu:
  New

Bug description:
  I'm trying to do some automated testing that involved upgrading a
  system from xenial to bionic, so I need it to not ask for user input.

  Before running do-release-upgrade, the system got a fresh dist-upgrade
  and reboot.

  To avoid interactive responses, I'm using:
  $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive

  Part way through the upgrade, I do get prompted for something though:
  Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ...

  Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ...

  Processing triggers for libc-bin (2.27-3ubuntu1) ...

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file
  or directory

  /sbin/ldconfig.real: Warning: ignoring configuration file that cannot
  be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or
  directory

  Setting up apt (1.6.3ubuntu0.1) ...

  Installing new version of config file /etc/apt/apt.conf.d/01autoremove
  ...


  Configuration file '/etc/cron.daily/apt-compat'

   ==> Deleted (by you or by a script) since installation.

   ==> Package distributor has shipped an updated version.

 What would you like to do about it ?  Your options are:

  Y or I  : install the package maintainer's version

  N or O  : keep your currently-installed version

D : show the differences between the versions

Z : start a shell to examine the situation

   The default action is to keep your current version.

  Comparing the sha1 of apt-compat before the upgrade to another xenial
  system that has been unmodified, they are the same:

  In /var/log/dist-upgrade/main.log, I also found this:
  2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: 
'/etc/cron.daily/apt-compat'
  2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 
'str'' when trying to write to the conffile

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

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

[Touch-packages] [Bug 1821415] Re: pkexec fails in a non-graphical environment

[Brian Murray]

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

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

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

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  New
Status in apport package in Ubuntu:
  Triaged
Status in policykit-1 package in Ubuntu:
  Triaged

Bug description:
  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not
  in a non-graphical one.

  N.B. you first need to create a /var/log/plymouth-debug.log file for
  the plymouth apport package hook to actually trigger this.

  ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  Subsequently, bug reports from servers will contain less information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1821415/+subscriptions

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

[Touch-packages] [Bug 1825001] Re: Allow archives to send a 4xx response to tell apt to try again later

[Julian Andres Klode]

** Changed in: apt (Ubuntu)
   Importance: Undecided => Wishlist

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

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

Title:
  Allow archives to send a 4xx response to tell apt to try again later

Status in apt package in Ubuntu:
  Triaged

Bug description:
  As part of a broad plan to improve our ability to manage traffic to
  the archive servers, it would be useful if the archives could return a
  4xx response to indicate to apt that they were over capacity and it
  should try again later, where later could be defined on the client
  side as several hours, the next day for unattended-upgrades runs, etc.

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

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

[Touch-packages] [Bug 1825021] Re: apt's dpkgpm.cc WriteApportReport function should gather more data

[Steve Langasek]

** Also affects: apt (Ubuntu Eoan)
   Importance: High
   Status: New

** Tags removed: rls-ee-incoming

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

Title:
  apt's dpkgpm.cc WriteApportReport function should gather more data

Status in apt package in Ubuntu:
  New
Status in apt source package in Eoan:
  New

Bug description:
  While fixing bug 1813464 it occurred to me that it is not obvious that
  the dist-upgrader tarball includes its own copy of invoke-rc.d and
  that this has been complicated to debug more than once. The apport
  information in that report was gathered by apt's dpkgpm.cc code and I
  think we should extend that to gather additional information from the
  environment at the time that the package installation failed. For
  example the dist-upgrader sets the following:

  os.environ["PATH"] = "%s:%s" % (os.getcwd()+"/imported",
  os.environ["PATH"])

  Gathering path from the environment would have made diagnosing bug
  1813464 a lot easier. I tested modifying dpkgpm.cc with the following:

 if(const char* env_p = std::getenv("PATH"))
fprintf(report, "EnvPATH: %s\n", env_p);

  I then installed the crash-in-postinst package from the daisy-plucker-
  seeds PPA and received a crash report with the EnvPATH key and value.
  Its worth noting that when apport gathers environment information only
  a white listed set of keys is gathered to prevent disclosing
  potentially sensitive information. So we should look at what
  environment variables the dist-upgrader sets and gather those at a
  minimum.

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

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

[Touch-packages] [Bug 1826870] Re: cache.commit() doesn't release the archives lock

[Julian Andres Klode]

I installed the upgrades, and ran the script in the bug description and
see if it got fixed.

xenial python3-apt (1.1.0~beta1ubuntu0.16.04.4) verified - note that the one in 
-updates is fine too, it only broke for the previous upload in proposed.
bionic python3-apt (1.6.4) verified
cosmic python3-apt (1.7.1) verified


Full testing script for inside a lxd container:

while ! grep cloud-init /etc/apt/sources.list; do
sleep 1
done
while ! ping -c1 google.com; do
sleep 1
done
echo "deb http://archive.ubuntu.com/ubuntu $(lsb_release -cs)-proposed main" >> 
/etc/apt/sources.list
apt update
python3 - << EOF
#!/usr/bin/env python
import apt
import subprocess

cache = apt.Cache()
pkg = cache["hello"]
pkg.mark_install()
cache.commit()
subprocess.check_call(["apt", "remove", "--yes", "hello"])
EOF
apt install python3-apt
python3 - << EOF
#!/usr/bin/env python
import apt
import subprocess

cache = apt.Cache()
pkg = cache["hello"]
pkg.mark_install()
cache.commit()
subprocess.check_call(["apt", "remove", "--yes", "hello"])
EOF


Run like this:

( i=cosmic; lxc launch -e ubuntu:$i test-$i && lxc exec test-$i -- bash
-x - < ~/a.sh  ; lxc stop test-$i )


** Tags removed: verification-needed verification-needed-bionic 
verification-needed-cosmic verification-needed-xenial
** Tags added: verification-done verification-done-bionic 
verification-done-cosmic verification-done-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/1826870

Title:
  cache.commit() doesn't release the archives lock

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 Cosmic:
  Fix Committed
Status in python-apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  cache.commit() does not release all the locks it acquires as part of 
committing. This is a regression of locking fixes in bug 1795407.

  [Test case]
  This script should work:

  #!/usr/bin/env python
  import apt
  import subprocess

  cache = apt.Cache()
  pkg = cache["hello"]
  pkg.mark_install()
  cache.commit()
  subprocess.check_call(["apt", "remove", "--yes", "hello"])

  [Regression potential]
  Other new locking bugs could pop up

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

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

[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

[AaronMa]

Hi, Khairul,
Could you try the attached patch?

you can apply this patch in latest kernel.
And give it a try? no kernel parameter needed.

If it works, I will upstream it.

Thanks in advance.

** Patch added: 
"0002-Input-synaptics-remove-X240-from-the-topbuttonpad-li.patch"
   
https://bugs.launchpad.net/hwe-next/+bug/1786574/+attachment/5262688/+files/0002-Input-synaptics-remove-X240-from-the-topbuttonpad-li.patch

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Cosmic:
  In Progress

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

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

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

[Touch-packages] [Bug 1524215] Re: Lenovo B50-70 inverted internal microphone

[Michał Wadowski]

I can confirm that bug still exists in Linux Kernel 5.1.0.

I created patch to fix this issue.

** Patch added: "fix_for_lenovo_b50-70_inverted_internal_microphone_bug.patch"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1524215/+attachment/5262687/+files/fix_for_lenovo_b50-70_inverted_internal_microphone_bug.patch

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

Title:
  Lenovo B50-70 inverted internal microphone

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978 
  Attached the alsa-info txt to this bug
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marian 1981 F pulseaudio
   /dev/snd/pcmC1D0c:   marian 1981 F...m pulseaudio
   /dev/snd/pcmC1D0p:   marian 1981 F...m pulseaudio
   /dev/snd/controlC1:  marian 1981 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=10570c82-8e52-4379-9a8e-2e30baae9f63
  InstallationDate: Installed on 2015-09-10 (90 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20384
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=1791e4c1-12de-4fef-88b1-31716c981648 ro quiet splash
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: Upgraded to wily on 2015-10-24 (45 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9DCN34WW(V3.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo B50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9DCN34WW(V3.04):bd07/21/2015:svnLENOVO:pn20384:pvrLenovoB50-70:rvnLENOVO:rnLenovoB50-70:rvrNODPK:cvnLENOVO:ct10:cvrLenovoB50-70:
  dmi.product.name: 20384
  dmi.product.version: Lenovo B50-70
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

[AaronMa]

Hi Khairul:

Have you tried passing "psmouse.synaptics_intertouch=0" in kernel
parameter?

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Cosmic:
  In Progress

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

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

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

[Touch-packages] [Bug 1803203] Re: Support preferred_lft for IPv6 addresses

[Dan Streetman]

systemd back to bionic already supports the PreferredLifetime config
param.  Only netplan needs a change to provide a param to set
PreferredLifetime.

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

** Changed in: netplan
   Status: New => In Progress

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: netplan
   Status: In Progress => New

** Changed in: netplan.io (Ubuntu)
   Status: New => In Progress

** Changed in: netplan.io (Ubuntu)
 Assignee: (unassigned) => Heitor Alves de Siqueira (halves)

** Changed in: netplan.io (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Support preferred_lft for IPv6 addresses

Status in netplan:
  New
Status in netplan.io package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  There doesn't currently seem to be any way to set the preferred_lft of
  an IPv6 address.

  With the "ip" command it might be, for example:

  # ip address add 2001:db8::2/32 dev eth0 preferred_lft 0

  In a systemd unit file it might be:

  [Match]
  Name=eth0

  [Network]
  Address=2001:db8::2/32
  Gateway=2001:db8::1/32
  PreferredLifetime=0

  but I can't find any way to express this with netplan.

  This is commonly used for per-service IP addresses that should never
  be used as source addresses for outgoing traffic.

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

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

[Touch-packages] [Bug 1803203] Re: Support preferred_lft for IPv6 addresses

[Dan Streetman]

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

Title:
  Support preferred_lft for IPv6 addresses

Status in netplan:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  There doesn't currently seem to be any way to set the preferred_lft of
  an IPv6 address.

  With the "ip" command it might be, for example:

  # ip address add 2001:db8::2/32 dev eth0 preferred_lft 0

  In a systemd unit file it might be:

  [Match]
  Name=eth0

  [Network]
  Address=2001:db8::2/32
  Gateway=2001:db8::1/32
  PreferredLifetime=0

  but I can't find any way to express this with netplan.

  This is commonly used for per-service IP addresses that should never
  be used as source addresses for outgoing traffic.

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

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

[Touch-packages] [Bug 1825972] Re: Remove libgnome-keyring, libgnomeui, linsmith from eoan

[Julian Andres Klode]

Added tasks for the remainder of the old gnome/bonobo stack.


chromium is fixed in proposed, tracked in #1828192.

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

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

** Summary changed:

- Remove libgnome-keyring, libgnomeui, linsmith from eoan
+ Remove libgnome-keyring, libgnomeui, linsmith, and friendsd from eoan

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

** Description changed:

  Please remove these packages from eoan. They are not shipped in Debian
  buster, unmaintained since 2015 and the libgnome-keyring one has not
  been updated for libgcrypt{11,20}-dev rename.
  
- jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnome-keyring

 
+ jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnome-keyring
  Reverse-Depends
  ===
  * libgnomeui-0  (for libgnome-keyring0)
  * libgnomeui-dev(for libgnome-keyring-dev)
  
  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnomeui
  Reverse-Depends
  ===
  * linsmith  (for libgnomeui-0)
  
  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco src:linsmith
  Reverse-Recommends
  ==
  * electronics-radio-dev (for linsmith)
  * hamradio-antenna  (for linsmith)
  * science-electronics   (for linsmith)
  
  Packages without architectures listed are reverse-dependencies in:
  amd64, arm64, armhf, i386, ppc64el, s390x
+ 
+ 
+ Also, these other related packages do not have reverse dependencies either, 
and can be removed:
+ 
+ $ reverse-depends -r eoan src:libbonoboui -b
+ No reverse dependencies found
+ $ reverse-depends -r eoan src:libgnome -b
+ Reverse-Build-Depends
+ =
+ * libbonoboui   (for libgnome2-dev)
+ 
+ $ reverse-depends -r eoan src:libbonobo -b
+ Reverse-Build-Depends
+ =
+ * libbonoboui   (for libbonobo2-dev)
+ * libgnome  (for libbonobo2-dev)

** Description changed:

  Please remove these packages from eoan. They are not shipped in Debian
  buster, unmaintained since 2015 and the libgnome-keyring one has not
  been updated for libgcrypt{11,20}-dev rename.
  
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnome-keyring
  Reverse-Depends
  ===
  * libgnomeui-0  (for libgnome-keyring0)
  * libgnomeui-dev(for libgnome-keyring-dev)
  
  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco 
src:libgnomeui
  Reverse-Depends
  ===
  * linsmith  (for libgnomeui-0)
  
  Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
  jak@jak-t480s:~/Projects/Ubuntu/Scratch$ reverse-depends -r disco src:linsmith
  Reverse-Recommends
  ==
  * electronics-radio-dev (for linsmith)
  * hamradio-antenna  (for linsmith)
  * science-electronics   (for linsmith)
  
  Packages without architectures listed are reverse-dependencies in:
  amd64, arm64, armhf, i386, ppc64el, s390x
  
- 
- Also, these other related packages do not have reverse dependencies either, 
and can be removed:
+ Also, these other related packages do not have reverse dependencies
+ either, and can be removed:
  
  $ reverse-depends -r eoan src:libbonoboui -b
  No reverse dependencies found
  $ reverse-depends -r eoan src:libgnome -b
  Reverse-Build-Depends
  =
  * libbonoboui   (for libgnome2-dev)
  
  $ reverse-depends -r eoan src:libbonobo -b
  Reverse-Build-Depends
  =
  * libbonoboui   (for libbonobo2-dev)
  * libgnome  (for libbonobo2-dev)
+ 
+ $ reverse-depends -r eoan src:gnome-vfs -b
+ Reverse-Build-Depends
+ =
+ * libgnome  (for libgnomevfs2-dev)

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

** Summary changed:

- Remove libgnome-keyring, libgnomeui, linsmith, and friendsd from eoan
+ Remove gnome 2 stack + linsmith from eoan

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

** Description changed:

  Please remove these packages from eoan. They are not shipped in Debian
  buster, 

[Touch-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Hui Wang]

After booting up, please run:

ls -la /dev/snd/   #could you see some dev nodes

aplay -l  # could you see some audio devices

sudo chmod a+rw /dev/snd/*
aplay -l # could you see some different output from the 1st time.

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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

-- 
Mailing list: https://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 1786574] Re: remove i2c-i801 from blacklist

[Khairul Aizat Kamarudzzaman]

Im still having this issue when booting from hibernate :(

On Thu, May 9, 2019, 16:56 Yuan-Chen Cheng 
wrote:

> ** Tags added: hwe oem-priority
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1786574
>
> Title:
>   remove i2c-i801 from blacklist
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/hwe-next/+bug/1786574/+subscriptions
>

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Cosmic:
  In Progress

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

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

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

[Touch-packages] [Bug 1828282] Re: busybox 1.30.1 crashes bzip2 test case with glibc 2.29, always

[Francis Ginther]

** Tags added: id-5cc732a8910db44841cff9f0

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

Title:
  busybox 1.30.1 crashes bzip2 test case with glibc 2.29, always

Status in Ubuntu on IBM z Systems:
  New
Status in busybox package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1) Get a system with glibc 2.29

  2) Get busybox 1.30.1 installed (e.g. eoan, or download busybox
  package from
  https://launchpad.net/ubuntu/+source/busybox/1:1.30.1-4ubuntu3/+build/16724246
  and use $ apt install ./busybox*.deb to install)

  3) Get busybox 1.30.1 source code, e.g. $ pull-lp-source busybox
  Or like download the orig tarball from 
https://launchpad.net/ubuntu/+source/busybox/1:1.30.1-4ubuntu3

  4) Run the bunzip2 testsuite:

  cd testsuite/
  ECHO=/bin/echo ./bunzip2.tests

  Observe that with glibc 2.29 the:
  PASS: bunzip2: bz2_issue_11.bz2 corrupted example

  is XFAIL or FAIL, on s390x, whereas it passes on all other arches.

  If one uses glibc 2.28 (ie. use Cosmic, and install busybox & use
  matching test suite from eoan using links above) one can observe that
  the testcase always passes.

  We suspect this might be a glibc 2.29 s390x-specific setjmp
  regression. Probably due to setjmp usage in
  ./archival/libarchive/decompress_bunzip2.c

  The tests were done on a z13 machine.

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

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