[Touch-packages] [Bug 1721795] Re: Move Recommends: gnome-getting-started-docs from ubuntu-docs to ubuntu-desktop

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-docs - 17.10.7

---
ubuntu-docs (17.10.7) artful; urgency=medium

  * debian/control.in, debian/control:
- Don't recommend gnome-getting-started-docs - ubuntu-desktop
  recommends it instead (LP: #1721795).
  * The latest translations exported from Launchpad.
  * ubuntu-help/sl/sl.po: Mallard syntax error fixed.

 -- Gunnar Hjalmarsson   Wed, 11 Oct 2017 00:05:00
+0200

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

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

Title:
  Move Recommends: gnome-getting-started-docs from ubuntu-docs to
  ubuntu-desktop

Status in ubuntu-docs package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Budgie includes ubuntu-docs since it's generally useful and
  they don't have another docs system.

  But Ubuntu Budgie does not need gnome-getting-started-docs

  https://help.gnome.org/users/gnome-help/stable/getting-started.html

  We can fix this issue by having ubuntu-desktop recommend gnome-
  getting-started-docs and dropping that recommends from ubuntu-docs.

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

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

[Touch-packages] [Bug 1722708] [NEW] Crash when setting laptop display resolution

[Ville Skyttä]

Public bug reported:

This system has a 4k laptop screen with resolution 3840x2160, and an
external HP monitor connected via HDMI, resolution 1920x1200. Windows,
fonts etc are not scaled properly on the external monitor (too large,
etc), and the only workaround I've found with earlier versions and other
distros is to set the laptop display to 1920x1080 mode, so that's what
I'm trying here as well.

However, when doing that, the X (wayland, not sure if the package is
correct here) session crashes and brings me back to login screen.

So to summarize: connect the external monitor, go to Settings > Devices
> Displays, click primary built in display, observe that it shows
Resolution 3840x2160 (16:9) and Scale 200%, change resolution to
1920x1080 (16:9), click Apply --> crash.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
BootLog:
 
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 07:49:08 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
EcryptfsInUse: Yes
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 620 [17aa:2248]
   Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:2248]
InstallationDate: Installed on 2017-10-10 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171008)
MachineType: LENOVO 20H9004MMX
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=182b5236-fa96-4fb5-bea9-f90769b65f3c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/06/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1VET35W (1.25 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20H9004MMX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1VET35W(1.25):bd09/06/2017:svnLENOVO:pn20H9004MMX:pvrThinkPadT570:rvnLENOVO:rn20H9004MMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T570
dmi.product.name: 20H9004MMX
dmi.product.version: ThinkPad T570
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7
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

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


** Tags: amd64 apport-bug artful crash ubuntu wayland-session

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

Title:
  Crash when setting laptop display resolution

Status in xorg package in Ubuntu:
  New

Bug description:
  This system has a 4k laptop screen with resolution 3840x2160, and an
  external HP monitor connected via HDMI, resolution 1920x1200. Windows,
  fonts etc are not scaled properly on the external monitor (too large,
  etc), and the only workaround I've found with earlier versions and
  other distros is to set the laptop display to 1920x1080 mode, so
  that's what I'm trying here as well.

  However, when doing that, the X (wayland, not sure if the package is
  correct here) session crashes and brings me back to login screen.

  So to summarize: connect the external monitor, go to Settings >
  Devices > Displays, click primary built in display, observe that it
  shows Resolution 3840x2160 (16:9) and Scale 200%, change resolution to
  1920x1080 (16:9), click Apply --> crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 07:49:08 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:2248]
 Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:2248]
  InstallationDate: Installed on 2017-10-10 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171008)
  MachineType: LENOVO 20H9004MMX
  

[Touch-packages] [Bug 861642] Re: upowerd uses 100% cpu till killed

[ls]

** Also affects: upower
   Importance: Undecided
   Status: New

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

Title:
  upowerd uses 100% cpu till killed

Status in Upower:
  New
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  top - 12:57:54 up  2:56,  3 users,  load average: 1.06, 1.12, 1.35
  Tasks: 219 total,   2 running, 216 sleeping,   0 stopped,   1 zombie
  Cpu0  : 70.2%us, 29.8%sy,  0.0%ni,  0.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu1  :  2.3%us,  1.3%sy,  0.0%ni, 96.4%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu2  :  1.0%us,  0.3%sy,  0.0%ni, 98.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu3  :  0.7%us,  1.6%sy,  0.0%ni, 97.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu4  :  0.0%us,  0.3%sy,  0.0%ni, 99.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu5  :  0.0%us,  0.3%sy,  0.0%ni, 98.3%id,  1.4%wa,  0.0%hi,  0.0%si,  0.0%st
  Mem:   5994176k total,  4198260k used,  1795916k free,63308k buffers
  Swap:  8193144k total,   355188k used,  7837956k free,   334316k cached

PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND  
  
   2268 root  20   0  148m 1572  680 R  100  0.0 111:08.37 upowerd

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: upower 0.9.9-4
  ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Wed Sep 28 12:53:23 2011
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  ProcEnviron:
   
  SourcePackage: upower
  UpgradeStatus: Upgraded to natty on 2011-04-06 (175 days ago)

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

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

[Touch-packages] [Bug 1721839] Re: Services asked for by UDEV do not get triggered

[Till Kamppeter]

It seems that with a 70-printers.rules as follows at least a correct
service name is generated

--
# Low-level USB device add trigger
ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", 
ENV{ID_USB_INTERFACES}=="*:0701??:*", TAG+="udev-configure-printer", 
TAG+="systemd", PROGRAM="/bin/systemd-escape 
--template=udev-configure-printer@.service %p", ENV{SYSTEMD_WANTS}+="'%c'"
# Low-level USB device remove trigger
ACTION=="remove", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", 
ENV{ID_USB_INTERFACES}=="*:0701*:*", RUN+="udev-configure-printer remove %p"
--

Note that in the first rule the systemd-escape command has NO "-p"
option and that the %c for ENV{SYSTEMD_WANTS} has extra single quotes.
Compared to the original file only these single quotes got added.

After restarting UDEV with

sudo udevadm control --reload

and re-plugging the printer in most cases the service does not get
started.

systemctl status 'udev-configure-printer@-devices-
pci:00-:00:14.0-usb2-2\x2d2.service' > status.txt

gives something like

--
● udev-configure-printer@devices-pci:00-:00:14.0-usb2-2\x2d2.service - 
Automatic USB/Bluetooth printer setup 
(devices-pci:00-:00:14.0-usb2-2\x2d2)
   Loaded: loaded (/lib/systemd/system/udev-configure-printer@.service; static; 
vendor preset: enabled)
   Active: inactive (dead)
--

In such a case one can start the service manually with

sudo systemctl start 'udev-configure-printer@-devices-
pci:00-:00:14.0-usb2-2\x2d2.service'

and this starts correctly udev-configure printer which sets up the
printer (and starts ippusbxd if needed).

In some very few cases the service actually gets correctly started (and
the printer set up) when one plugs the printer, but this happens rarely
(can there be some kind of race condition?).

So this only rarely happening automatic start of the printer setup
service is now the problem. The escaping seems to be fixed by the extra
single quotes.

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

Title:
  Services asked for by UDEV do not get triggered

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The packages system-config-printer-udev and ippusbxd are installed,
  having the following UDEV rule files:

  /lib/udev/rules.d/70-printers.rules

  --
  # Low-level USB device add trigger
  ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", 
ENV{ID_USB_INTERFACES}=="*:0701??:*", TAG+="udev-configure-printer", 
TAG+="systemd", PROGRAM="/bin/systemd-escape 
--template=udev-configure-printer@.service %p", ENV{SYSTEMD_WANTS}+="%c"
  # Low-level USB device remove trigger
  ACTION=="remove", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", 
ENV{ID_USB_INTERFACES}=="*:0701*:*", RUN+="udev-configure-printer remove %p"
  --

  /lib/udev/rules.d/55-ippusbxd.rules

  --
  # ippusbxd udev rules file

  ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device" 
ENV{ID_USB_INTERFACES}=="*:070104:*", OWNER="root", GROUP="lp", MODE="0664", 
PROGRAM="/bin/systemd-escape --template=ippusbxd@.service 
$env{BUSNUM}:$env{DEVNUM}", ENV{SYSTEMD_WANTS}+="%c"
  --

  If I turn on an appropriate printer (USB, supporting IPP-over-USB,
  here the HP DeskJet 2540) I get in the output of "udevadm monitor
  --environment"

  --
  UDEV  [17527.514150] add  /devices/pci:00/:00:14.0/usb2/2-2 (usb)
  ACTION=add
  BUSNUM=002
  DEVNAME=/dev/bus/usb/002/033
  DEVNUM=033
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2
  DEVTYPE=usb_device
  DRIVER=usb
  ID_BUS=usb
  ID_MODEL=Deskjet_2540_series
  ID_MODEL_ENC=Deskjet\x202540\x20series
  ID_MODEL_ID=c211
  ID_REVISION=0100
  ID_SERIAL=HP_Deskjet_2540_series_BR54BFB02C05XK
  ID_SERIAL_SHORT=BR54BFB02C05XK
  ID_USB_INTERFACES=:ffcc00:070104:070102:ff0401:
  ID_VENDOR=HP
  ID_VENDOR_ENC=HP
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  ID_VENDOR_ID=03f0
  MAJOR=189
  MINOR=160
  PRODUCT=3f0/c211/100
  SEQNUM=9891
  SUBSYSTEM=usb
  SYSTEMD_WANTS=ippusbxd@002:033.service 
udev-configure-printer@-devices-pci:00-:00:14.0-usb2-2\x2d2.service 
printer.target
  TAGS=:udev-configure-printer:systemd:
  TYPE=0/0/0
  USEC_INITIALIZED=17527513940

  UDEV  [17527.517724] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb)
  .MM_USBIFNUM=00
  ACTION=add
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0
  DEVTYPE=usb_interface
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  INTERFACE=255/204/0
  MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00icFFiscCCip00in00
  PRODUCT=3f0/c211/100
  SEQNUM=9892
  SUBSYSTEM=usb
  TYPE=0/0/0
  USEC_INITIALIZED=17527517478

  UDEV  [17527.522565] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.2 (usb)
  .MM_USBIFNUM=02
  ACTION=add
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.2
  DEVTYPE=usb_interface
  

[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2

[forteller]

I seem to have almost exactly the same bug, and it's been bothering me
off and on for many months now. The step to reproduce in the latest
comment here from @anders works for me. (I only checked 'sudo setupcon
--force')

The only differences that I have is that

1) Alt + F2 doesn't send me to a terminal, but to the GUI (and if I'm
already in the GUI then it opens the run dialog as you'd expect) and

2) Ctrl + Alt + F-buttons still work during this bug for me.

This is the kind of bug that makes me think twice before recommending
Linux to non-technical people (which to me is the most important people
to recruit), so I'm really hoping it will get fixed soon. Thank you all
very much for your work!

Let me know if I can be of any help with any logs or the like.

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Confirmed
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

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

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

