date:20180216

Only one package needs to be downgraded for apt-cdrom to work again: 
libapt-pkg5.0 to version: libapt-pkg5.0_1.6~alpha5

http://changelogs.ubuntu.com/changelogs/pool/main/a/apt/apt_1.6~alpha7ubuntu1/changelog

Links used for testing:
http://launchpadlibrarian.net/353920547/libapt-pkg5.0_1.6~alpha7_amd64.deb
http://launchpadlibrarian.net/353116448/libapt-pkg5.0_1.6~alpha6_amd64.deb
http://launchpadlibrarian.net/345537288/libapt-pkg5.0_1.6~alpha5_amd64.deb

For each ... I manually "dpkg -i" and then ran "apt-cdrom add".

Results:
libapt-pkg5.0_1.6~alpha7ubuntu1 = fails <-- stock Bionic 20180216 
libapt-pkg5.0_1.6~alpha7ubuntu = fails
libapt-pkg5.0_1.6~alpha6 = fails
libapt-pkg5.0_1.6~alpha5 = works  <-- Bionic 20180131

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

Title:
  18.04 daily installer fails missing kernel

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  "No installable kernel was found in the defined APT sources.

  You may try to continue without a kernel, and manually install your own 
kernel later.
  This is only recommended for experts, otherwise you will likely end up with a 
machine
  that doesn't boot.

  Continue without installing a kernel."

  Lubuntu Daily 18.04 dated 2018-February 1.

  note: yesterdays (Jan 31) install works fine.

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

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

[Touch-packages] [Bug 1746807] Re: 18.04 daily installer fails missing kernel

