date:20170301

** Changed in: mir
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  [gallium] EGL clients using a gallium driver (radeon, nouveau,
  freedreno) that saturate the GPU cause the Mir server to slow, freeze
  and stutter, displaying very few frames

Status in Mir:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  GPU-heavy clients on Mesa gallium drivers (e.g. radeon, nouveau and
  freedreno) cause the Mir server to slow, sometimes to a halt. This is
  seen as a frozen screen, unable to move surfaces, or unable to switch
  VTs (for a while).

  For example:
     mir_demo_client_egltriangle -n
     mir_demo_client_eglplasma -n

  The -n flag (swapinterval = 0) seems to cause the client to overload
  the mir server to the point where it cannot render physical frames
  very often.

  $ es2_info
  EGL_VERSION = 1.4 (Gallium)
  EGL_VENDOR = Mesa Project
  EGL_EXTENSIONS = EGL_WL_bind_wayland_display EGL_KHR_image_base 
EGL_KHR_image_pixmap EGL_KHR_image EGL_KHR_reusable_sync EGL_KHR_fence_sync 
EGL_KHR_surfaceless_context EGL_NOK_swap_region EGL_NV_post_sub_buffer
  EGL_CLIENT_APIS = OpenGL OpenGL_ES OpenGL_ES2 OpenVG
  GL_VERSION: OpenGL ES 3.0 Mesa 9.2.0-devel
  GL_RENDERER: Gallium 0.4 on AMD CEDAR
  ...
  $ es2_info
  EGL_VERSION = 1.4 (Gallium)
  EGL_VENDOR = Mesa Project
  EGL_EXTENSIONS = EGL_WL_bind_wayland_display EGL_KHR_image_base 
EGL_KHR_image_pixmap EGL_KHR_image EGL_KHR_reusable_sync EGL_KHR_fence_sync 
EGL_KHR_surfaceless_context EGL_NOK_swap_region EGL_NV_post_sub_buffer
  EGL_CLIENT_APIS = OpenGL OpenGL_ES OpenGL_ES2 OpenVG
  GL_VERSION: OpenGL ES 3.0 Mesa 9.2.0-devel
  GL_RENDERER: Gallium 0.4 on NVA8
  ...

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

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

[Touch-packages] [Bug 1668906] [NEW] systemd occasionally hangs forever while booting: A start job is running for ...

2017-03-01 Thread Hadmut Danisch

Public bug reported:

Hi,
on several of my machines (encrypted, 16.04 and 16.10) it *sometimes* happens, 
that systemd is stuck in booting telling 

"A start job is running for dev-mapp...ypt.device (5min 40s / no limit)"
(endless loop, counting the time up)

(only) rebooting helps, but that's annoying and keeps machines from
automated booting.


Additional problem one: 
That damned systemd shortens the output to the terminal line length and instead 
of telling the device name to give a hint where the problems come from it just 
says  dev-mapp...ypt.device


Additional problem two:
I've activated systemd's debug shell on Terminal 9 in order to debug the 
problem, but the debug shell is rendered useless by systemd, since it blasts 
it's messages about the problem to tty9 as well, thus making it impossible to 
work there. 


Additional problem three: 
These device entries seem to be generated dynamically from fstab/crypttab and 
not exist as files, so it is not even visible, what's the contents of these 
tasks. 

Additional problem four: 
I did not find a description of a debugging procedure. 


So I do not even see how to debug that weird mess. Why on earth has
ubuntu moved to such a confused heap of undebuggable spaghetti code?

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: systemd 231-9ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
Uname: Linux 4.8.0-39-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Mar  1 10:18:15 2017
InstallationDate: Installed on 2016-04-22 (312 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200
 Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 
Optical USB Mouse]
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic 
root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash 
noplymouth nomodeset text
SourcePackage: systemd
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (135 days ago)
dmi.bios.date: 03/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: N3150-NUC
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.50:bd03/16/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  systemd occasionally hangs forever while booting: A start job is
  running for ...

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,
  on several of my machines (encrypted, 16.04 and 16.10) it *sometimes* 
happens, that systemd is stuck in booting telling 

  "A start job is running for dev-mapp...ypt.device (5min 40s / no
  limit)" (endless loop, counting the time up)

  (only) rebooting helps, but that's annoying and keeps machines from
  automated booting.


  
  Additional problem one: 
  That damned systemd shortens the output to the terminal line length and 
instead of telling the device name to give a hint where the problems come from 
it just says  dev-mapp...ypt.device


  Additional problem two:
  I've activated systemd's debug shell on Terminal 9 in order to debug the 
problem, but the debug shell is rendered useless by systemd, since it blasts 
it's messages about the problem to tty9 as well, thus making it impossible to 
work there. 


  Additional problem three: 
  These device entries seem to be generated dynamically from fstab/crypttab and 
not exist as files, so it is not even visible, what's the contents of these 
tasks. 

  Additional problem four: 
  I did not find a description of a debugging procedure. 


  So I do not even see how to debug that weird mess. Why on earth has
  ubuntu moved to such a confused heap of undebuggable spaghetti code?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  Uname: Linux 4.8.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Archi

[Touch-packages] [Bug 1177318] Re: Unattended Upgrades fail to parse "${distro_id}:${distro_codename}-security"

2017-03-01 Thread Jarno Suni

Here in Ubuntu 14.04.5 LTS it seems to install upgrades fine, even
though there is "InstCount=0" in the log.

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

Title:
  Unattended Upgrades fail to parse
  "${distro_id}:${distro_codename}-security"

Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  Beginning with Ubuntu 13.04 Raring Ringtail, unattended-upgrades seems
  not to be able to parse /etc/apt/apt.conf.d/50unattended-upgrades
  anymore. The logfile tells:

  cat /var/log/unattended-upgrades/unattended-upgrades.log 
  2013-05-06 14:57:05,724 INFO Pakete, die anfangs auf die schwarzen Liste 
standen: 
  2013-05-06 14:57:05,724 INFO Skript für unbeaufsichtigte Upgrades wird 
gestartet.
  2013-05-06 14:57:05,725 INFO erlaubte Ursprünge sind: 
['o=Ubuntu,a=raring-security', 'o=Ubuntu,a=raring-updates']
  2013-05-06 14:57:09,114 INFO Es wurden keine Pakete gefunden, von denen ein 
unbeaufsichtigtes Upgrade durchgeführt werden kann.
  2013-05-07 11:33:04,944 INFO Pakete, die anfangs auf die schwarzen Liste 
standen: 
  2013-05-07 11:33:04,944 INFO Skript für unbeaufsichtigte Upgrades wird 
gestartet.
  2013-05-07 11:33:04,944 INFO erlaubte Ursprünge sind: 
['o=Ubuntu,a=raring-security', 'o=Ubuntu,a=raring-updates']
  2013-05-07 11:33:08,398 INFO Es wurden keine Pakete gefunden, von denen ein 
unbeaufsichtigtes Upgrade durchgeführt werden kann.

  which means two times, that allowed sources are ['o=Ubuntu,a=raring-
  security', 'o=Ubuntu,a=raring-updates'].

  I do suspect it is because of the automatic distribution setting in
  /etc/apt/apt.conf.d/50unattended-upgrades or the setting of the
  corresponding variables:

  "${distro_id}:${distro_codename}-updates"

  When this line is set manually to "Ubuntu:raring-updates", it will
  work.

  System: Ubuntu Gnome 13.04, all up-to-date

  $ lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04

  $ cat /etc/apt/apt.conf.d/10periodic 
  APT::Periodic::Update-Package-Lists "1";
  APT::Periodic::Download-Upgradeable-Packages "1";
  APT::Periodic::AutocleanInterval "1";
  APT::Periodic::Unattended-Upgrade "1";

  $ cat /etc/apt/apt.conf.d/50unattended-upgrades 
  // Automatically upgrade packages from these (origin:archive) pairs
  Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}-security";
"${distro_id}:${distro_codename}-updates";
  //"${distro_id}:${distro_codename}-proposed";
  //"${distro_id}:${distro_codename}-backports";
  };

  // List of packages to not update
  Unattended-Upgrade::Package-Blacklist {
  //"vim";
  //"libc6";
  //"libc6-dev";
  //"libc6-i686";
  };
  ...

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

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

[Touch-packages] [Bug 1668914] [NEW] package humanity-icon-theme 0.6.10.1 failed to install/upgrade: package humanity-icon-theme is not ready for configuration cannot configure (current status 'half-i

2017-03-01 Thread Anil Vignesh

Public bug reported:

really dont knw

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: humanity-icon-theme 0.6.10.1
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.5
Architecture: amd64
Date: Wed Mar  1 14:44:40 2017
ErrorMessage: package humanity-icon-theme is not ready for configuration  
cannot configure (current status 'half-installed')
InstallationDate: Installed on 2017-02-23 (6 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: humanity-icon-theme
Title: package humanity-icon-theme 0.6.10.1 failed to install/upgrade: package 
humanity-icon-theme is not ready for configuration  cannot configure (current 
status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: humanity-icon-theme (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 humanity-icon-theme in
Ubuntu.
https://bugs.launchpad.net/bugs/1668914

Title:
  package humanity-icon-theme 0.6.10.1 failed to install/upgrade:
  package humanity-icon-theme is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in humanity-icon-theme package in Ubuntu:
  New

Bug description:
  really dont knw

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: humanity-icon-theme 0.6.10.1
  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.5
  Architecture: amd64
  Date: Wed Mar  1 14:44:40 2017
  ErrorMessage: package humanity-icon-theme is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-02-23 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: humanity-icon-theme
  Title: package humanity-icon-theme 0.6.10.1 failed to install/upgrade: 
package humanity-icon-theme is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1668914/+subscriptions

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

[Touch-packages] [Bug 1666900] Re: avahi-autoipd fails because network interface name is too long

2017-03-01 Thread Paul Boven

Happened to connect my Pi Zero through a hub today. The interface name
on the PC becomes "enp0s26u1u3u3i1" which itself is already 15
characters, so no room at all to append a label.

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

Title:
  avahi-autoipd fails because network interface name is too long

Status in avahi package in Ubuntu:
  New

Bug description:
  Trying to use avahi-autoipd on a USB network interface, which gets
  created when I connect a USB gadget (g_ether) device (my raspberry pi
  zero). Avahi-autoipd fails to assign an IPv4LL address, and instead
  reports:

  # avahi-autoipd enp0s29u1u2
  Found user 'avahi-autoipd' (UID 110) and group 'avahi-autoipd' (GID 120).
  Successfully called chroot().
  Successfully dropped root privileges.
  Starting with address 169.254.7.125
  Callout BIND, address 169.254.7.125 on interface enp0s29u1u2
  client: RTNETLINK answers: Numerical result out of range
  Script execution failed with return value 2
  Successfully claimed IP address 169.254.7.125

  Although avahi-autoipd claims that the IP address gets configured,
  ifconfig shows that it didn't succeed.

  The root cause is that the label for the interface exceeds the maximum
  length of 15 characters. This happens in line 44 of /etc/avahi/avahi-
  autoipd.action:

  ip addr add "$3"/16 brd 169.254.255.255 label "$2:avahi" scope link
  dev "$2"

  With $2 the interface name, and $3 the IPv4LL address that it wants to
  claim.

  Interface names and label names can only be 15 characters in length,
  this is a kernel limitation. IF_NAMESIZE = 16, leaving 15 chars for
  the name, see /usr/include/net/if.h and IFNAMSIZ in the kernel
  includes.

  The rather long interface name, appended with ":avahi", exceeds this
  length. This results in the 'Numerical result out of range' error
  message.

  Workaround: I've edited the /etc/avahi/avahi-autopid.action script to
  only append ":a" for the label (lines 44 and 50) ,and in this case it
  works as designed.

  avahi-autoipd should perhaps check that the label does not exceed this
  limit of 15 characters.

  Note that the label must start with the full interface name, see ip-
  address(8).

  A more compact interface name would be helpful, as these long interface names 
tend to break
  other things as well. The kernel assigns 'usb0', but this gets changed right 
away.

  This occurs on both 16.04 and 16.10, haven't tried any other versions
  yet.

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

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

[Touch-packages] [Bug 1665802] Re: [regression] mir_demo_client_eglplasma results in 100% cpu and hardly any updates in dragonboard

** Branch linked: lp:~vanvugt/mir/gpu-load-balance

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

Title:
  [regression] mir_demo_client_eglplasma results in 100% cpu and hardly
  any updates in dragonboard

Status in Mir:
  In Progress
Status in Mir 0.26 series:
  Triaged
Status in mesa package in Ubuntu:
  New

Bug description:
  On a dragonboard 410c,

  With Mir 0.25 mir_demo_client_eglplasma renders steadily at 15FPS and
  with low cpu usage.

  With mir 0.26.1, the process takes 100% cpu (according to top) and
  frames hardly update on screen, but the client performance is
  60-27FPS.

  To replicate:

  mir_demo_server --arw-file --launch-client mir_demo_client_eglplasma

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

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

[Touch-packages] [Bug 1211700] Re: [gallium] EGL clients using a gallium driver (radeon, nouveau, freedreno) that saturate the GPU cause the Mir server to slow, freeze and stutter, displaying very few

** Branch linked: lp:~vanvugt/mir/gpu-load-balance

** Changed in: mir
Milestone: None => 1.0.0

** Changed in: mir
   Status: Confirmed => In Progress

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

Title:
  [gallium] EGL clients using a gallium driver (radeon, nouveau,
  freedreno) that saturate the GPU cause the Mir server to slow, freeze
  and stutter, displaying very few frames

Status in Mir:
  In Progress
Status in mesa package in Ubuntu:
  New

Bug description:
  GPU-heavy clients on Mesa gallium drivers (e.g. radeon, nouveau and
  freedreno) cause the Mir server to slow, sometimes to a halt. This is
  seen as a frozen screen, unable to move surfaces, or unable to switch
  VTs (for a while).

  For example:
     mir_demo_client_egltriangle -n
     mir_demo_client_eglplasma -n

  The -n flag (swapinterval = 0) seems to cause the client to overload
  the mir server to the point where it cannot render physical frames
  very often.

  $ es2_info
  EGL_VERSION = 1.4 (Gallium)
  EGL_VENDOR = Mesa Project
  EGL_EXTENSIONS = EGL_WL_bind_wayland_display EGL_KHR_image_base 
EGL_KHR_image_pixmap EGL_KHR_image EGL_KHR_reusable_sync EGL_KHR_fence_sync 
EGL_KHR_surfaceless_context EGL_NOK_swap_region EGL_NV_post_sub_buffer
  EGL_CLIENT_APIS = OpenGL OpenGL_ES OpenGL_ES2 OpenVG
  GL_VERSION: OpenGL ES 3.0 Mesa 9.2.0-devel
  GL_RENDERER: Gallium 0.4 on AMD CEDAR
  ...
  $ es2_info
  EGL_VERSION = 1.4 (Gallium)
  EGL_VENDOR = Mesa Project
  EGL_EXTENSIONS = EGL_WL_bind_wayland_display EGL_KHR_image_base 
EGL_KHR_image_pixmap EGL_KHR_image EGL_KHR_reusable_sync EGL_KHR_fence_sync 
EGL_KHR_surfaceless_context EGL_NOK_swap_region EGL_NV_post_sub_buffer
  EGL_CLIENT_APIS = OpenGL OpenGL_ES OpenGL_ES2 OpenVG
  GL_VERSION: OpenGL ES 3.0 Mesa 9.2.0-devel
  GL_RENDERER: Gallium 0.4 on NVA8
  ...

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

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

[Touch-packages] [Bug 1665802] Re: [regression] mir_demo_client_eglplasma results in 100% cpu and hardly any updates in dragonboard

Alberto,

Please try this experiment: lp:~vanvugt/mir/gpu-load-balance
It improves the situation on radeon quite a lot (from below 0.1FPS to 20-40FPS).

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

Title:
  [regression] mir_demo_client_eglplasma results in 100% cpu and hardly
  any updates in dragonboard

Status in Mir:
  In Progress
Status in Mir 0.26 series:
  Triaged
Status in mesa package in Ubuntu:
  New

Bug description:
  On a dragonboard 410c,

  With Mir 0.25 mir_demo_client_eglplasma renders steadily at 15FPS and
  with low cpu usage.

  With mir 0.26.1, the process takes 100% cpu (according to top) and
  frames hardly update on screen, but the client performance is
  60-27FPS.

  To replicate:

  mir_demo_server --arw-file --launch-client mir_demo_client_eglplasma

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

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

[Touch-packages] [Bug 1668387] Re: inconsistent grab of window unity8 zesty

** Tags added: unity8-desktop

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

Title:
  inconsistent grab of window unity8 zesty

Status in Canonical System Image:
  In Progress
Status in miral package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  this is on the Feb 27 daily iso of zesty, base install exploration of u8
  how to repro:
  1) open a window
  2) grab the title bar area and quickly drag upward
  result: sometimes the window follows the grabby-hand cursor and sometimes it 
doesn't

  note: seems to "recover" if you re-enter the title bar area with the grabby 
hand active
  also, seems interesting that even when the window doesn't follow, the shell 
will still draw a full screen highlight when "pushing" upward

  here's video of it
  a legacy app
  http://www.youtube.com/watch?v=DIuNKPen1BA
  then with a u8 app
  https://www.youtube.com/watch?v=MNYIABNuVtk

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

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

[Touch-packages] [Bug 1667604] Re: Cannot use window controls on a laptop with touchscreen

** Tags added: unity8-desktop

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

Title:
  Cannot use window controls on a laptop with touchscreen

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Zesty Desktop up to date on Dell Inspiron 11 3000 with touchscreen

  The user cannot interact with the window controls
  (close/minimize/maximize on the left of the title bar) with his
  fingers. Taping them does nothing but they work fine with the mouse or
  trackpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Fri Feb 24 09:56:57 2017
  InstallationDate: Installed on 2014-07-23 (946 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-15 (100 days ago)

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

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

[Touch-packages] [Bug 1668642] Re: [unity8] can still drag windows while the app switcher is active

** Branch linked: lp:~lukas-kde/unity8/cancel-drag-in-spread

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

Title:
  [unity8] can still drag windows while the app switcher is active

Status in Canonical System Image:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  ubuntu 17.04 unity8

  left click on a window's titlebar (keep the mouse button down, don't
  let go!) then press ALT TAB (don't let go of ALT to stay in the
  swithcer). now move your mouse to the edges of the screen while still
  holding the left mouse button down. you are actually dragging the
  window and you can snap it as normal, you'll see the snaping
  rectangles higligh but not the actual window because is probably some
  layers down. snap the window and let go of ALT and mouse button, now
  you'll see the snap highligh are above the app. see screenshot

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

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

[Touch-packages] [Bug 1668944] [NEW] The _apt user ignores group membership.

2017-03-01 Thread Reik Keutterling

Public bug reported:

Actually I had the same problem described in
http://askubuntu.com/questions/773955/apt-get-ssl-client-certificate-not-working-on-16-04-error-while-reading-file
I want to use client certificates with apt. But I don't want to make them world
readable in order to make apt working. So I created a group 'ssl-cert' and
changed the group ownership of the ssl cert files to match this group. I also
added the _apt user to the ssl-cert group.

Then I tried to open these files as user '_apt' in bash (su -s /bin/bash
_apt) which works well.

But if I run: "apt-get -o "Debug::Acquire::https=true" update" I still get the
following error:
* error reading ca cert file /etc/certs/mycert/ca.pem (Error while reading
file.)
* Closing connection 26

So my guess is that apt somehow ignores the ssl-cert membership.

Possible workarounds:
- make ssl client cert world readable
- change owner ssl client cert to _apt
- change main group of _apt user from 'nogroup' to 'ssl-cert'
- set APT::Sandbox::User "root"; in apt.conf.d

Neither of them is pretty.
Maybe this is a wanted behavior, then just suggest how to fix the issue in nice
way.

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

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

Title:
The _apt user ignores group membership.

Status in apt package in Ubuntu:
New

Bug description:
Actually I had the same problem described in
http://askubuntu.com/questions/773955/apt-get-ssl-client-certificate-not-working-on-16-04-error-while-reading-file
I want to use client certificates with apt. But I don't want to make them
world readable in order to make apt working. So I created a group 'ssl-cert'
and changed the group ownership of the ssl cert files to match this group. I
also added the _apt user to the ssl-cert group.

Then I tried to open these files as user '_apt' in bash (su -s
/bin/bash _apt) which works well.

But if I run: "apt-get -o "Debug::Acquire::https=true" update" I still get
the following error:
* error reading ca cert file /etc/certs/mycert/ca.pem (Error while reading
file.)
* Closing connection 26

So my guess is that apt somehow ignores the ssl-cert membership.

Neither of them is pretty.
Maybe this is a wanted behavior, then just suggest how to fix the issue in
nice way.

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

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

[Touch-packages] [Bug 1653635] Re: cmake unable to report INCLUDE_DIRS and LIBRARIES

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

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

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

Title:
  cmake unable to report INCLUDE_DIRS and LIBRARIES

Status in libjsoncpp package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  $ dpkg -l|grep libjsoncpp
  ii  libjsoncpp-dev:amd64   1.7.2-1
   amd64library for reading and writing JSON for C++ (devel 
files)
  ii  libjsoncpp1:amd64  1.7.2-1
   amd64library for reading and writing JSON for C++

  When try to use jsoncpp, the ${jsoncpp_INCLUDE_DIRS} and
  ${jsoncpp_LIBRARIES} fail to report.

  CMakeLists.txt
  
  cmake_minimum_required(VERSION 2.6.2)
  project(jsoncpp_test)

  find_package(jsoncpp REQUIRED)
  message("FOUND CONFIG: ${jsoncpp_CONFIG}")
  message("INCLUDE DIRS: ${jsoncpp_INCLUDE_DIRS}")
  message("LIBRARIES: ${jsoncpp_LIBRARIES}")

  The actual result is:
  
  FOUND CONFIG: /usr/lib/x86_64-linux-gnu/cmake/jsoncpp/jsoncppConfig.cmake
  INCLUDE DIRS: 
  LIBRARIES:

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

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

[Touch-packages] [Bug 1668699] Re: Drop "Open a " from .desktop Actions

2017-03-01 Thread Olivier Tilloy

The proposed change looks sound to me, thanks for the report and the patch!
I’d like to get feedback from design before merging, adding a ubuntu-ux task.

** Branch linked: lp:~jbicha/webbrowser-app/drop-open-a-prefix

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

** Changed in: webbrowser-app (Ubuntu)
   Status: New => In Progress

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Low

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

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

Title:
   Drop "Open a " from .desktop Actions

Status in Ubuntu UX:
  New
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Start the Web Browser app.
  Right-click on its icon in Unity's Dash (the strip on the left side of the 
screen).
  There are two custom Actions: "Open a New Window" and "Open a New Private 
Window".

  I propose that the "Open a " prefix be dropped.

  This provides greater consistency with other apps which just use "New
  Window" or "New Document" Actions. Examples include epiphany-browser,
  gedit, LibreOffice and Nautilus.

  In GNOME Shell, Actions show in the Activities Overview. GNOME Shell
  includes a default "New Window" action. So in GNOME Shell, the actions
  shown include the duplicate "New Window" and "Open a New Window".
  (Note that an explicit "New Window" shortcut does not duplicate the
  default "New Window" in GNOME Shell as long as the action is named
  new-window.)

  See also LP: #1668664 for Firefox and LP: #1668730 for Chromium.

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

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

[Touch-packages] [Bug 1668951] [NEW] package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-03-01 Thread Roland

Public bug reported:

Systempackage is corrupt

1. 

2. 

3. Update

4- 

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic i686
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: i386
Date: Wed Mar  1 12:00:25 2017
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2013-09-01 (1276 days ago)
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 
(20130820.1)
Lpstat: device for MFC7360N: usb://Brother/MFC-7360N?serial=E69717J1N892883
MachineType: Dell Inc. Inspiron One 2320
Papersize: a4
PpdFiles: MFC7360N: Brother MFC-7225N BR-Script3
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=f58ec9cd-7c26-49be-9698-46cb6bcfae59 ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=f58ec9cd-7c26-49be-9698-46cb6bcfae59 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: cups
Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2017-01-17 (43 days ago)
dmi.bios.date: 09/17/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0JC4YH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 13
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: PRFirestone_P7PG1_A01.SDR
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd09/17/2012:svnDellInc.:pnInspironOne2320:pvr00:rvnDellInc.:rn0JC4YH:rvrA00:cvnDellInc.:ct13:cvrPRFirestone_P7PG1_A01.SDR:
dmi.product.name: Inspiron One 2320
dmi.product.version: 00
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.default.cups:
 # Cups configure options
 
 # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
 # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
 # LOAD_LP_MODULE=yes
mtime.conffile..etc.default.cups: 2014-08-23T09:12:01.222658

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


** Tags: apport-package i386 need-duplicate-check xenial

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

Title:
  package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  New

Bug description:
  Systempackage is corrupt

  1. 

  2. 

  3. Update

  4- 

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Wed Mar  1 12:00:25 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2013-09-01 (1276 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 
(20130820.1)
  Lpstat: device for MFC7360N: usb://Brother/MFC-7360N?serial=E69717J1N892883
  MachineType: Dell Inc. Inspiron One 2320
  Papersize: a4
  PpdFiles: MFC7360N: Brother MFC-7225N BR-Script3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=f58ec9cd-7c26-49be-9698-46cb6bcfae59 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=f58ec9cd-7c26-49be-9698-46cb6bcfae59 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-01-17 (43 days ago)
  dmi.bios.date: 09/17/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0JC4YH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: PRFirestone_P7PG1_A01.SDR
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd09/17/2012:svnDellInc.:pnInspironOne2320:pvr00:rvnDellInc.:rn0JC4YH:rvrA00:cvnDellInc.:ct13:cvrPRFirestone_P7PG1_A01.SDR:
  dmi.product.name: Inspiron One 2320
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-08-23T09:12:01.222658

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

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

[Touch-packages] [Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

2017-03-01 Thread mohican

Solution from post #8 works partially for me : Asus R556UB, with Linux
Mint 18

Thanks to it I do now have input sound from webcam mic and output sound from 
internal speakers.
However I do not have output sound from external headphone.

To be noted : when rebooting from Windows 10 (dual-boot) sound is lost.
To recover : shutdown and restart the GNU/Linux OS.

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  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/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  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.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1668944] Re: The _apt user ignores group membership.

2017-03-01 Thread David Kalnischkies

The recommended way is "chown _apt:root FILE && chmod 400 FILE" at the moment.
Ideally we wouldn't need the chown (or have it root:root), but that isn't very
realistic to be implementable without rolling our own TLS stack in the process
at the moment, so we have to make due with that for now.
Disabling the feature or making the file world readable does work as well, but
totally defeats the point of course…

I don't see what the point of trying to us groups here is. Are you
trying to share the same certificate for multiple things? If so that's a
bad idea. You should have a certificate for each and every usecase (=
client), not a single one shared between multiple clients on the same
machine.

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

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

Title:
The _apt user ignores group membership.

Status in apt package in Ubuntu:
Invalid

Then I tried to open these files as user '_apt' in bash (su -s
/bin/bash _apt) which works well.

But if I run: "apt-get -o "Debug::Acquire::https=true" update" I still get
the following error:
* error reading ca cert file /etc/certs/mycert/ca.pem (Error while reading
file.)
* Closing connection 26

So my guess is that apt somehow ignores the ssl-cert membership.

Neither of them is pretty.
Maybe this is a wanted behavior, then just suggest how to fix the issue in
nice way.

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

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

[Touch-packages] [Bug 1638345] Re: avahi-daemon crashes multiple times an hour

2017-03-01 Thread Martin Mach

Same here - the problem occurred several times. Fresh install didn't
solve it though. I can confirm that it happens probably only on MSCHAPv2
WiFi networks.

16.10, 4.8.0-39-generic.

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

Title:
  avahi-daemon crashes multiple times an hour

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Ever since upgrading to 16.10, avahi-daemon crashes multiple times an
  hour, leading to the prompt to report the issue to Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: avahi-daemon 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  1 10:48:35 2016
  InstallationDate: Installed on 2016-07-08 (115 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago)

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

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

[Touch-packages] [Bug 1550983] Re: Fails to start with "Couldn't open libGL.so.1" (missing dependency?)

2017-03-01 Thread Robie Basak

> I have just verified it for Trusty and Yakkety

I take it you mean *Xenial* and Yakkety? Please could you report the
package names and versions that were tested to avoid any error?

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

Title:
  Fails to start with "Couldn't open libGL.so.1" (missing dependency?)

Status in One Hundred Papercuts:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  Fix Committed
Status in gtk+3.0 source package in Yakkety:
  Fix Committed
Status in gtk+3.0 package in Debian:
  Fix Released

Bug description:
  [Impact]
  There are some unlinked calls to libGL.so.1 undetected in the build process 
because of using libepoxy. Running an application that does not depend on 
libgl1 (directly or indirectly) may lead to aborting the process with an 
undefined reference to libGL.so.1.

  [Test Case]
  1. Deploy a server / cloud image of Xenial or Yakkety.
  2. Use a Windows or a Mac client with Cygwin/X and ssh -XY to Ubuntu machine.
  3. sudo apt install firefox; firefox

  Expected result:
  firefox is launched on the client machine.

  Actual result:
  "Couldn't open libGL.so.1" message is printed.

  [Regression Potential]
  Minimal, it is an upstream change already released to zesty. It performs a 
runtime check for GL support and disables GLX function calls in case they're 
not available.

  [Other Info]
  Original bug description:

  virt-manager fails to start:

  $ virt-manager --debug --no-fork
  [Sun, 28 Feb 2016 19:18:22 virt-manager 7592] DEBUG (cli:256) Launched with 
command line: /usr/share/virt-manager/virt-manager --debug --no-fork
  [Sun, 28 Feb 2016 19:18:22 virt-manager 7592] DEBUG (virt-manager:143) 
virt-manager version: 1.3.2
  [Sun, 28 Feb 2016 19:18:22 virt-manager 7592] DEBUG (virt-manager:144) 
virtManager import: 
  Couldn't open libGL.so.1: libGL.so.1: cannot open shared object file: No such 
file or directory
  $

  Installing the 'libgl1-mesa-glx' package resolves the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: virt-manager 1:1.3.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sun Feb 28 19:19:27 2016
  InstallationDate: Installed on 2016-02-27 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160206)
  PackageArchitecture: all
  SourcePackage: virt-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1665289] Re: [unity8]Ubuntu Software doesn't launch installed apps

