date:20171002

Marking bug as invalid, as it is intentional that ifupdown is not
installable by default.

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

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

Title:
  17.10Beta2. networking.service not available

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  tested on lubuntu 17.10B2 and budgie 17.10b2

  systemctl list-units
  systemctl list-unit-files

  Neither includes networking.service.

  systemctl status networking.service returns
  "Unit networking.service could not be found."

  Neither LAN nor internet are accessible

  This is available in 17.04 for both tested distros and is necessary
  for raising network with NetworkManager removed.

  in 17.04, status is active,exited. Both LAN and internet are
  accessible.

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

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

[Touch-packages] [Bug 1720892] Re: 17.10Beta2. networking.service not available

ifupdown which provides netowrking.service is no longer installed by
default or used.

desktop systems default to networkmanager for network management, as
they have done since forever.

server and cloud systems in artful default to using src:nplan package,
netplan command line by default. Which generates and uses systemd-
networkd by default.

If you do not wish to use Networkmanager, please write a netplan yaml
config in /etc/netplan and reboot.

netplan command has a helpful `ifupdown-migrate` subcommand, which may
be convenient for you to convert ifupdown e-n-i files into netplan yaml.
A simple example is:

$ cat /etc/netplan/10-netplan.yaml
network:
  version: 2
  ethernets:
eth0:
  match:
name: eth0
  dhcp4: true

Please see https://wiki.ubuntu.com/Netplan for more information.

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

Title:
  17.10Beta2. networking.service not available

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  tested on lubuntu 17.10B2 and budgie 17.10b2

  systemctl list-units
  systemctl list-unit-files

  Neither includes networking.service.

  systemctl status networking.service returns
  "Unit networking.service could not be found."

  Neither LAN nor internet are accessible

  This is available in 17.04 for both tested distros and is necessary
  for raising network with NetworkManager removed.

  in 17.04, status is active,exited. Both LAN and internet are
  accessible.

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

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

[Touch-packages] [Bug 1718029] Re: cloudstack and azure datasources broken when using netplan/systemd-networkd

** Changed in: cloud-init (Ubuntu)
 Assignee: Dimitri John Ledkov (xnox) => Scott Moser (smoser)

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

Title:
  cloudstack and azure datasources broken when using netplan/systemd-
  networkd

Status in netplan:
  Invalid
Status in cloud-init package in Ubuntu:
  In Progress