TLDR: try rebuilding the iso downgrading the four packages
/pool/main/a/apt/*.deb to 1.6~alpha 5?

Note: I pasted the info backwards...it's 1.6~alpha 5 that's the good
version.

As a test...I tried manually downgrading apt*.deb on-the fly:

I created a virtual machine with a second (empty) cdrom drive.  Once I
got the missing kernel:

I switch to alternate terminal..
chroot /target

"apt-cdrom add" gives same error...

Mounted the GOOD 20180131 iso into the vm as the second cdrom.
mkdir /blah
mount /dev/sr1 /blah
cd /blah/pool/main/a/apt
dpkg -i *.deb
cd /
umount /blah

i.e. force load previous apt and apt-cdrom packages.

apt-cdrom

This no longer gives the error.

Just as a test...

cd /media/cdrom/pool/main/a/apt  <-- original bad cdrom
dpkg -i *.deb

i.e. force load bad apt/apt-cdrom packages from latest 20180216

apt-cdrom

This gives the stat no such file or directory error.


So...downgrading the four packages /pool/main/a/apt/*.deb should work around 
the issue?

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

Title:
  18.04 daily installer fails missing kernel

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  "No installable kernel was found in the defined APT sources.

  You may try to continue without a kernel, and manually install your own 
kernel later.
  This is only recommended for experts, otherwise you will likely end up with a 
machine
  that doesn't boot.

  Continue without installing a kernel."

  Lubuntu Daily 18.04 dated 2018-February 1.

  note: yesterdays (Jan 31) install works fine.

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

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

[Touch-packages] [Bug 1738205] Re: no sound while playing audio/video

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

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

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

Title:
  no sound while playing audio/video

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Not able to hear audio through headset on ubuntu 14.04. Also, volume
  icon is not visible..

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-80-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu Dec 14 18:47:12 2017
  InstallationDate: Installed on 2016-02-04 (679 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: P01-A4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Veriton M6610
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAcer:bvrP01-A4:bd07/26/2011:svnAcer:pnVeritonSeries:pvr:rvnAcer:rnVeritonM6610:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Veriton Series
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1738605] Re: Yesterday I had sound. Today I don't.

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

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

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

Title:
  Yesterday I had sound. Today I don't.

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Happens every single time I install Ubuntu on every single computer I
  have ever install it on. This time, it doesn't seem to have a
  solution. Shows audio in volume control under output devices, but
  there is no sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.7
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  master 1752 F pulseaudio
   /dev/snd/pcmC0D0c:   master 1752 F...m pulseaudio
   /dev/snd/pcmC0D0p:   master 1752 F...m pulseaudio
   /dev/snd/controlC0:  master 1752 F pulseaudio
  Date: Sat Dec 16 23:23:28 2017
  InstallationDate: Installed on 2017-12-15 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Touch-packages] [Bug 1738404] Re: Bluetooth sound extreme low quality

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

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

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

Title:
  Bluetooth sound extreme low quality

Status in bluez package in Ubuntu:
  Expired

Bug description:
  I upgraded today from ubuntu 17.04 to ubuntu 17.10.

  I use 3 different bluetooth audio devices ( BT earphones, BT speaker,
  BT BOSE Soundlink speaker) , all of them worked properly on 17.04.

  Since the upgrade, the sound gets continuous interruptions/cracking. 
  These sound interruptions and cracking are so annoying that I cannot keep on 
listening to music.
  I could relate this to the fact that a new BT stack has replaced the former 
in Ubuntu.

  If I use wired devices (hdmi connected screen+audio, the sound quality is 
good and as before) so the issue is related to the use of the new Bluetooth 
stack.
  I have not found a way to parameterise it neither.

  I have not found any similar report. "apport" seems not ot exist in
  thise version, I cannot find and execute it.

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

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

[Touch-packages] [Bug 1738785] Re: package libxcursor1 1:1.1.14-1ubuntu0.14.04.1 failed to install/upgrade: 63.9316:package libxcursor1:amd64 1:1.1.14-1ubuntu0.14.04.1 cannot be configured because lib

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

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

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

Title:
  package libxcursor1 1:1.1.14-1ubuntu0.14.04.1 failed to
  install/upgrade: 63.9316:package libxcursor1:amd64
  1:1.1.14-1ubuntu0.14.04.1 cannot be configured because
  libxcursor1:i386 is at a different version (1:1.1.14-1)

Status in libxcursor package in Ubuntu:
  Expired

Bug description:
  Please let me know what is the solutions of this error?

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libxcursor1 1:1.1.14-1ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-133.182-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-133-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Dec 18 18:41:01 2017
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   oem-audio-hda-daily, 0.201508251546~ubuntu14.04.1, 3.13.0-133-generic, 
x86_64: installed
   oem-audio-hda-daily, 0.201508251546~ubuntu14.04.1, 3.13.0-137-generic, 
x86_64: built
   oem-audio-hda-daily, 0.201508251546~ubuntu14.04.1, 3.13.0-45-generic, 
x86_64: installed
   wifi-bt-dw1820b, 1.1, 3.13.0-133-generic, x86_64: installed
   wifi-bt-dw1820b, 1.1, 3.13.0-45-generic, x86_64: installed
  DuplicateSignature: 
package:libxcursor1:1:1.1.14-1ubuntu0.14.04.1:63.9316:package libxcursor1:amd64 
1:1.1.14-1ubuntu0.14.04.1 cannot be configured because libxcursor1:i386 is at a 
different version (1:1.1.14-1)
  ErrorMessage: 63.9316:package libxcursor1:amd64 1:1.1.14-1ubuntu0.14.04.1 
cannot be configured because libxcursor1:i386 is at a different version 
(1:1.1.14-1)
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:06f0]
  InstallationDate: Installed on 2017-10-09 (70 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Latitude 3460
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-133-generic.efi.signed 
root=UUID=7daf6ad4-13cf-4d52-bba5-f4cf9cfacda8 ro locale=en_IN quiet splash 
pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 
vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: libxcursor
  Title: package libxcursor1 1:1.1.14-1ubuntu0.14.04.1 failed to 
install/upgrade: 63.9316:package libxcursor1:amd64 1:1.1.14-1ubuntu0.14.04.1 
cannot be configured because libxcursor1:i386 is at a different version 
(1:1.1.14-1)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0XPKP0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/02/2017:svnDellInc.:pnLatitude3460:pvr:rvnDellInc.:rn0XPKP0:rvrA04:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3460
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1.01
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.7
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Dec 18 11:05:50 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5264 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2.11

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

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

[Touch-packages] [Bug 1707898] Re: systemd translations are not synced with upstream

2018-02-16 Thread Gunnar Hjalmarsson

Since moving polkit.{its,loc} would affect other packages, I made
another effort to fix it within systemd, and I think I made it this
time. Please see the attached patch (for Debian).

It's new variant of xgettext() call, but this time it makes use of
polkit.its from the systemd source. It's a bit ugly; the "|| true" is
there to compensate for a segmentation fault, but that happens only
after xgettext() has done its job, so systemd.pot actually gets updated.

It's worth mentioning that the upstream source currently includes
po/its/polkit.{its,loc}, but OTOH - as a result of the upstream issue I
submitted - they are about to drop those files. So that's the reason why
the patch adds polkit.its.

** Patch added: "0001-Extract-translatable-strings-from-policy-files.patch"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1707898/+attachment/5057015/+files/0001-Extract-translatable-strings-from-policy-files.patch

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

Title:
  systemd translations are not synced with upstream

Status in systemd:
  New
Status in Ubuntu Translations:
  New
Status in policykit-1 package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Translations for systemd are outdated because they do not seem to be
  synced with the upstream ones.

  For example the Czech one:
  Launchpad: 
https://translations.launchpad.net/ubuntu/artful/+source/systemd/+pots/systemd/cs/+translate
 - 0% translated
  Upstream: https://github.com/systemd/systemd/blob/master/po/cs.po - 100% 
translated

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

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

[Touch-packages] [Bug 1746807] Re: 18.04 daily installer fails missing kernel

p.s. Simon, Steve, Julian thanks for your assistance.

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

Title:
  18.04 daily installer fails missing kernel

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  "No installable kernel was found in the defined APT sources.

  You may try to continue without a kernel, and manually install your own 
kernel later.
  This is only recommended for experts, otherwise you will likely end up with a 
machine
  that doesn't boot.

  Continue without installing a kernel."

  Lubuntu Daily 18.04 dated 2018-February 1.

  note: yesterdays (Jan 31) install works fine.

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

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

[Touch-packages] [Bug 1746807] Re: 18.04 daily installer fails missing kernel

When the install was in progress on the good/at the point of failure on
the bad I did:

control-f2 to activate another terminal
chroot /target
apt
apt-cdrom

good 20180130: apt 1.6~alpha 7 (amd64)
bad 20180216 : apt 1.6~alpha 5 (amd64)

So yes, the version of apt/apt-cdrom is different.

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

Title:
  18.04 daily installer fails missing kernel

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  "No installable kernel was found in the defined APT sources.

  You may try to continue without a kernel, and manually install your own 
kernel later.
  This is only recommended for experts, otherwise you will likely end up with a 
machine
  that doesn't boot.

  Continue without installing a kernel."

  Lubuntu Daily 18.04 dated 2018-February 1.

  note: yesterdays (Jan 31) install works fine.

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

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

[Touch-packages] [Bug 1750085] [NEW] d

2018-02-16 Thread Pedro Rodriguez

Public bug reported:

d

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Feb 16 19:21:09 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[1028:0577]
InstallationDate: Installed on 2018-02-12 (4 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
MachineType: Dell Inc. OptiPlex 7010
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f0fb8733-b752-4d96-a6b4-0265d1c7e1a8 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/09/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 0YXT71
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/09/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0YXT71:rvrA02:cvnDellInc.:ct3:cvr:
dmi.product.name: OptiPlex 7010
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  d

Status in xorg package in Ubuntu:
  New

Bug description:
  d

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Feb 16 19:21:09 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[1028:0577]
  InstallationDate: Installed on 2018-02-12 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. OptiPlex 7010
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f0fb8733-b752-4d96-a6b4-0265d1c7e1a8 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/09/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0YXT71
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/09/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0YXT71:rvrA02:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 7010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

-- 
Mailing list: https://launchpad.net/~touch-packages
P

[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2018-02-16 Thread Steve Langasek

Marking open-iscsi high, because passing the configured network
interface from initramfs to root system needs to be done cleanly in the
non-resolvconf world (though this is likely going to be handled via
netplan rather than directly to resolved).

** Changed in: open-iscsi (Ubuntu)
   Importance: Medium => High

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

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  Triaged
Status in avahi package in Ubuntu:
  Triaged
Status in bind9 package in Ubuntu:
  Triaged
Status in cloud-init package in Ubuntu:
  Incomplete
Status in cloud-initramfs-tools package in Ubuntu:
  Invalid
Status in dhcpcd5 package in Ubuntu:
  New
Status in dibbler package in Ubuntu:
  Won't Fix
Status in dnscrypt-proxy package in Ubuntu:
  Confirmed
Status in dnsmasq package in Ubuntu:
  Invalid
Status in dnssec-trigger package in Ubuntu:
  Invalid
Status in fetchmail package in Ubuntu:
  Confirmed
Status in freedombox-setup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in ndisc6 package in Ubuntu:
  Fix Released
Status in netscript-2.4 package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  Triaged
Status in openvpn package in Ubuntu:
  Confirmed
Status in postfix package in Ubuntu:
  New
Status in pppconfig package in Ubuntu:
  Confirmed
Status in pump package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid
Status in sendmail package in Ubuntu:
  New
Status in squid3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in unbound package in Ubuntu:
  New
Status in vpnc package in Ubuntu:
  Invalid
Status in vpnc-scripts package in Ubuntu:
  Invalid
Status in whereami package in Ubuntu:
  Triaged

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

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

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

[Touch-packages] [Bug 1749722] Re: NTP: take into account systemd-timesyncd where present

2018-02-16 Thread Ryan Harper

Some further looking at the systemd side, Bionic no longer carries the
override conf (disable-with-time-daemon.conf) in favor of updating each
client's systemd unit to use:

Conflicts=systemd-timesyncd.service

Conflicts will ensure that the target service is stopped if the current
unit is started. So, if ntp or chrony unit were to start, it would stop
timesyncd.

This is roughly equivalent, however, it does leave timesyncd unit
enabled.  This means that if something starts systemd-timesyncd.service,
it would stop the ntp or chrony service.

There may be additional work on each of the time packages to *disable*
timesyncd unit when installed such that it won't start.  This may not be
possible to prevent users from starting timesyncd manually.

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

Title:
  NTP: take into account systemd-timesyncd where present

Status in cloud-init:
  In Progress
Status in systemd package in Ubuntu:
  New

Bug description:
  Currently, the NTP module configures ntpd during cloud-init install by
  installing and configuring ntpd.

  ntpd competes with systemd-timesyncd on systemd distros like Ubuntu
  Xenial.

  Ideally the NTP module should configure systemd-timesyncd where
  present, falling back to ntpd where not present.

  This stops two separate daemons (ntpd and systemd-timesyncd) competing
  with each other to set the time, where systemd-timesyncd (on Ubuntu at
  least) has an internal hardcoded compiled in timeserver to fall back
  on if no timeserver is configured (which is bad, but what can you do).

  The competing timeserver behaviour is invisible when the machine can
  see the net, but logs this error constantly when the machine cannot
  see the net:

  systemd-timesyncd[527]: Timed out waiting for reply from
  91.189.94.4:123 (ntp.ubuntu.com).

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

-- 
Mailing list: https://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 1725861] Re: APT::AutoRemove::SuggestsImportant "false" should be the default

2018-02-16 Thread Steve Langasek

On Fri, Feb 16, 2018 at 10:04:10PM -, Julian Andres Klode wrote:
> Unsupported and no longer available packages can be dealt with better by
> extending u-r-u, for example. They are not a valid argument for
> autoremoving packages still suggested by other packages.

> As I mentioned before, it seems reasonable to me that u-r-u would
> autoremove more than apt by setting SuggestsImportant to false. That
> solves (well, it improves, it's not an optimal solution) the problem of
> accumulated cruft during dist upgrades while at the same time not
> affecting operation on a running system.

Sure, I'm fine with the notion of this being handled in u-r-u instead of in
apt itself; but the general problem of cruft left behind across upgrades
should not be ignored.

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

Title:
  APT::AutoRemove::SuggestsImportant "false" should be the default

Status in apt package in Ubuntu:
  Triaged
Status in apt source package in Bionic:
  Triaged

Bug description:
  After an upgrade to 17.10, I took a look at how much cruft I had
  accumulated on my system, and started marking various packages 'auto'
  which I know I don't care about keeping installed.

  apt autoremove didn't remove nearly as much stuff as I expected, and
  as I dug down into some of them I found that a number of them were
  being kept because other packages on the system have Suggests:
  referencing them.

  This is asymmetric and wrong.  If Suggested packages are not
  automatically installed by default, then a Suggests should also not
  prevent a package from being automatically removed.

  After a web search led me to 'https://askubuntu.com/questions/351085
  /how-to-remove-recommended-and-suggested-dependencies-of-uninstalled-
  packages', I set 'APT::AutoRemove::SuggestsImportant "false"' in my
  apt config; apt autoremove now wants to remove 365MiB of packages from
  my system.  That is a LOT of cruft that has accumulated over the years
  of upgrades, none of which I have ever asked to be installed and all
  of which were universe or no-longer-available packages.

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

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

[Touch-packages] [Bug 1725861] Re: APT::AutoRemove::SuggestsImportant "false" should be the default

2018-02-16 Thread Julian Andres Klode

Unsupported and no longer available packages can be dealt with better by
extending u-r-u, for example. They are not a valid argument for
autoremoving packages still suggested by other packages.

As I mentioned before, it seems reasonable to me that u-r-u would
autoremove more than apt by setting SuggestsImportant to false. That
solves (well, it improves, it's not an optimal solution) the problem of
accumulated cruft during dist upgrades while at the same time not
affecting operation on a running system.

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

Title:
  APT::AutoRemove::SuggestsImportant "false" should be the default

Status in apt package in Ubuntu:
  Triaged
Status in apt source package in Bionic:
  Triaged

Bug description:
  After an upgrade to 17.10, I took a look at how much cruft I had
  accumulated on my system, and started marking various packages 'auto'
  which I know I don't care about keeping installed.

  apt autoremove didn't remove nearly as much stuff as I expected, and
  as I dug down into some of them I found that a number of them were
  being kept because other packages on the system have Suggests:
  referencing them.

  This is asymmetric and wrong.  If Suggested packages are not
  automatically installed by default, then a Suggests should also not
  prevent a package from being automatically removed.

  After a web search led me to 'https://askubuntu.com/questions/351085
  /how-to-remove-recommended-and-suggested-dependencies-of-uninstalled-
  packages', I set 'APT::AutoRemove::SuggestsImportant "false"' in my
  apt config; apt autoremove now wants to remove 365MiB of packages from
  my system.  That is a LOT of cruft that has accumulated over the years
  of upgrades, none of which I have ever asked to be installed and all
  of which were universe or no-longer-available packages.

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

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

[Touch-packages] [Bug 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)

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

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

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

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

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

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

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

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

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

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

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

Title:
  systemd-logind: memory leaks on session's connections (trusty-only)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  In Progress
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  It was observed that systemd-logind tool is leaking memory at each session
  connected. The issue happens in systemd from Trusty (14.04), which latest
  version currently (Feb/2018) is 204-5ubuntu20.26 (and still reproduces
  the bug).

  The basic test-case is to run the following loop from a remote
  machine:

  while true; do ssh  "whoami"; done

  and watch the increase in memory consumption from "systemd-logind" process
  in the target machine. One can use the "ps uax" command to verify the
  RSS of the process, or count the anon pages from /proc//smaps.

  To clarify a bit how a session works, the following "stack trace" details
  a bit which function calls happen when a SSH connection is opened, from
  Trusty's systemd-logind point of view:

  
  main() 
  manager_startup()
  manager_run() [event-loop]
  bus_loop_dispatch() 
  dbus_watch_handle() -> bus_manager_message_handler()
  bus_manager_create_session()
  manager_add_session() 
  session_new() 
  session_create_fifo()
  session_start()
  session_create_cgroup()
  session_save()
  session_bus_path()
  [...]

  After each session is closed, it was observed that session_free() isn't
  called, keeping the sessions alive. This can be verified through the
  command "loginctl list-session" - each session that once connected is
  present there "forever".

  The memory leaks can eventually lead to OOM situation of this process.
  Debug progress will be tracked here, in this LP.

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

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

[Touch-packages] [Bug 1715931] Re: Update to exiv2 version 0.26

2018-02-16 Thread Rik Mills

Seems not

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

Title:
  Update to exiv2 version 0.26

Status in exiv2 package in Ubuntu:
  Triaged
Status in exiv2 source package in Bionic:
  Triaged

Bug description:
  0.26 was released in April

  http://www.exiv2.org/whatsnew.html

  "This release contains a large collection of new features, new lenses
  and bugfixes across all areas of Exiv2. "

  Presumably debian stretch freeze interfered with a prompter update

  Currently in debian exp here:

  https://packages.debian.org/experimental/exiv2

  I was hoping to to get a new feature release of the very popular
  Digikam (5.7.0) into artful under a FFE, but that has bumped the
  minimum exiv2 build depend from 0.25 -> 0.26.

  If due to rdeps etc an update in artful turns out not to be possible,
  I would like to target this for early in 18.04 LTS cycle.

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

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

[Touch-packages] [Bug 1701161] Re: black terminal

christy yosua sasauw, thank you for reporting this and helping make
Ubuntu better.

To advise, your release has been EOL since July 28, 2016 as per
https://wiki.ubuntu.com/Releases .

Could you please update to a supported release via
http://cdimage.ubuntu.com/daily-live/current/ and advise if this is
reproducible?

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

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

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

Title:
  black terminal

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  my terminal becoms black all

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jun 29 12:32:32 2017
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fdd0]
  InstallationDate: Installed on 2016-10-16 (255 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  MachineType: TOSHIBA Satellite L740
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=5c492036-60d3-4079-8608-60181e27aac2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.50
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.50:bd04/12/2012:svnTOSHIBA:pnSatelliteL740:pvrPSK6XL-00C002:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L740
  dmi.product.version: PSK6XL-00C002
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.libdrm2: libdrm2 2.4.65-3
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.4-1intel1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Jun 29 11:43:33 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 760 
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Touch-packages] [Bug 1702140] Re: freeze system again adn again

ajay luthra, thank you for reporting this and helping make Ubuntu
better.

1) Is this something that started to happen after an update? If so,
which specifically?

2) To see if this is already resolved in your release, could you please
update your HWE stack as per
https://wiki.ubuntu.com/Kernel/LTSEnablementStack and advise to the
results?

** Tags added: bios-outdated-r0200z9

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

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

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

Title:
  freeze system again adn again

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  every three and four hours system will be freeze. i need help

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jul  3 22:48:38 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-83-generic, x86_64: installed
   nvidia-340, 340.102, 4.4.0-83-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GF119M [GeForce 410M] [10de:1055] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Sony Corporation GF119M [GeForce 410M] [104d:908b]
  InstallationDate: Installed on 2017-06-30 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Sony Corporation VPCEH25EN
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=53b92317-9503-44fe-bd39-9bbb573646ad ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R0190Z9
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDE:bvrR0190Z9:bd11/17/2011:svnSonyCorporation:pnVPCEH25EN:pvrC105Z9ZK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCEH25EN
  dmi.product.version: C105Z9ZK
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.81+git20170630.3095cc8e-0ubuntu0ricotz~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 
17.1.4~git20170629+17.1.03a0fdbd-0ubuntu0ricotz~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
17.1.4~git20170629+17.1.03a0fdbd-0ubuntu0ricotz~16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.8.99+git20170208.1351e48e-0ubuntu0ricotz2~xenial
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170208.e4fe79cf-0ubuntu0ricotz~xenial
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.13+git20170208.1516d35b-0ubuntu0ricotz~xenial
  xserver.bootTime: Mon Jul  3 22:23:30 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

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

-- 
Mailing list: https://launchp

[Touch-packages] [Bug 1725861] Re: APT::AutoRemove::SuggestsImportant "false" should be the default

2018-02-16 Thread Steve Langasek

Balint, if you think this is about disk space, I'm afraid you've missed
my point.  These packages are individually tiny.  The point is that
365MiB of packages is a *lot* of packages - all of which are
unsupported, many of which are no longer available in Ubuntu at all
anymore, each of which represents a change in behavior between an
upgraded system and a newly installed system that causes a combinatoric
explosion of possible configurations in Ubuntu's "supported" upgrade
path - "supported" in quotes, because in practice, any time a user
stumbles because of such a difference, they will categorically told by
the developers to remove the unsupported package.

The default behavior of Ubuntu should give users systems which, on
upgrade, are as well-supported and supportable as new installs.  The
current behavior, in its asymmetry, does not give us that.  The tools
are wrong.

** Changed in: apt (Ubuntu Bionic)
   Status: Incomplete => 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/1725861

Title:
  APT::AutoRemove::SuggestsImportant "false" should be the default

Status in apt package in Ubuntu:
  Triaged
Status in apt source package in Bionic:
  Triaged

Bug description:
  After an upgrade to 17.10, I took a look at how much cruft I had
  accumulated on my system, and started marking various packages 'auto'
  which I know I don't care about keeping installed.

  apt autoremove didn't remove nearly as much stuff as I expected, and
  as I dug down into some of them I found that a number of them were
  being kept because other packages on the system have Suggests:
  referencing them.

  This is asymmetric and wrong.  If Suggested packages are not
  automatically installed by default, then a Suggests should also not
  prevent a package from being automatically removed.

  After a web search led me to 'https://askubuntu.com/questions/351085
  /how-to-remove-recommended-and-suggested-dependencies-of-uninstalled-
  packages', I set 'APT::AutoRemove::SuggestsImportant "false"' in my
  apt config; apt autoremove now wants to remove 365MiB of packages from
  my system.  That is a LOT of cruft that has accumulated over the years
  of upgrades, none of which I have ever asked to be installed and all
  of which were universe or no-longer-available packages.

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

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

[Touch-packages] [Bug 1702495] Re: touchpad too sensitive

Digjam Sarma, thank you for reporting this and helping make Ubuntu
better.

1) Is this something that started to happen after an update? If so,
which specifically?

2) To see if this is already resolved in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

** Tags added: bios-outdated-f.47

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

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

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

Title:
  touchpad too sensitive

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The mouse cursor moves even when i move my fingers over the touchpad
  in the air(without touching it) but doesnt move at all when i use the
  touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jul  5 20:00:11 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:1854]
  InstallationDate: Installed on 2017-06-27 (8 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  MachineType: Hewlett-Packard HP 450 Notebook PC
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic 
root=UUID=159622e6-6a00-43f4-baad-7b2d60cb8bd8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.3C
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1854
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 64.2A
  dmi.chassis.asset.tag: 5CG347B4F2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.3C:bd10/11/2013:svnHewlett-Packard:pnHP450NotebookPC:pvr088612005B1600010:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 450 Notebook PC
  dmi.product.version: 088612005B1600010
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Jul  5 19:48:09 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
  xserver.video_driver: modeset

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

-- 
Mailing list: https://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 1748709] Re: Upgrade from xenial to bionic wants to replace moduli

2018-02-16 Thread Seth Arnold

On Fri, Feb 16, 2018 at 11:45:56AM -, ChristianEhrhardt wrote:
> So maybe (but only maybe) a ssh-extra-security package doing so as
> suggests or helper tool bundled to openssh that would do the update
> might be a nice security addition.  I'm adding the security Team to
> weight in on opinions:
> - should it be unique per system?

It is fine for this file to be shared amongst all OpenSSH users.

A cryptographer friend and I discussed the wisdom of self-generating DH
primes recently. He was strongly of the opinion that well-vetted primes
should be preferred over randomly-selected primes. Some numbers have
vastly weaker performance against the generalized number field sieve
than other numbers.

> - if so, preferred delivery mechanism

Packaging upstream's as a config file makes sense to me. Local sites can
replace it, and if they understand the risks it may make sense.

> - might an individual generated moduli file decrease security compared
> to a "curated and reviewed" shared one? There are mentions of
> "Ssh-keygen’s primality tests are statistical tests and can lead to
> false positives." that make me think so.

The statistical primality tests worry me less than performance of the
purported prime numbers against the GNFS in the precomputation steps that
lead to an attack. I believe this is the weakest link in the chain and
reason enough to stick with numbers shared with upstream.

Thanks

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

Title:
  Upgrade from xenial to bionic wants to replace moduli

Status in openssh package in Ubuntu:
  New

Bug description:
  I see this on upgrade on one machine, which is unexpected. If this
  file is generated by each machine, why would we ship a default?

  Configuration file '/etc/ssh/moduli'
   ==> Modified (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.
  *** moduli (Y/I/N/O/D/Z) [default=N] ?

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

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

[Touch-packages] [Bug 1750051] [NEW] cron doesn't support MAILFROM

2018-02-16 Thread Simon Déziel

Public bug reported:

Ubuntu's cron version doesn't support setting MAILFROM to set the
"From:" header of cron generated emails. This feature would be nice to
have and bring parity with RHEL/CentOS which has it since RHEL 6:

$ cat /etc/redhat-release 
CentOS release 6.6 (Final)

$ man 5 crontab | grep -1 FROM
   doesn´t do aliasing, and UUCP usually doesn´t read its mail.  If  MAIL-
   FROM is defined (and non-empty), it will be used as the envelope sender
   address, otherwise, ‘‘root’’ will be used.

$ apt-cache policy cron
cron:
  Installed: 3.0pl1-128ubuntu2
  Candidate: 3.0pl1-128ubuntu2
  Version table:
 *** 3.0pl1-128ubuntu2 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cron 3.0pl1-128ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 16 15:52:54 2018
InstallationDate: Installed on 2016-12-06 (436 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 
(20161206)
SourcePackage: cron
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  cron doesn't support MAILFROM

Status in cron package in Ubuntu:
  New

Bug description:
  Ubuntu's cron version doesn't support setting MAILFROM to set the
  "From:" header of cron generated emails. This feature would be nice to
  have and bring parity with RHEL/CentOS which has it since RHEL 6:

  $ cat /etc/redhat-release 
  CentOS release 6.6 (Final)

  $ man 5 crontab | grep -1 FROM
 doesn´t do aliasing, and UUCP usually doesn´t read its mail.  If  MAIL-
 FROM is defined (and non-empty), it will be used as the envelope sender
 address, otherwise, ‘‘root’’ will be used.

  $ apt-cache policy cron
  cron:
Installed: 3.0pl1-128ubuntu2
Candidate: 3.0pl1-128ubuntu2
Version table:
   *** 3.0pl1-128ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cron 3.0pl1-128ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 16 15:52:54 2018
  InstallationDate: Installed on 2016-12-06 (436 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 
(20161206)
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1615381] Re: apt-get autoremove may remove current kernel

... /etc/kernel/postinst.d/apt-auto-removal was run.

** Changed in: unattended-upgrades (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/1615381

Title:
  apt-get autoremove may remove current kernel

Status in apt package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  This may happen, if you boot one of the older kernels, that is not
  protected by /etc/apt/apt.conf.d/01autoremove-kernels

  Workaround: run
  /etc/kernel/postinst.d/apt-auto-removal
  during each boot (e.g. by using cron).
  Note: The workaround breaks autoremoving feature of new unneeded kernels in  
unattended-upgrades i.e. the setting 
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default 
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set 
in '/etc/apt/apt.conf.d/50unattended-upgrades'.

  
  In shell:

  $ uname -r
  4.4.0-22-generic
  $ apt-get -s autoremove
  NOTE: This is only a simulation!
    apt-get needs root privileges for real execution.
    Keep also in mind that locking is deactivated,
    so don't depend on the relevance to the real current situation!
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED:
    linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
    linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
    linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
    linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
    linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
  0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Aug 21 16:11:27 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (114 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified]
  mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 
2016-07-30T12:15:32.706300

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

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

[Touch-packages] [Bug 1615381] Re: apt-get autoremove may remove current kernel

In default configuration booted kernel does not become newly unused, but
when u-u is configured to remove all autoremovable packages the booted
kernel can be removed in case it was not running when was run.


** Also 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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1615381

Title:
  apt-get autoremove may remove current kernel

Status in apt package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  This may happen, if you boot one of the older kernels, that is not
  protected by /etc/apt/apt.conf.d/01autoremove-kernels

  Workaround: run
  /etc/kernel/postinst.d/apt-auto-removal
  during each boot (e.g. by using cron).
  Note: The workaround breaks autoremoving feature of new unneeded kernels in  
unattended-upgrades i.e. the setting 
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default 
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set 
in '/etc/apt/apt.conf.d/50unattended-upgrades'.

  
  In shell:

  $ uname -r
  4.4.0-22-generic
  $ apt-get -s autoremove
  NOTE: This is only a simulation!
    apt-get needs root privileges for real execution.
    Keep also in mind that locking is deactivated,
    so don't depend on the relevance to the real current situation!
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED:
    linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
    linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
    linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
    linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
    linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
  0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Aug 21 16:11:27 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (114 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified]
  mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 
2016-07-30T12:15:32.706300

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

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

[Touch-packages] [Bug 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)

2018-02-16 Thread Dan Streetman

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

** Also affects: systemd (Ubuntu Bionic)
   Importance: Medium
 Assignee: Guilherme G. Piccoli (gpiccoli)
   Status: In Progress

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

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

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

Title:
  systemd-logind: memory leaks on session's connections (trusty-only)

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Trusty:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Artful:
  New
Status in systemd source package in Bionic:
  In Progress

Bug description:
  It was observed that systemd-logind tool is leaking memory at each session
  connected. The issue happens in systemd from Trusty (14.04), which latest
  version currently (Feb/2018) is 204-5ubuntu20.26 (and still reproduces
  the bug).

  The basic test-case is to run the following loop from a remote
  machine:

  while true; do ssh  "whoami"; done

  and watch the increase in memory consumption from "systemd-logind" process
  in the target machine. One can use the "ps uax" command to verify the
  RSS of the process, or count the anon pages from /proc//smaps.

  To clarify a bit how a session works, the following "stack trace" details
  a bit which function calls happen when a SSH connection is opened, from
  Trusty's systemd-logind point of view:

  
  main() 
  manager_startup()
  manager_run() [event-loop]
  bus_loop_dispatch() 
  dbus_watch_handle() -> bus_manager_message_handler()
  bus_manager_create_session()
  manager_add_session() 
  session_new() 
  session_create_fifo()
  session_start()
  session_create_cgroup()
  session_save()
  session_bus_path()
  [...]

  After each session is closed, it was observed that session_free() isn't
  called, keeping the sessions alive. This can be verified through the
  command "loginctl list-session" - each session that once connected is
  present there "forever".

  The memory leaks can eventually lead to OOM situation of this process.
  Debug progress will be tracked here, in this LP.

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

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

[Touch-packages] [Bug 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)

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

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

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

Title:
  systemd-logind: memory leaks on session's connections (trusty-only)

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  It was observed that systemd-logind tool is leaking memory at each session
  connected. The issue happens in systemd from Trusty (14.04), which latest
  version currently (Feb/2018) is 204-5ubuntu20.26 (and still reproduces
  the bug).

  The basic test-case is to run the following loop from a remote
  machine:

  while true; do ssh  "whoami"; done

  and watch the increase in memory consumption from "systemd-logind" process
  in the target machine. One can use the "ps uax" command to verify the
  RSS of the process, or count the anon pages from /proc//smaps.

  To clarify a bit how a session works, the following "stack trace" details
  a bit which function calls happen when a SSH connection is opened, from
  Trusty's systemd-logind point of view:

  
  main() 
  manager_startup()
  manager_run() [event-loop]
  bus_loop_dispatch() 
  dbus_watch_handle() -> bus_manager_message_handler()
  bus_manager_create_session()
  manager_add_session() 
  session_new() 
  session_create_fifo()
  session_start()
  session_create_cgroup()
  session_save()
  session_bus_path()
  [...]

  After each session is closed, it was observed that session_free() isn't
  called, keeping the sessions alive. This can be verified through the
  command "loginctl list-session" - each session that once connected is
  present there "forever".

  The memory leaks can eventually lead to OOM situation of this process.
  Debug progress will be tracked here, in this LP.

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

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

[Touch-packages] [Bug 1718568] Re: dhclient-script fails to wait for link-local address

2018-02-16 Thread Dan Streetman

** Changed in: isc-dhcp (Ubuntu Zesty)
   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 isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1718568

Title:
  dhclient-script fails to wait for link-local address

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Xenial:
  In Progress
Status in isc-dhcp source package in Zesty:
  Won't Fix
Status in isc-dhcp source package in Artful:
  In Progress
Status in isc-dhcp source package in Bionic:
  In Progress
Status in isc-dhcp package in Debian:
  New

Bug description:
  [impact]

  bug 1633479 made a change to isc-dhcp to wait for an interface's link-local 
ipv6 address to switch from 'tentative' to normal, because all link-local 
addresses briefly go through a 'tentative' state while the kernel is performing 
ipv6 link-local 'duplicate address detection' (DAD).  While in the 'tentative' 
state, dhclient can't take over the interface and send out
  dhcpv6 requests; it must wait until DAD completes.

  However, the change made in that bug does not account for the case
  where the 'tentative' check is done before the interface has even set
  up a link-local address; its case statement assumes if there is no
  'tentative' or 'dadfailed' string in the output, the link-local
  address is ready to use.  When the address check finds no address at
  all, this will return as successful, even though it shouldn't, and
  dhclient will fail to get the dhcpv6 address.

  [test case]

  on a system that is configured for dhcpv6 on one or more of its
  interfaces, repeatedly try to get the dhcpv6 address.  For interfaces
  that are slower to actually set up their initial tentative link-local
  address, they will occasionally fail, since the current code is a race
  between the kernel adding the tentative link-local address, and the
  dhclient-script.linux code checking the interface for a tentative
  address.

  with the patch to correct this, even interfaces slow to add their
  tentative link-local address should correctly wait for the address to
  get added, and then transition from tentative to normal, and then
  begin the dhcpv6 process.

  [regression potential]

  errors in this function can cause dhclient to fail to get a ipv6
  address for an interface; regression would happen if this patch makes
  it fail more than it already is failing, but would not cause other
  failures or problems after getting an ipv6 address; this patch will
  affect only startup-time.

  [other info]

  related bug 1633479

  
  [original description]

  
  Summary:
  

  If a interface does not yet have a link-local address (as it may have
  just been brought up), dhclient -6  will fail. The built-in
  "wait for link-local address" loop does not function properly, causing
  DHCP failure.

  Discussion:
  ===

  In trying to configure isc-dhcp-client 4.3.5-3ubuntu1 for IPv6 on
  Ubuntu 17.04, I was finding that on boot I was getting failures with
  the logged message "no link-local IPv6 address for "

  I found that it took several seconds for the link-local address to be
  assigned when the interface came up (in this case, the ISP/modem-
  facing interface), and worked around it with a script that looks at

    /sbin/ifconfig $IFACE | /bin/fgrep -q 'scopeid 0x20'

  and loops for a fixed number of times for that to be successful.

  On looking at /sbin/dhclient-script it appears that it *tries* to do
  the same thing in

    # set the link up and wait for ipv6 link local dad to finish
    ipv6_link_up_and_dad()

  this code sets

    out=$(ip -6 -o address show dev "$dev" scope link)

  then checks it with a case statement inside of a loop for

  case " $out " in
  *\ dadfailed\ *)
  error "$dev: ipv6 dad failed."
  return 1;;
  *\ tentative\ *) :;;
  *) return 0;;
  esac

  If there is no link-local address, $out will be empty. The default
  case is taken, and the loop exits immediately:

  $ echo "'$out'" ; case " $out " in
  > *\ dadfailed\ *)
  > echo "dadfailed"
  > ;;
  > *\ tentative\ *)
  > echo "tentative"
  > ;;
  > *)
  > echo "default"
  > esac
  ''
  default

  As a result, there is no "wait for link-local address" and when there
  is no link-local address, dhclient fails later on.

  Possible Fix:
  =

  Adding "the missing case" for "no address" case that continues the
  loop is one possible solution.

  .case " $out " in
  .*\ dadfailed\ *)
  .error "$dev: ipv6 dad failed."
  .return 1;;
  .*\ tentative\ *) :;;
  +    "  ")
  +    :
  +    ;;
  .*) return 0;;
  .esac

  At least in my situation,

[Touch-packages] [Bug 1702347] Re: Graphical glitches in screen by default on 17.10 & 18.04

lotuspsychje, thank you for reporting this and helping make Ubuntu
better. Regarding only the Acer Aspire 7530:

1) Is this something that started to happen after an update? If so,
which?

2) Could you please post a screenshot or picture of the glitching?

3) When testing the nvidia proprietary drivers, which of the following did you 
test:
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340-updates
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340

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

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

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

Title:
  Graphical glitches in screen by default on 17.10 & 18.04

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10 development branch

  updated and dist-upgraded on 4 july 2017

  Im having weird glitches in screen when scrolling or switching windows
  by default

  Graphics:  Card: NVIDIA C77 [GeForce 9100M G]
 Display Server: X.Org 1.19.3 drivers: nouveau (unloaded: 
modesetting,fbdev,vesa)
 Resolution: 1440x900@60.00hz
 GLX Renderer: Gallium 0.4 on NVAA GLX Version: 3.0 Mesa 17.1.2

  installing nvidia-340 resulted in a black screen after login, so i had to 
purge nvidia* to get
  back to desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jul  4 20:59:21 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.8, 4.10.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation C77 [GeForce 9100M G] [10de:0844] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Acer Incorporated [ALI] C77 [GeForce 9100M G] [1025:014d]
  InstallationDate: Installed on 2017-06-13 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170612)
  MachineType: Acer, inc. Aspire 7530
  ProcEnviron:
   LANGUAGE=nl_BE:nl
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=e65dc3e3-3694-4b7c-b7c8-7e9cfe3cbd5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/01/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v1.3342
  dmi.board.name: EI Capitan
  dmi.board.vendor: Acer, Inc.
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrv1.3342:bd10/01/2008:svnAcer,inc.:pnAspire7530:pvrNotApplicable:rvnAcer,Inc.:rnEICapitan:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
  dmi.product.name: Aspire 7530
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer, inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.81-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Jul  4 20:45:53 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   event6  - (EE) SynPS/2 Synaptics TouchPad: (EE) kernel bug: Touch jump 
detected and discarded.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu2
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1698159] Re: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies

** Tags added: rls-bb-incoming

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

Title:
  linux-cloud-tools version specific packages are being removed by
  unattended-upgrade's  Remove-Unused-Dependencies

Status in apt package in Ubuntu:
  Triaged
Status in unattended-upgrades package in Ubuntu:
  Triaged

Bug description:
  When running kernel version 4.4.0-78 (for example) and the unattended-
  upgrade packages installs a new kernel 4.4.0-79 (for example) the
  linux-cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic
  packages are removed by the Remove-Unused-Dependencies rule, because
  unlike "normal" kernel packages they are not excluded by
  /etc/apt/apt.conf.d/01autoremove-kernels.

  The linux-cloud-tools package has the hyper-v integration services
  daemons in it, so it's deletion leaves some of the integration not
  working.

  Could /etc/apt/apt.conf.d/01autoremove-kernels be updated so other
  hyper-v users aren't caught out by this?

  Thanks,

  Ian.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.6
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun 15 15:27:35 2017
  InstallationDate: Installed on 2016-04-25 (415 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic: [modified]
  modified.conffile..etc.update-motd.d.90-updates-available: [deleted]
  modified.conffile..etc.update-motd.d.98-fsck-at-reboot: [deleted]
  modified.conffile..etc.update-motd.d.98-reboot-required: [deleted]
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-04-25T16:28:36.64

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

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

[Touch-packages] [Bug 1702347] Re: Graphical glitches in screen by default on 17.10 & 18.04

** Tags added: bios-outdated-3808

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

Title:
  Graphical glitches in screen by default on 17.10 & 18.04

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10 development branch

  updated and dist-upgraded on 4 july 2017

  Im having weird glitches in screen when scrolling or switching windows
  by default

  Graphics:  Card: NVIDIA C77 [GeForce 9100M G]
 Display Server: X.Org 1.19.3 drivers: nouveau (unloaded: 
modesetting,fbdev,vesa)
 Resolution: 1440x900@60.00hz
 GLX Renderer: Gallium 0.4 on NVAA GLX Version: 3.0 Mesa 17.1.2

  installing nvidia-340 resulted in a black screen after login, so i had to 
purge nvidia* to get
  back to desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jul  4 20:59:21 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.8, 4.10.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation C77 [GeForce 9100M G] [10de:0844] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Acer Incorporated [ALI] C77 [GeForce 9100M G] [1025:014d]
  InstallationDate: Installed on 2017-06-13 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170612)
  MachineType: Acer, inc. Aspire 7530
  ProcEnviron:
   LANGUAGE=nl_BE:nl
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=e65dc3e3-3694-4b7c-b7c8-7e9cfe3cbd5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/01/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v1.3342
  dmi.board.name: EI Capitan
  dmi.board.vendor: Acer, Inc.
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrv1.3342:bd10/01/2008:svnAcer,inc.:pnAspire7530:pvrNotApplicable:rvnAcer,Inc.:rnEICapitan:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
  dmi.product.name: Aspire 7530
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer, inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.81-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Jul  4 20:45:53 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   event6  - (EE) SynPS/2 Synaptics TouchPad: (EE) kernel bug: Touch jump 
detected and discarded.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu2
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

** Changed in: unattended-upgrades (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Committed
Status in update-manager package in Ubuntu:
  In Progress
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  In Progress

Bug description:
  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

This bug was fixed in the package ndisc6 - 1.0.3-3ubuntu1

---
ndisc6 (1.0.3-3ubuntu1) bionic; urgency=medium

  * debian/control: Drop resolvconf to a Suggests:. It's not absolutely
necessary to have resolvconf installed to use rdnssd, and resolvconf
might fight with systemd-resolved for ownership of /etc/resolv.conf.
(LP: #1713803)

 -- Mathieu Trudel-Lapierre   Fri, 16 Feb 2018
13:18:54 -0500

** Changed in: ndisc6 (Ubuntu)
   Status: New => 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/1713803

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  Triaged
Status in avahi package in Ubuntu:
  Triaged
Status in bind9 package in Ubuntu:
  Triaged
Status in cloud-init package in Ubuntu:
  Incomplete
Status in cloud-initramfs-tools package in Ubuntu:
  Invalid
Status in dhcpcd5 package in Ubuntu:
  New
Status in dibbler package in Ubuntu:
  Won't Fix
Status in dnscrypt-proxy package in Ubuntu:
  Confirmed
Status in dnsmasq package in Ubuntu:
  Invalid
Status in dnssec-trigger package in Ubuntu:
  Invalid
Status in fetchmail package in Ubuntu:
  Confirmed
Status in freedombox-setup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in ndisc6 package in Ubuntu:
  Fix Released
Status in netscript-2.4 package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  Triaged
Status in openvpn package in Ubuntu:
  Confirmed
Status in postfix package in Ubuntu:
  New
Status in pppconfig package in Ubuntu:
  Confirmed
Status in pump package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid
Status in sendmail package in Ubuntu:
  New
Status in squid3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in unbound package in Ubuntu:
  New
Status in vpnc package in Ubuntu:
  Invalid
Status in vpnc-scripts package in Ubuntu:
  Invalid
Status in whereami package in Ubuntu:
  Triaged

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

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

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

[Touch-packages] [Bug 1747711] Re: file mis-identifies modern executables as application/x-sharedlib

It is also an issue on bionic:

 $ schroot -u root -c bionic-amd64
(bionic-amd64)root@impulse:/tmp# echo "int main() { return 0; }" > foo.c
(bionic-amd64)root@impulse:/tmp# gcc -o foo foo.c
(bionic-amd64)root@impulse:/tmp# file foo
foo: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically 
linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, 
BuildID[sha1]=5222fe7f5f12ee8d286b84f93c981cab98ad382a, not stripped

But not on xenial:

 $ schroot -u root -c xenial-amd64
(xenial-amd64)root@impulse:/tmp# echo "int main() { return 0; }" > foo.c
(xenial-amd64)root@impulse:/tmp# gcc -o foo foo.c
(xenial-amd64)root@impulse:/tmp# file foo
foo: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, 
interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, 
BuildID[sha1]=5a079b5be569b3e0527b9685f1c7811fb193d37c, not stripped

Using gcc from xenial and file from bionic though the file is identified
as an executable so I don't think its file.

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

Title:
  file mis-identifies modern executables as application/x-sharedlib

Status in file package in Ubuntu:
  New

Bug description:
  file doesn't recognize modern PIE (Position Independent Executable)
  x86 executables as such, reporting them as “application/x-sharedlib”.
  Consequently, only non-PIE executables can be opened in graphical file
  managers such as nautilus. This may cause a minor (?) security risk if
  a commonly-published workaround is attempted.

  Expected behaviour:

  $ echo "int main() { return 0; }" > foo.c
  $ gcc -o foo foo.c
  $ file foo
  foo: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically 
linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, 
BuildID[sha1]=6e7749f995a89a53f74ec29d3c16fcf3f56be90f, not stripped
  $ file --mime-type foo
  foo: application/x-executable

  Actual behaviour:

  $ echo "int main() { return 0; }" > foo.c
  $ gcc -o foo foo.c
  $ file foo
  foo: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically 
linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, 
BuildID[sha1]=6e7749f995a89a53f74ec29d3c16fcf3f56be90f, not stripped
  $ file --mime-type foo
  foo: application/x-sharedlib

  Workaround (unsafe?):

  $ echo "int main() { return 0; }" > foo.c
  $ gcc -o foo-nopie foo.c -no-pie
  $ file foo-nopie
  foo-nopie: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), 
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 
3.2.0, BuildID[sha1]=3eb8c581f43c19997e3c828f5a9730dbdc794470, not stripped
  $ file --mime-type foo-nopie
  foo-nopie: application/x-executable

  gcc now defaults to building with PIE enabled for security reasons.

  Also affects: nautilus (and likely other graphical file managers like
  those on Lubuntu) - because nautilus uses mime-type to determine if a
  file is executable, double-click to run a program no longer works.

  Also noted on: Gnome Bugs -
  https://bugzilla.gnome.org/show_bug.cgi?id=737849 (2014) - before PIE
  became the default build option.

  This may be an upstream issue. This may not affect architectures
  outside x86.*

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: file 1:5.32-1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Feb  6 11:21:20 2018
  InstallationDate: Installed on 2017-05-11 (270 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: file
  UpgradeStatus: Upgraded to artful on 2017-10-21 (108 days ago)

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

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

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

Charlie, I'm closing this as per
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1704660/comments/3
given this is not reproducible on the originally reported hardware after
switching to 64-bit, and applying updates.

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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Using two monitors:

  1. Moved an image from picture folder to primary secondary monitor
  desktop

  2. Opened a folder on primary monitor

  3. Tried to drag image file into - file 'declines and mouse curser is
  now a fist icon and mouse clicks on image have no effect.

  4. Logged out and right click mouse menu is back and I can send the
  image to rubbish bin and return to the desktop but issue still occurs
  and is repeatable.

  I realize that this may not be a Xorg problem but not sure what is
  causing my issue. Happy to carry out more tests/supply more
  information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic i686
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: i386
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Jul 16 17:20:37 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: Dell Radeon HD 6670 [1028:0b0e]
  InstallationDate: Installed on 2017-07-14 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170606.1)
  MachineType: Dell Inc. OptiPlex 9010
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=5a1aae5a-efbf-41a8-bfb3-c460b0bda660 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0M9KCM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn0M9KCM:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.81-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1750031] [NEW] scary/unexpected output in adduser and deluser

2018-02-16 Thread Scott Moser

Public bug reported:

adduser and deluser are now printing to stderr 'sent invalidate(passwd)' and
'sent invalidate(group)'.

These are confusing at best and new in bionic.
See below. They do not seem harmful, but not wonderful.


smoser@ubuntu1:~$ sudo adduser guest
Adding user `guest' ...
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
Adding new group `guest' (1001) ...
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
sent invalidate(group) request, exiting
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
Adding new user `guest' (1001) with group `guest' ...
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
The home directory `/home/guest' already exists.  Not copying from `/etc/skel'.
Enter new UNIX password: 
Retype new UNIX password: 
passwd: password updated successfully
Changing the user information for guest
Enter the new value, or press ENTER for the default
Full Name []: Foo Bar
Room Number []: 
Work Phone []: 
Home Phone []: 
Other []: 
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
sent invalidate(passwd) request, exiting
Is the information correct? [Y/n] 
smoser@ubuntu1:~$ sudo deluser guest
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
Removing user `guest' ...
Warning: group `guest' has no more members.
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
Done.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: adduser 3.113+nmu3ubuntu4
ProcVersionSignature: User Name 4.13.0-1007.9-azure 4.13.13
Uname: Linux 4.13.0-1007-azure x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Fri Feb 16 19:30:12 2018
PackageArchitecture: all
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: adduser
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug uec-images xenial

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

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

Title:
  scary/unexpected output in adduser and deluser

Status in adduser package in Ubuntu:
  Confirmed

Bug description:
  adduser and deluser are now printing to stderr 'sent invalidate(passwd)' and
  'sent invalidate(group)'.

  These are confusing at best and new in bionic.
  See below. They do not seem harmful, but not wonderful.

  
  smoser@ubuntu1:~$ sudo adduser guest
  Adding user `guest' ...
  sent invalidate(passwd) request, exiting
  sent invalidate(group) request, exiting
  Adding new group `guest' (1001) ...
  sent invalidate(passwd) request, exiting
  sent invalidate(group) request, exiting
  sent invalidate(group) request, exiting
  sent invalidate(passwd) request, exiting
  sent invalidate(group) request, exiting
  Adding new user `guest' (1001) with group `guest' ...
  sent invalidate(passwd) request, exiting
  sent invalidate(group) request, exiting
  sent invalidate(passwd) request, exiting
  sent invalidate(group) request, exiting
  sent invalidate(passwd) request, exiting
  sent invalidate(group) request, exiting
  The home directory `/home/guest' already exists.  Not copying from 
`/etc/skel'.
  Enter new UNIX password: 
  Retype new UNIX password: 
  passwd: password updated successfully
  Changing the user information for guest
  Enter the new value, or press ENTER for the default
  Full Name []: Foo Bar
  Room Number []: 
  Work Phone []: 
  Home Phone []: 
  Other []: 
  sent invalidate(passwd) request, exiting
  sent invalidate(group) request, exiting
  sent invalidate(passwd) request, exiting
  Is the information correct? [Y/n] 
  smoser@ubuntu1:~$ sudo deluser guest
  sent invalidate(passwd) request, exiting
  sent invalidate(group) request, exiting
  Removing user `guest' ...
  Warning: group `guest' has no more members.
  sent invalidate(passwd) request, exiting
  sent invalidate(group) request, exiting
  sent invalidate(passwd) request, exiting
  sent invalidate(group) request, exiting
  sent invalidate(passwd) request, exiting
  sent invalidate(group) request, exiting
  Done.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: adduser 3.113+nmu3ubuntu4
  ProcVersionSignature: User Name 4.13.0-1007.9-azure 4.13.13
  Uname: Linux 4.13.0

[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

dnsmasq Suggests: resolvconf only, and checks before using it. None of
the steps involved would break with resolvconf not being present,
integration just happens via /etc/resolv.conf normally.

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

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

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  Triaged
Status in avahi package in Ubuntu:
  Triaged
Status in bind9 package in Ubuntu:
  Triaged
Status in cloud-init package in Ubuntu:
  Incomplete
Status in cloud-initramfs-tools package in Ubuntu:
  Invalid
Status in dhcpcd5 package in Ubuntu:
  New
Status in dibbler package in Ubuntu:
  Won't Fix
Status in dnscrypt-proxy package in Ubuntu:
  Confirmed
Status in dnsmasq package in Ubuntu:
  Invalid
Status in dnssec-trigger package in Ubuntu:
  Invalid
Status in fetchmail package in Ubuntu:
  Confirmed
Status in freedombox-setup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in ndisc6 package in Ubuntu:
  New
Status in netscript-2.4 package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  Triaged
Status in openvpn package in Ubuntu:
  Confirmed
Status in postfix package in Ubuntu:
  New
Status in pppconfig package in Ubuntu:
  Confirmed
Status in pump package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid
Status in sendmail package in Ubuntu:
  New
Status in squid3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in unbound package in Ubuntu:
  New
Status in vpnc package in Ubuntu:
  Invalid
Status in vpnc-scripts package in Ubuntu:
  Invalid
Status in whereami package in Ubuntu:
  Triaged

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

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

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

[Touch-packages] [Bug 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)

As already briefly mentioned, Trusty systemd's package has
additional patches to customize systemd - specially, we have the addition
of glue code to make Trusty's systemd work with cgmanager. This is
necessary due to the choice of upstart as init manager - it prevents
regular cgroup handling from systemd perspective, so cgmanager is used
in order to assist cgroup management on systemd code.

This glue code was used in some cgroup's routines when cgmanager is active
and running. In particular, it's used on systemd's cg_enumerate_tasks()
and cg_enumerate_processes() routines. In these cases, there's a memory
leak caused by a "string" allocation in cgm_get() that isn't freed on
cg_enumerate_tasks() / cg_enumerate_processes() - it shows up in Valgrind
like this:

58 bytes in 58 blocks are definitely lost in loss record 60 of 113
at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
by 0x638EB49: strdup (strdup.c:42)
by 0x422A90: cgm_get (cgmanager.c:148)
by 0x420AC6: cg_enumerate_tasks (cgroup-util.c:128)
by 0x420C89: cg_is_empty (cgroup-util.c:1129)
by 0x420DEA: cg_is_empty_recursive (cgroup-util.c:1175)
by 0x40FC48: session_check_gc (logind-session.c:979)
by 0x408694: manager_gc (logind.c:1503)
by 0x4094B8: manager_run (logind.c:1740)
by 0x40622B: main (logind.c:1868)
--

I wrote a small patch that fixes the leak by freeing the allocated pointer
after its use. It diverges from upstream since systemd upstream has no
cgmanager glue code, which was added specially for Trusty's need of
systemd packages without having it as init manager.

The free() calls are clear and simple, they're provided by a GCC attribute
that calls a free() whenever the scope of the pointer is not reachable
anymore. No side effects are expected, the patch frees the pointer in all
failure paths also since it's using the GCC attribute of auto-calling
free(). No double-frees are possible since the free() calls happens only
after the pointer was validated as has been successfully allocated.

The patch:

diff --git a/src/shared/cgroup-util.c b/src/shared/cgroup-util.c
index 6c07a49..ab50ad4 100644
--- a/src/shared/cgroup-util.c
+++ b/src/shared/cgroup-util.c
@@ -44,7 +44,7 @@ int cg_enumerate_processes(const char *controller, const char 
*path, FILE **_f)
 _cleanup_free_ char *fs = NULL;
 FILE *f;
 int r;
-char *value = NULL;
+_cleanup_free_ char *value = NULL;
 char *template = NULL;
 int fd;
 
@@ -111,7 +111,7 @@ int cg_enumerate_tasks(const char *controller, const char 
*path, FILE **_f) {
 _cleanup_free_ char *fs = NULL;
 FILE *f;
 int r;
-char *value = NULL;
+_cleanup_free_ char *value = NULL;
 char *template = NULL;
 int fd;
 

The patches above were tested during 4 days running the test-case, with
cgmanager package installed. More than 658000 sessions were started and
finished without memory leaks.

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

Title:
  systemd-logind: memory leaks on session's connections (trusty-only)

Status in systemd package in Ubuntu:
  New

Bug description:
  It was observed that systemd-logind tool is leaking memory at each session
  connected. The issue happens in systemd from Trusty (14.04), which latest
  version currently (Feb/2018) is 204-5ubuntu20.26 (and still reproduces
  the bug).

  The basic test-case is to run the following loop from a remote
  machine:

  while true; do ssh  "whoami"; done

  and watch the increase in memory consumption from "systemd-logind" process
  in the target machine. One can use the "ps uax" command to verify the
  RSS of the process, or count the anon pages from /proc//smaps.

  To clarify a bit how a session works, the following "stack trace" details
  a bit which function calls happen when a SSH connection is opened, from
  Trusty's systemd-logind point of view:

  
  main() 
  manager_startup()
  manager_run() [event-loop]
  bus_loop_dispatch() 
  dbus_watch_handle() -> bus_manager_message_handler()
  bus_manager_create_session()
  manager_add_session() 
  session_new() 
  session_create_fifo()
  session_start()
  session_create_cgroup()
  session_save()
  session_bus_path()
  [...]

  After each session is closed, it was observed that session_free() isn't
  called, keeping the sessions alive. This can be verified through the
  command "loginctl list-session" - each session that once connected is
  present there "forever".

  The memory leaks can eventually lead to OOM situation of this process.
  Debug progress will be tracked here, in this LP.

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

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

[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

vpnc and vpnc-scripts check for existance of /sbin/resolvconf and only
Suggests: resolvconf. DNS integration by modifying /etc/resolv.conf (and
thus the systemd symlink) should work appropriately and let systemd-
resolved know about the new nameservers.

** Changed in: vpnc-scripts (Ubuntu)
   Status: New => Invalid

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

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

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  Triaged
Status in avahi package in Ubuntu:
  Triaged
Status in bind9 package in Ubuntu:
  Triaged
Status in cloud-init package in Ubuntu:
  Incomplete
Status in cloud-initramfs-tools package in Ubuntu:
  Invalid
Status in dhcpcd5 package in Ubuntu:
  New
Status in dibbler package in Ubuntu:
  Won't Fix
Status in dnscrypt-proxy package in Ubuntu:
  Confirmed
Status in dnsmasq package in Ubuntu:
  New
Status in dnssec-trigger package in Ubuntu:
  Invalid
Status in fetchmail package in Ubuntu:
  Confirmed
Status in freedombox-setup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in ndisc6 package in Ubuntu:
  New
Status in netscript-2.4 package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  Triaged
Status in openvpn package in Ubuntu:
  Confirmed
Status in postfix package in Ubuntu:
  New
Status in pppconfig package in Ubuntu:
  Confirmed
Status in pump package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid
Status in sendmail package in Ubuntu:
  New
Status in squid3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in unbound package in Ubuntu:
  New
Status in vpnc package in Ubuntu:
  Invalid
Status in vpnc-scripts package in Ubuntu:
  Invalid
Status in whereami package in Ubuntu:
  Triaged

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

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

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

[Touch-packages] [Bug 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)

It was noticed that during the logind manager logic for creating a session
based on dbus event, the sessions's initialization procedure will allocate
2 structures related to cgroup management of a session: controllers and
reset_controllers.

Both these structs are filled with cgroup controllers (when they exist)
in bus_parse_strv_iter(), which will always allocate at least one of each
to be used as a parent for a "string"-based list of elements abstraction.

Currently, the code does not free reset_controllers, so we have a memory
leak at each session creation, which shows up in a valgrind output like
this:

2,696 bytes in 337 blocks are definitely lost in loss record 99 of 101
at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
by 0x434F58: malloc_multiply (util.h:564)
by 0x4368DA: bus_parse_strv_iter (dbus-common.c:905)
by 0x40AE9D: bus_manager_create_session (logind-dbus.c:498)
by 0x40EB39: manager_message_handler (logind-dbus.c:1752)
by 0x5ED8E85: ??? (in /lib/x86_64-linux-gnu/libdbus-1.so.3.7.6)
by 0x5ECBA20: dbus_connection_dispatch (in 
/lib/x86_64-linux-gnu/libdbus-1.so.3.7.6)
by 0x409E21: manager_run (logind.c:1729)
by 0x40A27C: main (logind.c:1860)

Notice this was after 337 sessions.
--

I wrote a small patch that addresses the issue by just adding the
necessary strv_free(). It diverges from upstream systemd since
reset_controllers entity was removed from the code after the refactor
on cgroup's handling made by commit
fb6becb ("logind: port over to use scopes+slices for all cgroup stuff").

The strv_free() call has no known risk and potential double-frees aren't
expected since strv_free() validates the struct and its "children"
before de-allocate the resources.

The patch:


diff --git a/src/login/logind-session.c b/src/login/logind-session.c
index 662273b..1a7389a 100644
--- a/src/login/logind-session.c
+++ b/src/login/logind-session.c
@@ -93,6 +93,7 @@ void session_free(Session *s) {
 
 free(s->cgroup_path);
 strv_free(s->controllers);
+strv_free(s->reset_controllers);
 
 free(s->tty);
 free(s->display);


After testing with both patches already mentioned and cgmanager, there
is still a (really) small leak to be investigated.

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

Title:
  systemd-logind: memory leaks on session's connections (trusty-only)

Status in systemd package in Ubuntu:
  New

Bug description:
  It was observed that systemd-logind tool is leaking memory at each session
  connected. The issue happens in systemd from Trusty (14.04), which latest
  version currently (Feb/2018) is 204-5ubuntu20.26 (and still reproduces
  the bug).

  The basic test-case is to run the following loop from a remote
  machine:

  while true; do ssh  "whoami"; done

  and watch the increase in memory consumption from "systemd-logind" process
  in the target machine. One can use the "ps uax" command to verify the
  RSS of the process, or count the anon pages from /proc//smaps.

  To clarify a bit how a session works, the following "stack trace" details
  a bit which function calls happen when a SSH connection is opened, from
  Trusty's systemd-logind point of view:

  
  main() 
  manager_startup()
  manager_run() [event-loop]
  bus_loop_dispatch() 
  dbus_watch_handle() -> bus_manager_message_handler()
  bus_manager_create_session()
  manager_add_session() 
  session_new() 
  session_create_fifo()
  session_start()
  session_create_cgroup()
  session_save()
  session_bus_path()
  [...]

  After each session is closed, it was observed that session_free() isn't
  called, keeping the sessions alive. This can be verified through the
  command "loginctl list-session" - each session that once connected is
  present there "forever".

  The memory leaks can eventually lead to OOM situation of this process.
  Debug progress will be tracked here, in this LP.

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

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

[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

It looks like open-iscsi makes use of resolvconf in debian/net-
interface-handler, but does check for its presence before doing so. That
said, there is not additional integration with anything to set
nameservers/search domains, so open-iscsi will need further
investigation to see if all is well with it when resolvconf is not
present and the iSCSI server is configured with an FQDN rather than a
straight IP address.

** Changed in: open-iscsi (Ubuntu)
   Importance: Undecided => Medium

** Changed in: open-iscsi (Ubuntu)
   Status: New => Triaged

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

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  Triaged
Status in avahi package in Ubuntu:
  Triaged
Status in bind9 package in Ubuntu:
  Triaged
Status in cloud-init package in Ubuntu:
  Incomplete
Status in cloud-initramfs-tools package in Ubuntu:
  Invalid
Status in dhcpcd5 package in Ubuntu:
  New
Status in dibbler package in Ubuntu:
  Won't Fix
Status in dnscrypt-proxy package in Ubuntu:
  Confirmed
Status in dnsmasq package in Ubuntu:
  New
Status in dnssec-trigger package in Ubuntu:
  Invalid
Status in fetchmail package in Ubuntu:
  Confirmed
Status in freedombox-setup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in ndisc6 package in Ubuntu:
  New
Status in netscript-2.4 package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  Triaged
Status in openvpn package in Ubuntu:
  Confirmed
Status in postfix package in Ubuntu:
  New
Status in pppconfig package in Ubuntu:
  Confirmed
Status in pump package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid
Status in sendmail package in Ubuntu:
  New
Status in squid3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in unbound package in Ubuntu:
  New
Status in vpnc package in Ubuntu:
  New
Status in vpnc-scripts package in Ubuntu:
  New
Status in whereami package in Ubuntu:
  Triaged

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

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

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

[Touch-packages] [Bug 1747711] Re: file mis-identifies modern executables as application/x-sharedlib

** Tags added: bionic

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

Title:
  file mis-identifies modern executables as application/x-sharedlib

Status in file package in Ubuntu:
  New

Bug description:
  file doesn't recognize modern PIE (Position Independent Executable)
  x86 executables as such, reporting them as “application/x-sharedlib”.
  Consequently, only non-PIE executables can be opened in graphical file
  managers such as nautilus. This may cause a minor (?) security risk if
  a commonly-published workaround is attempted.

  Expected behaviour:

  $ echo "int main() { return 0; }" > foo.c
  $ gcc -o foo foo.c
  $ file foo
  foo: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically 
linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, 
BuildID[sha1]=6e7749f995a89a53f74ec29d3c16fcf3f56be90f, not stripped
  $ file --mime-type foo
  foo: application/x-executable

  Actual behaviour:

  $ echo "int main() { return 0; }" > foo.c
  $ gcc -o foo foo.c
  $ file foo
  foo: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically 
linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, 
BuildID[sha1]=6e7749f995a89a53f74ec29d3c16fcf3f56be90f, not stripped
  $ file --mime-type foo
  foo: application/x-sharedlib

  Workaround (unsafe?):

  $ echo "int main() { return 0; }" > foo.c
  $ gcc -o foo-nopie foo.c -no-pie
  $ file foo-nopie
  foo-nopie: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), 
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 
3.2.0, BuildID[sha1]=3eb8c581f43c19997e3c828f5a9730dbdc794470, not stripped
  $ file --mime-type foo-nopie
  foo-nopie: application/x-executable

  gcc now defaults to building with PIE enabled for security reasons.

  Also affects: nautilus (and likely other graphical file managers like
  those on Lubuntu) - because nautilus uses mime-type to determine if a
  file is executable, double-click to run a program no longer works.

  Also noted on: Gnome Bugs -
  https://bugzilla.gnome.org/show_bug.cgi?id=737849 (2014) - before PIE
  became the default build option.

  This may be an upstream issue. This may not affect architectures
  outside x86.*

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: file 1:5.32-1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Feb  6 11:21:20 2018
  InstallationDate: Installed on 2017-05-11 (270 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: file
  UpgradeStatus: Upgraded to artful on 2017-10-21 (108 days ago)

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

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

[Touch-packages] [Bug 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)

After some debug, it was observed that the only path in which a session
is freed (other than in user/seat free or manager free) is in garbage
collecting, specifically in the function manager_gc().
It means a closing session should be somehow added to gc in order gc has
a chance to validate if the session is ready to go, and then performs
the clean-up.

To include a session in gc, the function session_add_to_gc_queue() should
be called. This function is currently called from 3 paths:

* from session_stop();
* from manager startup routines;
* and from the empty cgroup notification handler.

Since we are not using systemd as init system in Trusty, the empty cgroup
notifier is not reliable. We rely on cgmanager to perform cgroup
interaction on Trusty, and its release-agent also does not notify when
cgroups are empty. Finally, commit
efdb023 ("core: unified cgroup hierarchy support")
made a refactor in cgroup management and it claims for the first time,
cgroup empty notifications are reliable, meaning until this commit we
certainly couldn't rely on it.

The startup path of manager is executed only in logind start; session_stop()
could execute from Terminate dbus events (like loginctl terminate-session),
and from user/seat stopping routines. Meaning there's no way a session is
added to gc queue except the cgroup empty notification (if it worked) in
this version of systemd.

The simple test-case mentioned in the first comment leaks entire sessions
and logind consumes an increasing amount of memory.
--

In order to prevent that, I wrote a small patch that proactively puts a
session in gc on session_remove_fifo(). This function is always called in
the event of Release a session - when the ssh ends, for example.
This way, we guarantee closing sessions have a chance to be cleared.

But also, it was noticed that kernel may take a small time window to
clear the tasks' cgroup tracking for the session - hence, the gc
might fail in freeing the session, so the patch adds a check on gc too
in order to re-add the session on gc in case session is on closing state. 
This way stopping sessions are always freed and no leak is observed.


The patch:


diff --git a/src/login/logind-session.c b/src/login/logind-session.c
index 662273b..1a7389a 100644
--- a/src/login/logind-session.c
+++ b/src/login/logind-session.c
@@ -951,6 +952,7 @@ void session_remove_fifo(Session *s) {
 free(s->fifo_path);
 s->fifo_path = NULL;
 }
+session_add_to_gc_queue(s);
 }
 
 int session_check_gc(Session *s, bool drop_not_started) {
diff --git a/src/login/logind.c b/src/login/logind.c
index 333a779..0b9e165 100644
--- a/src/login/logind.c
+++ b/src/login/logind.c
@@ -1495,6 +1495,8 @@ void manager_gc(Manager *m, bool drop_not_started) {
 if (session_check_gc(session, drop_not_started) == 0) {
 session_stop(session);
 session_free(session);
+} else if (session_get_state(session) == SESSION_CLOSING) {
+session_add_to_gc_queue(session);
 }
 }


This diverges from upstream since we have refactors in systemd code,
specially in session shutdown logic on commit 5f41d1f
("logind: rework session shutdown logic"). The simple approach of this
patch is less expensive then bring multiple patches to the current code
of Trusty's systemd.

As possible side effects, adding a session to gc has none other than a
possible (non-measured) minimal performance penalty.

Finally, it was observed that "cgmanager" package is necessary to perform
the full clean-up of a session - since we don't handle cgroups with systemd
in Trusty, cgmanager is the responsible one to clear the cgroup directory
for each cleaned-up session.

After testing the solution above (with cgmanager), memory consumption was
drastically reduced, since systemd-logind is not "leaking" entire
sessions anymore.

More small leaks were observed though, so investigation continues.

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

Title:
  systemd-logind: memory leaks on session's connections (trusty-only)

Status in systemd package in Ubuntu:
  New

Bug description:
  It was observed that systemd-logind tool is leaking memory at each session
  connected. The issue happens in systemd from Trusty (14.04), which latest
  version currently (Feb/2018) is 204-5ubuntu20.26 (and still reproduces
  the bug).

  The basic test-case is to run the following loop from a remote
  machine:

  while true; do ssh  "whoami"; done

  and watch the increase in memory consumption from "systemd-logind" process
  in the target machine. One can use the "ps uax" command to verify the
  RSS of the process, or count the anon pages from /proc//smaps.

  To clarify a bit how a session works, the following "stack trace" details
  a bit which funct

[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

ndisc6 appears to Recommends: resolvconf (in rdnssd); will drop to a
Suggests. The code in the merge hook for resolvconf already checks
whether resolvconf is present before making use of it.

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

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  Triaged
Status in avahi package in Ubuntu:
  Triaged
Status in bind9 package in Ubuntu:
  Triaged
Status in cloud-init package in Ubuntu:
  Incomplete
Status in cloud-initramfs-tools package in Ubuntu:
  Invalid
Status in dhcpcd5 package in Ubuntu:
  New
Status in dibbler package in Ubuntu:
  Won't Fix
Status in dnscrypt-proxy package in Ubuntu:
  Confirmed
Status in dnsmasq package in Ubuntu:
  New
Status in dnssec-trigger package in Ubuntu:
  Invalid
Status in fetchmail package in Ubuntu:
  Confirmed
Status in freedombox-setup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in ndisc6 package in Ubuntu:
  New
Status in netscript-2.4 package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  Confirmed
Status in postfix package in Ubuntu:
  New
Status in pppconfig package in Ubuntu:
  Confirmed
Status in pump package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid
Status in sendmail package in Ubuntu:
  New
Status in squid3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in unbound package in Ubuntu:
  New
Status in vpnc package in Ubuntu:
  New
Status in vpnc-scripts package in Ubuntu:
  New
Status in whereami package in Ubuntu:
  Triaged

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

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

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

[Touch-packages] [Bug 1749222] Re: apport-collect requires python2

I believe this is correct and not fixable because apport-collect uses
launchpadlib and on Ubuntu 16.04 it needs to use python-launchpadlib,
not python3-launchpadlib, because of some bugs in launchpadlib or its
dependencies that were not fixed in Ubuntu 16.04. See bug 1153671 for
details.

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

Title:
  apport-collect requires python2

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Confirmed

Bug description:
  I'm booted into a 16.04 maas rescue environment.

  $ apport-collect
  You need to run 'sudo apt-get install python-apport' for apport-collect to 
work.

  running the provided command will get me a python2 stack.
  python3-apport is already installed.

  python3 should be used.

  I then tried a stock bionic container, and run the same.  The message
  changes to suggest python3-apport.

  root@b1:~# apport-collect
  You need to run 'sudo apt-get install python3-apport' for apport-collect to 
work.

  That seems better.  However, python3-apport is already installed.
  # sudo apt-get install python3-apport
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  python3-apport is already the newest version (2.20.8-0ubuntu8).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.15
  ProcVersionSignature: User Name 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Feb 13 15:38:43 2018
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

  Related bugs:
   * bug 1748621: apport-collect won't work (bionic)

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

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

[Touch-packages] [Bug 1750013] [NEW] systemd-logind: memory leaks on session's connections (trusty-only)

Public bug reported:

It was observed that systemd-logind tool is leaking memory at each session
connected. The issue happens in systemd from Trusty (14.04), which latest
version currently (Feb/2018) is 204-5ubuntu20.26 (and still reproduces
the bug).

The basic test-case is to run the following loop from a remote machine:

while true; do ssh  "whoami"; done

and watch the increase in memory consumption from "systemd-logind" process
in the target machine. One can use the "ps uax" command to verify the
RSS of the process, or count the anon pages from /proc//smaps.

To clarify a bit how a session works, the following "stack trace" details
a bit which function calls happen when a SSH connection is opened, from
Trusty's systemd-logind point of view:


main() 
manager_startup()
manager_run() [event-loop]
bus_loop_dispatch() 
dbus_watch_handle() -> bus_manager_message_handler()
bus_manager_create_session()
manager_add_session() 
session_new() 
session_create_fifo()
session_start()
session_create_cgroup()
session_save()
session_bus_path()
[...]

After each session is closed, it was observed that session_free() isn't
called, keeping the sessions alive. This can be verified through the
command "loginctl list-session" - each session that once connected is
present there "forever".

The memory leaks can eventually lead to OOM situation of this process.
Debug progress will be tracked here, in this LP.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: New


** Tags: sts

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

Title:
  systemd-logind: memory leaks on session's connections (trusty-only)

Status in systemd package in Ubuntu:
  New

Bug description:
  It was observed that systemd-logind tool is leaking memory at each session
  connected. The issue happens in systemd from Trusty (14.04), which latest
  version currently (Feb/2018) is 204-5ubuntu20.26 (and still reproduces
  the bug).

  The basic test-case is to run the following loop from a remote
  machine:

  while true; do ssh  "whoami"; done

  and watch the increase in memory consumption from "systemd-logind" process
  in the target machine. One can use the "ps uax" command to verify the
  RSS of the process, or count the anon pages from /proc//smaps.

  To clarify a bit how a session works, the following "stack trace" details
  a bit which function calls happen when a SSH connection is opened, from
  Trusty's systemd-logind point of view:

  
  main() 
  manager_startup()
  manager_run() [event-loop]
  bus_loop_dispatch() 
  dbus_watch_handle() -> bus_manager_message_handler()
  bus_manager_create_session()
  manager_add_session() 
  session_new() 
  session_create_fifo()
  session_start()
  session_create_cgroup()
  session_save()
  session_bus_path()
  [...]

  After each session is closed, it was observed that session_free() isn't
  called, keeping the sessions alive. This can be verified through the
  command "loginctl list-session" - each session that once connected is
  present there "forever".

  The memory leaks can eventually lead to OOM situation of this process.
  Debug progress will be tracked here, in this LP.

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

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

[Touch-packages] [Bug 1750005] Re: Please remove in bionic

2018-02-16 Thread Jamie Strandboge

$ ./remove-package -m "unmaintained. LP: #1750005" apparmor-easyprof-ubuntu
Removing packages from bionic:
apparmor-easyprof-ubuntu 16.10.3 in bionic
apparmor-easyprof-ubuntu 16.10.3 in bionic amd64
apparmor-easyprof-ubuntu 16.10.3 in bionic arm64
apparmor-easyprof-ubuntu 16.10.3 in bionic armhf
apparmor-easyprof-ubuntu 16.10.3 in bionic i386
apparmor-easyprof-ubuntu 16.10.3 in bionic ppc64el
apparmor-easyprof-ubuntu 16.10.3 in bionic s390x
Comment: unmaintained. LP: #1750005
Remove [y|N]? y
1 package successfully removed.

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

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

Title:
  Please remove in bionic

Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released

Bug description:
  This package is unmaintained and was only used by click-apparmor and
  webbrowser-app, which have been removed from bionic. This package is
  not seeded in bionic.

  $ checkrdepends apparmor-easyprof-ubuntu
  -- bionic/universe build deps on apparmor-easyprof-ubuntu:
  click-apparmor
  -- bionic/universe amd64 deps on apparmor-easyprof-ubuntu:
  python3-apparmor-click [all]
  -- bionic/universe i386 deps on apparmor-easyprof-ubuntu:
  python3-apparmor-click [all]
  -- bionic/universe arm64 deps on apparmor-easyprof-ubuntu:
  python3-apparmor-click [all]
  -- bionic/universe armhf deps on apparmor-easyprof-ubuntu:
  python3-apparmor-click [all]
  -- bionic/universe ppc64el deps on apparmor-easyprof-ubuntu:
  python3-apparmor-click [all]
  -- bionic/universe s390x deps on apparmor-easyprof-ubuntu:
  python3-apparmor-click [all]

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

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

[Touch-packages] [Bug 1750005] [NEW] Please remove in bionic

2018-02-16 Thread Jamie Strandboge

Public bug reported:

This package is unmaintained and was only used by click-apparmor and
webbrowser-app, which have been removed from bionic. This package is not
seeded in bionic.

$ checkrdepends apparmor-easyprof-ubuntu
-- bionic/universe build deps on apparmor-easyprof-ubuntu:
click-apparmor
-- bionic/universe amd64 deps on apparmor-easyprof-ubuntu:
python3-apparmor-click [all]
-- bionic/universe i386 deps on apparmor-easyprof-ubuntu:
python3-apparmor-click [all]
-- bionic/universe arm64 deps on apparmor-easyprof-ubuntu:
python3-apparmor-click [all]
-- bionic/universe armhf deps on apparmor-easyprof-ubuntu:
python3-apparmor-click [all]
-- bionic/universe ppc64el deps on apparmor-easyprof-ubuntu:
python3-apparmor-click [all]
-- bionic/universe s390x deps on apparmor-easyprof-ubuntu:
python3-apparmor-click [all]

** Affects: apparmor-easyprof-ubuntu (Ubuntu)
 Importance: Undecided
 Assignee: Jamie Strandboge (jdstrand)
 Status: Fix Released

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

Title:
  Please remove in bionic

Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released

Bug description:
  This package is unmaintained and was only used by click-apparmor and
  webbrowser-app, which have been removed from bionic. This package is
  not seeded in bionic.

  $ checkrdepends apparmor-easyprof-ubuntu
  -- bionic/universe build deps on apparmor-easyprof-ubuntu:
  click-apparmor
  -- bionic/universe amd64 deps on apparmor-easyprof-ubuntu:
  python3-apparmor-click [all]
  -- bionic/universe i386 deps on apparmor-easyprof-ubuntu:
  python3-apparmor-click [all]
  -- bionic/universe arm64 deps on apparmor-easyprof-ubuntu:
  python3-apparmor-click [all]
  -- bionic/universe armhf deps on apparmor-easyprof-ubuntu:
  python3-apparmor-click [all]
  -- bionic/universe ppc64el deps on apparmor-easyprof-ubuntu:
  python3-apparmor-click [all]
  -- bionic/universe s390x deps on apparmor-easyprof-ubuntu:
  python3-apparmor-click [all]

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

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

[Touch-packages] [Bug 1749993] Re: After turning low-resolution-graphics Dash is transparent to unusable state

2018-02-16 Thread grofaty

In both cases "low graphic mode" true or false the "tab switcher" background is 
too transparent too.
This happened to me first time and I am using Ubuntu more then 10 years 
(different versions of course but the same! laptop).

I pressed Alt key and hold and then press Tab key. Still holding Alt key
I did a photo from my phone with one hand, so not the best photo. But
from attachment it is clear tab switcher background is too transparent
too.

** Attachment added: "tab_switcher_photographed_by_phone.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1749993/+attachment/5056806/+files/tab_switcher_photographed_by_phone.jpg

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

Title:
  After turning low-resolution-graphics Dash is transparent to unusable
  state

Status in xorg package in Ubuntu:
  New

Bug description:
  I have fresh installed Ubuntu 16.04 like two weeks ago or something. Today I 
have updated packages:
  sudo apt update && sudo apt full-upgrade

  I have noticed compiz and other packages updated and from article
  http://www.omgubuntu.co.uk/2018/02/new-unity-desktop-update-now-
  available I have seen it is now possible to turn on "low graphic mode"
  which is excellent idea for my 14-years old 32-bit laptop.

  I did:
  gsettings set com.canonical.Unity lowgfx true

  logged off and logged back in.

  When I press Super key Dash is launched, but display is totally
  useless way too transparent. See print screen.

  I have never had such a problem. Turning low graphic mode off and this
  problem disappears.

  P.S. I also have the problem with Alt+Tab switcher now background in
  switcher is white (if white background) it looks the same transparent
  problem. I turn off low graphic mode, switcher is still white. This is
  new problem after today Ubuntu update.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Feb 16 17:34:08 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GconfCompiz:
   /apps/compiz-1/plugins:
 /apps/compiz-1/plugins/unityshell:
  /apps/compiz-1/plugins/unityshell/screen0:
   /apps/compiz-1/plugins/unityshell/screen0/options:
dash_blur_experimental = 1
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a]
 Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a]
  InstallationDate: Installed on 2018-01-20 (27 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  MachineType: LENOVO 1951F5G
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=0cdfefb9-a78c-458e-826e-f76c94537c2a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/12/2006
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ET62WW (1.07 )
  dmi.board.name: 1951F5G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ET62WW(1.07):bd06/12/2006:svnLENOVO:pn1951F5G:pvrThinkPadT60:rvnLENOVO:rn1951F5G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T60
  dmi.product.name: 1951F5G
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Feb 16 16:56:33 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log

[Touch-packages] [Bug 1723042] Re: libkmod2.0-udeb is not linked with pthreads

2018-02-16 Thread lplewa

This issue affects the PMDK project -
https://github.com/pmem/issues/issues/806

Minimal reproduction:
$ cat test.c
#include 

int foo() {
kmod_ref((void *)0);
return 0;
}
cat main.c
void foo (void);
int main () {
foo();
return 0;
}
$ gcc -fPIC -c -o test.o test.c
$ gcc -shared -fPIC -o libfoo.so test.o -lc -lkmod
$ gcc -L. -o main.o main.c -lfoo -pthread
$ LD_LIBRARY_PATH=. ./main.o
./main.o: Relink `/lib/x86_64-linux-gnu/libkmod.so.2' with 
`/lib/x86_64-linux-gnu/libpthread.so.0' for IFUNC symbol `system'



** Bug watch added: github.com/pmem/issues/issues #806
   https://github.com/pmem/issues/issues/806

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

Title:
  libkmod2.0-udeb is not linked with pthreads

Status in kmod package in Ubuntu:
  Confirmed

Bug description:
  libkmod2.0-udeb is not linked with pthreads

  When running udevadm in d-i the following happens:

  udevadm: Relink `/lib/libkmod.so.2' with `/lib/libpthread.so.0' for
  IFUNC symbol `system'

  Maybe libkmod2.0 needs a rebuild and/or fix up?

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

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

[Touch-packages] [Bug 1749993] Re: After turning low-resolution-graphics Dash is transparent to unusable state

2018-02-16 Thread grofaty

Now I have turned off low graphic mode in terminal:
gsettings set com.canonical.Unity lowgfx false

And ever worse problem appeared with launcher icons becoming black. I
restarted computer and problem persists. See attachment.

If I turn on lowgfx again with:
gsettings set com.canonical.Unity lowgfx true
launcher icons are in colour again (but as reported above Dash transparency 
appear - just like in original bug report).

Did several tests. Turing on/off lowgfx and every time:
- lowgfx false --> black icons in Launcher
- lowgfx true --> icons in Launcher are fine, but original transparency problem 
in Dash is present

** Attachment added: "after_turning_low-graphic-mode_to_false.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1749993/+attachment/5056795/+files/after_turning_low-graphic-mode_to_false.png

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

Title:
  After turning low-resolution-graphics Dash is transparent to unusable
  state

Status in xorg package in Ubuntu:
  New

Bug description:
  I have fresh installed Ubuntu 16.04 like two weeks ago or something. Today I 
have updated packages:
  sudo apt update && sudo apt full-upgrade

  I have noticed compiz and other packages updated and from article
  http://www.omgubuntu.co.uk/2018/02/new-unity-desktop-update-now-
  available I have seen it is now possible to turn on "low graphic mode"
  which is excellent idea for my 14-years old 32-bit laptop.

  I did:
  gsettings set com.canonical.Unity lowgfx true

  logged off and logged back in.

  When I press Super key Dash is launched, but display is totally
  useless way too transparent. See print screen.

  I have never had such a problem. Turning low graphic mode off and this
  problem disappears.

  P.S. I also have the problem with Alt+Tab switcher now background in
  switcher is white (if white background) it looks the same transparent
  problem. I turn off low graphic mode, switcher is still white. This is
  new problem after today Ubuntu update.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Feb 16 17:34:08 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GconfCompiz:
   /apps/compiz-1/plugins:
 /apps/compiz-1/plugins/unityshell:
  /apps/compiz-1/plugins/unityshell/screen0:
   /apps/compiz-1/plugins/unityshell/screen0/options:
dash_blur_experimental = 1
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a]
 Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a]
  InstallationDate: Installed on 2018-01-20 (27 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  MachineType: LENOVO 1951F5G
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=0cdfefb9-a78c-458e-826e-f76c94537c2a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/12/2006
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ET62WW (1.07 )
  dmi.board.name: 1951F5G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ET62WW(1.07):bd06/12/2006:svnLENOVO:pn1951F5G:pvrThinkPadT60:rvnLENOVO:rn1951F5G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T60
  dmi.product.name: 1951F5G
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  ve

[Touch-packages] [Bug 1282294] Re: "Cannot open pixbuf loader module file"

2018-02-16 Thread Ken Sharp

** Tags removed: i386 xenial

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

Title:
  "Cannot open pixbuf loader module file"

Status in gdk-pixbuf package in Ubuntu:
  Triaged
Status in gdk-pixbuf package in Debian:
  New

Bug description:
  While doing testing on trusty, I keep finding errors like the
  following in my apt-get -u dist-upgrade output:

  Preparing to unpack 
.../indicator-printers_0.1.7+14.04.20140213-0ubuntu1_amd64.deb ...
  Unpacking indicator-printers (0.1.7+14.04.20140213-0ubuntu1) over 
(0.1.7daily13.03.01-0ubuntu1) ...

  (gtk-update-icon-cache-3.0:29671): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.

  (gtk-update-icon-cache-3.0:29672): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.
  ...
  Processing triggers for hicolor-icon-theme (0.13-1) ...

  (gtk-update-icon-cache-3.0:32198): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.

  
  These errors make it difficult to look for errors that I might have 
introduced in my own packages and if they persist in our final product will 
make users wonder what is broken and why it is broken.

  sarnold@sec-trusty-amd64:~$ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04
  sarnold@sec-trusty-amd64:~$ dpkg -S gdk-pixbuf-query-loaders
  libgdk-pixbuf2.0-0:amd64: 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders
  sarnold@sec-trusty-amd64:~$ apt-cache policy libgdk-pixbuf2.0-0
  libgdk-pixbuf2.0-0:
Installed: 2.30.5-0ubuntu1
Candidate: 2.30.5-0ubuntu1
Version table:
   *** 2.30.5-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  sarnold@sec-trusty-amd64:~$ dpkg -S /usr/bin/gtk-update-icon-cache-3.0
  libgtk-3-bin: /usr/bin/gtk-update-icon-cache-3.0
  sarnold@sec-trusty-amd64:~$ apt-cache policy libgtk-3-bin
  libgtk-3-bin:
Installed: 3.10.7-0ubuntu2
Candidate: 3.10.7-0ubuntu2
Version table:
   *** 3.10.7-0ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  sarnold@sec-trusty-amd64:~$ 


  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgtk-3-bin 3.10.7-0ubuntu2
  ProcVersionSignature: User Name 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Wed Feb 19 14:38:47 2014
  InstallationDate: Installed on 2014-01-09 (41 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140108)
  ProcEnviron:
   TERM=rxvt-unicode
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1650022] Re: We need a "close" action for killing an app in a trust prompt

2018-02-16 Thread Matthew Paul Thomas

** No longer affects: ubuntu-ux

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

Title:
  We need a "close" action for killing an app in a trust prompt

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

Bug description:
  The original designs for trust prompts included a close action in the
  header to close apps that were opened in a trust session.  This is
  particularly important when apps might not behave well or hang, there
  is no way out.  The close action is like a back button to take you
  back out of the app.

  We're close to landing trust session support in content-hub, where
  we'll open source apps for content picking in a trust prompt.  We've
  found apps that have a tendency to hang, leaving the user no way out
  besides killing both the source and destination apps.  Clearly those
  apps need some fixing, but we need to give the user an easy way out.

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

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

[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

Ubuntu has long carried a patch which "Eliminate all references to
/etc/resolvconf/run." However, freedombox-setup contains the following
code in a preseed file.

# Make sure DNS lookup work after resolvconf is installed
# and set up the Freedombox.  Block init.d scripts from running using
# policy-rc.d to make sure dnsmasq do not overwrite the resolv.conf
# file we just inserted (and to keep services from starting in the chroot).
d-i preseed/late_command   string cp /etc/resolv.conf 
/target/etc/resolvconf/run/resolv.conf

That's not likely to work and has probably been broken for a long time
(without a bug report). So while freedombox-setup needs fixing it
doesn't seem important to anybody.



** Changed in: freedombox-setup (Ubuntu)
   Importance: Undecided => Low

** Changed in: freedombox-setup (Ubuntu)
   Status: New => Confirmed

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

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  Triaged
Status in avahi package in Ubuntu:
  Triaged
Status in bind9 package in Ubuntu:
  Triaged
Status in cloud-init package in Ubuntu:
  Incomplete
Status in cloud-initramfs-tools package in Ubuntu:
  Invalid
Status in dhcpcd5 package in Ubuntu:
  New
Status in dibbler package in Ubuntu:
  Won't Fix
Status in dnscrypt-proxy package in Ubuntu:
  Confirmed
Status in dnsmasq package in Ubuntu:
  New
Status in dnssec-trigger package in Ubuntu:
  Invalid
Status in fetchmail package in Ubuntu:
  Confirmed
Status in freedombox-setup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in ndisc6 package in Ubuntu:
  New
Status in netscript-2.4 package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  Confirmed
Status in postfix package in Ubuntu:
  New
Status in pppconfig package in Ubuntu:
  Confirmed
Status in pump package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid
Status in sendmail package in Ubuntu:
  New
Status in squid3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in unbound package in Ubuntu:
  New
Status in vpnc package in Ubuntu:
  New
Status in vpnc-scripts package in Ubuntu:
  New
Status in whereami package in Ubuntu:
  Triaged

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-androres

[Touch-packages] [Bug 1749993] [NEW] After turning low-resolution-graphics Dash is transparent to unusable state

2018-02-16 Thread grofaty

Public bug reported:

I have fresh installed Ubuntu 16.04 like two weeks ago or something. Today I 
have updated packages:
sudo apt update && sudo apt full-upgrade

I have noticed compiz and other packages updated and from article
http://www.omgubuntu.co.uk/2018/02/new-unity-desktop-update-now-
available I have seen it is now possible to turn on "low graphic mode"
which is excellent idea for my 14-years old 32-bit laptop.

I did:
gsettings set com.canonical.Unity lowgfx true

logged off and logged back in.

When I press Super key Dash is launched, but display is totally useless
way too transparent. See print screen.

I have never had such a problem. Turning low graphic mode off and this
problem disappears.

P.S. I also have the problem with Alt+Tab switcher now background in
switcher is white (if white background) it looks the same transparent
problem. I turn off low graphic mode, switcher is still white. This is
new problem after today Ubuntu update.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Feb 16 17:34:08 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GconfCompiz:
 /apps/compiz-1/plugins:
   /apps/compiz-1/plugins/unityshell:
/apps/compiz-1/plugins/unityshell/screen0:
 /apps/compiz-1/plugins/unityshell/screen0/options:
  dash_blur_experimental = 1
GraphicsCard:
 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a]
   Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a]
InstallationDate: Installed on 2018-01-20 (27 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
MachineType: LENOVO 1951F5G
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=0cdfefb9-a78c-458e-826e-f76c94537c2a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/12/2006
dmi.bios.vendor: LENOVO
dmi.bios.version: 79ET62WW (1.07 )
dmi.board.name: 1951F5G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr79ET62WW(1.07):bd06/12/2006:svnLENOVO:pn1951F5G:pvrThinkPadT60:rvnLENOVO:rn1951F5G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T60
dmi.product.name: 1951F5G
dmi.product.version: ThinkPad T60
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri Feb 16 16:56:33 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   16451 
 vendor LEN
xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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


** Tags: apport-bug compiz-0.9 i386 regression-update ubuntu xenial

** Attachment added: "dash_too_trasparent.png"
   
https://bugs.launchpad.net/bugs/1749993/+attachment/5056753/+files/dash_too_trasparent.png

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

Title:
  After turning low-resolution-graphics Dash is transparent to unusable
  state

Status in xorg package in Ubuntu:
  New

Bug description:
  I have fresh installed Ubuntu 16.04 like two weeks ago or something. Today I 
have updated packages:
  sudo apt update && sudo apt full-upgrade

  I have noticed compiz and other packages updated and from article
  http://www.omgubuntu.co.uk/2018/02/new-unity-desktop-update-now-
  available I have seen it is now possible to turn on "low gra

[Touch-packages] [Bug 1749985] Re: dpkg: error processing package libc-bin (--configure): triggers looping, abandoned

2018-02-16 Thread themusicgod1

using aptitude:

removed ufw, libav-tools
reinstalled tex-common, gconf2, menu, libc-bin

and then

reinstalled libav-tools

and I did not get this error.

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

Title:
  dpkg: error processing package libc-bin (--configure):  triggers
  looping, abandoned

Status in gconf2 package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in libav package in Ubuntu:
  New
Status in ufw package in Ubuntu:
  New

Bug description:
  While installing the latest round of updates for bionic via aptitude:

  Setting up libav-tools (7:3.4.2-1) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
ufw -> gconf2
   packages' pending triggers which are or may be unresolvable:
libc-bin: ldconfig
menu: /usr/share/menu
tex-common: texmf-format
gconf2: /usr/share/GConf/gsettings
ufw: /etc/ufw/applications.d
  dpkg: error processing package libc-bin (--configure):
   triggers looping, abandoned
  ...
  Setting up python3-all-dev (3.6.4-1) ...
  Processing triggers for menu (2.1.47ubuntu1) ...
  Processing triggers for tex-common (6.09) ...
  Building format(s) --all.
This may take some time... done.
  Errors were encountered while processing:
   libc-bin
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  Setting up libc-bin (2.26-0ubuntu2) ...
  Press Return to continue, 'q' followed by Return to quit.

  Ubuntu: bionic 18.04

  dpkg:
Installed: 1.19.0.5ubuntu1
Candidate: 1.19.0.5ubuntu1
Version table:
   *** 1.19.0.5ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  aptitude:
Installed: 0.8.10-6ubuntu1
Candidate: 0.8.10-6ubuntu1
Version table:
   *** 0.8.10-6ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  libc-bin:
Installed: 2.26-0ubuntu2
Candidate: 2.26-0ubuntu2
Version table:
   *** 2.26-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  menu:
Installed: 2.1.47ubuntu1
Candidate: 2.1.47ubuntu1
Version table:
   *** 2.1.47ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  tex-common:
Installed: 6.09
Candidate: 6.09
Version table:
   *** 6.09 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status
  gconf2:
Installed: 3.2.6-4ubuntu1
Candidate: 3.2.6-4ubuntu1
Version table:
   *** 3.2.6-4ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  ufw:
Installed: 0.35-5
Candidate: 0.35-5
Version table:
   *** 0.35-5 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status
  libav-tools:
Installed: 7:3.4.2-1
Candidate: 7:3.4.2-1
Version table:
   *** 7:3.4.2-1 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libc-bin 2.26-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Fri Feb 16 16:08:12 2018
  Dependencies:
   gcc-8-base 8-20180208-0ubuntu1
   libc6 2.26-0ubuntu2
   libgcc1 1:8-20180208-0ubuntu1
  InstallationDate: Installed on 2016-05-07 (649 days ago)
  InstallationMedia:
   
  JournalErrors:
   Hint: You are currently not seeing messages from other users and the system.
 Users in groups 'adm', 'systemd-journal' can see all messages.
 Pass -q to turn off this notice.
   -- Logs begin at Thu 2018-01-04 17:12:35 UTC, end at Fri 2018-02-16 04:45:37 
UTC. --
   -- No entries --
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: glibc
  UpgradeStatus: Upgraded to bionic on 2017-11-20 (87 days ago)

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

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

[Touch-packages] [Bug 1749985] Re: dpkg: error processing package libc-bin (--configure): triggers looping, abandoned

2018-02-16 Thread themusicgod1

installed packages via dpkg -l

** Attachment added: "installed packages via dpkg -l"
   
https://bugs.launchpad.net/ubuntu/+source/gconf2/+bug/1749985/+attachment/5056751/+files/installed.txt

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

Title:
  dpkg: error processing package libc-bin (--configure):  triggers
  looping, abandoned

Status in gconf2 package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in libav package in Ubuntu:
  New
Status in ufw package in Ubuntu:
  New

Bug description:
  While installing the latest round of updates for bionic via aptitude:

  Setting up libav-tools (7:3.4.2-1) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
ufw -> gconf2
   packages' pending triggers which are or may be unresolvable:
libc-bin: ldconfig
menu: /usr/share/menu
tex-common: texmf-format
gconf2: /usr/share/GConf/gsettings
ufw: /etc/ufw/applications.d
  dpkg: error processing package libc-bin (--configure):
   triggers looping, abandoned
  ...
  Setting up python3-all-dev (3.6.4-1) ...
  Processing triggers for menu (2.1.47ubuntu1) ...
  Processing triggers for tex-common (6.09) ...
  Building format(s) --all.
This may take some time... done.
  Errors were encountered while processing:
   libc-bin
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  Setting up libc-bin (2.26-0ubuntu2) ...
  Press Return to continue, 'q' followed by Return to quit.

  Ubuntu: bionic 18.04

  dpkg:
Installed: 1.19.0.5ubuntu1
Candidate: 1.19.0.5ubuntu1
Version table:
   *** 1.19.0.5ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  aptitude:
Installed: 0.8.10-6ubuntu1
Candidate: 0.8.10-6ubuntu1
Version table:
   *** 0.8.10-6ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  libc-bin:
Installed: 2.26-0ubuntu2
Candidate: 2.26-0ubuntu2
Version table:
   *** 2.26-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  menu:
Installed: 2.1.47ubuntu1
Candidate: 2.1.47ubuntu1
Version table:
   *** 2.1.47ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  tex-common:
Installed: 6.09
Candidate: 6.09
Version table:
   *** 6.09 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status
  gconf2:
Installed: 3.2.6-4ubuntu1
Candidate: 3.2.6-4ubuntu1
Version table:
   *** 3.2.6-4ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  ufw:
Installed: 0.35-5
Candidate: 0.35-5
Version table:
   *** 0.35-5 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status
  libav-tools:
Installed: 7:3.4.2-1
Candidate: 7:3.4.2-1
Version table:
   *** 7:3.4.2-1 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libc-bin 2.26-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Fri Feb 16 16:08:12 2018
  Dependencies:
   gcc-8-base 8-20180208-0ubuntu1
   libc6 2.26-0ubuntu2
   libgcc1 1:8-20180208-0ubuntu1
  InstallationDate: Installed on 2016-05-07 (649 days ago)
  InstallationMedia:
   
  JournalErrors:
   Hint: You are currently not seeing messages from other users and the system.
 Users in groups 'adm', 'systemd-journal' can see all messages.
 Pass -q to turn off this notice.
   -- Logs begin at Thu 2018-01-04 17:12:35 UTC, end at Fri 2018-02-16 04:45:37 
UTC. --
   -- No entries --
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: glibc
  UpgradeStatus: Upgraded to bionic on 2017-11-20 (87 days ago)

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

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

[Touch-packages] [Bug 1749985] [NEW] dpkg: error processing package libc-bin (--configure): triggers looping, abandoned

2018-02-16 Thread themusicgod1

Public bug reported:

While installing the latest round of updates for bionic via aptitude:

Setting up libav-tools (7:3.4.2-1) ...
dpkg: cycle found while processing triggers:
 chain of packages whose triggers are or may be responsible:
  ufw -> gconf2
 packages' pending triggers which are or may be unresolvable:
  libc-bin: ldconfig
  menu: /usr/share/menu
  tex-common: texmf-format
  gconf2: /usr/share/GConf/gsettings
  ufw: /etc/ufw/applications.d
dpkg: error processing package libc-bin (--configure):
 triggers looping, abandoned
...
Setting up python3-all-dev (3.6.4-1) ...
Processing triggers for menu (2.1.47ubuntu1) ...
Processing triggers for tex-common (6.09) ...
Building format(s) --all.
This may take some time... done.
Errors were encountered while processing:
 libc-bin
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up libc-bin (2.26-0ubuntu2) ...
Press Return to continue, 'q' followed by Return to quit.

Ubuntu: bionic 18.04

dpkg:
  Installed: 1.19.0.5ubuntu1
  Candidate: 1.19.0.5ubuntu1
  Version table:
 *** 1.19.0.5ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
aptitude:
  Installed: 0.8.10-6ubuntu1
  Candidate: 0.8.10-6ubuntu1
  Version table:
 *** 0.8.10-6ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
libc-bin:
  Installed: 2.26-0ubuntu2
  Candidate: 2.26-0ubuntu2
  Version table:
 *** 2.26-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
menu:
  Installed: 2.1.47ubuntu1
  Candidate: 2.1.47ubuntu1
  Version table:
 *** 2.1.47ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status
tex-common:
  Installed: 6.09
  Candidate: 6.09
  Version table:
 *** 6.09 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
100 /var/lib/dpkg/status
gconf2:
  Installed: 3.2.6-4ubuntu1
  Candidate: 3.2.6-4ubuntu1
  Version table:
 *** 3.2.6-4ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status
ufw:
  Installed: 0.35-5
  Candidate: 0.35-5
  Version table:
 *** 0.35-5 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
100 /var/lib/dpkg/status
libav-tools:
  Installed: 7:3.4.2-1
  Candidate: 7:3.4.2-1
  Version table:
 *** 7:3.4.2-1 500
500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic/universe i386 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libc-bin 2.26-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Fri Feb 16 16:08:12 2018
Dependencies:
 gcc-8-base 8-20180208-0ubuntu1
 libc6 2.26-0ubuntu2
 libgcc1 1:8-20180208-0ubuntu1
InstallationDate: Installed on 2016-05-07 (649 days ago)
InstallationMedia:
 
JournalErrors:
 Hint: You are currently not seeing messages from other users and the system.
   Users in groups 'adm', 'systemd-journal' can see all messages.
   Pass -q to turn off this notice.
 -- Logs begin at Thu 2018-01-04 17:12:35 UTC, end at Fri 2018-02-16 04:45:37 
UTC. --
 -- No entries --
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: glibc
UpgradeStatus: Upgraded to bionic on 2017-11-20 (87 days ago)

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

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

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

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


** Tags: amd64 apport-bug bionic

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

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

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

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

Title:
  dpkg: error processing package libc-bin (--configure):  triggers
  looping, abandoned

Status in gconf2 package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in libav package in Ubuntu:
  New
Status in ufw package in Ubuntu:
  New

Bug description:
  While installing the latest round of updates for bionic via aptitude:

  Setting up libav-tools (7:3.4.2-1) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be respons

[Touch-packages] [Bug 993298] Re: Please make NetworkManager-controlled dnsmasq respect /etc/hosts

2018-02-16 Thread L-reimann

+1 Also affects me. Took me quite some time to find this bug report.
Very unusual behavior.

Using a hosts.conf in /etc/NetworkManager/dnsmasq.d with the content is not
able to simulate multiple IP addresses for one FQDN:
address=/admin.app/127.0.0.1

>From the manpage:
-A, --address=//[domain/][]

Specify an IP address to return for any host in the given domains.
Queries in the domains are never forwarded and always replied to with
the specified IP address which may be IPv4 or IPv6. To give both IPv4
and IPv6 addresses for a domain, use repeated -A flags. Note that
/etc/hosts and DHCP leases override this for individual names.

This is untrue if the --no-hosts is forced upon us. Also I do not like
to restart services to modify a host entry.

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

Title:
Please make NetworkManager-controlled dnsmasq respect /etc/hosts

Status in network-manager package in Ubuntu:
Confirmed

Bug description:
Since 12.04 NetworkManager uses the dnsmasq plugin by default to
resolve DNS requests. Unfortunately the dnsmasq plug-in has --no-
hosts, etc. hard coded [1] which means (among other things) that after
the upgrade to 12.04 /etc/hosts will no longer be used to resolve DNS
requests. This changes the prior behavior of NetworkManager without
any visible warning to the end user. AFAICS there's no other way to
work around this problem as to manually revert the change and disable
the dnsmasq plug-in in the NetworkManager config, see [2,3]:

"To turn off dnsmasq in Network Manager, you need to edit
/etc/NetworkManager/NetworkManager.conf and comment the 'dns=dnsmasq'
line then do a 'sudo restart network-manager'."

This is of course not a bug in the NetworkManager which just behaves
as intended. The problem is in the change of the configuration of the
Ubuntu packaging which will probably leave many wondering why their
/etc/hosts suddenly no longer works. This cost me considerable time to
debug and probably is a usability problem for others, too.

Maybe you could provide a more visible documentation than that in [3]?
E.g., *including a comment in /etc/hosts that explains the change* and
how to work around it would have saved me a lot of time. It would have
automatically alerted me on upgrade as manual changes to /etc/hosts
would then have triggered a prompt while leaving those users with
standard /etc/hosts in peace.

Probably similar problems arise with other disabled config files and
could be alerted to the users? Thinking of resolv.conf, etc.

[1]
http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/dnsmasq-manager/nm-dnsmasq-manager.c,
line 285
[2] i.e. http://ubuntuforums.org/showthread.php?t=1968061
[3] http://www.stgraber.org/2012/02/24/dns-in-ubuntu-12-04/

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

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

[Touch-packages] [Bug 1282294] Re: "Cannot open pixbuf loader module file"

2018-02-16 Thread Ken Sharp

** Tags added: i386 xenial

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

Title:
  "Cannot open pixbuf loader module file"

Status in gdk-pixbuf package in Ubuntu:
  Triaged
Status in gdk-pixbuf package in Debian:
  New

Bug description:
  While doing testing on trusty, I keep finding errors like the
  following in my apt-get -u dist-upgrade output:

  Preparing to unpack 
.../indicator-printers_0.1.7+14.04.20140213-0ubuntu1_amd64.deb ...
  Unpacking indicator-printers (0.1.7+14.04.20140213-0ubuntu1) over 
(0.1.7daily13.03.01-0ubuntu1) ...

  (gtk-update-icon-cache-3.0:29671): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.

  (gtk-update-icon-cache-3.0:29672): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.
  ...
  Processing triggers for hicolor-icon-theme (0.13-1) ...

  (gtk-update-icon-cache-3.0:32198): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.

  
  These errors make it difficult to look for errors that I might have 
introduced in my own packages and if they persist in our final product will 
make users wonder what is broken and why it is broken.

  sarnold@sec-trusty-amd64:~$ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04
  sarnold@sec-trusty-amd64:~$ dpkg -S gdk-pixbuf-query-loaders
  libgdk-pixbuf2.0-0:amd64: 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders
  sarnold@sec-trusty-amd64:~$ apt-cache policy libgdk-pixbuf2.0-0
  libgdk-pixbuf2.0-0:
Installed: 2.30.5-0ubuntu1
Candidate: 2.30.5-0ubuntu1
Version table:
   *** 2.30.5-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  sarnold@sec-trusty-amd64:~$ dpkg -S /usr/bin/gtk-update-icon-cache-3.0
  libgtk-3-bin: /usr/bin/gtk-update-icon-cache-3.0
  sarnold@sec-trusty-amd64:~$ apt-cache policy libgtk-3-bin
  libgtk-3-bin:
Installed: 3.10.7-0ubuntu2
Candidate: 3.10.7-0ubuntu2
Version table:
   *** 3.10.7-0ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  sarnold@sec-trusty-amd64:~$ 


  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgtk-3-bin 3.10.7-0ubuntu2
  ProcVersionSignature: User Name 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Wed Feb 19 14:38:47 2014
  InstallationDate: Installed on 2014-01-09 (41 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140108)
  ProcEnviron:
   TERM=rxvt-unicode
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1717995] Re: extra domains not removed from resolv.conf when VPN disconnects

2018-02-16 Thread mrvanes

It seems this systemd bug is related and is supposed to be fixed. I still 
experience the problem however:
https://github.com/systemd/systemd/issues/7305

** Bug watch added: github.com/systemd/systemd/issues #7305
   https://github.com/systemd/systemd/issues/7305

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

Title:
  extra domains not removed from resolv.conf when VPN disconnects

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  I use a VPN (network manager "vpnc" config) to connect to my work
  network.  The gateway is "webvpn.purestorage.com".  When I connect, I
  get "purestorage.com" added to the "search" line in my
  /etc/resolv.conf (and /run/resolvconf/interface/systemd-resolved) -
  which makes perfect sense, the VPN passes this info to me and then I
  can connect to systems within the work network without having to use a
  FQDN.

  The bug (which is a regression from older versions of Ubuntu) is that
  when I lose my connection to the VPN (either because I disconnect
  explicitly, or because the network goes down or I suspend my laptop),
  the "purestorage.com" domain is not removed from those "search" lines.
  And for some reason this prevents me from resolving
  webvpn.purestorage.com (which prevents me from reconnecting to the
  VPN).

  In particular, if I connect and disconnect my VPN, I get:

   $ systemd-resolve webvpn.purestorage.com
  webvpn.purestorage.com: resolve call failed: No appropriate name servers or 
networks for name found

  If I then edit /etc/resolv.conf by hand to remove all the
  purestorage.com entries from the search line - in other words, change

   $ cat /etc/resolv.conf 
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  search home.digitalvampire.org purestorage.com dev.purestorage.com

  to

   $ cat /etc/resolv.conf 
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  search home.digitalvampire.org

  and change nothing else, then:

   $ systemd-resolve webvpn.purestorage.com
  webvpn.purestorage.com: 192.30.189.1
  (vpn.purestorage.com)

  -- Information acquired via protocol DNS in 25.9ms.
  -- Data is authenticated: no

  
  I'm not sure if the bug is in systemd, network manager, or some other 
package, but I'm happy to try any debugging that is helpful to resolve this (no 
pun intended).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu10
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 11:20:17 2017
  InstallationDate: Installed on 2016-09-01 (381 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160901)
  MachineType: LENOVO 20FRS2FK00
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic 
root=UUID=30d5ada5-835d-4cf7-96cf-3329c0316107 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-07-26 (53 days ago)
  dmi.bios.date: 07/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET53W (1.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FRS2FK00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET53W(1.27):bd07/13/2017:svnLENOVO:pn20FRS2FK00:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2FK00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 1st
  dmi.product.name: 20FRS2FK00
  dmi.product.version: ThinkPad X1 Yoga 1st
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

2018-02-16 Thread Michele Bordi

Thank you to all for your work, from another "simple user" really looking
into this fix update :)

2018-02-16 15:20 GMT+01:00 Jeremy Bicha :

> Jon, the changelog message said that this bug was fixed in bionic (which
> is Ubuntu 18.04 Alpha). The bug is not fixed in Ubuntu 14.04 LTS
> "Trusty" yet.
>
> Maybe it's a bit more clear if you look at the bug page:
> https://launchpad.net/bugs/1714518
>
> I closed the Thunderbird task because we believe this bug can be fixed
> in the gtk+3.0 package without needing to update Thunderbird and several
> other packages.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1579543).
> https://bugs.launchpad.net/bugs/1714518
>
> Title:
>   GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
>   shares in file chooser
>
> Status in GTK+:
>   Fix Released
> Status in gtk+3.0 package in Ubuntu:
>   Fix Released
> Status in gtk+3.0 source package in Trusty:
>   Triaged
> Status in gtk+3.0 source package in Xenial:
>   Triaged
> Status in gtk+3.0 source package in Artful:
>   Triaged
>
> Bug description:
>   Steps to reproduce:
>   1. Install any Gtk3 application such as Firefox or Chromium which use
> modern file-chooser dialog.
>   2. Mount network location through fstab or file-manager ("smb://" =
> SMB/CIFS, "sftp://"; = SFTP/SSH and so on)
>   3. Try to save/open file to/from the remote location from Gtk3
> application.
>
>   Expected results:
>   * user is able to find network folder and save/open file to/from it with
> GtkFileChooser dialog
>
>   Actual results:
>   * user is unable to find network folder and save/open file to/from it
> with GtkFileChooser dialog and many user applications are affected
>
>   
> -
>   Original bug description is below:
>
>   GTK+3 doesn't show FUSE network shares in file chooser - it used to do
>   so in GTK+2, and the GTK+3 documentation still mentions it should do
>   it.
>
>   In the mean time, every user of every application switching to GTK+3
>   -- including Chromium, at some point between 58 and 60 -- (a change
>   which happened in 16.04 LTS!!), loses the functionality to open or
>   save directly to a network share.
>
>   I had chosen 16.04 LTS for deploying our workstations at work, and my 50
> users have been suddenly unable to do a simple operation they have to do
> dozens of times a day.
>   They now have to "buffer" these files to their local filesystem when
> saving them and before uploading them, and then copy them to the company's
> network shares.
>   They were already a little bit grumpy when it stopped working with
> Firefox, and are now really side-eyeing me when they apply updates and find
> Chromium broken.
>
>   I have reported the bug upstream and provided a patch to fix this. I
>   hope you'll be able and willing to include it to Ubuntu's GTK+3
>   package.
>
>   Thanks in advance.
>
>   Colin
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gtk/+bug/1714518/+subscriptions
>

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

Title:
  GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
  shares in file chooser

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Trusty:
  Triaged
Status in gtk+3.0 source package in Xenial:
  Triaged
Status in gtk+3.0 source package in Artful:
  Triaged

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium which use modern 
file-chooser dialog. 
  2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://"; = SFTP/SSH and so on)
  3. Try to save/open file to/from the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving

[Touch-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

2018-02-16 Thread Scott Moser

** Description changed:

  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  
  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
-   Installed: 4.13.0-16.19
-   Candidate: 4.13.0-16.19
-   Version table:
-  *** 4.13.0-16.19 500
- 500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
- 100 /var/lib/dpkg/status
+   Installed: 4.13.0-16.19
+   Candidate: 4.13.0-16.19
+   Version table:
+  *** 4.13.0-16.19 500
+ 500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
+ 100 /var/lib/dpkg/status
  
  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.
  
  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath
  
- 
- It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.
+ It appears that since the initramfs loads the bcache module which probes
+ and finds all of the cache devices and backing devices then once the
+ rootfs is mounted and udev gets to run, the bcache kernel module does
+ not emit the CACHED_UUID value into the environment if the underlying
+ devices are already registered.
  
  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:
  
  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1
  
  then rootfs ismounted and systemd starts systemd-udev
  
  [9.350889] systemd[1]: Listening on udev Kernel Socket.
  
  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails
  
  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered
  
  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:
  
  bcache_register()
-   register_bdev()
- bch_cached_dev_run()
-   kobject_uevent_env(&disk_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);
-   
- where env includes: 
- "DRIVER=bcache",
- kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
- NULL,
- NULL,
- };
+   register_bdev()
+ bch_cached_dev_run()
+   kobject_uevent_env(&disk_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);
+ 
+ where env includes:
+ "DRIVER=bcache",
+ kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
+ NULL,
+ NULL,
+ };
  
  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
-  total 0
-  crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
-  crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
+  total 0
+  crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
+  crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
-  Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
-  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+  Bus 001 Device 002: ID 0627:0001 Adomax Technol

[Touch-packages] [Bug 1749670] Re: Display Arrangement is changed after changing the Display Mode

2018-02-16 Thread Robert Walter

Also includes other properties like "Scale". Changing between "Join
Display" and "External Only" switches the scale to 100%.

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

Title:
  Display Arrangement is changed after changing the Display Mode

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  The Display Arrangement is changed after changing the Display Mode
  (single display, mirror, join displays).

  I have a notebook connected to an external display which is physically
  placed on the right side of the notebook and which I typically is as
  my primary display.

  The default seems to be that the primary display is the notebook ones
  on the left and the joined external on the right. In the Gnome display
  settings I can change both to make the external display the primary
  one and move it to the right. So far all perfect.

  However I often disable my notebook display. Typically using the
  %SUPER%-P shortcut but also using the Gnome display settings.
  Unfortunately when I switch back to joined displays the placement gets
  messed up. While it is remembered that my external was chosen as the
  primary one (opposed to the default) the placement gets reset and the
  primary display is assumed to be on the right despite having it
  arranged it the Gnome Display settings to the right before. As a
  result I have to re-arrange it manually using the Gnome Display
  settings every time I switch back to joined displays.

  Is there anyway to make Ubuntu/Gnome/Xorg remember the display
  arrangement? Or as a workaround switch the arrangement with another
  shortcut?

  P.S. I'm using Xorg and NVIDIA 390.25 drivers from the graphics PPA in
  case that's important in any way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.25  Wed Jan 24 20:02:43 
PST 2018
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 10:52:43 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-31-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-32-generic, x86_64: installed
   nvidia-390, 390.25, 4.13.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation GP104M [GeForce GTX 1070 Mobile] [10de:1be1] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GP104M [GeForce GTX 1070 Mobile] 
[1558:65a4]
  InstallationDate: Installed on 2018-01-16 (29 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Notebook P65_67HSHP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=5b2c0693-6cca-4666-9bfc-7ecb40dee064 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RTR1 02/21/2017
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67HSHP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RTR102/21/2017:bd02/21/2017:svnNotebook:pnP65_67HSHP:pvrNotApplicable:rvnNotebook:rnP65_67HSHP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67HSHP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about

[Touch-packages] [Bug 1749670] Re: Display Arrangement is changed after changing the Display Mode

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

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

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

Title:
  Display Arrangement is changed after changing the Display Mode

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  The Display Arrangement is changed after changing the Display Mode
  (single display, mirror, join displays).

  I have a notebook connected to an external display which is physically
  placed on the right side of the notebook and which I typically is as
  my primary display.

  The default seems to be that the primary display is the notebook ones
  on the left and the joined external on the right. In the Gnome display
  settings I can change both to make the external display the primary
  one and move it to the right. So far all perfect.

  However I often disable my notebook display. Typically using the
  %SUPER%-P shortcut but also using the Gnome display settings.
  Unfortunately when I switch back to joined displays the placement gets
  messed up. While it is remembered that my external was chosen as the
  primary one (opposed to the default) the placement gets reset and the
  primary display is assumed to be on the right despite having it
  arranged it the Gnome Display settings to the right before. As a
  result I have to re-arrange it manually using the Gnome Display
  settings every time I switch back to joined displays.

  Is there anyway to make Ubuntu/Gnome/Xorg remember the display
  arrangement? Or as a workaround switch the arrangement with another
  shortcut?

  P.S. I'm using Xorg and NVIDIA 390.25 drivers from the graphics PPA in
  case that's important in any way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.25  Wed Jan 24 20:02:43 
PST 2018
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 10:52:43 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-31-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-32-generic, x86_64: installed
   nvidia-390, 390.25, 4.13.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation GP104M [GeForce GTX 1070 Mobile] [10de:1be1] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GP104M [GeForce GTX 1070 Mobile] 
[1558:65a4]
  InstallationDate: Installed on 2018-01-16 (29 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Notebook P65_67HSHP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=5b2c0693-6cca-4666-9bfc-7ecb40dee064 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RTR1 02/21/2017
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67HSHP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RTR102/21/2017:bd02/21/2017:svnNotebook:pnP65_67HSHP:pvrNotApplicable:rvnNotebook:rnP65_67HSHP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67HSHP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notification

[Touch-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

2018-02-16 Thread Jeremy Bicha

Jon, the changelog message said that this bug was fixed in bionic (which
is Ubuntu 18.04 Alpha). The bug is not fixed in Ubuntu 14.04 LTS
"Trusty" yet.

Maybe it's a bit more clear if you look at the bug page:
https://launchpad.net/bugs/1714518

I closed the Thunderbird task because we believe this bug can be fixed
in the gtk+3.0 package without needing to update Thunderbird and several
other packages.

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

Title:
  GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
  shares in file chooser

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Trusty:
  Triaged
Status in gtk+3.0 source package in Xenial:
  Triaged
Status in gtk+3.0 source package in Artful:
  Triaged

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium which use modern 
file-chooser dialog. 
  2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://"; = SFTP/SSH and so on)
  3. Try to save/open file to/from the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

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

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

[Touch-packages] [Bug 1707898] Re: systemd translations are not synced with upstream

2018-02-16 Thread Jeremy Bicha

Martin, a small number of packages Build-Depend on policykit-1 only for
the .its file so moving that file will mean we'll need to update those
packages. One example is gnome-multi-writer.

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

Title:
  systemd translations are not synced with upstream

Status in systemd:
  New
Status in Ubuntu Translations:
  New
Status in policykit-1 package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Translations for systemd are outdated because they do not seem to be
  synced with the upstream ones.

  For example the Czech one:
  Launchpad: 
https://translations.launchpad.net/ubuntu/artful/+source/systemd/+pots/systemd/cs/+translate
 - 0% translated
  Upstream: https://github.com/systemd/systemd/blob/master/po/cs.po - 100% 
translated

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

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

[Touch-packages] [Bug 1707898] Re: systemd translations are not synced with upstream

2018-02-16 Thread Gunnar Hjalmarsson

I notice that gschema.{its,loc} is included in libglib2.0-dev, so simply
moving polkit.{its,loc} to libpolkit-gobject-1-dev wouldn't be the only
example of xml format descriptions provided by a -dev package.

I attached a policykit patch (Debian) with this change.

** Patch added: 
"0001-Install-xml-format-descriptions-via-libpolkit-gobjec.patch"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1707898/+attachment/5056651/+files/0001-Install-xml-format-descriptions-via-libpolkit-gobjec.patch

** Also affects: policykit-1 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: policykit-1 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: policykit-1 (Ubuntu)
   Status: New => In Progress

** Changed in: policykit-1 (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  systemd translations are not synced with upstream

Status in systemd:
  New
Status in Ubuntu Translations:
  New
Status in policykit-1 package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Translations for systemd are outdated because they do not seem to be
  synced with the upstream ones.

  For example the Czech one:
  Launchpad: 
https://translations.launchpad.net/ubuntu/artful/+source/systemd/+pots/systemd/cs/+translate
 - 0% translated
  Upstream: https://github.com/systemd/systemd/blob/master/po/cs.po - 100% 
translated

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

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

[Touch-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2018-02-16 Thread Dimitri John Ledkov

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  New
Status in chrony package in Ubuntu:
  Confirmed
Status in clamav package in Ubuntu:
  New
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  New
Status in ifmetric package in Ubuntu:
  New
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  New
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Committed
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  New
Status in vzctl package in Ubuntu:
  New
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  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: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 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: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1748709] Re: Upgrade from xenial to bionic wants to replace moduli

2018-02-16 Thread ChristianEhrhardt

Hi Mark,
the file is installed from the build, not generated on install.
Install is by debian/openssh-client.install

It also is considered a conffile for the sense ot change tracking.
$ dpkg --status openssh-client
[...]
Conffiles:
/etc/ssh/moduli 0075fd4b72a421f909af9809d0dd3bdc

A quick check showed that they are the same on all xenial systems I ever
touched even across architectures.
oO lets hope this is not a comeback of the "same key on all systems" issue :-/

A check across distributions and releases showed me:
1. at least in a given Ubuntu release all systems have the same file
2. Debian is the same, e.g. buster/bionic match
3. all Fedora are the same, but different to Ubuntu/Debian
4. if removing the version tracking header on Fedora it is the same as
Ubuntu/Debian

Hmm, either this is broken everywhere or this doesn't have to be that
unique.

The file is actually provided by upstream, that is the reason why the
only change found is on upgrading versions if e.g. upstream deprecated
some. E.g. after the Snowden leaks those with less than 2k were removed.

There are articles mentioning that it might be useful to regenerate that
like [1][2], but no hard requirement to do so it seems.

So it seems a hardening action, but not a hard requirement to be unique.
Note: a regen run takes quite a few cpu cycles and time - I measured the two
steps to be:
- ssh-keygen -G took 8:57.55 with 534.61 seconds cpu load
- ssh-keygen -T I aborted this at 33% at 30:31.67 with 1816.35 seconds cpu load
Lets assume it is 1-2 hours, not even thinking about raspi's and such.
That is clearly too much for an instance instantiation, even too much for a
default package install later on.

Furthermore I'd like to quote this from [3] which might be a good reason it is
even less important these days than we thought at first.
"Regardless, the moduli file is only used when using the Diffie-Hellman Group
Exchange method, which isn’t the default key exchange."

>From man sshd_config in Bionic the current order seems:
curve25519-sha256,curve25519-sha...@libssh.org,
ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1

So maybe (but only maybe) a ssh-extra-security package doing so as suggests or
helper tool bundled to openssh that would do the update might be a nice
security addition.
I'm adding the security Team to weight in on opinions:
- should it be unique per system?
- if so, preferred delivery mechanism
- might an individual generated moduli file decrease security compared to a
"curated and reviewed" shared one? There are mentions of "Ssh-keygen’s
primality tests are statistical tests and can lead to false positives." that
make me think so.

@Mark - all that does not explain why you got the upgrade message thou. I'd
assume you had not changed your file - so it should have silently be upgraded
to the new version IMHO.
Have you custom generated your's in the past?
If there still is a dpkg-old version of it what is the checksum (Xenial was
0075fd4b72a421f909af9809d0dd3bdc)?

[1]: https://stribika.github.io/2015/01/04/secure-secure-shell.html
[2]:
https://security.stackexchange.com/questions/79043/is-it-considered-worth-it-to-replace-opensshs-moduli-file
[3]: https://entropux.net/article/openssh-moduli

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

Title:
Upgrade from xenial to bionic wants to replace moduli

Status in openssh package in Ubuntu:
New

Bug description:
I see this on upgrade on one machine, which is unexpected. If this
file is generated by each machine, why would we ship a default?

Configuration file '/etc/ssh/moduli'
==> Modified (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.
*** moduli (Y/I/N/O/D/Z) [default=N] ?

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

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

[Touch-packages] [Bug 1748659] Re: Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess retur

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

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

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

Title:
  Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3
  failed to install/upgrade: installed systemd package post-installation
  script subprocess returned error exit status 1

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This was fresh Ubuntu 16.04 instance on Windows 10, running inside a
  Virtual Box on an iMac. I did an apt-get dist-upgrade before
  attempting to upgrade to 18.04.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Function not implemented
  Date: Sat Feb 10 18:59:28 2018
  Dmesg:
   
  ErrorMessage: installed systemd package post-installation script subprocess 
returned error exit status 1
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcInterrupts:
   
  ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro
  ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 
2: sort: cannot read: /proc/modules: No such file or directory
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.2.24
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: package systemd 235-3ubuntu3 failed to install/upgrade: installed 
systemd package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-02-10 (0 days ago)

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

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

[Touch-packages] [Bug 1662814] Re: dhclient doesn't honor metric setting in network interfaces on ubuntu 16.04

2018-02-16 Thread Stanislav Makar

ifmetric package will help you and patch is not needed anymore

sudo apt-get install ifmetric -y

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

Title:
  dhclient doesn't honor metric setting in network interfaces on ubuntu
  16.04

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  $ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.04
  DISTRIB_CODENAME=xenial
  DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"

  $ dpkg-query -l isc-dhcp-client
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name Version  
 Architecture  Description
  
+++--=-=-==
  ii  isc-dhcp-client  
4.3.3-5ubuntu12.6 amd64 
DHCP client for automatically obtaining an IP address

  # configure metric in network interface
  $ cat /etc/network/interfaces.d/ens4.cfg 
  auto ens4
  iface ens4 inet dhcp
metric 1000

  # dhclient set IF_METRIC=1000 environment variable for ens4
  $ ps xau|egrep -i 'dhclient'
  root 27906  0.0  0.0  16120   864 ?Ss   08:35   0:00 
/sbin/dhclient -1 -v -pf /run/dhclient.ens3.pid -lf 
/var/lib/dhcp/dhclient.ens3.leases -I -df /var/lib/dhcp/dhclient6.ens3.leases 
ens3
  root 28392  0.0  0.0  16120   868 ?Ss   08:59   0:00 
/sbin/dhclient -1 -v -pf /run/dhclient.ens4.pid -lf 
/var/lib/dhcp/dhclient.ens4.leases -I -df /var/lib/dhcp/dhclient6.ens4.leases 
ens4 -e IF_METRIC=1000

  $ route -nee
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface 
   MSS   Window irtt
  0.0.0.0 xxx.xxx.xxx.xxx 0.0.0.0 UG0  00 ens3  
   0 0  0
  xxx.xxx.xxx.xxx 0.0.0.0 255.255.255.192 U 0  00 ens3  
   0 0  0
  172.16.0.0  192.168.12.1255.240.0.0 UG0  00 ens4  
   0 0  0
  192.168.0.0 192.168.12.1255.255.0.0 UG0  00 ens4  
   0 0  0
  192.168.12.00.0.0.0 255.255.255.0   U 0  00 ens4  
   0 0  0

  After ifdown ens4, ifup ens4, dhclient doens't configure metric for
  ens4 routes.

  below patch fix this issue.

  --- /etc/dhcp/dhclient-exit-hooks.d/rfc3442-classless-routes2017-02-08 
08:59:16.407956495 +
  +++ ./rfc3442-classless-routes  2017-02-08 08:58:58.328337696 +
  @@ -71,7 +71,7 @@
   
  # set route (ip detects host routes 
automatically)
  ip -4 route add 
"${net_address}/${net_length}" \
  -   ${via_arg} dev "${interface}" 
>/dev/null 2>&1
  +   ${via_arg} dev "${interface}" 
${IF_METRIC:+metric $IF_METRIC} >/dev/null 2>&1
  done
  fi
  fi

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

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

[Touch-packages] [Bug 1749688] Re: 16.04 HWE -> 18.04 = xorg held back (+ partial breakage because of it)

2018-02-16 Thread Timo Aaltonen

needs a new release of xorg-lts-transitional in bionic, which I've got
halfway done

** Package changed: xorg (Ubuntu) => xorg-lts-transitional (Ubuntu)

** Changed in: xorg-lts-transitional (Ubuntu)
   Status: New => In Progress

** Changed in: xorg-lts-transitional (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  16.04 HWE -> 18.04 = xorg held back (+ partial breakage because of it)

Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in xorg-lts-transitional package in Ubuntu:
  In Progress

Bug description:
  When upgrading from a 16.04 installation which had HWE (later point
  releases) xorg is getting held back as apt is having trouble resolving
  the path from xserver-xorg-core-hwe-16.04 to xserver-xorg-core.

  In at least one instance I've seen a system from a user POV completely
  break because of that as it failed to get any keyboard input. Forcing
  xorg to get properly installed fixes any and all issues as expected.

  - devel upgrade from xenial to bionic
  - restart
  - xorg not upgraded
  - try to get a hold of tty or repair mode
  - sudo apt install dist-upgrade && sudo apt install xorg
  - restart
  - working system

  I am going to attach logs for an ubuntu-desktop system, but I've also
  seen this with kubuntu-desktop and the derived neon-desktop. It's a
  bit unclear to me why apt is having trouble with the resolution, it
  does seem like a fairly serious problem though.

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

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

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

2018-02-16 Thread Charlie

Christopher, I am currently running Ubuntu 17.10 64 bit, Mate 1.18.0,
kernel 4.13.0-30-generic X86_64. I have not seen this problem for a long
time and it's so long ago now I'm afraid that I don't recall whether it
occurred after an update. I have attached current Xorg log.

I am also running Ubuntu 18.04 in Vbox and not seeing the issue.

Sorry I can't be of more help but can upload more current logs if of any
use.

** Attachment added: "Xorg0_log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1704660/+attachment/5056567/+files/Xorg0_log.txt

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Using two monitors:

  1. Moved an image from picture folder to primary secondary monitor
  desktop

  2. Opened a folder on primary monitor

  3. Tried to drag image file into - file 'declines and mouse curser is
  now a fist icon and mouse clicks on image have no effect.

  4. Logged out and right click mouse menu is back and I can send the
  image to rubbish bin and return to the desktop but issue still occurs
  and is repeatable.

  I realize that this may not be a Xorg problem but not sure what is
  causing my issue. Happy to carry out more tests/supply more
  information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic i686
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: i386
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Jul 16 17:20:37 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: Dell Radeon HD 6670 [1028:0b0e]
  InstallationDate: Installed on 2017-07-14 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170606.1)
  MachineType: Dell Inc. OptiPlex 9010
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=5a1aae5a-efbf-41a8-bfb3-c460b0bda660 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0M9KCM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn0M9KCM:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.81-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1749688] Re: 16.04 HWE -> 18.04 = xorg held back (+ partial breakage because of it)

2018-02-16 Thread Jean-Baptiste Lallement

Confirmed by installing 16.04 daily and upgrading to 18.04.

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided => Critical

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

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

** Tags added: bionic rls-bb-incomin xenial

** Tags removed: rls-bb-incomin
** Tags added: rls-bb-incoming xenial2bionic

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

Title:
  16.04 HWE -> 18.04 = xorg held back (+ partial breakage because of it)

Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in xorg package in Ubuntu:
  New

Bug description:
  When upgrading from a 16.04 installation which had HWE (later point
  releases) xorg is getting held back as apt is having trouble resolving
  the path from xserver-xorg-core-hwe-16.04 to xserver-xorg-core.

  In at least one instance I've seen a system from a user POV completely
  break because of that as it failed to get any keyboard input. Forcing
  xorg to get properly installed fixes any and all issues as expected.

  - devel upgrade from xenial to bionic
  - restart
  - xorg not upgraded
  - try to get a hold of tty or repair mode
  - sudo apt install dist-upgrade && sudo apt install xorg
  - restart
  - working system

  I am going to attach logs for an ubuntu-desktop system, but I've also
  seen this with kubuntu-desktop and the derived neon-desktop. It's a
  bit unclear to me why apt is having trouble with the resolution, it
  does seem like a fairly serious problem though.

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

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

[Touch-packages] [Bug 1749480] Re: Totem black screen with Sparks

2018-02-16 Thread dino99

Thanks for the reply; so closing that one.

** Changed in: gstreamer1.0 (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Totem black screen with Sparks

Status in gstreamer1.0 package in Ubuntu:
  Invalid

Bug description:
  Try play a video in Ubuntu 18.04 x11, i see a black screen with sparks. Same 
video is played correctly in wayland session.
  corrado@corrado-p9-bb-1221:~$ inxi -SCGx
  System:Host: corrado-p9-bb-1221 Kernel: 4.15.0-9-generic x86_64
 bits: 64 gcc: 7.3.0
 Desktop: Gnome 3.26.2 (Gtk 3.22.26-2ubuntu1)
 Distro: Ubuntu Bionic Beaver (development branch)
  CPU:   Dual core Intel Core i3-7100 (-MT-MCP-) 
 arch: Skylake rev.9 cache: 3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
 clock speeds: max: 3900 MHz 1: 800 MHz 2: 800 MHz 3: 804 MHz
 4: 811 MHz
  Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
 Display Server: x11 (X.Org 1.19.6 ) driver: i915
 Resolution: 1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 17.3.3 Direct Render: Yes
  corrado@corrado-p9-bb-1221:~$ apt policy totem
  totem:
Installed: 3.26.0-0ubuntu3
Candidate: 3.26.0-0ubuntu3
Version table:
   *** 3.26.0-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p9-bb-1221:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.12.4-1
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 15:58:07 2018
  InstallationDate: Installed on 2017-12-23 (53 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1749480/+subscriptions

-- 
Mailing list: https://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 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

2018-02-16 Thread Jon

Ok,

If it was fixed why didn't the updates in 14.04LTS fix it. I've installed
everything offered up and including yesterday's updates.

Once again, I'm a humble *user*. A lot of this is gobbledegook to me. I
simply reported the bug when my network shares disappeared from
Thunderbird.

Can someone please explain in plain English how my 14.04LTS gets this
fix?

Thanks


On 15 Feb 2018 8:11 p.m., "Launchpad Bug Tracker" <
1714...@bugs.launchpad.net> wrote:

> This bug was fixed in the package gtk+3.0 - 3.22.28-1ubuntu1
>
> ---
> gtk+3.0 (3.22.28-1ubuntu1) bionic; urgency=medium
>
>   * Merge with Debian. Remaining changes:
> + Install a settings.ini file to set our themes
> + Enable Mir backend
> + Update debian/libgtk-3-0.symbols
> + debian/control.in:
>   - Build-depend on adwaita-icon-theme-full for icon name check test
> + debian/rules: Mark additional known test failures:
>   - box-shadow-changes-modify-clip.ui
>   - label-text-shadow-changes-modify-clip.ui
> + Ubuntu-specific patches:
>   - 073_treeview_almost_fixed.patch
>   - bzg_gtkcellrenderer_grabbing_modifier.patch
>   - ubuntu_gtk_custom_menu_items.patch
>   - print-dialog-show-options-of-remote-dnssd-printers.patch
>   - uimanager-guard-against-nested-node-updates.patch
>   - x-canonical-accel.patch
>   - message-dialog-restore-traditional-look-on-unity.patch
>   - 0001-gtk-reftest-Force-icon-theme-to-Adwaita.patch
>   - restore_filechooser_typeaheadfind.patch
>   - 0001-calendar-always-emit-day-selected-once.patch
>   - 0001-gtkwindow-set-transparent-background-color.patch
>   - ubuntu_fileselector_behaviour.patch
>   - unity-border-radius.patch
>   - unity-headerbar-maximized-mode.patch
>   - gtksocket-unscale-before-sending-configurenotify.patch
>   - no_content_hub.patch
>
> gtk+3.0 (3.22.28-1) unstable; urgency=medium
>
>   * New upstream release (LP: #1698270) (LP: #1714518)
>   * Update Vcs fields for conversion to git
>   * Add debian/gbp.conf
>   * Bump Standards-Version to 4.1.3
>   * Update Vcs fields for migration to https://salsa.debian.org/
>   * Drop git_text-view-support-emoji-chooser.patch: Applied in new release
>
>  -- Jeremy Bicha   Thu, 15 Feb 2018 10:15:34 -0500
>
> ** Changed in: gtk+3.0 (Ubuntu)
>Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1694129).
> https://bugs.launchpad.net/bugs/1714518
>
> Title:
>   GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
>   shares in file chooser
>
> Status in GTK+:
>   Fix Released
> Status in gtk+3.0 package in Ubuntu:
>   Fix Released
> Status in gtk+3.0 source package in Trusty:
>   Triaged
> Status in gtk+3.0 source package in Xenial:
>   Triaged
> Status in gtk+3.0 source package in Artful:
>   Triaged
>
> Bug description:
>   Steps to reproduce:
>   1. Install any Gtk3 application such as Firefox or Chromium which use
> modern file-chooser dialog.
>   2. Mount network location through fstab or file-manager ("smb://" =
> SMB/CIFS, "sftp://"; = SFTP/SSH and so on)
>   3. Try to save/open file to/from the remote location from Gtk3
> application.
>
>   Expected results:
>   * user is able to find network folder and save/open file to/from it with
> GtkFileChooser dialog
>
>   Actual results:
>   * user is unable to find network folder and save/open file to/from it
> with GtkFileChooser dialog and many user applications are affected
>
>   
> -
>   Original bug description is below:
>
>   GTK+3 doesn't show FUSE network shares in file chooser - it used to do
>   so in GTK+2, and the GTK+3 documentation still mentions it should do
>   it.
>
>   In the mean time, every user of every application switching to GTK+3
>   -- including Chromium, at some point between 58 and 60 -- (a change
>   which happened in 16.04 LTS!!), loses the functionality to open or
>   save directly to a network share.
>
>   I had chosen 16.04 LTS for deploying our workstations at work, and my 50
> users have been suddenly unable to do a simple operation they have to do
> dozens of times a day.
>   They now have to "buffer" these files to their local filesystem when
> saving them and before uploading them, and then copy them to the company's
> network shares.
>   They were already a little bit grumpy when it stopped working with
> Firefox, and are now really side-eyeing me when they apply updates and find
> Chromium broken.
>
>   I have reported the bug upstream and provided a patch to fix this. I
>   hope you'll be able and willing to include it to Ubuntu's GTK+3
>   package.
>
>   Thanks in advance.
>
>   Colin
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gtk/+bug/1714518/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packag

[Touch-packages] [Bug 1747619] Re: package samba-common 2:4.3.11+dfsg-0ubuntu0.16.04.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10

2018-02-16 Thread ChristianEhrhardt

Sorry Sergio, this seems like some total apt breakage on your system and I fail 
to see how to resolve :-/
I'll add a bug task for apt and subscribe juliank for his expertise.

** Also affects: apt (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/1747619

Title:
  package samba-common 2:4.3.11+dfsg-0ubuntu0.16.04.12 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 10

Status in apt package in Ubuntu:
  New
Status in samba package in Ubuntu:
  Incomplete

Bug description:
  installation of a new package impossible

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: samba-common 2:4.3.11+dfsg-0ubuntu0.16.04.12
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Feb  6 10:22:06 2018
  DuplicateSignature:
   package:samba-common:2:4.3.11+dfsg-0ubuntu0.16.04.12
   Setting up grub-pc (2.02~beta2-36ubuntu3.16) ...
   dpkg: error processing package grub-pc (--configure):
subprocess installed post-installation script returned error exit status 10
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 10
  InstallationDate: Installed on 2014-04-24 (1383 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  RelatedPackageVersions:
   nautilus 1:3.18.4.is.3.14.3-0ubuntu6
   gvfs 1.28.2-1ubuntu1~16.04.2
  SambaClientRegression: No
  SourcePackage: samba
  Title: package samba-common 2:4.3.11+dfsg-0ubuntu0.16.04.12 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1749480] Re: Totem black screen with Sparks

2018-02-16 Thread corrado venturini

problem solved by upgrading with proposed enabled, but now I have again the 
problem https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1721248
solved again removing gstreamer1.0-vaapi plugin

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

Title:
  Totem black screen with Sparks

Status in gstreamer1.0 package in Ubuntu:
  Incomplete

Bug description:
  Try play a video in Ubuntu 18.04 x11, i see a black screen with sparks. Same 
video is played correctly in wayland session.
  corrado@corrado-p9-bb-1221:~$ inxi -SCGx
  System:Host: corrado-p9-bb-1221 Kernel: 4.15.0-9-generic x86_64
 bits: 64 gcc: 7.3.0
 Desktop: Gnome 3.26.2 (Gtk 3.22.26-2ubuntu1)
 Distro: Ubuntu Bionic Beaver (development branch)
  CPU:   Dual core Intel Core i3-7100 (-MT-MCP-) 
 arch: Skylake rev.9 cache: 3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
 clock speeds: max: 3900 MHz 1: 800 MHz 2: 800 MHz 3: 804 MHz
 4: 811 MHz
  Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
 Display Server: x11 (X.Org 1.19.6 ) driver: i915
 Resolution: 1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 17.3.3 Direct Render: Yes
  corrado@corrado-p9-bb-1221:~$ apt policy totem
  totem:
Installed: 3.26.0-0ubuntu3
Candidate: 3.26.0-0ubuntu3
Version table:
   *** 3.26.0-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p9-bb-1221:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.12.4-1
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 15:58:07 2018
  InstallationDate: Installed on 2017-12-23 (53 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1749480/+subscriptions

-- 
Mailing list: https://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 1734104] Re: 'upgrade' in bionic should by default autoremove as well

2018-02-16 Thread Mark Shuttleworth

Perhaps we are talking at cross purposes. My expectation is that update
would list the packages to be removed because they are no longer
dependencies of packages that were consciously installed. On that basis,
there should be no surprise to users. The messaging could point users to
a handy document to understand how they can make a package stick around
by flagging it as one they have manually / consciously installed.

My point is that most users don't install
'linux-image-extra-4.13.0-15-generic' themselves, they have a system
with 'linux-image-generic' installed, and it's dependencies change over
time.

AIUI, we already have a good way of holding back from autoremoval
versions of the kernel which are currently in use, or which are the
last-best-guess-good kernel, or which are the next-kernel-to-boot. All
other kernels that were not explicitly installed by the user are simply
ephemeral to that user, and for the vast majority of users, those
ephemeral kernels build up over time taking large amounts of space and
slowing down upgrades thanks to the initramfs generation mechanisms.
Those kernels should go when they are deemed surplus; the user did not
ask for them explicitly, and the user isn't going to boot them either.

Here's what I have in mind, note the changes to text in the output of
apt upgrade. The user is prompted, and told how to avoid autoremoval.

$ sudo apt upgrade
Reading package lists... Done
Building dependency tree  
Reading state information... Done
Calculating upgrade... Done

These packages were automatically installed and are no longer needed:
  libgweather-3-6, linux-image-extra-4.13.0-15-generic
Cancel this operation and use 'sudo apt install ' to keep them
from automatic removal.

The following packages have been kept back:
  libreoffice-help-en-us

The following packages will be upgraded:
  libio-socket-ssl-perl

1 upgraded, 0 newly installed, 2 to remove and 1 not upgraded.

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

Title:
  'upgrade' in bionic should by default autoremove as well

Status in apt package in Ubuntu:
  Triaged

Bug description:
  In bionic, apt upgrade should also autoremove by default. I have a few
  bionic systems (upgrades from xenial mostly) which are not yet showing
  that behaviour, it may be we haven't implemented that yet so this is
  just a placeholder bug in that case :)

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

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

[Touch-packages] [Bug 1725861] Re: APT::AutoRemove::SuggestsImportant "false" should be the default

Reopening as incomplete for the further discussion, if needed.

** Changed in: apt (Ubuntu Bionic)
   Status: Opinion => 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/1725861

Title:
  APT::AutoRemove::SuggestsImportant "false" should be the default

Status in apt package in Ubuntu:
  Incomplete
Status in apt source package in Bionic:
  Incomplete

Bug description:
  After an upgrade to 17.10, I took a look at how much cruft I had
  accumulated on my system, and started marking various packages 'auto'
  which I know I don't care about keeping installed.

  apt autoremove didn't remove nearly as much stuff as I expected, and
  as I dug down into some of them I found that a number of them were
  being kept because other packages on the system have Suggests:
  referencing them.

  This is asymmetric and wrong.  If Suggested packages are not
  automatically installed by default, then a Suggests should also not
  prevent a package from being automatically removed.

  After a web search led me to 'https://askubuntu.com/questions/351085
  /how-to-remove-recommended-and-suggested-dependencies-of-uninstalled-
  packages', I set 'APT::AutoRemove::SuggestsImportant "false"' in my
  apt config; apt autoremove now wants to remove 365MiB of packages from
  my system.  That is a LOT of cruft that has accumulated over the years
  of upgrades, none of which I have ever asked to be installed and all
  of which were universe or no-longer-available packages.

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

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

[Touch-packages] [Bug 1749086] Re: 5 minute delay on booting to login screen

2018-02-16 Thread Steve Bainton

Until further notice, all works fine.

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

Title:
  5 minute delay on booting to login screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  With Xubuntu or Kubuntu the screen turns off a few seconds after
  choosing Ubuntu in grub2 menu, and sometimes the login screen takes 5
  minutes to be presented. From that point on everything seems to work
  as normal.

  Booting consistently took only a minute in Kubuntu 14.04.

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1725861] Re: APT::AutoRemove::SuggestsImportant "false" should be the default

@vorlon

> After an upgrade to 17.10, I took a look at how much cruft I had accumulated 
> on my system, and
> started marking various packages 'auto' which I know I don't care about 
> keeping installed.
>
> apt autoremove didn't remove nearly as much stuff as I expected, and as I dug 
> down into some of
> them I found that a number of them were being kept because other packages on 
> the system have
>Suggests: referencing them.
>
> This is asymmetric and wrong. If Suggested packages are not automatically 
> installed by default,
> then a Suggests should also not prevent a package from being automatically 
> removed.

IMO this is asymmetric and right because the cost of keeping the
packages on the system is much lower than the expected benefits they
provide for the user. Why else would be suggested?

> After a web search led me to 
> 'https://askubuntu.com/questions/351085/how-to-remove-recommended-and-suggested-dependencies-of-uninstalled-packages',
>  I set 'APT::AutoRemove::SuggestsImportant "false"' in my apt config; apt 
> autoremove now wants
> to remove 365MiB of packages from my system. That is a LOT of cruft that has 
> accumulated over
> the years of upgrades, none of which I have ever asked to be installed and 
> all of which were
> universe or no-longer-available packages.

IMO 365MiB over _years_ is not a lot at all the age of streaming 4K videos 
every day. Did you experience any improvement in the system's performance after 
removing the packages?
I just checked the size of apt's package list cache on an Artful system as a 
comparison:

 ~$ du -sh /var/lib/apt/lists
 367M   /var/lib/apt/lists

IMO saving a tiny amount of space and surprising people by removing more
packages than before would hardly make the Ubuntu experience better.

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

Title:
  APT::AutoRemove::SuggestsImportant "false" should be the default

Status in apt package in Ubuntu:
  Opinion
Status in apt source package in Bionic:
  Opinion

Bug description:
  After an upgrade to 17.10, I took a look at how much cruft I had
  accumulated on my system, and started marking various packages 'auto'
  which I know I don't care about keeping installed.

  apt autoremove didn't remove nearly as much stuff as I expected, and
  as I dug down into some of them I found that a number of them were
  being kept because other packages on the system have Suggests:
  referencing them.

  This is asymmetric and wrong.  If Suggested packages are not
  automatically installed by default, then a Suggests should also not
  prevent a package from being automatically removed.

  After a web search led me to 'https://askubuntu.com/questions/351085
  /how-to-remove-recommended-and-suggested-dependencies-of-uninstalled-
  packages', I set 'APT::AutoRemove::SuggestsImportant "false"' in my
  apt config; apt autoremove now wants to remove 365MiB of packages from
  my system.  That is a LOT of cruft that has accumulated over the years
  of upgrades, none of which I have ever asked to be installed and all
  of which were universe or no-longer-available packages.

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

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

[Touch-packages] [Bug 1725861] Re: APT::AutoRemove::SuggestsImportant "false" should be the default