[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2

[forteller]

Sorry, I forgot to mention that I'm on Ubuntu Gnome 17.04 64 bit, and
also had the issue on 16.10.

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Confirmed
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

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

-- 
Mailing list: https://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 1714803] Re: Search list in resolv.conf breaks resolving for that domain

[Dimitri John Ledkov]

On 10 October 2017 at 15:39, Matthias Fratz <1714...@bugs.launchpad.net> wrote:
> Our DHCP server delivers a search domain (inf.uni-konstanz.de) as well.
> This isn't enough to trigger the bug for me, though, at least on 17.04.
> (systemd-resolve doesn't actually USE the search path, so merkur236.inf
> .uni-konstanz.de works but merkur236 doesn't, but that's a different
> problem.)
>
> What does trigger the bug on 17.04 is manually configuring a search
> path, like it seems the original reporter did:
>
> $ cat /etc/resolvconf/resolv.conf.d/base
> search disy.inf.uni-konstanz.de inf.uni-konstanz.de uni-konstanz.de
>
> At some point this gets copied to /etc/resolv.conf. After a "service
> systemd-resolved restart", resolution is broken for those domains until
> I remove the search path and restart systemd-resolved again.
>
> I couldn't yet reproduce this on 17.10 because restarting systemd-
> resolved overwrites /etc/resolv.conf. Where is the right place to
> configure a search path on 17.10? I don't see it anywhere in the GUI and
> I'm not sure whether /etc/systemd/resolved.conf is the right place.
>

The really correct way on 17.10 is to stop using ifupdown and stop
using resolvconf and stop using libnss-resolve

$ upgrade to 17.10
$ sudo netplan ifupdown-migrate
$ sudo apt remove --purge ifupdown
$ sudo apt remove --purge resolvconf
$ sudo apt remove --purge libnss-resolve
$ sudo reboot

At this point, /etc/resolv.conf will start pointing at a resolved
managed stub-resolv.conf file which will automatically pick up and use
DHCP provided domains.
Further domains configuration can be provided by adjusting
/etc/netplan/*.yaml file, or by adjusting systemd-networkd drop-ins,
or by adjusting /etc/systemd/resolved.conf.
It's best for the search domains to be provided over DHCP instead of
hardcoding the config in files on disk.

You may also choose to use networks: backend: network-manager in the
netplan.yaml file, if you wish to use NetworkManager instead of the
networkd as the networking management backend.

Search domains specified in resolvconf syntax / directly in the
/etc/resolv.conf will not be read/used by resolved stub resolver, and
will not be used by libnss-resolve, thus if you wish to keep using
resolvconf/ifupdown one will need to provide the search domain to
resolved separately. Best way to do that would be via
/etc/systemd/resolved.conf.

-- 
Regards,

Dimitri.

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

Title:
  Search list in resolv.conf breaks resolving for that domain

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.04
  systemd 232-21ubuntu5

  Adding a domain to the search list in /etc/resolv.conf breaks
  resolving for that domain. Not only does the search list not get used
  as expected, but host names in the domain cannot be resolved by
  systemd-resolved at all.

  I just ran into this after upgrading from ubuntu 16.04 to 17.04 which
  enabled systemd-resolved. I have for a long time used resolveconf to
  add a 'search my-domain'-line to my /etc/resolv.conf.

  
  Example of expected behaviour. With Googles DNS server (8.8.8.8) and 
ubuntu.com in the search list in /etc/resolv.conf. Both dig and systemd-resolve 
can resolve www.ubuntu.com and www:

  $ cat /etc/resolv.conf 
  nameserver 8.8.8.8
  search ubuntu.com
  $ dig +nostat +nocmd www.ubuntu.com
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55037
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 512
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  ;; ANSWER SECTION:
  www.ubuntu.com.   501 IN  A   91.189.89.115
  
  $ dig +search +nostat +nocmd www
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25772
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 512
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  ;; ANSWER SECTION:
  www.ubuntu.com.   382 IN  A   91.189.89.103
  
  $ systemd-resolve www.ubuntu.com
  www.ubuntu.com: 91.189.89.115
  
  -- Information acquired via protocol DNS in 2.7ms.
  -- Data is authenticated: no
  $ systemd-resolve www
  www: 91.189.90.59
   (www.ubuntu.com)
  
  -- Information acquired via protocol DNS in 3.8ms.
  -- Data is authenticated: no

  Ubuntu 17.04 default config, with the systemd-resolved name server in
  /etc/resolv.conf and no search list. www.ubuntu.com can still be
  resolved correctly:

  $ cat /etc/resolv.conf
  nameserver 127.0.0.53
  $ dig +nostat 

[Touch-packages] [Bug 1712433] Re: man page typo

[Dimitri John Ledkov]

** Changed in: util-linux (Ubuntu)
   Status: Fix Committed => Triaged

** Changed in: util-linux (Ubuntu)
 Assignee: Liam Ryan (lrdev) => (unassigned)

** Changed in: util-linux (Ubuntu)
   Importance: Low => Wishlist

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

Title:
  man page typo

Status in util-linux package in Ubuntu:
  Triaged

Bug description:
  man mount contains the following section:

  Note  that mount is very strict about non-root users and all paths specified 
on command line are verified before fstab is
     parsed or a helper program is executed. It's strogly recommended to 
use a valid mountpoint to specify filesystem,  other‐
     wise mount may fail. For example it's bad idea to use NFS or CIFS 
source on command line.

  The word 'strogly' should be 'strongly'

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: mount 2.29-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Wed Aug 23 07:48:32 2017
  InstallationDate: Installed on 2017-03-23 (152 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to zesty on 2017-08-13 (9 days ago)

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

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

[Touch-packages] [Bug 1619258] Re: netplan should allow NICs to be disconnected and not stall the boot

[Steve Langasek]

The netplan piece of this is being driven via LP: #1664844.

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

Title:
  netplan should allow NICs to be disconnected and not stall the boot

Status in Snappy:
  Confirmed
Status in nplan package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  in older snappy image we used to set "allow-hotplug" in
  /etc/network/interfaces.d/ when configuring a NIC to avoid the boot to
  completely stall or to be stuck for 5min when trying to find an
  internet connection.

  with recent versions of netplan the configuration seems to be back to
  require a network to be up before moving on with them boot so that
  booting takes forever until the network connection times out.

  netplan should make the system check the physical link status when
  trying to bring up a network device instead of stalling the boot.

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

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

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

[Mark]

I am still having this issue on Lubuntu 16.04.3, could it be possibly
related to another bug I opened: #1719731?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719731

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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

[Touch-packages] [Bug 1722313] Re: [SRU][xenial] Enable auditing in util-linux.

[Joy Latten]

** Description changed:

  [IMPACT]
- There is a requirement for Common Criteria EAL2 certification that changes to 
the system's hardware clock be audited/monitored. In Ubuntu the hwclock command 
can be used to alter the system's hardware clock. Thus this event needs to be 
audited for EAL2. The hwclock command within util-linux has the ability to 
create an audit event when the system's hardware clock is altered, but this 
ability is enabled via the --with-audit config option. This option is currently 
not enabled.
+ Enable auditing in util-linux. The config option, --with-audit enables 
auditing.
+  
+ Only the hwclock and the login commands within util-linux package have source 
code for auditing. But that source code is disabled by default and requires the 
config option, --with-audit to enable it. The login command is not built nor 
shipped in util-linux. Ubuntu uses the login command from shadow instead. Thus, 
only hwclock command would be affected by this change.
  
- Only the hwclock and the login commands within util-linux package use
- this --with-audit config option to enable auditing. However, it appears
- the login command is not built nor shipped in util-linux. Ubuntu uses
- the login command from shadow instead. Thus, only hwclock command would
- be affected by this change. The change would enable (1) call to
- audit_open to create a netlink socket descritor. (2) generate an audit
- entry when system hardware clock altered. The entry will be logged into
- the /var/log/audit/audit.log IF auditd is installed and running.
+ The change would enable the hwclock command to generate an audit log
+ message to /var/log/audit/audit.log whenever it changes the hardware
+ clock. This message will only get logged if auditd daemon is running.
+ Otherwise, nothing gets logged.
+ 
+ That the hwclock generates an audit message when hardware clock is
+ changed is a requirement for Common Criteria EAL2 certification for
+ Xenial.
  
  [TEST]
  
  This has been tested on both P8 and amd64 architectures. With the patch
  all the Common Criteria testcases pass for hwclock. Before this patch,
  the functional part of the testcase passed, but the check for the
  triggered audit records would fail. Attached the Common Criteria
  testcase below.
  
  Also, the util-linux package has testcases that get run during the
  build. All of these pass. Pointer to build log below.
  
  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

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

Title:
  [SRU][xenial] Enable auditing in util-linux.

Status in util-linux package in Ubuntu:
  New
Status in util-linux source package in Xenial:
  New
Status in util-linux source package in Zesty:
  New
Status in util-linux source package in Artful:
  New
Status in util-linux package in Debian:
  Unknown

Bug description:
  [IMPACT]
  Enable auditing in util-linux. The config option, --with-audit enables 
auditing.
   
  Only the hwclock and the login commands within util-linux package have source 
code for auditing. But that source code is disabled by default and requires the 
config option, --with-audit to enable it. The login command is not built nor 
shipped in util-linux. Ubuntu uses the login command from shadow instead. Thus, 
only hwclock command would be affected by this change.

  The change would enable the hwclock command to generate an audit log
  message to /var/log/audit/audit.log whenever it changes the hardware
  clock. This message will only get logged if auditd daemon is running.
  Otherwise, nothing gets logged.

  That the hwclock generates an audit message when hardware clock is
  changed is a requirement for Common Criteria EAL2 certification for
  Xenial.

  [TEST]

  This has been tested on both P8 and amd64 architectures. With the
  patch all the Common Criteria testcases pass for hwclock. Before this
  patch, the functional part of the testcase passed, but the check for
  the triggered audit records would fail. Attached the Common Criteria
  testcase below.

  Also, the util-linux package has testcases that get run during the
  build. All of these pass. Pointer to build log below.

  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

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

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

[Touch-packages] [Bug 1722649] [NEW] package linux-image-4.10.0-37-generic 4.10.0-37.41 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Normando Sobral Pereira Cardoso]

Public bug reported:

dpkg: erro ao processar o pacote linux-image-4.10.0-37-generic (--configure):
 sub-processo script post-installation instalado retornou estado de saída de 
erro 2
Configurando libreoffice-calc (1:5.4.2~rc2-0ubuntu0.17.04.1~lo1) ...
A processar 'triggers' para man-db (2.7.6.1-2) ...
dpkg: problemas com dependências impedem a configuração de linux-image-generic:
 linux-image-generic depende de linux-image-4.10.0-37-generic; porém:
  Pacote linux-image-4.10.0-37-generic não está configurado ainda.

dpkg: erro ao processar o pacote linux-image-generic (--configure):
 problemas de dependência - deixando desconfigurado
Nenhum relatório apport escrito pois a mensagem de erro indica que é um erro de 
seguimento de um erro anterior.
   dpkg: problemas com dependências impedem a 
configuração de linux-image-extra-4.10.0-37-generic:
 linux-image-extra-4.10.0-37-generic depende de linux-image-4.10.0-37-generic; 
porém:
  Pacote linux-image-4.10.0-37-generic não está configurado ainda.

dpkg: erro ao processar o pacote linux-image-extra-4.10.0-37-generic 
(--configure):
 problemas de dependência - deixando desconfigurado
Configurando libreoffice-impress (1:5.4.2~rc2-0ubuntu0.17.04.1~lo1) ...
Nenhum relatório apport escrito pois a mensagem de erro indica que é um erro de 
seguimento de um erro anterior.
   dpkg: problemas com dependências impedem a 
configuração de linux-generic:
 linux-generic depende de linux-image-generic (= 4.10.0.37.37); porém:
  Pacote linux-image-generic não está configurado ainda.

dpkg: erro ao processar o pacote linux-generic (--configure):
 problemas de dependência - deixando desconfigurado
Nenhum relatório apport escrito pois MaxReports já foi atingido
   Erros foram 
encontrados durante o processamento de:
 linux-image-4.10.0-37-generic
 linux-image-generic
 linux-image-extra-4.10.0-37-generic
 linux-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@normando-System-Product-Name:/home/normando#

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-37-generic 4.10.0-37.41
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.10.0-35-generic.
ApportVersion: 2.20.4-0ubuntu4.5
AptOrdering:
 libreoffice-calc:amd64: Install
 libreoffice-draw:amd64: Install
 libreoffice-impress:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  normando   1096 F pulseaudio
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfe9f4000 irq 16'
   Mixer name   : 'Realtek ALC887-VD'
   Components   : 'HDA:10ec0887,10438445,00100302'
   Controls  : 46
   Simple ctrls  : 22
Date: Tue Oct 10 17:33:41 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=01429459-4dbd-4e50-8cdb-adadf87e4597
InstallationDate: Installed on 2017-10-01 (9 days ago)
InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
IwConfig:
 lono wireless extensions.
 
 enp2s0no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=11fe4144-bf27-49ba-999a-6feaac01cfa9 ro locale=pt_BR quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2
RfKill:
 
SourcePackage: initramfs-tools
Title: package linux-image-4.10.0-37-generic 4.10.0-37.41 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/19/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1101
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M5A78L-M LX/BR
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1101:bd04/19/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-package zesty

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

Title:
  package 

[Touch-packages] [Bug 1722313] Re: [SRU][xenial] Enable auditing in util-linux.

[Joy Latten]

** Summary changed:

- [SRU][xenial] Add "--with-audit" config option so that the hwclock command 
creates an audit record when the hardware clock is altered.
+ [SRU][xenial] Enable auditing in util-linux.

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

Title:
  [SRU][xenial] Enable auditing in util-linux.

Status in util-linux package in Ubuntu:
  New
Status in util-linux source package in Xenial:
  New
Status in util-linux source package in Zesty:
  New
Status in util-linux source package in Artful:
  New
Status in util-linux package in Debian:
  Unknown

Bug description:
  [IMPACT]
  There is a requirement for Common Criteria EAL2 certification that changes to 
the system's hardware clock be audited/monitored. In Ubuntu the hwclock command 
can be used to alter the system's hardware clock. Thus this event needs to be 
audited for EAL2. The hwclock command within util-linux has the ability to 
create an audit event when the system's hardware clock is altered, but this 
ability is enabled via the --with-audit config option. This option is currently 
not enabled.

  Only the hwclock and the login commands within util-linux package use
  this --with-audit config option to enable auditing. However, it
  appears the login command is not built nor shipped in util-linux.
  Ubuntu uses the login command from shadow instead. Thus, only hwclock
  command would be affected by this change. The change would enable (1)
  call to audit_open to create a netlink socket descritor. (2) generate
  an audit entry when system hardware clock altered. The entry will be
  logged into the /var/log/audit/audit.log IF auditd is installed and
  running.

  [TEST]

  This has been tested on both P8 and amd64 architectures. With the
  patch all the Common Criteria testcases pass for hwclock. Before this
  patch, the functional part of the testcase passed, but the check for
  the triggered audit records would fail. Attached the Common Criteria
  testcase below.

  Also, the util-linux package has testcases that get run during the
  build. All of these pass. Pointer to build log below.

  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

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

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

[Touch-packages] [Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full

[Jarno Suni]

For some reason with my patch mv may fail even if I try to make sure mv
will not be run, if there is not enough space on /boot:

Setting up linux-generic-lts-xenial (4.4.0.97.81) ...
Processing triggers for initramfs-tools (0.103ubuntu4.8) ...
update-initramfs: Generating /boot/initrd.img-4.4.0-97-generic
W: TMPDIR is mounted noexec, will not cache run scripts.
mv: error writing '/boot/initrd.img-4.4.0-97-generic': No space left on device
mv: failed to extend '/boot/initrd.img-4.4.0-97-generic': No space left on 
device
update-initramfs: failed for /boot/initrd.img-4.4.0-97-generic with mv 
returning 1.
Backup file /boot/initrd.img-4.4.0-97-generic.dpkg-bak remains.
dpkg: error processing package initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  Removing a linux-image-extra package fails, if /boot is about full

Status in initramfs-tools:
  New
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  System calls /etc/kernel/postinst.d/initramfs-tools when
  purging/removing a linux-image-extra package. That calls "update-
  initramfs -c" which needs significant amount of additional disk space
  in /boot temporarily. But there is no space left, if /boot is full.

  Likewise /etc/kernel/postinst.d/dkms may call "update-initramfs -u".

  The fix could be to create the new initrg.img file in different partition 
before replacing the old one by it in update-initramfs. So the update-initramfs 
script should be fixed. But there may not be such a partition..
  Anyway the likely case when space runs out is when there is a separate /boot 
partition.

  Alternatively the init scripts should remove the respective 
/boot/initrd.img- file when removing/installing the linux-image-extra 
package. That could also be done by
  update-initramfs -d -k 
  That may be worse way, as then initrd.img file is missing for longer period 
of time and system integrity may suffer in case of e.g. power cut.

  Related question: http://askubuntu.com/q/898499/21005
  The output of 'dpkg --purge' presented there shows that corresponding 
linux-image package may get successfully removed while the linux-image-extra is 
left broken. If the linux-image-extra package will be removed later, the 
post-installation script will create an initrd.img file for a non-installed 
kernel! Same would happen, if removing would be done by apt-get purge.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.7
  ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 17:42:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (922 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1722641] [NEW] Bad Resolution

[ARmingga]

Public bug reported:

theres no right or fit resolution in my linux

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
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
CurrentDesktop: Unity
Date: Wed Oct 11 02:50:25 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.4.0-31-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.4.0-96-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics 
Controller (primary) [1025:0136]
   Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics 
Controller (secondary) [1025:0136]
InstallationDate: Installed on 2017-10-04 (6 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Acer Aspire 5315
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic 
root=UUID=5eb303ac-1277-4276-be36-4749a701b8f1 ro 
resume=UUID=471936fc-2e69-45b4-9b1f-b8cc72c7671c quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/10/2008
dmi.bios.vendor: Acer
dmi.bios.version: V1.45
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Acadia
dmi.board.vendor: Acer
dmi.board.version: V1.45
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.45
dmi.modalias: 
dmi:bvnAcer:bvrV1.45:bd11/10/2008:svnAcer:pnAspire5315:pvrV1.45:rvnAcer:rnAcadia:rvrV1.45:cvnAcer:ct1:cvrV1.45:
dmi.product.name: Aspire 5315
dmi.product.version: V1.45
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Oct 11 08:58:31 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.4

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


** Tags: amd64 apport-bug compiz-0.9 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/1722641

Title:
  Bad Resolution

Status in xorg package in Ubuntu:
  New

Bug description:
  theres no right or fit resolution in my linux

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  CurrentDesktop: Unity
  Date: Wed Oct 11 02:50:25 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.4.0-31-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-96-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics 
Controller (primary) [1025:0136]
 Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics 
Controller (secondary) [1025:0136]
  InstallationDate: Installed on 2017-10-04 (6 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Acer Aspire 5315
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic 
root=UUID=5eb303ac-1277-4276-be36-4749a701b8f1 ro 
resume=UUID=471936fc-2e69-45b4-9b1f-b8cc72c7671c 

[Touch-packages] [Bug 1722292] Re: [FFe] Mir 1.0 release

[Iain Lane]

I guess this should be low risk for users, since they aren't likely to
be using mir without knowing about it. I don't have a particular problem
with the upload.

You'll need to find an archive admin (member of ~ubuntu-archive) to
publish this silo for you, since it introduces new packages & needs a
review for that. That person can also process the removal bugs you need:

  https://bugs.launchpad.net/ubuntu/+source/unity-system-
compositor/+bug/1718023

  https://bugs.launchpad.net/ubuntu/+source/miral/+bug/1722628

** Package changed: ubuntu => mir (Ubuntu)

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

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

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

Title:
  [FFe] Mir 1.0 release

Status in mir package in Ubuntu:
  Confirmed

Bug description:
   * New upstream release 1.0.0(https://launchpad.net/mir/+milestone/1.0.0)
 - ABI summary:
   . mirclient ABI unchanged at 9
   . miral ABI introduced at 2
   . mirserver ABI bumped to 45
   . mircommon ABI unchanged at 7
   . mirplatform ABI unchanged at 61
   . mirprotobuf ABI unchanged at 3
   . mirplatformgraphics ABI unchanged at 13
   . mirclientplatform ABI unchanged at 5
   . mirinputplatform ABI unchanged at 7
   . mircore ABI unchanged at 1
 - Enhancements:
   . Update licences to (L)GPL3 or (L)GPL2.
   . Initial support for Wayland clients
   . [mir_demo_client_display_config] add orientation changing
   . RPC: Don't require the server ACK client's buffer-release requests.
   . Added libmirclientcpp to Mir source package
   . Added libmiral to Mir source package
   . Various small improvements to miral-shell example
   . [libmiral, miral-shell] handle display reconfiguration better and allow
 shells to customize maximized placements.
   . Enable CommandLineOptions to be processed before server initialization
 - Bugs fixed:
   . Fix handling of invalid display configuration. (LP: #1643446)
   . Move full responsibility for buffer IPC into frontend. (LP: #1395421)
   . Don't destroy an IPC "closure" object when it may yet be used
 (LP: #1672960)
   . [mesa-kms] Respect display orientation when painting cursor.
 (LP: #1610078)
   . Respect cursor hotspot when hosted on Mir. (LP: #1705284)
   . mcl::BufferVault: Fix lock inversion.
   . Handle mir_event_type_close_window in examples (LP: #1706004),
 (LP: #1705439)
   . Drop BufferStream::suitable_for_cursor()
   . Only notify resize events for valid surfaces (LP: #1643446)
   . Don't leak DRM fds in platform-eglstream probe.
   . Remove obsolete & broken example code. (LP: #1663130)
   . Move buffer-release IPC to a dedicated IPC thread. (LP: #1395421)
   . [NestedServerWithTwoDisplays] Look for the last of a series of
 synthetic events to ensure that the queue is drained before the test
 exits. (LP: #1709666)
   . floating window manager allows resizing maximized windows (LP: 
#1704776)
   . [miral-shell] doesn't work with breeze X cursor theme (LP: #1699084)
   . [miral-shell] Don't allow splashscreen to be occluded (LP: #1705973)
   . [miral-shell] Update maximized windows on display changes (LP: 
#1705695)
   . Make racy DragAndDrop test reliable. (LP: #1704780)
   . [libmiral] Define default window settings in one place and clamp the
 actual values to avoid ldiv0. (LP: #1717061)
   . [miral-kiosk] Apply fullscreen logic when hidden windows are restored.
 (LP: #1717910)
   . [mir-on-x11] Less annoying clipping of Mir-on-X11 window when it 
exceeds
 display bounds. (LP: #1668599)

  See https://bileto.ubuntu.com/#/ticket/2983 for build artifacts.

  Install log: http://pastebin.ubuntu.com/25707752/

  We've followed https://wiki.ubuntu.com/Process/Merges/TestPlans/Mir
  for testing.

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

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

[Touch-packages] [Bug 1722635] Re: apport-gtk crashed with SIGSEGV

[Apport retracing service]

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1722635/+attachment/4967012/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1722635/+attachment/4967015/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1722635/+attachment/4967018/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1722635/+attachment/4967019/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1722635/+attachment/4967020/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1722635/+attachment/4967021/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1722635/+attachment/4967022/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1552577
   apport-gtk crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  apport-gtk crashed with SIGSEGV

Status in apport package in Ubuntu:
  New

Bug description:
  ubuntu asked me to report this so that is hopefully what I'm doing

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: apport-gtk 2.20.7-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Oct 10 20:27:09 2017
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2017-09-22 (18 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f00a38db009:mov(%rbx),%rdi
   PC (0x7f00a38db009) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-10-10 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1722629] Re: package ca-certificates 20170717~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package ca-certificates 20170717~14.04.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  after update process. Now a windo appears each time i boot : system
  problem detected

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: ca-certificates 20170717~14.04.1
  ProcVersionSignature: Ubuntu 4.4.0-97.120~14.04.1-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Mon Oct  9 22:13:41 2017
  DuplicateSignature: package:ca-certificates:20170717~14.04.1:subprocess 
installed post-installation script returned error exit status 128
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2012-05-18 (1971 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120425-15:28
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: ca-certificates
  Title: package ca-certificates 20170717~14.04.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: Upgraded to trusty on 2016-05-21 (507 days ago)

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

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

[Touch-packages] [Bug 1722292] [NEW] [FFe] Mir 1.0 release

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

 * New upstream release 1.0.0(https://launchpad.net/mir/+milestone/1.0.0)
   - ABI summary:
 . mirclient ABI unchanged at 9
 . miral ABI introduced at 2
 . mirserver ABI bumped to 45
 . mircommon ABI unchanged at 7
 . mirplatform ABI unchanged at 61
 . mirprotobuf ABI unchanged at 3
 . mirplatformgraphics ABI unchanged at 13
 . mirclientplatform ABI unchanged at 5
 . mirinputplatform ABI unchanged at 7
 . mircore ABI unchanged at 1
   - Enhancements:
 . Update licences to (L)GPL3 or (L)GPL2.
 . Initial support for Wayland clients
 . [mir_demo_client_display_config] add orientation changing
 . RPC: Don't require the server ACK client's buffer-release requests.
 . Added libmirclientcpp to Mir source package
 . Added libmiral to Mir source package
 . Various small improvements to miral-shell example
 . [libmiral, miral-shell] handle display reconfiguration better and allow
   shells to customize maximized placements.
 . Enable CommandLineOptions to be processed before server initialization
   - Bugs fixed:
 . Fix handling of invalid display configuration. (LP: #1643446)
 . Move full responsibility for buffer IPC into frontend. (LP: #1395421)
 . Don't destroy an IPC "closure" object when it may yet be used
   (LP: #1672960)
 . [mesa-kms] Respect display orientation when painting cursor.
   (LP: #1610078)
 . Respect cursor hotspot when hosted on Mir. (LP: #1705284)
 . mcl::BufferVault: Fix lock inversion.
 . Handle mir_event_type_close_window in examples (LP: #1706004),
   (LP: #1705439)
 . Drop BufferStream::suitable_for_cursor()
 . Only notify resize events for valid surfaces (LP: #1643446)
 . Don't leak DRM fds in platform-eglstream probe.
 . Remove obsolete & broken example code. (LP: #1663130)
 . Move buffer-release IPC to a dedicated IPC thread. (LP: #1395421)
 . [NestedServerWithTwoDisplays] Look for the last of a series of
   synthetic events to ensure that the queue is drained before the test
   exits. (LP: #1709666)
 . floating window manager allows resizing maximized windows (LP: #1704776)
 . [miral-shell] doesn't work with breeze X cursor theme (LP: #1699084)
 . [miral-shell] Don't allow splashscreen to be occluded (LP: #1705973)
 . [miral-shell] Update maximized windows on display changes (LP: #1705695)
 . Make racy DragAndDrop test reliable. (LP: #1704780)
 . [libmiral] Define default window settings in one place and clamp the
   actual values to avoid ldiv0. (LP: #1717061)
 . [miral-kiosk] Apply fullscreen logic when hidden windows are restored.
   (LP: #1717910)
 . [mir-on-x11] Less annoying clipping of Mir-on-X11 window when it exceeds
   display bounds. (LP: #1668599)

See https://bileto.ubuntu.com/#/ticket/2983 for build artifacts.

Install log: http://pastebin.ubuntu.com/25707752/

We've followed https://wiki.ubuntu.com/Process/Merges/TestPlans/Mir for
testing.

** Affects: mir (Ubuntu)
 Importance: High
 Status: Confirmed

-- 
[FFe] Mir 1.0 release
https://bugs.launchpad.net/bugs/1722292
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mir in Ubuntu.

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

[Touch-packages] [Bug 1722629] [NEW] package ca-certificates 20170717~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[pdm]

Public bug reported:

after update process. Now a windo appears each time i boot : system
problem detected

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: ca-certificates 20170717~14.04.1
ProcVersionSignature: Ubuntu 4.4.0-97.120~14.04.1-generic 4.4.87
Uname: Linux 4.4.0-97-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: amd64
Date: Mon Oct  9 22:13:41 2017
DuplicateSignature: package:ca-certificates:20170717~14.04.1:subprocess 
installed post-installation script returned error exit status 128
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2012-05-18 (1971 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120425-15:28
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: ca-certificates
Title: package ca-certificates 20170717~14.04.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: Upgraded to trusty on 2016-05-21 (507 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package ca-certificates 20170717~14.04.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  after update process. Now a windo appears each time i boot : system
  problem detected

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: ca-certificates 20170717~14.04.1
  ProcVersionSignature: Ubuntu 4.4.0-97.120~14.04.1-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Mon Oct  9 22:13:41 2017
  DuplicateSignature: package:ca-certificates:20170717~14.04.1:subprocess 
installed post-installation script returned error exit status 128
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2012-05-18 (1971 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120425-15:28
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: ca-certificates
  Title: package ca-certificates 20170717~14.04.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: Upgraded to trusty on 2016-05-21 (507 days ago)

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

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

[Touch-packages] [Bug 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by lo

[Gabor Simon]

Thanks for the kernel bugzilla link, Dik, its power-save saving
suspicion seems valid, at least now I had a full day of uptime without
this wifi failure.

So, for anyone else who also wants to give it a try:

1. If you are using NetworkManager, then check
'/etc/NetworkManager/conf.d/default-wifi-powersave-on.conf', and try
setting 'wifi.powersave = 0'

2. If you aren't using NetworkManager, then you may add an udev rule for 
turning it off:
Add this to '/etc/udev/rules.d/90-iwl3945-quirk.rules':
# disable power saving, as per https://bugzilla.kernel.org/show_bug.cgi?id=93041
ACTION=="add", SUBSYSTEM=="net", ENV{DEVTYPE}=="wlan", 
ENV{ID_NET_DRIVER}=="iwl3945", RUN+="/sbin/iw dev %E{INTERFACE} set power_save 
off"

NOTE: the '90-...' is important, as it must be evaluated after
'80-drivers.rules' (I think).

3. You may set it manually via 'iw dev  set power_save off', but it will 
last only
until something overrides it, or until reboot.


I collected some dmesg stack traces, this was the most relevant one (the rest 
came from generic ieee80211 code).

[ 7729.780167] [ cut here ]
[ 7729.780189] WARNING: CPU: 1 PID: 4563 at 
/build/linux-CQR1pk/linux-4.10.0/drivers/net/wireless/intel/iwlegacy/common.c:3178
 il_enqueue_hcmd+0x35c/0x3d0 [iwlegacy]
[ 7729.780191] Modules linked in: uas usb_storage ccm pcmcia coretemp kvm_intel 
kvm input_leds joydev arc4 irqbypass iwl3945 iwlegacy serio_raw mac80211 
yenta_socket snd_hda_codec_conexant snd_hda_codec_generic pcmcia_rsrc lpc_ich 
pcmcia_core snd_hda_intel cfg80211 snd_hda_codec snd_hda_core snd_hwdep snd_pcm 
snd_timer snd soundcore shpchp toshiba_acpi sparse_keymap industrialio wmi 
mac_hid parport_pc ppdev lp parport ip_tables x_tables autofs4 raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear hid_generic i915 8139too usbhid 
i2c_algo_bit psmouse drm_kms_helper syscopyarea 8139cp sysfillrect sysimgblt 
pata_acpi fb_sys_fops mii drm hid fjes video
[ 7729.780260] CPU: 1 PID: 4563 Comm: kworker/u4:1 Tainted: GW   
4.10.0-19-generic #21-Ubuntu
[ 7729.780261] Hardware name: TOSHIBA SATELLITE L100/SATELLITE L100, BIOS V3.00 
   12/25/2008
[ 7729.780307] Workqueue: phy0 ieee80211_scan_work [mac80211]
[ 7729.780309] Call Trace:
[ 7729.780318]  dump_stack+0x58/0x73
[ 7729.780321]  __warn+0xea/0x110
[ 7729.780330]  ? il_enqueue_hcmd+0x35c/0x3d0 [iwlegacy]
[ 7729.780332]  warn_slowpath_null+0x2a/0x30
[ 7729.780340]  il_enqueue_hcmd+0x35c/0x3d0 [iwlegacy]
[ 7729.780344]  ? default_send_IPI_single+0x2c/0x30
[ 7729.780347]  ? native_smp_send_reschedule+0x1f/0x40
[ 7729.780354]  il_send_cmd_sync+0x40/0x340 [iwlegacy]
[ 7729.780360]  il3945_request_scan+0x3e6/0x5a0 [iwl3945]
[ 7729.780368]  il_mac_hw_scan+0x108/0x180 [iwlegacy]
[ 7729.780400]  __ieee80211_start_scan+0x22d/0x6a0 [mac80211]
[ 7729.780433]  ieee80211_scan_work+0x3db/0x4b0 [mac80211]
[ 7729.780437]  process_one_work+0x1b8/0x420
[ 7729.780440]  worker_thread+0x37/0x4c0
[ 7729.780442]  ? process_one_work+0x420/0x420
[ 7729.780445]  kthread+0xd5/0x100
[ 7729.780447]  ? process_one_work+0x420/0x420
[ 7729.780449]  ? kthread_create_on_node+0x30/0x30
[ 7729.780453]  ret_from_fork+0x21/0x2c
[ 7729.780456] ---[ end trace 2fddf3f499f47c42 ]---

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

Title:
  [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945
  :03:00.0: BSM uCode verification failed at addr ...; wlan0:
  deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING),

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
  WICD on-the-fly enables to continue browsing without rebooting, so it
  seems to be no hardware issue or iwl3945 issue.

  What to expect: stable connections and flawless network managing.
  What happens: so above.

  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.

  Interesting, according to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  apt-cache policy network-manager
  network-manager:
    Installiert:   0.9.8.8-0ubuntu28
    Installationskandidat: 0.9.8.8-0ubuntu28
    Versionstabelle:
   *** 0.9.8.8-0ubuntu28 0
  500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

[Touch-packages] [Bug 1722622] [NEW] Brightness

[Dayana]

Public bug reported:

I can't change the brightness

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-132.181-generic 3.13.11-ckt39
Uname: Linux 3.13.0-132-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Oct 10 21:51:19 2017
DistUpgraded: 2017-10-09 23:27:38,749 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:2213]
InstallationDate: Installed on 2017-10-06 (3 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Hewlett-Packard HP 15 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-132-generic 
root=UUID=f74ed4d8-459a-4372-9992-efa8be3f558e ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2017-10-09 (0 days ago)
dmi.bios.date: 05/26/2015
dmi.bios.vendor: Insyde
dmi.bios.version: F.39
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2213
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 57.54
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.39:bd05/26/2015:svnHewlett-Packard:pnHP15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2213:rvr57.54:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP 15 Notebook PC
dmi.product.version: 0991100600087
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
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.9
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: Tue Oct 10 21:42:38 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5547 
 vendor CMN
xserver.version: 2:1.15.1-0ubuntu2.9

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu

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

Title:
  Brightness

Status in xorg package in Ubuntu:
  New

Bug description:
  I can't change the brightness

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-132.181-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-132-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Oct 10 21:51:19 2017
  DistUpgraded: 2017-10-09 23:27:38,749 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:2213]
  InstallationDate: Installed on 2017-10-06 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-132-generic 
root=UUID=f74ed4d8-459a-4372-9992-efa8be3f558e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2017-10-09 (0 days ago)
  dmi.bios.date: 05/26/2015
 

[Touch-packages] [Bug 1699216] Re: Encrypted home support

[Jeremy Soller]

12:36   seb128  dmj_s76, right, we are likely to get it reviewed next cycle
12:37   seb128  it hasn't been high priority for us since we don't use 
gnome-inital-setup and don't plan to for next cycle either
12:37   seb128  but we should be able to review those changes anyways
12:51   jackpot51   seb128 what about for creating new users? It is not 
supported in gnome-control-center either
12:52   seb128  jackpot51, that would be a nice improvement to get
12:52   seb128  but for next cycle now

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

Title:
  Encrypted home support

Status in accountsservice package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-initial-setup package in Ubuntu:
  Confirmed

Bug description:
  In the CreateUser D-bus call, allow the home directory of the new user
  to be encrypted.

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

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

[Touch-packages] [Bug 1719720] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From hegdevas...@in.ibm.com 2017-10-10 14:24 EDT---
(In reply to comment #8)
> (In reply to comment #7)
> > On Thu, Sep 28, 2017 at 06:20:03AM -, bugproxy wrote:
> > > Yeah. even I thought its touch issue. I did look into touch source code
> > > as well. It uses below flag to create file.
> >
> > > O_WRONLY | O_CREAT | O_NONBLOCK | O_NOCTTY, MODE_RW_UGO);
> >
> > This is not about file creation flags, it's about memory maps.  This is
> > likely to be either a toolchain regression, or a bug in glibc, since touch
> > itself should not be calling mmap() for anything that it does.
>
> Looks like this is new flag introduced recently in systemd-udevd.service
> script.
>

How do we proceed with this bug? any update?

-Vasant

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

Title:
  [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with
  exit code 127

Status in The Ubuntu-power-systems project:
  Triaged
Status in coreutils package in Ubuntu:
  Triaged

Bug description:
  ---Problem Description---
  Currently syslog is getting flooded with below log messages ..
  Sep 25 03:16:41 ubuntu1710 systemd-udevd[2654]: Process '/bin/touch 
/run/run.vpdd
  update' failed with exit code 127.

  This is on UBuntu 17.10 latest build.. 
   
  ---uname output---
  Linux ubuntu1710 4.12.0-11-generic #12-Ubuntu SMP Fri Aug 11 12:23:06 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = ZZ-L 

  ---Steps to Reproduce---
   I have seen these messages logged more often when we do any hotplug 
operations.. ex. cpu hotplug..

  Ok. .this is the continuation of LTC #144627 / Launchpad #1682774.

  As suggested in that bug, we did change udev script to create
  temporary file under /run and that patch is available in ubuntu 17.10.

  Looks like this is udev script issue. If I modify systemd-udevd like
  below it works fine.

  I've limited udev knowledge. I don't know if you have any other better
  solution to this issue.

  root@ltc-boston123:/lib/systemd/system# diff -Naurp  
systemd-udevd.service.org systemd-udevd.service
  --- systemd-udevd.service.org 2017-09-26 04:37:47.090057318 -0500
  +++ systemd-udevd.service 2017-09-26 04:37:55.381739372 -0500
  @@ -25,7 +25,7 @@ KillMode=mixed
   WatchdogSec=3min
   TasksMax=infinity
   MountFlags=slave
  -MemoryDenyWriteExecute=yes
  +#MemoryDenyWriteExecute=yes
   RestrictRealtime=yes
   RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
   SystemCallArchitectures=native

  
  -Vasant

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

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

[Touch-packages] [Bug 1699216] Re: Encrypted home support

[Jeremy Soller]

IRC Log:


10:39   jackpot51   Can we talk about this patch again? 
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216
···
10:39   ubot5   Ubuntu bug 1699216 in gnome-initial-setup (Ubuntu) "Encrypted 
home support" [Wishlist,Confirmed]
10:40   jackpot51   I just saw a new accountsservice show up, superseding 
my patches for encrypted home.
10:40   jackpot51   Here is a debdiff of the patch I want to keep in 
accountsservice, one that allows gnome-initial-setup and gnome-control-center 
to support Encrypted Home 
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4945507/+files/accountsservice_encrypt_home.debdiff
···
10:40   ubot5   Ubuntu bug 1699216 in gnome-initial-setup (Ubuntu) "Encrypted 
home support" [Wishlist,Confirmed]
10:41   jackpot51   GunnarHj and others would you mind taking a look?
10:44   seb128  jackpot51, sounds a bit late in this cycle for such changes
10:47   jackpot51   All I want is the accountsservice patch, so we don't 
have to hold a forked accountsservice
10:52   jbicha  we never found anyone willing to review the accountsservice 
patch :(
10:53   jackpot51   Well, every time accountsservice gets updated in 
Ubuntu, I get fucked. Why? Because I cannot rename the package.
10:53   jackpot51   So I am probably going to have to drop the patches for 
encrypted home entirely
10:56   jbicha  once Ubuntu 17.10 is released, any SRUs for accountsservice 
will have to age in -proposed for at least 7 days first. That gives you time to 
update your PPA.
10:56   jackpot51   Ok, that would be good
10:57   jackpot51   Many users are getting pop-gnome-initial-setup removed 
if they dist-upgrade
10:58   jackpot51   It doesn't break their systems, but it introduces a 
significant amount of maintenance work
11:54   GunnarHjHi jackpot51, sorry if you felt ignored by my 
accountsservice upload. That was not my intention.
11:54   GunnarHjI have noticed your patches previously, but 
unfortunately they are too complex for me to review. The change I uploaded was 
a trivial one, and that's what I do - trivial stuff. :)
11:54   GunnarHjHopefully some experienced developer will find the time 
in the beginning of next cycle.
11:57   jackpot51   I dropped all our patches. Users will have to wait 
until Ubuntu can merge the patch, it is too much maintenance work to have 
encrypted home in gnome-initial-setup and gnome-control-center
11:59   jackpot51   The only other alternative was to use an epoch, which 
would make it impossible to go back to the Ubuntu version if the patches are 
merged
12:00   dmj_s76 This patch represents a fairly important feature for us.

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

Title:
  Encrypted home support

Status in accountsservice package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-initial-setup package in Ubuntu:
  Confirmed

Bug description:
  In the CreateUser D-bus call, allow the home directory of the new user
  to be encrypted.

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

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

[Touch-packages] [Bug 1722606] Re: apport-gtk crashed with SIGABRT in g_assertion_message()

[Apport retracing service]

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1722606/+attachment/4966868/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1722606/+attachment/4966870/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1722606/+attachment/4966873/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1722606/+attachment/4966874/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1722606/+attachment/4966875/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1722606/+attachment/4966876/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1722606/+attachment/4966877/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1622414

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  apport-gtk crashed with SIGABRT in g_assertion_message()

Status in apport package in Ubuntu:
  New

Bug description:
  dpkg -a configure on upgrade

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: apport-gtk 2.20.7-0ubuntu2
  Uname: Linux 4.13.0-041300rc1-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CrashReports:
   640:1000:119:2330704:2017-10-10 12:04:35.859253406 -0400:2017-10-10 
12:04:36.859253406 -0400:/var/crash/_usr_bin_nautilus-desktop.1000.crash
   640:1000:119:2037487:2017-10-10 12:05:33.015285491 -0400:2017-10-10 
12:05:34.015285491 
-0400:/var/crash/_usr_lib_gnome-terminal_gnome-terminal-server.1000.crash
   640:1000:119:23910688:2017-10-10 12:11:48.858009099 -0400:2017-10-10 
12:11:49.858009099 -0400:/var/crash/_usr_share_apport_apport-gtk.1000.crash
  CurrentDesktop: GNOME
  Date: Tue Oct 10 12:11:33 2017
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2017-07-23 (79 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  Signal: 6
  SourcePackage: apport
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1721840] Re: dl module is missing?

[Dimitri John Ledkov]

annoyingly python2 has: ctypes.RTLD_GLOBAL  ctypes.RTLD_LOCAL, but not
ctypes.RTLD_NOW

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

Title:
  dl module is missing?

Status in python2.7 package in Ubuntu:
  New

Bug description:
  The Python 2.7 documentation documents the "dl" module (I know it's
  deprecated and has been removed in Python 3), but it doesn't actually
  exist:

>>> import dl
Traceback (most recent call last):
  File "", line 1, in 
ImportError: No module named dl

  Seen with both 2.7.12-1ubuntu0~16.04.1 (xenial amd64) and
  2.7.14-2ubuntu2 (artful amd64).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1721840/+subscriptions

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

[Touch-packages] [Bug 1721840] Re: dl module is missing?

[Dimitri John Ledkov]

I wonder if https://pypi.python.org/pypi/backports.os
https://github.com/pjdelport/backports.os should grow this feature,
since python3 is the future.

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

Title:
  dl module is missing?

Status in python2.7 package in Ubuntu:
  New

Bug description:
  The Python 2.7 documentation documents the "dl" module (I know it's
  deprecated and has been removed in Python 3), but it doesn't actually
  exist:

>>> import dl
Traceback (most recent call last):
  File "", line 1, in 
ImportError: No module named dl

  Seen with both 2.7.12-1ubuntu0~16.04.1 (xenial amd64) and
  2.7.14-2ubuntu2 (artful amd64).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1721840/+subscriptions

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

[Touch-packages] [Bug 1455097] Re: /etc/pm/sleep.d/ is no more processed

[Launchpad Bug Tracker]

This bug was fixed in the package unattended-upgrades - 0.98ubuntu1

---
unattended-upgrades (0.98ubuntu1) artful; urgency=medium

  * Merge from Debian unstable (LP: #1722426)
- Remaining changes:
  - unattended-upgrades: Do not automatically upgrade the development
release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
- Dropped changes, included in Debian:
  - Use lsb_release instead of dpkg-vendor in postinst

unattended-upgrades (0.98) unstable; urgency=medium

  * Rename test to test_non_minimal_steps_upgrade to reflect content
  * Catch SystemError while keeping apt lock unlocked (LP: #1632361)
  * Add --stop-only option to unattended-upgrade-shutdown and use it on
hibernation. This prevents starting unattended-upgrades right before
hibernating when Unattended-Upgrade::InstallOnShutdown is true.
(Closes: #610333)
  * Stop already running unattended-upgrades before hibernation even with
systemd (LP: #1455097)
  * Use lsb_release instead of dpkg-vendor in postinst (LP: #1719630)
  * Update README.md with the fact that unattended=upgrades is enabled
by default (Closes: #865519)

 -- Balint Reczey   Tue, 10 Oct 2017 03:47:58 +0200

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Fix Released

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

Title:
  /etc/pm/sleep.d/ is no more processed

Status in aiccu package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in ifplugd package in Ubuntu:
  New
Status in lizardfs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  New
Status in pm-utils package in Ubuntu:
  Won't Fix
Status in toshset package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  I added a new script in /etc/pm/sleep.d/ that worked fine before the
  upgrade to vivid. I was wondering why it doesn't work and I find out
  that /var/log/pm-suspend.log is empty, and pm-powersave.log too (last
  logs from pm-suspend were on Apr 28, when I upgraded from utopic to
  vivid.

  The laptop suspends and wakes fine, it just seems that no pm scripts
  are run after suspend/powersave.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pm-utils 1.4.1-15
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 14 15:36:26 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-03-12 (792 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1632361] Re: unattended-update installArchives

[Launchpad Bug Tracker]

This bug was fixed in the package unattended-upgrades - 0.98ubuntu1

---
unattended-upgrades (0.98ubuntu1) artful; urgency=medium

  * Merge from Debian unstable (LP: #1722426)
- Remaining changes:
  - unattended-upgrades: Do not automatically upgrade the development
release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
- Dropped changes, included in Debian:
  - Use lsb_release instead of dpkg-vendor in postinst

unattended-upgrades (0.98) unstable; urgency=medium

  * Rename test to test_non_minimal_steps_upgrade to reflect content
  * Catch SystemError while keeping apt lock unlocked (LP: #1632361)
  * Add --stop-only option to unattended-upgrade-shutdown and use it on
hibernation. This prevents starting unattended-upgrades right before
hibernating when Unattended-Upgrade::InstallOnShutdown is true.
(Closes: #610333)
  * Stop already running unattended-upgrades before hibernation even with
systemd (LP: #1455097)
  * Use lsb_release instead of dpkg-vendor in postinst (LP: #1719630)
  * Update README.md with the fact that unattended=upgrades is enabled
by default (Closes: #865519)

 -- Balint Reczey   Tue, 10 Oct 2017 03:47:58 +0200

** Changed in: unattended-upgrades (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  unattended-update installArchives

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-98-generic 
/boot/vmlinuz-3.13.0-98-generic
  Generating grub configuration file ...
  Found linux image: /boot/vmlinuz-3.13.0-98-generic
  Found initrd image: /boot/initrd.img-3.13.0-98-generic
  Found linux image: /boot/vmlinuz-3.13.0-85-generic
  Found initrd image: /boot/initrd.img-3.13.0-85-generic
  Found linux image: /boot/vmlinuz-3.13.0-83-generic
  Found initrd image: /boot/initrd.img-3.13.0-83-generic
  done
  Setting up mysql-client-core-5.5 (5.5.52-0ubuntu0.14.04.1) ...
  Setting up mysql-client-5.5 (5.5.52-0ubuntu0.14.04.1) ...
  Setting up mysql-server-core-5.5 (5.5.52-0ubuntu0.14.04.1) ...
  Setting up mysql-server-5.5 (5.5.52-0ubuntu0.14.04.1) ...
  start: Job failed to start
  invoke-rc.d: initscript mysql, action "start" failed.
  dpkg: error processing package mysql-server-5.5 (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of mysql-server:
   mysql-server depends on mysql-server-5.5; however:
Package mysql-server-5.5 is not configured yet.

  dpkg: error processing package mysql-server (--configure):
   dependency problems - leaving unconfigured
  Setting up php5-common (5.5.9+dfsg-1ubuntu4.20) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.
  php5_invoke pdo: already enabled for apache2 SAPI
  php5_invoke pdo: already enabled for cli SAPI
  php5_invoke opcache: already enabled for apache2 SAPI
  php5_invoke opcache: already enabled for cli SAPI
  Setting up php5-mysql (5.5.9+dfsg-1ubuntu4.20) ...
  php5_invoke mysql: already enabled for apache2 SAPI
  php5_invoke mysql: already enabled for cli SAPI
  php5_invoke mysqli: already enabled for apache2 SAPI
  php5_invoke mysqli: already enabled for cli SAPI
  php5_invoke pdo_mysql: already enabled for apache2 SAPI
  php5_invoke pdo_mysql: already enabled for cli SAPI
  Setting up php5-cli (5.5.9+dfsg-1ubuntu4.20) ...
  php5_invoke opcache: already enabled for cli SAPI
  php5_invoke apcu: already enabled for cli SAPI
  php5_invoke json: already enabled for cli SAPI
  php5_invoke pdo_mysql: already enabled for cli SAPI
  php5_invoke pdo: already enabled for cli SAPI
  php5_invoke mysqli: already enabled for cli SAPI
  php5_invoke mysql: already enabled for cli SAPI
  php5_invoke gd: already enabled for cli SAPI
  php5_invoke mcrypt: already enabled for cli SAPI
  php5_invoke curl: already enabled for cli SAPI
  php5_invoke readline: already enabled for cli SAPI
  Setting up php5-readline (5.5.9+dfsg-1ubuntu4.20) ...
  php5_invoke readline: already enabled for apache2 SAPI
  php5_invoke readline: already enabled for cli SAPI
  Setting up apache2-bin (2.4.7-1ubuntu4.13) ...
  Setting up apache2-data (2.4.7-1ubuntu4.13) ...
  Setting up apache2 (2.4.7-1ubuntu4.13) ...
  Installing new version of config file 
/etc/apache2/mods-available/mpm_prefork.load ...
  Installing new version of config file 
/etc/apache2/mods-available/mpm_worker.load ...
  Installing new version of config file 
/etc/apache2/mods-available/mpm_event.load ...
   * Restarting web server apache2
 ...done.
  Setting up apache2-mpm-prefork (2.4.7-1ubuntu4.13) ...
  Setting up libapache2-mod-php5 (5.5.9+dfsg-1ubuntu4.20) ...
  

[Touch-packages] [Bug 1722426] Re: Please merge unattended-upgrades 0.98 (main) from Debian unstable (main) Edit

[Launchpad Bug Tracker]

This bug was fixed in the package unattended-upgrades - 0.98ubuntu1

---
unattended-upgrades (0.98ubuntu1) artful; urgency=medium

  * Merge from Debian unstable (LP: #1722426)
- Remaining changes:
  - unattended-upgrades: Do not automatically upgrade the development
release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
- Dropped changes, included in Debian:
  - Use lsb_release instead of dpkg-vendor in postinst

unattended-upgrades (0.98) unstable; urgency=medium

  * Rename test to test_non_minimal_steps_upgrade to reflect content
  * Catch SystemError while keeping apt lock unlocked (LP: #1632361)
  * Add --stop-only option to unattended-upgrade-shutdown and use it on
hibernation. This prevents starting unattended-upgrades right before
hibernating when Unattended-Upgrade::InstallOnShutdown is true.
(Closes: #610333)
  * Stop already running unattended-upgrades before hibernation even with
systemd (LP: #1455097)
  * Use lsb_release instead of dpkg-vendor in postinst (LP: #1719630)
  * Update README.md with the fact that unattended=upgrades is enabled
by default (Closes: #865519)

 -- Balint Reczey   Tue, 10 Oct 2017 03:47:58 +0200

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

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

Title:
   Please merge unattended-upgrades 0.98 (main) from Debian unstable
  (main) Edit

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  u-u 0.98 fixes bashism in 0.97ubuntu2'a postinst and fixes hibernation
  handling.

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

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

[Touch-packages] [Bug 1699216] Re: Encrypted home support

[Jeremy Soller]

This one updates the symbol names - they did not get updated with a
debuild -S

** Patch added: "accountsservice_encrypt_home.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4966858/+files/accountsservice_encrypt_home.debdiff

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

Title:
  Encrypted home support

Status in accountsservice package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-initial-setup package in Ubuntu:
  Confirmed

Bug description:
  In the CreateUser D-bus call, allow the home directory of the new user
  to be encrypted.

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

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

[Touch-packages] [Bug 1721840] Re: dl module is missing?

[Colin Watson]

Your changelog entry for 2.2.1-1 suggests that it was enabled once.

As far as I can tell there's no other terribly sensible way to get at
the value of RTLD_NOW in Python 2; I was helping a friend who was
writing a complicated thing to do with the Python gdb bindings that
needed that and that needed to work in both Python 2 and 3.  (In Python
3, it's os.RTLD_NOW.)

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

Title:
  dl module is missing?

Status in python2.7 package in Ubuntu:
  New

Bug description:
  The Python 2.7 documentation documents the "dl" module (I know it's
  deprecated and has been removed in Python 3), but it doesn't actually
  exist:

>>> import dl
Traceback (most recent call last):
  File "", line 1, in 
ImportError: No module named dl

  Seen with both 2.7.12-1ubuntu0~16.04.1 (xenial amd64) and
  2.7.14-2ubuntu2 (artful amd64).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1721840/+subscriptions

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

[Touch-packages] [Bug 1699216] Re: Encrypted home support

[Jeremy Soller]

Here is an updated version of the patch for accountsservice

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

Title:
  Encrypted home support

Status in accountsservice package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-initial-setup package in Ubuntu:
  Confirmed

Bug description:
  In the CreateUser D-bus call, allow the home directory of the new user
  to be encrypted.

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

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

[Touch-packages] [Bug 1699216] Re: Encrypted home support

[Jeremy Soller]

** Patch added: "accountsservice_encrypt_home.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4966857/+files/accountsservice_encrypt_home.debdiff

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

Title:
  Encrypted home support

Status in accountsservice package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-initial-setup package in Ubuntu:
  Confirmed

Bug description:
  In the CreateUser D-bus call, allow the home directory of the new user
  to be encrypted.

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

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

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[Brian Murray]

The verification of this also passed for Xenial, Ubuntu 16.04.

run-parts: executing /etc/kernel/prerm.d/dkms 4.4.0-31-generic 
/boot/vmlinuz-4.4.0-31-generic
dkms: removing: r8168 8.041.00 (4.4.0-31-generic) (x86_64)

 Uninstall Beginning 
Module:  r8168
Version: 8.041.00
Kernel:  4.4.0-31-generic (x86_64)
-

Status: Before uninstall, this module version was ACTIVE on this kernel.

r8168.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.4.0-31-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod

Backing up initrd.img-4.4.0-31-generic to 
/boot/initrd.img-4.4.0-31-generic.old-dkms
Making new initrd.img-4.4.0-31-generic
(If next boot fails, revert to initrd.img-4.4.0-31-generic.old-dkms image)
update-initramfs

DKMS: uninstall completed.
removed '/boot/initrd.img-4.4.0-31-generic.old-dkms'
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-31-generic 
/boot/vmlinuz-4.4.0-31-generic
update-initramfs: Deleting /boot/initrd.img-4.4.0-31-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-31-generic 
/boot/vmlinuz-4.4.0-31-generic
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
Found linux image: /boot/vmlinuz-4.4.0-97-generic
Found initrd image: /boot/initrd.img-4.4.0-97-generic
Found linux image: /boot/vmlinuz-4.4.0-38-generic
Found initrd image: /boot/initrd.img-4.4.0-38-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
done
bdmurray@clean-xenial-amd64:~$ ls -lh /boot/
total 132M
-rw-r--r-- 1 root root 1.2M Sep  6  2016 abi-4.4.0-38-generic
-rw-r--r-- 1 root root 1.2M Sep 19 13:29 abi-4.4.0-97-generic
-rw-r--r-- 1 root root 186K Sep  6  2016 config-4.4.0-38-generic
-rw-r--r-- 1 root root 187K Sep 19 13:29 config-4.4.0-97-generic
drwxr-xr-x 5 root root 4.0K Oct 10 09:42 grub
-rw-r--r-- 1 root root  36M Oct 10 09:39 initrd.img-4.4.0-38-generic
-rw-r--r-- 1 root root  36M Oct 10 09:38 initrd.img-4.4.0-38-generic.old-dkms
-rw-r--r-- 1 root root  37M Oct 10 09:41 initrd.img-4.4.0-97-generic
-rw-r--r-- 1 root root 179K Jan 28  2016 memtest86+.bin
-rw-r--r-- 1 root root 181K Jan 28  2016 memtest86+.elf
-rw-r--r-- 1 root root 181K Jan 28  2016 memtest86+_multiboot.bin
-rw--- 1 root root 3.7M Sep  6  2016 System.map-4.4.0-38-generic
-rw--- 1 root root 3.8M Sep 19 13:29 System.map-4.4.0-97-generic
-rw--- 1 root root 6.8M Sep  6  2016 vmlinuz-4.4.0-38-generic
-rw--- 1 root root 6.8M Sep 19 13:29 vmlinuz-4.4.0-97-generic


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

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  New
Status in dkms source package in Zesty:
  Fix Committed
Status in initramfs-tools source package in Zesty:
  New
Status in dkms package in Debian:
  New

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting 
has be manually configured by a user then when a kernel is removed its possible 
for an ".old-dkms" file to be left in /boot with no associated kernel.

  [Test Case]
  On a system with two old kernels and one new kernel available in -updates:
  1) install r8168-dkms
  2) install the dkms module for the old kernel e.g. 'sudo dkms install -m 
r8168 -v 8.041.00 -k 4.4.0-31-generic'
  3) upgrade your kernel e.g. "sudo apt install linux-image-generic'
  4) sudo apt autoremove
  5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot 
without a corresponding "initrd.img-4.4.0-31-generic"

  With the version of dkms in -proposed, the .old-dkms file will be
  removed when the kernel is auto removed.

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems 
like an odd expectation.

  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[Brian Murray]

I've verified that the version of dkms, 2.3-3ubuntu1.2, in zesty-
proposed now does the right thing.

Backing up initrd.img-4.10.0-19-generic to 
/boot/initrd.img-4.10.0-19-generic.old-dkms
Making new initrd.img-4.10.0-19-generic
(If next boot fails, revert to initrd.img-4.10.0-19-generic.old-dkms image)
update-initramfs...

DKMS: uninstall completed.
removed '/boot/initrd.img-4.10.0-19-generic.old-dkms'
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.10.0-19-generic 
/boot/vmlinuz-4.10.0-19-generic
update-initramfs: Deleting /boot/initrd.img-4.10.0-19-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.10.0-19-generic 
/boot/vmlinuz-4.10.0-19-generic
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
Found linux image: /boot/vmlinuz-4.10.0-37-generic
Found initrd image: /boot/initrd.img-4.10.0-37-generic
Found linux image: /boot/vmlinuz-4.10.0-28-generic
Found initrd image: /boot/initrd.img-4.10.0-28-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
done
bdmurray@clean-zesty-amd64:~$ ls -lh /boot/
total 149M
-rw-r--r-- 1 root root 1.4M Jun 29 02:14 abi-4.10.0-28-generic
-rw-r--r-- 1 root root 1.4M Oct  6 12:45 abi-4.10.0-37-generic
-rw-r--r-- 1 root root 201K Jun 29 02:14 config-4.10.0-28-generic
-rw-r--r-- 1 root root 201K Oct  6 12:45 config-4.10.0-37-generic
drwxr-xr-x 5 root root 4.0K Oct 10 09:33 grub
-rw-r--r-- 1 root root  42M Oct 10 09:26 initrd.img-4.10.0-28-generic
-rw-r--r-- 1 root root  41M Oct 10 09:26 initrd.img-4.10.0-28-generic.old-dkms
-rw-r--r-- 1 root root  42M Oct 10 09:29 initrd.img-4.10.0-37-generic
-rw-r--r-- 1 root root 179K Jan 28  2016 memtest86+.bin
-rw-r--r-- 1 root root 181K Jan 28  2016 memtest86+.elf
-rw-r--r-- 1 root root 181K Jan 28  2016 memtest86+_multiboot.bin
-rw--- 1 root root 3.6M Jun 29 02:14 System.map-4.10.0-28-generic
-rw--- 1 root root 3.6M Oct  6 12:45 System.map-4.10.0-37-generic
-rw--- 1 root root 7.3M Jun 29 02:14 vmlinuz-4.10.0-28-generic
-rw--- 1 root root 7.3M Oct  6 12:45 vmlinuz-4.10.0-37-generic


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

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  New
Status in dkms source package in Zesty:
  Fix Committed
Status in initramfs-tools source package in Zesty:
  New
Status in dkms package in Debian:
  New

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting 
has be manually configured by a user then when a kernel is removed its possible 
for an ".old-dkms" file to be left in /boot with no associated kernel.

  [Test Case]
  On a system with two old kernels and one new kernel available in -updates:
  1) install r8168-dkms
  2) install the dkms module for the old kernel e.g. 'sudo dkms install -m 
r8168 -v 8.041.00 -k 4.4.0-31-generic'
  3) upgrade your kernel e.g. "sudo apt install linux-image-generic'
  4) sudo apt autoremove
  5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot 
without a corresponding "initrd.img-4.4.0-31-generic"

  With the version of dkms in -proposed, the .old-dkms file will be
  removed when the kernel is auto removed.

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems 
like an odd expectation.

  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: allSourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

[Scott Moser]

** Attachment added: "lp-1711760-test.sh:  script to aid in testing default to 
proposed"
   
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/4966838/+files/lp-1711760-test.sh

** Attachment removed: "lp-1711760 script to aid in testing"
   
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/4961827/+files/lp-1711760-test

** Attachment removed: "lp-1711760-test.sh:  script to aid in testing"
   
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/4966752/+files/lp-1711760-test.sh

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

Title:
  [2.3] resolv.conf is not set (during commissioning or testing)

Status in MAAS:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  In Progress

Bug description:
  === Begin SRU Template ===
  [Impact] 
  Without this fix applied, dns settings provided to the dhcp response
  in the initramfs are not reflected in the "real root".

  Thus dns resolution does not work. Of most interest was the MAAS use
  case of the 'root=http://<>/squashfs' use case.  MAAS 2.3 uses this for
  the installation environment and also the rescue environment.

  [Test Case]
  There are two tests for this.

  a.) local/non-MAAS test
  Download the test case attached.
  Run it and follow the instructions.
  Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
  without the fix there would be no data in /etc/resolv.conf.  With the
  fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'

  b.) MAAS test.
  For the full maas test, you need to build a image stream for maas
  with the fix included in the squashfs image and then import that
  stream to maas and use the rescue environment and verify dns.
  This process is beyond the scope of the SRU template, but is
  described partially in 

http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README

  
  [Regression Potential] 
  Regression potential should be very low.  There are gates in the code
  to make sure that this code is inactive other than when it is explicitly
  enabled.

  net-interface-handler will exit without doing anything unless:
  a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
  and these files have non-empty values for a variable mentioned above.
  (These files are written by the initramfs code when 'ip=' is seen).

  b.) this is not a container.

  b.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
  if open-iscsi has written this file due to open-iscsi root, then it
  will handle this functionality. resolvconf will get out of the way.

  c.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
  This lowers the scope of changes in runtime to cases with where either the
  new flag is seen or cloud-config-url is passed. The MAAS use case will
  contain this flag.

  [Other Info]
   
  === End SRU Template ===

  Using MAAS 2.3, during commissioning (and likely in the rest of the
  ephemeral environment) we have noticed that resolv.conf is not set
  with the DNS server.

  That said, during the commissioning process, MAAS does not send any
  metadata to cloud-init to configure the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:

  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0

  Which correctly includes the DNS server. However:

  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com

  If restart the interfacE:

  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x5403eb14)
  DHCPOFFER of 192.168.122.195 from 192.168.122.2
  DHCPACK of 192.168.122.195 from 192.168.122.2
  Restarting ntp (via systemctl): ntp.service.
  bound to 

[Touch-packages] [Bug 1722397] Re: idle doesn't run in 17.10

[Serhiy Storchaka]

** Changed in: python3-defaults (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  idle doesn't run in 17.10

Status in python3-defaults package in Ubuntu:
  Fix Released

Bug description:
  In 17.10 the idle package (v. 3.6.3-0ubuntu1) depends on Python 3.6.
  But the /usr/bin/idle script contains the code that doesn't work in
  Python 3.6.

  $ idle
  Traceback (most recent call last):
File "/usr/bin/idle", line 3, in 
  from idlelib.PyShell import main
  ModuleNotFoundError: No module named 'idlelib.PyShell'

  In Python 3.6 the PyShell module was renamed to pyshell (see
  https://bugs.python.org/issue24225).

  /usr/bin/idle-python3.6 from the idle-python3.6 package works
  correctly.

  Maybe make /usr/bin/idle just a link to /usr/bin/idle-python3.6?

  If you want /usr/bin/idle always run the default python3 and don't
  depent of future changes in the idlelib Python package, you can make
  it a shell script:

  #! /bin/sh
  exec /usr/bin/python3 -m idlelib

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

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

[Touch-packages] [Bug 1722426] Re: Please merge unattended-upgrades 0.98 (main) from Debian unstable (main) Edit

[Mathieu Trudel-Lapierre]

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

** Changed in: unattended-upgrades (Ubuntu)
 Assignee: (unassigned) => Balint Reczey (rbalint)

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

Title:
   Please merge unattended-upgrades 0.98 (main) from Debian unstable
  (main) Edit

Status in unattended-upgrades package in Ubuntu:
  In Progress

Bug description:
  u-u 0.98 fixes bashism in 0.97ubuntu2'a postinst and fixes hibernation
  handling.

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

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

[Touch-packages] [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

[Scott Moser]

** Description changed:

+ === Begin SRU Template ===
+ [Impact] 
+ Without this fix applied, dns settings provided to the dhcp response
+ in the initramfs are not reflected in the "real root".
+ 
+ Thus dns resolution does not work. Of most interest was the MAAS use
+ case of the 'root=http://<>/squashfs' use case.  MAAS 2.3 uses this for
+ the installation environment and also the rescue environment.
+ 
+ [Test Case]
+ There are two tests for this.
+ 
+ a.) local/non-MAAS test
+ Download the test case attached.
+ Run it and follow the instructions.
+ Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
+ without the fix there would be no data in /etc/resolv.conf.  With the
+ fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'
+ 
+ b.) MAAS test.
+ For the full maas test, you need to build a image stream for maas
+ with the fix included in the squashfs image and then import that
+ stream to maas and use the rescue environment and verify dns.
+ This process is beyond the scope of the SRU template, but is
+ described partially in 
+   
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README
+ 
+ 
+ [Regression Potential] 
+ Regression potential should be very low.  There are gates in the code
+ to make sure that this code is inactive other than when it is explicitly
+ enabled.
+ 
+ net-interface-handler will exit without doing anything unless:
+ a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
+ and these files have non-empty values for a variable mentioned above.
+ (These files are written by the initramfs code when 'ip=' is seen).
+ 
+ b.) this is not a container.
+ 
+ b.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
+ if open-iscsi has written this file due to open-iscsi root, then it
+ will handle this functionality. resolvconf will get out of the way.
+ 
+ c.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
+ This lowers the scope of changes in runtime to cases with where either the
+ new flag is seen or cloud-config-url is passed. The MAAS use case will
+ contain this flag.
+ 
+ [Other Info]
+  
+ === End SRU Template ===
+ 
  Using MAAS 2.3, during commissioning (and likely in the rest of the
  ephemeral environment) we have noticed that resolv.conf is not set with
  the DNS server.
  
  That said, during the commissioning process, MAAS does not send any
  metadata to cloud-init to configure the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:
  
  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  
  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0
  
  Which correctly includes the DNS server. However:
  
  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com
  
  If restart the interfacE:
  
  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/
  
  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x5403eb14)
  DHCPOFFER of 192.168.122.195 from 192.168.122.2
  DHCPACK of 192.168.122.195 from 192.168.122.2
  Restarting ntp (via systemctl): ntp.service.
  bound to 192.168.122.195 -- renewal in 290 seconds.
  
  ubuntu@manual:~$ 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
  nameserver 192.168.122.2
  search maas
  
  ubuntu@manual:~$ ping google.com
  PING google.com (216.58.192.46) 56(84) bytes of data.
  64 bytes from mia07s46-in-f14.1e100.net (216.58.192.46): icmp_seq=1 ttl=52 
time=7.47 ms
  ^C
  --- google.com ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 7.472/7.472/7.472/0.000 ms
  
  As such, this either seems like a bug in Ubuntu, or caused by cloud-init
  when writing e/n/i.d/50-cloud-init.cfg
  
  ubuntu@manual:~$ dpkg -l | grep cloud-init
  ii  cloud-init   

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[Denis Kalinin]

OK, I've just compiled freetype 2.8.1 from the latest source

https://sourceforge.net/projects/freetype/files/freetype2/2.8.1/

and re-pointed the `libfreetype.so.6` link to a newly built .SO-file. I
restarted the system and the hinting started working great. So,
apparently only the 2.8.0 version of "freetype" is affected.
Unfortunately, this is the version that's going to be shipped with
Artful.

** Description changed:

  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-wise.
  However, if you install "gnome-tweak-tool" and disable antialiasing
  there, the problem becomes obvious.
  
  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/
  
  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/
  
  * When comparing the pictures make sure you "Open image in new tab" and
  see them without browser zoom, otherwise the problem may no be obvious.
  
  I suspect that this issue is caused by a bug in some base font rendering
- package that Ubuntu uses. A couple of months ago a similar issue was
- reported (and promptly fixed) in Chromium after they had changed
- something in FreeType rendering
+ package that Ubuntu uses (edit: the problem is probably caused by
+ FreeType 2.8.0, see my comments below). A couple of months ago a similar
+ issue was reported (and promptly fixed) in Chromium after they had
+ changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).
- 
  
  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

Title:
  Font hinting appears broken on 17.10 beta

Status in freetype package in Ubuntu:
  New

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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

[Touch-packages] [Bug 1722313] Re: [SRU][xenial] Add "--with-audit" config option so that the hwclock command creates an audit record when the hardware clock is altered.

[dann frazier]

** Also affects: util-linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: util-linux (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: util-linux (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

Title:
  [SRU][xenial] Add "--with-audit" config option so that the hwclock
  command creates an audit record when the hardware clock is altered.

Status in util-linux package in Ubuntu:
  New
Status in util-linux source package in Xenial:
  New
Status in util-linux source package in Zesty:
  New
Status in util-linux source package in Artful:
  New
Status in util-linux package in Debian:
  Unknown

Bug description:
  [IMPACT]
  There is a requirement for Common Criteria EAL2 certification that changes to 
the system's hardware clock be audited/monitored. In Ubuntu the hwclock command 
can be used to alter the system's hardware clock. Thus this event needs to be 
audited for EAL2. The hwclock command within util-linux has the ability to 
create an audit event when the system's hardware clock is altered, but this 
ability is enabled via the --with-audit config option. This option is currently 
not enabled.

  Only the hwclock and the login commands within util-linux package use
  this --with-audit config option to enable auditing. However, it
  appears the login command is not built nor shipped in util-linux.
  Ubuntu uses the login command from shadow instead. Thus, only hwclock
  command would be affected by this change. The change would enable (1)
  call to audit_open to create a netlink socket descritor. (2) generate
  an audit entry when system hardware clock altered. The entry will be
  logged into the /var/log/audit/audit.log IF auditd is installed and
  running.

  [TEST]

  This has been tested on both P8 and amd64 architectures. With the
  patch all the Common Criteria testcases pass for hwclock. Before this
  patch, the functional part of the testcase passed, but the check for
  the triggered audit records would fail. Attached the Common Criteria
  testcase below.

  Also, the util-linux package has testcases that get run during the
  build. All of these pass. Pointer to build log below.

  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

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

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

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[Brian Murray]

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

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

Title:
  Font hinting appears broken on 17.10 beta

Status in freetype package in Ubuntu:
  New

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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

[Touch-packages] [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

[Scott Moser]

I've also asked the MAAS team to build a maas-images with an updated
squashfs.

I made a couple changes to lp:maas-images on Friday to make that easy to do
 
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/revision/381
 
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/revision/382

So, to build a image and stream with this content, you essentially need
to just set M2E_ADD_REPOS in the environment and then build as you
would.

example:
  export M2E_ADD_REPOS=ppa:smoser/lp1711760

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

Title:
  [2.3] resolv.conf is not set (during commissioning or testing)

Status in MAAS:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  In Progress

Bug description:
  Using MAAS 2.3, during commissioning (and likely in the rest of the
  ephemeral environment) we have noticed that resolv.conf is not set
  with the DNS server.

  That said, during the commissioning process, MAAS does not send any
  metadata to cloud-init to configure the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:

  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0

  Which correctly includes the DNS server. However:

  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com

  If restart the interfacE:

  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x5403eb14)
  DHCPOFFER of 192.168.122.195 from 192.168.122.2
  DHCPACK of 192.168.122.195 from 192.168.122.2
  Restarting ntp (via systemctl): ntp.service.
  bound to 192.168.122.195 -- renewal in 290 seconds.

  ubuntu@manual:~$ 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
  nameserver 192.168.122.2
  search maas

  ubuntu@manual:~$ ping google.com
  PING google.com (216.58.192.46) 56(84) bytes of data.
  64 bytes from mia07s46-in-f14.1e100.net (216.58.192.46): icmp_seq=1 ttl=52 
time=7.47 ms
  ^C
  --- google.com ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 7.472/7.472/7.472/0.000 ms

  As such, this either seems like a bug in Ubuntu, or caused by cloud-
  init when writing e/n/i.d/50-cloud-init.cfg

  ubuntu@manual:~$ dpkg -l | grep cloud-init
  ii  cloud-init   0.7.9-153-g16a7302f-0ubuntu1~16.04.2 
  all  Init scripts for cloud instances
  ii  cloud-initramfs-copymods 0.27ubuntu1.4
  all  copy initramfs modules into root filesystem for later use
  ii  cloud-initramfs-dyn-netconf  0.27ubuntu1.4
  all  write a network interface file in /run for BOOTIF

  ubuntu@manual:~$ uname -a
  Linux manual 4.4.0-92-generic #115-Ubuntu SMP Thu Aug 10 09:04:33 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  ubuntu@manual:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.3 LTS
  Release:16.04
  Codename:   xenial

  ubuntu@manual:~$ pastebinit /var/log/cloud-init.log
  http://paste.ubuntu.com/25342738/
  ubuntu@manual:~$ pastebinit /var/log/cloud-init-output.log
  http://paste.ubuntu.com/25342740/

  Related bugs:
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1713803: replacement of resolvconf with systemd needs integration

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

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

[Touch-packages] [Bug 1722313] Re: [SRU][xenial] Add "--with-audit" config option so that the hwclock command creates an audit record when the hardware clock is altered.

[Joy Latten]

** Bug watch added: Debian Bug tracker #745771
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745771

** Also affects: util-linux (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745771
   Importance: Unknown
   Status: Unknown

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

Title:
  [SRU][xenial] Add "--with-audit" config option so that the hwclock
  command creates an audit record when the hardware clock is altered.

Status in util-linux package in Ubuntu:
  New
Status in util-linux package in Debian:
  Unknown

Bug description:
  [IMPACT]
  There is a requirement for Common Criteria EAL2 certification that changes to 
the system's hardware clock be audited/monitored. In Ubuntu the hwclock command 
can be used to alter the system's hardware clock. Thus this event needs to be 
audited for EAL2. The hwclock command within util-linux has the ability to 
create an audit event when the system's hardware clock is altered, but this 
ability is enabled via the --with-audit config option. This option is currently 
not enabled.

  Only the hwclock and the login commands within util-linux package use
  this --with-audit config option to enable auditing. However, it
  appears the login command is not built nor shipped in util-linux.
  Ubuntu uses the login command from shadow instead. Thus, only hwclock
  command would be affected by this change. The change would enable (1)
  call to audit_open to create a netlink socket descritor. (2) generate
  an audit entry when system hardware clock altered. The entry will be
  logged into the /var/log/audit/audit.log IF auditd is installed and
  running.

  [TEST]

  This has been tested on both P8 and amd64 architectures. With the
  patch all the Common Criteria testcases pass for hwclock. Before this
  patch, the functional part of the testcase passed, but the check for
  the triggered audit records would fail. Attached the Common Criteria
  testcase below.

  Also, the util-linux package has testcases that get run during the
  build. All of these pass. Pointer to build log below.

  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

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

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

[Touch-packages] [Bug 1722564] [NEW] apport question will not accept multi-character responses

[Scott Moser]

Public bug reported:

the newly added cloud-init apport support shows a list of cloud
providers and asks the user to select one.  There are currently 18
options.  For any option > 10, apport will just take the '1' that is
typed as the answer.

It should obviously wait for more than one character or a carriage
return.


*** Please select the cloud vendor or environment in which this instance is 
running


Choices:
  1: Amazon - Ec2
  2: AliYun
  3: AltCloud
  4: Azure
  5: Bigstep
  6: CloudSigma
  7: CloudStack
  8: DigitalOcean
  9: GCE - Google Compute Engine
  10: MAAS
  11: NoCloud
  12: OpenNebula
  13: OpenStack
  14: OVF
  15: Scaleway
  16: SmartOS
  17: VMware
  18: Other
  C: Cancel
Please choose (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/C): 1

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: apport 2.20.7-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
Date: Tue Oct 10 15:21:48 2017
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  apport question will not accept multi-character responses

Status in apport package in Ubuntu:
  New

Bug description:
  the newly added cloud-init apport support shows a list of cloud
  providers and asks the user to select one.  There are currently 18
  options.  For any option > 10, apport will just take the '1' that is
  typed as the answer.

  It should obviously wait for more than one character or a carriage
  return.

  
  *** Please select the cloud vendor or environment in which this instance is 
running

  
  Choices:
1: Amazon - Ec2
2: AliYun
3: AltCloud
4: Azure
5: Bigstep
6: CloudSigma
7: CloudStack
8: DigitalOcean
9: GCE - Google Compute Engine
10: MAAS
11: NoCloud
12: OpenNebula
13: OpenStack
14: OVF
15: Scaleway
16: SmartOS
17: VMware
18: Other
C: Cancel
  Please choose (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/C): 1

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 10 15:21:48 2017
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1719934] Re: Missing fonts in list of languages

[Jeremy Bicha]

Fixed in https://launchpad.net/ubuntu/+source/ubuntu-meta/1.403

(This ended up being a duplicate of LP: #1720809 )

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

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

Title:
  Missing fonts in list of languages

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  There is a font missing on the ISO and one of the language is shown as
  unicode characters (cf screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 27 11:22:24 2017
  InstallationDate: Installed on 2013-09-03 (1484 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

[Scott Moser]

This script runs and demonstrates functional dns.

It launches a guest with a custom kernel command line
pointing to a nocloud datasource running on the host.
It uses user mode networking to seed a dns server and a
dns search.

The 'seedfrom' is done over dns which would not work if this
change were put in place.  To get that to work, you have to add
an entry in /etc/hosts for 10.0.2.2 (suggest 'qemu-host').

There is a PPA available at 
  https://launchpad.net/~smoser/+archive/ubuntu/lp1711760
with the fix in place.


** Attachment added: "lp-1711760-test.sh:  script to aid in testing"
   
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/4966752/+files/lp-1711760-test.sh

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

Title:
  [2.3] resolv.conf is not set (during commissioning or testing)

Status in MAAS:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  In Progress

Bug description:
  Using MAAS 2.3, during commissioning (and likely in the rest of the
  ephemeral environment) we have noticed that resolv.conf is not set
  with the DNS server.

  That said, during the commissioning process, MAAS does not send any
  metadata to cloud-init to configure the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:

  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0

  Which correctly includes the DNS server. However:

  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com

  If restart the interfacE:

  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x5403eb14)
  DHCPOFFER of 192.168.122.195 from 192.168.122.2
  DHCPACK of 192.168.122.195 from 192.168.122.2
  Restarting ntp (via systemctl): ntp.service.
  bound to 192.168.122.195 -- renewal in 290 seconds.

  ubuntu@manual:~$ 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
  nameserver 192.168.122.2
  search maas

  ubuntu@manual:~$ ping google.com
  PING google.com (216.58.192.46) 56(84) bytes of data.
  64 bytes from mia07s46-in-f14.1e100.net (216.58.192.46): icmp_seq=1 ttl=52 
time=7.47 ms
  ^C
  --- google.com ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 7.472/7.472/7.472/0.000 ms

  As such, this either seems like a bug in Ubuntu, or caused by cloud-
  init when writing e/n/i.d/50-cloud-init.cfg

  ubuntu@manual:~$ dpkg -l | grep cloud-init
  ii  cloud-init   0.7.9-153-g16a7302f-0ubuntu1~16.04.2 
  all  Init scripts for cloud instances
  ii  cloud-initramfs-copymods 0.27ubuntu1.4
  all  copy initramfs modules into root filesystem for later use
  ii  cloud-initramfs-dyn-netconf  0.27ubuntu1.4
  all  write a network interface file in /run for BOOTIF

  ubuntu@manual:~$ uname -a
  Linux manual 4.4.0-92-generic #115-Ubuntu SMP Thu Aug 10 09:04:33 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  ubuntu@manual:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.3 LTS
  Release:16.04
  Codename:   xenial

  ubuntu@manual:~$ pastebinit /var/log/cloud-init.log
  http://paste.ubuntu.com/25342738/
  ubuntu@manual:~$ pastebinit /var/log/cloud-init-output.log
  http://paste.ubuntu.com/25342740/

  Related bugs:
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1713803: replacement of resolvconf with systemd needs integration

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

-- 

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[Denis Kalinin]

I've just checked 17.04, and it also looks fine. My guess is that
something has changed in "freetype" when it was updated from 2.6.3 to
2.8.0, so I'm setting "freetype" as the package for this bug.

** Package changed: ubuntu => freetype (Ubuntu)

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

Title:
  Font hinting appears broken on 17.10 beta

Status in freetype package in Ubuntu:
  New

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses. A couple of months ago a similar
  issue was reported (and promptly fixed) in Chromium after they had
  changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  
  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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

[Touch-packages] [Bug 1722508] [NEW] Font hinting appears broken on 17.10 beta

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

It appears that font hinting in 17.10 (beta) doesn't work as expected.
The issue is easy to miss if you have antialiasing enabled system-wise.
However, if you install "gnome-tweak-tool" and disable antialiasing
there, the problem becomes obvious.

Here is how it looks on 17.10 beta:
https://postimg.org/image/3auqsbkqtn/

And here is how it looks on my 16.04 machine (and this is pretty much how it's 
supposed to look):
https://postimg.org/image/85n5ss3l4b/

* When comparing the pictures make sure you "Open image in new tab" and
see them without browser zoom, otherwise the problem may no be obvious.

I suspect that this issue is caused by a bug in some base font rendering
package that Ubuntu uses. A couple of months ago a similar issue was
reported (and promptly fixed) in Chromium after they had changed
something in FreeType rendering
(https://bugs.chromium.org/p/chromium/issues/detail?id=748997).


lsb_release -rd
Description: Ubuntu Artful Aardvark (development branch)
Release: 17.10

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


** Tags: artful bot-comment
-- 
Font hinting appears broken on 17.10 beta
https://bugs.launchpad.net/bugs/1722508
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to freetype in Ubuntu.

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

[Touch-packages] [Bug 1714803] Re: Search list in resolv.conf breaks resolving for that domain

[Matthias Fratz]

Our DHCP server delivers a search domain (inf.uni-konstanz.de) as well.
This isn't enough to trigger the bug for me, though, at least on 17.04.
(systemd-resolve doesn't actually USE the search path, so merkur236.inf
.uni-konstanz.de works but merkur236 doesn't, but that's a different
problem.)

What does trigger the bug on 17.04 is manually configuring a search
path, like it seems the original reporter did:

$ cat /etc/resolvconf/resolv.conf.d/base 
search disy.inf.uni-konstanz.de inf.uni-konstanz.de uni-konstanz.de

At some point this gets copied to /etc/resolv.conf. After a "service
systemd-resolved restart", resolution is broken for those domains until
I remove the search path and restart systemd-resolved again.

I couldn't yet reproduce this on 17.10 because restarting systemd-
resolved overwrites /etc/resolv.conf. Where is the right place to
configure a search path on 17.10? I don't see it anywhere in the GUI and
I'm not sure whether /etc/systemd/resolved.conf is the right place.


I attached the files you suggested from a fresh 17.10 install, with 
"Domains=ubuntu.com" manually added to /etc/systemd/resolved.conf. Adding that 
line (and restarting systemd-resolved) breaks resolving; removing (and 
restarting) restores functionality.

** Attachment added: "resolved.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1714803/+attachment/4966747/+files/resolved.tgz

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

Title:
  Search list in resolv.conf breaks resolving for that domain

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.04
  systemd 232-21ubuntu5

  Adding a domain to the search list in /etc/resolv.conf breaks
  resolving for that domain. Not only does the search list not get used
  as expected, but host names in the domain cannot be resolved by
  systemd-resolved at all.

  I just ran into this after upgrading from ubuntu 16.04 to 17.04 which
  enabled systemd-resolved. I have for a long time used resolveconf to
  add a 'search my-domain'-line to my /etc/resolv.conf.

  
  Example of expected behaviour. With Googles DNS server (8.8.8.8) and 
ubuntu.com in the search list in /etc/resolv.conf. Both dig and systemd-resolve 
can resolve www.ubuntu.com and www:

  $ cat /etc/resolv.conf 
  nameserver 8.8.8.8
  search ubuntu.com
  $ dig +nostat +nocmd www.ubuntu.com
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55037
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 512
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  ;; ANSWER SECTION:
  www.ubuntu.com.   501 IN  A   91.189.89.115
  
  $ dig +search +nostat +nocmd www
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25772
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 512
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  ;; ANSWER SECTION:
  www.ubuntu.com.   382 IN  A   91.189.89.103
  
  $ systemd-resolve www.ubuntu.com
  www.ubuntu.com: 91.189.89.115
  
  -- Information acquired via protocol DNS in 2.7ms.
  -- Data is authenticated: no
  $ systemd-resolve www
  www: 91.189.90.59
   (www.ubuntu.com)
  
  -- Information acquired via protocol DNS in 3.8ms.
  -- Data is authenticated: no

  Ubuntu 17.04 default config, with the systemd-resolved name server in
  /etc/resolv.conf and no search list. www.ubuntu.com can still be
  resolved correctly:

  $ cat /etc/resolv.conf
  nameserver 127.0.0.53
  $ dig +nostat +nocmd www.ubuntu.com
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64646
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  ;; ANSWER SECTION:
  www.ubuntu.com.   482 IN  A   91.189.89.110
  $ systemd-resolve www.ubuntu.com
  www.ubuntu.com: 91.189.90.58
  
  -- Information acquired via protocol DNS in 18.2ms.
  -- Data is authenticated: no

  Broken behaviour, using the systemd-resolved name server and specify
  ubuntu.com in search list. Resolving fails for www.ubuntu.com and www,
  both using dig (DNS) and using sytemd-resolve:

  $ cat /etc/resolv.conf
  nameserver 127.0.0.53
  search ubuntu.com
  $ dig +nostat +nocmd www.ubuntu.com
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 

[Touch-packages] [Bug 1657425] Re: Testsuite failure does not fail the build

[Launchpad Bug Tracker]

This bug was fixed in the package libseccomp - 2.3.1-2.1ubuntu3

---
libseccomp (2.3.1-2.1ubuntu3) artful; urgency=medium

  * debian/rules: Make test failures cause the build to fail (LP:
#1657425)

 -- Tyler Hicks   Fri, 06 Oct 2017 18:08:21 +

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

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

Title:
  Testsuite failure does not fail the build

Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp package in Debian:
  New

Bug description:
  Bug 1450642 states: "seccomp itself has a comprehensive testsuite, and
  while it doesn't fail the build, regressions can be seen by looking at
  the build log."

  Presumably this is a separate bug that needs to be fixed, at least in
  the development release? IMHO bundling a fix in any future SRU should
  be fine, too.

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

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

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Eric Desrochers]

## PENDING SRU / REGRESSION EXPLANATIONS **

All the current systemd (trusty) autopktest failure are not related to the 
current SRU.
Seems like they are failing for a while now and should be considered as known 
test failure already.

Regression in autopkgtest for network-manager (ppc64el): test log
 - Always fails the same way since at least  "systemd/204-5ubuntu20.17" : 
http://autopkgtest.ubuntu.com/packages/n/network-manager/trusty/ppc64el

Regression in autopkgtest for linux-lts-wily (armhf): test log
 - Always timeout the same way since at least  "systemd/204-5ubuntu20.17" : 
http://autopkgtest.ubuntu.com/packages/l/linux-lts-wily/trusty/armhf 

Regression in autopkgtest for linux-lts-vivid (ppc64el): test log
 - ERROR: running version does not match source package

Regression in autopkgtest for linux-lts-vivid (i386): test log
 - ERROR: running version does not match source package

Regression in autopkgtest for linux-lts-vivid (amd64): test log
 - ERROR: running version does not match source package

Regression in autopkgtest for linux-lts-vivid (armhf): test log
 - Always fails the same way since at least  "systemd/204-5ubuntu20.14" : 
http://autopkgtest.ubuntu.com/packages/l/linux-lts-vivid/trusty/armhf

Regression in autopkgtest for linux-lts-utopic (ppc64el): test log
 - ERROR: running version does not match source package

Regression in autopkgtest for linux-lts-utopic (i386): test log
 - ERROR: running version does not match source package

Regression in autopkgtest for linux-lts-utopic (amd64): test log
 - ERROR: running version does not match source package

Regression in autopkgtest for linux-lts-utopic (armhf): test log
 - Always fails the same way since at least "systemd/204-5ubuntu20.15" : 
http://autopkgtest.ubuntu.com/packages/l/linux-lts-utopic/trusty/armhf

Regression in autopkgtest for linux-lts-xenial (ppc64el): test log
 - ERROR: running version does not match source package

Regression in autopkgtest for linux-lts-xenial (i386): test log
 - ERROR: running version does not match source package

Regression in autopkgtest for linux-lts-xenial (amd64): test log
 - ERROR: running version does not match source package

Regression in autopkgtest for linux-lts-xenial (armhf): test log
 - Always fails the same way since "systemd/204-5ubuntu20.19" : 
http://autopkgtest.ubuntu.com/packages/l/linux-lts-xenial/trusty/armhf


** ERROR: running version does not match source package **
Source Package Version: 3.16.0-77.99~14.04.1
Running Kernel Version: 3.13.0-133.182

- Eric

** Description changed:

  [Impact]
  
  Installing snaps is not possible on Ubuntu 14.04 when having /var on its
  own partition, whether its LVM or not.
  
  The issue is with the core snap being unable to mount:
  
  The error with /var isolated and using LVM:
  
  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )
  
  The error with /var isolated but without using LVM:
  
  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service
 failed to load: No such file or directory. See system logs and 'systemctl 
status 
systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service'
 for details.
  )
  
  The same error happens if I try to install the hello-world snap (with
  LVM in this example):
  
  root@ubuntu:~# snap install hello-world
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )
  
  I cannot reproduce the issue in Ubuntu 16.04.
  
  I couldn't reproduce this issue by using the Ubuntu 14.04 cloud image
  which doesn't isolate /var on its own partition. I tried adding a
  secondary disk to that cloud image VM and create a dummy VG and LV, but
  couldn't reproduce the issue.
  
  Also could not reproduce using Ubuntu 14.04 (with LVM or not) but with
  only a / partition and swap.
  
  [Test Case]
  
  # Install Ubuntu 14.04 in KVM (I used the 14.04.4 server iso) and
  configure /, /var and swap on their own partitions (with LVM or not, the
  issue happens in both situations).
  
  root@ubuntu:~# lvs
  LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
  rootvol vg00 -wi-ao--- 

[Touch-packages] [Bug 1714596] Re: PDF images are blank

[Launchpad Bug Tracker]

This bug was fixed in the package poppler - 0.57.0-2ubuntu3

---
poppler (0.57.0-2ubuntu3) artful; urgency=medium

  * debian/rules:
- build with --enable-libopenjpeg=unmaintained which makes the poppler
  openjpeg parser used as it was in Ubuntu until now. Upstream doesn't
  recommend that but the libopenjpeg MIR has still not been approved and
  without a parser some documents are rendered as blank. (lp: #1714596)

 -- Sebastien Bacher   Mon, 09 Oct 2017 19:31:17
+0200

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

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

Title:
  PDF images are blank

Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  1. Download a PDFs with images such as - 
  
http://www.dvrpc.org/Connections2045/pdf/2045_DRAFT_Plan_for_Public_Comment.pdf
  
http://www.hopkinsmedicine.org/human_resources/_docs/employee_handbook_non-union_non-represented.pdf
  http://humanservices.arkansas.gov/dccece/classroom_docs/carseatsafety.pdf

  2. Open in Evince, note how first page is blank

  Open with Firefox and note how it displays a nice intro page.

  Ubuntu 17.04 LiveCD works fine
  Ubuntu 17.10 LiveCD does not

  For Evince Zesty (3.24.0) vs Artful (3.24.1) which might be any easy thing to 
rule out. (I also tried the artful -proposed evince which has the issue too)
  For Poppler Zesty (0.48.0) vs Artful (0.57.0) so my guess is bug is in 
poppler.

  Given my testing in Fedora (C#2) which worked fine with same version
  of poppler and by downgrading the packages I believe this a Ubuntu
  specific poppler bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.24.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Sep  1 17:22:35 2017
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-07-26 (37 days ago)

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

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

[Touch-packages] [Bug 1698967] Re: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed')

[Ayman Sheikh Yasin]

I cant make update for the software and install

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

Title:
  package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package
  bsdutils is not ready for configuration  cannot configure (current
  status 'half-installed')

Status in dpkg package in Ubuntu:
  Invalid
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package
  bsdutils is not ready for configuration  cannot configure (current
  status 'half-installed')

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   bsdutils:amd64: Configure
   axel:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Jun 18 17:43:58 2017
  DpkgTerminalLog:
   dpkg: error processing package bsdutils (--configure):
package bsdutils is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package bsdutils is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-06-15 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package 
bsdutils is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1721839] Re: Services asked for by UDEV do not get triggered

[Launchpad Bug Tracker]

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

Title:
  Services asked for by UDEV do not get triggered

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The packages system-config-printer-udev and ippusbxd are installed,
  having the following UDEV rule files:

  /lib/udev/rules.d/70-printers.rules

  --
  # Low-level USB device add trigger
  ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", 
ENV{ID_USB_INTERFACES}=="*:0701??:*", TAG+="udev-configure-printer", 
TAG+="systemd", PROGRAM="/bin/systemd-escape 
--template=udev-configure-printer@.service %p", ENV{SYSTEMD_WANTS}+="%c"
  # Low-level USB device remove trigger
  ACTION=="remove", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", 
ENV{ID_USB_INTERFACES}=="*:0701*:*", RUN+="udev-configure-printer remove %p"
  --

  /lib/udev/rules.d/55-ippusbxd.rules

  --
  # ippusbxd udev rules file

  ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device" 
ENV{ID_USB_INTERFACES}=="*:070104:*", OWNER="root", GROUP="lp", MODE="0664", 
PROGRAM="/bin/systemd-escape --template=ippusbxd@.service 
$env{BUSNUM}:$env{DEVNUM}", ENV{SYSTEMD_WANTS}+="%c"
  --

  If I turn on an appropriate printer (USB, supporting IPP-over-USB,
  here the HP DeskJet 2540) I get in the output of "udevadm monitor
  --environment"

  --
  UDEV  [17527.514150] add  /devices/pci:00/:00:14.0/usb2/2-2 (usb)
  ACTION=add
  BUSNUM=002
  DEVNAME=/dev/bus/usb/002/033
  DEVNUM=033
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2
  DEVTYPE=usb_device
  DRIVER=usb
  ID_BUS=usb
  ID_MODEL=Deskjet_2540_series
  ID_MODEL_ENC=Deskjet\x202540\x20series
  ID_MODEL_ID=c211
  ID_REVISION=0100
  ID_SERIAL=HP_Deskjet_2540_series_BR54BFB02C05XK
  ID_SERIAL_SHORT=BR54BFB02C05XK
  ID_USB_INTERFACES=:ffcc00:070104:070102:ff0401:
  ID_VENDOR=HP
  ID_VENDOR_ENC=HP
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  ID_VENDOR_ID=03f0
  MAJOR=189
  MINOR=160
  PRODUCT=3f0/c211/100
  SEQNUM=9891
  SUBSYSTEM=usb
  SYSTEMD_WANTS=ippusbxd@002:033.service 
udev-configure-printer@-devices-pci:00-:00:14.0-usb2-2\x2d2.service 
printer.target
  TAGS=:udev-configure-printer:systemd:
  TYPE=0/0/0
  USEC_INITIALIZED=17527513940

  UDEV  [17527.517724] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb)
  .MM_USBIFNUM=00
  ACTION=add
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0
  DEVTYPE=usb_interface
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  INTERFACE=255/204/0
  MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00icFFiscCCip00in00
  PRODUCT=3f0/c211/100
  SEQNUM=9892
  SUBSYSTEM=usb
  TYPE=0/0/0
  USEC_INITIALIZED=17527517478

  UDEV  [17527.522565] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.2 (usb)
  .MM_USBIFNUM=02
  ACTION=add
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.2
  DEVTYPE=usb_interface
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  INTERFACE=255/4/1
  MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00icFFisc04ip01in02
  PRODUCT=3f0/c211/100
  SEQNUM=9895
  SUBSYSTEM=usb
  TYPE=0/0/0
  USEC_INITIALIZED=17527522332

  UDEV  [17527.523761] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1 (usb)
  .MM_USBIFNUM=01
  ACTION=add
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1
  DEVTYPE=usb_interface
  DRIVER=usblp
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  INTERFACE=7/1/2
  MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00ic07isc01ip02in01
  PRODUCT=3f0/c211/100
  SEQNUM=9893
  SUBSYSTEM=usb
  TYPE=0/0/0
  USEC_INITIALIZED=17527523500

  UDEV  [17527.527275] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1/usbmisc/lp1 (usbmisc)
  .MM_USBIFNUM=01
  ACTION=add
  DEVNAME=/dev/usb/lp1
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1/usbmisc/lp1
  MAJOR=180
  MINOR=1
  SEQNUM=9894
  SUBSYSTEM=usbmisc
  USEC_INITIALIZED=17527527175
  --

  Here one can see that the UDEV rules files are correct, leading to the
  correct systemd services being requested

  SYSTEMD_WANTS=ippusbxd@002:033.service udev-configure-printer
  @-devices-pci:00-:00:14.0-usb2-2\x2d2.service printer.target

  but neither the service ippusbxd@002:033.service nor the service udev-
  configure-printer@-devices-pci:00-:00:14.0-usb2-2\x2d2.service
  get started (note that I have put the .service file for ippusbxd in
  place by "sudo cp /usr/share/doc/ippusbxd/examples/ippusbxd@.service
  /lib/systemd/system/").

  I can start each of these services manually though:

  sudo systemctl start 'udev-configure-printer@-devices-
  pci:00-:00:14.0-usb2-2\x2d2.service'

  sudo systemctl start ippusbxd@002:033.service

  In each case ippusbxd gets started for this printer and a print queue
  auto-created.

  What I expect is 

[Touch-packages] [Bug 1722528] [NEW] find buffer-overflow with -printf '%T+'

[Kai Mast]

Public bug reported:

This has already been reported upstream. Just reporting it here because
I observed it in artful.

** Affects: findutils
 Importance: Unknown
 Status: Unknown

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


** Tags: artful

** Bug watch added: GNU Savannah Bug Tracker #51841
   http://savannah.gnu.org/bugs/?51841

** Also affects: findutils via
   http://savannah.gnu.org/bugs/?51841
   Importance: Unknown
   Status: Unknown

** Tags added: artful

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

Title:
   find buffer-overflow with -printf '%T+'

Status in findutils:
  Unknown
Status in findutils package in Ubuntu:
  New

Bug description:
  This has already been reported upstream. Just reporting it here
  because I observed it in artful.

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

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

[Touch-packages] [Bug 1556927] Re: python3 builtin help() fails with exception

[Matthias Klose]

so fixed at least in 16.04 LTS and newer releases

** Changed in: python3-defaults (Ubuntu)
   Status: New => Fix Released

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

Title:
  python3 builtin help() fails with exception

Status in python3-defaults package in Ubuntu:
  Fix Released

Bug description:
  The builtin help() function fails with an exception when called on a
  class that has a data attribute initialized to an object of a class
  which implements __eq__ in a manner that raises an exception when
  comparing to None.

  The attached file, help_bug.py, is a module that illustrates the
  problem.  In an interactive python3 session, importing the module as
  help_bug and then using the command:

help(help_bug)

  will cause help to fail with a TypeError exception raised by the
  __eq__ method of the RestrictedCompare class before any help
  documentation is displayed.

  In this example, it is the attribute named 'restricted' in the HelpBug
  class that is causing the problem, specifically its initialization to
  an object from the RestrictedCompare class.  The command
  help(help_bug.HelpBug) also fails with the exception, although
  help(help_bug.RestrictedCompare) is successful.

  This is a result of a comparison of objects that is not protected by
  try ... except in the classify_class_attrs() function of the standard
  inspect module.  In particular, it is happening at the first
  comparison of:

  srch_obj == get_obj

  when srch_obj is None.

  The help(help_bug) and help(help_bug.HelpBug) calls successfully
  display help documentation in Python 2.7.

  The output of lsb_release -rd is:

  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04

  The package containing the inspect.py file is version
  libpython3.4-minimal 3.4.3-1ubuntu~14.04.3

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

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

[Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Ubuntu Foundations Team Bug Bot]

The attachment "[PATCH] Fix "Message truncated" issue with many VF's"
seems to be a patch.  If it isn't, please remove the "patch" flag from
the attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Confirmed
Status in iproute2 package in CentOS:
  Unknown

Bug description:
  I've ran into an issue when creating a large number of virtual
  functions on a SR-IOV capable device.

  ip link show reports a message truncated error:
  ip link show > /dev/null
  Message truncated
  Message truncated
  Message truncated

  A likely cause might be that when called in a system where the number
  of PCIe Virtual Functions are more than 30 for a given Physical
  Function, the netlink response is larger than 16K, meaning that a
  message is truncated.

  The issue is seen with Ubuntu14.04 and Ubuntu16.04.

  A possible solution for the issue is to increase the size of the
  receive buffer in libnetlink.c

  Additional information:
  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
Installed: 3.12.0-2ubuntu1
Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

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

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

[Touch-packages] [Bug 1722426] Re: Please merge unattended-upgrades 0.98 (main) from Debian unstable (main) Edit

[Francis Ginther]

** Tags added: id-596781a4fd7307546010c061

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

Title:
   Please merge unattended-upgrades 0.98 (main) from Debian unstable
  (main) Edit

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  u-u 0.98 fixes bashism in 0.97ubuntu2'a postinst and fixes hibernation
  handling.

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

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

[Touch-packages] [Bug 1722481] Re: systemd should sync disks, before killing all processes on shutdown

[Francis Ginther]

** Tags added: id-59dba43d6e5b35acb9bbee0b

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

Title:
  systemd should sync disks, before killing all processes on shutdown

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  New

Bug description:
  [Impact]

   * systemd-shutdown binary is executed to complete system shutdown. In
  xenial, it calls sync() after killing all processes, and not before
  killing them. This means that processes are racing the SIGKILL/TERM
  timeouts to sync all IO to disk. To mitigate this race condition, and
  make the shutdown process more reliable the sync() should also happen
  before process killing spree starts.

  [Fix]
  Backport upstream commit 
https://github.com/systemd/systemd/commit/2e79d1828a8da9b3af1b052297e3617905ec94f3

  
  [Test Case]

   * Make sure systems still shuts down, including e.g. root on raid.

  [Regression Potential]

   * Shutdowns may appear to be slower due to two sync() calls instead of one
   * However total shutdown time should not be impacted much, as there really 
should not be much additional IO caused by killing all processes.

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

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

[Touch-packages] [Bug 1722151] Re: Incorrect syntax when writing to ~/.pam_environment

[Launchpad Bug Tracker]

This bug was fixed in the package accountsservice - 0.6.42-0ubuntu3

---
accountsservice (0.6.42-0ubuntu3) artful; urgency=medium

  * debian/patches/0009-language-tools.patch:
- Use correct syntax when writing to ~/.pam_environment
  (LP: #1722151).

 -- Gunnar Hjalmarsson   Mon, 09 Oct 2017 23:08:00
+0200

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

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

Title:
  Incorrect syntax when writing to ~/.pam_environment

Status in accountsservice package in Ubuntu:
  Fix Released

Bug description:
  While investigating bug #1662031, I found out that /usr/share
  /language-tools/save-to-pam-env writes to ~/.pam_environment using an
  incorrect syntax: "VARIABLE=value" on each line. The expected syntax
  is "VARIABLE [DEFAULT=[value]] [OVERRIDE=[value]]" (man pam_env.conf).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: accountsservice 0.6.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 06:57:17 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (463 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: accountsservice
  UpgradeStatus: Upgraded to artful on 2017-06-04 (126 days ago)

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

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

[Touch-packages] [Bug 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by lo

[Dik]

It seems to be the right way.


On the other side, one could check the dmesg log on the presence of kernel 
warning about probably firmware fails, but it's a wrong concept I think.

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

Title:
  [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945
  :03:00.0: BSM uCode verification failed at addr ...; wlan0:
  deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING),

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
  WICD on-the-fly enables to continue browsing without rebooting, so it
  seems to be no hardware issue or iwl3945 issue.

  What to expect: stable connections and flawless network managing.
  What happens: so above.

  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.

  Interesting, according to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  apt-cache policy network-manager
  network-manager:
    Installiert:   0.9.8.8-0ubuntu28
    Installationskandidat: 0.9.8.8-0ubuntu28
    Versionstabelle:
   *** 0.9.8.8-0ubuntu28 0
  500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1629123] Re: multiprocessing.Pool fails

[Dmitry Shachnev]

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

** This bug has been marked a duplicate of bug 1628763
   Example of Queue from documentation fails

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

Title:
  multiprocessing.Pool fails

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  Trying the examples from
  
https://docs.python.org/3.5/library/multiprocessing.html#exchanging-objects-between-processes

  
  the example for Pool fails.  It's attached.  The error implicates something 
missing in SimpleQueue
  $ python3 Pool.py 
  Traceback (most recent call last):
File "Pool.py", line 13, in 
  with Pool(5) as p:
File "/usr/lib/python3.5/multiprocessing/context.py", line 118, in Pool
  context=self.get_context())
File "/usr/lib/python3.5/multiprocessing/pool.py", line 150, in __init__
  self._setup_queues()
File "/usr/lib/python3.5/multiprocessing/pool.py", line 243, in 
_setup_queues
  self._inqueue = self._ctx.SimpleQueue()
File "/usr/lib/python3.5/multiprocessing/context.py", line 110, in 
SimpleQueue
  from .queues import SimpleQueue
File "/usr/lib/python3.5/multiprocessing/queues.py", line 20, in 
  from queue import Empty, Full

  This also fails in the default 2.7 python, with a simpler (less
  informative) error message.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: python3-minimal 3.5.1-3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep 29 15:04:55 2016
  InstallationDate: Installed on 2016-08-08 (52 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1712433] Re: man page typo

[Liam Ryan]

Upstream pull request has been merged and will be available in next
release

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

Title:
  man page typo

Status in util-linux package in Ubuntu:
  Fix Committed

Bug description:
  man mount contains the following section:

  Note  that mount is very strict about non-root users and all paths specified 
on command line are verified before fstab is
     parsed or a helper program is executed. It's strogly recommended to 
use a valid mountpoint to specify filesystem,  other‐
     wise mount may fail. For example it's bad idea to use NFS or CIFS 
source on command line.

  The word 'strogly' should be 'strongly'

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: mount 2.29-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Wed Aug 23 07:48:32 2017
  InstallationDate: Installed on 2017-03-23 (152 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to zesty on 2017-08-13 (9 days ago)

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

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

[Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Jan Gutter]

This fix has been pulled into CentOS 7.3 and later

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Confirmed
Status in iproute2 package in CentOS:
  Unknown

Bug description:
  I've ran into an issue when creating a large number of virtual
  functions on a SR-IOV capable device.

  ip link show reports a message truncated error:
  ip link show > /dev/null
  Message truncated
  Message truncated
  Message truncated

  A likely cause might be that when called in a system where the number
  of PCIe Virtual Functions are more than 30 for a given Physical
  Function, the netlink response is larger than 16K, meaning that a
  message is truncated.

  The issue is seen with Ubuntu14.04 and Ubuntu16.04.

  A possible solution for the issue is to increase the size of the
  receive buffer in libnetlink.c

  Additional information:
  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
Installed: 3.12.0-2ubuntu1
Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

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

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

[Touch-packages] [Bug 1702459] Re: Failed to send request: 'str' object has no attribute 'decode' on Ubuntu 16.04

[Serhiy Storchaka]

It would be helpful if you provide a traceback. Just remove try/except
or insert raise before print.

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

Title:
  Failed to send request: 'str' object has no attribute 'decode' on
  Ubuntu 16.04

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  The code attached below generates an error on Ubuntu 16.04 LTS with
  python3 default package installed (python3 --version returns 3.5.2).

  The error message is:
  «Failed to send request: 'str' object has no attribute 'decode'»

  The code works fine on Ubuntu 17.04 and Fedora 25 (both python3 --version 
returning 3.5.3). The code also runs on Ubuntu 16.04 LTS with self-compiled 
from source python 3.6.1.
  Also, the code has been running ok for over a year on Ubuntu 16.04 LTS - it 
only fails since mid June 2017.
  Not sure where the issue is, probably in Ubuntu package for python or in 
python version 3.5.2.

  from datetime import datetime,date,time,timezone
  import tweepy as twitter

  
  def sendToTwitter():
  consumer_key='...'
  consumer_secret='...'
  access_token_key='...'
  access_token_secret='..'
  #connect to the twitter api
  message = "tweet test"
  print("trying to send the tweet...")
  try:
  auth = twitter.OAuthHandler(consumer_key, consumer_secret)
  auth.set_access_token(access_token_key, access_token_secret)
  api = twitter.API(auth)
  status = api.update_status(status=message)
  print("tweet sent")
  except Exception as e:
  print("error while tweeting. reason : " + str(e))
  return
  sendToTwitter()

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

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

[Touch-packages] [Bug 1671952] Re: python program gets segmentation fault

[Serhiy Storchaka]

Please file a bug on the Python bug tracker (https://bugs.python.org/)
and provide a minimal script that reproduces a crash.

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

Title:
  python program gets segmentation fault

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  Running a Python 3 / sqlite3 script that develops a database
  representing a game tree, a segmentation fault occurred.

  The program had written 4,910,495 lines of output when it crashed, redirected 
to a file.  It
  appears normal, and its size is about right for the job being performed.  
There's nothing
  suspicious at the end.

  This is a hobby project, so I can share the entire database and any of the 
code you need, but much of it is included in the screen-scraped console session 
attached herewith.  In particular:
  - the command-line
  - a gdb stack backtrace of the core dump
  - the program being run
  - a run of the sqlite3 "pragma integrity_check" that shows the database is 
sound
  - database .schema output

  CPU is Core i-7, 32 GB RAM.  
  Code is recursive, but limited by the nature of the problem and parameters to 
depth of about 10 calls.  Code has been used before, albeit on a problem with 
smaller recursive depth and shorter
  expected run-time. 
  db is 18GB on a 12TB RAID partition; plenty of space
  kernel is X86-64 4.4.0-66-generic un-fooled-around-with
  Python and the sqlite3 package is 3.5.2, straight from the repositories

  I have a backup of the database right after this crash (being
  performed as I write this)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: python3 3.5.1-3
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 10 13:47:54 2017
  InstallationDate: Installed on 2016-08-08 (214 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Jan Gutter]

This bug has already been fixed upstream in the following commit:

https://anonscm.debian.org/git/collab-maint/pkg-
iproute.git/commit/?id=72b365e8e0fd5efe1d5c05d04c25950736635cfb


This commit happened between: tags debian/4.3.0-1 and debian/4.6.0-1

** Bug watch added: Red Hat Bugzilla #1380803
   https://bugzilla.redhat.com/show_bug.cgi?id=1380803

** Also affects: iproute2 (CentOS) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1380803
   Importance: Unknown
   Status: Unknown

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Confirmed
Status in iproute2 package in CentOS:
  Unknown

Bug description:
  I've ran into an issue when creating a large number of virtual
  functions on a SR-IOV capable device.

  ip link show reports a message truncated error:
  ip link show > /dev/null
  Message truncated
  Message truncated
  Message truncated

  A likely cause might be that when called in a system where the number
  of PCIe Virtual Functions are more than 30 for a given Physical
  Function, the netlink response is larger than 16K, meaning that a
  message is truncated.

  The issue is seen with Ubuntu14.04 and Ubuntu16.04.

  A possible solution for the issue is to increase the size of the
  receive buffer in libnetlink.c

  Additional information:
  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
Installed: 3.12.0-2ubuntu1
Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

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

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

[Touch-packages] [Bug 1628763] Re: Example of Queue from documentation fails

[Serhiy Storchaka]

This looks like there is a queue.py file in the current directory which
hides the queue module from the stdlib. In Python 2.7 this module is
named Queue and doesn't conflict with a local file queue.py.

Can you confirm Kevin?

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

Title:
  Example of Queue from documentation fails

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  Reading https://docs.python.org/3.5/library/multiprocessing.html
  #exchanging-objects-between-processes, I have copy-pasted the code
  into a file.  Running it with python3 fails thus:

  Traceback (most recent call last):
File "q.py", line 7, in 
  q = Queue()
File "/usr/lib/python3.5/multiprocessing/context.py", line 100, in Queue
  from .queues import Queue
File "/usr/lib/python3.5/multiprocessing/queues.py", line 20, in 
  from queue import Empty, Full
  ImportError: cannot import name 'Empty'

  
  I will attach the actual code file.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: python3 3.5.1-3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Sep 28 20:54:17 2016
  InstallationDate: Installed on 2016-08-08 (51 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1629123] Re: multiprocessing.Pool fails

[Serhiy Storchaka]

This is a duplicate of bug #628763.

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

Title:
  multiprocessing.Pool fails

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  Trying the examples from
  
https://docs.python.org/3.5/library/multiprocessing.html#exchanging-objects-between-processes

  
  the example for Pool fails.  It's attached.  The error implicates something 
missing in SimpleQueue
  $ python3 Pool.py 
  Traceback (most recent call last):
File "Pool.py", line 13, in 
  with Pool(5) as p:
File "/usr/lib/python3.5/multiprocessing/context.py", line 118, in Pool
  context=self.get_context())
File "/usr/lib/python3.5/multiprocessing/pool.py", line 150, in __init__
  self._setup_queues()
File "/usr/lib/python3.5/multiprocessing/pool.py", line 243, in 
_setup_queues
  self._inqueue = self._ctx.SimpleQueue()
File "/usr/lib/python3.5/multiprocessing/context.py", line 110, in 
SimpleQueue
  from .queues import SimpleQueue
File "/usr/lib/python3.5/multiprocessing/queues.py", line 20, in 
  from queue import Empty, Full

  This also fails in the default 2.7 python, with a simpler (less
  informative) error message.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: python3-minimal 3.5.1-3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep 29 15:04:55 2016
  InstallationDate: Installed on 2016-08-08 (52 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by lo

[Kai-Heng Feng]

Hmm, so we probably should default to disable power save on iwlegacy,
and add an extra knob to force enabling power save?

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

Title:
  [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945
  :03:00.0: BSM uCode verification failed at addr ...; wlan0:
  deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING),

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
  WICD on-the-fly enables to continue browsing without rebooting, so it
  seems to be no hardware issue or iwl3945 issue.

  What to expect: stable connections and flawless network managing.
  What happens: so above.

  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.

  Interesting, according to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  apt-cache policy network-manager
  network-manager:
    Installiert:   0.9.8.8-0ubuntu28
    Installationskandidat: 0.9.8.8-0ubuntu28
    Versionstabelle:
   *** 0.9.8.8-0ubuntu28 0
  500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1556927] Re: python3 builtin help() fails with exception

[Serhiy Storchaka]

This is fixed in version 3.4.4 in mainstream
(https://bugs.python.org/issue23898).

** Bug watch added: Python Roundup #23898
   http://bugs.python.org/issue23898

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

Title:
  python3 builtin help() fails with exception

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  The builtin help() function fails with an exception when called on a
  class that has a data attribute initialized to an object of a class
  which implements __eq__ in a manner that raises an exception when
  comparing to None.

  The attached file, help_bug.py, is a module that illustrates the
  problem.  In an interactive python3 session, importing the module as
  help_bug and then using the command:

help(help_bug)

  will cause help to fail with a TypeError exception raised by the
  __eq__ method of the RestrictedCompare class before any help
  documentation is displayed.

  In this example, it is the attribute named 'restricted' in the HelpBug
  class that is causing the problem, specifically its initialization to
  an object from the RestrictedCompare class.  The command
  help(help_bug.HelpBug) also fails with the exception, although
  help(help_bug.RestrictedCompare) is successful.

  This is a result of a comparison of objects that is not protected by
  try ... except in the classify_class_attrs() function of the standard
  inspect module.  In particular, it is happening at the first
  comparison of:

  srch_obj == get_obj

  when srch_obj is None.

  The help(help_bug) and help(help_bug.HelpBug) calls successfully
  display help documentation in Python 2.7.

  The output of lsb_release -rd is:

  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04

  The package containing the inspect.py file is version
  libpython3.4-minimal 3.4.3-1ubuntu~14.04.3

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

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

[Touch-packages] [Bug 1722504] [NEW] HP Probook 4515s

[Pertti Ahvonen]

Public bug reported:

Update Problems

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-129.178-generic 3.13.11-ckt39
Uname: Linux 3.13.0-129-generic i686
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Oct 10 13:43:06 2017
DistUpgraded: 2017-07-09 14:18:03,311 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS780M [Mobility Radeon HD 3200] 
[1002:9612] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:3077]
InstallationDate: Installed on 2017-03-06 (217 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
MachineType: Hewlett-Packard HP ProBook 4515s
ProcEnviron:
 LANGUAGE=fi
 PATH=(custom, no user)
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-129-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=sync vesafb.invalid=1 
plymouth:debug nopat drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2017-07-09 (92 days ago)
dmi.bios.date: 06/17/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68GPI Ver. F.06
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3077
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 25.0C
dmi.chassis.asset.tag: CNU9320V0W
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68GPIVer.F.06:bd06/17/2009:svnHewlett-Packard:pnHPProBook4515s:pvrF.06:rvnHewlett-Packard:rn3077:rvrKBCVersion25.0C:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 4515s
dmi.product.version: F.06
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
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.9
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: Tue Oct 10 03:19:50 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.9
xserver.video_driver: radeon

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


** Tags: apport-bug compiz-0.9 i386 third-party-packages trusty ubuntu

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

Title:
  HP Probook 4515s

Status in xorg package in Ubuntu:
  New

Bug description:
  Update Problems

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-129.178-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-129-generic i686
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Oct 10 13:43:06 2017
  DistUpgraded: 2017-07-09 14:18:03,311 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780M [Mobility Radeon HD 3200] 
[1002:9612] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:3077]
  InstallationDate: Installed on 2017-03-06 (217 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: Hewlett-Packard HP ProBook 4515s
  ProcEnviron:
   LANGUAGE=fi
   PATH=(custom, no user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-129-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=sync vesafb.invalid=1 
plymouth:debug nopat drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2017-07-09 (92 days ago)
  dmi.bios.date: 06/17/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68GPI Ver. F.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3077
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 25.0C
  dmi.chassis.asset.tag: CNU9320V0W
  dmi.chassis.type: 10
  dmi.chassis.vendor: 

[Touch-packages] [Bug 1722426] Re: Please merge unattended-upgrades 0.98 (main) from Debian unstable (main) Edit

[Balint Reczey]

Autopkgtest passed on my system:
...
autopkgtest [11:51:12]: test test-systemd.py: [---
bash: line 1:  5437 Killed  
/tmp/autopkgtest.lIv7Of/build.fbn/unattended-upgrades-0.98ubuntu1/debian/tests/test-systemd.py
 2> >(tee -a /tmp/autopkgtest.lIv7Of/test-systemd.py-stderr >&2) > >(tee -a 
/tmp/autopkgtest.lIv7Of/test-systemd.py-stdout)
autopkgtest [11:51:13]: test process requested reboot with marker 
InstallOnShutdown
autopkgtest [11:51:44]: test test-systemd.py: ---]
test-systemd.py  PASS
autopkgtest [11:51:45]: test test-systemd.py:  - - - - - - - - - - results - - 
- - - - - - - -
autopkgtest [11:51:46]:  summary
run-testsPASS
test-systemd.py  PASS
qemu-system-x86_64: terminating on signal 15 from pid 11553 (/usr/bin/python3)

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

Title:
   Please merge unattended-upgrades 0.98 (main) from Debian unstable
  (main) Edit

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  u-u 0.98 fixes bashism in 0.97ubuntu2'a postinst and fixes hibernation
  handling.

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

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

[Touch-packages] [Bug 1720754] Re: rhythmbox doesn't show up headerbar in ubuntu session

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-session - 3.26.1-0ubuntu1

---
gnome-session (3.26.1-0ubuntu1) artful; urgency=medium

  [ Marco Trevisan ]
  * Remove scale factor reset in migration script as now handled in the unity
settings package and only impact people migrating with unity installed
(LP: #1721082)

  [ Didier Roche ]
  * New upstream release
  * debian/unity-gnome-shell-migration.17.10.py:
- reset the rhythmbox plugins key and rename the migration script for
  people who installed pre-alpha getting the glib fix where some
  applications weren't supporting the per session override.
  (LP: #1720754)
- rename it so that can applies to upgraders (the script is idempotent)

 -- Didier Roche   Mon, 09 Oct 2017 12:23:49 +0200

** Changed in: gnome-session (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  rhythmbox doesn't show up headerbar in ubuntu session

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in gnome-session package in Ubuntu:
  Fix Released

Bug description:
  No headerbar plugin extension enabled despite for it being the default
  in rhythmbox. This is due to the per-session override not working for
  the way rhythmbox access the value.

  We need to reset it as well for people who already installed the beta
  or before and upgrading.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1720754/+subscriptions

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

[Touch-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low

[Daniel van Vugt]

Now looking into issue 3 from comment #11 again.

Every time the big stutter occurs it coincides with my PC's harddisk
LED. Also, the same place in the video seems to be the first time the
stream bitrate peaks over 10Mbps. So there seems to be some kind of
cause and effect at this particularly detailed part of the video.

The stutter only occurs in totem though. No other gstreamer tool seems
to exhibit the problem when playing the same video. Even using "gst-
launch-1.0 playbin uri=file:///" seems to not have the  problem. So
all evidence at the moment is suggesting the biggest stutter is somehow
specific to the totem binary, and not gstreamer in general.

I've also just noticed a 5th source of stuttering; that is using
clutterautovideosink in an X11 session. Will ignore that problem for
now...


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

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

Title:
  Totem pauses and stutters during video playback even when CPU usage is
  low

Status in GTK+:
  Confirmed
Status in Totem:
  Incomplete
Status in clutter-1.0 package in Ubuntu:
  Won't Fix
Status in clutter-gtk package in Ubuntu:
  In Progress
Status in gstreamer package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in totem package in Ubuntu:
  In Progress

Bug description:
  Totem pauses and stutters during video playback even when CPU usage is
  low.

  After figuring out how to play videos with full hardware accelerated
  decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
  and stutters during playback. Other apps like Mplayer, VLC and even
  gst-play-1.0 never have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:03:18 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1722426] Re: Please merge unattended-upgrades 0.98 (main) from Debian unstable (main) Edit

[Balint Reczey]

Interestingly autopkgtest ran with 0.97ubuntu2. Investigating while running 
test on my machine.
Tests are passing in Debian: 
https://ci.debian.net/packages/u/unattended-upgrades/unstable/amd64/

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

Title:
   Please merge unattended-upgrades 0.98 (main) from Debian unstable
  (main) Edit

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  u-u 0.98 fixes bashism in 0.97ubuntu2'a postinst and fixes hibernation
  handling.

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

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

[Touch-packages] [Bug 1720754] Re: rhythmbox doesn't show up headerbar in ubuntu session

[Didier Roche]

** Changed in: glib2.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: gnome-session (Ubuntu)
   Status: New => Fix Committed

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

Title:
  rhythmbox doesn't show up headerbar in ubuntu session

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in gnome-session package in Ubuntu:
  Fix Committed

Bug description:
  No headerbar plugin extension enabled despite for it being the default
  in rhythmbox. This is due to the per-session override not working for
  the way rhythmbox access the value.

  We need to reset it as well for people who already installed the beta
  or before and upgrading.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1720754/+subscriptions

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

[Touch-packages] [Bug 1722426] Re: Please merge unattended-upgrades 0.98 (main) from Debian unstable (main) Edit

[Balint Reczey]

I uploaded the updated package here:
https://launchpad.net/~rbalint/+archive/ubuntu/scratch

The autopkgtests also pass:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-rbalint-scratch/artful/amd64/u/unattended-upgrades/20171010_020547_b7480@/log.gz

** 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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1722426

Title:
   Please merge unattended-upgrades 0.98 (main) from Debian unstable
  (main) Edit

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  u-u 0.98 fixes bashism in 0.97ubuntu2'a postinst and fixes hibernation
  handling.

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

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

[Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Jan Gutter]

I'm unfamiliar with where to submit the fix for this bug. Am I
submitting the fix to the wrong forum?

** Patch added: "[PATCH] Fix "Message truncated" issue with many VF's"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+attachment/4966551/+files/iproute2-fix-netlink-overflow.patch

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Confirmed

Bug description:
  I've ran into an issue when creating a large number of virtual
  functions on a SR-IOV capable device.

  ip link show reports a message truncated error:
  ip link show > /dev/null
  Message truncated
  Message truncated
  Message truncated

  A likely cause might be that when called in a system where the number
  of PCIe Virtual Functions are more than 30 for a given Physical
  Function, the netlink response is larger than 16K, meaning that a
  message is truncated.

  The issue is seen with Ubuntu14.04 and Ubuntu16.04.

  A possible solution for the issue is to increase the size of the
  receive buffer in libnetlink.c

  Additional information:
  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
Installed: 3.12.0-2ubuntu1
Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

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

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

[Touch-packages] [Bug 1722483] Re: package libpangoxft-1.0-0:i386 1.38.1-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurat

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libpangoxft-1.0-0:i386 1.38.1-1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in pango1.0 package in Ubuntu:
  New

Bug description:
  Every time I try to install something, the whole procedure fails because of 
this package. I unsuccesfully tried to reinstall or fix it. What am I supposed 
to do?
  I am using Ubuntu 16.04.1 LTS.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpangoxft-1.0-0:i386 1.38.1-1
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Oct 10 10:42:24 2017
  DuplicateSignature:
   package:libpangoxft-1.0-0:i386:1.38.1-1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libpangoxft-1.0-0:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-09-24 (380 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: pango1.0
  Title: package libpangoxft-1.0-0:i386 1.38.1-1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1722483/+subscriptions

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

[Touch-packages] [Bug 1722483] [NEW] package libpangoxft-1.0-0:i386 1.38.1-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configur

[Melania Ghelli]

Public bug reported:

Every time I try to install something, the whole procedure fails because of 
this package. I unsuccesfully tried to reinstall or fix it. What am I supposed 
to do?
I am using Ubuntu 16.04.1 LTS.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpangoxft-1.0-0:i386 1.38.1-1
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Oct 10 10:42:24 2017
DuplicateSignature:
 package:libpangoxft-1.0-0:i386:1.38.1-1
 Processing triggers for man-db (2.7.5-1) ...
 dpkg: error processing package libpangoxft-1.0-0:i386 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2016-09-24 (380 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: pango1.0
Title: package libpangoxft-1.0-0:i386 1.38.1-1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pango1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package libpangoxft-1.0-0:i386 1.38.1-1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in pango1.0 package in Ubuntu:
  New

Bug description:
  Every time I try to install something, the whole procedure fails because of 
this package. I unsuccesfully tried to reinstall or fix it. What am I supposed 
to do?
  I am using Ubuntu 16.04.1 LTS.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpangoxft-1.0-0:i386 1.38.1-1
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Oct 10 10:42:24 2017
  DuplicateSignature:
   package:libpangoxft-1.0-0:i386:1.38.1-1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libpangoxft-1.0-0:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-09-24 (380 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: pango1.0
  Title: package libpangoxft-1.0-0:i386 1.38.1-1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1722483/+subscriptions

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

[Touch-packages] [Bug 1722397] Re: idle doesn't run in 17.10

[dino99]

Should be fixed now:

python3-defaults (3.6.3-0ubuntu2) artful; urgency=medium

  * Fix idle script. LP: #1721852.

 -- Matthias Klose   Tue, 10 Oct 2017 08:00:04 +0200

** Changed in: python3-defaults (Ubuntu)
   Status: New => Incomplete

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

Title:
  idle doesn't run in 17.10

Status in python3-defaults package in Ubuntu:
  Incomplete

Bug description:
  In 17.10 the idle package (v. 3.6.3-0ubuntu1) depends on Python 3.6.
  But the /usr/bin/idle script contains the code that doesn't work in
  Python 3.6.

  $ idle
  Traceback (most recent call last):
File "/usr/bin/idle", line 3, in 
  from idlelib.PyShell import main
  ModuleNotFoundError: No module named 'idlelib.PyShell'

  In Python 3.6 the PyShell module was renamed to pyshell (see
  https://bugs.python.org/issue24225).

  /usr/bin/idle-python3.6 from the idle-python3.6 package works
  correctly.

  Maybe make /usr/bin/idle just a link to /usr/bin/idle-python3.6?

  If you want /usr/bin/idle always run the default python3 and don't
  depent of future changes in the idlelib Python package, you can make
  it a shell script:

  #! /bin/sh
  exec /usr/bin/python3 -m idlelib

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

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

[Touch-packages] [Bug 1722481] [NEW] systemd should sync disks, before killing all processes on shutdown

[Dimitri John Ledkov]

Public bug reported:

[Impact]

 * systemd-shutdown binary is executed to complete system shutdown. In
xenial, it calls sync() after killing all processes, and not before
killing them. This means that processes are racing the SIGKILL/TERM
timeouts to sync all IO to disk. To mitigate this race condition, and
make the shutdown process more reliable the sync() should also happen
before process killing spree starts.

[Fix]
Backport upstream commit 
https://github.com/systemd/systemd/commit/2e79d1828a8da9b3af1b052297e3617905ec94f3


[Test Case]

 * Make sure systems still shuts down, including e.g. root on raid.

[Regression Potential]

 * Shutdowns may appear to be slower due to two sync() calls instead of one
 * However total shutdown time should not be impacted much, as there really 
should not be much additional IO caused by killing all processes.

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

** Affects: systemd (Ubuntu Xenial)
 Importance: Undecided
 Status: New

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

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

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

Title:
  systemd should sync disks, before killing all processes on shutdown

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  New

Bug description:
  [Impact]

   * systemd-shutdown binary is executed to complete system shutdown. In
  xenial, it calls sync() after killing all processes, and not before
  killing them. This means that processes are racing the SIGKILL/TERM
  timeouts to sync all IO to disk. To mitigate this race condition, and
  make the shutdown process more reliable the sync() should also happen
  before process killing spree starts.

  [Fix]
  Backport upstream commit 
https://github.com/systemd/systemd/commit/2e79d1828a8da9b3af1b052297e3617905ec94f3

  
  [Test Case]

   * Make sure systems still shuts down, including e.g. root on raid.

  [Regression Potential]

   * Shutdowns may appear to be slower due to two sync() calls instead of one
   * However total shutdown time should not be impacted much, as there really 
should not be much additional IO caused by killing all processes.

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

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

[Touch-packages] [Bug 1709708] Re: Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but produces no sound on NUC6CAYH

[Daniel van Vugt]

Ironically, the first information we would ask for is for someone to
test 17.10:

  http://cdimages.ubuntu.com/daily-live/current/

and tell us if it fixes the issue :)

Also we would ask someone who experiences the problem to test a
different brand of TV other than Samsung.

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

Title:
  Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but
  produces no sound on NUC6CAYH

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Upon bootup, the HDMI output connected to a Samsung TV shows up as an
  output. If this output is selected and a sound test run (either using
  the GUI or using aplay /user/share/sounds/alsa/Front_Center.wav) no
  sound is heard. Pavumeter does however show sound coming through.

  I found that sound can be fixed by allowing the display to sleep,
  waking it up, and then restarting pulseaudio (pulseaudio -k). After
  that sound output through HDMI to the TV will work until rebooted.

  The fix can be succesfully scripted as follows:

  xset dpms force off
  sleep 1
  pulseaudio -k

  The machine is an Intel NUC6CAYH, connected to a not particularly new
  Samsung 42" TV using an HDMI cable, running a fresh install of Ubuntu
  16.04.

  In earlier attempts at fixing the issue I set pulseaudio to never let
  the sound device sleep (commented out load-module module-suspend-on-
  idle in /etc/pulse/default.pa), and also set the default sampling rate
  to 48000 (default-sample-rate = 48000 in /etc/pulse/daemon.conf). Not
  sure if these settings contributed to the fix, but they are not
  sufficient on their own.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Aug  9 21:48:39 2017
  InstallationDate: Installed on 2017-08-06 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Title: [, Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio fails to detect 
card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0029.2016.1124.1625:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-402:cvn:ct3:cvr:
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-08-06T22:55:35.510382
  mtime.conffile..etc.pulse.default.pa: 2017-08-06T22:51:49.639085

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

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

[Touch-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low

[Daniel van Vugt]

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

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

Title:
  Totem pauses and stutters during video playback even when CPU usage is
  low

Status in GTK+:
  Confirmed
Status in Totem:
  Incomplete
Status in clutter-1.0 package in Ubuntu:
  Won't Fix
Status in clutter-gtk package in Ubuntu:
  In Progress
Status in gstreamer package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in totem package in Ubuntu:
  Fix Released

Bug description:
  Totem pauses and stutters during video playback even when CPU usage is
  low.

  After figuring out how to play videos with full hardware accelerated
  decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
  and stutters during playback. Other apps like Mplayer, VLC and even
  gst-play-1.0 never have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:03:18 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1714933] Re: Xenial: Please roll SRU with upstream fix for networkd to "accept colons in network interface names"

[Dimitri John Ledkov]

With 232-21ubuntu5

Oct 10 08:04:08 darling-stud systemd-networkd[401]:
[/run/systemd/network/10-netplan-eth0.network:12] Interface label is not
valid or too long, ignoring assignment: xo:xo

With 232-21ubuntu7
inet 10.0.0.1/8 brd 10.255.255.255 scope global xo:xo -> got assigned with 
correct label.

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

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

Title:
  Xenial: Please roll SRU with upstream fix for networkd to "accept
  colons in network interface names"

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  networkd cannot manage interface names with ':' in them. As used commonly, by 
convention, by other tools.

  [Fix]
  Update networkd validation routines and test-suites to accept network 
interface names with ':' in it.

  [Testcase]
  Create an inteface with ':' in its name and use it anywhere where systemd 
validates ifname. E.g. Socket BindToDevice definition, nspawn network zone 
info, Label= in [Address] section in networkd.

  [Regression Potential]
  This fix will change validation routines, and thus commands or settings that 
were previously rejected or ignored will now take effect. Specifically Label= 
settings in networkd may lead to networking conflicts. The justification for 
this change is that networkd should really use the sensible ':' ifnames that 
the user is requesting systemd to use.

  [Original Bug Reprot]
  PR: https://github.com/systemd/systemd/pull/5117

  issue: https://github.com/systemd/systemd/issues/4057

  Before the networkd from 231 was backported, it was possible to use
  interface alias names that contained a colon, e.g. eth0:1. This is
  commonly used to make legacy tools like "ifconfig" work, because they
  *expect* a colon in the interface name.

  Martin told me to file a bug for this.

  Merging networkd from 231 lead to a regression where valid configs
  were not accepted anymore after the backport. Please merge that fix
  for the regression.

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

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

[Touch-packages] [Bug 1709708] Re: Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but produces no sound on NUC6CAYH

[Adam Kwarciak]

Dear Community,

I can confirm that the same thing happens for ASRock ITX motherboard
with Intel's J4205 CPU connected to Samsung TV.

Since I want to give Linux a go and not buy another OS from M$ - it is a
bit disappointing that we have to use tricks to get a pretty basic thing
to work.

Does anyone knows if this issue will be fixed in 17.10?

Is there an information I could provide to make it easier to fix the
issue?

BR
Adam

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

Title:
  Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but
  produces no sound on NUC6CAYH

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Upon bootup, the HDMI output connected to a Samsung TV shows up as an
  output. If this output is selected and a sound test run (either using
  the GUI or using aplay /user/share/sounds/alsa/Front_Center.wav) no
  sound is heard. Pavumeter does however show sound coming through.

  I found that sound can be fixed by allowing the display to sleep,
  waking it up, and then restarting pulseaudio (pulseaudio -k). After
  that sound output through HDMI to the TV will work until rebooted.

  The fix can be succesfully scripted as follows:

  xset dpms force off
  sleep 1
  pulseaudio -k

  The machine is an Intel NUC6CAYH, connected to a not particularly new
  Samsung 42" TV using an HDMI cable, running a fresh install of Ubuntu
  16.04.

  In earlier attempts at fixing the issue I set pulseaudio to never let
  the sound device sleep (commented out load-module module-suspend-on-
  idle in /etc/pulse/default.pa), and also set the default sampling rate
  to 48000 (default-sample-rate = 48000 in /etc/pulse/daemon.conf). Not
  sure if these settings contributed to the fix, but they are not
  sufficient on their own.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Aug  9 21:48:39 2017
  InstallationDate: Installed on 2017-08-06 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Title: [, Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio fails to detect 
card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0029.2016.1124.1625:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-402:cvn:ct3:cvr:
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-08-06T22:55:35.510382
  mtime.conffile..etc.pulse.default.pa: 2017-08-06T22:51:49.639085

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

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

[Touch-packages] [Bug 1713536] Re: udev: boot script does not trigger subsystem coldplug

[Dimitri John Ledkov]

With systemd 232-21ubuntu7 installed, changing default boot param to
break=bottom, and added set -x to the udev init-top script and
rebooting.

Observed that in the console boot log that both subsystems and devices
are triggered.


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

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

Title:
  udev: boot script does not trigger subsystem coldplug

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  subsystems udev rules are not processed on boot, thus resulting in missing 
devices on boot / before rootfs is mounted.

  [Solution]
  trigger udev subsystems and devices, in the initramfs, in that order.

  [Testcase]
  Boot s390x system with chzdev configured devices, and cio_ignore=all kernel 
command line parameter. The chzdev configured devices should still be 
discovered on boot.

  [Original Bug report]

  The udev initramfs-tools boot script does not trigger subsystem "add"
  uevents. As a result, udev rules that listen to subsystem "add" events
  are never activated. This problem exists on at least Ubuntu 16.04 and
  17.10.

  On s390, this results in a boot failure if the kernel is configured to
  start with an active device black list (kernel parameter
  cio_ignore=all,!condev). An example for an affected udev rule looks
  like this:

  ACTION=="add", SUBSYSTEM=="subsystem", KERNEL=="ccw",
  RUN{program}+="/bin/sh -c 'echo free 0009,ec30,ec32,f5f0-f5f2 >
  /proc/cio_ignore'"

  A proposed fix would be:

  Modify /usr/share/initramfs-tools/scripts/init-top/udev:

  Replace line
  udevadm trigger --action=add
  with
  udevadm trigger --type=subsystems --action=add
  udevadm trigger --type=devices --action=add

  This would also be consistent with the steps that the systemd udev
  coldplug unit file performs (see /lib/systemd/system/systemd-udev-
  trigger.service).

  [Regression Potential]
  More udev rules will be now triggered, earlier, during initramfs stage of 
boot rather than post-pivot-root. However, this is inline with current rootfs 
behaviour and thus should not regress behaviour - simply some rules will get 
triggered earlier.

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

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

[Touch-packages] [Bug 1709649] Re: 229 backport for race between explicit mount and handling automount

[Dimitri John Ledkov]

Reproduced hang with systemd 232-21ubuntu5.

Upgrading to 232-21ubuntu7 resolves the race.


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

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

Title:
  229 backport for  race between explicit mount and handling automount

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Triaged
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  In systemd prior to 234 a race exists between .mount and .automount units 
such that automount requests from kernel may not be serviced by systemd 
resulting in kernel holding the mountpoint and any processes that try to use 
said mount will hang. A race like this may lead to denial of service, until 
mount points are unmounted.

  [Testcase]
  Create a race between .mount and .automount units, such that automout request 
is serviced after .mount unit has been started. Observe a hang.
  More detailed steps are available at 
https://github.com/systemd/systemd/pull/5916

  [Butfix]
  Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/e7d54bf58789545a9eb0b3964233defa0b007318

  [Regression Potential]
  The underlying logic of starting/stopping/triggering units is unchanged. 
However, there the logic as to when to send automout_send_ready() is relaxed, 
such that it is always sent whenever unit is already mounted. This is done to 
explicitly cope with late arrival of the incoming [aircraft] automount request.

  [Original Bug report / request]

  Hi,

  We have a blocking issue in systemd for the following release

  ```
  NAME="Ubuntu"
  VERSION="16.04.3 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.3 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  ```

  This release runs systemd229, we are affected by the following auto-
  mouting race condition

  ```
  https://github.com/systemd/systemd/pull/5916
  ```

  Is back porting  the fix to the release 229 an option?

  Regards.

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

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

[Touch-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones

[Erikas]

Since we are talking about bash commands, shouldn't this be more elegant
solution?

=
#!/bin/bash
hda-verb /dev/snd/hwC[[:print:]]*D0 0x20 SET_COEF_INDEX 0x67
hda-verb /dev/snd/hwC[[:print:]]*D0 0x20 SET_PROC_COEF 0x3000
=

Just test it yourself:

ls -l /dev/snd/hwC[[:print:]]*D0

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

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

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

[Touch-packages] [Bug 1710410] Re: Must run systemd-resolve --status before DNS resolving is operative

[Dimitri John Ledkov]

Upgrading from 232-21ubuntu5 to 232-21ubuntu7 enables systemd-
resolved.service by default now.

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

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

Title:
  Must run systemd-resolve --status before DNS resolving is operative

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  systemd-resolved is not enabled by default, therefore relies on dbus 
activation to become active and operatable and update resolvconf with resolved 
stub resolver

  [Fix]
  Enable systemd-resolved in the src:systemd package by default, even when 
libnss-resolve is not installed

  [Regression Potential]
  Minimal, simply the service is now started earlier in the boot, as part of 
the multi-user.targer, rather than awaiting for dbus activation from command 
line tool or the nss-resolved module.

  [Testcase]
  Debootstrap minimal zesty, without libnss-resolve package installed, boot and 
check that 127.0.0.53 is present in /etc/resolv.conf and that 
systemd-resolved.service is running

  Context: fresh install of zesty via

  debootstrap --include=nano,dbus,iputils-ping,iproute2 zesty zesty1
  http://fr.archive.ubuntu.com/ubuntu

  ran via asystemd-nspawn with a static IP

  1. Upon first connexion, a ping fails:

  root@zesty1:~# ping google.com
  ping: google.com: Temporary failure in name resolution

  2. The content of /etc/resolv.conf:

  root@zesty1:~# 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.

  3. When running systemd-resolve --status:

  root@zesty1:~# systemd-resolve --status
  Global
   DNS Servers: 8.8.8.8
    8.8.4.4
    2001:4860:4860::
    2001:4860:4860::8844
    DNSSEC NTA: 10.in-addr.arpa
    16.172.in-addr.arpa
    168.192.in-addr.arpa
  (...)

  4. After running this command the resolution is miraculously restored:

  root@zesty1:~# ping google.com
  PING google.com (172.217.22.142) 56(84) bytes of data.
  64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=1 ttl=53 time=2.62 ms
  64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=2 ttl=53 time=1.93 ms

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

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

[Touch-packages] [Bug 1703393] Re: TCP offloads disabled by default

[Dimitri John Ledkov]

Reproduced
ubuntu@sruz:~$ ethtool -k ens3 | grep tcp
tcp-segmentation-offload: off
tx-tcp-segmentation: off
tx-tcp-ecn-segmentation: off [fixed]
tx-tcp-mangleid-segmentation: off
tx-tcp6-segmentation: off [fixed]
ubuntu@sruz:~$ dpkg-query -W systemd
systemd 232-21ubuntu5

Fixed
ubuntu@sruz:~$ ethtool -k ens3 | grep tcp
tcp-segmentation-offload: on
tx-tcp-segmentation: on
tx-tcp-ecn-segmentation: off [fixed]
tx-tcp-mangleid-segmentation: off
tx-tcp6-segmentation: off [fixed]
ubuntu@sruz:~$ dpkg-query -W systemd
systemd 232-21ubuntu7



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

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

Title:
  TCP offloads disabled by default

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]
  Regression in systemd v232 resulted in IPv4 TCP segmentation offload ("tso" 
in ethtool) to be disabled by default, yet previously it was enabled.

  [Fix]
  Backport upstream patch to fix the regression

  [Testcase]
  Use ethtool to verify that tso is enabled on e.g. e1000e card with fixed 
package.

  [Regression Potential]
  Link features were incorrectly initialised, this fix changes the 
initialisation code back to the correct default values. This changes the 
defaults back to what they are in all other releases. Users on zesty release 
may have been accustomed to the wrong defaults and may need to adjust .link 
files to e.g. disable tso if that is the behavior they want.

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

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

[Touch-packages] [Bug 1702823] Re: Systemd fails to serialize tasks correctly on daemon-reload

[Dimitri John Ledkov]

Reproducing the bug on zesty:
$ dpkg-query -W systemd
systemd 232-21ubuntu5
$ bash test.sh 
  accounts-daemon.service : Tasks: 3 (limit: 4915)
acpid.service : Tasks: 1 (limit: 4915)
  atd.service : Tasks: 1 (limit: 4915)
 cron.service : Tasks: 1 (limit: 4915)
 dbus.service : Tasks: 1 (limit: 4915)
   iscsid.service : Tasks: 2 (limit: 4915)
 lvm2-lvmetad.service : Tasks: 1 (limit: 4915)
lxcfs.service : Tasks: 3 (limit: 4915)
   polkit.service : Tasks: 3 (limit: 4915)
  rsyslog.service : Tasks: 4 (limit: 4915)
snapd.service : Tasks: 6 (limit: 4915)
  ssh.service : Tasks: 1 (limit: 4915)
 systemd-journald.service : Tasks: 1 (limit: 4915)
   systemd-logind.service : Tasks: 1 (limit: 4915)
 systemd-networkd.service : Tasks: 1 (limit: 4915)
 systemd-resolved.service : Tasks: 1 (limit: 4915)
systemd-timesyncd.service : Tasks: 2 (limit: 4915)
systemd-udevd.service : Tasks: 1
  accounts-daemon.service : 
acpid.service : 
  atd.service : 
 cron.service : 
 dbus.service : 
   iscsid.service : 
 lvm2-lvmetad.service : 
lxcfs.service : 
   polkit.service : 
  rsyslog.service : 
snapd.service : 
  ssh.service : 
 systemd-journald.service : 
   systemd-logind.service : 
 systemd-networkd.service : 
 systemd-resolved.service : 
systemd-timesyncd.service : 
systemd-udevd.service : 
  accounts-daemon.service : Tasks: 3 (limit: 4915)
acpid.service : Tasks: 1 (limit: 4915)
  atd.service : Tasks: 1 (limit: 4915)
 cron.service : Tasks: 1 (limit: 4915)
 dbus.service : Tasks: 1 (limit: 4915)
   iscsid.service : Tasks: 2 (limit: 4915)
 lvm2-lvmetad.service : Tasks: 1 (limit: 4915)
lxcfs.service : Tasks: 3 (limit: 4915)
   polkit.service : Tasks: 3 (limit: 4915)
  rsyslog.service : Tasks: 4 (limit: 4915)
snapd.service : Tasks: 6 (limit: 4915)
  ssh.service : Tasks: 1 (limit: 4915)
 systemd-journald.service : Tasks: 1 (limit: 4915)
   systemd-logind.service : Tasks: 1 (limit: 4915)
 systemd-networkd.service : Tasks: 1 (limit: 4915)
 systemd-resolved.service : Tasks: 1 (limit: 4915)
systemd-timesyncd.service : Tasks: 2 (limit: 4915)
systemd-udevd.service : Tasks: 1

Upgrading
$ dpkg-query -W systemd
systemd 232-21ubuntu7
$ bash test.sh 
  accounts-daemon.service : Tasks: 3 (limit: 4915)
acpid.service : Tasks: 1 (limit: 4915)
  atd.service : Tasks: 1 (limit: 4915)
 cron.service : Tasks: 1 (limit: 4915)
 dbus.service : Tasks: 1 (limit: 4915)
   iscsid.service : Tasks: 2 (limit: 4915)
 lvm2-lvmetad.service : Tasks: 1 (limit: 4915)
lxcfs.service : Tasks: 3 (limit: 4915)
   polkit.service : Tasks: 3 (limit: 4915)
  rsyslog.service : Tasks: 4 (limit: 4915)
snapd.service : Tasks: 5 (limit: 4915)
  ssh.service : Tasks: 1 (limit: 4915)
 systemd-journald.service : Tasks: 1 (limit: 4915)
   systemd-logind.service : Tasks: 1 (limit: 4915)
 systemd-networkd.service : Tasks: 1 (limit: 4915)
 systemd-resolved.service : Tasks: 1 (limit: 4915)
systemd-timesyncd.service : Tasks: 2 (limit: 4915)
systemd-udevd.service : Tasks: 1
  accounts-daemon.service : Tasks: 3 (limit: 4915)
acpid.service : Tasks: 1 (limit: 4915)
  atd.service : Tasks: 1 (limit: 4915)
 cron.service : Tasks: 1 (limit: 4915)
 dbus.service : Tasks: 1 (limit: 4915)
   iscsid.service : Tasks: 2 (limit: 4915)
 lvm2-lvmetad.service : Tasks: 1 (limit: 4915)
lxcfs.service : Tasks: 

[Touch-packages] [Bug 1682154] Re: loginctl ignoring user given sessions IDs at command-line

[Dimitri John Ledkov]

ubuntu@sruz:~$ dpkg-query -W systemd
systemd 232-21ubuntu5
ubuntu@sruz:~$ loginctl show-session 3 1 | grep -e Id= -e Leader
Id=3
Leader=1290
Id=3
Leader=1290

ubuntu@sruz:~$ dpkg-query -W systemd
systemd 232-21ubuntu7
ubuntu@sruz:~$ loginctl show-session 3 1 | grep -e Id= -e Leader
Id=3
Leader=1290
Id=1
Leader=1370


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

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

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

Title:
  loginctl ignoring user given sessions IDs at command-line

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  loginctl command does not process session IDs given on the command-line, like 
the documentation suggests. This makes it impossible to use simple command-line 
calls to check properties of a given session. 

  [Fix]
  Backport upstream patch to fix the issue

  [Testcase]
  Use loginctl command and specify multiple session IDs at the command-line and 
verify that details about these sessons are brought up in the output.

  [Regression Potential]
  Minimal, current behaviour is not sane at all, and it is a typpo fix from '1' 
to 'i' meaning that first argument was always used, instead of the current 
iterated one.

  
  Kubuntu zesty, 232-21ubuntu2

  See upstream bug https://github.com/systemd/systemd/issues/5733 with
  patch attached.

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

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

[Touch-packages] [Bug 1709135] Re: add bond primary parameter

[Dimitri John Ledkov]

$ sudo netplan apply
Error in network definition //etc/netplan/bond.yaml line 13 column 8: unknown 
key primary

$ dpkg-query -W nplan systemd
nplan   0.23~17.04.1
systemd 232-21ubuntu5

$ sudo netplan apply
$ echo $?
0

$ dpkg-query -W systemd nplan
nplan   0.29~17.04.1
systemd 232-21ubuntu7

Bond is up, changing primary setting in netplan and executing apply,
changes the active_slave.

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

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

Title:
  add bond primary parameter

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Committed
Status in nplan source package in Zesty:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed
Status in nplan source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Some complex bond configurations require setting a "primary" interface for 
the bond, or setting this greatly improves performance on the network bond.

  [Test case]
  See below for a configuration example.
  1) Apply configuration on a system with netplan.
  2) Run 'netplan apply'
  3) Validate that netplan apply does not return with an error
  4) Validate that netplan properly sets the "primary_slave" value on the bond. 
This can be verified by looking at /sys/class/net//bonding/primary_slave.
  5) Validate that there are no parsing errors from systemd-networkd in the 
journalctl

  [Regression potential]
  If existing configuration fails to be parsed, or lack of primary interface 
breaks configuration for existing bonds, this would be a regression caused by 
this update.

  ---

  ifenslave/eni support a bond parameter:  bond-primary which accepts an
  interface name that can be used to tell the kernel bonding driver
  which interface it should preferred in active-backup (and other
  modes).  This config option is missing in netplan.

   % cat bond-primary.yaml
  network:
    version: 2
    ethernets:
  eth0:
    match:
  driver: virtio
  ens4:
    match:
  driver: e1000
    bonds:
  bond0:
    parameters:
  mode: active-backup
  mii-monitor-interval: 100
  primary: e1000
    dhcp4: true

  % ./generate -r `pwd`/target
  Error in network definition 
/home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 
column 8: unknown key primary

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

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

[Touch-packages] [Bug 1720809] Re: Move fonts to desktop-common

[Launchpad Bug Tracker]

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

---
ubuntu-meta (1.403) artful; urgency=medium

  * Refreshed dependencies
  * Added fonts-indic to desktop-recommends (LP: #1720809)
  * Added gnome-getting-started-docs to desktop-recommends (LP: #1721795)
  * Removed apt-transport-https from standard-recommends (LP: #1712871)
  * Removed fonts-guru from desktop-recommends (LP: #1720809)
  * Removed thunderbird from desktop-recommends [s390x] (LP: #1720422)
  * Removed thunderbird-gnome-support from desktop-recommends [s390x]

 -- Jeremy Bicha   Sun, 08 Oct 2017 17:14:33 -0400

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

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

Title:
  Move fonts to desktop-common

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  I split this bug out from LP: #1719934

  Summary
  ===
  Move fonts-indic from supported to desktop-common as Recommends
  Move fonts-noto-cjk, fonts-nanum, and fonts-liberation from desktop to 
desktop-common as Recommends

  Details
  ===

  Indic
  -
  desktop-common in 14.04 had recommends for:

   * (ttf-indic-fonts-core)
   * (ttf-punjabi-fonts)

  https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/platform.trusty/view/head:/desktop-common#L89

  But those were dropped before 16.04 LTS.

  There's a description of ttf-indic-fonts-core in the changelog:
  https://launchpad.net/ubuntu/+source/ttf-indic-fonts/1:0.5.14ubuntu1

  sudo apt install fonts-indic gives these numbers:

  Need to get 3,315 kB of archives.
  After this operation, 11.6 MB of additional disk space will be used.

  The other 3 fonts
  -
  The comment says there were "space reasons" to have some fonts listed in 
desktop instead of desktop-common but I believe that doesn't apply any more. 
(All the Desktop flavors appear to ship those fonts except Lubuntu doesn't 
include fonts-liberation but Lubuntu Next does so that seems a mistake to not 
include that font.)

  https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/ubuntu.artful/view/head:/desktop#L34

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

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

[Touch-packages] [Bug 1719047] Re: Unable to resize window after snapped to half screen.

[Alex Willmer]

> I did an apt upgrade, an apt uninstall of *unity*, and a reboot. I can
now resize snapped windows.

Spoke to soon. Resizing snapped windows works sometimes, not all the
time.

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

Title:
  Unable to resize window after snapped to half screen.

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Unable to resize window after snapped to half screen.  You can see the
  arrow, tempting you to just try and resize the window at the edge, but
  it's just toying with you.

  More info https://bugzilla.gnome.org/show_bug.cgi?id=645153

  This used to work in z+Unity ;(.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 19:15:17 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome-beta.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 
'gnome-control-center.desktop', 'keepassx.desktop', 
'chrome-knipolnnllmklapflnccelgolnpehhpl-Default.desktop', 
'terminator.desktop', 'org.gnome.Calculator.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.2'
   b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-04-25 (515 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-09-09 (13 days ago)

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

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