** Also affects: gnome-software (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [unity8]Ubuntu Software doesn't launch installed apps

Status in Canonical System Image:
  New
Status in gnome-software package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  ubuntu 17.04 unity8

  launch Ubuntu Software
  install some random app (deb or snap) and after it is installed click on the 
Launch button. 
  the app doesn't launch

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

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

[Touch-packages] [Bug 1550983] Re: Fails to start with "Couldn't open libGL.so.1" (missing dependency?)

2017-03-01 Thread Dariusz Gadomski

Of course I meant Xenial and Yakkety. Thanks for noticing that Robie.

The versions I tested:
* Xenial
libgtk-3-0:
  Installed: 3.18.9-1ubuntu3.2
* Yakkety:
libgtk-3-0:
  Installed: 3.20.9-1ubuntu2.1

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

Title:
  Fails to start with "Couldn't open libGL.so.1" (missing dependency?)

Status in One Hundred Papercuts:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  Fix Committed
Status in gtk+3.0 source package in Yakkety:
  Fix Committed
Status in gtk+3.0 package in Debian:
  Fix Released

Bug description:
  [Impact]
  There are some unlinked calls to libGL.so.1 undetected in the build process 
because of using libepoxy. Running an application that does not depend on 
libgl1 (directly or indirectly) may lead to aborting the process with an 
undefined reference to libGL.so.1.

  [Test Case]
  1. Deploy a server / cloud image of Xenial or Yakkety.
  2. Use a Windows or a Mac client with Cygwin/X and ssh -XY to Ubuntu machine.
  3. sudo apt install firefox; firefox

  Expected result:
  firefox is launched on the client machine.

  Actual result:
  "Couldn't open libGL.so.1" message is printed.

  [Regression Potential]
  Minimal, it is an upstream change already released to zesty. It performs a 
runtime check for GL support and disables GLX function calls in case they're 
not available.

  [Other Info]
  Original bug description:

  virt-manager fails to start:

  $ virt-manager --debug --no-fork
  [Sun, 28 Feb 2016 19:18:22 virt-manager 7592] DEBUG (cli:256) Launched with 
command line: /usr/share/virt-manager/virt-manager --debug --no-fork
  [Sun, 28 Feb 2016 19:18:22 virt-manager 7592] DEBUG (virt-manager:143) 
virt-manager version: 1.3.2
  [Sun, 28 Feb 2016 19:18:22 virt-manager 7592] DEBUG (virt-manager:144) 
virtManager import: 
  Couldn't open libGL.so.1: libGL.so.1: cannot open shared object file: No such 
file or directory
  $

  Installing the 'libgl1-mesa-glx' package resolves the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: virt-manager 1:1.3.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sun Feb 28 19:19:27 2016
  InstallationDate: Installed on 2016-02-27 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160206)
  PackageArchitecture: all
  SourcePackage: virt-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1668979] [NEW] package lvm2 2.02.98-6ubuntu failed to install%%C3%A9Fupgrade%3A le sous processus nouveau script pre-installation a retourn C3 A9 une erreur de sortie d%27 C3 A9t

2017-03-01 Thread Bernard Rpacchi

Public bug reported:

trying to do an do-release-upgrade to 16.04.2 LTS

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: lvm2 2.02.98-6ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-110.157-generic 3.13.11-ckt39
Uname: Linux 3.13.0-110-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
Date: Wed Mar  1 13:54:20 2017
DuplicateSignature: package:lvm2:2.02.98-6ubuntu2:le sous-processus nouveau 
script pre-installation a retourné une erreur de sortie d'état 2
ErrorMessage: le sous-processus nouveau script pre-installation a retourné une 
erreur de sortie d'état 2
InstallationDate: Installed on 2014-01-27 (1129 days ago)
InstallationMedia: Ubuntu-Server 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.0.1ubuntu2.17
SourcePackage: lvm2
Title: package lvm2 2.02.98-6ubuntu2 failed to install/upgrade: le 
sous-processus nouveau script pre-installation a retourné une erreur de sortie 
d'état 2
UpgradeStatus: Upgraded to xenial on 2017-03-01 (0 days ago)

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


** Tags: amd64 apport-package need-duplicate-check third-party-packages xenial

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

Title:
  package lvm2 2.02.98-6ubuntu failed to install%%C3%A9Fupgrade%3A le
  sous processus nouveau script pre-installation a retourn C3 A9 une
  erreur de sortie d%27 C3 A9tat 2

Status in lvm2 package in Ubuntu:
  New

Bug description:
  trying to do an do-release-upgrade to 16.04.2 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lvm2 2.02.98-6ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-110.157-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-110-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Wed Mar  1 13:54:20 2017
  DuplicateSignature: package:lvm2:2.02.98-6ubuntu2:le sous-processus nouveau 
script pre-installation a retourné une erreur de sortie d'état 2
  ErrorMessage: le sous-processus nouveau script pre-installation a retourné 
une erreur de sortie d'état 2
  InstallationDate: Installed on 2014-01-27 (1129 days ago)
  InstallationMedia: Ubuntu-Server 12.04.3 LTS "Precise Pangolin" - Release 
amd64 (20130820.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.0.1ubuntu2.17
  SourcePackage: lvm2
  Title: package lvm2 2.02.98-6ubuntu2 failed to install/upgrade: le 
sous-processus nouveau script pre-installation a retourné une erreur de sortie 
d'état 2
  UpgradeStatus: Upgraded to xenial on 2017-03-01 (0 days ago)

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

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

[Touch-packages] [Bug 1668944] Re: The _apt user ignores group membership.

2017-03-01 Thread Reik Keutterling

Ok, but:

Why is it a bad idea to have a shared client certificate between multiple
client applications on the same host?
Why is apt-get just not "respecting" the groups of the _apt user?

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

Title:
The _apt user ignores group membership.

Status in apt package in Ubuntu:
Invalid

Then I tried to open these files as user '_apt' in bash (su -s
/bin/bash _apt) which works well.

But if I run: "apt-get -o "Debug::Acquire::https=true" update" I still get
the following error:
* error reading ca cert file /etc/certs/mycert/ca.pem (Error while reading
file.)
* Closing connection 26

So my guess is that apt somehow ignores the ssl-cert membership.

Neither of them is pretty.
Maybe this is a wanted behavior, then just suggest how to fix the issue in
nice way.

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

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

[Touch-packages] [Bug 1668982] [NEW] Backport memory leak fix

2017-03-01 Thread Albert Astals Cid

Public bug reported:

https://codereview.qt-project.org/#/c/187028/2

fixes a small memory leak that happens in some corner case.

It's not very important but nice to have.

** Affects: qtdeclarative-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Backport memory leak fix

Status in qtdeclarative-opensource-src package in Ubuntu:
  New

Bug description:
  https://codereview.qt-project.org/#/c/187028/2

  fixes a small memory leak that happens in some corner case.

  It's not very important but nice to have.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1668982/+subscriptions

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

[Touch-packages] [Bug 1668982] Re: Backport memory leak fix

2017-03-01 Thread Timo Jyrinki

** Changed in: qtdeclarative-opensource-src (Ubuntu)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

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

Title:
  Backport memory leak fix

Status in qtdeclarative-opensource-src package in Ubuntu:
  New

Bug description:
  https://codereview.qt-project.org/#/c/187028/2

  fixes a small memory leak that happens in some corner case.

  It's not very important but nice to have.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1668982/+subscriptions

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

[Touch-packages] [Bug 1641417] Re: Ubuntu 16.04 unable to detect/connect to and work properly with iPhone 4.

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

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

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

Title:
  Ubuntu 16.04 unable to detect/connect  to and work properly with
  iPhone 4.

Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  
  Action 1: Plug an iPhone 4 to a just booted up Ubuntu 16.04 workstation. 
  Result 1: 2 iPhone connections appear in Nautilus. 1st connect is mount via 
gphoto2, where access is limited to viewing and copying photos and videos. The 
2nd connection that is mounted via afc fail to work, hence other folders in 
iPhone are not accessible.

  Action 2: Unplugged and re-plugged iPhone 4 to the workstation.
  Result 2: iPhone 4 does not reappear in Nautilus at all. No iPhone mount 
point appear.

  Checks and Remedy used: 
  1. "ideviceinfo" and lsusb command show iPhone 4 is connected.
  2. "idevicepair validate" command shows "SUCCESS: Validated pairing with 
device [UDID]"
  3. After running "ifuse /media/iPhone" command, iPhone 4 reappears in 
Nautilus as mounted in /media/iPhone. Furthermore, all folders of iPhone 4 
appears and are accessible.

  I believe the 1st mounting of iPhone 4 on Nautilus is due to the
  "gvfs-backends" package. W/o it, auto detection/connection of iPhone 4
  would not occur and appear in Nautilus. However, the afc mount failed
  to work

  The 2nd mounting is caused by ifuse. This works perfectly but requires
  manual mounting and unmounting.

  
  Questions: 
  1. How to overcome issues/failures mentioned in Result 1 & 2? 
  2. Ideally, i would like the automatic detection-connection between Ubuntu 
and iPhone to work. If not, is there a way to automate connection via ifuse? 

  
  System and package info:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  $ uname -or
  4.4.0-47-generic GNU/Linux

  $ dpkg -l | grep iPhone
  ii  ifuse1.1.2-0.1build3 amd64  FUSE module for 
iPhone and iPod Touch devices
  ii  libimobiledevice-utils   1.2.0+dfsg-3~ubuntu0.2  amd64  Library for 
communicating with iPhone and iPod Touch devices
  ii  libimobiledevice6:amd64  1.2.0+dfsg-3~ubuntu0.2  amd64  Library for 
communicating with the iPhone and iPod Touch
  ii  libusbmuxd-tools 1.0.10-2ubuntu0.1   amd64  USB multiplexor 
daemon for iPhone and iPod Touch devices - tools
  ii  libusbmuxd4:amd641.0.10-2ubuntu0.1   amd64  USB multiplexor 
daemon for iPhone and iPod Touch devices - library
  ii  usbmuxd  1.1.0-2 amd64  USB multiplexor 
daemon for iPhone and iPod Touch devices

  $ dpkg -l | grep libusb
  ii  libgusb2:amd64   0.2.9-0ubuntu1  amd64   GLib wrapper around 
libusb1
  ii  libusb-0.1-4:amd64   2:0.1.12-28 amd64   userspace USB 
programming library
  ii  libusb-1.0-0:amd64   2:1.0.20-1  amd64   userspace USB 
programming library
  ii  libusb-1.0-0:i3862:1.0.20-1  i386userspace USB 
programming library
  ii  libusbmuxd-tools 1.0.10-2ubuntu0.1   amd64   USB multiplexor 
daemon for iPhone and iPod Touch devices - tools
  ii  libusbmuxd4:amd641.0.10-2ubuntu0.1   amd64   USB multiplexor 
daemon for iPhone and iPod Touch devices - library
  ii  libusbredirhost1:amd64   0.7.1-1 amd64   Implementing the 
usb-host (*) side of a usbredir connection (runtime)
  ii  libusbredirparser1:amd64 0.7.1-1 amd64   Parser for the 
usbredir protocol (runtime)

  $ dpkg -l | grep gvfs
  ii  gvfs:amd64  1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - GIO module
  ii  gvfs-backends   1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - backends
  ii  gvfs-bin1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - binaries
  ii  gvfs-common 1.28.2-1ubuntu1~16.04.1alluserspace virtual 
filesystem - common data files
  ii  gvfs-daemons1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - servers
  ii  gvfs-fuse   1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - fuse server
  ii  gvfs-libs:amd64 1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - private libraries

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

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

[Touch-packages] [Bug 1641417] Re: Ubuntu 16.04 unable to detect/connect to and work properly with iPhone 4.

2017-03-01 Thread Filip Pytloun

Hello,

I hit the same issue. Strange is that iPhone gets detected and it can mount 
gthumb:// and afc:// handle.. but it's using port 3 instead of port 0 which 
should be used instead.
I can mount afc manually just fine, access files, etc. but applications still 
doesn't see the iPhone properly to be able to sync.

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

Title:
  Ubuntu 16.04 unable to detect/connect  to and work properly with
  iPhone 4.

Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  
  Action 1: Plug an iPhone 4 to a just booted up Ubuntu 16.04 workstation. 
  Result 1: 2 iPhone connections appear in Nautilus. 1st connect is mount via 
gphoto2, where access is limited to viewing and copying photos and videos. The 
2nd connection that is mounted via afc fail to work, hence other folders in 
iPhone are not accessible.

  Action 2: Unplugged and re-plugged iPhone 4 to the workstation.
  Result 2: iPhone 4 does not reappear in Nautilus at all. No iPhone mount 
point appear.

  Checks and Remedy used: 
  1. "ideviceinfo" and lsusb command show iPhone 4 is connected.
  2. "idevicepair validate" command shows "SUCCESS: Validated pairing with 
device [UDID]"
  3. After running "ifuse /media/iPhone" command, iPhone 4 reappears in 
Nautilus as mounted in /media/iPhone. Furthermore, all folders of iPhone 4 
appears and are accessible.

  I believe the 1st mounting of iPhone 4 on Nautilus is due to the
  "gvfs-backends" package. W/o it, auto detection/connection of iPhone 4
  would not occur and appear in Nautilus. However, the afc mount failed
  to work

  The 2nd mounting is caused by ifuse. This works perfectly but requires
  manual mounting and unmounting.

  
  Questions: 
  1. How to overcome issues/failures mentioned in Result 1 & 2? 
  2. Ideally, i would like the automatic detection-connection between Ubuntu 
and iPhone to work. If not, is there a way to automate connection via ifuse? 

  
  System and package info:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  $ uname -or
  4.4.0-47-generic GNU/Linux

  $ dpkg -l | grep iPhone
  ii  ifuse1.1.2-0.1build3 amd64  FUSE module for 
iPhone and iPod Touch devices
  ii  libimobiledevice-utils   1.2.0+dfsg-3~ubuntu0.2  amd64  Library for 
communicating with iPhone and iPod Touch devices
  ii  libimobiledevice6:amd64  1.2.0+dfsg-3~ubuntu0.2  amd64  Library for 
communicating with the iPhone and iPod Touch
  ii  libusbmuxd-tools 1.0.10-2ubuntu0.1   amd64  USB multiplexor 
daemon for iPhone and iPod Touch devices - tools
  ii  libusbmuxd4:amd641.0.10-2ubuntu0.1   amd64  USB multiplexor 
daemon for iPhone and iPod Touch devices - library
  ii  usbmuxd  1.1.0-2 amd64  USB multiplexor 
daemon for iPhone and iPod Touch devices

  $ dpkg -l | grep libusb
  ii  libgusb2:amd64   0.2.9-0ubuntu1  amd64   GLib wrapper around 
libusb1
  ii  libusb-0.1-4:amd64   2:0.1.12-28 amd64   userspace USB 
programming library
  ii  libusb-1.0-0:amd64   2:1.0.20-1  amd64   userspace USB 
programming library
  ii  libusb-1.0-0:i3862:1.0.20-1  i386userspace USB 
programming library
  ii  libusbmuxd-tools 1.0.10-2ubuntu0.1   amd64   USB multiplexor 
daemon for iPhone and iPod Touch devices - tools
  ii  libusbmuxd4:amd641.0.10-2ubuntu0.1   amd64   USB multiplexor 
daemon for iPhone and iPod Touch devices - library
  ii  libusbredirhost1:amd64   0.7.1-1 amd64   Implementing the 
usb-host (*) side of a usbredir connection (runtime)
  ii  libusbredirparser1:amd64 0.7.1-1 amd64   Parser for the 
usbredir protocol (runtime)

  $ dpkg -l | grep gvfs
  ii  gvfs:amd64  1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - GIO module
  ii  gvfs-backends   1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - backends
  ii  gvfs-bin1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - binaries
  ii  gvfs-common 1.28.2-1ubuntu1~16.04.1alluserspace virtual 
filesystem - common data files
  ii  gvfs-daemons1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - servers
  ii  gvfs-fuse   1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - fuse server
  ii  gvfs-libs:amd64 1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - private libraries

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

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

[Touch-packages] [Bug 1666495] Re: [Zesty] No default apps shown on first start in kvm oem end user

2017-03-01 Thread Iain Lane

uploaded, please test tomorrow once it hits an image

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

Title:
  [Zesty] No default apps shown on first start in kvm oem end user

Status in unity-lens-applications:
  Invalid
Status in zeitgeist package in Ubuntu:
  In Progress

Bug description:
  STEPS:
  1. Install the latest iso in kvm
  2. Click on Ubuntu button

  EXPECTED:
  I expect to see Thunderbird, rhythmbox, totem, etc.  There are normally 5 
default apps shown.

  ACTUAL:
  I get what you see in the attached screenshot.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-02-21 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170221)
  Package: unity-lens-applications 7.1.0+16.10.20160927-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Tags:  zesty
  Uname: Linux 4.10.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-lens-applications/+bug/1666495/+subscriptions

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