Status in nplan package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu artful, cloud-init renders network configuration through netplan.
  This means that there is no dhclient and thus no /var/lib/dhclient/*.leases.

  Azure and CloudStack both are reading those leases file to get useful
  information about the platform.

  Specifically:
   * Azure reads option-245 from the dhclient response to find the IP address 
of the metadata service.
   * CloudStack reads the 'dhcp-server-identifier' option in the dhclient 
response to get the address of the virtual router (metadata service). [1]

  In ubuntu this happens to be done with systemd-networkd, so cloud-init
  can possibly probably interact over the dbus with systemd-networkd to
  get information.  However that is less than ideal, as ultimately
  cloud-init should not need to know that it systemd-networkd is
  involved.  It should be hidden via netplan.  So there should be an
  interface to get current networking configuratoin information from
  netplan including dhcp lease response info.

  
  --
  [1] 
http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.8/virtual_machines/user-data.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: cloud-init 0.7.9-280-ge626966e-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CloudName: Amazon - Ec2
  Date: Mon Sep 18 19:56:40 2017
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: cloud-init
  UpgradeStatus: No upgrade log present (probably fresh install)
  user_data.txt:
   #cloud-config
   {}

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

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

[Touch-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

2017-10-02 Thread David H. Wilkins

Solved?

Thanks for this forum Ubuntu. I'm a Fedora user, but I frequently find
solutions here

I have an XPS 9550 along with the issue of the headphone microphone not
working. I changed /etc/modprobe.d/alsa.conf from:

options snd-hda-intel single_cmd=1 probe_mask=1 model=dell-headset-multi

to:

options snd-hda-intel single_cmd=1 probe_mask=1 model=headset-mic

And now my headphone microphone works. There is no annoying popup when
you plug in the headphones either. Hopefully this helps someone.

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

Title:
[XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
while

Status in alsa-driver package in Ubuntu:
Confirmed

Bug description:
I'm experiencing a strange behavior with a headphone jack on my
laptop.

I have an external audio speaker connected to it. When I disconnect the
speaker and reconnect it again it stops working.
Even more, laptop audio stops working too. And after the reboot, I don't even
see any of the audio devices.

I've googled a lot and tried different fixes from forums with no luck.
After a while, I've accidentally discovered that putting the laptop to
the sleep mode and rebooting system after brings audio back to live.
Even more, if speakers were attached during this sleep-reboot
procedure, they are starting to work as well.

However, after the next reboot speakers are not working again. And if
I will plug them out and in - problem with completely missing audio
returns.

P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
hibernation made me believe that it's somehow related. But after
uninstalling this package nothing really changed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: kop3224 F...m pulseaudio
/dev/snd/controlC0: kop3224 F pulseaudio
CurrentDesktop: Unity
Date: Tue Apr 26 12:17:03 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-22 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Встроенное аудио - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: Sound works for a while, then breaks
Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after
a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1720256] Re: Wrong display of fonts in Gnome Tweak Tool after installing cantarell fonts

2017-10-02 Thread Jeremy Soller

This affects pop-session as well, which uses session overrides similar
to how ubuntu-session does. The desktop icon settings are also
incorrect.

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

Title:
  Wrong display of fonts in Gnome Tweak Tool after installing cantarell
  fonts

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  When cantarell fonts are installed, Gnome Tweak Tools shows as if
  "Cantarell" was the font being used when it is actually "Ubuntu".
  Before that, it showed "None".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1720256/+subscriptions

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

[Touch-packages] [Bug 1564426] Re: Import problem - Spanish (es) - glib20 in Ubuntu Xenial package "glib2.0"

This is a recurring problem with the Spanish translations because of a
bug in the gtranslator app used by the primary Spanish translator for
GNOME.

https://git.gnome.org/browse/glib/commit/?id=362ee2c

https://bugzilla.gnome.org/show_bug.cgi?id=771765

** Changed in: glib2.0 (Ubuntu)
   Status: New => Fix Released

** Bug watch added: GNOME Bug Tracker #771765
   https://bugzilla.gnome.org/show_bug.cgi?id=771765

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

Title:
  Import problem - Spanish (es) - glib20 in Ubuntu Xenial package
  "glib2.0"

Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  Looks like there was an accidental word-wrap problem in po/es.po.

  Line 13 is really the end of line 12. I've included a patch to send
  upstream.

  Here's a copy of the email that IS has been getting for a while now:

  Hello Launchpad Translations Administrators,

  On 2016-03-18 13:50z (12 days 14 hours 16 minutes ago), you uploaded a
  file with Spanish (es) translations for glib20 in Ubuntu Xenial package
  "glib2.0" to Launchpad.

  We were unable to import the file because of errors in its format:

  Line 13: Invalid content: u', 2013, 2014, 2015, 2016.'

  If you use gettext, you can check your file for correct formatting with
  the 'msgfmt -c' command. Please fix any errors raised by msgfmt and
  upload the file again. If you check the file and you don't find any
  error in it, please look for an answer or file a question at
  https://answers.launchpad.net/rosetta/

  For your convenience, you can get the file you uploaded at:
  http://launchpadlibrarian.net/250464407/es.po

  Thank you,

  The Launchpad team

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1564426/+subscriptions

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

[Touch-packages] [Bug 1700319] Re: GTK3 menus don't work over SSH forwarding

2017-10-02 Thread Harry Coin

Just to be clear:  This is a regression.  It worked in 3.16.

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

Title:
  GTK3 menus don't work over SSH forwarding

Status in GTK+:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  When connecting remotely (either SSH X11 forwarding or direct to X11
  server), drop down menus do not display properly.

  Bug upstream in gtk3:
  https://bugzilla.gnome.org/show_bug.cgi?id=780101

  Client: Ubuntu 17.04 - gtk3-3.22.11-0ubuntu3
  Server: Windows 10 Cygwin/X 1.19.2-1

  Programs exhibiting this problem:
  evince 3.24.0 (and any other gtk3 apps with menus along the top).

  Patch applied to gtk3 in cygwin to fix this problem and attached to this post:
  https://github.com/cygwinports/gtk3/blob/master/3.22.10-xrandr12-compat.patch

  Console errors:

  (evince:7390): GLib-GIO-CRITICAL **: g_dbus_proxy_get_name_owner:
  assertion 'G_IS_DBUS_PROXY (proxy)' failed

  (evince:7390): GLib-WARNING **: GError set over the top of a previous GError 
or uninitialized memory.
  This indicates a bug in someone's code. You must ensure an error is NULL 
before it's set.
  The overwriting error message was: The name org.freedesktop.portal.Desktop is 
not owned

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: 
assertion 'width >= 0' failed
  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  
  (evince:7390): Gtk-WARNING **: Negative content width -7 (allocation 1, 
extents 4x4) while allocating gadget (node arrow, owner GtkMenu)

  (evince:7390): Gtk-WARNING **: Negative content width -7 (allocation 1, 
extents 4x4) while allocating gadget (node arrow, owner GtkMenu)
  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  
  (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation 1, 
extents 6x6) while allocating gadget (node menuitem, owner GtkModelMenuItem)

  (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation
  1, extents 6x6) while allocating gadget (node menuitem, owner
  GtkModelMenuItem)

  (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation
  1, extents 6x6) while allocating gadget (node menuitem, owner
  GtkModelMenuItem)

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

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

[Touch-packages] [Bug 1700319] Re: GTK3 menus don't work over SSH forwarding

2017-10-02 Thread Harry Coin

I installed this patch on 3.22.10, it did not solve the problem of no
menu entries listed when menu headings chosen in virt-manager.  I also
tried the latest upstream version, 3.22.21, which still has the same
problem via x11 and no other time.

The errors in the paste below occur when the "File" menu item is clicked
once in the virt-manager via ssh / x11 forwarding (obviously it works
locally).  The relevant error is:

(virt-manager:12201): Gtk-CRITICAL **: 
gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
a few times, followed by 
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug


[administrator@ceo1homenx ~]$ virt-manager --debug
[Mon, 02 Oct 2017 20:51:21 virt-manager 12201] DEBUG (cli:261) Launched with 
command line: /usr/share/virt-manager/virt-manager --debug
[Mon, 02 Oct 2017 20:51:21 virt-manager 12201] DEBUG (virt-manager:183) 
virt-manager version: 1.4.1
[Mon, 02 Oct 2017 20:51:21 virt-manager 12201] DEBUG (virt-manager:184) 
virtManager import: 
[Mon, 02 Oct 2017 20:51:23 virt-manager 12201] DEBUG (virt-manager:214) 
PyGObject version: 3.22.0
[Mon, 02 Oct 2017 20:51:23 virt-manager 12201] DEBUG (virt-manager:218) GTK 
version: 3.22.10
[Mon, 02 Oct 2017 20:51:24 virt-manager 12201] DEBUG (engine:496) libguestfs 
inspection support: False
[Mon, 02 Oct 2017 20:51:24 virt-manager 12201] DEBUG (systray:156) Showing 
systray: False
[Mon, 02 Oct 2017 20:51:24 virt-manager 12201] DEBUG (engine:1037) processing 
cli command uri= show_window= domain=
[Mon, 02 Oct 2017 20:51:24 virt-manager 12201] DEBUG (engine:1039) No cli 
action requested, launching default window
[Mon, 02 Oct 2017 20:51:24 virt-manager 12201] DEBUG (manager:203) Showing 
manager
[Mon, 02 Oct 2017 20:51:24 virt-manager 12201] DEBUG (engine:401) window 
counter incremented to 1
[Mon, 02 Oct 2017 20:51:24 virt-manager 12201] DEBUG (engine:161) Loading 
stored URIs:
qemu+ssh://administra...@noc1.ll.quietfountain.com/system  
qemu+ssh://administra...@noc1.ri.mamabosso.com/system  
qemu+ssh://administra...@noc2.ll.quietfountain.com/system  
qemu+ssh://administra...@noc2.ri.mamabosso.com/system  
qemu:///system
[Mon, 02 Oct 2017 20:51:24 virt-manager 12201] DEBUG (engine:140) Initial 
gtkapplication activated

(virt-manager:12201): Gtk-CRITICAL **:
gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed

(virt-manager:12201): Gtk-CRITICAL **:
gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed

(virt-manager:12201): Gtk-CRITICAL **:
gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed

(virt-manager:12201): Gtk-CRITICAL **:
gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed

(virt-manager:12201): Gtk-CRITICAL **: 
gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug


(virt-manager:12201): Gtk-WARNING **: Negative content width -7 (allocation 1, 
extents 4x4) while allocating gadget (node arrow, owner GtkMenu)

(virt-manager:12201): Gtk-WARNING **: Negative content width -7 (allocation 1, 
extents 4x4) while allocating gadget (node arrow, owner GtkMenu)
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug


(virt-manager:12201): Gtk-WARNING **: Negative content width -11 (allocation 1, 
extents 6x6) while allocating gadget (node menuitem, owner GtkImageMenuItem)

(virt-manager:12201): Gtk-WARNING **: Negative content width -11
(allocation 1, extents 6x6) while allocating gadget (node menuitem,
owner GtkMenuItem)

(virt-manager:12201): Gtk-WARNING **: Negative content width -11
(allocation 1, extents 6x6) while allocating gadget (node menuitem,
owner GtkImageMenuItem)

(virt-manager:12201): Gtk-WARNING **: Negative content width -11
(allocation 1, extents 6x6) while allocating gadget (node menuitem,
owner GtkImageMenuItem)

(virt-manager:12201): Gtk-CRITICAL **:
gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed

(virt-manager:12201): Gtk-CRITICAL **:
gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed

(virt-manager:12201): Gtk-CRITICAL **:
gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed

(virt-manager:12201): Gtk-CRITICAL **:
gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed

(virt-manager:12201): Gtk-CRITICAL **: 
gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug


(virt-manager:12201): Gtk-WARNING **: Negative content

[Touch-packages] [Bug 1720919] [NEW] package libgl1-mesa-dri:amd64 17.0.7-0ubuntu0.17.04.1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar

2017-10-02 Thread raybarretomundico

Public bug reported:

ACUSANDO UM ERRO NO SISTEMA

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libgl1-mesa-dri:amd64 17.0.7-0ubuntu0.17.04.1
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.5
AptOrdering: NULL: ConfigurePending
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Oct  2 01:11:05 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
DpkgHistoryLog:
 Start-Date: 2017-10-02  01:11:05
 Commandline: apt-get purge openjdk*
 Requested-By: raybarreto (1000)
DpkgLog: 2017-10-02 01:11:05 startup packages configure
DpkgTerminalLog:
 dpkg: erro ao processar o pacote libgl1-mesa-dri:amd64 (--configure):
  O pacote está num mau estado de inconsistência; deve
  reinstala-lo antes de tentar configura-lo.
ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6530D] 
[1002:964a] (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd BeaverCreek [Radeon HD 6530D] 
[1458:d000]
InstallationDate: Installed on 2017-07-30 (64 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Gigabyte Technology Co., Ltd. GA-A75M-UD2H
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=4ab4464d-6b41-48e7-b398-9a675ddfa854 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: mesa
Title: package libgl1-mesa-dri:amd64 17.0.7-0ubuntu0.17.04.1 failed to 
install/upgrade: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-A75M-UD2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd06/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-A75M-UD2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
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.14-0ubuntu1
xserver.bootTime: Mon Oct  2 19:55:09 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.1
xserver.video_driver: radeon

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


** Tags: amd64 apport-package compiz-0.9 ubuntu zesty

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

Title:
  package libgl1-mesa-dri:amd64 17.0.7-0ubuntu0.17.04.1 failed to
  install/upgrade: O pacote está num mau estado de inconsistência; deve
  reinstala-lo antes de tentar configura-lo.

Status in mesa package in Ubuntu:
  New

Bug description:
  ACUSANDO UM ERRO NO SISTEMA

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libgl1-mesa-dri:amd64 17.0.7-0ubuntu0.17.04.1
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Oct  2 01:11:05 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DpkgHistoryLog:
   Start-Date: 2017-10-02  01:11:05
   Commandline: apt-get purge openjdk*
   Requested-By: raybarreto (1000)
  DpkgLog: 2017-10-02 01:11:05 startup packages configure
  DpkgTerminalLog:
   dpkg: erro ao processar o pacote libgl1-mesa-dri:amd64

[Touch-packages] [Bug 1720914] Re: gdebi-kde crashed with ModuleNotFoundError in /usr/lib/python3/dist-packages/PyKDE4/init.py: No module named 'DLFCN'

2017-10-02 Thread Apport retracing service

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

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 #1708947, 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.

** Tags removed: need-duplicate-check

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

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

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

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

** Information type changed from Private to Public

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

Title:
  gdebi-kde crashed with ModuleNotFoundError in /usr/lib/python3/dist-
  packages/PyKDE4/__init__.py: No module named 'DLFCN'

Status in gdebi package in Ubuntu:
  New

Bug description:
  During new install of 17.10 I always install gdebi for .deb packages.
  Haven't used it yet, but downloaded using Ubuntu Softwareand then clicked 
Launch from the Ubuntu Software wizard...never opened.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gdebi-kde 0.9.5.7+nmu1ubuntu3
  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
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  2 19:57:59 2017
  ExecutablePath: /usr/share/gdebi/gdebi-kde
  InstallationDate: Installed on 2017-10-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-kde
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 
3.6.2-1ubuntu4
  PythonArgs: ['/usr/bin/gdebi-kde']
  PythonDetails: /home/lee/Error: command ['which', 'python'] failed with exit 
code 1:, Error: [Errno 2] No such file or directory: "/home/lee/Error: command 
['which', 'python'] failed with exit code 1:": "/home/lee/Error: command 
['which', 'python'] failed with exit code 1:", unpackaged
  SourcePackage: gdebi
  Title: gdebi-kde crashed with ModuleNotFoundError in 
/usr/lib/python3/dist-packages/PyKDE4/__init__.py: No module named 'DLFCN'
  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/gdebi/+bug/1720914/+subscriptions

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

[Touch-packages] [Bug 1712871] Re: ubuntu-standard should not depend on apt-transport-https in >= artful

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

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

Title:
  ubuntu-standard should not depend on apt-transport-https in >= artful

Status in ubuntu-meta package in Ubuntu:
  Fix Committed

Bug description:
  https support has been merged into apt itself for artful (apt >=
  1.5~), and stable since 1.5~beta2, so please stop seeding apt-
  transport-https (maybe we can demote the binary package to universe
  then? - I don't know how well people like that).

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

-- 
Mailing list: https://launchpad.net/~touch-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

2017-10-02 Thread Rafael David Tinoco

Meanwhile I have created a PPA containing the fix for all those affected
users:

https://launchpad.net/~inaddy/+archive/ubuntu/lp1718966

$ sudo add-apt-repository ppa:inaddy/lp1718966
$ sudo apt-get update
$ sudo apt-get dist-upgrade

Is likely enough for you to have a temporary fix.

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

Title:
  Cannot install snaps on Ubuntu 14.04 with /var on its own partition

Status in snapd:
  Invalid
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Trusty:
  In Progress

Bug description:
  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.

  
  Steps to reproduce:
  ===

  # 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--- 3.72g 
  swap vg00 -wi-ao--- 3.72g 
  varvol vg00 -wi-ao--- 3.72g 

  root@ubuntu:~# df -h
  Filesystem   Size  Used Avail Use% Mounted on
  udev 484M  4.0K  484M   1% /dev
  tmpfs100M  988K   99M   1% /run
  /dev/dm-03.7G  1.7G  1.8G  49% /
  none 4.0K 0  4.0K   0% /sys/fs/cgroup
  none 5.0M 0  5.0M   0% /run/lock
  none 497M 0  497M   0% /run/shm
  none 100M 0  100M   0% /run/user
  /dev/mapper/vg00-varvol  3.7G  716M  2.8G  21% /var

  
  # Upgrade system, install snapd and reboot

  root@ubuntu:~# apt update
  root@ubuntu:~# apt upgrade -y
  root@ubuntu:~# apt install -y snapd
  root@ubuntu:~# reboot

  
  # After reboot, check kernel version and try to install the 
canonical-livepatch snap:

  root@ubuntu:~# uname -a
  Linux ubuntu 4.4.0-96-generic #119~14.04.1-Ubuntu SMP Wed Sep 13 08:40:48 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  root@ubuntu:~# snap list
  No snaps are installed yet. Try "snap install hello-world".

  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.
  )

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

-- 
Mailing list: https://launchpad.net/~touch-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

2017-10-02 Thread Ubuntu Foundations Team Bug Bot

The attachment "trusty_systemd_204-5ubuntu20.25.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1718966

Title:
  Cannot install snaps on Ubuntu 14.04 with /var on its own partition

Status in snapd:
  Invalid
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Trusty:
  In Progress

Bug description:
  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.

  
  Steps to reproduce:
  ===

  # 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--- 3.72g 
  swap vg00 -wi-ao--- 3.72g 
  varvol vg00 -wi-ao--- 3.72g 

  root@ubuntu:~# df -h
  Filesystem   Size  Used Avail Use% Mounted on
  udev 484M  4.0K  484M   1% /dev
  tmpfs100M  988K   99M   1% /run
  /dev/dm-03.7G  1.7G  1.8G  49% /
  none 4.0K 0  4.0K   0% /sys/fs/cgroup
  none 5.0M 0  5.0M   0% /run/lock
  none 497M 0  497M   0% /run/shm
  none 100M 0  100M   0% /run/user
  /dev/mapper/vg00-varvol  3.7G  716M  2.8G  21% /var

  
  # Upgrade system, install snapd and reboot

  root@ubuntu:~# apt update
  root@ubuntu:~# apt upgrade -y
  root@ubuntu:~# apt install -y snapd
  root@ubuntu:~# reboot

  
  # After reboot, check kernel version and try to install the 
canonical-livepatch snap:

  root@ubuntu:~# uname -a
  Linux ubuntu 4.4.0-96-generic #119~14.04.1-Ubuntu SMP Wed Sep 13 08:40:48 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  root@ubuntu:~# snap list
  No snaps are installed yet. Try "snap install hello-world".

  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.
  )

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

--

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

2017-10-02 Thread Alan

...and resolved on my system.

Searched again recently for the error. Found a recommendation to try

sudo apt install mount --reinstall

Look at what I had tried before as noted in initial bug report. Did not
try this.

mount was successfully reinstalled followed by me updating the 215
packages that were pending update since this problem began.

Have now successfully updated packages twice since performing this fix.

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

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

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

Bug description:
  sudo apt upgrade fails. Output is as follows...

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 0 B/130 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  dpkg: error processing package mount (--configure):
   package mount is not ready for configuration
   cannot configure (current status 'half-installed')
  Errors were encountered while processing:
   mount
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  I've combed the web for a solution and tried all of the following.
  None of which have resolved the issue...

  sudo apt-get install -f
  sudo apt-get install --fix-broken --fix-missing
  sudo apt-get -f install
  sudo apt-get update –fix-missing
  sudo apt-get autoremove
  sudo apt-get -u dist-upgrade
  sudo apt --reinstall mount

  sudo dpkg –configure -a
  sudo dpkg -r -a

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: mount 2.29-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   mount:amd64: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Jun 29 00:16:17 2017
  DpkgTerminalLog:
   dpkg: error processing package mount (--configure):
package mount is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package mount is not ready for configuration  cannot configure 
(current status 'half-installed')
  InstallationDate: Installed on 2016-09-02 (300 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package mount 2.29-1ubuntu2.1 failed to install/upgrade: package mount 
is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: Upgraded to zesty on 2017-05-20 (39 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-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

2017-10-02 Thread Rafael David Tinoco

I've made a small change creating a unit file slightly different from
the one already present in systemd-204, considering different
dependencies for this usage (mounting/umounting volumes when upstart has
already taken part on it).

The result is here: http://pastebin.ubuntu.com/25663762/

As you can see, after installing the new packages, being proposed in
this fix, snapd can work again mounting all new squash filesystems it
depends on.

- Attaching the debdiff for SRU.
- Requesting SRU sponsoring.
- Will verify once it gets uploaded to -proposed.

** Patch added: "trusty_systemd_204-5ubuntu20.25.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718966/+attachment/4960880/+files/trusty_systemd_204-5ubuntu20.25.debdiff

** Tags added: sts sts-sponsor

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

Title:
  Cannot install snaps on Ubuntu 14.04 with /var on its own partition

Status in snapd:
  Invalid
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Trusty:
  In Progress

Bug description:
  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.

  
  Steps to reproduce:
  ===

  # 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--- 3.72g 
  swap vg00 -wi-ao--- 3.72g 
  varvol vg00 -wi-ao--- 3.72g 

  root@ubuntu:~# df -h
  Filesystem   Size  Used Avail Use% Mounted on
  udev 484M  4.0K  484M   1% /dev
  tmpfs100M  988K   99M   1% /run
  /dev/dm-03.7G  1.7G  1.8G  49% /
  none 4.0K 0  4.0K   0% /sys/fs/cgroup
  none 5.0M 0  5.0M   0% /run/lock
  none 497M 0  497M   0% /run/shm
  none 100M 0  100M   0% /run/user
  /dev/mapper/vg00-varvol  3.7G  716M  2.8G  21% /var

  
  # Upgrade system, install snapd and reboot

  root@ubuntu:~# apt update
  root@ubuntu:~# apt upgrade -y
  root@ubuntu:~# apt install -y snapd
  root@ubuntu:~# reboot

  
  # After reboot, check kernel version and try to install the 
canonical-livepatch snap:

  root@ubuntu:~# uname -a
  Linux ubuntu 4.4.0-96-generic #119~14.04.1-Ubuntu SMP Wed Sep 13 08:40:48 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  root@ubuntu:~# snap list
  No snaps are installed yet. Try "snap install hello-world".

  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

[Touch-packages] [Bug 1720903] [NEW] Driver Nvidia and Skylake hybrid

2017-10-02 Thread Charly

Public bug reported:

Errors with load of graphic counter-parts such as nvidia, skylake, vga.
problems of this type


AER: Corrected error received: id=00e3
[12548.649166] pcieport :00:1c.3: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, id=00e3(Transmitter ID)
[12548.649174] pcieport :00:1c.3:   device [8086:a113] error 
status/mask=3000/2000
[12548.649180] pcieport :00:1c.3:[12] Replay Timer Timeout

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 
PDT 2017
 GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
BootLog: /dev/sdb5: clean, 321608/7790592 files, 3013756/31133440 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Oct  2 17:24:35 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1c5d]
   Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1c5d]
InstallationDate: Installed on 2017-09-09 (23 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd 
 Bus 001 Device 004: ID 0458:003a KYE Systems Corp. (Mouse Systems) NetScroll+ 
Mini Traveler / Genius NetScroll 120
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. GL552VW
ProcEnviron:
 LANGUAGE=es_CR:es
 PATH=(custom, no user)
 LANG=es_CR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=f53b18f9-610c-4845-8a14-dd2273235f72 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/06/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL552VW.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL552VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: GL552VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
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.14-0ubuntu1
xserver.bootTime: Mon Oct  2 13:36:39 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.1

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


** Tags: amd64 apport-bug ubuntu zesty

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

Title:
  Driver Nvidia and Skylake hybrid

Status in xorg package in Ubuntu:
  New

Bug description:
  Errors with load of graphic counter-parts such as nvidia, skylake,
  vga. problems of this type


  AER: Corrected error received: id=00e3
  [12548.649166] pcieport :00:1c.3: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, id=00e3(Transmitter ID)
  [12548.649174] pcieport :00:1c.3:   device [8086:a113] error 
status/mask=3000/2000
  [12548.649180] pcieport :00:1c.3:[12] Replay Timer Timeout

  ProblemType: Bug
  DistroRelease:

[Touch-packages] [Bug 1669254] Re: 16.04 apparmor, aa-logprof and log files

2017-10-02 Thread Christian Boltz

** Tags added: aa-tools

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

Title:
  16.04 apparmor, aa-logprof and log files

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  First of all I'd like to say that by default

  /etc/apparmor/logprof.conf

  contains

   logfiles = /var/log/audit/audit.log /var/log/syslog /var/log/messages

  from which only syslog exists in 16.04.

  And there is kern.log , which seems to be better suited for reading
  apparmor kernel messages.

  Why not change this in distribution?

  Thank you!

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

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

[Touch-packages] [Bug 1720898] [NEW] Facebook Sign-On doesn't work

2017-10-02 Thread cement_head

Public bug reported:

Asks for password, never signs-on

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 [modified: 
usr/share/accounts/providers/facebook.provider]
ProcVersionSignature: Ubuntu 4.10.0-36.40~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Oct  2 18:39:31 2017
InstallationDate: Installed on 2017-09-29 (3 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
SourcePackage: account-plugins
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: account-plugins (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages xenial

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

Title:
  Facebook Sign-On doesn't work

Status in account-plugins package in Ubuntu:
  New

Bug description:
  Asks for password, never signs-on

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 [modified: 
usr/share/accounts/providers/facebook.provider]
  ProcVersionSignature: Ubuntu 4.10.0-36.40~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct  2 18:39:31 2017
  InstallationDate: Installed on 2017-09-29 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: account-plugins
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1720892] Re: 17.10Beta2. networking.service not available

2017-10-02 Thread holiday

Excuse me I should have stated at the top that this issue appears after
purging NetworkManager.

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

Title:
  17.10Beta2. networking.service not available

Status in systemd package in Ubuntu:
  New

Bug description:
  tested on lubuntu 17.10B2 and budgie 17.10b2

  systemctl list-units
  systemctl list-unit-files

  Neither includes networking.service.

  systemctl status networking.service returns
  "Unit networking.service could not be found."

  Neither LAN nor internet are accessible

  This is available in 17.04 for both tested distros and is necessary
  for raising network with NetworkManager removed.

  in 17.04, status is active,exited. Both LAN and internet are
  accessible.

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

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

[Touch-packages] [Bug 1714122] Re: latest skype update causes xorg to segfault

2017-10-02 Thread Yuriy Vidineev

Looks like for me issue was fixed agter upgrade to linux 4.13. But I'm
not 100% sure yet

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

Title:
  latest skype update causes xorg to segfault

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After update skypeforlinux to 8.5.76.55323 I've started to get xorg segfaults 
when connected to 2 external monitors via docking station.
  My setup: Dell XPS 13 9360 + Dell DS1000 USB-C docking station+2 external 
FullHD Dell monitors.
  In xorg logs I can see:

  [ 17917.757] (II) LoadModule: "modesetting"
  [ 17917.757] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
  [ 17917.757] (II) Module modesetting: vendor="X.Org Foundation"
  [ 17917.757]compiled for 1.18.4, module version = 1.18.4
  [ 17917.757]Module class: X.Org Video Driver
  [ 17917.757]ABI class: X.Org Video Driver, version 20.0
  [ 17917.757] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
  [ 17917.759] (II) modeset(0): using drv /dev/dri/card0
  [ 17917.759] (EE) 
  [ 17917.759] (EE) Backtrace:
  [ 17917.759] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55c4f0526b6e]
  [ 17917.759] (EE) 1: /usr/lib/xorg/Xorg (0x55c4f0374000+0x1b6ef9) 
[0x55c4f052aef9]
  [ 17917.759] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fb6199e2000+0x354b0) 
[0x7fb619a174b0]
  [ 17917.759] (EE) 3: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 
(pci_device_next+0x118) [0x7fb61afd1a38]
  [ 17917.759] (EE) 4: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 
(pci_device_find_by_slot+0x3b) [0x7fb61afd1abb]
  [ 17917.759] (EE) 5: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 
(pci_device_vgaarb_init+0xaf) [0x7fb61afd37af]
  [ 17917.759] (EE) 6: /usr/lib/xorg/Xorg (0x55c4f0374000+0xb1a39) 
[0x55c4f0425a39]
  [ 17917.759] (EE) 7: /usr/lib/xorg/Xorg (xf86BusConfig+0x62) [0x55c4f03fe7a2]
  [ 17917.759] (EE) 8: /usr/lib/xorg/Xorg (InitOutput+0x968) [0x55c4f040cd58]
  [ 17917.759] (EE) 9: /usr/lib/xorg/Xorg (0x55c4f0374000+0x57be4) 
[0x55c4f03cbbe4]
  [ 17917.759] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7fb619a02830]
  [ 17917.759] (EE) 11: /usr/lib/xorg/Xorg (_start+0x29) [0x55c4f03b6049]
  [ 17917.759] (EE) 
  [ 17917.759] (EE) Segmentation fault at address 0x0
  [ 17917.759] (EE) 
  Fatal server error:
  [ 17917.759] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [ 17917.759] (EE) 
  [ 17917.759] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 17917.759] (EE) Please also check the log file at "/var/log/Xorg.1.log" for 
additional information.
  [ 17917.759] (EE) 
  [ 17917.816] (EE) Server terminated with error (1). Closing log file.

  I'm not facing this issue when I'm not connected to external monitors.
  Any help will be much appretiated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  .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
  Date: Wed Aug 30 18:27:41 2017
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:075b]
  InstallationDate: Installed on 2016-10-06 (328 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=f79f9409-625c-4f78-83af-cf2cf7928690 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.0
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9

[Touch-packages] [Bug 1720892] [NEW] 17.10Beta2. networking.service not available

2017-10-02 Thread holiday

Public bug reported:

tested on lubuntu 17.10B2 and budgie 17.10b2

systemctl list-units
systemctl list-unit-files

Neither includes networking.service.

systemctl status networking.service returns
"Unit networking.service could not be found."

Neither LAN nor internet are accessible

This is available in 17.04 for both tested distros and is necessary for
raising network with NetworkManager removed.

in 17.04, status is active,exited. Both LAN and internet are accessible.

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

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

Title:
  17.10Beta2. networking.service not available

Status in systemd package in Ubuntu:
  New

Bug description:
  tested on lubuntu 17.10B2 and budgie 17.10b2

  systemctl list-units
  systemctl list-unit-files

  Neither includes networking.service.

  systemctl status networking.service returns
  "Unit networking.service could not be found."

  Neither LAN nor internet are accessible

  This is available in 17.04 for both tested distros and is necessary
  for raising network with NetworkManager removed.

  in 17.04, status is active,exited. Both LAN and internet are
  accessible.

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

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

[Touch-packages] [Bug 1720890] [NEW] vulkan-smoketest segfaults steam vulkan games segfault

2017-10-02 Thread Lawrence A Fossi

Public bug reported:

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

$ apt-cache policy mesa-vulkan-drivers
mesa-vulkan-drivers:
  Installed: 17.2.1-0ubuntu1
  Candidate: 17.2.1-0ubuntu1
  Version table:
 *** 17.2.1-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
100 /var/lib/dpkg/status


Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

Open a terminal type vulkan-smoketest instead of a glxgears type window it will 
segfault.
message from kernel.log:
Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
syslog:
Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
It appears that the culprit is an old or broken libvulkan_radeon.so provided by 
mesa-vulkan-drivers.

As a test I renamed the old lib and dropped in a newer version from
oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
Max now work properly in Vulkan mode as well instead of segfaulting.

This issue is also present on Zesty and fixed in both Oibaf's and
Padoka's ppa's since April back when they were rolling 17.2 mesa.

I have no idea if libvulkan_intel.so also needs updating no hardware to
check.

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


** Tags: amd artful mesa steam vulkan zesty

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  New

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

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

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

-- 
Mailing list: https://launchpad.net/~touch-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

2017-10-02 Thread Serhiy Zahoriya

Sorry I didn't test it. Turns out in my case it's Intel drivers

/var/lib/dkms $ grep REMAKE_INITRD * -rF
i915-4.6.3-4.4.0/1/build/dkms.conf:REMAKE_INITRD=yes

-- 
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:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  In Progress
Status in initramfs-tools source package in Xenial:
  New
Status in dkms source package in Zesty:
  In Progress
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@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1720888] Re: package libperl5.24 5.24.1-2ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.24/changelog.Debian.gz', which is different from o

2017-10-02 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libperl5.24 5.24.1-2ubuntu1 failed to install/upgrade: trying
  to overwrite shared '/usr/share/doc/libperl5.24/changelog.Debian.gz',
  which is different from other instances of package libperl5.24:i386

Status in perl package in Ubuntu:
  New

Bug description:
  i dont know

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libperl5.24 5.24.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-36.40-generic 4.10.17
  Uname: Linux 4.10.0-36-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Mon Oct  2 18:12:20 2017
  DuplicateSignature:
   package:libperl5.24:5.24.1-2ubuntu1
   Unpacking libperl5.24:i386 (5.24.1-2ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-zgCg2Q/28-libperl5.24_5.24.1-2ubuntu1_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.24/changelog.Debian.gz', which is different from other 
instances of package libperl5.24:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.24/changelog.Debian.gz', which is different from other 
instances of package libperl5.24:i386
  InstallationDate: Installed on 2017-03-22 (194 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.8
  SourcePackage: perl
  Title: package libperl5.24 5.24.1-2ubuntu1 failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libperl5.24/changelog.Debian.gz', which is 
different from other instances of package libperl5.24:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-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

** Description changed:

+ [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: Bug
- DistroRelease: Ubuntu 15.04
+ 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: all
- SourcePackage: dkms
+ PackageArchitecture: allSourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

** Also affects: dkms (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

** Changed in: dkms (Ubuntu Xenial)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: dkms (Ubuntu Zesty)
 Assignee: (unassigned) => Brian Murray (brian-murray)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  In Progress
Status in initramfs-tools source package in Xenial:
  New
Status in dkms source package in Zesty:
  In Progress
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

[Touch-packages] [Bug 1720888] [NEW] package libperl5.24 5.24.1-2ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.24/changelog.Debian.gz', which is different from

2017-10-02 Thread Mark Grewar

Public bug reported:

i dont know

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libperl5.24 5.24.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-36.40-generic 4.10.17
Uname: Linux 4.10.0-36-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Mon Oct  2 18:12:20 2017
DuplicateSignature:
 package:libperl5.24:5.24.1-2ubuntu1
 Unpacking libperl5.24:i386 (5.24.1-2ubuntu1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-zgCg2Q/28-libperl5.24_5.24.1-2ubuntu1_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libperl5.24/changelog.Debian.gz', 
which is different from other instances of package libperl5.24:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.24/changelog.Debian.gz', which is different from other 
instances of package libperl5.24:i386
InstallationDate: Installed on 2017-03-22 (194 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4.8
SourcePackage: perl
Title: package libperl5.24 5.24.1-2ubuntu1 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.24/changelog.Debian.gz', which is 
different from other instances of package libperl5.24:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package package-conflict zesty

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

Title:
  package libperl5.24 5.24.1-2ubuntu1 failed to install/upgrade: trying
  to overwrite shared '/usr/share/doc/libperl5.24/changelog.Debian.gz',
  which is different from other instances of package libperl5.24:i386

Status in perl package in Ubuntu:
  New

Bug description:
  i dont know

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libperl5.24 5.24.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-36.40-generic 4.10.17
  Uname: Linux 4.10.0-36-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Mon Oct  2 18:12:20 2017
  DuplicateSignature:
   package:libperl5.24:5.24.1-2ubuntu1
   Unpacking libperl5.24:i386 (5.24.1-2ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-zgCg2Q/28-libperl5.24_5.24.1-2ubuntu1_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.24/changelog.Debian.gz', which is different from other 
instances of package libperl5.24:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.24/changelog.Debian.gz', which is different from other 
instances of package libperl5.24:i386
  InstallationDate: Installed on 2017-03-22 (194 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.8
  SourcePackage: perl
  Title: package libperl5.24 5.24.1-2ubuntu1 failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libperl5.24/changelog.Debian.gz', which is 
different from other instances of package libperl5.24:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-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

I found some commonly used dkms packages that do set REMAKE_INITRD.

broadcom-sta-6.30.223.271/debian/broadcom-sta-dkms.dkms:REMAKE_INITRD="YES"
flashcache-3.1.3+git20150701/src/dkms.conf:REMAKE_INITRD=yes
r8168-8.044.02/debian/r8168-dkms.dkms:REMAKE_INITRD="YES"

And zfs sets REMAKE_INITRD sometimes.

-- 
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:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  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: Bug
  DistroRelease: 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: all
  SourcePackage: 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@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1623666] Re: iOS device contents not displayed in Ubuntu

2017-10-02 Thread William F Hammond

I've had success with newly installed 16.04.3 LTS following steps 8 - 11
given in #44 after installing the October 2016 ppa for 16.04 from Martin
Salbaba.  That is, my first 3 steps were:

  sudo add-apt-repository ppa:martin-salbaba/ppa+libimobiledevice
  sudo apt-get update
  sudo apt-get dist-upgrade

After retrieving my photos and before disconnecting the iPhone, I
suggest

  idevicepair  unpair
  fusermount  -u  x (where x is the "mount point").

One more note: I was running the Mate Desktop. When I connected the
(unlocked) iPhone, the program "Shotwell" appeared.  I did not want to
use it. The alternate selection was Caja (Mate's file manager similar to
Nautilus), but Caja was not seeing the phone. (The command lsusb was
seeing the phone.) I selected "unmount" in the requester offering
"Shotwell" just in case Shotwell did have access before I proceeded to
use idevicepair.

I seem to have a solution that is satisfactory for me -- especially
because I want to have command-line access to the photos, and using
idevicepair and ifuse makes the mounted location of the photos quite
explicit to me since I specify the mount point.

I do think, however, that many LTS desktop users will want something
such as what Mate purports to offer.

I also completely fail to understand why Apple thinks that lightening
port access to the small user portion of the iPhone filesystem requires
either SSL or TLS.  (Might this be explained by an alternate route
"through the air"?)

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

Title:
  iOS device contents not displayed in Ubuntu

Status in Libimobiledevice:
  Fix Released
Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice*:

  Vauge discussion that mentions using the latest git HEAD*:
  https://github.com/libimobiledevice/libimobiledevice/issues/327

  *This discussion is quite vague. One comment points out "iOS 10
  devices don't allow SSLv3 anymore but require at least TLSv1", but not
  how or if that has been fixed in libimobiledevice git HEAD.

  This ppa packages the git version and may resolve the issue:
  
https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages

  There are several other upstream reports related to this problem.

  Partial success patch (idevicepair only) trying to keep GnuTLS:
  https://github.com/libimobiledevice/libimobiledevice/issues/413

  Failure with GnuTLS, Success with OpenSSL:
  https://gitlab.com/gnutls/gnutls/issues/145

  Ubuntu packages libimobiledevice with "--disable-openssl":
  https://github.com/libimobiledevice/ifuse/issues/32

  Duplicate bug 1638177 suggests to repackage libimobiledevice using
  OpenSSL to avoid this problem, as per comment 27 below.

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

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

[Touch-packages] [Bug 1644975] Re: Resume from disk (swapfile) fails

2017-10-02 Thread Dirk F

In the latest upstream version 0.130
, the faulty script has been rewritten, with
supporting sourced scripts.

Perhaps a better solution would be for Ubuntu to pull in this version,
and repackage it for Aardvark and LTS releases.

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

Title:
  Resume from disk (swapfile) fails

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

Bug description:
  Well, hibernation with swap file doesn't work while hibernation with
  swap partition works perfectly fine with the exactly same
  configuration and hardware.

  The reason is that when resuming from swap file, initramfs script
  can't correctly detect the machine are hibernated from the last shut
  down.

  And I investigated the issue and found this patch solved
  https://bugs.launchpad.net/ubuntu/+source/initramfs-
  tools/+bug/554009/+attachment/1366060/+files/resume.patch) for the
  hibernate to work.

  And it isn't applied to the package. I'd like to help this is really
  applied to the official package.

  In short, my setup is swapfile inside the system filesystem (LUKS +
  LVM2 + ext4).

  Also, I roughly followed this tutorial to prepare this configurartion
  that: https://ubuntuforums.org/showthread.php?t=1042946

  I've opening this bug because the original bug report is closed and
  getting no response...

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

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

[Touch-packages] [Bug 1720331] Re: Whoopsie continually relaunching

I was able to recreate this but had to move through different options in
the Settings control panel to trigger it e.g. switch from something back
to Privacy. Eventually, switch to the Privacy panel would start the
constant reloading. However, as soon as  I closed the Settings control
panel whoopise quit restarting.

Does closing the control panel stop whoopsie from acting crazy?

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

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

** Tags added: rls-aa-incoming

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

Title:
  Whoopsie continually relaunching

Status in whoopsie package in Ubuntu:
  Triaged

Bug description:
  Today for the first time, and coincidentally looking for a different
  setting, I went to the Settings->Privacy dialogue. I was also
  (coincidentally for a different reason, relating to #1720149) already
  tailing /var/log/syslog to a terminal.

  Immediately on opening that dialogue, the syslog tail flooded with
  whoopsie continually relaunching, causing enough work to raise the fan
  speeds. This is a representative section from towards the end of me
  letting it, before I killed the service, with some necessary
  viciousness. Specifically

  systemctl stop whoopsie
  (didn't stop it)
  systemctl disable whoopsie
  (didn't stop it)
  (find pid for whoopsie's root process and kill it)
  (that stopped it)

  Also for good measure ensured the automatic bug reporting option in
  the privacy settings dialog was set to manual, which I think was done
  anyway when I disabled whoopsie, though the dialog wasn't on top at
  the time for me to be sure. It had been set to automatic when I first
  opened the dialog.

  Snippet from syslog attached. It was just repeating this continually
  for several minutes before I stopped it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: whoopsie 0.2.58
  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-0ubuntu1
  Architecture: amd64
  CrashReports:
   664:1000:119:0:2017-09-25 18:16:58.760134901 +0100:2017-09-25 
18:16:58.760134901 +0100:/var/crash/_opt_google_chrome_chrome.1000.upload
   640:1000:119:102847031:2017-09-27 20:28:45.352315425 +0100:2017-09-28 
09:02:32.195212507 +0100:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:119:34020328:2017-09-25 18:16:57.656132936 +0100:2017-09-25 
18:16:58.760134901 +0100:/var/crash/_opt_google_chrome_chrome.1000.crash
   600:111:119:0:2017-09-25 18:16:59.348145502 +0100:2017-09-25 
18:16:59.348145502 +0100:/var/crash/_opt_google_chrome_chrome.1000.uploaded
  CurrentDesktop: GNOME
  Date: Fri Sep 29 10:00:34 2017
  InstallationDate: Installed on 2017-07-30 (60 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions: apport-noui N/A
  SourcePackage: whoopsie
  UpgradeStatus: Upgraded to artful on 2017-08-22 (37 days ago)

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

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

[Touch-packages] [Bug 1714429] Re: hang on shutdown with static network configuration

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

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

Title:
  hang on shutdown with static network configuration

Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  Hi Folks


  Problem:

  system doesn't reboot/shutdown but *only* when the network
  configuration is static (described below). When I change the network
  configuration to dhcp, the bug doesn't occur.


  The network configuration is set to static:

  iface eth0 inet static
address my_ip
netmask 255.255.255.224
gateway router_ip
dns-nameservers primary_dns secondary_dns 8.8.8.8 8.8.4.4
  (I have masked some configuration values)


  lsb_release -rd
  Release:16.04


  apt-cache policy unattended-upgrades
  Installed: 0.90ubuntu0.7
  Candidate: 0.90ubuntu0.7


  symptoms:

  a python3 process appears ~2sec after the shutdown command: 2005
  python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown

  Screenshot of the VM virtual display output as attachment.

  only / is mounted, all other file systems are unmounted already:
  /boot, /var, /tmp, /var/log, /var/tmp


  other informations:

  The network still works. I can ping different addresses like
  google.com, debian.org, and other stuff.

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

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

[Touch-packages] [Bug 1713226] Re: systemd-networkd messes up networking

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nplan (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/1713226

Title:
  systemd-networkd messes up networking

Status in ifupdown package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in nplan package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Since systemd-234-2ubuntu8 systemd-networkd is enabled by default.

  This causes problems existing configurations
  ex1: if the network has ipv6 enables (the host recieves a router 
advertisement), networkmanager does not configure the network anymore so you 
get only ipv6 and no ipv4 connections (since systemd-networkd seems to bring 
only the link up)

  ex2: if you use systemd-nspawn and configured static ip addresses in
  /etc/network/interfaces, systemd-networkd adds a dhcp obtained address
  on the host0 adapter and a 169.254 address

  For the average user both is not expected, so my solution was
  systemctl disable systemd-networkd, but since you seem to insist
  having this enabled, it must be made sure systemd-networkd does not
  touch existing configurations.

  My suggestion is:
  1) if /etc/network/interfaces contains anything other than lo -> do not 
enable systemd-networkd
  2) if network-manager is enabled, systemd-networkd must be disabled and vice 
versa

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

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

[Touch-packages] [Bug 1713226] Re: systemd-networkd messes up networking

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

Title:
  systemd-networkd messes up networking

Status in ifupdown package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in nplan package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Since systemd-234-2ubuntu8 systemd-networkd is enabled by default.

  This causes problems existing configurations
  ex1: if the network has ipv6 enables (the host recieves a router 
advertisement), networkmanager does not configure the network anymore so you 
get only ipv6 and no ipv4 connections (since systemd-networkd seems to bring 
only the link up)

  ex2: if you use systemd-nspawn and configured static ip addresses in
  /etc/network/interfaces, systemd-networkd adds a dhcp obtained address
  on the host0 adapter and a 169.254 address

  For the average user both is not expected, so my solution was
  systemctl disable systemd-networkd, but since you seem to insist
  having this enabled, it must be made sure systemd-networkd does not
  touch existing configurations.

  My suggestion is:
  1) if /etc/network/interfaces contains anything other than lo -> do not 
enable systemd-networkd
  2) if network-manager is enabled, systemd-networkd must be disabled and vice 
versa

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

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

[Touch-packages] [Bug 1713226] Re: systemd-networkd messes up networking

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ifupdown (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/1713226

Title:
  systemd-networkd messes up networking

Status in ifupdown package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in nplan package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Since systemd-234-2ubuntu8 systemd-networkd is enabled by default.

  This causes problems existing configurations
  ex1: if the network has ipv6 enables (the host recieves a router 
advertisement), networkmanager does not configure the network anymore so you 
get only ipv6 and no ipv4 connections (since systemd-networkd seems to bring 
only the link up)

  ex2: if you use systemd-nspawn and configured static ip addresses in
  /etc/network/interfaces, systemd-networkd adds a dhcp obtained address
  on the host0 adapter and a 169.254 address

  For the average user both is not expected, so my solution was
  systemctl disable systemd-networkd, but since you seem to insist
  having this enabled, it must be made sure systemd-networkd does not
  touch existing configurations.

  My suggestion is:
  1) if /etc/network/interfaces contains anything other than lo -> do not 
enable systemd-networkd
  2) if network-manager is enabled, systemd-networkd must be disabled and vice 
versa

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

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

[Touch-packages] [Bug 1713226] Re: systemd-networkd messes up networking

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: network-manager (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/1713226

Title:
  systemd-networkd messes up networking

Status in ifupdown package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in nplan package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Since systemd-234-2ubuntu8 systemd-networkd is enabled by default.

  This causes problems existing configurations
  ex1: if the network has ipv6 enables (the host recieves a router 
advertisement), networkmanager does not configure the network anymore so you 
get only ipv6 and no ipv4 connections (since systemd-networkd seems to bring 
only the link up)

  ex2: if you use systemd-nspawn and configured static ip addresses in
  /etc/network/interfaces, systemd-networkd adds a dhcp obtained address
  on the host0 adapter and a 169.254 address

  For the average user both is not expected, so my solution was
  systemctl disable systemd-networkd, but since you seem to insist
  having this enabled, it must be made sure systemd-networkd does not
  touch existing configurations.

  My suggestion is:
  1) if /etc/network/interfaces contains anything other than lo -> do not 
enable systemd-networkd
  2) if network-manager is enabled, systemd-networkd must be disabled and vice 
versa

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

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

[Touch-packages] [Bug 1623666] Re: iOS device contents not displayed in Ubuntu

2017-10-02 Thread William F Hammond

#47: When you say you are using the regular packaged versions, am I
correct in thinking that you are speaking about an updated Ubuntu 17.04?

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

Title:
  iOS device contents not displayed in Ubuntu

Status in Libimobiledevice:
  Fix Released
Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice*:

  Vauge discussion that mentions using the latest git HEAD*:
  https://github.com/libimobiledevice/libimobiledevice/issues/327

  *This discussion is quite vague. One comment points out "iOS 10
  devices don't allow SSLv3 anymore but require at least TLSv1", but not
  how or if that has been fixed in libimobiledevice git HEAD.

  This ppa packages the git version and may resolve the issue:
  
https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages

  There are several other upstream reports related to this problem.

  Partial success patch (idevicepair only) trying to keep GnuTLS:
  https://github.com/libimobiledevice/libimobiledevice/issues/413

  Failure with GnuTLS, Success with OpenSSL:
  https://gitlab.com/gnutls/gnutls/issues/145

  Ubuntu packages libimobiledevice with "--disable-openssl":
  https://github.com/libimobiledevice/ifuse/issues/32

  Duplicate bug 1638177 suggests to repackage libimobiledevice using
  OpenSSL to avoid this problem, as per comment 27 below.

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

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

[Touch-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root

2017-10-02 Thread Joseph Salisbury

I built a Xenial test kernel with a pick of commit  37091fd. The test
kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp696435/

To test the kernel, be sure to install both the linux-image and linux-
image-extra .deb packages.

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

Title:
  wait-for-root fails to detect nbd root

Status in linux package in Ubuntu:
  Fix Released
Status in nbd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  Incomplete

Bug description:
  When using an nbd root, wait-for-root blocks for 30 seconds before
  booting continues successfully.

  Using Ubuntu Natty, related packages versions:
  nbd-client 1:2.9.16-6ubuntu1 
  initramfs-tools 0.98.1ubuntu9

  The wait-for-root call from /usr/share/initramfs-tools/scripts/local:
while [ -z "${FSTYPE}" ]; do
FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})

# Run failure hooks, hoping one of them can fix up the system
# and we can restart the wait loop.  If they all fail, abort
# and move on to the panic handler and shell.
if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
break
fi
done

  I replaced wait-for-root with a sh script that did `set >&2`, here are the 
relevant environment variables at the time wait-for-root was called:
  ROOT='/dev/nbd0'
  ROOTDELAY=''
  ROOTFLAGS=''
  ROOTFSTYPE=''
  nbdroot='192.168.0.1,2011'

  It's probably worth noting that "nbd0: unknown partition table" was
  displayed asynchronously 1-2 seconds after wait-for-root was invoked
  and while it was still waiting. But I tried adding a "sleep 5" as the
  last line of local-top/nbd, so that the nbd message was displayed a
  lot before wait-for-root was called, and it didn't make a difference.
  So I don't think a race condition is involved in this problem.

  Temporarily I'm passing rootdelay=1 in the kernel command line to work
  around the problem.

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

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

[Touch-packages] [Bug 1707929] Re: [FFe] Revert blacklisting of Indic layouts

2017-10-02 Thread Gunnar Hjalmarsson

Proposed upload is available in this PPA:

https://launchpad.net/~gunnarhj/+archive/ubuntu/xkeyboard-config

** Changed in: xkeyboard-config (Ubuntu)
   Status: Triaged => In Progress

** Changed in: xkeyboard-config (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  [FFe] Revert blacklisting of Indic layouts

Status in xkeyboard-config:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  In Progress
Status in xkeyboard-config package in Debian:
  Fix Released

Bug description:
  In xkeyboard-config 2.19-1 several Indic keyboard layouts were moved
  to "extras".

  https://cgit.freedesktop.org/xkeyboard-config/commit/?id=913af7

  The measure has been criticized and has been reverted afterwards at
  both freedesktop.org and Debian. We should make sure it's reverted in
  Ubuntu 17.10 as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1707929/+subscriptions

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

[Touch-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root

2017-10-02 Thread Joseph Salisbury

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: Canonical Kernel (canonical-kernel) => Joseph Salisbury 
(jsalisbury)

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

Title:
  wait-for-root fails to detect nbd root

Status in linux package in Ubuntu:
  Fix Released
Status in nbd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  Incomplete

Bug description:
  When using an nbd root, wait-for-root blocks for 30 seconds before
  booting continues successfully.

  Using Ubuntu Natty, related packages versions:
  nbd-client 1:2.9.16-6ubuntu1 
  initramfs-tools 0.98.1ubuntu9

  The wait-for-root call from /usr/share/initramfs-tools/scripts/local:
while [ -z "${FSTYPE}" ]; do
FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})

# Run failure hooks, hoping one of them can fix up the system
# and we can restart the wait loop.  If they all fail, abort
# and move on to the panic handler and shell.
if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
break
fi
done

  I replaced wait-for-root with a sh script that did `set >&2`, here are the 
relevant environment variables at the time wait-for-root was called:
  ROOT='/dev/nbd0'
  ROOTDELAY=''
  ROOTFLAGS=''
  ROOTFSTYPE=''
  nbdroot='192.168.0.1,2011'

  It's probably worth noting that "nbd0: unknown partition table" was
  displayed asynchronously 1-2 seconds after wait-for-root was invoked
  and while it was still waiting. But I tried adding a "sleep 5" as the
  last line of local-top/nbd, so that the nbd message was displayed a
  lot before wait-for-root was called, and it didn't make a difference.
  So I don't think a race condition is involved in this problem.

  Temporarily I'm passing rootdelay=1 in the kernel command line to work
  around the problem.

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

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

[Touch-packages] [Bug 1720519] Re: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.

2017-10-02 Thread David Eichelsdörfer

had the same problem and could only fix it by removing the line
load-module module-switch-on-connect
from
/etc/pulse/default.pa

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

Title:
  Module "module-switch-on-connect" should be loaded once at most.
  Refusing to load.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Pulseaudio daemon does not start after the update to Kubuntu 17.10
  beta2, because the module fails to load although it is there.

  From 'pulseaudio -vv'

  E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded 
once at most. Refusing to load.
  E: [pulseaudio] main.c: Module load failed.
  E: [pulseaudio] main.c: Failed to initialize daemon.

  PS sorry I am not a seasoned bug reporter. Let me know if I can
  provide more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ben2809 F...m chrome
   /dev/snd/controlC0:  ben2809 F chrome
   /dev/snd/timer:  ben2809 f chrome
  CurrentDesktop: KDE
  Date: Sat Sep 30 11:20:55 2017
  InstallationDate: Installed on 2017-04-07 (175 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: B150M-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

-- 
Mailing list: https://launchpad.net/~touch-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

My testing indicates that the .old-dkms files are only created if
"remake_initrd" is yes in /usr/sbin/dkms and that is controlled by
"REMAKE_INITRD" in a dkms.conf file.  From what I can tell most
dkms.conf files do not contain the REMAKE_INITRD option. So I don't
think this effects a lot of people.

-- 
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:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  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: Bug
  DistroRelease: 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: all
  SourcePackage: 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@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1719851] Re: ca-certificates isn't updated in LTS 16.04

2017-10-02 Thread Marc Deslauriers

Both. The new bundle added some new CAs, and also removed CAs that
Mozilla has deemed no longer trustworthy or have requested to be
removed.

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

Title:
  ca-certificates isn't updated in LTS 16.04

Status in ca-certificates package in Ubuntu:
  Fix Released
Status in ca-certificates source package in Trusty:
  Fix Released
Status in ca-certificates source package in Xenial:
  Fix Released
Status in ca-certificates source package in Zesty:
  Fix Released
Status in ca-certificates source package in Artful:
  Fix Released

Bug description:
  ca-certificates should contain root certificates for new CA from
  Amazon

  They are added in version 20170717, The Artful Aardvark (pre-release freeze) 
  But that isn't reflected neither in zesty, nor backports or security

  We recently got a letter from Amazon to update our SSL certs till
  October 25. Would be extremely great if ca-certificates will be
  updated via unattended upgrades in-time.

  Marking as security, because several CAs were removed (compromised?).
  Or maybe there is a reason, why root cert list isn't updated on LTS releases?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ca-certificates 20161130
  ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Wed Sep 27 11:10:01 2017
  Ec2AMI: ami-6edd3078
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: m3.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  SourcePackage: ca-certificates
  UpgradeStatus: Upgraded to zesty on 2017-05-19 (131 days ago)

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

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

[Touch-packages] [Bug 1719851] Re: ca-certificates isn't updated in LTS 16.04

2017-10-02 Thread David Glasser

I just saw this via the USN. I'm having trouble evaluating the urgency
of this fix.

Is the issue:

- Without this, connecting to some sites will fail because of
missing/lapsed CAs

or

- Without this, you'll probably get MITMed because you're trusting some
insecure hacked CAs

?

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

Title:
  ca-certificates isn't updated in LTS 16.04

Status in ca-certificates package in Ubuntu:
  Fix Released
Status in ca-certificates source package in Trusty:
  Fix Released
Status in ca-certificates source package in Xenial:
  Fix Released
Status in ca-certificates source package in Zesty:
  Fix Released
Status in ca-certificates source package in Artful:
  Fix Released

Bug description:
  ca-certificates should contain root certificates for new CA from
  Amazon

  They are added in version 20170717, The Artful Aardvark (pre-release freeze) 
  But that isn't reflected neither in zesty, nor backports or security

  We recently got a letter from Amazon to update our SSL certs till
  October 25. Would be extremely great if ca-certificates will be
  updated via unattended upgrades in-time.

  Marking as security, because several CAs were removed (compromised?).
  Or maybe there is a reason, why root cert list isn't updated on LTS releases?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ca-certificates 20161130
  ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Wed Sep 27 11:10:01 2017
  Ec2AMI: ami-6edd3078
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: m3.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  SourcePackage: ca-certificates
  UpgradeStatus: Upgraded to zesty on 2017-05-19 (131 days ago)

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

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

[Touch-packages] [Bug 1720116] Re: apport-gtk sigfault in libgtk-3

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

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

Title:
  apport-gtk sigfault in libgtk-3

Status in apport package in Ubuntu:
  New

Bug description:
  Daily notification of system error and request to report it but
  nothing get sent.  Syslog shows apport-gtk sigfault in libgtk-3.
  There us usually no crash dump generated.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashReports: 640:0:119:6940216:2017-09-22 05:36:31.895203406 
-0400:2017-09-22 05:36:27.979332060 
-0400:/var/crash/_usr_share_apport_apport-gtk.0.crash
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Thu Sep 28 06:54:23 2017
  InstallationDate: Installed on 2017-07-24 (65 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170723)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1720861] [NEW] package python-minimal 2.7.13-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-10-02 Thread Tareq Issa Abufayad

Public bug reported:

Hello There,

This package "python-minimal 2.7.13-2 " crashed my apt-get program
i can't update or upgrade any thing

i will be appreciate if you would help


Thank you

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: python-minimal 2.7.13-2
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Mon Oct  2 17:51:53 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-09-26 (6 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4.6~17.04.1
SourcePackage: python-defaults
Title: package python-minimal 2.7.13-2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python-defaults (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 python-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1720861

Title:
  package python-minimal 2.7.13-2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in python-defaults package in Ubuntu:
  New

Bug description:
  Hello There,

  This package "python-minimal 2.7.13-2 " crashed my apt-get program
  i can't update or upgrade any thing

  i will be appreciate if you would help

  
  Thank you

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python-minimal 2.7.13-2
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Mon Oct  2 17:51:53 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-09-26 (6 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: python-defaults
  Title: package python-minimal 2.7.13-2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1718029] Re: cloudstack and azure datasources broken when using netplan/systemd-networkd

** Merge proposal linked:
   https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/331664

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

Title:
  cloudstack and azure datasources broken when using netplan/systemd-
  networkd

Status in netplan:
  Invalid
Status in cloud-init package in Ubuntu:
  In Progress
Status in nplan package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu artful, cloud-init renders network configuration through netplan.
  This means that there is no dhclient and thus no /var/lib/dhclient/*.leases.

  Azure and CloudStack both are reading those leases file to get useful
  information about the platform.

  Specifically:
   * Azure reads option-245 from the dhclient response to find the IP address 
of the metadata service.
   * CloudStack reads the 'dhcp-server-identifier' option in the dhclient 
response to get the address of the virtual router (metadata service). [1]

  In ubuntu this happens to be done with systemd-networkd, so cloud-init
  can possibly probably interact over the dbus with systemd-networkd to
  get information.  However that is less than ideal, as ultimately
  cloud-init should not need to know that it systemd-networkd is
  involved.  It should be hidden via netplan.  So there should be an
  interface to get current networking configuratoin information from
  netplan including dhcp lease response info.

  
  --
  [1] 
http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.8/virtual_machines/user-data.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: cloud-init 0.7.9-280-ge626966e-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CloudName: Amazon - Ec2
  Date: Mon Sep 18 19:56:40 2017
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: cloud-init
  UpgradeStatus: No upgrade log present (probably fresh install)
  user_data.txt:
   #cloud-config
   {}

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

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

[Touch-packages] [Bug 1717309] Re: 17.10 Artful Aardvark Mascot

2017-10-02 Thread Will Cooke

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

** Changed in: ubuntu-themes
   Status: New => Fix Released

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

Title:
  17.10 Artful Aardvark Mascot

Status in Ubuntu theme:
  Fix Released
Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  Aardvark attached.

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

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

[Touch-packages] [Bug 1701780] Re: GTK file chooser shows entries from /sys, /dev, etc.

** Tags added: gtk

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

Title:
  GTK file chooser shows entries from /sys, /dev, etc.

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  On Kubuntu 17.10 Alpha 1, the GTK file chooser shows several unwanted
  entries from /sys, /dev, etc. For me, this occurs in the GTK3 file
  chooser opened from Firefox, GNOME Disks, etc. At the time of writing,
  I haven't tested whether it occurs in the GTK2 chooser as well. I have
  attached a screenshot showing the problem.

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

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

[Touch-packages] [Bug 1719851] Re: ca-certificates isn't updated in LTS 16.04

2017-10-02 Thread Marc Deslauriers

The ca-certificates package has been updated for all releases:

https://usn.ubuntu.com/usn/usn-3432-1/

Marking bug as Fix Released. Thanks!

** Changed in: ca-certificates (Ubuntu Trusty)
   Status: New => Fix Released

** Changed in: ca-certificates (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: ca-certificates (Ubuntu Zesty)
   Status: New => Fix Released

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

Title:
  ca-certificates isn't updated in LTS 16.04

Status in ca-certificates package in Ubuntu:
  Fix Released
Status in ca-certificates source package in Trusty:
  Fix Released
Status in ca-certificates source package in Xenial:
  Fix Released
Status in ca-certificates source package in Zesty:
  Fix Released
Status in ca-certificates source package in Artful:
  Fix Released

Bug description:
  ca-certificates should contain root certificates for new CA from
  Amazon

  They are added in version 20170717, The Artful Aardvark (pre-release freeze) 
  But that isn't reflected neither in zesty, nor backports or security

  We recently got a letter from Amazon to update our SSL certs till
  October 25. Would be extremely great if ca-certificates will be
  updated via unattended upgrades in-time.

  Marking as security, because several CAs were removed (compromised?).
  Or maybe there is a reason, why root cert list isn't updated on LTS releases?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ca-certificates 20161130
  ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Wed Sep 27 11:10:01 2017
  Ec2AMI: ami-6edd3078
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: m3.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  SourcePackage: ca-certificates
  UpgradeStatus: Upgraded to zesty on 2017-05-19 (131 days ago)

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

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

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

2017-10-02 Thread Steve Beattie

** Information type changed from Private to Public

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

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

Status in ibus package in Ubuntu:
  New

Bug description:
  Email me if you have any questions.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: ibus 1.5.14-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Wed Sep 27 12:15:48 2017
  ExecutablePath: /usr/lib/ibus/ibus-x11
  InstallationDate: Installed on 2017-03-14 (199 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170612)
  ProcCmdline: /usr/lib/ibus/ibus-x11 --kill-daemon
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f6690efc1c8 <__cxa_finalize+40>:mov
0x8(%r14),%rax
   PC (0x7f6690efc1c8) ok
   source "0x8(%r14)" (0x0048) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   __cxa_finalize (d=0x7f668d3dafd0) at cxa_finalize.c:39
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
   ?? ()
   _dl_fini () at dl-fini.c:235
  Title: ibus-x11 crashed with SIGSEGV in __cxa_finalize()
  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/ibus/+bug/1720419/+subscriptions

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

[Touch-packages] [Bug 1720848] [NEW] [a11y] No border around focused listbox rows

Public bug reported:

Ubuntu 17.10 Beta
light-themes 16.10+17.10.20170930-0ubuntu1
gnome-control-center 1:3.26.0-0ubuntu3

I originally reported this to GNOME but it looks like a theming issue
with Ubuntu's default theme Ambiance.

Impact
==
It is very difficult to enable Mouse Keys if you have a working keyboard but 
not a mouse or touchpad or similar pointing device.

Test Case
=
Open the Settings app (gnome-control-center)
Press Shift-Tab.
Then use the arrow keys to scroll down to Universal Access.
Press Enter to load the Universal Access panel
Press the right arrow to switch the focus to the Universal Access panel.
Press the down arrow several times to scroll down the page. The page scrolls 
down and you can select individual elements with the Enter key. But the bug is 
that you can't visually tell which element is focused.

Alternate Test Case
===
Switch your theme to Adwaita by running in a terminal:
gsettings set org.gnome.desktop.interface gtk-theme 'Adwaita'

Now follow the steps in the Test Case.
With the Adwaita theme, the listbox rows have a dotted border around them so 
you can visually tell which element is focused.

To change your theme back to the default, run
gsettings reset org.gnome.desktop.interface gtk-theme

** Affects: ubuntu-themes (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: a11y

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

Title:
  [a11y] No border around focused listbox rows

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10 Beta
  light-themes 16.10+17.10.20170930-0ubuntu1
  gnome-control-center 1:3.26.0-0ubuntu3

  I originally reported this to GNOME but it looks like a theming issue
  with Ubuntu's default theme Ambiance.

  Impact
  ==
  It is very difficult to enable Mouse Keys if you have a working keyboard but 
not a mouse or touchpad or similar pointing device.

  Test Case
  =
  Open the Settings app (gnome-control-center)
  Press Shift-Tab.
  Then use the arrow keys to scroll down to Universal Access.
  Press Enter to load the Universal Access panel
  Press the right arrow to switch the focus to the Universal Access panel.
  Press the down arrow several times to scroll down the page. The page scrolls 
down and you can select individual elements with the Enter key. But the bug is 
that you can't visually tell which element is focused.

  Alternate Test Case
  ===
  Switch your theme to Adwaita by running in a terminal:
  gsettings set org.gnome.desktop.interface gtk-theme 'Adwaita'

  Now follow the steps in the Test Case.
  With the Adwaita theme, the listbox rows have a dotted border around them so 
you can visually tell which element is focused.

  To change your theme back to the default, run
  gsettings reset org.gnome.desktop.interface gtk-theme

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

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

[Touch-packages] [Bug 1572244] Re: Kubuntu requires that the WiFi password be entered twice before WiFi can be used

Added plasma-nm as affected package. I think it may be more of an issue
with KDE/Plasma than NetworkManager itself, since it only affects
Kubuntu and not other *buntu editions which also use NetworkManager.

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

Title:
  Kubuntu requires that the WiFi password be entered twice before WiFi
  can be used

Status in network-manager package in Ubuntu:
  Confirmed
Status in plasma-nm package in Ubuntu:
  New

Bug description:
  Kubuntu 16.04 ISO number 20160417.1 Xenial Final
  Bug reported against network-manager 
  Every time I tried the live Kubuntu 16.04 image on a Lenovo t420 laptop it 
requires to enter the wifi password twice before I can use the wifi. Once from 
the network icon panel, then second time a prompt on the desktop to enter the 
wifi password.

  I do not know if this is typical behavior of Kubuntu since I usually use GTK 
base desktops.
  I guess network-manager is the right package to file this report against.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.373
  CurrentDesktop: KDE
  Date: Tue Apr 19 16:48:02 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.77.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.77.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.77.128  
metric 600
  LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  802-11-wireless  
1461084315  Tue 19 Apr 2016 04:45:15 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/3 
   Wired connection 1  4957fbd0-8ffa-4de8-aa18-275e6dfdcd9e  802-3-ethernet   
1461077415  Tue 19 Apr 2016 02:50:15 PM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  --  --
 --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1572244] Re: Kubuntu requires that the WiFi password be entered twice before WiFi can be used

Can we please have some information on this/how to make it work
correctly? It is now about a year and a half since this bug was
reported.

** Tags added: artful kubuntu

** Also affects: plasma-nm (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Kubuntu requires that the WiFi password be entered twice before WiFi
  can be used

Status in network-manager package in Ubuntu:
  Confirmed
Status in plasma-nm package in Ubuntu:
  New

Bug description:
  Kubuntu 16.04 ISO number 20160417.1 Xenial Final
  Bug reported against network-manager 
  Every time I tried the live Kubuntu 16.04 image on a Lenovo t420 laptop it 
requires to enter the wifi password twice before I can use the wifi. Once from 
the network icon panel, then second time a prompt on the desktop to enter the 
wifi password.

  I do not know if this is typical behavior of Kubuntu since I usually use GTK 
base desktops.
  I guess network-manager is the right package to file this report against.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.373
  CurrentDesktop: KDE
  Date: Tue Apr 19 16:48:02 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.77.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.77.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.77.128  
metric 600
  LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  802-11-wireless  
1461084315  Tue 19 Apr 2016 04:45:15 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/3 
   Wired connection 1  4957fbd0-8ffa-4de8-aa18-275e6dfdcd9e  802-3-ethernet   
1461077415  Tue 19 Apr 2016 02:50:15 PM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  --  --
 --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1720404] Re: package ntp 1:4.2.8p4+dfsg-3ubuntu5.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-10-02 Thread Joshua Powers

>From log:

insserv: Starting panasoniclpd-init depends on plymouth and therefore on
system facility `$all' which can not be true!

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

Title:
  package ntp 1:4.2.8p4+dfsg-3ubuntu5.7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  something to do with installing the driver for the printer and scanner
  Panasonic KX-MB2110.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.7
  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: Fri Sep 29 15:50:02 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-15 (288 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic 
root=UUID=a784bf3c-f5a1-4b14-9c07-22b064da1362 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1720404] Re: package ntp 1:4.2.8p4+dfsg-3ubuntu5.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-10-02 Thread Joshua Powers

Thanks for taking the time to file a bug!

It looks like your panasoniclpd-init file in /etc/init.d/lacks an LSB
header defining its dependencies. You can move this init script aside or
add an LSB header to that script to make it compatible again.

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

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

Title:
  package ntp 1:4.2.8p4+dfsg-3ubuntu5.7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  something to do with installing the driver for the printer and scanner
  Panasonic KX-MB2110.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.7
  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: Fri Sep 29 15:50:02 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-15 (288 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic 
root=UUID=a784bf3c-f5a1-4b14-9c07-22b064da1362 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1720838] Re: Nvidia gnome control center scale gets overridden on reboot

2017-10-02 Thread Thomas Cross

** Description changed:

- Hi,
- 
- When I set the scale to 200% on ubuntu 17.10 Beta 2 it sets it correctly for 
my session.
+ When I set the scale to 200% on Ubuntu 17.10 Beta 2 it sets it correctly for 
my session.
  If I reboot then the scale is reset back to 100% but the value on the control 
center "displays" section shows "200%".
  
  To work around it I save the scale to 100% then save it back to 200%.
  After rebooting I have to do this every time.
  
  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
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.82  Wed Jul 19 21:16:49 
PDT 2017
-  GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-7ubuntu1)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.82  Wed Jul 19 21:16:49 
PDT 2017
+  GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-7ubuntu1)
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  BootLog:
-  
+ 
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  2 11:34:59 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
-  bbswitch, 0.8, 4.13.0-12-generic, x86_64: installed
-  nvidia-375, 375.82, 4.13.0-12-generic, x86_64: installed
+  bbswitch, 0.8, 4.13.0-12-generic, x86_64: installed
+  nvidia-375, 375.82, 4.13.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 
[VGA controller])
-Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:2230]
+  NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 
[VGA controller])
+    Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:2230]
  InstallationDate: Installed on 2017-10-02 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20ENCTO1WW
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=84fbf9ab-353c-4dad-8f4b-4f55ea991033 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET70W (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ENCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET70W(1.43):bd07/12/2017:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20ENCTO1WW
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.82-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.1-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.1-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct  2 11:32:23 2017
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  
+ 
  xserver.version: 2:1.19.3-1ubuntu6

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

Title:
  Nvidia gnome control center scale gets overridden on reboot

Status in xorg package in Ubuntu:
  New

Bug description:
  When I set the scale to 200% on Ubuntu 17.10 Beta 2 it sets it correctly for 
my session.
  If I reboot then the scale is reset back to 100% but the value on the control 
center "displays" section shows "200%".

  To work around it I save the scale to 100% then save it back to 200%.
  After rebooting I have to do this every time.

  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

[Touch-packages] [Bug 1701780] Re: GTK file chooser shows entries from /sys, /dev, etc.

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

** Tags removed: gnome-17.10
** Tags added: artful kubuntu-17.10

** Tags removed: kubuntu-17.10
** Tags added: kubuntu

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

Title:
  GTK file chooser shows entries from /sys, /dev, etc.

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  On Kubuntu 17.10 Alpha 1, the GTK file chooser shows several unwanted
  entries from /sys, /dev, etc. For me, this occurs in the GTK3 file
  chooser opened from Firefox, GNOME Disks, etc. At the time of writing,
  I haven't tested whether it occurs in the GTK2 chooser as well. I have
  attached a screenshot showing the problem.

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

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

[Touch-packages] [Bug 1720828] Re: Outline effect should be disabled for tabs

I can duplicate this in the Settings > Sound panel with Ubuntu 17.10
Beta. The easiest way is to click an already selected tab.

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Confirmed

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

Title:
  Outline effect should be disabled for tabs

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  When opening System Settings -> Appearance, for instance, the selected
  tab has by default an orange outline effect that I don't think should
  be displayed for tabs at all.

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

-- 
Mailing list: https://launchpad.net/~touch-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

2017-10-02 Thread Joshua Powers

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

-- 
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 1720838] [NEW] Nvidia gnome control center scale gets overridden on reboot

2017-10-02 Thread Thomas Cross

Public bug reported:

When I set the scale to 200% on Ubuntu 17.10 Beta 2 it sets it correctly for my 
session.
If I reboot then the scale is reset back to 100% but the value on the control 
center "displays" section shows "200%".

To work around it I save the scale to 100% then save it back to 200%.
After rebooting I have to do this every time.

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
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.82  Wed Jul 19 21:16:49 
PDT 2017
 GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-7ubuntu1)
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
BootLog:

CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct  2 11:34:59 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.13.0-12-generic, x86_64: installed
 nvidia-375, 375.82, 4.13.0-12-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:2230]
InstallationDate: Installed on 2017-10-02 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
MachineType: LENOVO 20ENCTO1WW
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=84fbf9ab-353c-4dad-8f4b-4f55ea991033 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/12/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1EET70W (1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20ENCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET70W(1.43):bd07/12/2017:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P50
dmi.product.name: 20ENCTO1WW
dmi.product.version: ThinkPad P50
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.82-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.1-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.1-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Oct  2 11:32:23 2017
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.19.3-1ubuntu6

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


** Tags: amd64 apport-bug artful ubuntu

** Attachment added: "Screenshot from 2017-10-02 11-38-01.png"
   
https://bugs.launchpad.net/bugs/1720838/+attachment/4960570/+files/Screenshot%20from%202017-10-02%2011-38-01.png

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

Title:
  Nvidia gnome control center scale gets overridden on reboot

Status in xorg package in Ubuntu:
  New

Bug description:
  When I set the scale to 200% on Ubuntu 17.10 Beta 2 it sets it correctly for 
my session.
  If I reboot then the scale is reset back to 100% but the value on the control 
center "displays" section shows "200%".

  To work around it I save the scale to 100% then save it back to 200%.
  After rebooting I have to do this every time.

  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
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.82  Wed Jul 19 21:16:49 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-7ubuntu1)
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  BootLog:

  CompositorRunning: None
  CurrentDesktop:

[Touch-packages] [Bug 1720834] [NEW] Insufficient padding in horizontal panes causes a resize of the panes when alternating between toggle buttons

2017-10-02 Thread Danilo Cominotti Marques

Public bug reported:

In Ubuntu Software, when clicking on "Updates", the horizontal pane that
holds the buttons "All", "Installed," and "Updates" gets resized
vertically in order to accommodate the "Refresh" button that gets shown
in the "Updates" section, which causes a small visual glitch.

The same effect happens in System Monitor when alternating between the
"Processes" section and "Resources" and/or "Filesystem."

** Affects: ubuntu-themes (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Insufficient padding in horizontal panes causes a resize of the panes
  when alternating between toggle buttons

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  In Ubuntu Software, when clicking on "Updates", the horizontal pane
  that holds the buttons "All", "Installed," and "Updates" gets resized
  vertically in order to accommodate the "Refresh" button that gets
  shown in the "Updates" section, which causes a small visual glitch.

  The same effect happens in System Monitor when alternating between the
  "Processes" section and "Resources" and/or "Filesystem."

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

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

[Touch-packages] [Bug 1720828] [NEW] Outline effect should be disabled for tabs

2017-10-02 Thread Danilo Cominotti Marques

Public bug reported:

When opening System Settings -> Appearance, for instance, the selected
tab has by default an orange outline effect that I don't think should be
displayed for tabs at all.

** Affects: ubuntu-themes (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "tabs.png"
   https://bugs.launchpad.net/bugs/1720828/+attachment/4960555/+files/tabs.png

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

Title:
  Outline effect should be disabled for tabs

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  When opening System Settings -> Appearance, for instance, the selected
  tab has by default an orange outline effect that I don't think should
  be displayed for tabs at all.

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

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

[Touch-packages] [Bug 1720827] [NEW] Tab selection shouldn't have a "resize" effect

2017-10-02 Thread Danilo Cominotti Marques

Public bug reported:

When alternating between tabs in Systems Settings -> Sound, for
instance, we can notice that the tabs get resized after a tab is
selected, which looks like a small visual glitch.

** Affects: ubuntu-themes (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Tab selection shouldn't have a "resize" effect

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  When alternating between tabs in Systems Settings -> Sound, for
  instance, we can notice that the tabs get resized after a tab is
  selected, which looks like a small visual glitch.

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

-- 
Mailing list: https://launchpad.net/~touch-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

verification is done for the systemd portion of the bug.

-- 
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:
  Triaged
Status in systemd source package in Xenial:
  Fix Committed
Status in nplan source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  In Progress
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 1709135] Re: add bond primary parameter

Installed nplan 0.29 from artful to get it process the test-case yaml,
to then test networkd portion is working right.

Using:
# cat /etc/netplan/bond-primary.yaml
network:
  version: 2
  ethernets:
eth0:
  match:
name: eth0
dummy0:
  match:
driver: dummy
  bonds:
bond0:
  interfaces: [eth0, dummy0]
  parameters:
mode: active-backup
mii-monitor-interval: 100
primary: eth0
  dhcp4: true

229-4ubuntu19
Oct 02 15:37:21 test-upgrade systemd-networkd[1773]: 
[/run/systemd/network/10-netplan-eth0.network:8] Unknown lvalue 'PrimarySlave' 
in section 'Network'
Oct 02 15:37:21 test-upgrade systemd-networkd[1773]: bond0: IPv6 enabled for 
interface: Success


229-4ubuntu20
Oct 02 15:39:22 test-upgrade systemd[1]: Starting Network Service...
Oct 02 15:39:22 test-upgrade systemd-networkd[3821]: bond0: IPv6 enabled for 
interface: Success
Oct 02 15:39:22 test-upgrade systemd-networkd[3821]: bond0: netdev ready
Oct 02 15:39:22 test-upgrade systemd-networkd[3821]: eth0: Gained IPv6LL
Oct 02 15:39:22 test-upgrade systemd-networkd[3821]: Enumeration completed
Oct 02 15:39:22 test-upgrade systemd[1]: Started Network Service.

All is good.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Triaged
Status in systemd source package in Xenial:
  Fix Committed
Status in nplan source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  In Progress
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 1715131] Re: networkd add support for Bridge Priority, AgeingTimeSec and DefaultPVID

Aging and Priority got tested in
https://bugs.launchpad.net/netplan/+bug/1665088/comments/15

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

Title:
  networkd add support for Bridge Priority, AgeingTimeSec and
  DefaultPVID

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

Bug description:
  [Impact]
  Newer releases of networkd support more optional settings for Bridge 
Priority, AgeingTimeSec and DefaultPVID.

  
https://www.freedesktop.org/software/systemd/man/systemd.netdev.html#AgeingTimeSec=
  https://www.freedesktop.org/software/systemd/man/systemd.netdev.html#Priority=
  
https://www.freedesktop.org/software/systemd/man/systemd.netdev.html#DefaultPVID=

  Backporting these features to xenial, allows to use/set these options
  via netplan for any releases as for example deployed by MAAS.

  [Fix]
  cherrypick these settings for better supportability of networkd on xenial 
with netplan.

  [Testcase]
  1) Create .netdev bridge device
  2) Specify Priority, AgeingTimeSec, DefaultPVID settings in the [Bridge] 
section
  3) Verify that there are no parsing errors in journalctl from systemd-netword
  4) Verify with `ip` command that the bridge device got created
  5) Verify in sysfs that the settings requested have been applied to the device

  [Regression]
  These stanazas are optional, and will be ignored by older networkd if for 
example users start using them, and downgrade networkd to the one in release 
pocket. It is future compatible settings that will not cause upgrade issues, 
nor could result in failure to create the bridge device.

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

-- 
Mailing list: https://launchpad.net/~touch-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

On jibel's request, I split my issue to a separate bug, LP: #1720809

** Changed in: ubuntu-meta (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 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 Committed

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 1709135] Re: add bond primary parameter

** Description changed:

  [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
- ethernets:
+ 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

-- 
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:
  Triaged
Status in systemd source package in Xenial:
  Fix Committed
Status in nplan source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  In Progress
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 1665088] Re: netplan bridge config doesn't support stp boolean

229-4ubuntu19
netplan apply resulted in:
Oct 02 15:19:49 test-upgrade systemd[1]: Starting Network Service...
Oct 02 15:19:49 test-upgrade systemd-networkd[1149]: 
[/run/systemd/network/10-netplan-br0.netdev:6] Unknown lvalue 'AgeingTimeSec' 
in section 'Bridge'
Oct 02 15:19:49 test-upgrade systemd-networkd[1149]: 
[/run/systemd/network/10-netplan-br0.netdev:7] Unknown lvalue 'Priority' in 
section 'Bridge'
Oct 02 15:19:49 test-upgrade systemd-networkd[1149]: 
[/run/systemd/network/10-netplan-br0.netdev:11] Unknown lvalue 'STP' in section 
'Bridge'
Oct 02 15:19:49 test-upgrade systemd-networkd[1149]: br0: IPv6 enabled for 
interface: Success

229-4ubuntu20
netplan apply resulted in
Oct 02 15:21:35 test-upgrade systemd[1]: Starting Network Service...
Oct 02 15:21:35 test-upgrade systemd-networkd[3188]: br0: IPv6 enabled for 
interface: Success
Oct 02 15:21:35 test-upgrade systemd-networkd[3188]: br0: netdev ready


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

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

Title:
  netplan bridge config doesn't support stp boolean

Status in netplan:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in nplan source package in Yakkety:
  Fix Released
Status in nplan source package in Zesty:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Users of netplan may wish to specify a custom MTU value for a device.

  [Test case]
  - Run nplan integration tests on the release
  - Validate that netplan generate && netplan apply alone, without config, 
behave as expected (no result)
  - Validate that netplan generate && netplan apply with minimal config writes 
/run/NetworkManager/conf.d/10-globally-managed-devices.conf
  - Validate that netplan generate && netplan apply works with any existing 
configuation.
  - Use the config below; ensure behavior is as expected (STP value is set on 
the interface; adjust device names as appropriate). There should be no errors 
at applying the requested configuration.
  - Use the config below with the 'stp' key; the device should be brought up 
and include the default value set for the kernel.

  [Regression potential]
  STP default value should continue to be used for the bridge configured using 
netplan if STP is unset in configuration.

  ---

  networkd supports setting STP value in Bridge type netdevs, but
  netplan does not accept the key.

  root@ubuntu:/etc/netplan# apt-cache policy nplan
  nplan:
    Installed: 0.18
    Candidate: 0.18
    Version table:
   *** 0.18 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:/etc/netplan# lsb_release -rd
  Description: Ubuntu Zesty Zapus (development branch)
  Release: 17.04

  root@ubuntu:/etc/netplan# cat 52-bridge.yaml
  network:
  ethernets:
  eth0:
  addresses:
  - 10.11.12.13/24
  match:
  macaddress: '52:54:00:12:34:00'
  set-name: foobar0
  eth1:
  match:
  macaddress: '52:54:00:12:34:02'
  set-name: eth1
  eth2:
  match:
  macaddress: '52:54:00:12:34:04'
  set-name: eth2
  bridges:
  br0:
  addresses:
  - 192.168.14.2/24
  interfaces:
  - eth1
  - eth2
  parameters:
  ageing-time: 250
  priority: 22
  forward-delay: 1
  hello-time: 1
  max-age: 10
  path-cost:
  eth1: 50
  eth2: 75
  stp: true
  version: 2

  root@ubuntu:/etc/netplan# netplan generate
  Error in network definition //etc/netplan/52-bridge.yaml line 24 column 16: 
unknown key stp

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

-- 
Mailing list: https://launchpad.net/~touch-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

** Branch linked: lp:~jbicha/ubuntu-seeds/add-fonts-to-desktop-common

-- 
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:
  New

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 1600000] Re: libnss-resolve treats two trailing dots on a domain name incorrectly

229-4ubuntu19
# systemd-resolve www.gnu.org..
www.gnu.org..: 208.118.235.148
   2001:4830:134:3::a
   (www.gnu.org)

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

Which is BAD.

229-4ubuntu20
# systemd-resolve www.gnu.org..
www.gnu.org..: resolve call failed: Invalid hostname 'www.gnu.org..'

Which is GOOD and standards compliant.

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

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

Title:
  libnss-resolve treats two trailing dots on a domain name incorrectly

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

Bug description:
  [Impact]
  libnss-resolve is an optional component not used by default in xenial. 
However it treats doubledot incorrectly, meaning it gets resolved when it 
shouldn't.

  [Fix]
  Cherrypick upstream patch to resolve this issue.

  [Testcase]

  * Enable resolve nss module
  * attempt resolving www.gnu.org..
  * It should fail to resolve

  (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org..
  208.118.235.148 STREAM wildebeest.gnu.org
  208.118.235.148 DGRAM
  208.118.235.148 RAW
  (base)adconrad@nosferatu:~$ sudo sed -i -e 's/ resolve dns/ dns/' 
/etc/nsswitch.conf
  (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org..
  (base)adconrad@nosferatu:~$ sudo sed -i -e 's/ dns/ resolve dns/' 
/etc/nsswitch.conf
  (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org..
  208.118.235.148 STREAM wildebeest.gnu.org
  208.118.235.148 DGRAM
  208.118.235.148 RAW
  (base)adconrad@nosferatu:~$

  This is responsible for the new regression in glibc:

  --
  FAIL: posix/tst-getaddrinfo5
  original exit status 1
  resolving "localhost." worked, proceeding to test
  resolving "localhost.." failed, test passed
  resolving "www.gnu.org." worked, proceeding to test
  resolving "www.gnu.org.." worked, test failed
  --

  [Regression potential]
  Minimal, since this component is not used by default. However, systems that 
have this enabled exhibit standards non-compliant behavior. It is not expected 
for anybody to depend on this broken behavior.

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

-- 
Mailing list: https://launchpad.net/~touch-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] [NEW] Move fonts to desktop-common

Public bug reported:

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

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful

** Branch linked: lp:~jbicha/ubuntu-seeds/drop-fonts-moved-to-desktop-
common

-- 
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:
  New

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 1703393] Re: TCP offloads disabled by default

** 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 1720692] Re: Add multiarch metadata to libxkbcommon*dev packages

2017-10-02 Thread Hans Joachim Desserud

** Tags added: artful

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

Title:
  Add multiarch metadata to libxkbcommon*dev packages

Status in libxkbcommon package in Ubuntu:
  New

Bug description:
  Release: Artful Aardvark 17.10
  Package Version: 0.7.1-2

  As far as I can tell (after creating a local patch and building and
  installing them as Multi-Arch: same) libxkbcommon-dev and
  libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no
  additional changes. Note that in order to cross-build the package, I
  also patched the build dependency x11-xkb-utils as Multi-Arch:
  allowed, and then used an :any dep. The use of :any as a dep is
  possibly appropriate, as I successfully built the package this way, I
  think only the tests depend on it, and they seem to call the binaries
  at runtime rather than compiling against them.

  Also, tests/x11comp is actually deactivated (since Mar 13, 2016
  upstream), and seems to be the only place that uses one of the x11
  -xkb-utils binaries, so maybe this dependency can just be removed?

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

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

[Touch-packages] [Bug 1682154] Re: loginctl ignoring user given sessions IDs at command-line

systemd 232-21ubuntu5
# loginctl show-session 2227 c1 | grep -e Id= -e Leader
Id=2227
Leader=723
Id=2227
Leader=723

systemd 232-21ubuntu6
# loginctl show-session 2227 c1 | grep -e Id= -e Leader
Id=2227
Leader=723
Id=c1
Leader=593

** 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/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 1710410] Re: Must run systemd-resolve --status before DNS resolving is operative

Starting with zesty container that has 232-21ubuntu5 installed.
Removed libnss-resolve.
Reboot.
Notice that systemd-resolve is not enabled.
Upgrade to 232-21ubuntu6.
 and systemd-resolved was not enabled by default

This is a fail, the version number in postinst is too low when comparing
whether or not resolved should be enabled or not.

** Tags removed: verification-needed verification-needed-zesty
** Tags added: verification-failed verification-failed-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 1707929] Re: [FFe] Revert blacklisting of Indic layouts

2017-10-02 Thread Iain Lane

02/10 15:15:18  GunnarHj: sorry about that - looks OK to me, feel
free to merge the pkg with Debian (that's the only change there)

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

Title:
  [FFe] Revert blacklisting of Indic layouts

Status in xkeyboard-config:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Triaged
Status in xkeyboard-config package in Debian:
  Fix Released

Bug description:
  In xkeyboard-config 2.19-1 several Indic keyboard layouts were moved
  to "extras".

  https://cgit.freedesktop.org/xkeyboard-config/commit/?id=913af7

  The measure has been criticized and has been reverted afterwards at
  both freedesktop.org and Debian. We should make sure it's reverted in
  Ubuntu 17.10 as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1707929/+subscriptions

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

[Touch-packages] [Bug 1720741] Re: On 17.10, two-finger scrolling on thinkpad x1 3rd generation non-working

2017-10-02 Thread Timo Aaltonen

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

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

Title:
  On 17.10, two-finger scrolling on thinkpad x1 3rd generation non-
  working

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  Two-finger scrolling is non-functional after upgrade to 17.10 beta.

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  2 09:10:27 2017
  DistUpgraded: 2017-09-29 16:06:55,873 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:2227]
  InstallationDate: Installed on 2016-04-28 (521 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20BTS26N00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=96f314f8-7e1b-4d70-b372-84febb180710 ro vesafb.invalid=1 quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-09-29 (2 days ago)
  dmi.bios.date: 03/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET28W (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTS26N00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET28W(1.06):bd03/12/2015:svnLENOVO:pn20BTS26N00:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS26N00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 3rd
  dmi.product.name: 20BTS26N00
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.82-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.1-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.1-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Sep 26 16:43:38 2017
  xserver.configfile: default
  xserver.errors:
   intel(0): failed to set mode: Invalid argument [22]
   intel(0): failed to set mode: Invalid argument [22]
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1049 
   vendor LGD
  xserver.version: 2:1.19.3-1ubuntu1.1

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

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

[Touch-packages] [Bug 1449001] Re: systemd-resolved: please do not use Google public DNS by default

Checked that zesty container has google DNS in the resolved.conf and
checked that when no interfaces are configured systemd-resolve --status
lists google DNS servers.

Upgraded to 232-21ubuntu6 and check that resolved.conf no longer lists
google dns by default and when no links are configured there are no
nameservers listed in systemd-resolve --status.

** 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/1449001

Title:
  systemd-resolved: please do not use Google public DNS by default

Status in systemd:
  New
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
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]
  systemd-resolved will fall back to Google public DNS (8.8.8.8, etc.) in the 
absence of other configured DNS servers.

  systemd-resolved is not enabled by default in Ubuntu 15.04, but it is
  installed by default and will behave in this way if enabled by the
  user.

  $ cat /etc/systemd/resolved.conf
  (...)
  # Entries in this file show the compile time defaults.
  (...)
  #FallbackDNS=8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844

  This raises privacy concerns since in the event of accidental
  misconfiguration DNS queries will be sent unencrypted across the
  internet, and potentially also security concerns given systemd-
  resolved does not perform DNSSEC validation and is not particularly
  well hardened against malicious responses e.g. from a MITM
  (http://www.openwall.com/lists/oss-security/2014/11/12/5).

  I believe that it would be better to fail safe if no DNS server is
  configured -- i.e. have DNS lookups fail; it's better that the user is
  aware of their misconfiguration, rather than silently sending their
  queries to Google.  The user can intentionally opt to use Google
  public DNS if they wish.

  [Testcase]
  Steps to reproduce:
  1. Remove existing DNS configuration (from /etc/network/interfaces, 
/etc/resolv.conf, /etc/resolvconf/resolv.conf.d/*)
  2. Reboot, or otherwise clear relevant state
  3. sudo service systemd-resolved start
  4. Note that Google's servers are listed in /run/systemd/resolve/resolv.conf
  5. If systemd-resolved is enabled in /etc/nsswitch.conf (it isn't by 
default), observe that DNS lookups probably still work, and queries are being 
sent to one of Google's servers

  Possible workaround/bugfix: ship a resolved.conf which clears the
  FallbackDNS parameter.

  [Solution]
  In ubuntu, we disable fallback DNS at build time, via build system 
configuration flags.

  This issue has been discussed in the Debian BTS
  (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658).  My
  interpretation of the Debian package maintainer's position is that a
  user concerned with the privacy implications shouldn't let systemd get
  into a state where it uses the fallback DNS servers (quoting Marco
  d'Itri: "Short summary: have a resolv.conf file or use DHCP").  I
  would argue that it's safest not to have fallback DNS servers
  configured at all by default.

  [Regression Potential]
  Missconfigured networks, that do not have a DNS server would previously 
magically work due to having Google DNS preconfigured regardless. With this 
change, such network configurations will fail to work, and one will have to 
properly fix network config to point at the right/existing name server.

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

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

[Touch-packages] [Bug 1719579] Re: [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save

2017-10-02 Thread Manoj Iyer

** Tags added: triage-g

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

Title:
  [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved
  in /var/tmp folder using virsh save

Status in The Ubuntu-power-systems project:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  == Comment: #1 - SEETEENA THOUFEEK  - 2017-01-17 
00:09:16 ==
  Bala, Please mail me the machine information.

  == Comment: #3 - SEETEENA THOUFEEK  - 2017-01-17 
02:14:06 ==
  2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACRestoreFileLabelInternal:388 : Restoring DAC user and group on 
'/var/tmp/bala'
  2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACSetOwnershipInternal:290 : Setting DAC user and group on 
'/var/tmp/bala' to '0:0'
  2017-01-16 12:09:37.707+: 7024: warning : qemuDomainSaveImageStartVM:6750 
: failed to restore save state label on /var/tmp/bala
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: debug : qemuDomainObjEndAsyncJob:1848 : 
Stopping async job: start (vm=0x3fff4ca535c0 name=virt-tests-vm1-bala)
  2017-01-16 12:09:37.707+: 7024: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca535c0
  2017-01-16 12:09:37.707+: 7024: debug : virThreadJobClear:121 : Thread 
7024 (virNetServerHandleJob) finished job remoteDispatchDomainRestore with 
ret=-1
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
  2017-01-16 12:09:37.707+: 7024: debug : virNetServerProgramSendError:153 
: prog=536903814 ver=1 proc=54 type=1 serial=4 msg=0x100133d2590 
rerr=0x3fffa59be3c0
  2017-01-16 12:09:37.707+: 7024: debug : virNetMessageEncodePayload:376 : 
Encode length as 172
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientSendMessageLocked:1399 : msg=0x100133d2590 proc=54 len=172 
offset=0
  2017-01-16 12:09:37.707+: 7024: info : 
virNetServerClientSendMessageLocked:1407 : RPC_SERVER_CLIENT_MSG_TX_QUEUE: 
client=0x100133d23c0 len=172 prog=536903814 vers=1 proc=54 type=1 status=1 
serial=4
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:157 : tls=(nil) hs=-1, rx=0x100133d0670 
tx=0x100133d2590
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:192 : mode=3
  2017-01-16 12:09:37.707+: 7024: info : virEventPollUpdateHandle:152 : 
EVENT_POLL_UPDATE_HANDLE: watch=417 events=3
  2017-01-16 12:09:37.707+: 7024: debug : virEventPollInterruptLocked:727 : 
Interrupting
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133caea0
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133d23c0
  .
  2017-01-16 12:14:28.445+: 7019: info : qemuMonitorJSONIOProcessLine:201 : 
QEMU_MONITOR_RECV_EVENT: mon=0x3fff94004d90 event={"timestamp": {"seconds": 
1484568868, "microseconds": 444620}, "event": "MIGRATION", "data": {"status": 
"failed"}}
  2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorJSONIOProcessEvent:147 
: mon=0x3fff94004d90 obj=0x100133b5670
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1762 : 
object=0x100133a8000
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133a8000 type=0 gen=0x100133d1160
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133d2a80 type=2 gen=0x100133d1160
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1795 : 
result={"status":"failed"}
  2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorEmitEvent:1218 : 
mon=0x3fff94004d90 event=MIGRATION
  2017-01-16 12:14:28.445+: 7019: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff94004d90
  2017-01-16 12:14:28.445+: 7019: debug : qemuProcessHandleEvent:629 : 
vm=0x3fff4ca535c0
  2017-01-16 12:14:28.445+: 7019: info : virObjectNew:202 : OBJECT_NEW: 
obj=0x100133d2870 classname=virDomainQemuMonitorEvent
  2017-01-16 12:14:28.445+: 7019: debug : virObjectEventNew:645 : 
obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:261 : 
OBJECT_DISPOSE: obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: debug : 
virDomainQemuMonitorEventDispose:477 : obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: debug : virObjectEventDispose:121 : 
obj=0x100133d2870
  2017-01-16

[Touch-packages] [Bug 1719851] Re: ca-certificates isn't updated in LTS 16.04

2017-10-02 Thread Marc Deslauriers

** Information type changed from Private Security to Public Security

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

Title:
  ca-certificates isn't updated in LTS 16.04

Status in ca-certificates package in Ubuntu:
  Fix Released
Status in ca-certificates source package in Trusty:
  New
Status in ca-certificates source package in Xenial:
  New
Status in ca-certificates source package in Zesty:
  New
Status in ca-certificates source package in Artful:
  Fix Released

Bug description:
  ca-certificates should contain root certificates for new CA from
  Amazon

  They are added in version 20170717, The Artful Aardvark (pre-release freeze) 
  But that isn't reflected neither in zesty, nor backports or security

  We recently got a letter from Amazon to update our SSL certs till
  October 25. Would be extremely great if ca-certificates will be
  updated via unattended upgrades in-time.

  Marking as security, because several CAs were removed (compromised?).
  Or maybe there is a reason, why root cert list isn't updated on LTS releases?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ca-certificates 20161130
  ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Wed Sep 27 11:10:01 2017
  Ec2AMI: ami-6edd3078
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: m3.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  SourcePackage: ca-certificates
  UpgradeStatus: Upgraded to zesty on 2017-05-19 (131 days ago)

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

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

[Touch-packages] [Bug 1720695] Re: Two different icons for sound volume

Thanks for reporting this bug and help making ubuntu better!

This bug is an upstream one in Adwaita icon I guess, but still good to test:
- installing the gnome vanilla session (sudo apt install gnome-session), reboot 
and switch to the "GNOME" session in GDM. 
- you should have the Adwaita theme there. Check if you can reproduce the bug
- please report here if you can reproduce it. If there is a bug in that 
session, do you mind filing the bug against upstream bugzilla in gnome-shell?


** Package changed: ubuntu-themes (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  Two different icons for sound volume

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 Beta running live from USB

  The "sound volume" icon in the top right corner of the screen is
  different from the icon in the popup dialog. Screenshot attached.

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

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

[Touch-packages] [Bug 1720697] Re: Some elements in calendar popup don't stay in the same place

Thanks for reporting this bug and help making ubuntu better!

I don't know if this bug is special to the ubuntu session or related to the 
gnome-shell itself. Something to check:
- installing the gnome vanilla session (sudo apt install gnome-session), reboot 
and switch to the "GNOME" session in GDM. 
- you should have the Adwaita theme there. Check if you can reproduce the bug
- please report here if you can reproduce it. If there is a bug in that 
session, do you mind filing the bug against upstream bugzilla in gnome-shell?


** Package changed: ubuntu-themes (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  Some elements in calendar popup don't stay in the same place

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 Beta running live from USB

  Steps to reproduce:
  1. Click the time indicator in the top centre of the screen
  2. Move between months in the calendar popup

  Expected result:
  View changes without visual glitches

  What happens instead:
  Sometimes both the "No event" icon and the vertical divider move right and 
left on the screen

  Short video attached.

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

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

[Touch-packages] [Bug 1720696] Re: Sound volume notification jumps left and right when changing volume

Thanks for reporting this bug and help making ubuntu better!

I don't know if this bug is special to the ubuntu session or related to the
gnome-settings-daemon. Something to check:
- installing the gnome vanilla session (sudo apt install gnome-session), reboot
and switch to the "GNOME" session in GDM.
- you should have the Adwaita theme there. Check if you can reproduce the bug
- please report here if you can reproduce it. If there is a bug in that
session, do you mind filing the bug against upstream bugzilla in
gnome-settings-daemon.

** Package changed: ubuntu-themes (Ubuntu) => gnome-settings-daemon (Ubuntu)

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

Title:
Sound volume notification jumps left and right when changing volume

Status in gnome-settings-daemon package in Ubuntu:
Confirmed

Bug description:
Ubuntu 17.10 Beta running live from USB

Steps to reproduce:
1. Place the mouse cursor over the volume icon in the top right corner of the
screen
2. Turn the mouse wheel
You will notice quite big notification bubble at the bottom centre of the
screen. When you're turning the mouse wheel the notification is showing the
volume level.

Expected result:
The notification stays in one place all the time I change the volume level

What happens instead:
For some volume values the notification jumps left and right on the screen

Short video attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1720696/+subscriptions

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

[Touch-packages] [Bug 1720698] Re: Different height for window top bar in one app

Thanks for reporting this bug and help making ubuntu better!

I don't know if this bug is special to the ubuntu session or related to the 
application. Something to check:
- installing the gnome vanilla session (sudo apt install gnome-session), reboot 
and switch to the "GNOME" session in GDM. 
- you should have the Adwaita theme there. Check if you can reproduce the bug
- please report here if you can reproduce it. If there is a bug in that 
session, do you mind filing the bug against upstream bugzilla in 
gnome-control-center.

PS: the name is "headerbar" :)

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

Title:
  Different height for window top bar in one app

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 Beta running live from USB

  I admit I have no idea how that "top bar" decoration of windows is
  called. Is it "tittle bar" or "tool bar"? Anyway I'm talking about
  that dark part with minimize and close buttons on it.

  I noticed the height of that bar is different if there's no additional
  buttons and different if there is an extra button or two. For example
  in the Settings app go to Details and switch between Users and Default
  Application tabs. When you're in Users tab you will see Add User
  button in the top bar. There's no button in the top bar of Default
  Application. When you switch between those two tabs you will notice
  that the top bar for Users tab has bigger height. And that gives
  visually unpleasant effect of interface jumping up and down when
  switching tabs.

  Short video attached.

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

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

[Touch-packages] [Bug 1720751] Re: Error message hidden behind modal dialog

Thanks for reporting this bug and help making ubuntu better! This bug is
an upstream GNOME bug, do you mind opening it against bugzilla (gnome-
shell component)?

** Package changed: ubuntu-themes (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Status: New => Triaged

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

Title:
  Error message hidden behind modal dialog

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 17.10 Beta running live from USB

  When Settings app crashed there was a modal dialog visible.
  Unfortunately the error message about the crash showed up behind that
  dialog. Screenshot attached.

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

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

[Touch-packages] [Bug 1720696] Re: Sound volume notification jumps left and right when changing volume

2017-10-02 Thread Alan Pope  濾

I'm unable to reproduce this on an up to date install of Ubuntu Artful.
Can you please update and see if it still happens? I tested on wayland
and xorg.

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

Title:
  Sound volume notification jumps left and right when changing volume

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 Beta running live from USB

  Steps to reproduce:
  1. Place the mouse cursor over the volume icon in the top right corner of the 
screen
  2. Turn the mouse wheel
  You will notice quite big notification bubble at the bottom centre of the 
screen. When you're turning the mouse wheel the notification is showing the 
volume level.

  Expected result:
  The notification stays in one place all the time I change the volume level

  What happens instead:
  For some volume values the notification jumps left and right on the screen

  Short video attached.

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

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

[Touch-packages] [Bug 1716082] Re: package libblkid1:amd64 2.28.2-1ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configur

2017-10-02 Thread Phillip Susi

** Also affects: dpkg (Ubuntu)
   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/1716082

Title:
  package libblkid1:amd64 2.28.2-1ubuntu1.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  i m not able to update or install any application

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libblkid1:amd64 2.28.2-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.7
  AptOrdering:
   libblkid1:amd64: Configure
   libglib2.0-0:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Sep  4 22:56:24 2017
  DuplicateSignature:
   package:libblkid1:amd64:2.28.2-1ubuntu1.2
   Unpacking unity-control-center (15.04.0+16.10.20170214-0ubuntu1) over 
(15.04.0+16.10.20161003.1-0ubuntu2) ...
Log started: 2017-09-04  22:56:24
   dpkg: error processing package libblkid1:amd64 (--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 2017-09-02 (6 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: util-linux
  Title: package libblkid1:amd64 2.28.2-1ubuntu1.2 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/dpkg/+bug/1716082/+subscriptions

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

[Touch-packages] [Bug 1720789] [NEW] package resolvconf 1.78ubuntu4 failed to install/upgrade: пакет resolvconf не готов к настройке настройка невозможна (текущее состояние: «half-installed»)

2017-10-02 Thread buguldey

Public bug reported:

it was first installed automatically by unknown package

and became half-installed at some stage

i ran apt-get install resolvconf -f

after some hours, it launched apport

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: resolvconf 1.78ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
AptOrdering:
 libboost-program-options1.58.0: Install
 resolvconf: Configure
 libboost-program-options1.58.0: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Sun Oct  1 05:31:14 2017
DpkgHistoryLog:
 Start-Date: 2017-10-01  05:31:02
 Requested-By: user (1000)
 Install: libboost-program-options1.58.0:amd64 (1.58.0+dfsg-5ubuntu3.1, 
automatic)
ErrorMessage: пакет resolvconf не готов к настройке  настройка невозможна 
(текущее состояние: «half-installed»)
InstallationDate: Installed on 2017-07-19 (74 days ago)
InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: resolvconf
Title: package resolvconf 1.78ubuntu4 failed to install/upgrade: пакет 
resolvconf не готов к настройке  настройка невозможна (текущее состояние: 
«half-installed»)
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package resolvconf 1.78ubuntu4 failed to install/upgrade: пакет
  resolvconf не готов к настройке  настройка невозможна (текущее
  состояние: «half-installed»)

Status in resolvconf package in Ubuntu:
  New

Bug description:
  it was first installed automatically by unknown package

  and became half-installed at some stage

  i ran apt-get install resolvconf -f

  after some hours, it launched apport

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: resolvconf 1.78ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   libboost-program-options1.58.0: Install
   resolvconf: Configure
   libboost-program-options1.58.0: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Oct  1 05:31:14 2017
  DpkgHistoryLog:
   Start-Date: 2017-10-01  05:31:02
   Requested-By: user (1000)
   Install: libboost-program-options1.58.0:amd64 (1.58.0+dfsg-5ubuntu3.1, 
automatic)
  ErrorMessage: пакет resolvconf не готов к настройке  настройка невозможна 
(текущее состояние: «half-installed»)
  InstallationDate: Installed on 2017-07-19 (74 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: resolvconf
  Title: package resolvconf 1.78ubuntu4 failed to install/upgrade: пакет 
resolvconf не готов к настройке  настройка невозможна (текущее состояние: 
«half-installed»)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1714122] Re: latest skype update causes xorg to segfault

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  latest skype update causes xorg to segfault

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After update skypeforlinux to 8.5.76.55323 I've started to get xorg segfaults 
when connected to 2 external monitors via docking station.
  My setup: Dell XPS 13 9360 + Dell DS1000 USB-C docking station+2 external 
FullHD Dell monitors.
  In xorg logs I can see:

  [ 17917.757] (II) LoadModule: "modesetting"
  [ 17917.757] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
  [ 17917.757] (II) Module modesetting: vendor="X.Org Foundation"
  [ 17917.757]compiled for 1.18.4, module version = 1.18.4
  [ 17917.757]Module class: X.Org Video Driver
  [ 17917.757]ABI class: X.Org Video Driver, version 20.0
  [ 17917.757] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
  [ 17917.759] (II) modeset(0): using drv /dev/dri/card0
  [ 17917.759] (EE) 
  [ 17917.759] (EE) Backtrace:
  [ 17917.759] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55c4f0526b6e]
  [ 17917.759] (EE) 1: /usr/lib/xorg/Xorg (0x55c4f0374000+0x1b6ef9) 
[0x55c4f052aef9]
  [ 17917.759] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fb6199e2000+0x354b0) 
[0x7fb619a174b0]
  [ 17917.759] (EE) 3: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 
(pci_device_next+0x118) [0x7fb61afd1a38]
  [ 17917.759] (EE) 4: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 
(pci_device_find_by_slot+0x3b) [0x7fb61afd1abb]
  [ 17917.759] (EE) 5: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 
(pci_device_vgaarb_init+0xaf) [0x7fb61afd37af]
  [ 17917.759] (EE) 6: /usr/lib/xorg/Xorg (0x55c4f0374000+0xb1a39) 
[0x55c4f0425a39]
  [ 17917.759] (EE) 7: /usr/lib/xorg/Xorg (xf86BusConfig+0x62) [0x55c4f03fe7a2]
  [ 17917.759] (EE) 8: /usr/lib/xorg/Xorg (InitOutput+0x968) [0x55c4f040cd58]
  [ 17917.759] (EE) 9: /usr/lib/xorg/Xorg (0x55c4f0374000+0x57be4) 
[0x55c4f03cbbe4]
  [ 17917.759] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7fb619a02830]
  [ 17917.759] (EE) 11: /usr/lib/xorg/Xorg (_start+0x29) [0x55c4f03b6049]
  [ 17917.759] (EE) 
  [ 17917.759] (EE) Segmentation fault at address 0x0
  [ 17917.759] (EE) 
  Fatal server error:
  [ 17917.759] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [ 17917.759] (EE) 
  [ 17917.759] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 17917.759] (EE) Please also check the log file at "/var/log/Xorg.1.log" for 
additional information.
  [ 17917.759] (EE) 
  [ 17917.816] (EE) Server terminated with error (1). Closing log file.

  I'm not facing this issue when I'm not connected to external monitors.
  Any help will be much appretiated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  .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
  Date: Wed Aug 30 18:27:41 2017
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:075b]
  InstallationDate: Installed on 2016-10-06 (328 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=f79f9409-625c-4f78-83af-cf2cf7928690 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.0
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version:

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

I believe all of the cloud-init is covered by
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1718029 and
addressed by https://code.launchpad.net/~xnox/cloud-init/+git/cloud-
init/+merge/331642

** Changed in: cloud-init (Ubuntu)
   Status: New => In Progress

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

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

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

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 775803] ❣Fw: yahoo! useful article

2017-10-02 Thread John Butterworth

Hello!

I've read articles recently, it  appears to be  really filled with
amazing facts,  it  could interest you too.  You may red it here
http://andrichak.com/rc/plugins/jqueryui/js/i18n/political.php?UE83NzU4MDNAYnVncy5sYXVuY2hwYWQubmV0

See you soon, Thelma Andersen

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

Title:
  /usr/bin/python: error while loading shared libraries: /lib/i386
  -linux-gnu/libz.so.1: invalid ELF header

Status in zlib package in Ubuntu:
  New

Bug description:
  Binary package hint: nvidia-common

  Upgrade failed to install correctly

  ProblemType: Package
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-9-generic 2.6.38-9.43
  ProcVersionSignature: Ubuntu 2.6.35-29.51-generic 2.6.35.12
  Uname: Linux 2.6.35-29-generic i686
  Architecture: i386
  Date: Mon May  2 19:42:26 2011
  ErrorMessage: run-parts: /etc/kernel/postinst.d/nvidia-common exited with 
return code 127
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  SourcePackage: nvidia-common
  Title: package linux-image-2.6.38-9-generic 2.6.38-9.43 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/nvidia-common exited with 
return code 127
  UpgradeStatus: Upgraded to natty on 2011-05-02 (0 days ago)

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

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

[Touch-packages] [Bug 1720755] [NEW] [LifeBook hostname, Realtek ALC269, Speaker, Internal] Underruns, dropouts or crackling sound

2017-10-02 Thread xixvision

Public bug reported:

Audio cracking

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pulseaudio 1:4.0-0ubuntu11.1
ProcVersionSignature: Ubuntu 4.4.0-96.119~14.04.1-generic 4.4.83
Uname: Linux 4.4.0-96-generic i686
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jonny  1738 F pulseaudio
CurrentDesktop: Unity
Date: Mon Oct  2 11:29:32 2017
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
Symptom_AlsaPlaybackTestStderr:
 W r i t e   e r r o r :   - 5 , I n p u t / o u t p u t   e r r o r 
  x r u n _ r e c o v e r y   f a i l e d :   - 5 , I n p u t / o u t p u t   e 
r r o r 
  T r a n s f e r   f a i l e d :   I n p u t / o u t p u t   e r r o r
Symptom_Card: Audio Interno - HDA Intel MID
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [LifeBook hostname, Realtek ALC269, Speaker, Internal] Underruns, 
dropouts or crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/30/2009
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.22
dmi.board.name: FJNB1EE
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: D3N016D10110
dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.22:bd04/30/2009:svnFUJITSU:pnLifeBookU2010:pvr:rvnFUJITSU:rnFJNB1EE:rvr:cvnD3N016D10110:ct10:cvr:
dmi.product.name: LifeBook U2010
dmi.sys.vendor: FUJITSU

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


** Tags: apport-bug i386 trusty

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

Title:
  [LifeBook hostname, Realtek ALC269, Speaker, Internal] Underruns,
  dropouts or crackling sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Audio cracking

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 4.4.0-96.119~14.04.1-generic 4.4.83
  Uname: Linux 4.4.0-96-generic i686
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jonny  1738 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Oct  2 11:29:32 2017
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_AlsaPlaybackTestStderr:
   W r i t e   e r r o r :   - 5 , I n p u t / o u t p u t   e r r o r 
x r u n _ r e c o v e r y   f a i l e d :   - 5 , I n p u t / o u t p u t   
e r r o r 
T r a n s f e r   f a i l e d :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Audio Interno - HDA Intel MID
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [LifeBook hostname, Realtek ALC269, Speaker, Internal] Underruns, 
dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2009
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.22
  dmi.board.name: FJNB1EE
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: D3N016D10110
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.22:bd04/30/2009:svnFUJITSU:pnLifeBookU2010:pvr:rvnFUJITSU:rnFJNB1EE:rvr:cvnD3N016D10110:ct10:cvr:
  dmi.product.name: LifeBook U2010
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1720698] Re: Different height for window top bar in one app

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Confirmed

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

Title:
  Different height for window top bar in one app

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 Beta running live from USB

  I admit I have no idea how that "top bar" decoration of windows is
  called. Is it "tittle bar" or "tool bar"? Anyway I'm talking about
  that dark part with minimize and close buttons on it.

  I noticed the height of that bar is different if there's no additional
  buttons and different if there is an extra button or two. For example
  in the Settings app go to Details and switch between Users and Default
  Application tabs. When you're in Users tab you will see Add User
  button in the top bar. There's no button in the top bar of Default
  Application. When you switch between those two tabs you will notice
  that the top bar for Users tab has bigger height. And that gives
  visually unpleasant effect of interface jumping up and down when
  switching tabs.

  Short video attached.

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

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

[Touch-packages] [Bug 1720697] Re: Some elements in calendar popup don't stay in the same place

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Confirmed

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

Title:
  Some elements in calendar popup don't stay in the same place

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 Beta running live from USB

  Steps to reproduce:
  1. Click the time indicator in the top centre of the screen
  2. Move between months in the calendar popup

  Expected result:
  View changes without visual glitches

  What happens instead:
  Sometimes both the "No event" icon and the vertical divider move right and 
left on the screen

  Short video attached.

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

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

[Touch-packages] [Bug 1720696] Re: Sound volume notification jumps left and right when changing volume

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Confirmed

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

Title:
  Sound volume notification jumps left and right when changing volume

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 Beta running live from USB

  Steps to reproduce:
  1. Place the mouse cursor over the volume icon in the top right corner of the 
screen
  2. Turn the mouse wheel
  You will notice quite big notification bubble at the bottom centre of the 
screen. When you're turning the mouse wheel the notification is showing the 
volume level.

  Expected result:
  The notification stays in one place all the time I change the volume level

  What happens instead:
  For some volume values the notification jumps left and right on the screen

  Short video attached.

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

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

[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

2017-10-02 Thread Konrad Zapałowicz

Hey, let me chime in into the discussion.

First I'm terribly sorry to see that people are affected by this kind of issue.
I remember a similar one on Ubuntu Phone which we have finally tracked down to
the hardware side but were never able to fix completely.

Canonical as a company and we as a developers working on Ubuntu do actually care
about Bluetooth. Myself, Daniel and a few others formed an informal group that
meets regularly and strives to set the course for improvement. Believe me, we
would be delighted to see it working flawlessly because well... among other
reasons we also use Bluetooth devices on daily basis. However, sadly, it is not
that easy as the underlying technology itself is fairly complex and requires
both hardware, software and remote side to click in.

We are not searching for the white flag though :) this would be too easy.
Instead we plan our work in a way that we are able to take down issues and
gradually improve the overall experience. This is a step by step process where
we tackle problems one by one aiming for these that have the best chance to be
solved in order to deliver improvements with each cycle. 

In this case the audio in under running, PulseAudio tries to catch up and this
is why you see skipped bytes messages. There might be multiple reasons for this
starting from PulseAudio (and it's Bluetooth modules), through bluez, system
load and such and ending on the hardware configuration itself. For example
hugely popular WiFi+BT combo chipsets are prone to such issues as Bluetooth and
WiFi have to compete for throughput.

If I were you I would start from reporting this issue to Pulse Audio developers
through their mailing list (perhaps also on bluez) and start working from there.
We do keep an eye on these so if there is something interesting coming up in the
discussions we will pick it up. We will also remember about this one and for an
upcoming bluez 5.47 testing we will include high-load tests to see if we can
even experience this issue (so far we did not) with the hardware we test with.
Does it make sense?

Hope that at some point in the near future we will learn enough about this one
so that we can fix it.

Hope this helps,
K

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

Title:
  A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
  audio stream"]

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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

[Touch-packages] [Bug 1720695] Re: Two different icons for sound volume