[Touch-packages] [Bug 1668608] Re: [unity8] main menu active when kate is maximized, you can open multiple child window

** Summary changed:

- [unity8] main menu active when kate is maximized, you can open many child 
window 
+ [unity8] main menu active when kate is maximized, you can open multiple child 
window

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

Title:
  [unity8] main menu active when kate is maximized, you can open
  multiple child window

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

Bug description:
  ubuntu 17.04 Unity 8
  [unity8] main menu active when kate is maximized, you can open multiple child 
windows (kinda cool but probably wrong) but if you close kate while the child 
windows are opened the windows close but the kate process remains noming 100% 
CPU until forever (or until the process is killed/terminated)

  see attached screenshot

  launch kate, maximize, from the menu About -> Kate, About KDE, File
  Open etc, open a lot of child windows

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

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

[Touch-packages] [Bug 1442851] Re: Checkbox labels ellipsized on phone screen in portrait orientation

2017-03-01 Thread Christian Dywan

** Branch linked: lp:~daker/ubuntu-ui-toolkit/fix.1333228

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

Title:
  Checkbox labels ellipsized on phone screen in portrait orientation

Status in Ubuntu UX:
  Fix Committed
Status in webbrowser-app:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Vivid:
  Confirmed

Bug description:
  Browser's Settings screen shows an example of a checkbox where its
  label does not fit in the available screen width, so it is ellipsized.
   The only way
  to see what the option means is to switch the phone to landscape.

  Even if an app developer avoids this, in portrait mode, on the
  smallest shipping phone, for every string in their app, in English,
  they are quite likely not to check their app in every shipping
  language. And the app may not provide a landscape mode at all. So
  ellipsizing the label is not an ideal solution.

  : "A checkbox or switch should almost always
  have a label, which can be tapped just like the checkbox or switch
  itself. If there is not enough room to display the label on one line,
  by default it should wrap to multiple lines. It should not be cropped
  or ellipsized unless the app developer specifically requests this,
  typically for text that they do not control the length of (such as a
  Wi-Fi network name, filename, or bookmark title)."

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

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

[Touch-packages] [Bug 1669010] [NEW] Window does not remember size when using keyboard shortcuts

2017-03-01 Thread Victor gonzalez

Public bug reported:

Story: this is a detail I noticed while testing bug fix for LP: #1312892
in webbrowser silo 2504. If the user wants to resize/move/close the
window only with the mouse it might remember the size and will work
right, but using keyboard shortcuts to resize/move/close like
ctrl+super+arrows and alt+F4 can make it fail.

Environment: unity8-deb session on zesty+silo 2504

Test case 1

1. Open webbrowser and press ctrl+super+up arrow to maximize
2. Close webbrowser with the mouse or alt+F4
3. Open webbrowser again and check the window size

Expected result: webbrowser appears maximized
Current result: on first boot webbrowser appears with its normal/by default size

Test case 2

1. Open webbrowser and press ctrl+super+right arrow to put it on the right edge
2. Close webbrowser with the mouse or alt+F4
3. Open webbrowser again and check its size and position

Expected result: webbrowser should open next to the right edge
Current result: webbrowser does not start oon the right edge

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Assignee: Lukáš Tinkl (lukas-kde)
 Status: In Progress

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: Invalid

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

** Description changed:

  Story: this is a detail I noticed while testing bug fix for LP: #1312892
  in webbrowser silo 2504. If the user wants to resize/move/close the
  window only with the mouse it might remember the size and will work
  right, but using keyboard shortcuts to resize/move/close like
- ctrl+super+arrows and alt+F4 can make the test case fail.
+ ctrl+super+arrows and alt+F4 can make it fail.
  
  Environment: unity8-deb session on zesty+silo 2504
  
  Test case 1
  
- 1. Open webbrowser and press ctrl+super+up arrow to maximize 
+ 1. Open webbrowser and press ctrl+super+up arrow to maximize
  2. Close webbrowser with the mouse or alt+F4
  3. Open webbrowser again and check the window size
  
  Expected result: webbrowser appears maximized
  Current result: on first boot webbrowser appears with its normal/by default 
size
  
  Test case 2
  
- 1. Open webbrowser and press ctrl+super+right arrow to put it on the right 
edge 
+ 1. Open webbrowser and press ctrl+super+right arrow to put it on the right 
edge
  2. Close webbrowser with the mouse or alt+F4
  3. Open webbrowser again and check its size and position
  
  Expected result: webbrowser should open next to the right edge
  Current result: webbrowser does not start oon the right edge

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

Title:
  Window does not remember size when using keyboard shortcuts

Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Story: this is a detail I noticed while testing bug fix for LP:
  #1312892 in webbrowser silo 2504. If the user wants to
  resize/move/close the window only with the mouse it might remember the
  size and will work right, but using keyboard shortcuts to
  resize/move/close like ctrl+super+arrows and alt+F4 can make it fail.

  Environment: unity8-deb session on zesty+silo 2504

  Test case 1

  1. Open webbrowser and press ctrl+super+up arrow to maximize
  2. Close webbrowser with the mouse or alt+F4
  3. Open webbrowser again and check the window size

  Expected result: webbrowser appears maximized
  Current result: on first boot webbrowser appears with its normal/by default 
size

  Test case 2

  1. Open webbrowser and press ctrl+super+right arrow to put it on the right 
edge
  2. Close webbrowser with the mouse or alt+F4
  3. Open webbrowser again and check its size and position

  Expected result: webbrowser should open next to the right edge
  Current result: webbrowser does not start oon the right edge

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

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

[Touch-packages] [Bug 1665598] Re: python-crypto throws exception ValueError: CTR mode needs counter parameter, not IV

2017-03-01 Thread Ryan Beisner

** Changed in: charm-test-infra
Milestone: None => 17.05

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

Title:
  python-crypto throws exception ValueError: CTR mode needs counter
  parameter, not IV

Status in OpenStack Charm Test Infra:
  Fix Released
Status in python-crypto package in Ubuntu:
  Fix Released

Bug description:
  We've recently upgraded python-crypto package on 14.04 due to this USN
  https://www.ubuntu.com/usn/usn-3199-1/

  
  apt history log

  ```
  Start-Date: 2017-02-16  23:43:48
  Commandline: apt-get -q -y -o DPkg::Options::=--force-confold -o 
DPkg::Options::=--force-confdef dist-upgrade
  Upgrade: bind9-host:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), 
liblwres90:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), 
python-crypto:amd64 (2.6.1-4build1, 2.6.1-4ubuntu0.1), libdns100:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libisccfg90:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libbind9-90:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), bind9:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), dnsutils:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), bind9utils:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libisccc90:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libisc95:amd64 
(9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13)
  End-Date: 2017-02-16  23:43:52
  ```

  Then our python script which uses paramiko failed with this exception

  ```
  Traceback (most recent call last):
File 
"/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/transport.py", 
line 1583, in run
  self.kex_engine.parse_next(ptype, m)
File 
"/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/kex_group1.py", 
line 68, in parse_next
  return self._parse_kexdh_reply(m)
File 
"/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/kex_group1.py", 
line 107, in _parse_kexdh_reply
  self.transport._activate_outbound()
File 
"/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/transport.py", 
line 1881, in _activate_outbound
  engine = self._get_cipher(self.local_cipher, key_out, IV_out)
File 
"/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/transport.py", 
line 1500, in _get_cipher
  return self._cipher_info[name]['class'].new(key, 
self._cipher_info[name]['mode'], iv, counter)
File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 94, in 
new
  return AESCipher(key, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 59, in 
__init__
  blockalgo.BlockAlgo.__init__(self, _AES, key, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/blockalgo.py", line 
141, in __init__
  self._cipher = factory.new(key, *args, **kwargs)
  ValueError: CTR mode needs counter parameter, not IV

  ```

  packages versions

  ```
  pycrypto==2.6.1
  paramiko==1.12.0
  ```

  which works okay BEFORE the upgrade.

  Maybe Debian bug report: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=850025

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-test-infra/+bug/1665598/+subscriptions

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

[Touch-packages] [Bug 1669010] Re: Window does not remember size when using keyboard shortcuts

** Branch linked: lp:~lukas-kde/unity8/fix-shell-chrome

** Changed in: webbrowser-app (Ubuntu)
   Status: New => In Progress

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

** Changed in: webbrowser-app (Ubuntu)
   Status: In Progress => Invalid

** Changed in: unity8 (Ubuntu)
   Status: Invalid => In Progress

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Lukáš Tinkl (lukas-kde)

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

Title:
  Window does not remember size when using keyboard shortcuts

Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Story: this is a detail I noticed while testing bug fix for LP:
  #1312892 in webbrowser silo 2504. If the user wants to
  resize/move/close the window only with the mouse it might remember the
  size and will work right, but using keyboard shortcuts to
  resize/move/close like ctrl+super+arrows and alt+F4 can make it fail.

  Environment: unity8-deb session on zesty+silo 2504

  Test case 1

  1. Open webbrowser and press ctrl+super+up arrow to maximize
  2. Close webbrowser with the mouse or alt+F4
  3. Open webbrowser again and check the window size

  Expected result: webbrowser appears maximized
  Current result: on first boot webbrowser appears with its normal/by default 
size

  Test case 2

  1. Open webbrowser and press ctrl+super+right arrow to put it on the right 
edge
  2. Close webbrowser with the mouse or alt+F4
  3. Open webbrowser again and check its size and position

  Expected result: webbrowser should open next to the right edge
  Current result: webbrowser does not start oon the right edge

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

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

[Touch-packages] [Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

2017-03-01 Thread Laurent Bonnaud

I am still seeing this error with the 4.10.1-041001-generic mainline
kernel.

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

Title:
  systemd-udevd: Error calling EVIOCSKEYCODE on device node
  '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  the symptom is this error message in my system's logs:

  juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling
  EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key
  code 190): Invalid argument

  According to /proc/bus/input/devices the corresponding input device
  is:

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Dell WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1000b0400 0 e 0
  B: MSC=10

  This laptop is a Dell Latitude E6520.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Wed Jun 29 17:43:01 2016
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

2017-03-01 Thread Peter S

It definitely could be. Personally, I think many of the issues mentioned
above are completely unrelated to Network Manager. Those cases should be
excluded from a bug report. Therefore I suggest that everyone who's
having problems check their beacon interval settings.

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

Title:
  cannot view wifi networks after re-enabling wifi

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

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

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

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

[Touch-packages] [Bug 1442851] Re: Checkbox labels ellipsized on phone screen in portrait orientation

2017-03-01 Thread Christian Dywan

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Triaged => In Progress

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Adnane Belmadiaf (daker)

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

Title:
  Checkbox labels ellipsized on phone screen in portrait orientation

Status in Ubuntu UX:
  Fix Committed
Status in webbrowser-app:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Vivid:
  Confirmed

Bug description:
  Browser's Settings screen shows an example of a checkbox where its
  label does not fit in the available screen width, so it is ellipsized.
   The only way
  to see what the option means is to switch the phone to landscape.

  Even if an app developer avoids this, in portrait mode, on the
  smallest shipping phone, for every string in their app, in English,
  they are quite likely not to check their app in every shipping
  language. And the app may not provide a landscape mode at all. So
  ellipsizing the label is not an ideal solution.

  : "A checkbox or switch should almost always
  have a label, which can be tapped just like the checkbox or switch
  itself. If there is not enough room to display the label on one line,
  by default it should wrap to multiple lines. It should not be cropped
  or ellipsized unless the app developer specifically requests this,
  typically for text that they do not control the length of (such as a
  Wi-Fi network name, filename, or bookmark title)."

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

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

[Touch-packages] [Bug 1666495] Re: [Zesty] No default apps shown on first start in kvm oem end user

This bug was fixed in the package zeitgeist - 1.0-0ubuntu1

---
zeitgeist (1.0-0ubuntu1) zesty; urgency=medium

  [ Jeremy Bicha ]
  * New upstream release (LP: #1665902)
  * debian/control:
- Drop Build-Depends on intltool
  * Drop patches applied in new release
- Give-the-D-Bus-service-files-the-correct-names.patch
- Add-a-systemd-user-service-for-each-D-Bus-session-se.patch
- fix_autocomplete.diff
- fix-test-crash.patch
- thread-default-context.patch
  * Refresh patches

  [ Iain Lane ]
  * Fix debian/patches/startup-database-vacuum.patch
- The vacuum mode is now included upstream
- Move the wrapper script to a file in debian/ and install that
- Call the wrapper and allow it to fail so that zeitgeist starts for new
  users (LP: #1666495)
  * debian/patches/0001-Fix-placeholder-in-systemd-service-template.patch:
Cherry-pick. Fix substitution in systemd unit file.

 -- Iain Lane   Wed, 01 Mar 2017 14:09:01
+

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

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

Title:
  [Zesty] No default apps shown on first start in kvm oem end user

Status in unity-lens-applications:
  Invalid
Status in zeitgeist package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Install the latest iso in kvm
  2. Click on Ubuntu button

  EXPECTED:
  I expect to see Thunderbird, rhythmbox, totem, etc.  There are normally 5 
default apps shown.

  ACTUAL:
  I get what you see in the attached screenshot.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-02-21 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170221)
  Package: unity-lens-applications 7.1.0+16.10.20160927-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Tags:  zesty
  Uname: Linux 4.10.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-lens-applications/+bug/1666495/+subscriptions

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

[Touch-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd reports "Not enough handles to register service" at start

2017-03-01 Thread Laurent Bonnaud

On Ubuntu 16.10 with this bluez package:

Package: bluez
Version: 5.41-0ubuntu3with 

I no longer see the "Not enough handles to register service" messages.


** Tags added: xenial

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

Title:
  15:10 and 16.04: bluetoothd reports "Not enough handles to register
  service" at start

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl start bluetooth
  $ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print 
$0}'
23:31:53  systemd[1]: Starting Bluetooth service...
23:31:53  bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53  systemd[1]: Started Bluetooth service.
23:31:53  bluetoothd[16647]: Starting SDP server
23:31:53  bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53  bluetoothd[16647]: Failed to obtain handles for "Service Changed" 
characteristic
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Error adding Link Loss service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Current Time Service could not be registered
23:31:53  bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Sap driver initialization failed.
23:31:53  bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSource
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSink

  And

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

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

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

[Touch-packages] [Bug 1665902] Re: Update zeitgeist to 1.0

This bug was fixed in the package zeitgeist - 1.0-0ubuntu1

---
zeitgeist (1.0-0ubuntu1) zesty; urgency=medium

  [ Jeremy Bicha ]
  * New upstream release (LP: #1665902)
  * debian/control:
- Drop Build-Depends on intltool
  * Drop patches applied in new release
- Give-the-D-Bus-service-files-the-correct-names.patch
- Add-a-systemd-user-service-for-each-D-Bus-session-se.patch
- fix_autocomplete.diff
- fix-test-crash.patch
- thread-default-context.patch
  * Refresh patches

  [ Iain Lane ]
  * Fix debian/patches/startup-database-vacuum.patch
- The vacuum mode is now included upstream
- Move the wrapper script to a file in debian/ and install that
- Call the wrapper and allow it to fail so that zeitgeist starts for new
  users (LP: #1666495)
  * debian/patches/0001-Fix-placeholder-in-systemd-service-template.patch:
Cherry-pick. Fix substitution in systemd unit file.

 -- Iain Lane   Wed, 01 Mar 2017 14:09:01
+

** Changed in: zeitgeist (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Update zeitgeist to 1.0

Status in zeitgeist package in Ubuntu:
  Fix Released

Bug description:
  Zeitgeist 1.0 has been released!

  https://launchpad.net/zeitgeist/1.0/1.0

   - Drop dependency on gnome-common and intltool
   - Use GNU gettext only
   - Fix some valac warnings
   - Use $PYTHON to check for rdflib
   - Install zeitgeist-fts to pkglibexecdir rather than
 libexecdir
   - Use correct names for D-Bus service files
   - Add systemd user service for each D-Bus session service
   - Fix bash auto-completions script
   - Add --vacuum option to Daemon to perform VACUUM SQLite
 database

  Libzeitgeist:
   - Ensure the log mainloop uses the current thread's context
 when waiting

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

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

[Touch-packages] [Bug 1627750] Re: gnome-terminal displays input in wrong window

2017-03-01 Thread Alan Griffiths

** Changed in: miral
   Status: Triaged => Incomplete

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

Title:
  gnome-terminal displays input in wrong window

Status in MirAL:
  Incomplete
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  $ miral-server --startup gnome-terminal

  Go "File=>Open Terminal" to create a second window

  Type in the new window.

  Expect: typing to appear in the new window
  Actual: typing appears in the original window

  Focus *is* on the new window as can be verified by Alt-F4, which
  correctly closes the new window.

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

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

[Touch-packages] [Bug 1625397] Re: [gtk] Focus is stuck on the save as window vs the main window

2017-03-01 Thread Alan Griffiths

** Changed in: miral
   Status: Triaged => Incomplete

** Changed in: miral
   Importance: Medium => Undecided

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

Title:
  [gtk] Focus is stuck on the save as window vs the main window

Status in GTK+:
  Fix Committed
Status in MirAL:
  Incomplete
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  To reproduce:
  Open gedit in miral
  click save (the window should pop up)
  click back on the main window leaving the save window open
  type

  Expected:
  Text to appear in the main top most window

  Result:
  Text appears on the save as window behind the main window.

  I checked with mir_demo_server and same issue so this could be a gtk
  bug it self.

  Added by alan_g:

  As described in comment #5 this seems to be mostly a gtk-mir problem.
  (Where are they filed?) But there is a MirAL component (because even
  if gtk-mir was right, this problem would sill be seen).

  Added later by alan_g:
  The problem mentioned in lp:1626659 has been committed, everything left is a 
gtk-mir issue.

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

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

[Touch-packages] [Bug 1661287] Re: Canon printer failed to connect with CUPS

2017-03-01 Thread SunBear

After switching the connection of the printer in the printer properties,
from USB type to using the printer DNNS, my Canon printer is able to
print again.  In the make and mode, it shows Canon MG5300 series -
CUPS+Gutenprint v5.2.11. It is puzzling how cups is not able to detect
my printer.

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

Title:
  Canon printer failed to connect with CUPS

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  My canon printer has been working with Ubuntu 16.04 for quite
  sometime. Presently, for no reason, it now cannot be recognised. I
  have checked that the USB connections are working fine. When I unplug
  and replug the printer usb connection to my computer the syslog
  reflects it's present. However, it shows that it failed to connect
  with CUPS. udev-configure-printer[5761]: failed to connect to CUPS
  server; giving up I have provide the results to my printer checks
  below.

  Appreciate help to reestablish the proper connection of my printer and
  get it working with  Ubuntu 16.04.

  
  tail -f /var/log/syslog
  Feb  2 22:36:38 Eliot kernel: [95807.581378] usb 1-14: New USB device found, 
idVendor=04a9, idProduct=1754
  Feb  2 22:36:38 Eliot kernel: [95807.581387] usb 1-14: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Feb  2 22:36:38 Eliot kernel: [95807.581391] usb 1-14: Product: MG5300 series
  Feb  2 22:36:38 Eliot kernel: [95807.581395] usb 1-14: Manufacturer: Canon
  Feb  2 22:36:38 Eliot kernel: [95807.581399] usb 1-14: SerialNumber: 20EE62
  Feb  2 22:36:38 Eliot kernel: [95807.591385] usblp 1-14:1.1: usblp0: USB 
Bidirectional printer dev 42 if 1 alt 0 proto 2 vid 0x04A9 pid 0x1754
  Feb  2 22:36:38 Eliot kernel: [95807.591527] usb-storage 1-14:1.2: USB Mass 
Storage device detected
  Feb  2 22:36:38 Eliot kernel: [95807.593328] scsi host13: usb-storage 1-14:1.2
  Feb  2 22:36:38 Eliot systemd[1]: Starting Automatic USB/Bluetooth printer 
setup (-devices-pci:00-:00:14.0-usb1-1\x2d14)...
  Feb  2 22:36:38 Eliot udev-configure-printer[5761]: add 
/devices/pci:00/:00:14.0/usb1/1-14
  Feb  2 22:36:38 Eliot udev-configure-printer[5761]: device devpath is 
/devices/pci:00/:00:14.0/usb1/1-14
  Feb  2 22:36:38 Eliot udev-configure-printer[5761]: MFG:Canon MDL:MG5300 
series SERN:- serial:20EE62
  Feb  2 22:36:39 Eliot kernel: [95808.591918] scsi 13:0:0:0: Direct-Access 
CanonMG5300 series0103 PQ: 0 ANSI: 2
  Feb  2 22:36:39 Eliot kernel: [95808.592839] sd 13:0:0:0: Attached scsi 
generic sg6 type 0
  Feb  2 22:36:39 Eliot kernel: [95808.597229] sd 13:0:0:0: [sdf] Attached SCSI 
removable disk
  Feb  2 22:36:43 Eliot udev-configure-printer[5761]: failed to connect to CUPS 
server; giving up
  Feb  2 22:36:43 Eliot systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:14.0-usb1-1\x2d14.service: 
Control process exited, code=exited status=1
  Feb  2 22:36:43 Eliot systemd[1]: Failed to start Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:14.0-usb1-1\x2d14).
  Feb  2 22:36:43 Eliot systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:14.0-usb1-1\x2d14.service: 
Unit entered failed state.
  Feb  2 22:36:43 Eliot systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:14.0-usb1-1\x2d14.service: 
Failed with result 'exit-code'.

  @Eliot:~$ lsusb
  Bus 001 Device 043: ID 04a9:1754 Canon, Inc. 

  @Eliot:~$ ls -l /dev/usb/lp* /dev/bus/usb/*/*
  crw-rw-r--+ 1 root lp   189,  42 Feb  2 22:40 /dev/bus/usb/001/043
  crw-rw  1 root lp   180,   0 Feb  2 22:39 /dev/usb/lp0

  @Eliot:~$ sudo usb_printerid /dev/usb/lp0 
  GET_DEVICE_ID string:
  
MFG:Canon;CMD:BJL,BJRaster3,BSCCe,NCCe,IVEC,IVECPLI;SOJ:BJNP2,BJNPe;MDL:MG5300 
series;CLS:PRINTER;DES:Canon MG5300 
series;VER:1.030;STA:10;FSI:03;HRI:7;MSI:B030,DAT,E3,HFSF,JON,K21000700;PDR:6;PSE:ACFJ03117;

  @Eliot:~$ sudo usb_printerid /dev/bus/usb/001/043
  Error: Inappropriate ioctl for device: GET_DEVICE_ID on '/dev/bus/usb/001/043'

  @Eliot:~$ lpinfo -v
  lpinfo: Bad file descriptor

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb  2 23:17:01 2017
  InstallationDate: Installed on 2016-05-01 (277 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2017-03-01 Thread Jeremy LaCroix

Network Manager is the culprit, not anyone's routers. This is evident by
the fact that earlier versions of Ubuntu didn't experience this issue,
this issue happens regardless of which router we're connecting to, it
happens regardless of which location we are at, and the underlying issue
is that Network Manager cannot see ANY access points, not just the one
we normally connect to. There is literally no scenario in which it is
someone's router that is causing this.

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

Title:
  cannot view wifi networks after re-enabling wifi

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

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

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

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

[Touch-packages] [Bug 1661287] Re: Canon printer failed to connect with CUPS

2017-03-01 Thread SunBear

I found the answer. I checked "apt" history log in /var/log/apt and
discovered that when I executed the "apt-get install ubuntu-desktop",
the "ubuntu-desktop" package installed many cups packages (see below).
These installations fixed whatever problems cups had previously. Wish
someone could have just told me about this simple solution to fixing
cups.

Start-Date: 2017-02-25  19:10:43
Commandline: apt-get install ubuntu-desktop
Requested-By: sunbear (1000)
Install: python3-pexpect:amd64 (4.0.1-1, automatic), hplip-data:amd64 
(3.16.3+repack0-1, automatic), libqpdf17:amd64 (6.0.0-2, automatic), 
liblouisutdml-data:amd64 (2.5.0-3, automatic), printer-driver-splix:amd64 
(2.0.0+svn315-4fakesync1, automatic), bluez-cups:amd64 (5.37-0ubuntu5, 
automatic), printer-driver-hpcups:amd64 (3.16.3+repack0-1, automatic), 
printer-driver-postscript-hp:amd64 (3.16.3+repack0-1, automatic), 
libsnmp-base:amd64 (5.7.3+dfsg-1ubuntu4, automatic), 
python3-reportlab-accel:amd64 (3.3.0-1, automatic), ubuntu-desktop:amd64 
(1.361), printer-driver-pxljr:amd64 (1.4+repack0-4, automatic), 
cups-server-common:amd64 (2.1.3-4, automatic), ssl-cert:amd64 (1.0.37, 
automatic), python3-renderpm:amd64 (3.3.0-1, automatic), cups-filters:amd64 
(1.8.3-2ubuntu3.1, automatic), libsnmp30:amd64 (5.7.3+dfsg-1ubuntu4, 
automatic), libcupsmime1:amd64 (2.1.3-4, automatic), hplip:amd64 
(3.16.3+repack0-1, automatic), liblouisutdml6:amd64 (2.5.0-3, automatic), 
libhpmud0:amd64 (3.16.3+repack0-
 1, automatic), printer-driver-gutenprint:amd64 (5.2.11-1, automatic), 
libfontembed1:amd64 (1.8.3-2ubuntu3.1, automatic), libgutenprint2:amd64 
(5.2.11-1, automatic), liblouisutdml-bin:amd64 (2.5.0-3, automatic), 
libsane-hpaio:amd64 (3.16.3+repack0-1, automatic), qpdf:amd64 (6.0.0-2, 
automatic), cups-filters-core-drivers:amd64 (1.8.3-2ubuntu3.1, automatic), 
python3-ptyprocess:amd64 (0.5-1, automatic), cups-core-drivers:amd64 (2.1.3-4, 
automatic), cups-daemon:amd64 (2.1.3-4, automatic), python3-reportlab:amd64 
(3.3.0-1, automatic), cups:amd64 (2.1.3-4, automatic), libcupscgi1:amd64 
(2.1.3-4, automatic), cups-browsed:amd64 (1.8.3-2ubuntu3.1, automatic)
Remove: foomatic-filters:amd64 (4.0.17-8)
End-Date: 2017-02-25  19:11:16

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

Title:
  Canon printer failed to connect with CUPS

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  My canon printer has been working with Ubuntu 16.04 for quite
  sometime. Presently, for no reason, it now cannot be recognised. I
  have checked that the USB connections are working fine. When I unplug
  and replug the printer usb connection to my computer the syslog
  reflects it's present. However, it shows that it failed to connect
  with CUPS. udev-configure-printer[5761]: failed to connect to CUPS
  server; giving up I have provide the results to my printer checks
  below.

  Appreciate help to reestablish the proper connection of my printer and
  get it working with  Ubuntu 16.04.

  
  tail -f /var/log/syslog
  Feb  2 22:36:38 Eliot kernel: [95807.581378] usb 1-14: New USB device found, 
idVendor=04a9, idProduct=1754
  Feb  2 22:36:38 Eliot kernel: [95807.581387] usb 1-14: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Feb  2 22:36:38 Eliot kernel: [95807.581391] usb 1-14: Product: MG5300 series
  Feb  2 22:36:38 Eliot kernel: [95807.581395] usb 1-14: Manufacturer: Canon
  Feb  2 22:36:38 Eliot kernel: [95807.581399] usb 1-14: SerialNumber: 20EE62
  Feb  2 22:36:38 Eliot kernel: [95807.591385] usblp 1-14:1.1: usblp0: USB 
Bidirectional printer dev 42 if 1 alt 0 proto 2 vid 0x04A9 pid 0x1754
  Feb  2 22:36:38 Eliot kernel: [95807.591527] usb-storage 1-14:1.2: USB Mass 
Storage device detected
  Feb  2 22:36:38 Eliot kernel: [95807.593328] scsi host13: usb-storage 1-14:1.2
  Feb  2 22:36:38 Eliot systemd[1]: Starting Automatic USB/Bluetooth printer 
setup (-devices-pci:00-:00:14.0-usb1-1\x2d14)...
  Feb  2 22:36:38 Eliot udev-configure-printer[5761]: add 
/devices/pci:00/:00:14.0/usb1/1-14
  Feb  2 22:36:38 Eliot udev-configure-printer[5761]: device devpath is 
/devices/pci:00/:00:14.0/usb1/1-14
  Feb  2 22:36:38 Eliot udev-configure-printer[5761]: MFG:Canon MDL:MG5300 
series SERN:- serial:20EE62
  Feb  2 22:36:39 Eliot kernel: [95808.591918] scsi 13:0:0:0: Direct-Access 
CanonMG5300 series0103 PQ: 0 ANSI: 2
  Feb  2 22:36:39 Eliot kernel: [95808.592839] sd 13:0:0:0: Attached scsi 
generic sg6 type 0
  Feb  2 22:36:39 Eliot kernel: [95808.597229] sd 13:0:0:0: [sdf] Attached SCSI 
removable disk
  Feb  2 22:36:43 Eliot udev-configure-printer[5761]: failed to connect to CUPS 
server; giving up
  Feb  2 22:36:43 Eliot systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:14.0-usb1-1\x2d14.service: 
Control process exited, code=exited status=1
  Feb  2 22:36:43 Eliot systemd[1]: Faile

[Touch-packages] [Bug 1048430] Re: "dnsmasq not available on the bus"

2017-03-01 Thread Laurent Bonnaud

This bug no longer exists in yakkety:

# journalctl -b |grep dnsmasq
Feb 26 20:12:47 xeelee audit[1052]: AVC apparmor="STATUS" 
operation="profile_load" name="/usr/sbin/dnsmasq" pid=1052 
comm="apparmor_parser"
Feb 26 20:12:47 xeelee audit[1052]: AVC apparmor="STATUS" 
operation="profile_load" name="/usr/sbin/dnsmasq//libvirt_leaseshelper" 
pid=1052 comm="apparmor_parser"
Feb 26 20:12:47 xeelee NetworkManager[1088]:   [1488136367.5567] 
dns-mgr[0x55d53a357a80]: init: dns=dnsmasq, rc-manager=resolvconf, 
plugin=dnsmasq
Feb 26 20:12:50 xeelee NetworkManager[1088]:   [1488136370.2108] 
dns-plugin[0x55d53a37b500]: starting dnsmasq...
Feb 26 20:12:50 xeelee dnsmasq[1397]: started, version 2.76 cachesize 1000
Feb 26 20:12:50 xeelee dnsmasq[1397]: compile time options: IPv6 GNU-getopt 
DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect 
inotify
Feb 26 20:12:50 xeelee dnsmasq[1397]: DBus support enabled: connected to system 
bus
Feb 26 20:12:50 xeelee dnsmasq[1397]: using nameserver 8.8.4.4#53
Feb 26 20:12:50 xeelee dnsmasq[1397]: using nameserver 8.8.8.8#53
Feb 26 20:12:50 xeelee dnsmasq[1397]: cleared cache
Feb 26 20:12:50 xeelee NetworkManager[1088]:   [1488136370.2832] 
dnsmasq[0x55d53a37b500]: dnsmasq appeared as :1.13
Feb 26 20:12:50 xeelee dnsmasq[1397]: setting upstream servers from DBus
[...]

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

Title:
  "dnsmasq not available on the bus"

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Dnsmasq seems to be having some issues. This occurs whenever I try to
  connect to my wireless network; sometimes it only happens once, but
  sometimes the error loops for a while.

  Sep  9 17:43:51 bkerensa NetworkManager[935]:  DNS: starting dnsmasq...
  Sep  9 17:43:51 bkerensa NetworkManager[935]:  [1347237831.899067] 
[nm-dns-dnsmasq.c:390] update(): dnsmasq not available on the bus, can't update 
servers.
  Sep  9 17:43:51 bkerensa NetworkManager[935]:  [1347237831.899142] 
[nm-dns-dnsmasq.c:392] update(): dnsmasq owner not found on bus: Could not get 
owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
  Sep  9 17:43:51 bkerensa NetworkManager[935]:  DNS: plugin dnsmasq 
update failed
  Sep  9 17:43:51 bkerensa NetworkManager[935]:  ((null)): writing 
resolv.conf to /sbin/resolvconf

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: dnsmasq (not installed)
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  Date: Sun Sep  9 17:47:22 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to quantal on 2012-08-08 (32 days ago)

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

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

[Touch-packages] [Bug 1661611] Re: apt/unattended-upgrades stalls shutdown

2017-03-01 Thread kay

It doesn't relate to "/usr/share/unattended-upgrades/unattended-upgrade-
shutdown" file at all. When you "fix" it - it just fails because of the
invalid python syntax. And shutdown just works.

The real problem is systemd dependencies. Here is the log of the shutdown 
process:
Unattended upgrades should be started before filesystem unmount, but it starts 
after unmount:

[  OK  ] Unmounted /home.
[  OK  ] Stopped File System Check on /dev/mapper/VG-home.
[  OK  ] Unmounted /var.
[  OK  ] Stopped File System Check on /dev/mapper/VG-var.
[  OK  ] Unmounted /boot.
[  OK  ] Stopped File System Check on /dev/mapper/VG-boot.
[  OK  ] Removed slice system-systemd\x2dfsck.slice.
[  OK  ] Stopped Login to default iSCSI targets.
 Stopping iSCSI initiator daemon (iscsid)...
[  OK  ] Stopped iSCSI initiator daemon (iscsid).
[  OK  ] Stopped target Network is Online.
[  OK  ] Stopped target Network.
[  OK  ] Stopped Initial cloud-init job (metadata service crawler).
 Stopping Raise network interfaces...
[  OK  ] Stopped Raise network interfaces.
[  OK  ] Stopped target Local File Systems.
 Unmounting /run/user/1000...
 Starting Unattended Upgrades Shutdown...
[  OK  ] Stopped Apply Kernel Variables.
[  OK  ] Stopped target Network (Pre).
[  OK  ] Stopped Initial cloud-init job (pre-networking).
[  OK  ] Stopped Load Kernel Modules.
[  OK  ] Unmounted /run/user/1000.
[  OK  ] Reached target Unmount All Filesystems.
[  OK  ] Stopped target Local File Systems (Pre).
[  OK  ] Stopped Create Static Device Nodes in /dev.
 Stopping Monitoring of LVM2 mirrors... dmeventd or progress polling...
[  OK  ] Stopped Remount Root and Kernel File Systems.
[  OK  ] Stopped Monitoring of LVM2 mirrors,...ng dmeventd or progress polling.
 Stopping LVM2 metadata daemon...
[  OK  ] Stopped LVM2 metadata daemon.


And it is reproducible with LVM only. Have to spend some time on investigation.

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

Title:
  apt/unattended-upgrades stalls shutdown

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  When unattended-upgrades is installed, 9 out of 10 shutdowns/reboots
  hang while "starting unattended upgrades shutdown". This hang stalls
  the shutdown process for 5-10 mins.

  If I disable unnattended-upgrades via the /etc/apt/apt.conf.d/20auto-
  upgrades and/or 50unattended-upgrades, the problems occurs.

  If I terminate the service before shutdown/reboot (sudo service
  unattended-upgrades stop) the problem still occurs.

  If I remove the package (sudo apt remove unattended-upgrades) the
  problem no longer occurs.

  This occurs on a freshly installed version of Ubuntu Server 16.04.1
  (both unattended-upgrades installed via install GUI or manual install
  of unattended-upgrades)

  Both Kern.log & syslog do not show the shutdown process (I believe
  because the filesystems have already unmounted)

  Original report: http://askubuntu.com/questions/878630/apt-unattended-
  upgrades-stalls-shutdown

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

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

[Touch-packages] [Bug 1048430] Re: "dnsmasq not available on the bus"

2017-03-01 Thread dino99

** Tags removed: quantal wily

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

Title:
  "dnsmasq not available on the bus"

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Dnsmasq seems to be having some issues. This occurs whenever I try to
  connect to my wireless network; sometimes it only happens once, but
  sometimes the error loops for a while.

  Sep  9 17:43:51 bkerensa NetworkManager[935]:  DNS: starting dnsmasq...
  Sep  9 17:43:51 bkerensa NetworkManager[935]:  [1347237831.899067] 
[nm-dns-dnsmasq.c:390] update(): dnsmasq not available on the bus, can't update 
servers.
  Sep  9 17:43:51 bkerensa NetworkManager[935]:  [1347237831.899142] 
[nm-dns-dnsmasq.c:392] update(): dnsmasq owner not found on bus: Could not get 
owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
  Sep  9 17:43:51 bkerensa NetworkManager[935]:  DNS: plugin dnsmasq 
update failed
  Sep  9 17:43:51 bkerensa NetworkManager[935]:  ((null)): writing 
resolv.conf to /sbin/resolvconf

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: dnsmasq (not installed)
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  Date: Sun Sep  9 17:47:22 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to quantal on 2012-08-08 (32 days ago)

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

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

[Touch-packages] [Bug 1669047] [NEW] [Unity8] the launcher is couning the context menus as windows

Public bug reported:

ubuntu 17.04 unity8

the launcher is showing some white dots for every opened window/instance
of the same app (from what i understand, like unity7), but if you open
Kate and then right click on document and then open then open a submenu
now the launcher shows 3 white dots (left side of Kate's icon)

see attached screenshot

i am not super sure but i think that the launcher is counting menus as
instances or something

also not specific to kate, happens with lot of apps (can't tell if bug
or feature)

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

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

** Attachment added: "screenshot20170301_183424921.png"
   
https://bugs.launchpad.net/bugs/1669047/+attachment/4829091/+files/screenshot20170301_183424921.png

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

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

Title:
  [Unity8] the launcher is couning the context menus as windows

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

Bug description:
  ubuntu 17.04 unity8

  the launcher is showing some white dots for every opened
  window/instance of the same app (from what i understand, like unity7),
  but if you open Kate and then right click on document and then open
  then open a submenu now the launcher shows 3 white dots (left side of
  Kate's icon)

  see attached screenshot

  i am not super sure but i think that the launcher is counting menus as
  instances or something

  also not specific to kate, happens with lot of apps (can't tell if bug
  or feature)

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

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

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

2017-03-01 Thread James Bowery

After I gave up and shifted to a wired connection, I noticed that I'd get
disconnected periodically but then it would reconnect successfully.  It
seems some drivers manage to reconnect and other drivers don't.

So there may be _two_ bugs:

1) A bug that results in occasional loss of connection.
2) A bug in one or more drivers that disables automatic reconnection.


On Wed, Mar 1, 2017 at 9:42 AM, Jeremy LaCroix <1589...@bugs.launchpad.net>
wrote:

> Network Manager is the culprit, not anyone's routers. This is evident by
> the fact that earlier versions of Ubuntu didn't experience this issue,
> this issue happens regardless of which router we're connecting to, it
> happens regardless of which location we are at, and the underlying issue
> is that Network Manager cannot see ANY access points, not just the one
> we normally connect to. There is literally no scenario in which it is
> someone's router that is causing this.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1589401
>
> Title:
>   cannot view wifi networks after re-enabling wifi
>
> Status in NetworkManager:
>   Unknown
> Status in network-manager package in Ubuntu:
>   Incomplete
>
> Bug description:
>   after re enabling wifi, up-down arrows just like wired network. cannot
>   see any wifi ssid.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions
>

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

Title:
  cannot view wifi networks after re-enabling wifi

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

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

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

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

[Touch-packages] [Bug 1669047] Re: [Unity8] the launcher is couning the context menus as windows

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

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

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

Title:
  [Unity8] the launcher is couning the context menus as windows

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

Bug description:
  ubuntu 17.04 unity8

  the launcher is showing some white dots for every opened
  window/instance of the same app (from what i understand, like unity7),
  but if you open Kate and then right click on document and then open
  then open a submenu now the launcher shows 3 white dots (left side of
  Kate's icon)

  see attached screenshot

  i am not super sure but i think that the launcher is counting menus as
  instances or something

  also not specific to kate, happens with lot of apps (can't tell if bug
  or feature)

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

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

[Touch-packages] [Bug 1669052] [NEW] [unity8] launcher shows the tooltip at the wrong position if you play with the launcher's size for a while

Public bug reported:

ubuntu 17.04 unity8
[unity8] launcher shows the tooltip at the wrong position if you play with the 
launcher's size for a while

see attached screenshot, the mouse is hovering the calculator app and
the tooltip is Gallery, also if i right click on the calculator it opens
the calculator menu (calculator/unpin calculator) beside the gallery
app.

how to reproduce: have a lot of apps pinned to the launcher, open system
settings and play with the launcher size

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

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

** Attachment added: "screenshot20170301_184427781.png"
   
https://bugs.launchpad.net/bugs/1669052/+attachment/4829094/+files/screenshot20170301_184427781.png

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

Title:
  [unity8] launcher shows the tooltip at the wrong position if you play
  with the launcher's size for a while

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

Bug description:
  ubuntu 17.04 unity8
  [unity8] launcher shows the tooltip at the wrong position if you play with 
the launcher's size for a while

  see attached screenshot, the mouse is hovering the calculator app and
  the tooltip is Gallery, also if i right click on the calculator it
  opens the calculator menu (calculator/unpin calculator) beside the
  gallery app.

  how to reproduce: have a lot of apps pinned to the launcher, open
  system settings and play with the launcher size

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

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

[Touch-packages] [Bug 1669055] [NEW] TZ is not set by default

2017-03-01 Thread Matteo Croce

Public bug reported:

It seems that unsetting the environment variable TZ there is a huge
performance penalty calling some glibc functions, eg. time()

this has been documented here:

https://blog.packagecloud.io/eng/2017/02/21/set-environment-variable-
save-thousands-of-system-calls/

and I can confirm it on an amd64 system running Yakkety:

$ cat time.c
#include 

int main(int argc, char *argv[])
{
int i = 0;
time_t timep;

for (i = 0; i < 1000; i++) {
time(&timep);
localtime(&timep);
}

return 0;
}
$ gcc -Wall -O3 time.c -o time
$ time ./time

real0m7.102s
user0m2.060s
sys 0m5.040s
$ time TZ=:/etc/localtime ./time

real0m0.952s
user0m0.948s
sys 0m0.000s
$

I've set TZ in /etc/environment to have it globally defined.

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

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

Title:
  TZ is not set by default

Status in shadow package in Ubuntu:
  New

Bug description:
  It seems that unsetting the environment variable TZ there is a huge
  performance penalty calling some glibc functions, eg. time()

  this has been documented here:

  https://blog.packagecloud.io/eng/2017/02/21/set-environment-variable-
  save-thousands-of-system-calls/

  and I can confirm it on an amd64 system running Yakkety:

  $ cat time.c
  #include 

  int main(int argc, char *argv[])
  {
  int i = 0;
  time_t timep;

  for (i = 0; i < 1000; i++) {
  time(&timep);
  localtime(&timep);
  }

  return 0;
  }
  $ gcc -Wall -O3 time.c -o time
  $ time ./time

  real0m7.102s
  user0m2.060s
  sys 0m5.040s
  $ time TZ=:/etc/localtime ./time

  real0m0.952s
  user0m0.948s
  sys 0m0.000s
  $

  I've set TZ in /etc/environment to have it globally defined.

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

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

[Touch-packages] [Bug 1661287] Re: Canon printer failed to connect with CUPS

2017-03-01 Thread Till Kamppeter

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

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

Title:
  Canon printer failed to connect with CUPS

Status in cups package in Ubuntu:
  Invalid

Bug description:
  My canon printer has been working with Ubuntu 16.04 for quite
  sometime. Presently, for no reason, it now cannot be recognised. I
  have checked that the USB connections are working fine. When I unplug
  and replug the printer usb connection to my computer the syslog
  reflects it's present. However, it shows that it failed to connect
  with CUPS. udev-configure-printer[5761]: failed to connect to CUPS
  server; giving up I have provide the results to my printer checks
  below.

  Appreciate help to reestablish the proper connection of my printer and
  get it working with  Ubuntu 16.04.

  
  tail -f /var/log/syslog
  Feb  2 22:36:38 Eliot kernel: [95807.581378] usb 1-14: New USB device found, 
idVendor=04a9, idProduct=1754
  Feb  2 22:36:38 Eliot kernel: [95807.581387] usb 1-14: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Feb  2 22:36:38 Eliot kernel: [95807.581391] usb 1-14: Product: MG5300 series
  Feb  2 22:36:38 Eliot kernel: [95807.581395] usb 1-14: Manufacturer: Canon
  Feb  2 22:36:38 Eliot kernel: [95807.581399] usb 1-14: SerialNumber: 20EE62
  Feb  2 22:36:38 Eliot kernel: [95807.591385] usblp 1-14:1.1: usblp0: USB 
Bidirectional printer dev 42 if 1 alt 0 proto 2 vid 0x04A9 pid 0x1754
  Feb  2 22:36:38 Eliot kernel: [95807.591527] usb-storage 1-14:1.2: USB Mass 
Storage device detected
  Feb  2 22:36:38 Eliot kernel: [95807.593328] scsi host13: usb-storage 1-14:1.2
  Feb  2 22:36:38 Eliot systemd[1]: Starting Automatic USB/Bluetooth printer 
setup (-devices-pci:00-:00:14.0-usb1-1\x2d14)...
  Feb  2 22:36:38 Eliot udev-configure-printer[5761]: add 
/devices/pci:00/:00:14.0/usb1/1-14
  Feb  2 22:36:38 Eliot udev-configure-printer[5761]: device devpath is 
/devices/pci:00/:00:14.0/usb1/1-14
  Feb  2 22:36:38 Eliot udev-configure-printer[5761]: MFG:Canon MDL:MG5300 
series SERN:- serial:20EE62
  Feb  2 22:36:39 Eliot kernel: [95808.591918] scsi 13:0:0:0: Direct-Access 
CanonMG5300 series0103 PQ: 0 ANSI: 2
  Feb  2 22:36:39 Eliot kernel: [95808.592839] sd 13:0:0:0: Attached scsi 
generic sg6 type 0
  Feb  2 22:36:39 Eliot kernel: [95808.597229] sd 13:0:0:0: [sdf] Attached SCSI 
removable disk
  Feb  2 22:36:43 Eliot udev-configure-printer[5761]: failed to connect to CUPS 
server; giving up
  Feb  2 22:36:43 Eliot systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:14.0-usb1-1\x2d14.service: 
Control process exited, code=exited status=1
  Feb  2 22:36:43 Eliot systemd[1]: Failed to start Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:14.0-usb1-1\x2d14).
  Feb  2 22:36:43 Eliot systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:14.0-usb1-1\x2d14.service: 
Unit entered failed state.
  Feb  2 22:36:43 Eliot systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:14.0-usb1-1\x2d14.service: 
Failed with result 'exit-code'.

  @Eliot:~$ lsusb
  Bus 001 Device 043: ID 04a9:1754 Canon, Inc. 

  @Eliot:~$ ls -l /dev/usb/lp* /dev/bus/usb/*/*
  crw-rw-r--+ 1 root lp   189,  42 Feb  2 22:40 /dev/bus/usb/001/043
  crw-rw  1 root lp   180,   0 Feb  2 22:39 /dev/usb/lp0

  @Eliot:~$ sudo usb_printerid /dev/usb/lp0 
  GET_DEVICE_ID string:
  
MFG:Canon;CMD:BJL,BJRaster3,BSCCe,NCCe,IVEC,IVECPLI;SOJ:BJNP2,BJNPe;MDL:MG5300 
series;CLS:PRINTER;DES:Canon MG5300 
series;VER:1.030;STA:10;FSI:03;HRI:7;MSI:B030,DAT,E3,HFSF,JON,K21000700;PDR:6;PSE:ACFJ03117;

  @Eliot:~$ sudo usb_printerid /dev/bus/usb/001/043
  Error: Inappropriate ioctl for device: GET_DEVICE_ID on '/dev/bus/usb/001/043'

  @Eliot:~$ lpinfo -v
  lpinfo: Bad file descriptor

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb  2 23:17:01 2017
  InstallationDate: Installed on 2016-05-01 (277 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1669052] Re: [unity8] launcher shows the tooltip at the wrong position if you play with the launcher's size for a while

2017-03-01 Thread Michał Sawicz

** Changed in: canonical-devices-system-image
   Status: New => Triaged

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

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

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

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

Title:
  [unity8] launcher shows the tooltip at the wrong position if you play
  with the launcher's size for a while

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  ubuntu 17.04 unity8
  [unity8] launcher shows the tooltip at the wrong position if you play with 
the launcher's size for a while

  see attached screenshot, the mouse is hovering the calculator app and
  the tooltip is Gallery, also if i right click on the calculator it
  opens the calculator menu (calculator/unpin calculator) beside the
  gallery app.

  how to reproduce: have a lot of apps pinned to the launcher, open
  system settings and play with the launcher size

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

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

[Touch-packages] [Bug 1669047] Re: [Unity8] launcher pips include child windows

2017-03-01 Thread Michał Sawicz

** Summary changed:

- [Unity8] the launcher is couning the context menus as windows
+ [Unity8] launcher pips include child windows

** Changed in: unity8 (Ubuntu)
   Status: Confirmed => Triaged

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

** Changed in: canonical-devices-system-image
   Status: New => Triaged

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

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

Title:
  [Unity8] launcher pips include child windows

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  ubuntu 17.04 unity8

  the launcher is showing some white dots for every opened
  window/instance of the same app (from what i understand, like unity7),
  but if you open Kate and then right click on document and then open
  then open a submenu now the launcher shows 3 white dots (left side of
  Kate's icon)

  see attached screenshot

  i am not super sure but i think that the launcher is counting menus as
  instances or something

  also not specific to kate, happens with lot of apps (can't tell if bug
  or feature)

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

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

[Touch-packages] [Bug 1532855] Re: add-apt-repository exits with 0 even when adding key failed

** Branch linked: lp:software-properties

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

Title:
  add-apt-repository exits with 0 even when adding key failed

Status in software-properties package in Ubuntu:
  Fix Committed
Status in software-properties source package in Xenial:
  Confirmed
Status in software-properties source package in Yakkety:
  Confirmed

Bug description:
  add-apt-repository exits happily even if it failed adding the key:

  $ sudo env LANGUAGE=en add-apt-repository ppa:launchpad/buildd-staging -k 
hkp://bad-server/
   Buildd staging packages for Launchpad. New packages are staged here for 
testing on the staging PPA buildds.
   More info: https://launchpad.net/~launchpad/+archive/ubuntu/buildd-staging
  Press [ENTER] to continue or ctrl-c to cancel adding it

  gpg: keyring `/tmp/tmp3246v7n8/secring.gpg' created
  gpg: keyring `/tmp/tmp3246v7n8/pubring.gpg' created
  gpg: requesting key 0A5174AF from hkp server bad-server
  ?: bad-server: Host not found
  gpgkeys: HTTP fetch error 7: couldn't connect: Success
  gpg: no valid OpenPGP data found.
  gpg: Total number processed: 0
  gpg: keyserver communications error: keyserver unreachable
  gpg: keyserver communications error: public key not found
  gpg: keyserver receive failed: public key not found

  $ echo $?
  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-properties-common 0.96.17
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 11 17:17:56 2016
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (74 days ago)

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

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

[Touch-packages] [Bug 1532855] Re: add-apt-repository exits with 0 even when adding key failed

2017-03-01 Thread Dimitri John Ledkov

** Changed in: software-properties (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  add-apt-repository exits with 0 even when adding key failed

Status in software-properties package in Ubuntu:
  Fix Committed
Status in software-properties source package in Xenial:
  Confirmed
Status in software-properties source package in Yakkety:
  Confirmed

Bug description:
  add-apt-repository exits happily even if it failed adding the key:

  $ sudo env LANGUAGE=en add-apt-repository ppa:launchpad/buildd-staging -k 
hkp://bad-server/
   Buildd staging packages for Launchpad. New packages are staged here for 
testing on the staging PPA buildds.
   More info: https://launchpad.net/~launchpad/+archive/ubuntu/buildd-staging
  Press [ENTER] to continue or ctrl-c to cancel adding it

  gpg: keyring `/tmp/tmp3246v7n8/secring.gpg' created
  gpg: keyring `/tmp/tmp3246v7n8/pubring.gpg' created
  gpg: requesting key 0A5174AF from hkp server bad-server
  ?: bad-server: Host not found
  gpgkeys: HTTP fetch error 7: couldn't connect: Success
  gpg: no valid OpenPGP data found.
  gpg: Total number processed: 0
  gpg: keyserver communications error: keyserver unreachable
  gpg: keyserver communications error: public key not found
  gpg: keyserver receive failed: public key not found

  $ echo $?
  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-properties-common 0.96.17
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 11 17:17:56 2016
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (74 days ago)

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

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

[Touch-packages] [Bug 1667898] Re: Failed to start Zeitgeist activity log service on Ubuntu 17.04

2017-03-01 Thread Mateusz Stachowski

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

** This bug has been marked a duplicate of bug 1666495
   [Zesty] No default apps shown on first start in kvm oem end user

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

Title:
  Failed to start Zeitgeist activity log service on Ubuntu 17.04

Status in zeitgeist package in Ubuntu:
  Confirmed

Bug description:
  I just installed Ubuntu 17.04 from last daily Ubuntu 17.04 "Zesty Zapus" - 
Alpha amd64 (20170222) 
  corrado@corrado-z4:~$ uname -a
  Linux corrado-z4 4.10.0-9-generic #11-Ubuntu SMP Mon Feb 20 13:47:35 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  corrado@corrado-z4:~$ 
  corrado@corrado-z4:~$ inxi -Fx
  System:Host: corrado-z4 Kernel: 4.10.0-9-generic x86_64 (64 bit gcc: 
6.3.0)
 Desktop: Gnome  (Gtk 3.22.7-1ubuntu4) Distro: Ubuntu Zesty Zapus 
(development branch)
  Machine:   Device: desktop Mobo: Gigabyte model: H87M-D3H v: x.x UEFI: 
American Megatrends v: F3 date: 04/24/2013
  CPU:   Dual core Intel Core i3-4130 (-HT-MCP-) cache: 3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 13567
 clock speeds: max: 3400 MHz 1: 806 MHz 2: 803 MHz 3: 873 MHz 4: 
814 MHz
  Graphics:  Card: Intel 4th Generation Core Processor Family Integrated 
Graphics Controller bus-ID: 00:02.0
 Display Server: X.Org 1.18.4 drivers: modesetting (unloaded: 
fbdev,vesa)
 Resolution: 1680x1050@59.88hz
 GLX Renderer: Mesa DRI Intel Haswell GLX Version: 3.0 Mesa 17.0.0 
Direct Rendering: Yes
  Audio: Card-1 Intel 8 Series/C220 Series High Definition Audio Controller
 driver: snd_hda_intel bus-ID: 00:1b.0
 Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
Controller
 driver: snd_hda_intel bus-ID: 00:03.0
 Sound: Advanced Linux Sound Architecture v: k4.10.0-9-generic
  Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller
 driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 02:00.0
 IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: 
94:de:80:7e:90:a7
  Drives:HDD Total Size: 1000.2GB (1.3% used)
 ID-1: /dev/sda model: ST1000DM003 size: 1000.2GB temp: 33C
  Partition: ID-1: / size: 32G used: 4.9G (17%) fs: ext4 dev: /dev/sda4
 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 212 Uptime: 23 min Memory: 1008.6/7861.2MB Init: 
systemd runlevel: 5 Gcc sys: 6.3.0
 Client: Shell (bash 4.4.51) inxi: 2.3.8 
  corrado@corrado-z4:~$ 

  and zeitgeist does not start:

  Feb 23 10:19:35 corrado-z4 dbus-daemon[2048]: Activating via systemd: service 
name='org.gnome.zeitgeist.Engine' unit='zeitgeist.service'
  Feb 23 10:19:35 corrado-z4 systemd[2015]: Starting Zeitgeist activity log 
service...
  Feb 23 10:19:35 corrado-z4 zeitgeist-vacuu[2842]: zeitgeist-vacuum.vala:38: 
Impossible to open database 
`/home/corrado/.local/share/zeitgeist/activity.sqlite': unable to open database 
file
  Feb 23 10:19:35 corrado-z4 systemd[2015]: zeitgeist.service: Control process 
exited, code=exited status=14
  Feb 23 10:19:35 corrado-z4 systemd[2015]: Failed to start Zeitgeist activity 
log service.
  Feb 23 10:19:35 corrado-z4 systemd[2015]: zeitgeist.service: Unit entered 
failed state.
  Feb 23 10:19:35 corrado-z4 systemd[2015]: zeitgeist.service: Failed with 
result 'exit-code'.
  Feb 23 10:19:43 corrado-z4 gnome-software-service.desktop[2612]: 
09:19:43:0074 Gs  failed to call gs_plugin_add_updates_historical on fwupd: 
Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached
  Feb 23 10:20:00 corrado-z4 zeitgeist-datah[2834]: log.vala:103: Unable to 
connect to Zeitgeist: Error calling StartServiceByName for 
org.gnome.zeitgeist.Engine: Timeout was reached
  Feb 23 10:20:01 corrado-z4 systemd[1]: Starting Stop ureadahead data 
collection...
  Feb 23 10:20:01 corrado-z4 systemd[1]: Started Stop ureadahead data 
collection.
  Feb 23 10:20:25 corrado-z4 zeitgeist-datah[2834]: Unable to connect to 
Zeitgeist's DataSourceRegistry: Error calling StartServiceByName for 
org.gnome.zeitgeist.Engine: Timeout was reached
  Feb 23 10:20:25 corrado-z4 zeitgeist-datah[2834]: zeitgeist-datahub.vala:103: 
Error calling StartServiceByName for org.gnome.zeitgeist.Engine: Timeout was 
reached
  Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: 
g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' 
failed
  Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: 
gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' 
f

[Touch-packages] [Bug 1532855] Re: add-apt-repository exits with 0 even when adding key failed

2017-03-01 Thread Scott Moser

** Also affects: software-properties (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: software-properties (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: software-properties (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: software-properties (Ubuntu Yakkety)
   Status: New => Confirmed

** Changed in: software-properties (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: software-properties (Ubuntu Yakkety)
   Importance: Undecided => Medium

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

Title:
  add-apt-repository exits with 0 even when adding key failed

Status in software-properties package in Ubuntu:
  Fix Committed
Status in software-properties source package in Xenial:
  Confirmed
Status in software-properties source package in Yakkety:
  Confirmed

Bug description:
  add-apt-repository exits happily even if it failed adding the key:

  $ sudo env LANGUAGE=en add-apt-repository ppa:launchpad/buildd-staging -k 
hkp://bad-server/
   Buildd staging packages for Launchpad. New packages are staged here for 
testing on the staging PPA buildds.
   More info: https://launchpad.net/~launchpad/+archive/ubuntu/buildd-staging
  Press [ENTER] to continue or ctrl-c to cancel adding it

  gpg: keyring `/tmp/tmp3246v7n8/secring.gpg' created
  gpg: keyring `/tmp/tmp3246v7n8/pubring.gpg' created
  gpg: requesting key 0A5174AF from hkp server bad-server
  ?: bad-server: Host not found
  gpgkeys: HTTP fetch error 7: couldn't connect: Success
  gpg: no valid OpenPGP data found.
  gpg: Total number processed: 0
  gpg: keyserver communications error: keyserver unreachable
  gpg: keyserver communications error: public key not found
  gpg: keyserver receive failed: public key not found

  $ echo $?
  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-properties-common 0.96.17
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 11 17:17:56 2016
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (74 days ago)

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

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

[Touch-packages] [Bug 1645827] Re: [SRU] Add support for ocata cloud-archive

2017-03-01 Thread Scott Moser

** Branch linked: lp:~smoser/software-properties/trunk.os-releases

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

Title:
  [SRU] Add support for ocata cloud-archive

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  Fix Released
Status in software-properties source package in Zesty:
  New

Bug description:
  Please add support for:

 cloud-archive:ocata
 cloud-archive:ocata-proposed

  This will also need to be SRU'ed back to xenial.

  [Impact]
  End users have to manually enable the ocata cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:ocata
  sudo add-apt-repository cloud-archive:ocata-proposed

  [Regression potential]
  Limited - just a data item addition

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

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

[Touch-packages] [Bug 1666125] Re: Suspend to RAM with active bluetooth network connection causes problems

2017-03-01 Thread PeterPall

Weird:
a

sudo dhclient

resolves the network problem in most of the cases.

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

Title:
  Suspend to RAM with active bluetooth network connection causes
  problems

Status in network-manager package in Ubuntu:
  New

Bug description:
  If I close my coputer while it is connected to my phone's network via 
bluetooth after resuming all of the following might happen
   - Everything works right and i can re-connect to my bluetooth network using 
the network-manager-gnome icon
   - Bluetooth network can still be used but network-manager seems to forget 
about my WiFi
   - Bluetooth network can still be used and network-manager offers to connect 
to the WiFi stations that were there before suspending. But it doesn't scan for 
new ones
   - Network works. But /etc/resolv.conf points to 127.0.0.0 and hosts cannot 
be resolved until I replace this number by a working nameserver
   - Network works. But dnsmasq no more reacts
   - Network no more works including my loopback network => even a poweroff 
command cannot shut down my computer.

  If any problems exist a sudo service network-manager restart normally
  breaks my loopback network. No idea why.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu2
  Uname: Linux 4.10.0-041000-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Feb 20 08:23:59 2017
  EcryptfsInUse: Yes
  IpRoute:
   default via 192.168.44.1 dev bnep0 proto static metric 750 
   10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 
   169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 
   192.168.44.0/24 dev bnep0 proto kernel scope link src 192.168.44.140 metric 
750
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1669081] [NEW] Ubuntu doesnt boot stuck on FSCK prompt - Press S to skip mounting or M for manual recovery

2017-03-01 Thread Bazak1

Public bug reported:


Working with headless server, my kernel boot console=ttyS0, 
console=ttyS0,115200n8
Ubuntu stuck during boot , fsck prompt for user input
and wait for user input however keyboard console does not function
so system keep stuck ,
i expect that keyboard will be operation so i will be able to press S to skip 
or R to recovery ,
or to workaround it with 10 seconds timeout and automatic Skip later on 


   68.810067] init: plymouth-upstart-bridge main process ended, respawning 
[   68.822144] init: plymouth-upstart-bridge main process (178) terminated with 
status 1
[   68.830078] init: plymouth-upstart-bridge main process ended, respawning 
[   68.842770] init: plymouth-upstart-bridge main process (180) terminated with 
status 1
[   68.850655] init: plymouth-upstart-bridge main process ended, respawning 
 * Stopping Read required files in advance[ OK ]
 * Starting Mount filesystems on boot[ OK ] 
 * Stopping Track if upstart is running in a container[ OK ]
 * Starting Initialize or finalize resolvconf[ OK ] 
 * Starting set console keymap[ OK ]
 * Starting Signal sysvinit that virtual filesystems are mounted[ OK ]  
 * Starting Signal sysvinit that virtual filesystems are mounted[ OK ]  
 * Starting Bridge udev events into upstart[ OK ]   
 * Starting Signal sysvinit that remote filesystems are mounted[ OK ]   
 * Starting device node and kernel event manager[ OK ]  
 * Starting load modules from /etc/modules[ OK ]
 * Starting cold plug devices[ OK ] 
 * Starting log initial device creation[ OK ]   
 * Stopping set console keymap[ OK ]
 * Stopping load modules from /etc/modules[ OK ]
 * Starting Uncomplicated firewall[ OK ]
 * Starting configure network device security[ OK ] 
 * Starting configure network device[ OK ]  
 * Starting configure network device security[ OK ] 
 * Starting configure network device[ OK ]  
 * Starting configure network device security[ OK ] 
 * Starting configure network device[ OK ]  
 * Starting configure network device security[ OK ] 
 * Starting configure network device security[ OK ] 
 * Starting Mount network filesystems[ OK ] 
 * Stopping Mount network filesystems[ OK ] 
 * Starting Signal sysvinit that the rootfs is mounted[ OK ]
 * Starting Clean /tmp directory[ OK ]  
 * Stopping Clean /tmp directory[ OK ]  
 * Starting configure network device[ OK ]  
 * Starting Bridge socket events into upstart[ OK ] 
 * Stopping Read required files in advance (for other mountpoints)[ OK ]
 * Stopping cold plug devices[ OK ] 
 * Stopping log initial device creation[ OK ]   
 * Starting set console font[ OK ]  
 * Stopping set console font[ OK ]  
 * Starting userspace bootsplash[ OK ]  
 * Stopping userspace bootsplash[ OK ]  
 * Starting Send an event to indicate plymouth is up[ OK ]  
 * Stopping Send an event to indicate plymouth is up[ OK ]  
The disk drive for /rescuecd is not ready yet or not present.   
keys:Continue to wait, or Press S to skip mounting or M for manual recovery  

<--- STUCK CANNOT PROCEED WITH BOOT  --->

using  mountall2.53  
amd64 
   filesystem mounting tool 

Description:Ubuntu 14.04.5 LTS  
Release:14.04

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

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

Title:
  Ubuntu doesnt boot stuck on FSCK prompt  - Press S to skip mounting or

[Touch-packages] [Bug 1668813] Re: The tc man page references tc-index man page but tc-index man page does not exist

2017-03-01 Thread Hans Joachim Desserud

Thanks for taking your time to report this issue and help making Ubuntu
better.

I confirm that this issue is still present in 4.9.0-1ubuntu1 on Ubuntu
Zesty. The manpage still mentions tc-index but it is a dead link
http://manpages.ubuntu.com/manpages/zesty/en/man8/tc.8.html. (As you
mention, the tcindex manpage seems to exists.


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

** Tags added: manpage xenial yakkety zesty

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

Title:
  The tc man page references tc-index man page but tc-index man page
  does not exist

Status in iproute2 package in Ubuntu:
  Confirmed

Bug description:
  The tc man page references tc-index man page but tc-index man page
  does not exist.

  The tc-index man page is incorrectly named tcindex.

  This is on Xenial, using package version 4.3.0-1ubuntu3 of iproute2

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

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

[Touch-packages] [Bug 1668485] Re: Xorg intel blank screen

2017-03-01 Thread André Claudino

** Also affects: xserver-xorg-video-intel (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Xorg intel blank screen

Status in xorg package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I have an Hybrid graphics card, my lspci output for then is:

  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
  02:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 960M] (rev a2)

  Once installed nvidia drivre, things work fine (instead they don't
  with noveau). But my problem is using intel driver. This is parte of
  my xorg.conf for nvidia (complete file is attached).

  Section "ServerLayout"
  Identifier "layout"
  Screen 0 "nvidia"
  Inactive "intel"
  EndSection

  
  I have installed xserver-xorg-video-intel and just change xorg.conf

  
  Section "ServerLayout"
  Identifier "layout"
  Screen 0 "intel"
  Inactive "nvidia"
  EndSection

  
  this way, when restarting, I get frozen blank screen while booting, and can't 
do anything other than pressing the power button and and reboot.

  So, I have to start in recovery mode, only way I can work in terminal,
  and change xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb 28 00:33:16 2017
  InstallationDate: Installed on 2017-02-15 (12 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170125.3)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1665559] Re: UbuntuListView dividers don't get updated on model changes

2017-03-01 Thread Josh Arenson

Seeing this here https://code.launchpad.net/~josharenson/unity8
/dashboard-manager as well.

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

Title:
  UbuntuListView dividers don't get updated on model changes

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  I have an UbuntuListView with ListItems, and I add items into the model at 
runtime.
  I want to keep the list sorted, so I insert items at specific positions 
instead of appending them.
  The problem is that the divider only shows up for items that are inserted 
before the last one.
  I read in the API documentation for ListItem [1]:
  > When used in ListView or UbuntuListView, the last list item will not show 
the divider no matter of the visible property value set.

  So I suppose this is the reason. But shouldn't the divider become
  visible when the model changes and the ListItem is no longer the last
  one?

  For example, I add the following items, in order:
  * aaa
  * ccc
  * bbb

  Because the list is sorted, when adding `bbb` it is inserted in the
  middle and receives a divider. But `aaa` remains with no divider, and
  the list looks weird.

  Expected:
  aaa
  -
  bbb
  -
  ccc

  Actual:
  aaa
  bbb
  -
  ccc

  Here is the full source code:

  === Main.qml ===

  import QtQuick 2.4
  import QtQuick.Layouts 1.1

  import Ubuntu.Components 1.2

  MainView {

  width: units.gu(40)
  height: units.gu(40)

  Page {

  ColumnLayout {
  spacing: units.gu(1)
  anchors {
  margins: units.gu(2)
  fill: parent
  }

  TextField {
  id: textInput
  Layout.fillWidth: true;
  hasClearButton: true
  onAccepted: {
  addToList();
  }
  }

  MyList {
  id: myList
  anchors {
  left: parent.left
  right: parent.right
  }
  height: parent.height
  }
  }
  }

  function addToList() {
  if(textInput.text.length > 0) {
  myList.add(textInput.text);
  textInput.text = '';
  }
  }
  }

  === MyList.qml ===

  import QtQuick 2.4
  import Ubuntu.Components 1.2
  import Ubuntu.Components.ListItems 1.0

  Item {

  ListModel {
  id: listModel
  }

  UbuntuListView {
  anchors.fill: parent
  model: listModel

  delegate: ListItem {
  id: listItem
  height: units.gu(5)

  divider.visible: true; // doesn't help
  Label {
  text: itemName
  verticalAlignment: Text.AlignVCenter
  height: parent.height
  }

  onClicked: {
  divider.visible = true; // doesn't help
  }
  }
  }

  function add(text) {
  var indexToInsert = listModel.count;
  for(var i = 0; i < listModel.count; i++) {
  var compareResult = text.localeCompare(listModel.get(i).itemName);
  if(compareResult <= 0) {
  indexToInsert = i;
  break;
  }
  }
  listModel.insert(indexToInsert, {itemName: text});
  }
  }

  
  I'm not really sure if this is a bug, or if I'm not using the API correctly.

  [1]
  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04/Ubuntu.Components.ListItem/

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

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

[Touch-packages] [Bug 1577926] Re: apt-key works fine, yet apt fails with "Could not execute 'apt-key'"

2017-03-01 Thread Griffin

I encountered this bug also, and it originated with a shell script that
invoked rrdtool and exported a tar file to /tmp. Once this was done,
/tmp was apparently owned by user ganglia (the rrdtool user) rather than
root.  Chown-ing to root:root didn't fix the issue, however.  Chmod-ing
/tmp to 1777 *did* fix this issue and apt-key was working normally after
that.

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

Title:
  apt-key works fine, yet apt fails with "Could not execute 'apt-key'"

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Apt can fail to verify a Release file which verifies just fine when
  calling apt-key directly.

  Please advise how i can supply further debug information to help fix
  the underlying bug.

  Expected:
  apt-get should only report that a repository is not signed when no such 
signature was found.
  If a signature was in fact successfully acquired but not verified, apt-get 
should report failure to verify instead.
  apt-get should have a meaningful error message when calling apt-key fails.

  Bonus:
  Calling apt-key should not fail when the same thing works fine on command 
line.
  A reference to "Debug::Acquire::gpgv" should be in apt-secure(8) 
documentation.

  Observed:

  # uname -a
  Linux hostname 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 
i686 i686 i686 GNU/Linux
  # chroot reproducable
  $ uname -a
  Linux hostname 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 
armv7l armv7l armv7l GNU/Linux

  $ lsb_release -a 2>/dev/null
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  $ apt-get -o "Debug::Acquire::gpgv=true" update
  Get:1 http://ports.ubuntu.com xenial-security InRelease [92.2 kB]
  0% [1 InRelease gpgv 92.2 kB]igners 
  Preparing to exec:  /usr/bin/apt-key --quiet --readonly verify --status-fd 3 
/tmp/apt.sig.jYGUCG /tmp/apt.data.uTkX1c
  gpgv exited with status 111
  Summary:
Good: 
Bad: 
Worthless: 
SoonWorthless: 
NoPubKey: 
  Ign:1 http://ports.ubuntu.com xenial-security InRelease
  Fetched 92.2 kB in 1s (79.5 kB/s)
  Reading package lists... Done
  W: GPG error: http://ports.ubuntu.com xenial-security InRelease: Could not 
execute 'apt-key' to verify signature (is gnupg installed?)
  W: The repository 'http://ports.ubuntu.com xenial-security InRelease' is not 
signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.

  $ /usr/bin/apt-key --quiet --readonly verify --status-fd /dev/stderr 
/tmp/apt.sig.jYGUCG /tmp/apt.data.uTkX1c
  gpgv: Signature made Tue May  3 19:02:17 2016 UTC using DSA key ID 437D05B5
  [GNUPG:] SIG_ID e53PXRjA/EMb7CuZJtAicvvUm60 2016-05-03 1462302137
  [GNUPG:] GOODSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key 

  gpgv: Good signature from "Ubuntu Archive Automatic Signing Key 
"
  [GNUPG:] VALIDSIG 630239CC130E1A7FD81A27B140976EAF437D05B5 2016-05-03 
1462302137 0 4 0 17 10 01 630239CC130E1A7FD81A27B140976EAF437D05B5
  gpgv: Signature made Tue May  3 19:02:17 2016 UTC using RSA key ID C0B21F32
  [GNUPG:] SIG_ID kCsrLo9VUm7YcYhhqQUw2fbWoY4 2016-05-03 1462302137
  [GNUPG:] GOODSIG 3B4FE6ACC0B21F32 Ubuntu Archive Automatic Signing Key (2012) 

  gpgv: Good signature from "Ubuntu Archive Automatic Signing Key (2012) 
"
  [GNUPG:] VALIDSIG 790BC7277767219C42C86F933B4FE6ACC0B21F32 2016-05-03 
1462302137 0 4 0 1 10 01 790BC7277767219C42C86F933B4FE6ACC0B21F32

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

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

[Touch-packages] [Bug 1596056] [init-system-helpers/xenial] verification still needed

2017-03-01 Thread Ubuntu Foundations Team Bug Bot

The fix for this bug has been awaiting testing feedback in the -proposed
repository for xenial for more than 90 days.  Please test this fix and
update the bug appropriately with the results.  In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed from the -proposed repository.

** Tags added: removal-candidate

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

Title:
  output of invoke-rc.d for systemd units un-debuggable on failure

Status in init-system-helpers package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Xenial:
  Fix Committed

Bug description:
  [SRU Justification]
  Currently if a systemd unit fails to start in a non-interactive upgrade and 
all you have is a log, it's impossible to debug.  Fix this so that logs contain 
the actual details of the unit failure.

  [Test case]
  1. Get a root shell.
  2. Run "sed -e's,sbin/sshd,sbin/sshd-noexists,; /Alias/d' 
/lib/systemd/system/ssh.service > /lib/systemd/system/ssh-noexists.service"
  3. Run 'systemctl enable ssh-noexists'
  4. Run 'invoke-rc.d ssh-noexists start'
  5. Verify that the command directs you to run 'systemctl status' for details, 
and provides no details.
  6. Install init-system-helpers from -proposed.
  7. Run 'invoke-rc.d ssh-noexists start'.
  8. Verify that the command provides details about the failure to start 
ssh-noexists service.
  9. Run 'systemctl disable ssh-noexists'.
  10. Run 'rm -f /lib/systemd/system/ssh-noexists.service'.

  [Regression potential]
  Minimal.  On the failure case, an additional command is run; the additional 
command is guarded with || true.

  [Original description]

  When invoke-rc.d is called on a systemd system, if the unit fails to
  start, you get output like:

  Created symlink 
/etc/systemd/system/multi-user.target.wants/openafs-fileserver.service → 
/lib/systemd/system/openafs-fileserver.service.
  Job for openafs-fileserver.service failed because the control process exited 
with error code.
  See "systemctl status openafs-fileserver.service" and "journalctl -xe" for 
details.
  invoke-rc.d: initscript openafs-fileserver, action "start" failed.
  dpkg: error processing package openafs-fileserver (--configure):
   subprocess installed post-installation script returned error exit status 1

  The output shown here comes from systemctl itself, and is usually
  fine.  The admin who ran systemctl can run those other commands to
  debug.

  However, when called by invoke-rc.d, this output is usually seen only
  in a log file; maybe submitted in a bug report, maybe attached to
  something like an autopkgtest:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-yakkety/yakkety/armhf/o/openafs/20160624_174535@/log.gz

  By the time someone looks at this log output, it is often too late to
  run those commands in order to debug the failure.

  invoke-rc.d should call these commands for us on systemd unit failure,
  so that the relevant debugging information is included in the log
  where it can help.

  We don't want to call 'journalctl -xe', which might leak information
  into the log from other jobs, but 'journalctl -x -u ' may
  be appropriate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1596056/+subscriptions

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

[Touch-packages] [Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

2017-03-01 Thread Scott Moser

** No longer affects: cloud-init

** No longer affects: cloud-init (Ubuntu)

** No longer affects: cloud-init (Ubuntu Xenial)

** No longer affects: cloud-init (Ubuntu Yakkety)

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

Title:
  systemd-networkd runs too late for cloud-init.service (net)

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

Bug description:
  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not
  yet available when cloud-init.service runs.

  cloud-init service unit deps look like this:

  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target

  Here's networkd unit deps:

  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target

  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname

  And a critical-chain output:

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  systemd-networkd.service +440ms
  └─dbus.service @11.461s
    └─basic.target @11.403s
  └─sockets.target @11.401s
    └─dbus.socket @11.398s
  └─cloud-init.service @10.127s +1.266s
    └─networking.service @9.305s +799ms
  └─network-pre.target @9.295s
    └─cloud-init-local.service @3.822s +5.469s
  └─local-fs.target @3.813s
    └─run-cgmanager-fs.mount @12.687s
  └─local-fs-pre.target @1.393s
    └─systemd-tmpfiles-setup-dev.service @1.116s +195ms
  └─kmod-static-nodes.service @887ms +193ms
    └─system.slice @783ms
  └─-.slice @721ms

  cloud-init would need networkd to run at or before
  'networking.service' so it can raise networking to then find and use
  network-based datasources.

  # grep systemd /usr/share/snappy/dpkg.list
  ii  libnss-resolve:amd64  229-4ubuntu11   
 amd64nss module to resolve names via systemd-resolved
  ii  libpam-systemd:amd64  229-4ubuntu11   
 amd64system and service manager - PAM module
  ii  libsystemd0:amd64 229-4ubuntu11   
 amd64systemd utility library
  ii  systemd   229-4ubuntu11   
 amd64system and service manager
  ii  systemd-sysv  229-4ubuntu11   
 amd64system and service manager - SysV links

  # grep cloud-init /usr/share/snappy/dpkg.list
  ii  cloud-init
0.7.8-201610260005-gf7a5756-0ubuntu1~trunk~ubuntu16.04.1 all  Init 
scripts for cloud instances

  SRU INFORMATION FOR systemd
  ===
  Fix: For xenial it is sufficient to drop systemd-networkd's 
After=dbus.service (https://github.com/systemd/systemd/commit/5f004d1e32) and 
(for xenial only) drop the useless org.freedesktop.network1.busname unit (which 
is always "condition failed" as there is no kdbus, but it moves 
systemd-network.service after sockets.target which is too late for cloud-init).

  Regression potential: Low. networkd is not widely being used out

[Touch-packages] [Bug 1668535] [NEW] Ubuntu17.04-Failed to activate (encrypted) Swap Partition

You have been subscribed to a public bug:

---Problem Description---
Ubuntu17.04 installation with swap encryption ,Fails to activate Swap Partition.

---uname output---
Linux tuleta4u-lp7 4.9.0-11-generic #12-Ubuntu SMP Mon Dec 12 16:16:45 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

---boot type---
VDVD installtion 

---Steps to reproduce--
1.Install creating a prep boot, swap and root partition.
2.Encrypt swap partition.
3.Installation completes, and after reboot can see the failed messages for 
activating swap partition.

--Error--
While booting,

[  OK  ] Started AppArmor initialization.
[FAILED] Failed to activate swap Swap Partition.
See 'systemctl status dev-sda2.swap' for details.
[FAILED] Failed to start Cryptography Setup for sda2_crypt.
See 'systemctl status systemd-cryptsetup@sda2_crypt.service' for details.
[DEPEND] Dependency failed for Encrypted Volumes.
 Starting Raise network interfaces...

---Logs---

root@tuleta4u-lp7:~# systemctl status systemd-cryptsetup@sda2_crypt.service
? systemd-cryptsetup@sda2_crypt.service - Cryptography Setup for sda2_crypt
   Loaded: loaded (/etc/crypttab; generated; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2017-01-02 01:58:14 EST; 1min 57
 Docs: man:crypttab(5)
   man:systemd-cryptsetup-generator(8)
   man:systemd-cryptsetup@.service(8)
 Main PID: 2023 (code=exited, status=0/SUCCESS)

Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: Starting Cryptography Setup for sda2_cr
Jan 02 01:58:14 tuleta4u-lp7 mkswap[2057]: mkswap: error: /dev/mapper/sda2_crypt
Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: 
Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: Failed to start Cryptography Setup for 
Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: 
Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: 


root@tuleta4u-lp7:~# systemctl start systemd-cryptsetup@sda2_crypt.service
Job for systemd-cryptsetup@sda2_crypt.service failed because the control 
process exited with error code.
See "systemctl status systemd-cryptsetup@sda2_crypt.service" and "journalctl 
-xe" for details.

root@tuleta4u-lp7:~# journalctl -xe
-- The start-up result is done.
Jan 02 03:17:01 tuleta4u-lp7 CRON[3955]: pam_unix(cron:session): session opened 
Jan 02 03:17:01 tuleta4u-lp7 CRON[3956]: (root) CMD (   cd / && run-parts --repo
Jan 02 03:17:01 tuleta4u-lp7 CRON[3955]: pam_unix(cron:session): session closed 
Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: Starting Cryptography Setup for sda2_cr
-- Subject: Unit systemd-cryptsetup@sda2_crypt.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit systemd-cryptsetup@sda2_crypt.service has begun starting up.
Jan 02 03:37:57 tuleta4u-lp7 systemd-cryptsetup[3960]: Volume sda2_crypt already
Jan 02 03:37:57 tuleta4u-lp7 mkswap[3962]: mkswap: error: /dev/mapper/sda2_crypt
Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: 
Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: Failed to start Cryptography Setup for 
-- Subject: Unit systemd-cryptsetup@sda2_crypt.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit systemd-cryptsetup@sda2_crypt.service has failed.
-- 
-- The result is failed.
Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: 
Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service:

root@tuleta4u-lp7:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
# / was on /dev/sda3 during installation
UUID=44e6ba68-4cbb-4978-8d90-6077796b3715 /   xfs defaults  
  0   0

root@tuleta4u-lp7:~# lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda  8:00   235G  0 disk  
??sda1   8:10 7M  0 part  
??sda2   8:2028G  0 part  
? ??sda2_crypt 253:0028G  0 crypt [SWAP]
??sda3   8:30 167.7G  0 part  /
??sda4   8:4028G  0 part  
sdb  8:16   0   235G  0 disk  
sr0 11:01 631.3M  0 rom   
sr1 11:11 631.3M  0 rom

== Comment: #12 -
Hi Canonical,

This is the patch (debdiff) for Zesty.
The same patch as submitted to systemd upstream on [1].

[1] https://github.com/systemd/systemd/pull/5480

== Comment: #14 - 
With this patch/test packages, the ordering between cryptsetup service (before) 
and swap target (after) is ensured.

# journalctl -b -x | grep 'crypt\|swap'
Feb 27 18:03:00 ubuntu kernel: zswap: loaded using pool lzo/zbud
Feb 27 18:03:00 ubuntu kernel: Key type encrypted registered
Feb 27 18:03:01 ubuntu kernel: crypto_register_alg 'aes' = 0
Feb 27 18:03:01 ubuntu kernel: crypto_register_alg '

[Touch-packages] [Bug 1668535] Re: Ubuntu17.04-Failed to activate (encrypted) Swap Partition

2017-03-01 Thread Dimitri John Ledkov

** Changed in: debian-installer (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Dimitri John Ledkov (xnox)

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

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

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

** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-17.03

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

Title:
  Ubuntu17.04-Failed to activate (encrypted) Swap Partition

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ---Problem Description---
  Ubuntu17.04 installation with swap encryption ,Fails to activate Swap 
Partition.

  ---uname output---
  Linux tuleta4u-lp7 4.9.0-11-generic #12-Ubuntu SMP Mon Dec 12 16:16:45 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  ---boot type---
  VDVD installtion 

  ---Steps to reproduce--
  1.Install creating a prep boot, swap and root partition.
  2.Encrypt swap partition.
  3.Installation completes, and after reboot can see the failed messages for 
activating swap partition.

  --Error--
  While booting,

  [  OK  ] Started AppArmor initialization.
  [FAILED] Failed to activate swap Swap Partition.
  See 'systemctl status dev-sda2.swap' for details.
  [FAILED] Failed to start Cryptography Setup for sda2_crypt.
  See 'systemctl status systemd-cryptsetup@sda2_crypt.service' for details.
  [DEPEND] Dependency failed for Encrypted Volumes.
   Starting Raise network interfaces...

  ---Logs---

  root@tuleta4u-lp7:~# systemctl status systemd-cryptsetup@sda2_crypt.service
  ? systemd-cryptsetup@sda2_crypt.service - Cryptography Setup for sda2_crypt
 Loaded: loaded (/etc/crypttab; generated; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2017-01-02 01:58:14 EST; 1min 
57
   Docs: man:crypttab(5)
 man:systemd-cryptsetup-generator(8)
 man:systemd-cryptsetup@.service(8)
   Main PID: 2023 (code=exited, status=0/SUCCESS)

  Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: Starting Cryptography Setup for 
sda2_cr
  Jan 02 01:58:14 tuleta4u-lp7 mkswap[2057]: mkswap: error: 
/dev/mapper/sda2_crypt
  Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: 
systemd-cryptsetup@sda2_crypt.service: 
  Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: Failed to start Cryptography Setup 
for 
  Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: 
systemd-cryptsetup@sda2_crypt.service: 
  Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: 
systemd-cryptsetup@sda2_crypt.service: 

  
  root@tuleta4u-lp7:~# systemctl start systemd-cryptsetup@sda2_crypt.service
  Job for systemd-cryptsetup@sda2_crypt.service failed because the control 
process exited with error code.
  See "systemctl status systemd-cryptsetup@sda2_crypt.service" and "journalctl 
-xe" for details.

  root@tuleta4u-lp7:~# journalctl -xe
  -- The start-up result is done.
  Jan 02 03:17:01 tuleta4u-lp7 CRON[3955]: pam_unix(cron:session): session 
opened 
  Jan 02 03:17:01 tuleta4u-lp7 CRON[3956]: (root) CMD (   cd / && run-parts 
--repo
  Jan 02 03:17:01 tuleta4u-lp7 CRON[3955]: pam_unix(cron:session): session 
closed 
  Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: Starting Cryptography Setup for 
sda2_cr
  -- Subject: Unit systemd-cryptsetup@sda2_crypt.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://www.ubuntu.com/support
  -- 
  -- Unit systemd-cryptsetup@sda2_crypt.service has begun starting up.
  Jan 02 03:37:57 tuleta4u-lp7 systemd-cryptsetup[3960]: Volume sda2_crypt 
already
  Jan 02 03:37:57 tuleta4u-lp7 mkswap[3962]: mkswap: error: 
/dev/mapper/sda2_crypt
  Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: 
systemd-cryptsetup@sda2_crypt.service: 
  Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: Failed to start Cryptography Setup 
for 
  -- Subject: Unit systemd-cryptsetup@sda2_crypt.service has failed
  -- Defined-By: systemd
  -- Support: http://www.ubuntu.com/support
  -- 
  -- Unit systemd-cryptsetup@sda2_crypt.service has failed.
  -- 
  -- The result is failed.
  Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: 
systemd-cryptsetup@sda2_crypt.service: 
  Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: 
systemd-cryptsetup@sda2_crypt.service:

  root@tuleta4u-lp7:~# cat /etc/fstab
  # /etc/fstab: static file system information.
  #
  # Use 'blkid' to print the universally unique identifier for a
  # device; this may be used with UUID= as a more robust way to name devices
  # that works even if disks are added and removed. See fstab(5).
  #
  #
  # / was on /dev/sda3 during installation
  UUID=44e6ba68-4cbb-4978-8d90-6077796b3715 /   xfs defaults
0   0

  root@tuleta4u-lp7:~# lsblk
  NAME   MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
  sda  8:00   235G  0 disk  
  ??sda1   8:10 7M  0 part  
  ??sda2   8:2028G  0 part  
  ? ??sda2_crypt 253:0

[Touch-packages] [Bug 1364492] Re: findutils uses nearly 100% CPU and memory resources

This bug was fixed in the package findutils - 4.6.0+git+20161106-2

---
findutils (4.6.0+git+20161106-2) unstable; urgency=medium

  * 20_find-fix-memory-leak-in-mount-list-handling.patch from upstream GIT
master: Fix memory leak in mount list handling. LP: #1364492
https://savannah.gnu.org/bugs/?50326

 -- Andreas Metzler   Sat, 18 Feb 2017 16:37:32
+0100

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

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

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

Title:
  findutils uses nearly 100% CPU and memory resources

Status in findutils package in Ubuntu:
  Fix Released

Bug description:
  findutils is using a find command, probably to auto-update indexing database.
  While this is normal behaviour, i found out that shortly after the indexing 
update started, findutils is using 100% of CPU resources (Haswell Pentium 
G3258), all of my system's memory (8GB RAM) and some of the swap, rendering the 
system completely unusable.

  Issueing the command 'ps ax | grep find' results in:
  29729 ?SN 0:00 /bin/sh /usr/bin/updatedb.findutils
  29737 ?SN 0:00 /bin/sh /usr/bin/updatedb.findutils
  29758 ?SN 0:00 su nobody -s /bin/sh -c /usr/bin/find / 
-ignore_readdir_race  \( -fstype NFS -o -fstype nfs -o -fstype nfs4 -o 
-fstype afs -o -fstype binfmt_misc -o -fstype proc -o -fstype smbfs -o -fstype 
autofs -o -fstype iso9660 -o -fstype ncpfs -o -fstype coda -o -fstype devpts -o 
-fstype ftpfs -o -fstype devfs -o -fstype mfs -o -fstype shfs -o -fstype sysfs 
-o -fstype cifs -o -fstype lustre_lite -o -fstype tmpfs -o -fstype usbfs -o 
-fstype udf -o -fstype ocfs2 -o  -type d -regex 
'\(^/tmp$\)\|\(^/usr/tmp$\)\|\(^/var/tmp$\)\|\(^/afs$\)\|\(^/amd$\)\|\(^/alex$\)\|\(^/var/spool$\)\|\(^/sfs$\)\|\(^/media$\)\|\(^/var/lib/schroot/mount$\)'
 \) -prune -o -print0
  29767 ?SNs0:00 sh -c /usr/bin/find / -ignore_readdir_race  \( 
-fstype NFS -o -fstype nfs -o -fstype nfs4 -o -fstype afs -o -fstype 
binfmt_misc -o -fstype proc -o -fstype smbfs -o -fstype autofs -o -fstype 
iso9660 -o -fstype ncpfs -o -fstype coda -o -fstype devpts -o -fstype ftpfs -o 
-fstype devfs -o -fstype mfs -o -fstype shfs -o -fstype sysfs -o -fstype cifs 
-o -fstype lustre_lite -o -fstype tmpfs -o -fstype usbfs -o -fstype udf -o 
-fstype ocfs2 -o  -type d -regex 
'\(^/tmp$\)\|\(^/usr/tmp$\)\|\(^/var/tmp$\)\|\(^/afs$\)\|\(^/amd$\)\|\(^/alex$\)\|\(^/var/spool$\)\|\(^/sfs$\)\|\(^/media$\)\|\(^/var/lib/schroot/mount$\)'
 \) -prune -o -print0
  29768 ?RN57:29 /usr/bin/find / -ignore_readdir_race ( -fstype NFS 
-o -fstype nfs -o -fstype nfs4 -o -fstype afs -o -fstype binfmt_misc -o -fstype 
proc -o -fstype smbfs -o -fstype autofs -o -fstype iso9660 -o -fstype ncpfs -o 
-fstype coda -o -fstype devpts -o -fstype ftpfs -o -fstype devfs -o -fstype mfs 
-o -fstype shfs -o -fstype sysfs -o -fstype cifs -o -fstype lustre_lite -o 
-fstype tmpfs -o -fstype usbfs -o -fstype udf -o -fstype ocfs2 -o -type d 
-regex 
\(^/tmp$\)\|\(^/usr/tmp$\)\|\(^/var/tmp$\)\|\(^/afs$\)\|\(^/amd$\)\|\(^/alex$\)\|\(^/var/spool$\)\|\(^/sfs$\)\|\(^/media$\)\|\(^/var/lib/schroot/mount$\)
 ) -prune -o -print0

  Results from 'top':
  top - 19:16:00 up  1:40,  3 users,  load average: 1,14, 1,20, 1,53
  Tasks: 274 total,   2 running, 272 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  2,9 us, 22,9 sy, 24,4 ni, 42,4 id,  7,6 wa,  0,0 hi,  0,0 si,  0,0 
st
  KiB Mem:   8086304 total,  7876904 used,   209400 free,   60 buffers
  KiB Swap: 20971516 total,   373796 used, 20597720 free.  4627412 cached Mem

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
  29768 nobody30  10   14968   1556   1116 R  92,2  0,0  70:16.74 find  
  

  System installation is Ubuntu Utopic on Unity 7 desktop, using nouveau nvidia 
drivers.
  findutils version is  4.4.2-9

  Sorry for posting the commands output in here, if there is another
  guideline for this i'll be happy to edit that.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: findutils 4.4.2-9
  ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1
  Uname: Linux 3.16.0-11-generic x86_64
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep  2 19:03:25 2014
  Dependencies:
   gcc-4.9-base 4.9.1-10ubuntu2
   libc6 2.19-10ubuntu1
   libgcc1 1:4.9.1-10ubuntu2
   multiarch-support 2.19-10ubuntu1
  InstallationDate: Installed on 2014-08-19 (14 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140815)
  SourcePackage: findutils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/

[Touch-packages] [Bug 1661611] Re: apt/unattended-upgrades stalls shutdown

2017-03-01 Thread SergeiFranco

I can confirm this bug also happens machines without LVM volumes.

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

Title:
  apt/unattended-upgrades stalls shutdown

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  When unattended-upgrades is installed, 9 out of 10 shutdowns/reboots
  hang while "starting unattended upgrades shutdown". This hang stalls
  the shutdown process for 5-10 mins.

  If I disable unnattended-upgrades via the /etc/apt/apt.conf.d/20auto-
  upgrades and/or 50unattended-upgrades, the problems occurs.

  If I terminate the service before shutdown/reboot (sudo service
  unattended-upgrades stop) the problem still occurs.

  If I remove the package (sudo apt remove unattended-upgrades) the
  problem no longer occurs.

  This occurs on a freshly installed version of Ubuntu Server 16.04.1
  (both unattended-upgrades installed via install GUI or manual install
  of unattended-upgrades)

  Both Kern.log & syslog do not show the shutdown process (I believe
  because the filesystems have already unmounted)

  Original report: http://askubuntu.com/questions/878630/apt-unattended-
  upgrades-stalls-shutdown

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

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

[Touch-packages] [Bug 1669133] [NEW] Drop unnecessary rename of dlm -> dlm-controld (binary package)

2017-03-01 Thread Nish Aravamudan

Public bug reported:

dlm -> dlm-controld transition (will need to be kept through 18.04 for LTS 
upgraders)
  - Add transitional dummy binary package to rename back
  - Drop delta in lvm2 and ocfs2-tools

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

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

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

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

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

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

Title:
  Drop unnecessary rename of dlm -> dlm-controld (binary package)

Status in dlm package in Ubuntu:
  New
Status in lvm2 package in Ubuntu:
  New
Status in ocfs2-tools package in Ubuntu:
  New

Bug description:
  dlm -> dlm-controld transition (will need to be kept through 18.04 for LTS 
upgraders)
- Add transitional dummy binary package to rename back
- Drop delta in lvm2 and ocfs2-tools

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

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

[Touch-packages] [Bug 1633828] Re: Mounting /boot/efi fails always after updating to 16.10

2017-03-01 Thread Phillip Susi

So the problem seems to have gone away eh?  Well, if it comes back let
us know.

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

Title:
  Mounting /boot/efi fails always after updating to 16.10

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  System does not boot properly as mounting /boot/efi fails. Commented
  out /boot/efi entry in /etc/fstab to boot system normally. This
  started happening after update to 16.10. Everything was working fine
  in 15.10, 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: mount 2.28.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Sun Oct 16 15:23:19 2016
  InstallationDate: Installed on 2015-11-20 (330 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago)

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

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

[Touch-packages] [Bug 1661406] Re: apparmor failing to be purged on trusty

2017-03-01 Thread Tyler Hicks

** Changed in: apparmor (Ubuntu Trusty)
   Status: Triaged => In Progress

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

Title:
  apparmor failing to be purged on trusty

Status in apparmor package in Ubuntu:
  Invalid
Status in apparmor source package in Trusty:
  In Progress

Bug description:
  Version: 2.10.95-0ubuntu2.5~14.04.1

  When executing apt -y purge apparmor.

  The purge run but has errors as files do not exist and the rmdir fails
  to execute.

  rmdir: failed to remove '/var/lib/apparmor/profiles': No such file or
  directory

  Steps to reproduce:
  apt-get update
  apt-get -y install apparmor
  apt -y purge apparmor

  I will put workarounds in place for now in puppet but this is making
  puppet not like it..

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

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

[Touch-packages] [Bug 1669156] [NEW] Fails writing with Caps Lock

2017-03-01 Thread johnmne

Public bug reported:

On Ubuntu 16.04:

When clicking on the following 3 keyboard keys simultaneously: 
Left-CTRL + Left-ALT + F1
Then you get to a textual terminal (CLI) where you can type commands.
But there is a problem when typing English letters with Caps Lock turned on:
Instead of English capital letters - you see squares, 
so actually you can't login to your user that way
if the username/password has Capital letters.

The only method which allows you to write capital English letters
is to simultaneously click Left-Shift + 'a letter'. 
That is the only method that works well.

Note that the Caps Lock key works well with the graphical terminal (pseudo / 
pts)
that appears on Ubuntu when hitting simultaneously:
Left-CTRL + Left-ALT + T

---

I assumed the bug report is relevant to "shadow" package because that
the "/bin/login" binary comes from that package.
Package version of 'shadow' is: 1:4.2-3.1ubuntu5

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

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

Title:
  Fails writing with Caps Lock

Status in shadow package in Ubuntu:
  New

Bug description:
  On Ubuntu 16.04:

  When clicking on the following 3 keyboard keys simultaneously: 
  Left-CTRL + Left-ALT + F1
  Then you get to a textual terminal (CLI) where you can type commands.
  But there is a problem when typing English letters with Caps Lock turned on:
  Instead of English capital letters - you see squares, 
  so actually you can't login to your user that way
  if the username/password has Capital letters.

  The only method which allows you to write capital English letters
  is to simultaneously click Left-Shift + 'a letter'. 
  That is the only method that works well.

  Note that the Caps Lock key works well with the graphical terminal (pseudo / 
pts)
  that appears on Ubuntu when hitting simultaneously:
  Left-CTRL + Left-ALT + T

  ---

  I assumed the bug report is relevant to "shadow" package because that
  the "/bin/login" binary comes from that package.
  Package version of 'shadow' is: 1:4.2-3.1ubuntu5

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

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

[Touch-packages] [Bug 1669055] Re: TZ is not set by default

2017-03-01 Thread Seth Arnold

Hello, thanks for this report; I suspect this would prevent the Time And
Date Settings... dialog box from changing the timezone for already-
running processes. It might make sense for very stationary systems but
wouldn't be very friendly for travelers with more mobile machines.

Thanks

** Changed in: shadow (Ubuntu)
   Status: New => Opinion

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

Title:
  TZ is not set by default

Status in shadow package in Ubuntu:
  Opinion

Bug description:
  It seems that unsetting the environment variable TZ there is a huge
  performance penalty calling some glibc functions, eg. time()

  this has been documented here:

  https://blog.packagecloud.io/eng/2017/02/21/set-environment-variable-
  save-thousands-of-system-calls/

  and I can confirm it on an amd64 system running Yakkety:

  $ cat time.c
  #include 

  int main(int argc, char *argv[])
  {
  int i = 0;
  time_t timep;

  for (i = 0; i < 1000; i++) {
  time(&timep);
  localtime(&timep);
  }

  return 0;
  }
  $ gcc -Wall -O3 time.c -o time
  $ time ./time

  real0m7.102s
  user0m2.060s
  sys 0m5.040s
  $ time TZ=:/etc/localtime ./time

  real0m0.952s
  user0m0.948s
  sys 0m0.000s
  $

  I've set TZ in /etc/environment to have it globally defined.

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

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

[Touch-packages] [Bug 1665589] Re: Killer 1535 802.11 2×2 Wi-Fi + BT 4.1 controller can't discover MS Mobile Mouse 3600

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

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

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

Title:
  Killer 1535 802.11 2×2 Wi-Fi + BT 4.1 controller can't discover MS
  Mobile Mouse 3600

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I saw number of posts here about Mobile Mouse 3600 but sadly none of
  them helped me to debug the issue.

  I have Killer 1535 card on my Dell XPS 13. According to specs it's
  Bluetooth 4.1 device. Mobile Mouse 3600 is Bluetooth Low Energy device
  of version 4.0.

  In theory these two devices should be able to communicate.
  Unfortunately they don't :(

  I'm on Ubuntu MATE 16.10 but I also tested it on Linux Mint 18 and
  Element OS. I have bluez 5.41 installed.

  Here is what info I have abut my devices

  usb-devices | awk '/e301/' RS=

  T:  Bus=01 Lev=01 Prnt=01 Port=02 Cnt=03 Dev#=  4 Spd=12  MxCh= 0
  D:  Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=0cf3 ProdID=e301 Rev=00.01
  C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

  
  hciconfig -a | grep HCI

  HCI Version: 4.1 (0x7)  Revision: 0x0

  lsusb | grep Ath

  Bus 001 Device 004: ID 0cf3:e301 Atheros Communications, Inc.

  `sudo hcitool lescan` finds nothing.

  After clean installation `dmesg | grep ath10` gives

  [   14.979939] ath10k_pci :3a:00.0: enabling device ( -> 0002)
  [   14.981966] ath10k_pci :3a:00.0: pci irq msi oper_irq_mode 2 
irq_mode 0 reset_mode 0
  [   15.263691] ath10k_pci :3a:00.0: Direct firmware load for 
ath10k/pre-cal-pci-:3a:00.0.bin failed with error -2
  [   15.263709] ath10k_pci :3a:00.0: Direct firmware load for 
ath10k/cal-pci-:3a:00.0.bin failed with error -2
  [   15.263734] ath10k_pci :3a:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
  [   15.263736] ath10k_pci :3a:00.0: could not fetch firmware file 
'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
  [   15.440154] ath10k_pci :3a:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:1535
  [   15.440156] ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1 tracing 
1 dfs 0 testmode 0
  [   15.440582] ath10k_pci :3a:00.0: firmware ver 
WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad 
crc32 75dee6c5
  [   15.532098] ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A crc32 
6fc88fe7
  [   17.658135] ath10k_pci :3a:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 
cal otp max-sta 32 raw 0 hwcrypto 1
  [   17.770412] ath10k_pci :3a:00.0 wlp58s0: renamed from wlan0

  My WiFi works. I can also pair Bluetooth keyboard. Since I don't
  really know how device drivers work in Linux I noticed line with error
  about `firmware-5.bin` in output of dmesg. So I took missing file from
  https://github.com/kvalo/ath10k-
  firmware/tree/master/QCA6174/hw3.0/4.4. It turned out to be bad idea
  because it botched wifi/bluetooth completely. Here is what I had in
  log

  [3.519354] ath10k_pci :3a:00.0: enabling device ( -> 0002)
  [3.521259] ath10k_pci :3a:00.0: pci irq msi-x interrupts 8 
irq_mode 0 reset_mode 0
  [3.765880] ath10k_pci :3a:00.0: Direct firmware load for 
ath10k/cal-pci-:3a:00.0.bin failed with error -2
  [3.831220] ath10k_pci :3a:00.0: failed to fetch board data for 
ath10k/QCA6174/hw3.0 from bus=pci,bmi-chip-id=0,bmi-board-id=0/board-2.bin
  [5.887772] ath10k_pci :3a:00.0: Unknown eventid: 90118
  [5.887786] ath10k_pci :3a:00.0: qca6174 hw3.2 (0x0503, 
0x00340aff bmi 0:0) fw WLAN.RM.4.4-00022-QCARMSWPZ-2 fwapi 5 bdapi 1 htt-ver 
3.32 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 features 
wowlan,ignore-otp
  [5.887789] ath10k_pci :3a:00.0: debug 0 debugfs 1 tracing 1 dfs 0 
testmode 0
  [8.884160] ath10k_pci :3a:00.0: could not suspend target (-11)
  [8.966789] ath10k_pci :3a:00.0 wlp58s0: renamed from wlan0
  [   11.178547] ath10k_pci :3a:00.0: Unknown eventid: 90118
  [   14.176459] ath10k_pci :3a:00.0: failed to enable dynamic BW: -11
  [   20.176417] ath10k_pci :3a:00.0: could not suspend target (-11)
  [   22.435758] ath10k_pci :3a:00.0: Unknown eventid: 90118
  [   25.432569] ath10k_pci :3a:00.0: failed to enable dynamic BW: -11
  [   31.432925] ath10k_pci :3a:00.0: could not suspend target (-11)
  [   33.687090] ath10k_pci :3a:00.0: Unknown eventid: 90118
  [   36.684683] ath10k_pci :3a:00.0: failed to enable dynamic BW: -11
  [   42.685119

[Touch-packages] [Bug 1596056] Re: output of invoke-rc.d for systemd units un-debuggable on failure

2017-03-01 Thread Steve Langasek

** Description changed:

  [SRU Justification]
  Currently if a systemd unit fails to start in a non-interactive upgrade and 
all you have is a log, it's impossible to debug.  Fix this so that logs contain 
the actual details of the unit failure.
  
  [Test case]
  1. Get a root shell.
  2. Run "sed -e's,sbin/sshd,sbin/sshd-noexists,; /Alias/d' 
/lib/systemd/system/ssh.service > /lib/systemd/system/ssh-noexists.service"
  3. Run 'systemctl enable ssh-noexists'
- 4. Run 'invoke-rc.d ssh-noexists start'
- 5. Verify that the command directs you to run 'systemctl status' for details, 
and provides no details.
- 6. Install init-system-helpers from -proposed.
- 7. Run 'invoke-rc.d ssh-noexists start'.
- 8. Verify that the command provides details about the failure to start 
ssh-noexists service.
- 9. Run 'systemctl disable ssh-noexists'.
- 10. Run 'rm -f /lib/systemd/system/ssh-noexists.service'.
+ 4. Run 'ln -s ../init.d/ssh /etc/rc5.d/S02ssh-noexists'
+ 5. Run 'invoke-rc.d ssh-noexists start'
+ 6. Verify that the command directs you to run 'systemctl status' for details, 
and provides no details.
+ 7. Install init-system-helpers from -proposed.
+ 8. Run 'invoke-rc.d ssh-noexists start'.
+ 9. Verify that the command provides details about the failure to start 
ssh-noexists service.
+ 10. Run 'systemctl disable ssh-noexists'.
+ 11. Run 'rm -f /lib/systemd/system/ssh-noexists.service'.
+ 12. Run 'rm -f /etc/rc5.d/S02ssh-noexists'
  
  [Regression potential]
  Minimal.  On the failure case, an additional command is run; the additional 
command is guarded with || true.
  
  [Original description]
  
  When invoke-rc.d is called on a systemd system, if the unit fails to
  start, you get output like:
  
  Created symlink 
/etc/systemd/system/multi-user.target.wants/openafs-fileserver.service → 
/lib/systemd/system/openafs-fileserver.service.
  Job for openafs-fileserver.service failed because the control process exited 
with error code.
  See "systemctl status openafs-fileserver.service" and "journalctl -xe" for 
details.
  invoke-rc.d: initscript openafs-fileserver, action "start" failed.
  dpkg: error processing package openafs-fileserver (--configure):
   subprocess installed post-installation script returned error exit status 1
  
  The output shown here comes from systemctl itself, and is usually fine.
  The admin who ran systemctl can run those other commands to debug.
  
  However, when called by invoke-rc.d, this output is usually seen only in
  a log file; maybe submitted in a bug report, maybe attached to something
  like an autopkgtest:
  
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-yakkety/yakkety/armhf/o/openafs/20160624_174535@/log.gz
  
  By the time someone looks at this log output, it is often too late to
  run those commands in order to debug the failure.
  
  invoke-rc.d should call these commands for us on systemd unit failure,
  so that the relevant debugging information is included in the log where
  it can help.
  
  We don't want to call 'journalctl -xe', which might leak information
  into the log from other jobs, but 'journalctl -x -u ' may be
  appropriate.

** Tags removed: removal-candidate verification-needed
** Tags added: verification-done

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

Title:
  output of invoke-rc.d for systemd units un-debuggable on failure

Status in init-system-helpers package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Xenial:
  Fix Committed

Bug description:
  [SRU Justification]
  Currently if a systemd unit fails to start in a non-interactive upgrade and 
all you have is a log, it's impossible to debug.  Fix this so that logs contain 
the actual details of the unit failure.

  [Test case]
  1. Get a root shell.
  2. Run "sed -e's,sbin/sshd,sbin/sshd-noexists,; /Alias/d' 
/lib/systemd/system/ssh.service > /lib/systemd/system/ssh-noexists.service"
  3. Run 'systemctl enable ssh-noexists'
  4. Run 'ln -s ../init.d/ssh /etc/rc5.d/S02ssh-noexists'
  5. Run 'invoke-rc.d ssh-noexists start'
  6. Verify that the command directs you to run 'systemctl status' for details, 
and provides no details.
  7. Install init-system-helpers from -proposed.
  8. Run 'invoke-rc.d ssh-noexists start'.
  9. Verify that the command provides details about the failure to start 
ssh-noexists service.
  10. Run 'systemctl disable ssh-noexists'.
  11. Run 'rm -f /lib/systemd/system/ssh-noexists.service'.
  12. Run 'rm -f /etc/rc5.d/S02ssh-noexists'

  [Regression potential]
  Minimal.  On the failure case, an additional command is run; the additional 
command is guarded with || true.

  [Original description]

  When invoke-rc.d is called on a systemd system, if the unit fails to
  start, you get output like:

  Created symlink 
/etc/systemd/system/multi-u

[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

2017-03-01 Thread Konstantinos Marinopoulos

i have  the same problem with the sound but also my keyboard at my
e200ha is not working at all any solution?

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  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.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

2017-03-01 Thread Juan Jesús García de Soria

About problems with the keyboard and/or touchpad, try disabling fast
boot in the BIOS, or passing the "i8042.reset" parameter to the kernel
command line.

It looks like the fast boot option won't initialize the keyboard
controller (http://wiki.osdev.org/%228042%22_PS/2_Controller) into a
state that the Linux kernel will be able to use by default.

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  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.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1661406] Re: apparmor failing to be purged when /var/lib/apparmor/profiles or /var/lib/apparmor doesn't exist

2017-03-01 Thread Tyler Hicks

All releases are technically affected but, in practice, this only shows
up on 14.04. I'm going to upload a fix to Zesty and then prepare a SRU
for 14.04. I don't plan on fixing any other stable releases as the
risk/reward trade-off from rebuilding the apparmor package just doesn't
make sense.

** Summary changed:

- apparmor failing to be purged on trusty
+ apparmor failing to be purged when /var/lib/apparmor/profiles or 
/var/lib/apparmor doesn't exist

** Changed in: apparmor (Ubuntu)
   Status: Invalid => In Progress

** Changed in: apparmor (Ubuntu)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

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

Title:
  apparmor failing to be purged when /var/lib/apparmor/profiles or
  /var/lib/apparmor doesn't exist

Status in apparmor package in Ubuntu:
  In Progress
Status in apparmor source package in Trusty:
  In Progress

Bug description:
  [Impact]

  The apparmor package cannot be successfully purged when
  /var/lib/apparmor/profiles or /var/lib/apparmor do not exist. This is
  the case in default installs of the apparmor
  2.10.95-0ubuntu2.5~14.04.1 package in Ubuntu 14.04 LTS.

  [Test Case]

  Ensure that /var/lib/apparmor/profiles does not exist and then `apt-
  get purge apparmor`.

  [Regression Potential]

  Very low. The only real regression potential comes from rebuilding the
  package itself. To counter this risk, I'll be going through the
  AppArmor Test Plan with the package once it is built in trusty-
  proposed:

https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor

  [Original Report]

  Version: 2.10.95-0ubuntu2.5~14.04.1

  When executing apt -y purge apparmor.

  The purge run but has errors as files do not exist and the rmdir fails
  to execute.

  rmdir: failed to remove '/var/lib/apparmor/profiles': No such file or
  directory

  Steps to reproduce:
  apt-get update
  apt-get -y install apparmor
  apt -y purge apparmor

  I will put workarounds in place for now in puppet but this is making
  puppet not like it..

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

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

[Touch-packages] [Bug 1661406] Re: apparmor failing to be purged when /var/lib/apparmor/profiles or /var/lib/apparmor doesn't exist

2017-03-01 Thread Tyler Hicks

** Description changed:

+ [Impact]
+ 
+ The apparmor package cannot be successfully purged when
+ /var/lib/apparmor/profiles or /var/lib/apparmor do not exist. This is
+ the case in default installs of the apparmor 2.10.95-0ubuntu2.5~14.04.1
+ package in Ubuntu 14.04 LTS.
+ 
+ [Test Case]
+ 
+ Ensure that /var/lib/apparmor/profiles does not exist and then `apt-get
+ purge apparmor`.
+ 
+ [Regression Potential]
+ 
+ Very low. The only real regression potential comes from rebuilding the
+ package itself. To counter this risk, I'll be going through the AppArmor
+ Test Plan with the package once it is built in trusty-proposed:
+ 
+   https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor
+ 
+ [Original Report]
+ 
  Version: 2.10.95-0ubuntu2.5~14.04.1
  
  When executing apt -y purge apparmor.
  
  The purge run but has errors as files do not exist and the rmdir fails
  to execute.
  
  rmdir: failed to remove '/var/lib/apparmor/profiles': No such file or
  directory
  
  Steps to reproduce:
  apt-get update
  apt-get -y install apparmor
  apt -y purge apparmor
  
  I will put workarounds in place for now in puppet but this is making
  puppet not like it..

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

Title:
  apparmor failing to be purged when /var/lib/apparmor/profiles or
  /var/lib/apparmor doesn't exist

Status in apparmor package in Ubuntu:
  In Progress
Status in apparmor source package in Trusty:
  In Progress

Bug description:
  [Impact]

  The apparmor package cannot be successfully purged when
  /var/lib/apparmor/profiles or /var/lib/apparmor do not exist. This is
  the case in default installs of the apparmor
  2.10.95-0ubuntu2.5~14.04.1 package in Ubuntu 14.04 LTS.

  [Test Case]

  Ensure that /var/lib/apparmor/profiles does not exist and then `apt-
  get purge apparmor`.

  [Regression Potential]

  Very low. The only real regression potential comes from rebuilding the
  package itself. To counter this risk, I'll be going through the
  AppArmor Test Plan with the package once it is built in trusty-
  proposed:

https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor

  [Original Report]

  Version: 2.10.95-0ubuntu2.5~14.04.1

  When executing apt -y purge apparmor.

  The purge run but has errors as files do not exist and the rmdir fails
  to execute.

  rmdir: failed to remove '/var/lib/apparmor/profiles': No such file or
  directory

  Steps to reproduce:
  apt-get update
  apt-get -y install apparmor
  apt -y purge apparmor

  I will put workarounds in place for now in puppet but this is making
  puppet not like it..

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

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

[Touch-packages] [Bug 1630860] Re: [HDA-Intel - HDA Intel PCH, playback] Playback problem

2017-03-01 Thread caltinay

coppermine, are you referring to the dock or the laptop headphone jack?
I am now on kernel 4.9.6-3 in Debian and the dock's jack is still not working.
I have checked and the snd-hda-codec-realtek module is in fact loaded and used.

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Playback problem

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

Bug description:
  Lenovo Thinkpad P50 with docking station

  Issues: Headphone jack on station not detected; no sound (works without 
docking station)
  Issues: Sound via HDMI on station not detected; no sound (works without 
docking station)

  Since all outputs are routed via the Thunderbolt chip, my guess is
  that it's related to the pin setup (lenovo-dock) in Alsa. Without the
  dock, everything works, headphone/mic jack on the P50 itself is
  hotplug (switches from speaker to headphones right away).

  Screenshots (with and without docking station) attached.

  Thanks and LG,
  Wolfgang

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-38.57~14.04.1-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: symap_custom_dkms_x86_64 nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wjl2943 F pulseaudio
   /dev/snd/controlC0:  wjl2943 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Oct  5 14:14:02 2016
  InstallationDate: Installed on 2016-09-10 (24 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: HDA NVidia - HDA NVidia
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/10/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET52W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS1EH0B
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET52W(1.26):bd05/10/2016:svnLENOVO:pn20EQS1EH0B:pvrThinkPadP50:rvnLENOVO:rn20EQS1EH0B:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20EQS1EH0B
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-10-04T12:48:36.270399

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

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

[Touch-packages] [Bug 1629797] Re: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up

2017-03-01 Thread Mathew Hodson

** Changed in: dbus (Ubuntu)
Milestone: ubuntu-16.11 => None

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

Title:
  resolve service in nsswitch.conf adds 25 seconds to failed lookups
  before systemd-resolved is up

Status in cloud-init:
  Fix Released
Status in D-Bus:
  Unknown
Status in cloud-init package in Ubuntu:
  Fix Released
Status in dbus package in Ubuntu:
  Won't Fix
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact] 
  In cases where cloud-init used dns during early boot and system was
  configured in nsswitch.conf to use systemd-resolvd, the system would
  timeout on dns attempts making system boot terribly slow.

  [Test Case]
  Boot a system on GCE.
  check for WARN in /var/log/messages
  check that time to boot is reasonable (<30 seconds).  In failure case the
  times would be minutes.

  [Regression Potential]
  Changing order in boot can be dangerous.  There is real chance for 
  regression here, but it should be fairly small as xenial does not include
  systemd-resolved usage.  This was first noticed on yakkety where it did.

  [Other Info]
  It seems useful to SRU this in the event that systemd-resolvd is used
  on 16.04 or the case where user upgrades components (admittedly small use
  case).

  === End SRU Template ===


  
  During boot, cloud-init does DNS resolution checks to if particular metadata 
services are available (in order to determine which cloud it is running on).  
These checks happen before systemd-resolved is up[0] and if they resolve 
unsuccessfully they take 25 seconds to complete.

  This has substantial impact on boot time in all contexts, because
  cloud-init attempts to resolve three known-invalid addresses ("does-
  not-exist.example.com.", "example.invalid." and a random string) to
  enable it to detect when it's running in an environment where a DNS
  server will always return some sort of redirect.  As such, we're
  talking a minimum impact of 75 seconds in all environments.  This
  increases when cloud-init is configured to check for multiple
  environments.

  This means that yakkety is consistently taking 2-3 minutes to boot on
  EC2 and GCE, compared to the ~30 seconds of the first boot and ~10
  seconds thereafter in xenial.

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

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

[Touch-packages] [Bug 1665371] Re: Relaunch after crash doesn't work right for gnome-terminal

2017-03-01 Thread Jeremy Bicha

gnome-terminal is an unusual app with a server and a client. I think it
might be easiest if the Relaunch button would not show for crashes
related to gnome-terminal.

** Summary changed:

- restrictive permissions after relaunch from crash message box
+ Relaunch after crash doesn't work right for gnome-terminal

** Also affects: apport (Ubuntu)
   Importance: Undecided
   Status: 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/1665371

Title:
  Relaunch after crash doesn't work right for gnome-terminal

Status in apport package in Ubuntu:
  New
Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I was using gnome-terminal on Ubunutu 14.04 when it crashed.  When the
  crash notification message box appeared ("submit dump", etc.) there
  was an option to relaunch the terminal.  I chose this option.

  Git started exhibiting strange behaviours when trying to clone
  repositories, claiming it did not have permission even if ran within a
  directory with 777.  Eventually I realised it may be a terminal issue
  and when I closed it and opened a new one from the launcher the
  permissions error disappeared.

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

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

[Touch-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts

2017-03-01 Thread Jeremy Bicha

yzp15, could you please report this upstream?

https://bugzilla.gnome.org/enter_bug.cgi?product=gtk%2B
https://wiki.ubuntu.com/Bugs/Upstream/GNOME.

If you have done so, please tell us the number of the upstream bug (or
the link), so we can add a bugwatch that will inform us about its
status. Thanks in advance.

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

Title:
  mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() -
  while editing Keyboard Shortcuts

Status in gnome-terminal package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in mate-terminal package in Ubuntu:
  New

Bug description:
  1) 
  $ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64

  2) 
  $ apt-cache policy mate-terminal
  mate-terminal:
Installed: 1.17.0-0ubuntu1
Candidate: 1.17.0-0ubuntu1
  3) 
  Open mate-terminal
  Select "Edit" -> "Keyboard Shortcuts"
  Select "Help"->"Contents", click on default shortcut key "F1" to change
  Try to set it to various key sequences. Sometimes bug is triggered by 
pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting 
Ctrl-Shift-W / Crtl-Shift-Alt-W
  Expected: changed keyboard shortcut for "Help"->"Contents"

  4) Abort and closed mate-terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-terminal 1.17.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 23 09:33:19 2017
  ExecutablePath: /usr/bin/mate-terminal
  ExecutableTimestamp: 1484233434
  InstallationDate: Installed on 2017-02-22 (1 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: mate-terminal
  ProcCwd: /home/user
  SegvAnalysis:
   Segfault happened at: 0x7f883e41c321 :
testb  $0x4,0x16(%rax)
   PC (0x7f883e41c321) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0x7001e) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: mate-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a()
  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/gnome-terminal/+bug/1667227/+subscriptions

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

[Touch-packages] [Bug 1669052] Re: [unity8] launcher shows the tooltip at the wrong position if you play with the launcher's size for a while

** Tags added: unity8-desktop

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

Title:
  [unity8] launcher shows the tooltip at the wrong position if you play
  with the launcher's size for a while

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  ubuntu 17.04 unity8
  [unity8] launcher shows the tooltip at the wrong position if you play with 
the launcher's size for a while

  see attached screenshot, the mouse is hovering the calculator app and
  the tooltip is Gallery, also if i right click on the calculator it
  opens the calculator menu (calculator/unpin calculator) beside the
  gallery app.

  how to reproduce: have a lot of apps pinned to the launcher, open
  system settings and play with the launcher size

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

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

[Touch-packages] [Bug 1669047] Re: [Unity8] launcher pips include child windows like menus

** Summary changed:

- [Unity8] launcher pips include child windows
+ [Unity8] launcher pips include child windows like menus

** Tags added: unity8-desktop

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

Title:
  [Unity8] launcher pips include child windows like menus

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  ubuntu 17.04 unity8

  the launcher is showing some white dots for every opened
  window/instance of the same app (from what i understand, like unity7),
  but if you open Kate and then right click on document and then open
  then open a submenu now the launcher shows 3 white dots (left side of
  Kate's icon)

  see attached screenshot

  i am not super sure but i think that the launcher is counting menus as
  instances or something

  also not specific to kate, happens with lot of apps (can't tell if bug
  or feature)

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

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

[Touch-packages] [Bug 1665289] Re: [unity8] Ubuntu Software can't launch installed apps from within its GUI

** Summary changed:

- [unity8]Ubuntu Software doesn't launch installed apps
+ [unity8] Ubuntu Software can't launch installed apps from within its GUI

** Tags added: unity8-desktop

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

Title:
  [unity8] Ubuntu Software can't launch installed apps from within its
  GUI

Status in Canonical System Image:
  New
Status in gnome-software package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  ubuntu 17.04 unity8

  launch Ubuntu Software
  install some random app (deb or snap) and after it is installed click on the 
Launch button. 
  the app doesn't launch

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

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

[Touch-packages] [Bug 1393578] Re: Subpixel order not included in Mir display information

Hmm, that's interesting. Using integrated Intel graphics (DisplayPort) I
get subpixel order "unknown" but if I use a radeon card (DVI) on the
same monitor then it can detect "HRGB".

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

Title:
  Subpixel order not included in Mir display information

Status in Mir:
  In Progress
Status in Mir 0.26 series:
  Triaged
Status in QtMir:
  Triaged
Status in qtubuntu:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Just capturing something mentioned by Trevinho on IRC this morning.
  MirDisplayOutput does not include subpixel ordering, it could and
  should though. The information is exposed on the drm side
  (drmModeSubPixel). Marking as wishlist in absence of other
  information.

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

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

[Touch-packages] [Bug 1666495] Re: [Zesty] No default apps shown on first start in kvm oem end user

2017-03-01 Thread Mathew Hodson

** Project changed: unity-lens-applications => ubuntu

** No longer affects: ubuntu

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

Title:
  [Zesty] No default apps shown on first start in kvm oem end user

Status in zeitgeist package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Install the latest iso in kvm
  2. Click on Ubuntu button

  EXPECTED:
  I expect to see Thunderbird, rhythmbox, totem, etc.  There are normally 5 
default apps shown.

  ACTUAL:
  I get what you see in the attached screenshot.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-02-21 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170221)
  Package: unity-lens-applications 7.1.0+16.10.20160927-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Tags:  zesty
  Uname: Linux 4.10.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1669237] [NEW] intel graphicss

2017-03-01 Thread pravin kharade

Public bug reported:

send some letest updates for ubuntu and student need labview
software in linux so plz update it

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
Uname: Linux 4.8.0-39-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  370.28  Thu Sep  1 19:45:04 
PDT 2016
 GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Mar  2 08:47:02 2017
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.8.0-22-generic, x86_64: installed
 bbswitch, 0.8, 4.8.0-39-generic, x86_64: installed
 nvidia-370, 370.28, 4.8.0-22-generic, x86_64: installed
 nvidia-370, 370.28, 4.8.0-39-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1457]
 NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. GF119M [GeForce 610M] [1043:1457]
InstallationDate: Installed on 2017-02-16 (13 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: ASUSTeK COMPUTER INC. K55VD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-39-generic 
root=UUID=9b4945de-985d-48fd-870f-31eebdd9e5fc ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/20/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K55VD.404
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K55VD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK55VD.404:bd08/20/2012:svnASUSTeKCOMPUTERINC.:pnK55VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: K55VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Thu Mar  2 01:19:36 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1

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


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

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

Title:
  intel graphicss

Status in xorg package in Ubuntu:
  New

Bug description:
  send some letest updates for ubuntu and student need labview
  software in linux so plz update it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  Uname: Linux 4.8.0-39-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  370.28  Thu Sep  1 19:45:04 
PDT 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_p

[Touch-packages] [Bug 1653354] Re: I am having the same problem on Thinkpad T460s

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

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

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

Title:
  I am having the same problem on Thinkpad T460s

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Hi, I am having the same problem with my cursor jumping and clicking to the 
left corner bottom where the Trash Tab opens. It happens when I am using both 
hands, clicking on my touchpad with my left hand and using my right hand to 
move the cursor.
  I tried Ubuntu 16.04 and 16.10, I tried several upgraded, new driver etc. But 
the problem occurs always.

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

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

[Touch-packages] [Bug 1652585] Re: [Dell XPS 13 9333] Fonts are broken after suspend/resume somtimes